3D Secure 1.0 Enrollment - Deprecated

post

https://api-integration.pxp-solutions.net/threeDSecureService/api/v5/3ds1/enrollment

This transaction type allows the merchant to check the 3D Enrollment status of a given card

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

🚧
PSD2 Exemptions:
Please note that the scaDetails object is not yet available for either the request or response.
PXP will notify merchants once this becomes available

Body Params

merchantId

string

required

[Length=3] This is the customer code, a unique customer ID allocated to a customer when the service is set up

storeId

string

required

[Length=12] This is the site identifier, a unique site ID allocated to a customer when the service is set up

userId

string

required

[Length<=50] This is a username allocated to a service user when the service is set up; it refers to a service account not a person

type

string

This is a combination of how the card was captured and transaction type of the transaction. i.e. mailorder.sale, internet.preAuthorization. Refer to Type under Elements

amount

string

required

This is the monetary value of the transaction in minor units

currencyCode

string

required

[Length=3] This is the currency of the transaction. This is the currency code. A three character code in accordance with ISO 4217

clientSystemTransactionId

string

required

[Length<=50] This is the merchant's own unique reference for the transaction

isAutoAuthorisationRequired

string

[True/False] If set to True, PXP will automatically proceed for authorisation following the 3D Secure authentication of the card holder

details

object

accountDetails

object

encryptionDetails

object

storedCredentialDetails

object

addressVerificationDetails

object

cardVerificationDetails

object

scaDetails

object

Headers

Authorization

string

Defaults to Basic QkREVGVzdDpCRERUZXN0

Responses

PSD2 Exemptions:

200200

412412