Standalone 3DS Authentication Service

Service Definition

Thie standalone 3DS authentication service allow you to partner with Evonet exclusively for 3DS authentication, while routing authorization through other service providers. This model is ideal for clinets who already have an established authorization channel but require enhanced authentication capabilities.

Prerequisties

• Your current authorization service provider or gateway must support submitting 3DS authentication result parameters obtained from a third party
• The merchant and acquirer parameters used during 3DS authentication and authorization must be identical to ensure the integrity and validity of the 3DS authentication, enabling liability shift in the event of a chargeback

Integration Steps

1. Configuration Requirements:

Submit your acquirer institution parameters and merchant IDs used for authorization with each card scheme to Evonet. The required parameters vary by card scheme:

2. Inpletementation Process:

• Evonet completes system configuration based on teh provided parameters
• Evonet provides the required Direct API credentials (KeyID, Key)
• Using the provided credentials ,submit card information and transaction details via the Direct API POST payment endpoint

3. Key Parameters:

• authenticationOnly: Must be set to true, indicating authentication only without authorization
• returnURL: Required; specifies the redirect page after authentication completes (typically a payment status inquiry page)
• webhook: Required; used to receive authentication results

4. Retrieving Authentication Results:

Authentication results are delivered via asynchronous notification and can also be queried through the GET payment endpoint. The result includes an authentication object as shown below:

{
  "cavv": "AJkBBmKHRQAAAABkhAFxdAAAAAA=",
  "dsTransID": "a6562a7b-f1cb-49ae-b380-ab408fa3b470",
  "eci": "05",
  "status": "Y",
  "threeDSVersion": "2.1.0"
}

5. Best Practice:

It is recommended to proceed with the subsequent authorization transaction only when the 3DS authentication result is explicitly successful (status value of "Y" or "A").

Standalone Authorization Service

Service Definition

The standalone authorization service enables you to complete 3DS authentication with another provider and then submit the obtained 3DS parameters to Evonet for authorization processing. This service is suitable for clients who already have 3DS authentication capabilities but seek a reliable authorization channel.

Prerequisites

• Use the same card scheme institution credentials and merchant parameters as those used for authorization
• Have obtained the complete 3DS authentication result parameters from your 3DS service provider

Required Parameters

Integration Steps

1. Use the SID associated with the corresponding merchant parameters to call the Evonet Merchant API POST payment endpoint
2. Submit the above parameters to their respective fields within the authentication object
3. Ensure the order amount (value and currency) matches exactly with the amount used during 3DS authentication
4. Ensure the card information matches exactly with the card used during 3DS authentication

Risk Management Recommendations

Determine whether to proceed with authorization based on the 3DS authentication result:

Transaction Result Interpretation

• Transaction Successful: result.code equals S0000 and payment.status equals Captured or Authorised
• Transaction Failed: result.code does not equal S0000 and payment.status equals Failed