Payment with the token creation option for the cardholder
At the moment of payment, the buyer has the possibility to remember the bank details for later by ticking the corresponding checkbox. This completely secure operation facilitates future purchases for the buyer.
- The merchant site submits a payment request.
The buyer selects the payment method to register and enters their payment method details.
The buyer can check a box to give their consent for their payment method to be registered by the payment gateway. By default, this checkbox is unchecked.
- The payment gateway initiates the cardholder’s authentication process with the issuer.If the buyer has checked the box, a payment method alias is created. Strong authentication is required by regulations.
Otherwise, the buyer is subject to authentication with or without interaction.
Regardless of the buyer’s choice, authentication is performed for the payment amount.
- Once the authentication is completed, the gateway proceeds with the authorization request by providing the cardholder’s authentication details.
- The issuer generates a unique transaction identifier and transmits it in the response to the authorization request.
- The payment gateway notifies the merchant website about the result.The token will not be created if the authorization or information request is rejected.The gateway displays the receipt to the buyer. It contains:If you have configured the corresponding notification rules, the buyer will receive an e-mail with:
- the payment result,
- the potentially created token.
- the payment receipt,
- the banking details registration confirmation on the payment gateway of the shop,
- the buyer’s token that they can later use for another financial operation.
Depending on how you use the alias (1-click payment, 0-click payment, recurring payment, etc.) the gateway will use the issuer transaction ID as the default chaining reference if necessary.
In case the merchant duplicates (MIT) the transaction created on the day of the order, the gateway automatically uses this identifier as a chaining reference.
In this use case, the way the chaining reference is handled is transparent to the merchant.