---
title: "Create a 3RI authenticated transaction"
method: POST
path: "/v1/transactions/3RI/multipleAuthentication/{transactionId}"
tags: ["/v1/transactions"]
---

# Create a 3RI authenticated transaction

`POST /v1/transactions/3RI/multipleAuthentication/{transactionId}`

## Request

- Base URL: `https://api.sandbox.datatrans.com`
- URL: `https://api.sandbox.datatrans.com/v1/transactions/3RI/multipleAuthentication/{transactionId}`
- Auth: HTTP basic

Use this endpoint to perform a 3‑D Secure Requestor Initiated (3RI) authentication when the cardholder is not actively participating in the transaction; This effectively results in an authenticated MIT (merchant initiated transaction). Typical use cases include split payments (deposit + balance), unscheduled card-on-file transactions, delayed charges or instalments. You must always use the original transaction reference for the initial CIT in the API endpoint, and then depending on which 3RI use case, the value of certain fields will need to be adjusted.

## Path parameters

- `transactionId` integer, required: The transactionId received after an authorization.

## Request body

- RefreshThreeRIMultipleMerchRequest
  - `refno` string, required: The merchant's reference number. It should be unique for each transaction.
  - `currency` string, required: 3 letter <a href='https://en.wikipedia.org/wiki/ISO_4217' target='_blank'>ISO-4217</a> character code. For example `CHF` or `USD`
  - `amount` integer, required: The amount of the transaction in the currency’s smallest unit. For example use 1000 for CHF 10.00.
  - `threeRIInd` string: The 3RI request related parameter threeRIInd with values 01-99
  - `multiMerchantName` string: Only used for the multi-party commerce use-case. This is the name of the third-party merchant who will be using the output of the 3RI authentication to process the authorization. Note that the name must be written exactly as the merchant sends it in the merchantName field in a 3DS request or authorization request.

## Response `200`

Successfully created 3RI authenticated transactions

- RefreshThreeRIResponse
  - `transactionId` string: The transactionId to use for subsequent actions like settlement.
  - `refreshed` boolean: The `3D` object is only present if init call was done with an `alias`.
  - `3D` EMVCo3DAuthenticationDataStatusResponse: 3D authentication data, if available
    - `eci` '01' | '02' | '05' | '06' | '07': The Electronic Commerce Indicator
    - `xid` string: The transaction ID returned by the directory server
    - `dsTransId` string: The transaction ID returned by the directory server
    - `threeDSTransactionId` string: The transaction ID returned by the 3D Secure Provider
    - `cavv` string: The Cardholder Authentication Verification Value
    - `threeDSVersion` string: The 3D version
    - `cavvAlgorithm` string: The 3D algorithm
    - `directoryResponse` 'Y' | 'N' | 'U' | 'C' | 'R' | 'A': Transaction status after `ARes` |Value|3Dv1|3Dv2| |:---|:---|:---| |Y| enrolled| authenticated| |N| not enrolled| authentication failed| |U| not available| not available| |C| |challenge needed| |R| |rejected| |A| |authentication attempt|
    - `authenticationResponse` 'Y' | 'N' | 'U' | 'A' | 'C' | 'R' | 'I' | 'D': Transaction status after `RReq` (Challenge flow) |Value|3Dv1|3Dv2| |:---|:---|:---| |Y| authenticated| authenticated| |N| authentication failed| authentication failed| |U| not available| not available| |A| authentication attempt| authentication attempt| |C| process incomplete| process incomplete| |R| |authentication/account verification rejected| |I| |informational only| |D| not enrolled| |
    - `transStatusReason` string: Transaction status reason |Value|Description| |:---|:---| |01| Card authentication failed| |02| Unknown Device| |03| Unsupported Device| |04| Exceeds authentication frequency limit| |05| Expired card| |06| Invalid card number| |07| Invalid transaction| |08| No Card record| |09| Security failure| |10| Stolen card| |11| Suspected fraud| |12| Transaction not permitted to cardholder| |13| Cardholder not enrolled in service| |14| Transaction timed out at the ACS| |15| Low confidence| |16| Medium confidence| |17| High confidence| |18| Very High confidence| |19| Exceeds ACS maximum challenges| |20| Non-Payment transaction not supported| |21| 3RI transaction not supported| |22| ACS technical issue| |23| Decoupled Authentication required by ACS but not requested by 3DS Requestor| |24| 3DS Requestor Decoupled Max Expiry Time exceeded| |25| Decoupled Authentication was provided insufficient time to authenticate cardholder. ACS will not make attempt| |26| Authentication attempted but not performed by the cardholder| |27–79| Reserved for EMVCo future use (values invalid until defined by EMVCo)| |80–99 | Reserved for DS use|
    - `cbAvalgo` string
    - `cbScore` string
    - `cbExemption` string
    - `cardHolderInfo` string: Text provided by the ACS/Issuer to Cardholder during a transaction that was not authenticated by the ACS. The Issuer can optionally provide information to Cardholder. For example, "Additional authentication is needed for this transaction, please contact (Issuer Name) at xxx-xxx-xxxx."

## Changes

- **2026-11-03** `78b27ccc5443`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/pci-proxy/apis/pci-proxy-api-reference-datatrans-endpoints/changes/v1/transactions/3RI/multipleAuthentication/:transactionId/post.md)

---

[API](https://skmtc.dev/pci-proxy/apis/pci-proxy-api-reference-datatrans-endpoints.md) - [All operations](https://skmtc.dev/pci-proxy/apis/pci-proxy-api-reference-datatrans-endpoints/llms.txt) - [OpenAPI document](https://skmtc.dev/pci-proxy/apis/pci-proxy-api-reference-datatrans-endpoints/revisions/78b27ccc5443?raw)