YES Pay Biz — UPI payment collection mobile app

YES Pay Biz — UPI payment collection mobile app

Designing a merchant payment collection app for Yes Bank

India’s customers had moved to UPI, and merchants had to move with them. But collecting a payment is only the start of a merchant’s job. They also have to see where the money came from, which counter took it and when it reaches their account.

Yes Bank wanted to give merchants one app for all of that. YES Pay Biz is an end-to-end business app built on two payment rails: UPI and India’s CBDC (digital rupee). It handles collections, gives merchants control over their transaction data, automates settlements and lets one QR code serve multiple terminals.

I worked on it end to end, from research to developer handoff, alongside two other designers, with a PM as my main counterpart.

Role

UX Designer

Team

Product & Business teams 

Duration

12 months

Tools

Figma, Adobe Suits

The Problem, and Market Conditions

By January 2022, UPI had digitized how consumers pay. Merchant tools hadn’t kept up.

Behind the counter, merchants were still managing collections, settlements and multi-counter tracking with fragmented or manual workflows. A shop might take hundreds of digital payments a day, then reconcile them by hand.

At the same time, the RBI was signaling that a CBDC was coming. The future wasn’t going to be one payment rail. It was going to be two, and merchants would need a single place to handle both.

That was the opportunity: build the merchant tool the market was missing, ready for the rail that hadn’t launched yet.

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 were built to be reusable rather than bespoke per-screen which is what allowed the app to scale to 200+ 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.