Request 3RI authentication
Last updated: August 27, 2025
3D requester-initiated authentications (3RI), also known as merchant-initiated authentications, allow you to submit data and authenticate a card-not-present (CNP) transaction. 3RI is a 3DS authentication message that enables processes such as account verification and re-authentication of recurring payments.
To generate the authentication data necessary for authorization, you'll need:
- The cardholder's information, which you stored during a previous transaction
- The details of a previous transaction
3RI benefits all parties in the payment ecosystem by facilitating better information flow between merchants and issuers. Additionally, 3RI:
- Helps the issuer make informed authorization decisions while protecting customer data
- Can shift liability away from you for merchant-initiated transactions (MITs) which can utilize 3RI, if necessary conditions are met
- Decreases the chance of SCA-related declines during authorization, which could increase approval rates (AR)
- 3RI enables you to obtain authentication or applicable fraud liability protection for CNP transactions, if there are previously authenticated transactions. This includes:- Delayed authorizations, including when the initial Cardholder Authentication Verification Value (CAVV) expires if later than 90 days - for example, preorders
- Split shipments - for example, orders containing multiple items, where part of the order is not available to ship yet
- To request CAVV as an authorized entity on behalf of a merchant, in a multi-party commerce scenario - for example, a travel agency requesting on behalf of another merchant
 
Note
Only Mastercard supports recurring 3RI MITs. If you request a recurring 3RI MIT with another scheme, it fails.
The customer-initiated transaction (CIT) referenced by your 3RI request must include:
- 3ds.enabledset to- true
- 3ds.challenge_indicatorset to- challenge_requested_mandate
- merchant_initiatedset to- false
- payment_typeset to- recurring
If the CIT does not meet these requirements, you must perform a new CIT with the required fields and values.
To process a 3RI request in your MIT, you need to provide the payment ID for a transaction in which 3DS was successful in the previous_payment_id field. You should also verify that 3ds.enabled is set to true in the request.
If your 3RI request fails, either due to an unsupported use case or lack of issuer approval, then it'll automatically fall back to being processed as a non-3DS MIT during authorization.
If the response contains an eci field set to 07, the 3RI request was successful.
If you previously processed the CIT with Checkout.com, you can provide the CIT's session ID value (prefixed with sid_)  to the 3RI request's initial_session_id field.
If not, you can either:
- Perform a new CIT with Checkout.com to renew the MIT contract
- Manually provide the initial_transactiondata, using the following fields:- acs_transaction_id
- authentication_method
- authentication_timestamp
- authentication_data
 
Note
For Mastercard 3RI requests, you must provide the Directory Server (DS) transaction ID in the authentication_data field.
If your 3RI request fails, either due to an unsupported use case or lack of issuer approval, you can choose to process the transaction as a non-3DS MIT for authorization.
If a third-party authentication provider performed the initial CIT authentication, you must manually provide the initial_transaction data using the following fields:
- acs_transaction_id
- authentication_method
- authentication_timestamp
- authentication_data
Note
For Mastercard 3RI requests, you must provide the DS transaction ID in the authentication_data field.
If your 3RI request fails, either due to an unsupported use case or lack of issuer approval, then it'll automatically fall back to being processed as a non-3DS MIT during authorization.