3DS Payment Lifecycle
How 3D Secure authentication works, when a challenge is triggered, and how to resume the flow after it.
The 3DS payment flow ensures an additional layer of security for online transactions. This page explains the 3DS payment flow in Tonder, detailing each step in the process so you understand how transactions are securely processed within the Tonder payment system.
See card payments for how 3D Secure applies within the card flow.
The 3DS payment flow
The steps below break down the 3DS flow to better demonstrate how it works.
The process starts by setting up the environment. Initialize Tonder's SDK, adding the necessary data:
returnUrl: the URL to which the user is redirected after the checkout process, regardless of success or failure.apiKey: the API key used for authentication and authorization.
Display the payment form to the user. Here the user adds their payment details and starts the payment process.
When the user clicks the payment button, the payment process returns a status defining the next step:
- Pending: the user is automatically redirected to the 3DS authentication page.
- Success: the payment is successfully processed, and the user is notified.
- Failed/Declined: the payment process is halted, and the user is informed of the failure or decline.
The status of the 3DS transaction is validated after the user is redirected back to the return URL. Depending on the response status, appropriate actions are taken:
- Success: the transaction proceeds normally.
- Failed: the user is notified, and necessary steps are taken to handle the failed transaction.