mirror of
https://github.com/gcatanese/adyen-openapi.git
synced 2026-03-10 08:01:24 +00:00
spec release
This commit is contained in:
Adyen Automation
@@ -1130,7 +1130,7 @@
|
||||
"type" : "string"
|
||||
},
|
||||
"threeDSVersion" : {
|
||||
"description" : "Indicates your preference for the 3D Secure version. \n> If you use this parameter, you override the checks from Adyen's Authentication Engine. We recommend to use this field only if you have an extensive knowledge of 3D Secure.\n\nPossible values:\n* **1.0.2**: Apply 3D Secure version 1.0.2. \n* **2.1.0**: Apply 3D Secure version 2.1.0. \n* **2.2.0**: Apply 3D Secure version 2.2.0. If the issuer does not support version 2.2.0, we will fall back to 2.1.0.\n\nThe following rules apply:\n* If you prefer 2.1.0 or 2.2.0 but we receive a negative `transStatus` in the `ARes`, we will apply the fallback policy configured in your account. For example, if the configuration is to fall back to 3D Secure 1, we will apply version 1.0.2.\n* If you prefer 2.1.0 or 2.2.0 but the BIN is not enrolled, you will receive an error.\n\n",
|
||||
"description" : "Indicates your preference for the 3D Secure version. \n> If you use this parameter, you override the checks from Adyen's Authentication Engine. We recommend to use this field only if you have an extensive knowledge of 3D Secure.\n\nPossible values:\n* **2.1.0**: Apply 3D Secure version 2.1.0. \n* **2.2.0**: Apply 3D Secure version 2.2.0. If the issuer does not support version 2.2.0, we will fall back to 2.1.0.\n\nThe following rules apply:\n* If you prefer 2.1.0 or 2.2.0 but we receive a negative `transStatus` in the `ARes`, we will apply the fallback policy configured in your account.\n* If you the BIN is not enrolled, you will receive an error.\n\n",
|
||||
"type" : "string"
|
||||
}
|
||||
},
|
||||
@@ -2904,7 +2904,7 @@
|
||||
"$ref" : "#/components/schemas/Address"
|
||||
},
|
||||
"browserInfo" : {
|
||||
"description" : "The shopper's browser information.\n> For 3D Secure, the full object is required for web integrations. For mobile app integrations, include the `userAgent` and `acceptHeader` fields to indicate that your integration can support a redirect in case a payment is routed to 3D Secure 1.",
|
||||
"description" : "The shopper's browser information.\n> For 3D Secure, the full object is required for web integrations. For mobile app integrations, include the `userAgent` and `acceptHeader` fields to indicate that your integration can support a redirect in case a payment is routed to 3D Secure 2 redirect.",
|
||||
"$ref" : "#/components/schemas/BrowserInfo"
|
||||
},
|
||||
"captureDelayHours" : {
|
||||
@@ -3061,7 +3061,7 @@
|
||||
"$ref" : "#/components/schemas/Name"
|
||||
},
|
||||
"shopperReference" : {
|
||||
"description" : "Required for recurring payments. \nYour reference to uniquely identify this shopper, for example user ID or account ID. Minimum length: 3 characters.\n> Your reference must not include personally identifiable information (PII), for example name or email address.",
|
||||
"description" : "Required for recurring payments. \nYour reference to uniquely identify this shopper, for example user ID or account ID. The value is case-sensitive and must be at least three characters.\n> Your reference must not include personally identifiable information (PII) such as name or email address.",
|
||||
"type" : "string"
|
||||
},
|
||||
"shopperStatement" : {
|
||||
@@ -3171,7 +3171,7 @@
|
||||
"$ref" : "#/components/schemas/Address"
|
||||
},
|
||||
"browserInfo" : {
|
||||
"description" : "The shopper's browser information.\n> For 3D Secure, the full object is required for web integrations. For mobile app integrations, include the `userAgent` and `acceptHeader` fields to indicate that your integration can support a redirect in case a payment is routed to 3D Secure 1.",
|
||||
"description" : "The shopper's browser information.\n> For 3D Secure, the full object is required for web integrations. For mobile app integrations, include the `userAgent` and `acceptHeader` fields to indicate that your integration can support a redirect in case a payment is routed to 3D Secure 2 redirect.",
|
||||
"$ref" : "#/components/schemas/BrowserInfo"
|
||||
},
|
||||
"captureDelayHours" : {
|
||||
@@ -3309,7 +3309,7 @@
|
||||
"$ref" : "#/components/schemas/Name"
|
||||
},
|
||||
"shopperReference" : {
|
||||
"description" : "Required for recurring payments. \nYour reference to uniquely identify this shopper, for example user ID or account ID. Minimum length: 3 characters.\n> Your reference must not include personally identifiable information (PII), for example name or email address.",
|
||||
"description" : "Required for recurring payments. \nYour reference to uniquely identify this shopper, for example user ID or account ID. The value is case-sensitive and must be at least three characters.\n> Your reference must not include personally identifiable information (PII) such as name or email address.",
|
||||
"type" : "string"
|
||||
},
|
||||
"shopperStatement" : {
|
||||
@@ -3920,12 +3920,29 @@
|
||||
"description" : "The 3D Secure 2 version.",
|
||||
"type" : "string"
|
||||
},
|
||||
"tokenization.shopperReference" : {
|
||||
"description" : "The provided reference of the shopper.",
|
||||
"type" : "string"
|
||||
},
|
||||
"tokenization.store.operationType" : {
|
||||
"description" : "The store operation performed on the token.",
|
||||
"enum" : [
|
||||
"created",
|
||||
"updated",
|
||||
"alreadyStored"
|
||||
],
|
||||
"type" : "string"
|
||||
},
|
||||
"tokenization.storedPaymentMethodId" : {
|
||||
"description" : "The reference that uniquely identifies tokenized payment details.",
|
||||
"type" : "string"
|
||||
},
|
||||
"visaTransactionId" : {
|
||||
"description" : "The `visaTransactionId`, has a fixed length of 15 numeric characters.\n\n> Contact Support Team to enable this field.",
|
||||
"type" : "string"
|
||||
},
|
||||
"xid" : {
|
||||
"description" : "The 3DS transaction ID of the 3DS session sent in notifications. The value is Base64-encoded and is returned for transactions with directoryResponse 'N' or 'Y'. If you want to submit the xid in your 3D Secure 1 request, use the `mpiData.xid`, field.\n\nExample: ODgxNDc2MDg2MDExODk5MAAAAAA=",
|
||||
"description" : "The 3DS transaction ID of the 3DS session sent in notifications. The value is Base64-encoded and is returned for transactions with directoryResponse 'N' or 'Y'. \n\nExample: ODgxNDc2MDg2MDExODk5MAAAAAA=",
|
||||
"type" : "string"
|
||||
}
|
||||
},
|
||||
@@ -4170,7 +4187,7 @@
|
||||
"additionalProperties" : false,
|
||||
"properties" : {
|
||||
"authenticationResponse" : {
|
||||
"description" : "In 3D Secure 1, the authentication response if the shopper was redirected.\n\nIn 3D Secure 2, this is the `transStatus` from the challenge result. If the transaction was frictionless, omit this parameter.",
|
||||
"description" : "In 3D Secure 2, this is the `transStatus` from the challenge result. If the transaction was frictionless, omit this parameter.\n\n",
|
||||
"enum" : [
|
||||
"Y",
|
||||
"N",
|
||||
@@ -4189,7 +4206,7 @@
|
||||
"type" : "string"
|
||||
},
|
||||
"directoryResponse" : {
|
||||
"description" : "In 3D Secure 1, this is the enrollment response from the 3D directory server.\n\nIn 3D Secure 2, this is the `transStatus` from the `ARes`.",
|
||||
"description" : "In 3D Secure 2, this is the `transStatus` from the `ARes`.\n\n",
|
||||
"enum" : [
|
||||
"A",
|
||||
"C",
|
||||
|
||||
Reference in New Issue
Block a user