Merchant payment data
The merchant prepares relevant payment data such as order reference and amount.
QR generation boundary
UPI Gateway Pro provides the highlighted QR generation layer. Customer payment, payment confirmation, fund movement, and settlement continue through external UPI, payment, banking, and merchant infrastructure.
Start with Dynamic UPI QR generation, then connect the flow through the integration guide. For payment-system context, read is UPI a payment gateway? and UPI intent vs Dynamic QR.
The merchant prepares relevant payment data such as order reference and amount.
The merchant system requests a Dynamic UPI QR instance.
A payment-specific QR is generated from supplied parameters.
The customer scans and continues in a compatible UPI app.
Payment activity occurs through UPI and financial infrastructure.
The merchant handles order status through connected payment and internal systems.
A static QR is reusable and usually represents a fixed payment identifier. A Dynamic QR is created for a particular payment request or order context.
Yes, Dynamic UPI QR codes can be displayed on websites, order pages, checkout pages, invoice pages, or merchant-assisted screens as part of a broader payment flow.
No. Payment processing, fund movement, payment confirmation, and settlement occur through the relevant UPI, payment, banking, and merchant infrastructure.
A merchant flow may use order reference, amount, payee context, and payment notes where supported by the relevant UPI payment flow.
The merchant prepares payment data, requests QR generation, displays the Dynamic QR, and then continues payment handling through its connected UPI and financial infrastructure.