Project duration
Summer 2024 (3 months)
Role
Lead Product Designer (IC + team lead)
CLient
RYVYL, Inc
Domain
FinTech / Payments, Onboarding & Compliance, B2B SaaS

Streamlining Multi-Step Business Workflows

Improving the end-to-end application flow for merchant onboarding.

Background

As Lead Product Designer, I overhauled a complex, compliance-driven merchant application to improve conversion and efficiency. Streamlining multi-step workflows and simplifying regulatory requirements led to faster completion times, lower abandonment, and higher overall success rates. I owned the full discovery and design process, from research and analysis to stakeholder alignment, experience mapping, and final design execution.

Analytics were showing a high rate of abandonment during the merchant application process.

This project zoomed in on the first stretch of the merchant journey: the path from signing up to finally hitting “submit” on the business application. It sounds simple, but in reality this was where we were losing the most merchants. The flow was long, compliance-heavy, and left users feeling underprepared and overwhelmed.

Questionnaire step of the final application design.

~ TLDR ~

Problem
High-risk merchants faced a long, compliance-heavy application for payment processing approval. The complexity led to slow submissions and high abandonment.
Approach
Used user insights and behavioral data to guide a redesign of the multi-step application workflow, simplifying flows and content to reduce friction while maintaining compliance.
Outcomes
Improved merchant application completion rates and significantly reduced task completion time by streamlining complex compliance steps into a clearer, faster workflow.
+15
%
Completion rate
-18
min
Task completion time
Confidentiality notice: Examples and artifacts are redacted/representative. Flow diagrams omit sensitive implementation details.

The Task

What we set out to achieve

Our analytics tools surfaced a critical problem: a large percentage of merchants were abandoning the application midway through. The challenge was to redesign this complex, compliance-heavy workflow in a way that improved completion rates and time-to-complete, while maintaining the rigor required for high-risk payment processing

To guide the redesign, I defined a clear objective and identified key success metrics to measure impact and validate outcomes. These metrics became the foundation for evaluating whether our design changes were truly improving the experience.

Completion rate
What percentage of merchants complete the application, and where the applicants drop off in the process.
Task completion time
How long it took to complete the application, end-to-end, from signup to submission.
Customer Effort Score (CES)
On a 1–7 scale, how easy merchants felt the process was after completing it.
Objective:
Redesign the compliance-heavy merchant application to minimize abandonment, reduce user friction, and accelerate onboarding.
Success measure:
Demonstrated improvement in conversion from application start to completion, alongside measurable time savings for merchants without compromising compliance.

Designing under tight constraints

Designing this flow wasn’t just about making things “simpler.” There were complex considerations I had to take into account, and some necessary requirements and I had to work within.

Multiple user types
Small merchants expected speed and guidance, enterprise merchants needed flexibility and thoroughness. On top of that, not every applicant would even qualify, so the flow had to handle both serious and unqualified leads.
Regulatory & compliance
The application had to collect everything required for KYC, AML, and PCI. That meant detailed questions and non-negotiable steps.
Risk tolerance
Compliance and underwriting teams wanted airtight checks against fraud and bad actors. Every design choice had to balance merchant convenience with business safety.
Technical realities
Some parts of the flow were tied to legacy systems and manual reviews. Undoing those processes required extra effort and would expanded project scope.

Research & Discovery

Finding clarity through research

Before diving into design, I conducted user research and data analysis to uncover where merchants struggled most in the application process and why abandonment was occurring.

Examine behavioral data
Quantitative data on abandonment rate, funnel analysis, task completion time, session recordings, etc.
Collect qualitative insights
Collect and organize user sentiment through feedback submissions, support tickets, and CES testing results.
Stakeholder interviews
Speak with key stakeholders who have insight into the process to develop empathy and perspective.

Finding patterns in the data

To understand how merchants were interacting with the application, I analyzed quantitative data such as funnel drop-off points, field-level error rates, and average time-to-complete across each step of the flow.

Behavior insights revealed problematic UI elements
Specific steps in the funnel analysis were showing heavy dropoff

Turning feedback into insight

To complement the analytics, I gathered qualitative insights by reviewing merchant feedback, Customer Effort Score (CES) comments, and support queries to identify pain points in language, flow, and overall usability

Collective qualitative insights from merchants

Learning from the teams behind the process

In addition to merchant insights, I conducted interviews with internal stakeholders who regularly touched the application, including compliance, risk, underwriting, and support teams. These sessions helped surface where they saw deficiencies in the current workflow, what improvements could make their jobs easier, and how proposed changes might impact their processes downstream.

Sales / Operations
Get insights into applicants, and get better understanding of sales process with new clients.
Compliance
Understand what data is required, where inconsistent applicant info might be creating bottlenecks
Support
Understand common complaints, where they see users struggle, what the support needs are.

Where merchants struggled

From the discovery work, four key pain points stood out in the merchant application. These findings highlighted the biggest sources of friction that were preventing merchants from completing the application successfully.

Pain point 1
Long and complex flow
Even with a progress bar, the application still felt like a marathon. There were too many steps and too much information packed into a single flow.
Pain point 2
Interrupted and abandoned applications
Merchants often paused mid-application to gather documents or clarify requirements, and many never returned to finish.
Pain point 3
Clunky form patterns
Non-practical field layouts, confusing validation errors, lack of inline guidance, and poor accessibility created unnecessary friction.
Pain point 4
High support burden
Confusing requirements and failed submissions drove a high volume of support tickets, creating extra work for internal teams and slowing down onboarding.

Key Design Decisions

Mapping the roadblocks along the way

To better understand where merchants struggled, I mapped the customer journey across each stage of the application. By combining analytics data with qualitative inputs like feedback, CES comments, and support queries, I was able to pinpoint the exact stages where friction occurred and build a clearer picture of the end-to-end experience.

Customer journey map for each stage of the application flow

Framing the way forward

With the main pain points identified, I began rapidly wireframing different approaches to the application. This allowed me to test new form patterns, try out simplified flows, and get early feedback before investing in high-fidelity designs. Wireframes gave us a fast way to iterate, visualize solutions, and validate which ideas reduced friction for merchants.

The wireframes that performed best in testing became the foundation for the final design solutions.

Rapid wireframes explored simpler flows and conditional logic/branching.

Designing against the biggest frictions

With the four main pain points identified, I focused on addressing each one directly through targeted design changes: simplifying the flow, creating guardrails to reduce abandonment, introducing consistent form patterns, and reducing the support burden through clearer guidance.

Pain point 1
Long and complex flow
Even with a progress bar, the application still felt like a marathon. There were too many steps and too much information packed into a single flow.
Solutions:
  • Merged related steps
  • Remove unnecessary steps that are not relevant to applicant
  • Design branching logic flows for specific cases to reduce redundant data
  • Move non-critical tasks downstream to spread effort out and not frontload
Before...
Updated design
Pain point 2
Interrupted and abandoned applications
Merchants often paused mid-application to gather documents or clarify requirements, and many never returned to finish.
Solutions:
  • Informed users of document requirements
  • Added additional microcopy and contextual guidance to prepare and inform users
  • Created automated nudge emails to inform and encourage users back to finish their application
One of my clients didn’t have all their documentation ready to go, so he left the application, not knowing that his progress would be saved. He didn’t want to fill everything out again, so he never came back.
Before...
Updated design
Pain point 3
Clunky form patterns
Non-practical field layouts, confusing validation errors, lack of inline guidance, and poor accessibility created unnecessary friction.
Solutions:
  • Optimized form patterns for better usability
  • Added more effective inline error handling
  • Updated some field patterns like disabled states and field labels for improved accessibility
  • Implemented more branching logic for progressive disclusure, reducing cognnjitve load
Before...
Updated design
Pain point 4
High support burden
Confusing requirements and failed submissions drove a high volume of support tickets, creating extra work for internal teams and slowing down onboarding.
Solutions:
  • Provided more contextual guidance through micro-copy
  • Primed users for applicaiton expecations and requirments
  • Added more effective inline error handling and guidance
  • Refined button patterns to reduce visual clutter
Before...
Updated design

Challenges

No redesign comes without its hurdles. Along the way, I ran into a few challenges that tested both the design and collaboration process, from navigating compliance limitations to balancing scope with user needs. The next two examples dive into the toughest moments and how I worked through them.

challenge 1
Form pattern impact vs effort
New form and field patterns were considered, but the engineering effort was too high relative to the expected UX benefit.
What I did:
Since the engineering effort expanded beyond our initial scope, I worked with the dev team to evaluate trade-offs, document the design for future adoption, and refocus the current sprint on lower-effort improvements that delivered meaningful impact without causing scope creep. My team ended up using the new form patterns in a design down the road successfully.
Before...
Original form patterns and layout was dense and visually cluttered.
After...
New single-column form pattern reduces visual clutter and cognitive load, while improving error prevention.
challenge 2
Strict compliance requirements
The merchant application had to meet rigorous KYC, AML, and underwriting standards, making even small UX changes sensitive to regulatory review. In this case, the Bank Account step was removed from the application and moved downstream to reduce front-loaded friction, but was needed by the underwriters for their review process.
What I did:
Many of the proposed changes risked altering mandatory data-collection steps, so I partnered closely with compliance and legal teams to refine copy, adjust field logic, and reorder sections, maintaining regulatory accuracy while making the experience feel simpler and more approachable. The removal of the Bank Account step did slip through the cracks, but there was already a fallback flow for the collection of this data so it was easy to design this step back into the application process with the new form patterns.
Before...
Previous step for collecting bank account information.
After...
New Bank Account step with better inline guidance and form patterns.

Achievements

Results that moved the needle

The redesign led to measurable improvements across key engagement and completion metrics. By simplifying the flow, clarifying content, and improving form interactions, we saw faster submission times, fewer drop-offs, and a higher overall completion rate.

Bonus metric: Support saw a 21% reduction in support tickets relating to the application flow.
59
%
Completion rate
Percent of merchants finishing applications (up from 44%)
28
min
Time to complete
Avgerage time per application (up from 46min)
4.3
Customer Effort Score (CES)
Perceived ease of completing the application (up from 2.2)

Impact beyond the numbers

The redesign led to measurable improvements across key engagement and completion metrics. By simplifying the flow, clarifying content, and improving form interactions, we saw faster submission times, fewer drop-offs, and a higher overall completion rate.

Customer Effort Score (CES) feedback
Applicant feedback
Merchants described the application as clearer, shorter and less intimidating, with fewer mid-flow surprises.
Improved trust
Feedback reported improved trust across the flow, increased thanks to more granular upfront requirements and guidance.
Stakeholder alignment
Sales and onboarding teams reported merchants having an improved sentiment and success during the onboarding process, getting the sales team onboard with our changes.

How the work scaled beyond this project

The redesign didn’t just improve the application, it also shaped how future products would be built. The work established scalable patterns, strengthened cross-team collaboration, and influenced roadmap decisions that extended beyond this single flow.

Scalable patterns
Established reusable, scalable design patterns for compliance-heavy forms, creating a foundation for future products and workflows.
Elevating design through data
Demonstrated the impact of data and metrics in driving design decisions, increasing the design team’s influence and ownership in product strategy.
Foundation for automation
Laid the groundwork for automation and AI-driven document checks and KYC processes, reducing manual review and paving the way for future efficiency gains.