APIs used for Integration
| API | Purpose |
|---|---|
| Dynamic QR Generation API | Generate a dynamic UPI QR for offline payment collection |
| Insta Static QR Generation API | Generate a static UPI or Bharat QR for repeat collections |
| Insta Deactivate VPA API | Permanently deactivate the VPA embedded in an Insta static QR |
| Insta Static QR Regeneration API | Regenerate a previously created Insta static UPI or Bharat QR |
| Integrated Static Bharat QR Generation API | Generate an integrated static UPI or Bharat QR |
| Payment Initiation API – Integrated Bharat QR | Initiate payment towards an integrated static QR |
| Offline Intent Link Generation API | Generate a UPI Intent link for customer payment |
| Expire Intent Link API | Expire one or more UPI Intent links |
| Print Invoice QR API | Generate a printable dynamic UPI QR for invoices |
| Send Invoice QR to SMS API | Send payment confirmation SMS after a transaction |
| Transaction Callback API | Receive transaction status on your webhook after QR payment processing |
| Transaction Status Check API | Check the status of a QR transaction |
| Cancel QR Transaction API | Cancel an initiated QR transaction |
Reference
- To imitate refund for a transaction, refer to Refund Transaction API.
- For error codes, refer to Error codes for QR APIs.
Testing UPI QR
UPI QR test limitations:
- UPI QR transactions require the
DBQRflag to be activated on your merchant account. If you receive an error when posting withpg=DBQRandbankcode=UPIDBQR, contact your KAM to enable this feature.- UPI QR in the test environment may show failures that do not replicate in production. If UPI QR transactions fail consistently in UAT with no clear error, contact [email protected] with your MID and a sample transaction ID for investigation.
- Ensure
txn_s2s_flow=4is included in your QR payment request. Without this flag, the DBQR flow will not initiate correctly.
Updated about 1 hour ago
Did this page help you?