This guide explains how to perform a merchant/PSP initiated 3D Secure authentication.
This is also known as a 3DS Requestor Initiated (3RI) authentication.
This type of authentication is performed without the cardholder present.
This can be used for recurring payments or payments made in installments, when the cardholder has previously set up the payment.
The merchant/PSP initiated 3D Secure flow is shown below:
To prepare an Authenticate Request your back-end must gather the required customer and transaction data.
See our 3D Secure API reference for full details of the Authenticate Request.
A merchant/PSP initiated authentication is identified by setting the
deviceChannel field to
Once Ravelin receives the Authenticate Request we will proceed with the 3D Secure process. The authentication request is sent to the ACS which decides the outcome of the authentication.
Merchant/PSP initiated authentications cannot use a 3D Secure challenge since the cardholder is not present.
The Authenticate Response will be returned to your back-end. An example of a successful Authenticate Response is shown below:
See our 3D Secure API reference for full details of the Authenticate Response.
The Authenticate Response
transStatus field describes the next action you need to take.
|Transaction Status||Description||Next Action|
||Authentication Successful||The transaction achieved a Frictionless authentication. Continue to authorisation using the
||Authentication Attempted||The cardholder was not authenticated, but proof of the authentication being attempted has been provided. Continue to authorisation using the
||Decoupled Challenge Required||Decoupled authentication will be performed by the issuer. Make a Result Request to learn the final outcome.|
||Authentication Failed||See the
||Authentication Unavailable||See the
||Authentication Rejected||See the
||Informational Only||Authentication was not requested. The data was sent to the ACS for informational purposes only.|
Was this page helpful?