v1

latestOpenAPI 3.1.02026-07-2418201.6 MB

Generate Dynamic QR

This API allows the platform to create a dynamic QR code using Decentro's UPI stack.

post/v3/payments/upi/qr

Headers

client_idstring required

Decentro assigned client_id during on boarding.

client_secretstring required

Decentro assigned client_secret during on boarding.

x_on_behalf_ofstring

This allows parent merchant to consume the API on behalf of sub-merchant.

authorizationstring

Customers can generate JWT using our Auth API with various grant types in the request body. JWT is valid for 15minutes.

Request body

reference_idstring required

A unique ID assigned by clients for every API request.

consumer_urnstring required

A unique identifier assigned to client's by Decentro during On boarding.

amountstring required

The transaction amount (in INR) you intent to collect. Min = 5.00 and MAX = 100000.00. The limits on the amount can be changed depending on merchant use case. Please contact support@decentro.tech for further assistance.

purpose_messagestring required

The narration that you want to show as a message for the transfer. (Note: Purpose message must be less than 50 characters).

generate_custom_qr_imageboolean

true/false depending on the choice to generate custom QR code with client's logo uploaded during on boarding. Default value: false

expiry_timestring required

Time parameter in minutes after which the QR will get expired. Max value = 1440 minutes (1 day)).

redirect_urlstring

The custom URL where the user will be redirected after the payment session. Only "https://" endpoints will be accepted.

account_numberstring

Used for TPV. The number of the source bank account from which the payment must be made. Payments from any other account (mapped to the UPI ID) will be rejected.

account_ifscstring

Used for TPV. The IFSC number of the source bank account from which the payment must be made. Payments from any other account (mapped to the UPI ID) will be rejected.

split_settlement_rule_urnstring

This param will help us to identify the split settlement rule at transaction level.

Response

200

decentro_txn_idstring

api_statusstring

messagestring

response_keystring

Example response

{
  "decentro_txn_id": "01ED978xxxxxxxxxxxx57B322E9717",
  "api_status": "SUCCESS",
  "message": "Payment QR created Successfully.",
  "data": {
    "dynamic_qr_image": "<link containing qr image>",
    "transaction_status": "PENDING"
  },
  "response_key": "success_payment_qr_created"
}