Yes, if you offer subscriptions / recurring payments to your customers. All subscriptions / recurring payments on Axepta Online started in 3DSV1 are concerned by this modification, whether the merchant keeps his 3DSV1 implementation or modifies his implementation to be compliant with 3DSV2. |
A change in the current regulations requires that transactions relating to subscriptions / recurring payments are chained to an chaining initilization transaction (cf. diagram). It's called chained transactions.
This section explains how to chained transaction for subscriptions on Axepta Online started in 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:
Chained transaction is also required for subscriptions on Axepta Online initiated in 3DSV1, cf. section Recurring payment / One click |
Chained transactions initiated in 3DSV1
You offer your customers payment by card
Customers made their subscriptions before the regulatory change
You store the pseudo card number
Chained transaction for subscriptions on Axepta Online started in 3DSV1 before 01/01/2022.
The creation of a new installement of a subscription / recurring payment can be initiated by the merchant with :
Server-to-server - direct.aspx
Batch - Batch integration
The following table describes the additional encrypted parameter to add in the payment 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 |
|
The creation of a new installement of a subscription / recurring payment can be initiated by the merchant with :
Server-to-server - direct.aspx
Batch - Batch integration
The following table describes the additional encrypted parameter to add in the payment request :
Parameter | Format | CND | Description | |
---|---|---|---|---|
ans..64 | M | Data used to chaine recurring transactions to the 1st transaction of the subscription
|
The parameter schemeReferenceID can be populated in the response of a chained transaction, but this value should not be used.
Only the value received in the response of the chaining initialization transaction has to be stored and used in the next intsallments of the subscription / recurring payments.