Overview

3D Secure Requestor-initiated Authentication (3RI) is a form of merchant-initiated 3D Secure that provides a merchant with liability-shift benefits when the cardholder is not present. To qualify, the linked customer-initiated transaction must be processed with full SCA 3DS performed. 3RI uses the same rails (technical infrastructure, API endpoints, and messaging protocols) as 3DS Data Only, and a merchant can get started with no integration changes required.

Nuvei supports 3RI for Mastercard and VISA transactions, if the initial customer-initiated transaction (CIT) is performed by Nuvei or via an external merchant plugin (MPI).

The 3RI feature is primarily intended for a merchant with a high volume of merchant-initiated transactions that wants to benefit from a liability shift on the transactions. For example, ideal candidates for use of 3RI include use cases such as recurring/subscription, travel/hospitality, and partial/split shipment.

Business Value and Benefits

With 3RI, a merchant benefits from a liability shift on fraudulent chargebacks on which 3RI is performed successfully. In some cases, use of 3RI may result in increased approval rates.

For the merchant, there is currently no additional cost resulting from 3RI; however, interchange and scheme fees may vary for 3RI transactions.

Geographical Coverage

The 3RI feature can be used globally, however it is dependent on issuer coverage and merchant 3DS-preferences. 3RI is expected to be compatible anywhere Nuvei supports 3DS. The majority of adoption is expected in Europe and APAC markets; however, any market is relevant.

Technical Integration Details

For a merchant that uses Nuvei as the merchant plugin (also known as 3DS Merchant Server or MPI) and processes the initial CIT via Nuvei, no integration effort is required.

A transaction that successfully completes 3RI and qualifies for a liability shift, receives an Electronic Commerce Indicator (ECI) of 7 and a liability-shift status of true.

If a merchant uses an external MPI and sends transaction details through the external scheme details class via REST API, the merchant must include details from the initial 3DS transaction to qualify for 3RI.

Example Request

"externalSchemeDetails": {
     "transactionId": "1085798118",
     "brand": "VISA",
     "initial3DSData": {
        "eci": "5",
        "dsTransId": "550e8400-e29b-41d4-a716-446655440000",
        "acsTransId": "A000000003",
        "rebillExpiry": "20300219",
        "rebillFrequency": "75",
        "threeDSReqPriorAuthTimestamp": "202606011200"
     }

 

If initial3DSData does not match the original CIT authentication then the 3RI request is unsuccessful. For any unsuccessful 3RI request, Nuvei continues with recurring authorization which prevents any drop-off due to a 3RI failure.

If 3RI authentication is successful, the merchant receives liabilityshift = 1 in the response.

Flow

Example Flow

1. CIT is created with 3D Secure authentication.
   The ECI value equals 2.
   rebillExpiry and rebillFrequency are included in the 3D Secure request.
2. The merchant-initiated transaction starts and is linked to the CIT using the Nuvei transactionId or by including externalSchemeDetails and initial3DSData.
3. A 3RI request is sent to the issuer to request a liability shift for the transaction.
4. Authorization continues.
   The ECT value equals 7.
   The liability shift equals true.

Support