Description
A change in the current regulations requires that transactions relating to a subscription are chained to an existing transaction. It's called chained transactions.
This section explains how to chained transaction for the subscriptions already in progress on 01/01/2022.
Setting up the chained transactions requires the management of an additional parameter in the payment request, the schemeReferenceID, which will be populated with the chaining value.
Updating subscriptions goes through 2 steps:
- Initiate the chaining (ex: January): Send a payment request with a chaining value defined by the customer’s card brand (CB, VISA, MC) and store the chaining value received in the answer
- Send chained transactions (ex: February, March...): Send a payment request with the chaining value received in response of the chaining initialization
Nouveaux abonnements
Chained transaction is also required for subscriptions started from 01/01/2022.
To set up new subscriptions, you can refer to the section Managing subscriptions (recurring payments)
Diagram
Prerequisites
You offer your customers payment by card
Customers made their subscriptions before the regulatory change
You store the pseudo card number
- You will store the schemeReferenceID received in the response of the chaining initialization
Available for implementations with or without the 'msgVer=2.0' parameter (3DSV2)
Implementation
Chaining initialization
The payment can be initiated by the merchant through :
Server-to-server - direct.aspx
Batch - Batch integration
Request
The following table describes the additional encrypted payment request parameters that needs to be added to the request :
| Parameter | Format | CND | Description |
|---|---|---|---|
| ans..64 | M | Chaining data for card subscriptions transactions To initialize the chaining, it is necessary to use the values defined by CB, Visa and Mastercard CB : 9999999999999 - 13 digits VISA: 887001863998888 - 15 digits MasterCard: 1231_MCC999999 - 13 digits |
Response :
- A new schemeReferenceID will be sent in the transaction response
- This value has to be stored and will be used in all subsequent transactions of this subscription
Creation of chained transactions
The payment can be initiated by the merchant through :
Server-to-server - direct.aspx
Batch - Batch integration
Request
The following table describes the additional encrypted payment request parameters that needs to be added to the request :
| Parameter | Format | CND | Description |
|---|---|---|---|
| ans..64 | M | Chaining data for card subscriptions transactions Send the value retrieved from the response of the chaining initialization transaction |