From 51691a8f82fb2cf0c8e3202748949d9dc46c1cec Mon Sep 17 00:00:00 2001 From: Adyen Automation Date: Fri, 12 Aug 2022 11:57:03 +0000 Subject: [PATCH] spec release --- json/PaymentService-v25.json | 21 ++++++++++++++++++++- json/PaymentService-v30.json | 21 ++++++++++++++++++++- json/PaymentService-v40.json | 21 ++++++++++++++++++++- json/PaymentService-v46.json | 21 ++++++++++++++++++++- json/PaymentService-v49.json | 21 ++++++++++++++++++++- json/PaymentService-v50.json | 21 ++++++++++++++++++++- json/PaymentService-v51.json | 21 ++++++++++++++++++++- json/PaymentService-v52.json | 21 ++++++++++++++++++++- json/PaymentService-v64.json | 21 ++++++++++++++++++++- json/PaymentService-v67.json | 21 ++++++++++++++++++++- json/PaymentService-v68.json | 21 ++++++++++++++++++++- yaml/PaymentService-v25.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v30.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v40.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v46.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v49.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v50.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v51.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v52.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v64.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v67.yaml | 26 +++++++++++++++++++++++++- yaml/PaymentService-v68.yaml | 26 +++++++++++++++++++++++++- 22 files changed, 495 insertions(+), 22 deletions(-) diff --git a/json/PaymentService-v25.json b/json/PaymentService-v25.json index f0d36ef..836645d 100644 --- a/json/PaymentService-v25.json +++ b/json/PaymentService-v25.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v25/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:27Z", + "x-timestamp" : "2022-08-04T16:20:50Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -875,6 +875,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -1344,6 +1355,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v30.json b/json/PaymentService-v30.json index 1c63b7c..e4b80fa 100644 --- a/json/PaymentService-v30.json +++ b/json/PaymentService-v30.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v30/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:27Z", + "x-timestamp" : "2022-08-04T16:20:50Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1111,6 +1111,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -1580,6 +1591,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v40.json b/json/PaymentService-v40.json index 1e50790..814744a 100644 --- a/json/PaymentService-v40.json +++ b/json/PaymentService-v40.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v40/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:27Z", + "x-timestamp" : "2022-08-04T16:20:50Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1574,6 +1574,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -2043,6 +2054,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v46.json b/json/PaymentService-v46.json index 5c1c9da..13d23ad 100644 --- a/json/PaymentService-v46.json +++ b/json/PaymentService-v46.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v46/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:27Z", + "x-timestamp" : "2022-08-04T16:20:50Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1574,6 +1574,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -2043,6 +2054,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v49.json b/json/PaymentService-v49.json index 1450ab1..9db48e6 100644 --- a/json/PaymentService-v49.json +++ b/json/PaymentService-v49.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v49/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:28Z", + "x-timestamp" : "2022-08-04T16:20:50Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1574,6 +1574,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -2043,6 +2054,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v50.json b/json/PaymentService-v50.json index adb9a28..8653ae4 100644 --- a/json/PaymentService-v50.json +++ b/json/PaymentService-v50.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v50/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:28Z", + "x-timestamp" : "2022-08-04T16:20:51Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1584,6 +1584,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -2053,6 +2064,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v51.json b/json/PaymentService-v51.json index 56e8dfa..9f83561 100644 --- a/json/PaymentService-v51.json +++ b/json/PaymentService-v51.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v51/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:28Z", + "x-timestamp" : "2022-08-04T16:20:51Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1698,6 +1698,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -2167,6 +2178,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v52.json b/json/PaymentService-v52.json index 855f8cc..cc3ce09 100644 --- a/json/PaymentService-v52.json +++ b/json/PaymentService-v52.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v52/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:28Z", + "x-timestamp" : "2022-08-04T16:20:51Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1698,6 +1698,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -2167,6 +2178,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v64.json b/json/PaymentService-v64.json index a5afb2b..9d9fbc2 100644 --- a/json/PaymentService-v64.json +++ b/json/PaymentService-v64.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v64/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:28Z", + "x-timestamp" : "2022-08-04T16:20:51Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1698,6 +1698,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -2167,6 +2178,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v67.json b/json/PaymentService-v67.json index e3221d4..d8d81c0 100644 --- a/json/PaymentService-v67.json +++ b/json/PaymentService-v67.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v67/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:29Z", + "x-timestamp" : "2022-08-04T16:20:51Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1698,6 +1698,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -2167,6 +2178,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/json/PaymentService-v68.json b/json/PaymentService-v68.json index 2670286..fb0e9c1 100644 --- a/json/PaymentService-v68.json +++ b/json/PaymentService-v68.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Payment API", "description" : "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods.\n\nTo learn more about the API, visit [Classic integration](https://docs.adyen.com/classic-integration).\n\n## Authentication\nTo connect to the Payments API, you must use your basic authentication credentials. For this, create your web service user, as described in [How to get the WS user password](https://docs.adyen.com/development-resources/api-credentials). Then use its credentials to authenticate your request, for example:\n\n```\ncurl\n-U \"ws@Company.YourCompany\":\"YourWsPassword\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\nNote that when going live, you need to generate new web service user credentials to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).\n\n## Versioning\nPayments API supports [versioning](https://docs.adyen.com/development-resources/versioning) using a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.\n\nFor example:\n```\nhttps://pal-test.adyen.com/pal/servlet/Payment/v68/authorise\n```", - "x-timestamp" : "2022-05-06T17:19:29Z", + "x-timestamp" : "2022-08-04T16:20:51Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -1832,6 +1832,17 @@ "description" : "Indicates if you are able to process 3D Secure 2 transactions natively on your payment page. Send this parameter when you are using `/payments` endpoint with any of our [native 3D Secure 2 solutions](https://docs.adyen.com/online-payments/3d-secure/native-3ds2).\n\n > This parameter only indicates readiness to support native 3D Secure 2 authentication. To specify if you _want_ to perform 3D Secure, use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) or send the `executeThreeD` parameter.\n\nPossible values:\n* **true** - Ready to support native 3D Secure 2 authentication. Setting this to true does not mean always applying 3D Secure 2. Adyen still selects the version of 3D Secure based on configuration to optimize authorisation rates and improve the shopper's experience.\n* **false** – Not ready to support native 3D Secure 2 authentication. Adyen will not offer 3D Secure 2 to your shopper regardless of your configuration.\n", "type" : "string" }, + "challengeWindowSize" : { + "description" : "Dimensions of the 3DS2 challenge window to be displayed to the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n* **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size of 600x400\n* **05** - Fullscreen", + "enum" : [ + "01", + "02", + "03", + "04", + "05" + ], + "type" : "string" + }, "executeThreeD" : { "description" : "Indicates if you want to perform 3D Secure authentication on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure) to configure rules for applying 3D Secure.\n\nPossible values:\n* **true** – Perform 3D Secure authentication.\n* **false** – Don't perform 3D Secure authentication. Note that this setting results in refusals if the issuer mandates 3D Secure because of the PSD2 directive or other, national regulations. \n", "type" : "string" @@ -2301,6 +2312,14 @@ "description" : "The number of invoice lines included in `openinvoicedata`.\n\nThere needs to be at least one line, so `numberOfLines` needs to be at least 1.", "type" : "string" }, + "openinvoicedata.recipientFirstName" : { + "description" : "First name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, + "openinvoicedata.recipientLastName" : { + "description" : "Last name of the recipient. If the delivery address and the billing address are different, specify the `recipientFirstName` and `recipientLastName` to share the delivery address with Klarna. Otherwise, only the billing address is shared with Klarna.", + "type" : "string" + }, "openinvoicedataLine[itemNr].currencyCode" : { "description" : "The three-character ISO currency code.", "type" : "string" diff --git a/yaml/PaymentService-v25.yaml b/yaml/PaymentService-v25.yaml index f65e9ae..52bc81f 100644 --- a/yaml/PaymentService-v25.yaml +++ b/yaml/PaymentService-v25.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v25/authorise ```' - x-timestamp: '2022-05-06T17:19:27Z' + x-timestamp: '2022-08-04T16:20:50Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -664,6 +664,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -1616,6 +1628,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v30.yaml b/yaml/PaymentService-v30.yaml index c929e0c..7557e76 100644 --- a/yaml/PaymentService-v30.yaml +++ b/yaml/PaymentService-v30.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v30/authorise ```' - x-timestamp: '2022-05-06T17:19:27Z' + x-timestamp: '2022-08-04T16:20:50Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -826,6 +826,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -1778,6 +1790,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v40.yaml b/yaml/PaymentService-v40.yaml index 941dacc..c4558ab 100644 --- a/yaml/PaymentService-v40.yaml +++ b/yaml/PaymentService-v40.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v40/authorise ```' - x-timestamp: '2022-05-06T17:19:27Z' + x-timestamp: '2022-08-04T16:20:50Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -1202,6 +1202,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -2154,6 +2166,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v46.yaml b/yaml/PaymentService-v46.yaml index 9e9f66b..be1a59d 100644 --- a/yaml/PaymentService-v46.yaml +++ b/yaml/PaymentService-v46.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v46/authorise ```' - x-timestamp: '2022-05-06T17:19:27Z' + x-timestamp: '2022-08-04T16:20:50Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -1202,6 +1202,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -2154,6 +2166,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v49.yaml b/yaml/PaymentService-v49.yaml index 6c0da39..c0fb58b 100644 --- a/yaml/PaymentService-v49.yaml +++ b/yaml/PaymentService-v49.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v49/authorise ```' - x-timestamp: '2022-05-06T17:19:28Z' + x-timestamp: '2022-08-04T16:20:50Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -1202,6 +1202,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -2154,6 +2166,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v50.yaml b/yaml/PaymentService-v50.yaml index f6dac6f..4dfc537 100644 --- a/yaml/PaymentService-v50.yaml +++ b/yaml/PaymentService-v50.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v50/authorise ```' - x-timestamp: '2022-05-06T17:19:28Z' + x-timestamp: '2022-08-04T16:20:51Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -1219,6 +1219,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -2171,6 +2183,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v51.yaml b/yaml/PaymentService-v51.yaml index 4253643..0af11c7 100644 --- a/yaml/PaymentService-v51.yaml +++ b/yaml/PaymentService-v51.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v51/authorise ```' - x-timestamp: '2022-05-06T17:19:28Z' + x-timestamp: '2022-08-04T16:20:51Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -1287,6 +1287,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -2239,6 +2251,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v52.yaml b/yaml/PaymentService-v52.yaml index 22a65e7..5d00c7a 100644 --- a/yaml/PaymentService-v52.yaml +++ b/yaml/PaymentService-v52.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v52/authorise ```' - x-timestamp: '2022-05-06T17:19:28Z' + x-timestamp: '2022-08-04T16:20:51Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -1287,6 +1287,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -2239,6 +2251,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v64.yaml b/yaml/PaymentService-v64.yaml index b60a249..fef1708 100644 --- a/yaml/PaymentService-v64.yaml +++ b/yaml/PaymentService-v64.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v64/authorise ```' - x-timestamp: '2022-05-06T17:19:28Z' + x-timestamp: '2022-08-04T16:20:51Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -1287,6 +1287,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -2239,6 +2251,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v67.yaml b/yaml/PaymentService-v67.yaml index 9420e2a..792d61d 100644 --- a/yaml/PaymentService-v67.yaml +++ b/yaml/PaymentService-v67.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v67/authorise ```' - x-timestamp: '2022-05-06T17:19:29Z' + x-timestamp: '2022-08-04T16:20:51Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -1287,6 +1287,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -2239,6 +2251,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string diff --git a/yaml/PaymentService-v68.yaml b/yaml/PaymentService-v68.yaml index 1d5b386..14b75df 100644 --- a/yaml/PaymentService-v68.yaml +++ b/yaml/PaymentService-v68.yaml @@ -52,7 +52,7 @@ info: https://pal-test.adyen.com/pal/servlet/Payment/v68/authorise ```' - x-timestamp: '2022-05-06T17:19:29Z' + x-timestamp: '2022-08-04T16:20:51Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -1434,6 +1434,18 @@ components: \ to support native 3D Secure 2 authentication. Adyen will not offer 3D\ \ Secure 2 to your shopper regardless of your configuration.\n" type: string + challengeWindowSize: + description: "Dimensions of the 3DS2 challenge window to be displayed to\ + \ the cardholder.\n\nPossible values:\n\n* **01** - size of 250x400 \n\ + * **02** - size of 390x400\n* **03** - size of 500x600\n* **04** - size\ + \ of 600x400\n* **05** - Fullscreen" + enum: + - '01' + - '02' + - '03' + - '04' + - '05' + type: string executeThreeD: description: "Indicates if you want to perform 3D Secure authentication\ \ on a transaction.\n\n > Alternatively, you can use [Dynamic 3D Secure](/risk-management/dynamic-3d-secure)\ @@ -2386,6 +2398,18 @@ components: There needs to be at least one line, so `numberOfLines` needs to be at least 1.' type: string + openinvoicedata.recipientFirstName: + description: First name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string + openinvoicedata.recipientLastName: + description: Last name of the recipient. If the delivery address and the + billing address are different, specify the `recipientFirstName` and `recipientLastName` + to share the delivery address with Klarna. Otherwise, only the billing + address is shared with Klarna. + type: string openinvoicedataLine[itemNr].currencyCode: description: The three-character ISO currency code. type: string