Card Tokenization
This function is used to generate a token for card details which can be used to initiate payments for subsequent requests.
There are various ways to do card tokenization: Generate Token, Charge Card and Generate Token, Card Charge with Token.
How card tokenization works:
The merchant will:
- Generate an OAUTH2 bearer to invoke the APIs.
- Invoke the to create a transaction.
- Generate a token to be used for future transactions or charge the card for the transaction and generate a token for the card.
- Charge customers using the token shared.
- Generate Token
This function will generate a token for the submitted card details.
The token can be stored.
| Function | Description |
|---|---|
| Authenticate Request | This function is used to retrieve an authentication token for all the requests done via the checkout API |
| Checkout Request | This function serves as a trigger to begin the checkout process once the customer has supplied the necessary information about the desired product or service. Its purpose is to enable the customer to proceed with the payment transaction. |
| Generate Token | This function will generate a token for the submitted card details. |
| Query Request Status | The query status is used by the merchant if they want to query for the status of the request they raised |
| Acknowledge Payments | This is when the merchant wants to acknowledge the request with a final status or a delivered status. This is sent as a JSON POST request. |
| Delete Token | Deletes a saved token. If the developer requires to delete it |
- Charge Card and Generate Token
Card details are used for the first time. The card will be charged and a token will be generated and sent back to the merchant. This can be done via 2D or 3DS
| Function | Description |
|---|---|
| Authenticate Request | This function is used to retrieve an authentication token for all the requests done via the checkout API |
| Checkout Request | This function serves as a trigger to begin the checkout process once the customer has supplied the necessary information about the desired product or service. Its purpose is to enable the customer to proceed with the payment transaction. |
| Charge Card and Generate Token | Card details are used for the first time. The card will be charged and a token will be generated and sent back to the merchant. This can be done via 2D or 3DS |
| Query Request Status | The query status is used by the merchant if they want to query for the status of the request they raised |
| Acknowledge Payments | This is when the merchant wants to acknowledge the request with a final status or a delivered status. This is sent as a JSON POST request. |
| Delete Token | Deletes a saved token. If the developer requires to delete it |
- Card Charge with Token
A token is sent instead of card details.
| Function | Description |
|---|---|
| Authenticate Request | This function is used to retrieve an authentication token for all the requests done via the checkout API |
| Checkout Request | This function serves as a trigger to begin the checkout process once the customer has supplied the necessary information about the desired product or service. Its purpose is to enable the customer to proceed with the payment transaction. |
| Charge Card with Token | |
| Query Request Status | The query status is used by the merchant if they want to query for the status of the request they raised |
| Acknowledge Payments | This is when the merchant wants to acknowledge the request with a final status or a delivered status. This is sent as a JSON POST request. |
| Delete Token | Deletes a saved token. If the developer requires to delete it |
Updated 12 months ago