3DS Standalone

The following describes the integration steps for Netvalve Standalone 3DS. Contact the Netvalve team to ensure 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.

Integration steps

https://netvalve.atlassian.net/wiki/spaces/ND/pages/950403

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

https://netvalve.atlassian.net/wiki/spaces/ND/pages/950335

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

https://netvalve.atlassian.net/wiki/spaces/ND/pages/950466

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

https://netvalve.atlassian.net/wiki/spaces/ND/pages/950524

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

https://netvalve.atlassian.net/wiki/spaces/ND/pages/950587

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

https://netvalve.atlassian.net/wiki/spaces/ND/pages/5046516
- Use the 3DS values in the request body of the Sale API

Demo Example of 3DS flow

https://netvalve.atlassian.net/wiki/spaces/ND/pages/21626902

API status codes

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

https://netvalve.atlassian.net/wiki/spaces/ND/pages/950475

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

Netvalve Documentation