education
Pay by Any UPI App Mandate: Why Payment Gateways Cannot Force Specific UPI Apps
Everything you need to know about the NPCI Pay by Any UPI App mandate: interoperability guidelines, deep-linking rules, and why app restriction hurts checkout conversion.
The core founding principle of India’s Unified Payments Interface (UPI) is universal interoperability. Unlike legacy closed-loop digital wallets where a customer with a Paytm wallet could not pay a merchant with a Mobikwik terminal, UPI was engineered so that any verified payer app can send funds to any verified merchant QR or VPA.
However, some payment gateways and proprietary ecosystem players have attempted to introduce subtle “app gating” or preference bias. The National Payments Corporation of India (NPCI) responded with the Pay by Any UPI App Mandate. Here is how it impacts merchants and checkout UX.
What is the Pay by Any UPI App Mandate?
Direct Answer: The Pay by Any UPI App Mandate is an NPCI compliance rule requiring all merchant checkout screens, QR codes, and intent selectors to offer complete, unbiased interoperability across all certified UPI Third-Party Application Providers (TPAPs) and bank apps. Acquirers and gateways are legally prohibited from locking checkout flows to exclusive apps or hiding competing UPI options.
Whether a buyer uses Google Pay, PhonePe, Paytm, CRED, Navi, Amazon Pay, or BHIM, every compliant UPI merchant setup must resolve the payment request seamlessly.
NPCI Interoperability and Deep-Linking Guidelines
Under the NPCI Procedural Guidelines on UPI Interoperability:
- Standardized BharatQR / UPI QR Specifications: Every printed or dynamically generated QR code must encode standardized key-value pairs conforming to NPCI specifications:
pa: Payee VPA address.pn: Payee display name.am: Exact order amount.tr: Transaction tracking reference.cu: Currency (INR).
- Intent Scheme Neutrality: On mobile browser checkouts, gateways must trigger the native generic URI scheme (
upi://pay?...). When invoked, the mobile operating system (Android or iOS) renders the device’s native app sheet, allowing the customer to choose their preferred app. - Prohibition of Dark Patterns: Gateways cannot intentionally fail or degrade competitor intent calls to promote their own affiliated consumer app.
How App Restrictions Damage Merchant Checkout Conversion
Merchants who implement single-app exclusivity or restrictive checkout flows suffer catastrophic drop-offs:
Customer Journey Comparison:
----------------------------
Case A (Restricted Flow):
Buyer selects UPI ➔ Forced to open "App X" ➔ Buyer doesn't have App X installed ➔ Drop-off (Sale Lost: 100%)
Case B (Open Interoperable Flow):
Buyer clicks Pay via UPI ➔ Native Sheet Opens:
[ PhonePe ] [ Google Pay ] [ Paytm ] [ CRED ] [ BHIM ]
Buyer selects preferred daily app ➔ 1-Tap PIN Authentication ➔ Payment Success (98.4% Completion)Studies across Indian e-commerce reveal that over 64% of smartphone users maintain at least two different UPI applications, often balancing personal daily spending in one app and larger purchases or credit lines in another. Limiting their choice artificially suppresses your sales.
The Technical Anatomy of a Compliant UPI Intent Link
A compliant, universal UPI intent string is formatted without proprietary prefixes:
upi://pay?pa=merchantvpa@bank&pn=StoreName&tr=ORD10492&am=1499.00&cu=INR&mc=5411If you wish to provide explicit app launch shortcuts (for mobile web checkout speed), compliant implementations offer parallel, unblocked buttons using our free UPI Intent Link Generator:
- Universal:
upi://pay?... - PhonePe:
phonepe://pay?... - Google Pay:
tez://upi/pay?... - Paytm:
paytmmp://pay?... - CRED:
cred://upi/pay?...
If the customer’s selected app is unavailable, the system should gracefully fall back to the universal intent or display the dynamic QR code on screen.
Delivering Frictionless Omnichannel Checkout
With VyaparGateway, true interoperability is built into the core API:
- Every order creation request returns both a dynamic QR payload (scannable by 100% of UPI apps) and app-agnostic intent links.
- No exclusive brand lock-in or forced wallet accounts.
- Direct-to-bank settlement with 0% transaction fees.
Test generating your own custom deep links instantly with our UPI Intent Generator Tool.
Direct answers
Frequently asked questions
- What is the NPCI Pay by Any UPI App mandate?
- The Pay by Any UPI App mandate is an official interoperability directive issued by the NPCI requiring all payment gateways, merchants, and acquiring switches to support open QR and intent resolution across all certified Third Party Application Providers (TPAPs) including Google Pay, PhonePe, Paytm, CRED, Navi, and BHIM.
- Can a payment gateway legally restrict payments to only one specific UPI app?
- No. The NPCI strictly forbids anti-competitive or closed-loop app gating that forces consumers to install or use a single preferred UPI application to complete a commercial transaction.
- How does open UPI interoperability improve merchant conversion?
- Offering universal app intent and dynamic QR codes eliminates checkout friction for users who keep their funds in different UPI-linked bank accounts, increasing transaction success rates by 18% to 25%.
Build your payment flow
Explore the API and browser-only merchant tools.
Create UPI checkout orders, verify signed events, or test the free calculators and generators without exposing credentials.