Integration



80%

Dynamic QR Checkout


In Dynamic QR checkout merchant needs to post the initial order request to hosted QR checkout page where customer will get the dynamic QR details. Customer need to Capture the QR code in his/her wallet and make the payment. Once the payment is verified, customer is redirected back to merchantRedirectUrl along with the payment status.


The initial request must contain all the required information:

  • - authentication credentials
  • - mode, brand , type and amount of transaction
  • - merchantTransactionId
  • - merchantRedirectUrl

Dynamic QR checkout request has to be sent to our endpoint i.e. /transaction/Checkout using POST method.


In our QR Checkout Specifications you can find a full list of parameters that can be sent in the initial request.

Workflow


1. Post an Initial Order

Merchant needs to post the initial request to hosted QR checkout page.

2. Verify the Details

Customer wallet will provide payment details to the Verification API.

3. Confirm the transaction status

After verification, customer wallet will have to confirm the status using Confirm Status API .

1. Post an Initial Order

To start the process, merchant has to post initial payment request. Here merchantRedirectUrl has to be url-encoded.

Sample Request

2. Verify the Details

The wallet owner has to send the order details to the Verify API which will validate and return merchantWalletId .

3. Confirm the transaction status

Once the the details are verified and the payment has been processed, the customer wallet will have to call the API to Confirm the Status and will be redirected to the Confirmation page .

Sample code for reading the response

Hashing Rule For Request

supports MD5 Cryptographic Hash for the authenticity of payment request sent to the server.


Below are the description of fields used for generating checksum.
  • memberId <Merchant ID as shared by >
  • totype <Name of PSP>
  • amount <Amount of transaction>
  • merchantTransactionId <Unique transaction ID provided by merchant>
  • merchantRedirectUrl <Customer is redirected to this url >
  • secureKey <Secure Key that can be generated through 's dashboard>

How to generate Checksum for request ?

Checksum can be calculated with the following combination and needs to be send along with the authentication parameters in each server-to-server request:
<memberId>|<toType>|<amount>|<merchantTransactionId>|<merchantRedirectUrl>|<secureKey>

Sample Code

Hashing Rule For Response

supports MD5 Cryptographic Hash for the authenticity of payment response to be sent to the merchant.


Below are the description of fields used for generating checksum.
  • PaymentId <Payment ID of the transaction>
  • merchantTransactionId <Unique transaction ID provided by merchant>
  • amount <Amount of transaction>
  • status <Status of the transaction>
  • secureKey <Secure Key that can be generated through 's dashboard>

How to generate Checksum for response ?

Checksum can be calculated with the following combination and needs to be send along with the authentication parameters in each server-to-server request:
<PaymentId>|<merchantTransactionId>|<amount>|<status>|<secureKey>