Button Checkout
Checkout Form is the primary way to integrate with your front end and accept payments online. It provides you with a well designed and tested checkout form for your end customers. This form handles credit/debit card details or netbanking details or wallets.
In a button checkout merchant needs to post the intial request to hosted checkout page where customer will provide card/account details.
Once the payment is verified customer is redirected back to the customer's website 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
Standard checkout request has to be sent to our endpoint i.e. /transaction/Checkout using POST method.
In our API Specifications you can find a full list of parameters that can be sent in the initial request.
Workflow
1. Click on Checkout Button
Merchant needs to post the intial request to hosted checkout page.
2. Checkout form
Customer will provide his/her card/account details on hosted checkout page.
3. Return to Merchant's Website
After payment confirmation, customer will be redirected to merchant's website.
1. Click on Checkout Button
To start the process, merchant has to POST request to our endpoint i.e. /transaction/Checkout .
In button checkout, the handler function specified will be called automatically at the end of the checkout process with an object consisting of response .
A Javascript file needs to be added with the request code (as shown in sameple request).
Sample Request
2. Checkout form
The account holder will be redirected to hosted page, where the account holder can fill the card/account details.
3. Return to Merchant's Website
Once the payment has been processed, the customer will return to Merchant's Website with the response in the handler function of the object passed in the request.
You can also check the payment confirmation with our Backoffice Inquiry API.
Hashing Rule
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>
Payment Modes and Brands
Find below the list of payment modes and brands for standard checkout.
| Mode | Brand |
|---|