3DS Standalone V2 Apis

Owned by Yogesh Dahe
Last updated: Aug 15, 2024 by Kyle Robinson
1 min read

The following describes the integration steps for Netvalve Standalone 3DS. Contact the Netvalve team to ensure the 3DS configuration steps have been followed, and you have credentials for the API authentication.

Flow

See below the required sequence of Netvalve 3DS API calls, and the iframes/redirects to be configured on the merchant sites. See the outline for each flow here, and a detailed description for each step in the pages below.

Integration steps

 

V2 Initialisation Api

  • Initiate the 3DS flow by calling this API. The response will indicate which flow to take - A, B, C.

V2 3DS Auth API (Flow C) Conditional

  • Using the transID call the Auth API. If response shows challengeRequired, proceed to Step 4

V2 ACS challenge (Flows B, C) Conditional

  • Setup the ACS challenge using an iframe or page-redirect, and wait for completion.

V2 3DS Result API (Flows B, C)Conditional

  • After being notified that the challenge is complete, call the Result API to access 3DS values.

V2 Add 3DS fields in Sale API (Flows A, B, C)
- Use the 3DS values in the request body of the Sale API

 

API status codes

Please refer to the document below for a list of API response codes and descriptions.

V2 API Status Codes

 

Swagger API documentation is also updated in the Netvale documentation link below

Netvalve Documentation

V2 Demo Video + Source Code

Demo Video + Source Code