3DS 1.0 API

3DS 1.0 Flow

3DS 1.0 Authentication Flow

For information about the API endpoints, please refer to the Integration Manual.

Schema

Note that the schema for the 3DSecure 1.x includes the 3-D Secure schema (ThreeDSecure.xsd) to refer to 3-D Secure protocol messages used in the response structures.

PaReqCreationRequest samples

There are two possibilities to transfer the merchant data to the Directory Server:

Merchant configured via the Admin application
Merchant configuration data passed in the PaReqCreationRequest

Merchant configured via the Admin application

The required merchant.id needs to be passed in the PaReqCreationRequest and it needs to match the id of the configured Merchant.

The required data to be passed in the PaReqCreationRequest consists of:

merchant.id
purchase.amount
purchase.currency
cardholder.expiry
cardholder.pan

Optional is:

purchase.xid
purchase.exponent

PaReqCreationRequest (minimum valid JSON)

PaReqCreationRequest (JSON/XML)

PaReqCreationRequest (POST parameters)

Merchant configuration data in PaReqCreationRequest

If Merchant data is available in the client's Payment Environment, there is a possibility to pass it as part of the PaReqCreationRequest, instead of configuring it via the Admin.

The required data to be passed in the PaReqCreationRequest consists of:

merchant.acquirerBin
merchant.countryCode
merchant.id
merchant.name
merchant.url
purchase.currency
purchase.amount
cardholder.expiry
cardholder.pan

Optional is:

merchant.password
purchase.xid
purchase.exponent

PaReqCreationRequest & Merchant data (minimum valid JSON)

PaReqCreationRequest & Merchant data (JSON/XML)

PaReqCreationRequest & Merchant data (POST parameters)

3-D Secure extension in PaReqCreationRequest

3-D Secure extensions are supported. They must be sent as a xml string for all media type requests.

PaReqCreationRequest & Extensions (minimum valid JSON)

PaReqCreationRequest & Extensions (JSON/XML)

PaReqCreationRequest & Extensions (POST parameters)

PaReqCreationResponse samples

PaReqCreationResponse (JSON)

PaReqCreationResponse (XML)

PaResValidationRequest samples

In order to verify the contents in the Payer Authentication Process step, values from the Verify Enrollment Step are needed. This data can be:

cached internally, or
could be provided externally through the API in the SessionData element.

Cached internally

PaResValidationRequest (JSON/XML)

PaResValidationRequest (POST parameters)

Please note that the real PaReq value has 3-4Kb in length and the above example just demonstrates the request format.