Real-time NPCI Link Compiler

Payment Parameters

Configure recipient VPA, transaction amount, reference IDs, and QR styling.

pa
@
Popular:
pn
Displayed at the top of payer's approval screen.
am
₹
cu
tr
tn
QR Appearance & Standee Themes
Advanced Protocol Parameters (MCC, Mode, Sign, MAM)
mc
mam
mode
url
sign
Physical Counter Standee
Vector Scaled • Ready to Scan
UPI
Google Pay PhonePe Paytm

Acme Store

merchant@okaxis

UPI
Standardized URI Protocol
Direct Handshake with PSP Apps
Compiled UPI Deep Link
upi://pay?pa=...

Active Protocol Parameters

Key NPCI Name Resolved Value
Zero-Fee Payment Button
Self-Contained HTML/CSS
Live Render Preview
Copy-Paste HTML & Inline CSS
<!-- Loading button... -->
Desktop Modal + Mobile Universal Script
<!-- Script loading... -->

NPCI Unified Payments Interface Protocol Anatomy

How QR codes and Intent URIs decode across PSP apps.

URI Structure

Every UPI checkout begins with the custom scheme upi://pay followed by query parameters. Mobile operating systems (Android Intent Filters & iOS Universal Links) parse this scheme and pass the dictionary of key-value pairs to verified payment apps (GPay, PhonePe, Paytm, BHIM).

Desktop vs Mobile Handshake

Because desktop browsers lack native UPI hardware token storage, attempting to launch upi:// directly will trigger an unhandled protocol error. The recommended merchant pattern is displaying the dynamic QR standee for smartphone camera scans.

Copied to clipboard!