3D Secure Integration

3DS 2.3.1 API changes

On this page:

This guide describes the changes to the request and response formats for version 2.3.1 relative to version 2.2.0.

Each field in a request or response section is linked through to its detailed definition on the corresponding 3DS API endpoints page.

Changes to Authenticate Request

These are the changes to the Authenticate Request for version 2.3.1.

Existing fields

These are changes to the existing fields on the Authenticate Request for version 2.3.1.

FieldDescription of changeAction required
threeDSRequestorAuthenticationInfofrom string to an array of stringsSingle string or array of strings accepted; consider using an array if you want to provide multiple values for this field on 2.3.1 requests
threeDSRequestorChallengeIndfrom object to array of objectsSingle object or array of objects accepted; consider using an array if you want to provide multiple instances of this field on 2.3.1 requests
threeDSRequestorPriorAuthenticationInfofrom object to array of objectsSingle object or array of objects accepted; consider using an array if you want to provide multiple instances of this field on 2.3.1 requests
whiteListStatusrenamed to trustListStatusFor maintaining backward compatibility we accept either field name.
whiteListStatusSourcerenamed to trustListStatusSourceFor maintaining backward compatibility we accept either field name.
authenticationTypechanged to authenticationMethodOn 2.1.0 and 2.2.0 responses the original authenticationType will be returned. On 2.3.1 responses the authenticationMethod will be mapped to an equivalent authenticationType

New fields

These are the new fields on the Authenticate Request for version 2.3.1.

FieldDescription of changeRequired, Conditional, Optional
acceptLanguagebrowser language preferenceRequired (BRW)
acquirerCountryCodecountry code of acquirerRequired (APP, BRW, 3RI)
appIpIP address used by the 3DS Requestor AppOptional
cardSecurityCodethree or four-digit security code printed on the cardConditional — based on DS rules
defaultSdkTypeindicates the characteristics of a Default-SDKOptional
deviceBindingStatusto allow devices to be remembered as trustedOptional
deviceBindingStatusSourcesource of device binding statusOptional
deviceIdunique and immutable identifier linked to a deviceConditional — required if available
multiTransactionadditional transaction information in case of multiple transactions or MerchantsOptional
payeeOriginorigin of Payee for SPC Transaction dataOptional
recurringAmountamount for recurring paymentsConditional
recurringCurrencycurrency for recurring amountConditional — required when recurringAmount is provided
recurringDatedate for recurring amountConditional — required if recurringInd (01) or recurringFrequency (01)
recurringExponentexponent for recurring amountConditional — required when recurringAmount is provided
recurringIndindicator for recurring paymentConditional — required when threeDSRequestorAuthenticationInd is Recurring (02) or Instalment (03), or threeRIInd is Recurring (01) or Instalment (02)
sdkTypetype of 3DS SDKRequired (APP)
splitSdkTypeindicates the characteristics of a Split-SDKConditional — required if sdkType = 02
sdkServerSignedContentsigned content for Split-SDKConditional — required if sdkType = 02
sdkSignatureTimestamptimestamp of signed contentOptional
threeDSMethodIdallows Method requests to be reusedConditional — required if 3DS Requestor reuses a previous 3DS Method execution
sellerInfoadditional transaction information regarding sellersOptional
threeDSRequestorSpcSupportindicates 3DS Requestor support for SPCOptional
taxIdcardholder’s tax identificationOptional
userIdidentifier of the transacting user’s Browser Account IDConditional — required if available

New values

These are the changes in permitted values for existing fields on the Authenticate Request.

FieldDescription of change
threeRIIndadditional values for version 2.3.1

Changes to Authenticate Response

These are the changes to the Authenticate Response for version 2.3.1.

Existing fields

These are changes to existing fields on the Authenticate Response for version 2.3.1.

FieldDescription of changeAction required
authenticationTypechanged to authenticationMethodOn 2.1.0 and 2.2.0 responses the original authenticationType will be returned. On 2.3.1 responses the authenticationMethod will be mapped to an equivalent authenticationType
whiteListStatusrenamed to trustListStatusFor maintaining backward compatibility we accept either field name.
whiteListStatusSourcerenamed to trustListStatusSourceFor maintaining backward compatibility we accept either field name.

New fields

These are new fields on the Authenticate Response for version 2.3.1.

FieldDescription of change
authenticationMethodFiner granularity than legacy authenticationType. On 2.3.1 responses authenticationMethod is returned from the scheme; on 2.1.0 and 2.2.0 we map authenticationType onto the nearest equivalent authenticationMethod.
cardholderInfoIssuerImagethe URL of the issuer’s logo or image to be displayed to the cardholder.
cardholderInfoPaymentSystemImagethe URL of the payment system’s logo or image to be displayed to the cardholder
cardSecurityCodeStatusenables the communication of Card Security Code Status between the ACS, the DS and the 3DS Requestor
cardSecurityCodeStatusSourcepopulated by the system setting Card Security Code Status
deviceBindingStatusto allow devices to be remembered as trusted
deviceBindingStatusSourcesource of device binding status
deviceRecognisedVersionthe highest Data Version of the Device Information supported by the ACS
spcTransDatainformation that the 3DS Requestor passes in the SPC API for display in the Smart Modal Window
threeDSRequestorAppURLIndindicates whether the OOB Authentication App used by the ACS during a challenge supports the 3DS Requestor App URL
transChallengeExemptionexemption applied by the ACS to authenticate the transaction without requesting a challenge
transStatusReasonInfotransaction Status Reason Information
webAuthnCredListlist of WebAuthn credentials that the ACS can use to authenticate the cardholder

New values

These are changes in permitted values for existing fields on the Authenticate Response.

FieldDescription of change
transStatusadditional values for 2.3.1
transStatusReasonadditional values for 2.3.1

Changes to Result Request

No changes have been made to the Result Request for version 2.3.1.

Changes to Result Response

These are changes to the Result Response for version 2.3.1.

Existing fields

These are changes to existing fields on the Result Response for version 2.3.1.

FieldDescription of changeAction required
authenticationTypechanged to authenticationMethodOn 2.1.0 and 2.2.0 responses the original authenticationType will be returned. On 2.3.1 responses the authenticationMethod will be mapped to an equivalent authenticationType
whiteListStatusrenamed to trustListStatusFor maintaining backward compatibility we accept either field name.
whiteListStatusSourcerenamed to trustListStatusSourceFor maintaining backward compatibility we accept either field name.

New fields

These are new fields on the Result Response for version 2.3.1.

FieldDescription of change
acsRenderingTypeidentifies the type of UI the ACS presents to the consumer
acsTransIDunique identifier (UUID) used by the Issuer for tracking the transaction throughout the 3DS process
authenticationMethodFiner granularity than legacy authenticationType. On 2.3.1 responses authenticationMethod is returned from the scheme; on 2.1.0 and 2.2.0 we map authenticationType onto the nearest equivalent authenticationMethod.
cardholderInfoinformation about the cardholder.
challengeErrorReportingerror message sent or received by the ACS in case of error in the CReq/CRes messages
deviceBindingStatusto allow devices to be remembered as trusted
deviceBindingStatusSourcesource of device binding status
dsTransIDunique identifier (UUID) used by the Scheme for tracking the transaction throughout the 3DS process
transStatusReasonInfotransaction Status Reason Information

New values

These are changes in permitted values for existing fields on the Result Response.

FieldDescription of change
challengeCanceladditional values for 2.3.1
transStatusadditional values for 2.3.1
transStatusReasonadditional values for 2.3.1

Feedback