On behalf duplication

Introduction

The aim of this document is to present the integration of the use of scheme tokens in the payment process for duplicate transaction.

Who does this document target?

This document is intended for merchants and their technical teams who wish to utilize scheme tokens in their MIT (Merchant Initiated Transaction) of Duplication type

To have an overview of Worldline Sips solution, we recommend that you consult the following documents :

Functional schema

This diagram describes the technical relationships between the merchant, Worldline Sips and TSPs (Token Service Provider).

Schema describing relationships between the merchant, Worldline and various TSP

Registration with TSP

Registration with the TSP is done through Worldline Sips. However, it is preferable to inform your acquirer in advance.

List of items to provide :

Trade name of the webshop ;
Webshop identification number :
- VISA et Mastercard : VAT identification number ;
- CB : Token Requestor ID (Initial temporary operation) ;

Note: Initial CB process specifics : You must contact your acquirer to request registration with the CB TSP. Once this registration is completed, the CB GIE will send the merchant (via their acquirer) an identifier (Token Requestor ID) that must be communicated to Worldline Sips.

Use case

Here are the use cases of the scheme token on Worldline Sips applied on duplicated transactions (COF MIT).

Note: The on behalf duplication mode does not allow for scheme tokens lifecycle management, unlike the on behalf merchant token mode.

Scheme tokenization during a duplicable CIT

Here is the use case for the Worldline Sips scheme token applied to the duplication of newly created COF (Card On File) MIT transactions following the activation of the "scheme token on behalf" option. Scheme tokenization does not apply if the transaction is made via Sips Paypage.

Scheme tokenization applies on the PAN from a transaction under the following conditions :

Authenticated (3DS)
Authorized
Dont le paymentpattern is valued to "RECURRING_1".

Image of the diagram showing the chaining kinematics

Scheme tokenization during a MIT (ongoing recurrence)

This use case concerns duplications (e.g., subscriptions) that are ongoing at the time of the activation of the "scheme token on behalf" option

Scheme tokenization applies on the PAN from a transaction under the following conditions :

Authorized
Dont le paymentpattern is valued to "RECURRING_N".

Merchant fallback

This use case concerns merchants who wish to revert the use of the scheme token and perform duplications using the PAN.

To do this, it is necessary to :

Disable the "scheme token on behalf" option in the merchant's configuration by making a request to your account manager.
Start from the reference of the initial CIT transaction in order to submit duplications using the PAN.

Note: If the "scheme token on behalf" option is disabled, the duplication of a transaction performed with a scheme token is rejected (responseCode =40)

WL SIPS DOCS