Description

A change in the current regulations now requires that transactions relating to a subscription be linked subscriptions / recurring payments are chained to an existing chaining initilization transaction . We will then talk about the chaining of (cf. diagram). It's called chained transactions.

This section discusses the implementation of the link on subscriptions already in progress on explains how to chained transaction for subscriptions on Axepta Online started in 3DSV1 before 01/01/2022.

Setting up this link the chained transactions requires the management of an additional parameter in the payment requestsrequest, the schemeReferenceID, which will contain be populated with the chaining value allowing transactions to be linked.

Updating subscriptions goes through 2 steps:

1. Initiation of Initiate the chain (ex: January): Sending chaining (for example in january): The merchant sends a payment request containing with a chain chaining value defined by the customer’s card brand (CB, VISA, MC) and retrieve of the chain value to be storecf. implementation section of the current page) and stores the chaining value received in the answer
   
2. Send chained transactions (for example in february, marchSending chained transactions (ex: February, March...): Sending The merchant sends a payment request containing with the chain chaining value received in response to the chain initialization transaction of the chaining initialization 

To set up a new subscription, please refer to the following page: Paiement récurrent (Abonnement) / One click

Diagram

Image Added

Chained transactions initiated in 3DSV1

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 schemeReferenceID in response to the chaining initiation transaction

• Available for implementations with or without the 'msgVer=2.0' parameter (3DSV2)

Implementation

• in the response of the chaining initialization
  

Implementation

Objective

Chained transaction for subscriptions on Axepta Online started in 3DSV1 before 01/01/2022.

Example

• January → Initialize chaining with a standard chaining value defined by the customer’s card brand and store the schemeReferenceID received in the reponse (Implementation: cf. Step 1)
• February→ Chained transactions i.e transactions with schemeReferenceID in the request, value retieved in the reponse of the chaining initialization transaction (Implementation : cf. Step 2)
• March and next →Chained transactions i.e transactions with schemeReferenceID in the request, value retieved in the reponse of the chaining initialization transaction (Implementation : cf. Step 2)

Step 1 : Chaining initialization

The creation of a new installement of a subscription / recurring

Chain initiation

The payment can be initiated by the merchant through with :

• Server-to-server - direct.aspx

• Batch - Batch integration

Request

 The The following table describes the additional encrypted payment request parameters that needs to be added to the parameter to add in the payment request :

Response

Step 2 : Creation of chained transactions

The creation of a new installement of a subscription / recurring payment can be initiated by the merchant through with :

• Server-to-server - direct.aspx

• Batch - Batch integration

Request

 The The following table describes the additional encrypted payment request parameters that needs to be added to the parameter to add in the payment request :

Response

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.