Note

From 01/10/2022 all authenticated transactions must use 3DSV2In October 2022, all transactions will only be auhtenticated with 3DSV2. 3DSV1 authentication won't be available anymore.

This section is a synthesis of the developments required in order to use 3DSV2 instead of 3DSV1.gathering information for merchants upgrading from 3DSV1 to 3DS2

For Axepta, this it means using : Add the parameter 'msgVer=2.0' for one-shot payments.Other payment use-cases are described in the section Payment Features

Tip

title	Are you concerned ?

To verify the version of the 3-D Secure protocol used by your online store, please refer to Identify your 3D Secure version.

Table of Contents

Introduction

3D Secure authentication protects the merchant against "cardeholder challenge".

3D Secure authentication V2 Version 2 provides a mechanism for strong authentication in accordance with PSD2.

The major difference with 3DS 1.0 is the possibilty to offer 3DS V2 allows frictionless payments to cardholders, in this case the issuing bank (bank of the cardholder) can approve a transaction without explicit action done by the cardholder (passive authentication).

3DS V1 authentication will remain possible until October 2022. After that date, all 3DS authentications must use version 2 (3DSV2).

info

By default, payment requests are sent with “nopreference”, the merchant does not specify a preference for the authentication mode (SCA or passive authentication).

More details :

Global overview : 3DSV2 and frictionless
Implementation :

Increase

Exemption & 'Frictionless' payments
Liability shift : Liability shift and 3DS Matrix

Table of Contents

Scope

CB (Carte Bancaire), Visa, Mastercard and AMEX transactions.

Upgrade to 3DSV2 - With CMS

Find all the information in the section: Get your 3DSecure 2.0 plugin for free

Upgrade to 3DSV2 - Direct Integration

Synthesis

Concepts

3DSV2 upgrade requires to manage :

New parameters in the request and responses
- Parameter 'msgVer=2.0'
- Optionnal Fields (NVP values) and JSON objects – for dedicated use-cases
- Additionnal authentication data

GET & POST responses for URLSuccess / URL Failure / URL Notify

New 3DS Response Codes

3DS2 implementation will also allow the merchant to request strong authentication or frictionless payment.

By default, payment requests are sent under “nopreference”, the merchant does not specify a preference for the authentication mode (SCA or passive authentication).

Tip

Si vous proposer du paiement

For one-shot

, l'évolution vers le 3DSV2 consiste à :Ajouter le paramètre

payments, upgrading to 3DSV2 means :

Add parameter "msgVer=2.0"

dans vos requêtes de paiement

Gérer les réponses envoyées en POST.

in the payment request
Manage POST responses

Detailed overview

3DSV2 key parameters

Key parameters are used according to the use-cases (one-shot, one-click, recurring...) :

Parameter

Type

Details

Request

Response

msgVer

Parameter

3DSV2 payment request

X

threeDSPolicy

JSON Object

Manage the authentication request (mandate, challenge...)

X

browserInfo

JSON Object

Need for paynow.aspx (one-click)

X

credentialOnFile

JSON Object

Needed if a merchant wants to reuse a card (one-click, recurring...)

X

billToCustomer

JSON Object

Customer billed for his purchases

X

shipToCustomer

JSON Object

Customer who received the goods

X

billingAddress

JSON Object

Billing address

X

shippingAddress

JSON Object

Shipping address

X

Card

JSON Object

Card object with the PCNr, card brand, expiry date...

X

schemeReferenceId

Parameter

Chaining data used for subscription transactions / recurring payments

X

resultsResponse

JSON Object

authentication additionnal data

X

threeDSData

JSON Object

Authentication data

X

Synthesis : Upgrade to 3DSV2

Use-case

3DSV1

3DSV2

Examples : JSON objects to add in ECOM payments

One-Shot payment

-

Add "MsgVer=2.0” - Create a payment request (CIT)

Info

D'autres données peuvent être indiquées dans la requête de paiement pour favoriser les paiements 'frictionless'.

Pour plus de détails

Additional data can be added to the request in order to increase frictionless payments.

More details :

Présentation générale : 3DSV2 et frictionless

Implémentation : Favoriser les paiements 'Frictionless'

Response format

Card payment

GET for URLFailure / URLSuccess / URLNotify

POST for URLFailure / URLSuccess / URLNotify

GET for URLFailure / URLSuccess / URLNotify if 3DSV1 fallback

Response format

Alternative payment methods

GET for URLFailure / URLSuccess / URLNotify

Card data

PCNr

CCExpiry

CCCVC

CCBrand

JSON Object Card

Or JSON Object Card + PCNR / CCExpiry / CCBrand if 3DSV1 fallback

Use-cases

One-click

Initial payment

/

Use "MsgVer=2.0”, JSON objects credentialOnFile and threeDSPolicy

One-click payment

JSON Object credentialOnFile

Code Block

theme	Eclipse
linenumbers	true

{
    "type": {
        "unscheduled": "CIT"
    },
    "initialPayment": true,
  	"useCase": "cof"   
}

JSON Object threeDSPolicy

Code Block

theme	Eclipse
linenumbers	true

{
	"challengePreference": "mandateChallenge"
}

One-click

One-click payments

PCNr

CCExpiry

CCCVC

CCBrand

Use "MsgVer=2.0”, JSON objects credentialOnFile and threeDSPolicy

One-click payment

JSON Object credentialOnFile

Code Block

theme	Eclipse
linenumbers	true

{
    "type": {
        "unscheduled": "CIT"
    },
    "initialPayment": false,
  	"useCase": "ucof"   
}

Subscription with fixed amount and frequency

Initial payment

Parameter "RTF=I"

Cards

Card data : PCNr, CCExpiry, CCBrand…

Server-to-Server

Use "MsgVer=2.0”, JSON objects credentialOnFile and threeDSPolicy

JSON Object Card and the parameter schemeReferenceID are sent in the response.

Tip

The object Card available in the response should be decrypted and stored.

The object card used in the next request requires less parameters than the card object in the reponse.

Batch

Batch implementation remains the same

More details

Managing subscriptions (recurring payments

JSON object credentialOnFile

Code Block

theme	Eclipse
linenumbers	true

{
    "type": {
        "recurring": {
            "recurringFrequency": 30,
            "recurringStartDate": "2019-09-14",
            "recurringExpiryDate": "2020-09-14"
        }
    },
    "initialPayment": true,
    "useCase": "fixed" 
}

JSON object threeDSPolicy

Code Block

theme	Eclipse
linenumbers	true

{
	"challengePreference": "mandateChallenge"
}

Abonnement à durée et montant fixes

Échéances suivantes

Subscription with fixed amount and frequency

Subscription payment

Parameter

Utilisation du paramètre

"RTF=R"

Infos carte

Card data : PCNr, CCExpiry, CCBrand…

Server-to-Server

Utiliser

Use "MsgVer=2.0”,

l’objet

JSON objects credentialOnFile,

l'objet JSON Card et le schemeReferenceID.

Batch

L'implémentation Batch reste inchangée

Pour plus de détails

Paiement récurrent carte (Abonnement)

Paiement récurrent carte (Abonnement

Card et the parameter schemeReferenceID.

JSON Object Card and the schemeReferenceID are sent in the response.

Tip

The object Card available in the response should be decrypted and stored.

The object card used in the next request requires less parameters than the card object in the reponse.

Batch

Batch implementation remains the same

More details

Créer des paiements par fichier (Batch

Create Batch payments (File)

Objet

JSON Object credentialOnFile

Code Block

theme	Eclipse
linenumbers	true

{
    "type": {
        "recurring": {
            "recurringFrequency": 30,
            "recurringStartDate": "2019-09-14",
            "recurringExpiryDate": "2020-09-14"
        }
    },
    "initialPayment": false,
    "useCase": "fixed" 
}

Abonnement à durée et montant variables

Paiement initial

Subscription with variable amount and frequency

Initial payment

Parameter

Utilisation du paramètre

"RTF=E"

Infos carte

Card data : PCNr, CCExpiry, CCBrand…

Server-to-Server

Utiliser

Use "MsgVer=2.0”,

l’objet

JSON objects credentialOnFile

et

and threeDSPolicy

L’objet JSON Card et le schemeReferenceID sont envoyés dans la réponse

Batch

L'implémentation Batch reste inchangée

Pour plus de détails

Paiement récurrent carte (Abonnement)

Paiement récurrent carte (Abonnement

JSON Object Card and the parameter schemeReferenceID are sent in the response.

Tip

The object Card available in the response should be decrypted and stored.

The object card used in the next request requires less parameters than the card object in the reponse.

Batch

Batch implementation remains the same

More details

Créer des paiements par fichier (Batch

Create Batch payments (File)

Objet

JSON Object credentialOnFile

Code Block

theme	Eclipse
linenumbers	true

{
    "type": {
        "unscheduled": "CIT"
    },
    "initialPayment": true,
  	"useCase": "ucof"   
}

Objet JSON

JSON Object threeDSPolicy

Code Block

theme	Eclipse
linenumbers	true

{
	"challengePreference": "mandateChallenge"
}

Abonnement à durée et montant variables

Échéances suivantes

Subscription with variable amount and frequency

Subsequent payments

Parameter

Utilisation du paramètre

"RTF=M"

Infos carte

Card data : PCNr, CCExpiry, CCBrand…

Server-to-Server

Utiliser

Use "MsgVer=2.0”,

l’objet

JSON objects credentialOnFile,

l'objet JSON Card et le schemeReferenceID.

Batch

L'implémentation Batch reste inchangée

Pour plus de détails

Paiement récurrent carte (Abonnement)

Paiement récurrent carte (Abonnement

Card et the parameter schemeReferenceID.

JSON Object Card and the schemeReferenceID are sent in the response.

Tip

The object Card available in the response should be decrypted and stored.

The object card used in the next request requires less parameters than the card object in the reponse.

Batch

Batch implementation remains the same

More details

Créer des paiements par fichier (Batch

Create Batch payments (File)

Objet

JSON Object credentialOnFile

Code Block

theme	Eclipse
linenumbers	true

{
    "type": {
        "unscheduled": "MIT"
    },
    "initialPayment": false,
  	"useCase": "ucof"   
}

Tip
Les fonctionnalités de paiement sont détaillés dans la section : Fonctionnalités de paiement

CMS et 3DSV2

Payment features are detailed in the section Payment Features

Test your 3DSV2 integration

To test your 3DSV2 integration, you can use our 3DSV2 Test environment

3DSV2 key parameters

Key parameters are used according to the use-cases (one-shot, one-click, recurring...) :

Parameter	Type	Details	Request	Response
msgVer	Parameter	3DSV2 payment request	X
threeDSPolicy	JSON Object	Manage the authentication request (mandate, challenge...)	X
browserInfo	JSON Object	Need for paynow.aspx (one-click)	X
credentialOnFile	JSON Object	Needed if a merchant wants to reuse a card (one-click, recurring...)	X
billToCustomer	JSON Object	Customer billed for his purchases	X
shipToCustomer	JSON Object	Customer who received the goods	X
billingAddress	JSON Object	Billing address	X
shippingAddress	JSON Object	Shipping address	X
Card	JSON Object	Card object with the PCNr, card brand, expiry date...	X	X
schemeReferenceId	Parameter	Chaining data used for subscription transactions / recurring payments	X	X
resultsResponse	JSON Object	authentication additionnal data		X
threeDSData	JSON Object	Authentication data		X

A VOIR AVEC DAMIEN

Page tree

Versions Compared

Old Version 1

New Version Current

Key

Introduction

Scope

Upgrade to 3DSV2 - With CMS

Upgrade to 3DSV2 - Direct Integration

Synthesis

Detailed overview

3DSV2 key parameters

Synthesis : Upgrade to 3DSV2

CMS et 3DSV2

Test your 3DSV2 integration

3DSV2 key parameters

Help

Intranet Tools

Page tree

Page History

Versions Compared

Old Version 1

New Version Current

Key

Introduction

Scope

Upgrade to 3DSV2 - With CMS

Upgrade to 3DSV2 - Direct Integration

Synthesis

Detailed overview

3DSV2 key parameters

Synthesis : Upgrade to 3DSV2

CMS et 3DSV2

Test your 3DSV2 integration

3DSV2 key parameters