• France
status page
demonstrations
assistance
FAQContact support
Search
Categories
Tags
English
French
English
Homepage
Use cases
Create a payment
Create an installment payment
Create a multi-card (split) payment
Create a payment by Alias (Token)
Create a payment link
Create a recurring payment
Manage subscriptions
Manage your transactions (refund, cancel...)
Analyze your reports
API docs
Embedded Form
REST API
Hosted payment
Mobile payment
File exchange
Snippets
Payment methods
Plugins
Guides
Merchant Back Office
Functional guides

Creating a token during a payment

In this case, the parameters necessary for registration are completed by the parameters required for a payment request.

Simplified diagram

  1. The merchant site submits a payment request with alias creation.

     

    Note for stores with the "Currency Conversion" option

    As soon as a payment is made at the time of the order, the currency conversion is authorized.

    Currency conversion is therefore supported for this operation, unlike the creation of an alias with or without subscription.

    The buyer selects the payment method to be registered, enters their payment method details and confirms the entry.

  2. The payment gateway initiates the cardholder’s authentication process with the issuer.
     Regulations require strong authentication for this use case.

    Authentication is performed for the payment amount.

  3. Once the authentication is completed, the gateway proceeds with the authorization request by providing the cardholder’s authentication details.
  4. The issuer generates a unique transaction identifier and transmits it in the response to the authorization request.
  5. The payment gateway notifies the merchant website about the result.
    The response contains:
    • the payment result,
    • 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:
    • the payment result,
    • the newly created token.
    If you have configured the corresponding notification rules, the buyer will receive an e-mail with:
    • 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.
 The issuer transaction identifier is stored by the payment gateway at the level of the alias and the transaction.

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.

© 2024 {'|'} All rights reserved to Sogecommerce
2.91.0-doc-1.11