Description

A change in the current regulations now requires that transactions relating to a subscription be linked to an existing transaction. We will then talk about the chaining of transactions.

This section discusses the implementation of the link on subscriptions already in progress on 01/01/2022.

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

Updating subscriptions goes through 2 steps:

1. Initiation of the chain (ex: January): Sending a payment request containing a chain value defined by the customer’s card brand (CB, VISA, MC) and retrieve of the chain value to be store
2. Sending chained transactions (ex: February, March...): Sending a payment request containing the chain value received in response to the chain initialization transaction

Schéma

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

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

Implementation

Chain initiation

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 :

Response :

• A new schemeReferenceID will be present in the transaction response
• This value must 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 :