Skip to main content

3DS Standalone V2 Apis

The following describes the integration steps for NetValve Standalone 3DS.

info

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​

  • Initialisation Api
    Initiate the 3DS flow by calling POST /3ds/v2/initialization. The response indicates which flow to take - A (frictionless) or B (challenge).
  • ACS challenge (Flow B) Conditional
    If the response is Flow B (ACS_REQUIRED), set up the ACS challenge using an iframe or page-redirect, and wait for completion.
  • 3DS Result API (Flow B) Conditional
    After being notified that the challenge is complete, call the Result API to access the 3DS values.
  • Add 3DS fields in Sale API (Flows A, B)
    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.

API Status Codes

Swagger API​

Swagger API documentation is also available at the link below:

NetValve Merchant Documentation

Demo Video & Source Code​

Follow this link for a demo video and a demo website source code.