Checkout Three Ds Requestor Authentication Info Structure
ThreeDSRequestorAuthenticationInfo schema from Adyen API
Type: objectProperties: 3
PaymentsFinancial-ServicesFintech
ThreeDSRequestorAuthenticationInfo is a JSON Structure definition published by Adyen, describing 3 properties. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.
{
"$schema": "https://json-structure.org/meta/core/v0/#",
"$id": "https://raw.githubusercontent.com/api-evangelist/adyen/refs/heads/main/json-structure/checkout-three-ds-requestor-authentication-info-structure.json",
"description": "ThreeDSRequestorAuthenticationInfo schema from Adyen API",
"type": "object",
"properties": {
"threeDSReqAuthData": {
"description": "Data that documents and supports a specific authentication process. Maximum length: 2048 bytes.",
"type": "string"
},
"threeDSReqAuthMethod": {
"description": "Mechanism used by the Cardholder to authenticate to the 3DS Requestor. Allowed values:\n* **01** \u2014 No 3DS Requestor authentication occurred (for example, cardholder \u201clogged in\u201d as guest).\n* **02** \u2014 Login to the cardholder account at the 3DS Requestor system using 3DS Requestor\u2019s own credentials.\n* **03** \u2014 Login to the cardholder account at the 3DS Requestor system using federated ID.\n* **04** \u2014 Login to the cardholder account at the 3DS Requestor system using issuer credentials.\n* **05** \u2014 Login to the cardholder account at the 3DS Requestor system using third-party authentication.\n* **06** \u2014 Login to the cardholder account at the 3DS Requestor system using FIDO Authenticator.",
"enum": [
"01",
"02",
"03",
"04",
"05",
"06"
],
"maxLength": 2,
"minLength": 2,
"type": "string"
},
"threeDSReqAuthTimestamp": {
"description": "Date and time in UTC of the cardholder authentication. Format: YYYYMMDDHHMM",
"maxLength": 12,
"minLength": 12,
"type": "string"
}
},
"name": "ThreeDSRequestorAuthenticationInfo"
}
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.