Digiaccel · 2024

UPI Limit Clarity & Spend Runway

An ambient bank balance runway meter and 1-tap failover checkout flow that alerts users of daily transaction caps before payment initiation to eliminate payment failure anxiety.

ROLE
Product Designer (Fintech UX)
TIMELINE
3 Weeks
TEAM / CONTEXT
Aditya Diundi (UX & Interaction Design) · Fintech Mentor Review
Tags: Fintech, Payments, Error Recovery, Proactive UX

The Bottleneck

Over 350 million Indians execute billions of UPI transactions monthly, yet millions of payments fail abruptly with cryptic errors like 'Payment Limit Exceeded'.

Users only learn they breached a limit AFTER payment fails at grocery counters or hospital bill desks, causing intense social awkwardness and transaction anxiety.

UPI limits are fragmented: NPCI sets a ₹1,00,000 daily cap, individual banks impose secondary transaction-count limits (10 to 20 transfers/day), and user-set app limits conflict silently.

The Architecture & Scope

Core Architecture & Ownership

  • Researched NPCI regulatory limit specifications across Tier-1 and PSU banks.
  • Designed the pre-transaction ambient runway meter within the payment drawer.
  • Architected the 1-tap split-route failover checkout flow.

Technical & Operational Constraints

  • NPCI Regulatory Limits: Payment screen architecture must adhere to strict guidelines on beneficiary verification.
  • Zero Latency: Limit checks could not add extra round-trip delays to fast payment flows.

Process & Engineering Decisions

1. Ambient UPI Spend Runway

A proactive progress indicator in the payment drawer showing real-time daily usage before payment: 'Today: ₹42,000 / ₹1,00,000 used · 9 / 20 transfers remaining'.

UPI Limit Clarity Screen Flow Stages

Tradeoff: Displays remaining bank limit ambiently without adding an extra confirmation screen to checkout.

2. Intelligent Split-Route Checkout

When an amount exceeds a single bank's remaining daily cap, the interface suggests splitting the payment across linked secondary accounts without re-entering recipient VPA.

Intelligent Split-Route Failover Flow

Tradeoff: Requires secondary bank authorization PIN, but saves users from absolute payment failure at the counter.

The Impact

-38%
anticipated dropoff reduction at checkout
92%
user awareness of daily bank caps prior to payment
1 Tap
direct bank limit recovery settings access

Shifting fintech error handling from reactive post-failure alerts to ambient pre-transaction meters eliminated payment anxiety and improved transaction success rates.

Design Technologist Retrospective

"I would test an offline SMS-based limit sync fallback for rural users experiencing intermittent network connectivity."