- Initiate a standalone authentication request
Initiates a standalone 3D Secure authentication request for a transaction. This endpoint is for merchants who use PXP's service solely for authentication purposes. The process involves verifying the cardholder's identity through a browser-based interaction. 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. This ensures a secure and efficient authentication process.
The URL for notifying the fingerprinting result. Base64 of {"threeDSMethodNotificationURL":"method url value","threeDSServerTransID":"transaction id value"}.
The four-digit Merchant Category Code (MCC) assigned to the merchant.
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
The 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.
- Production environmenthttps://api-services.pxp.io/api/v1/threedsecure/standalone/authentications/{authenticationId}/browser-authentication
- Sandbox environmenthttps://api-services.test.pxp.io/api/v1/threedsecure/standalone/authentications/{authenticationId}/browser-authentication
curl -i -X PUT \
'https://api-services.pxp.io/api/v1/threedsecure/standalone/authentications/{authenticationId}/browser-authentication' \
-H 'Content-Type: application/json' \
-d '{
"fingerprintNotification": "string",
"merchantCategoryCode": "5411",
"merchantCountryNumericCode": "840",
"merchantLegalName": "ACME Ltd",
"acquirerMerchantId": "string",
"challengeWindowSize": 1,
"requestorChallengeIndicator": "st",
"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
The current state of the authentication request. PendingClientData isn't returned during initiation.
The Directory Server transaction ID.
The status of the transaction.
Possible values include:
Y: AuthenticationVerificationSuccessfulN: NotAuthenticated_NotVerifiedU: AuthenticationCouldNotBePerformedA: AttemptsProcessingPerformedC: ChallengeRequiredR: AuthenticationRejectedI: InformationalOnly
The indicator used to signify the level of security used in the authentication, often used in electronic commerce transactions.
A value generated during the authentication process to verify the cardholder's identity.
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
{ "TransactionRiskAnalysisExemption": { "value": 5 } }
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.
Details about the state. This is returned only when the transactionStatus is different from Y or A.
{ "state": "AuthenticationSuccessful", "directoryServerTransactionId": "98ec7e22-04f6-47e9-ab45-5c5d20441935", "transactionStatus": "Y", "electronicCommerceIndicator": "05", "cardholderAuthenticationVerificationValue": "CAVV1234567890", "exemptionGranted": false, "exemptionGrantedByIssuer": "79", "cardholderInfo": "Additional authentication information" }