Creating a token upon the creation of a subscription with payment
In this use case, the following information must be visible:
- the buyer details,
- the transaction identifier,
- the recurring payment details (amounts).
Example: a recurring payment of X EUR/ over N months with commission fees to be paid upon taking the order.
Simplified diagram
On the day of the order:
- The merchant site submits a request to create an alias and subscribe to a recurring payment with immediate payment.
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.
- 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 amount of the first installment.
- 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 response contains:
- the payment result,
- the recurring payment details,
- the unique transaction identifier generated by the issuer, for information purposes,
- the newly created token.
The alias (token) and subscription will not be created if the authorization request is refused.The gateway displays the ticket 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 recurring payment amounts,
- the newly created token.
- the payment receipt,
- the banking details registration confirmation on the payment gateway of the shop,
- the confirmation of the recurring payment registration.
- the buyer's token that they can later use for another financial operation.
The buyer will be debited with the payment amount on the day of the order (or the day after, depending on the buyer).
The first installment of the subscription will be debited once the effective date is reached, between 00:00 and 05:00.
If the effective date is scheduled on the day of the order, the buyer will be debited 2 days in a row (on D for the payment and on D+1 for the first installment).
If you want the payment made on the day of the order to correspond to the first installment of the recurring payment, you must change the effective date. For example, for a monthly subscription, set the effective date to D+30 when requesting the creation of a recurring payment.
Upon each installment:
- The payment gateway performs an authorization request for the installment amount, providing the initial transaction identifier (ITC) as a chaining reference.
- The issuer recognizes the transaction as a MIT that is part of a series of payments for which the cardholder has previously authenticated themselves and proceeds with the authorization request.
The transaction will not be rejected for lack of authentication (soft decline).
- If the merchant has enabled the notification rule Instant Payment Notification URL when creating recurring payments, the payment gateway notifies the merchant site of the payment result.
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.
