Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Step 1: 3DS V2 Initialisation Api

  • Initiate the 3DS flow by calling this API and receiving back a redirectUrl of netvalve page to do Iframe Step.

Step 2: Create Device Data Collection Iframe and POST event listener

  • Setup a hidden iframe and wait for a POST message which contains a transID property.

...

  • . 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

Step 4: ACS challenge and receive challenge result V2 ACS challenge (Flows B, C) Conditional

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

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

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

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

Demo Example of 3DS flow

Demo Video

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

https://docs.netvalve.com/

V2 Demo Video + Source Code

Demo Video + Source Code