Pre-initiates an integrated 3D Secure authentication request for a transaction. In integrated mode, PXP processes the transaction in a separate initiate transaction request using the 3D Secure supplied data. This step ensures that all required data is gathered and validated before the full authentication process, facilitating a smoother and more secure transaction flow.
The unique identifier for the provider.
The intent of the authentication request. This field is conditionally required: it's required if providerId isn't sent, otherwise it's optional. It makes sense to authenticate transactions with the following intents:
PurchaseAuthorisationEstimatedAuthorisationVerification
Indicator used to specify the type of authentication request, such as payment authentication or account verification.
Possible values:
01: Payment transaction02: Initial recurring transaction03: Initial card-on-file transaction for subsequent MITs04: Initial card-on-file transaction for subsequent CITs05: Store card details without purchase (card verification)06: Instalment transaction07: Billing agreement08: Split shipment09: Delayed shipment10: Split payment
Use full card details for authentication. This option requires the primary account number, expiry date, cardholder name, and optionally, the card verification code (CVC).
- Production environmenthttps://api-services.pxp.io/api/v1/threedsecure/integrated/authentications
- Sandbox environmenthttps://api-services.test.pxp.io/api/v1/threedsecure/integrated/authentications
- Card
- Gateway token
- Scheme token
- Scheme token (external)
curl -i -X POST \
https://api-services.pxp.io/api/v1/threedsecure/integrated/authentications \
-H 'Content-Type: application/json' \
-d '{
"amount": {
"transactionValue": 0.1,
"currencyCode": "EUR"
},
"fingerprintCallbackUrl": "string",
"providerId": "provider_123456",
"intent": "Authorisation",
"requestorAuthenticationIndicator": "01",
"site": "string",
"card": {
"primaryAccountNumber": "4111111111111111",
"cardHolderName": "string",
"expiryMonth": 3,
"expiryYear": 2025,
"cardVerificationCode": "123"
}
}'OK
A unique reference provided by PXP for the authentication request, represented as a GUID.
The current state of the authentication request. For pre-initiation, this can only be PendingClientData or null (if the card isn't enrolled for 3DS).
Whether Strong Customer Authentication (SCA) is mandated for this transaction.
Specifies any exemptions that apply to the transaction from SCA requirements.
The version of the 3D Secure protocol being used for the authentication.
The URL to which the 3D Secure method data should be sent.
Data required for the 3D Secure method, typically a base64 encoded string.
Whether 3D Secure authentication is supported for this transaction.
{ "authenticationId": "550e8400-e29b-41d4-a716-446655440000", "state": "PendingClientData", "scaMandated": true, "applicableExemptions": "LVP", "threeDSecureVersion": "2.1.0", "threeDSecureFingerprintUrl": "https://example.com/3ds-method", "threeDSecureFingerprintData": "eyJ0aHJlZURTU2VjdXJlTWV0aG9kRGF0YSI6IlhYWiJ9", "threeDSecureSupported": true, "recommendedChallengeIndicator": "string" }