| Note | ||
|---|---|---|
| ||
All subscriptions / recurring payments started in 3DSV1 are concerned by this modification, whether the merchant keeps his 3DSV1 implementation or modifies his implementation to be compliant with 3DSV2. |
Description
A change in the current regulations requires that transactions relating to a subscription subscriptions / recurring payments are chained to an existing transactionchaining initilization transaction (cf. diagram). It's called chained transactions.
This section explains how to chained transaction for the subscriptions already started in progress on 3DSV1 before 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: Januaryfor example in january): Send The merchant sends a payment request with a chaining value defined by the customer’s card brand (CB, VISA, MCcf. implementation section of the current page) and store stores the chaining value received in the answer
- Send chained transactions (ex: February, Marchfor example in february, march...): Send The merchant sends a payment request with the chaining value received in response of the chaining initialization
| Info | ||
|---|---|---|
| ||
Chained transaction is also required for subscriptions started from 01/01/2022. |
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)initialization
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 |
|---|---|---|---|
RTF | a1 | O | In this case --> R = Routine payment (Recurring) |
| 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 | ||
|---|---|---|---|---|---|
RTF | a1 | O | In this case --> R = Routine payment (Recurring) | ||
| ans..64 | M | Data used to chaine recurring transactions to the 1st transaction of the subscription
|
Response
Issuers can send new schemeReferenceID, however it's not necessay to store these values because they won't be used.