Updating token details
This case corresponds to updating, at the initiative of the buyer, the information related to his or her payment method and/or his or her personal information.
Simplified diagram
- The merchant site submits a alias update request.
The buyer selects the payment method to be registered, enters their payment method details and confirms the entry.
- The payment gateway initiates the cardholder’s authentication process with the issuer.Regulations require strong authentication for each card registration.
Authentication is performed for an amount of EUR0.
- Once the authentication is completed, the gateway proceeds with the registration request by providing the cardholder’s authentication details.
- The issuer generates a unique transaction identifier and transmits it in the response to the registration request.
- The payment gateway notifies the merchant website about the result.The response contains:
- the unique transaction identifier generated by the issuer, for information purposes,
- the updated alias.
This operation results in the creation of a VERIFICATION type transaction, visible in the Expert Back Office and possessing the following characteristics:- its amount is 1.00 EUR or 0 EUR if supported by the acquirer,
- its status is either "Accepted" or "Refused",
- it is never captured and remains in the "Transactions is progress" tab.
The token will not be updated 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:- token,
- the buyer details.
- 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.
The issuer transaction identifier stored at the level of the alias is replaced by the identifier that is generated by the issuer upon the alias update.
Depending on how you use the alias (1-click payment, 0-click payment, recurring payment, etc.) the issuer transaction ID will be used as a chaining reference if necessary.
Similarly to the alias creation, the way the chaining reference is handled is transparent to the merchant.
