Smaller UPI apps flag competition risks in NPCI’s proposed UPI Meta checkout framework
Smaller UPI players say NPCI’s proposed UPI Meta/Checkout framework could entrench PhonePe and Google Pay by preserving saved payment preferences, potentially limiting choice at checkout and raising consent, operational and dispute-resolution concerns.
What happened
National Payments Corporation of India (NPCI) · Smaller UPI apps oppose NPCI’s UPI Meta/Checkout proposal, saying saved UPI preferences could cement PhonePe and
Why this matters
Evaluate partnerships or acquisitions among smaller UPI players and checkout-enablement vendors that can offer merchant-friendly, consent-led alternatives if the framework reshapes payment-app access.
What to watch
- NPCI consultation paper revisions specifying whether saved UPI app preferences can persist across merchants or devices.
- Requirements for neutral app ordering, user-visible switch options, default-reset intervals or prohibition of pre-selected apps.
- Clarification of who owns failed-payment, refund and dispute resolution liability across merchant, aggregator, bank and TPAP.
- Adoption commitments from major payment aggregators, e-commerce marketplaces, food delivery platforms and large offline merchant networks.
- RBI or CCI commentary linking UPI checkout design to competition, consumer choice or data-consent concerns.
- Changes in transaction-share trends for smaller TPAPs after pilot deployments.
- NPCI is likely to convene further consultations with TPAPs, payment aggregators, merchants and banks on default selection, consent and grievance ownership.
- Large payment apps may support standardisation publicly while lobbying for continuity of saved preferences and low-friction return-user flows.
- Smaller UPI apps may seek mandated app-neutral checkout screens, periodic default re-selection, portability of payment preferences and auditable ranking rules.
- Merchants and payment aggregators may test direct UPI intent flows, multi-app selectors and fallback routing to protect conversion while avoiding dependence on a single checkout standard.
- Regulatory scrutiny may expand from market share to interface design, dark-pattern risk, data minimisation and whether checkout defaults constitute discriminatory access.