VoPay

Designing Faster Payment Experiences

VoPay is a Canadian fintech company that provides embedded payment solutions, enabling businesses to automate payouts, bank transfers, and payment processing through a unified platform.

As part of the interview process, I completed a product design challenge focused on improving a core payment workflow, creating a more intuitive and user-friendly experience while addressing business and usability goals.

View Final Design

Client

Fintech

Duration

1 day

Team

Solo Project

Scope of work

End-to-End Design

Web App Design

Product Design

Competitive Analysis

UIUX Design

Wireframing

Prototyping

I was given a product design challenge as part of the interview process, with less than 24 hours to complete both the redesign and prepare presentation slides, requiring fast problem-solving, clear design thinking, and strong prioritization under time constraints.

Customer support was receiving 40% more tickets for cross‑border payments compared to domestic transactions, which indicated that users were not getting the clarity they needed from the product experience. Users struggled to understand what happens after submitting a payment, how fees are applied, and when funds will be delivered.

In this design challenge, I took end‑to‑end ownership of the design track and its coordination with product and engineering. My responsibilities included: scoping the solution into MVP and Phase 2, planning the timeline, aligning stakeholders (Support, Product, Sales), and collaborating with two part‑time frontend developers to ensure feasible delivery within 2.5 weeks.

The challenge was intentionally scoped to mirror realistic delivery conditions.

These constraints guided my decisions around scope, level of fidelity, and how to collaborate effectively with product and engineering.

1 week for design, 1.5 weeks for development

2 part‑time frontend developer

Limited direct access to end users due to typical B2B constraints.

I used a structured, end‑to‑end design process tailored to the compressed timeline and technical constraints.

Discovery

01

Research Current Experience

Review existing user flows, support tickets, and analytics to understand the current experience.

Gather Stakeholder Insights

Interview stakeholders to uncover business goals, technical constraints, and user needs.

Analyze the Market

Evaluate competitors to identify opportunities and industry best practices.

Define

02

Identify Constraints

Document business, technical, and project limitations.

Prioritize User Pain Points

Organize research findings to focus on the highest-impact problems.

Align on Success Metrics

Define goals, business impact, and technical feasibility with the team.

Design

03

Create Wireframes

Explore solutions through low- and mid-fidelity wireframes.

Design High-Fidelity UI

Develop polished interfaces with clear visual hierarchy and interactions.

Refine Through Iteration

Improve designs using feedback, usability insights, and microcopy.

Validate

04

Review Usability

Conduct heuristic evaluations and collect internal feedback.

Check Feasibility

Collaborate with PMs and developers to validate implementation.

Iterate & Finalize

Refine the design based on findings before development.

Handoff & QA

05

Prepare Developer Handoff

Deliver annotated designs, specs, and production-ready assets.

Support Development

Answer implementation questions and clarify design intent.

Perform Design QA

Verify the final product matches the approved design.

I formalized a simple project plan aligned with the fixed timeline and limited dev capacity.

Key notes:

● Use existing UI components where possible

● Break into MVP scope (basic confirmation + basic status)

● Phase 2: full progress bar and notifications

Week 1

UI Design + Dev Sync

Finalize problem framing, map user flows, produce mid‑ to high‑fidelity designs, and confirm scope and feasibility with PM and dev.

Week 2

Build MVP

Support developers in implementing the redesigned confirmation and status views, clarifying data needs and edge cases as they arise.

Week 3.5

QA + Deploy

Provide design QA, document issues, and collaborate on fixes to ensure the shipped experience matches the intended UX.

I redesigned the cross-border payment experience to improve transparency and reduce user uncertainty by introducing clearer fee breakdowns, payment status updates, and post-payment feedback. The solution prioritized an MVP approach that balanced user needs with technical feasibility.

The redesign would be evaluated through a mix of support volume, task clarity, user confidence, feature engagement, and transaction completion.

Reduction in cross-border payment inquiries related to fees, payment status, and delivery timelines.

Percentage of users who can correctly identify payment fees and expected delivery time before submitting a transaction.

Improvement in post-transaction satisfaction through surveys or CSAT.

Usage of payment status tracking and transaction details.

Higher completion rate for cross-border payments and fewer abandoned transactions.

• Prioritizing Impact Over Scope

Working within a constrained timeline reinforced the importance of identifying the highest-impact opportunities first. Rather than redesigning the entire payment experience, I focused on moments that directly influence user trust—fee transparency, payment status, and delivery expectations.

• Balancing User Needs with Technical Feasibility

Effective product design isn't just about creating the ideal experience; it's about delivering solutions that can realistically be built. By aligning the design with an MVP approach and existing UI components, I ensured the proposal balanced user value with engineering constraints.

• Designing for Trust for Fintech product

Cross-border payments involve uncertainty, making clear communication as important as the transaction itself. This project reinforced how thoughtful feedback, transparent information, and well-timed status updates can increase user confidence without adding unnecessary complexity.