This is an API reference for the 3D Secure authentication service.
- Pre-initiate an integrated authentication request
3D Secure authentication service API (1.0.0)
https://api-services.pxp.io/api/v1/
https://api-services.test.pxp.io/api/v1/
Request
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 acquirer's profile.
The unique identifier for the provider.
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
Details related to the card used for 3D Secure authentication. You can provide card details directly, use a stored gateway token, or use a scheme token.
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 environment
https://api-services.pxp.io/api/v1/threedsecure/integrated/authentications
- Sandbox environment
https://api-services.test.pxp.io/api/v1/threedsecure/integrated/authentications
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
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",
"acquirerProfileId": "acquirer_123456",
"providerId": "provider_123456",
"requestorAuthenticationIndicator": {
"PaymentTransaction": {
"value": 1
}
},
"site": "string",
"cardData": {
"card": {
"primaryAccountNumber": "4111111111111111",
"holderName": "string",
"expiryMonth": "03",
"expiryYear": "2025",
"cardVerificationCode": "123"
}
}
}'
OK
A unique reference provided by PXP for the authentication request, represented as a GUID.
Current state of the authentication request, indicating the status of the pre-initiation process.
Indicates 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.
Indicates 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" }
Request
Authenticates an integrated 3D Secure transaction request. In integrated mode, PXP processes the transaction in conjunction with the 3D Secure authentication data. This ensures that the transaction is authenticated securely, leveraging the full authentication data collected during the pre-initiation phase. The request payload must include comprehensive details about the transaction, card information, merchant information, and additional contextual data necessary for the 3D Secure authentication flow.
URL for notifying the fingerprinting result. Base64 of {"threeDSMethodNotificationURL":"method url value","threeDSServerTransID":"transaction id value"}
The three-digit country code of the merchant, following ISO 3166-1 numeric standard.
The legal name of the merchant.
The desired size of the challenge window displayed to the cardholder during authentication.
Possible values:
1
: 250x4002
: 390x4003
: 500x6004
: 600x4005
: FullScreen
Indicator of whether a challenge is requested for this transaction.
Possible values:
01
: NoPreference02
: NoChallengeRequested03
: ChallengeRequested3dsRequestorPreference04
: ChallengeRequestedMandate05
: NoChallengeRequestedTRAPerformed06
: NoChallengeRequestedDataShareOnly07
: NoChallengeRequestedStrongConsumerAuthentication08
: NoChallengeRequestedTrustListExemption09
: ChallengeRequestedTrustListPrompt10
: NoChallengeRequestedLowValueExemption11
: NoChallengeRequestedSecureCorporatePayment12
: ChallengeRequestedDeviceBindingPrompt13
: ChallengeRequestedIssuerRequested14
: ChallengeRequestedMerchantInitiatedTransactions
Fully qualified URL of the system that receives the CRes message or Error Message. The CRes message is posted by the ACS through the Cardholder Browser at the end of the challenge and receipt of the RRes message.
Details related to recurring transactions for 3D Secure authentication.
Details of the address used in browser-based authentication.
Details of the address used in browser-based authentication.
Information about the browser used in the authentication process.
The Accept HTTP header field from the browser.
The color depth of the browser's screen, measured in bits per pixel.
The IP address of the device running the browser, if available.
Indicates whether the browser has Java enabled.
Indicates whether the browser has JavaScript enabled.
IETF BCP 47 language tag is used
The height of the browser's screen in pixels.
The width of the browser's screen in pixels.
The difference, in minutes, between UTC and the local time of the browser.
Details about the shopper involved in the authentication.
The email address of the shopper.
The home phone number of the shopper.
The mobile phone number of the shopper.
- Production environment
https://api-services.pxp.io/api/v1/threedsecure/integrated/authentications/{authenticationId}/browser-authentication
- Sandbox environment
https://api-services.test.pxp.io/api/v1/threedsecure/integrated/authentications/{authenticationId}/browser-authentication
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://api-services.pxp.io/api/v1/threedsecure/integrated/authentications/{authenticationId}/browser-authentication' \
-H 'Content-Type: application/json' \
-d '{
"fingerprintNotification": "string",
"merchantCountryNumericCode": "840",
"merchantLegalName": "ACME ltd",
"challengeWindowSize": {
"500x600": {
"value": 3
}
},
"requestorChallengeIndicator": {
"NoPreference": {
"value": 1
}
},
"challengeCallbackUrl": "http://example.com",
"recurring": {
"expirationDate": "2024-12-31T23:59:59Z",
"frequencyInDays": 30
},
"billingAddress": {
"city": "San Francisco",
"countryNumericCode": "840",
"line1": "123 Market St",
"line2": "Apt 456",
"line3": "Building B",
"postalCode": "94105",
"stateCode": "CA"
},
"shippingAddress": {
"city": "San Francisco",
"countryNumericCode": "840",
"line1": "123 Market St",
"line2": "Apt 456",
"line3": "Building B",
"postalCode": "94105",
"stateCode": "CA"
},
"browserData": {
"acceptHeader": "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8",
"colorDepth": 24,
"ipAddress": "192.168.1.1",
"javaEnabled": true,
"javaScriptEnabled": true,
"language": "en-US",
"screenHeight": 1080,
"screenWidth": 1920,
"timeZoneOffsetInMinutes": -420,
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36"
},
"shopper": {
"email": "johndoe@example.com",
"homePhoneNumber": "+1234567890",
"mobilePhoneNumber": "+0987654321",
"workPhoneNumber": "+1123456789"
}
}'
OK
Current state of the authentication request, indicating the status of the authentication process.
The status of the transaction.
Possible values include:
Y
: AuthenticationVerificationSuccessfulN
: NotAuthenticated_NotVerifiedU
: AuthenticationCouldNotBePerformedA
: AttemptsProcessingPerformedC
: ChallengeRequiredR
: AuthenticationRejectedI
: InformationalOnly
Indicator used to signify the level of security used in the authentication, often used in electronic commerce transactions.
Indicates whether an exemption from Strong Customer Authentication (SCA) was granted.
Specifies if the exemption was granted by the issuer.
Possible values:
05
: TransactionRiskAnalysisExemption08
: TrustListExemption10
: LowValueExemption11
: SecureCorporatePaymentsExemption79
: NoExemptionApplied
The URL of the Access Control Server (ACS) where the cardholder is redirected for challenge authentication.
Data required for the challenge authentication process, typically a base64 encoded string.
{ "uniqueId": "string", "state": "PendingClientData", "transactionStatus": { "AuthenticationVerificationSuccessful": { … } }, "electronicCommerceIndicator": "05", "exemptionGranted": true, "exemptionGrantedByIssuer": { "TransactionRiskAnalysisExemption": { … } }, "acsUrl": "https://acs.example.com/challenge", "challengeData": "eyJjaGFsbGVuZ2VEYXRhIjoiQUJDIn0=", "stateData": { "code": "string", "reason": "string" }, "cardholderInfo": "string" }