NPCI COMPLIANCE Rapido® InfraTel LLP · UPI Native Intent Engineering
📞 +91-9327000022 ⚡ 100% Free Utility

NPCI UPI Native Intent Protocol & Integration

How Rapido®Pay leverages standard mobile OS custom URI schemes (upi://pay) to deliver seamless, non-custodial checkout transitions across your installed UPI payment applications.

1. Understanding UPI Intent vs. TPAP Integration

Dimension UPI Native Intent (Rapido®Pay Model) Full TPAP Integration (e.g. Third-Party Aggregator Model)
Licensing & Registration Open standard protocol. No standalone RBI or NPCI license required. Mandatory NPCI TPAP registration + Tripartite Bank Agreement + CERT-In audits.
Custodial Liability Zero custodial liability. Funds never touch Rapido®Pay systems. Direct operational liability for customer payment transactions.
Authentication Carried out inside the user's authentic banking application via NPCI common library. Integrated within the app using embedded NPCI SDKs.
VPA Issuance Does not issue VPAs. Routes to existing payee addresses. Issues proprietary handles (e.g., @ybl, @okhdfcbank).

2. Standard NPCI URI Schema Parameters

Rapido®Pay parses and reconstructs standard NPCI compliant URIs following this specification:

upi://pay?pa=merchant@ybl&pn=MerchantName&mc=5411&tr=TXN123456&am=250.00&cu=INR&tn=InvoiceDescription
Parameter Description Requirement
pa Payee Virtual Payment Address (VPA) / UPI ID. Mandatory
pn Payee Business or Individual Name. Mandatory
mc Merchant Category Code (4 digits standard ISO 18245). Optional (Mandatory for verified merchants)
tr Transaction Reference ID for settlement reconciliation. Mandatory for commercial merchants
am Transaction amount in decimal format (e.g., 250.00). Optional for dynamic QR; Mandatory for static checkout
cu Currency Code. Standard is INR. Mandatory
tn Transaction Note / Narrative displayed on bank statements. Optional

3. Mobile OS Intent Visibility Configuration

In accordance with Android 11+ (API level 30+) package visibility requirements and iOS Custom URL Scheme restrictions, the host mobile application declares explicit query intents:

  • Android: Requires <queries> declaration in AndroidManifest.xml targeting <intent><action android:name="android.intent.action.VIEW" /><data android:scheme="upi" /></intent>.
  • iOS: Requires LSApplicationQueriesSchemes configuration in Info.plist for major UPI provider schemes (e.g., upi, standard installed banking schemes).

Verified Clean Architecture

Rapido®Pay uses modern Flutter packages (upi_intent v1.0.1) and zero-cost Firebase caching for optimal reliability across all devices.

Try Simulator