YES Pay Biz — UPI payment collection mobile app

YES Pay Biz — UPI payment collection mobile app

Designing Merchant payemnt collection application for Yes Bank

Yes Bank needed an end-to-end business application for its merchant ecosystem for their merchants, one that could handle two payment sytems at once. The already-dominant UPI market, and India's emerging Central Bank Digital Currency (CBDC). Beyond collections, I designed the experience which the app had to give merchants real control over their transaction data, automate settlements, and let a single QR code serve multiple terminals.

I design end-to-end ecosystem from research through to developer handoff — with a team of two other designers and a PM as my primary counterpart.

Role

UX Designer

Team

Product & Business teams 

Duration

12 months

Tools

Figma, Adobe Suits

The Problem, and Market Conditions

By January 2022, In the fintech market UPI had already digitized consumer-side payments at scale, but merchant-side tooling hadn't caught up I saw most merchants were still managing collections, settlements, and multi-counter tracking with fragmented or manual workflows. At the same time, the RBI was signaling the arrival of CBDC, pointing to a near-future twin-rail payment ecosystem.

I understood this market and designed a experience for Yes Bank for their merchant collection app which will make sure for future of how merchant collection app will perform.

Research & Discovery

I started with sprint focused on one core capability Manage Terminal because it sat at the center of how merchants would actually run their day-to-day operations.

I did Collabrated directly with Product Managers early to align on strategic intent before any screens designed.

I Ran a structured competitive analysis of Paytm and PhonePe BIZ apps, not just cataloguing their features, but digging into why business users relied on those specific flows.

I led a series of UX brainstorming workshops with cross-functional stakeholders to convert market and business input into concrete use cases.

Key insight that shaped everything downstream:

I found in my on field research that Merchants spend roughly 80% of their time on the home screen. This single behavioral data point became the design principle behind the entire app.

Explore

Decision point: How should role-based terminal/QR access work?

I designed one of the core functionlity of the product how Yes bank end customer will able to access the role-based terminal and each terminal QR code

Where a sub-user's visibility is scoped to the specific counter(s) they're assigned to matched the actual mental model merchants described (counter-wise ownership).

Converge & Decide

I converged on the "upfront" design philosophy: no critical action should require more than the home or terminal-card level to complete. This wasn't an aesthetic choice — it was a direct response to the finding that small merchants often have limited financial-app literacy and simply don't have time to explore nested menus during a busy shift.

This principle was applied consistently across the app: Terminals, Settlements, and Sub-user management all follow the same "everything actionable at a glance" pattern — which is also what let the design scale into a system

As research showed landing page was having all important activities which merchanrt will be doing on daily basis

To keep fund in daily same work at shopkeer I have designed gamification so collection will be fun and profitable for them

Simiplied transaction/collection history with UPI, CBDC and eRupi payment mode

Cross-Functional Collaboration

With Product: Embedded early in strategic planning for the Manage Terminal flow, rather than receiving requirements after the fact.

With Business/Bank stakeholders: Personally ran interviews and testing sessions with the bank across five+ merchant groups (7–12 participants each) — not delegated to a researcher.

With Engineering: Ran multiple component-level workshops with the developer team post-UAT, walking through visual and interaction specs in Figma to ensure implementation fidelity.

With leadership/team: Managed a team of two designers, kept them aligned and motivated through a 12-month build, and personally owned final design QA before release.

Visual & System Craft

A major, durable output of this project was a complete Design Language System (DLS) — now the primary system underpinning Yes Pay BIZ. Because every screen in the app followed the same "upfront, card-first" interaction pattern, the components (terminal cards, action groups, status indicators) were built to be reusable rather than bespoke per-screen — which is what allowed the app to scale to 250+ screens without visual drift.

Validation

Closed User Group (CUG) Testing

I personally led interviews and usability sessions with 5+ merchant groups (7–12 participants each), observing real task completion on flows like "Complete Settlement" and "Add New Sub-user." Observations were fed directly back into design revisions before final release.

Refined designs delivered a 30–45% increase in engagement and task completion in subsequent testing — a direct, measurable validation of the upfront-design hypothesis.

User Acceptance Testing (UAT)

After CUG-driven revisions were implemented, I ran UAT with key stakeholders, testing every flow against business requirements to confirm the end-to-end experience was seamless before go-live.

Dummy text

Outcome & Impact

250+ screens shipped across the merchant app. Successful support for a dual-rail payment model (UPI + CBDC) ahead of most competitors

1L +

Downloads post-launch on playstore

30 min

Application time reduced from 60–80 minutes

30–45%

Lift in engagement and task completion

30 min

Application time reduced from 60–80 minutes

One System

Yes Bank central DS

~40%

Reduction in clicks

Leadership & Influence

  • Led and motivated a 3-person design team through a 12-month build cycle, from 0 to a released product.

  • Owned stakeholder alignment across the bank, Product, and Engineering — described in your own words as a "masterclass in stakeholder management," keeping distributed teams (client offices and remote) aligned on a single vision.

  • Authored the Design System that outlived this specific project and now governs future Yes Pay BIZ work — a direct, lasting evangelism of design standards within the org.

Reflection

This was my entry point into fintech, and it forced fast fluency in domains I hadn't designed for before — CBDC flows and POS collection logic among them. The clearest lesson wasn't visual or interaction design; it was that stakeholder alignment is a design skill — keeping a bank, a PM, engineers, and merchants pointed at the same problem definition mattered as much as any screen decision.

With great UX comes great responsibility.