/v1/transactions

Create a 3RI authenticated transaction

Changed on

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.

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

Path parameters

transactionIdinteger required

The transactionId received after an authorization.

Request body

refnostring required

The merchant's reference number. It should be unique for each transaction.

currencystring required

3 letter <a href='https://en.wikipedia.org/wiki/ISO_4217' target='_blank'>ISO-4217</a> character code. For example CHF or USD

amountinteger required

The amount of the transaction in the currency’s smallest unit. For example use 1000 for CHF 10.00.

threeRIIndstring

The 3RI request related parameter threeRIInd with values 01-99

multiMerchantNamestring

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

Successfully created 3RI authenticated transactions

transactionIdstring

The transactionId to use for subsequent actions like settlement.

refreshedboolean

The 3D object is only present if init call was done with an alias.

Changes