Creating a token without payment
This case corresponds to a simple token creation.
- The merchant site submits a alias creation request.
Note for stores with the "Currency Conversion" option:
The currency is mandatory when creating an alias.
Only contracts that support the currency passed in parameter will be selected. Currency conversion is therefore not taken into account.
E.g.: For an alias creation request in USD currency, on a shop associated with an AMEX contract and a CB contract:
if the AMEX contract only supports USD and the CB contract only supports EUR, then only AMEX cards will be accepted for the alias creation.
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 this use case.
Authentication is performed for an amount of EUR 0.
- 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:
This operation results in the creation of a VERIFICATION type transaction, visible in the Expert Back Office and possessing the following characteristics:
- the unique transaction identifier generated by the issuer, for information purposes,
- the newly created token.
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:
- 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 newly created 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.
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 this use case, the way the chaining reference is handled is transparent to the merchant.