3DS Standalone

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 to be configured on the merchant sites. See the detailed description for each step below.

Open

Integration steps

Step 1: 3DS 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.

Step 3: 3DS Auth API

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

Step 4: ACS challenge and receive challenge result

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

Step 5: 3DS Result API

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

Step 6: Add 3DS fields in Sale API
- 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.

API Status Codes

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

Netvalve Documentation