From 804442c9fcd9130423b64da43110a04a8105a71d Mon Sep 17 00:00:00 2001 From: Adyen Automation Date: Fri, 10 Feb 2023 10:18:56 +0000 Subject: [PATCH] spec release --- json/BinLookupService-v40.json | 2 +- json/BinLookupService-v50.json | 2 +- json/BinLookupService-v52.json | 2 +- json/BinLookupService-v53.json | 2 +- json/BinLookupService-v54.json | 2 +- json/CheckoutService-v37.json | 3 +-- json/CheckoutService-v40.json | 3 +-- json/CheckoutService-v41.json | 3 +-- json/CheckoutService-v46.json | 3 +-- json/CheckoutService-v49.json | 3 +-- json/CheckoutService-v50.json | 3 +-- json/CheckoutService-v51.json | 3 +-- json/CheckoutService-v52.json | 3 +-- json/CheckoutService-v53.json | 3 +-- json/CheckoutService-v64.json | 3 +-- json/CheckoutService-v65.json | 3 +-- json/CheckoutService-v66.json | 3 +-- json/CheckoutService-v67.json | 3 +-- json/CheckoutService-v68.json | 29 ++++++++++++++++--------- json/CheckoutService-v69.json | 17 ++++----------- json/CheckoutService-v70.json | 17 ++++----------- json/StoredValueService-v46.json | 10 ++++----- yaml/BinLookupService-v40.yaml | 2 +- yaml/BinLookupService-v50.yaml | 2 +- yaml/BinLookupService-v52.yaml | 2 +- yaml/BinLookupService-v53.yaml | 2 +- yaml/BinLookupService-v54.yaml | 2 +- yaml/CheckoutService-v37.yaml | 3 +-- yaml/CheckoutService-v40.yaml | 3 +-- yaml/CheckoutService-v41.yaml | 3 +-- yaml/CheckoutService-v46.yaml | 3 +-- yaml/CheckoutService-v49.yaml | 3 +-- yaml/CheckoutService-v50.yaml | 3 +-- yaml/CheckoutService-v51.yaml | 3 +-- yaml/CheckoutService-v52.yaml | 3 +-- yaml/CheckoutService-v53.yaml | 3 +-- yaml/CheckoutService-v64.yaml | 3 +-- yaml/CheckoutService-v65.yaml | 3 +-- yaml/CheckoutService-v66.yaml | 3 +-- yaml/CheckoutService-v67.yaml | 3 +-- yaml/CheckoutService-v68.yaml | 37 ++++++++++++-------------------- yaml/CheckoutService-v69.yaml | 30 ++++---------------------- yaml/CheckoutService-v70.yaml | 30 ++++---------------------- yaml/StoredValueService-v46.yaml | 10 ++++----- 44 files changed, 95 insertions(+), 183 deletions(-) diff --git a/json/BinLookupService-v40.json b/json/BinLookupService-v40.json index 4dcc9ed..5172adc 100644 --- a/json/BinLookupService-v40.json +++ b/json/BinLookupService-v40.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen BinLookup API", "description" : "The BIN Lookup API provides endpoints for retrieving information, such as cost estimates, and 3D Secure supported version based on a given BIN.\n\n## Authentication\nYou need an [API credential](https://docs.adyen.com/development-resources/api-credentials) to authenticate to the API.\n\nIf using an API key, add an `X-API-Key` header with the API key as the value, for example:\n\n ```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n\nAlternatively, you can use the username and password to connect to the API using basic authentication, for example:\n\n```\ncurl\n-U \"ws@Company.YOUR_COMPANY_ACCOUNT\":\"YOUR_BASIC_AUTHENTICATION_PASSWORD\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\n\n## Versioning\nThe BinLookup 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/BinLookup/v40/get3dsAvailability\n```## Going live\n\nTo authneticate to the live endpoints, you need an [API credential](https://docs.adyen.com/development-resources/api-credentials) from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v40/get3dsAvailability\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.", - "x-timestamp" : "2022-11-24T10:17:09Z", + "x-timestamp" : "2023-02-09T20:21:24Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", diff --git a/json/BinLookupService-v50.json b/json/BinLookupService-v50.json index 3295248..92c8785 100644 --- a/json/BinLookupService-v50.json +++ b/json/BinLookupService-v50.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen BinLookup API", "description" : "The BIN Lookup API provides endpoints for retrieving information, such as cost estimates, and 3D Secure supported version based on a given BIN.\n\n## Authentication\nYou need an [API credential](https://docs.adyen.com/development-resources/api-credentials) to authenticate to the API.\n\nIf using an API key, add an `X-API-Key` header with the API key as the value, for example:\n\n ```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n\nAlternatively, you can use the username and password to connect to the API using basic authentication, for example:\n\n```\ncurl\n-U \"ws@Company.YOUR_COMPANY_ACCOUNT\":\"YOUR_BASIC_AUTHENTICATION_PASSWORD\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\n\n## Versioning\nThe BinLookup 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/BinLookup/v50/get3dsAvailability\n```## Going live\n\nTo authneticate to the live endpoints, you need an [API credential](https://docs.adyen.com/development-resources/api-credentials) from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v50/get3dsAvailability\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.", - "x-timestamp" : "2022-11-24T10:17:09Z", + "x-timestamp" : "2023-02-09T20:21:25Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", diff --git a/json/BinLookupService-v52.json b/json/BinLookupService-v52.json index 4ecbf48..bf346c4 100644 --- a/json/BinLookupService-v52.json +++ b/json/BinLookupService-v52.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen BinLookup API", "description" : "The BIN Lookup API provides endpoints for retrieving information, such as cost estimates, and 3D Secure supported version based on a given BIN.\n\n## Authentication\nYou need an [API credential](https://docs.adyen.com/development-resources/api-credentials) to authenticate to the API.\n\nIf using an API key, add an `X-API-Key` header with the API key as the value, for example:\n\n ```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n\nAlternatively, you can use the username and password to connect to the API using basic authentication, for example:\n\n```\ncurl\n-U \"ws@Company.YOUR_COMPANY_ACCOUNT\":\"YOUR_BASIC_AUTHENTICATION_PASSWORD\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\n\n## Versioning\nThe BinLookup 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/BinLookup/v52/get3dsAvailability\n```## Going live\n\nTo authneticate to the live endpoints, you need an [API credential](https://docs.adyen.com/development-resources/api-credentials) from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v52/get3dsAvailability\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.", - "x-timestamp" : "2022-11-24T10:17:10Z", + "x-timestamp" : "2023-02-09T20:21:25Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", diff --git a/json/BinLookupService-v53.json b/json/BinLookupService-v53.json index b9d7250..30b0323 100644 --- a/json/BinLookupService-v53.json +++ b/json/BinLookupService-v53.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen BinLookup API", "description" : "The BIN Lookup API provides endpoints for retrieving information, such as cost estimates, and 3D Secure supported version based on a given BIN.\n\n## Authentication\nYou need an [API credential](https://docs.adyen.com/development-resources/api-credentials) to authenticate to the API.\n\nIf using an API key, add an `X-API-Key` header with the API key as the value, for example:\n\n ```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n\nAlternatively, you can use the username and password to connect to the API using basic authentication, for example:\n\n```\ncurl\n-U \"ws@Company.YOUR_COMPANY_ACCOUNT\":\"YOUR_BASIC_AUTHENTICATION_PASSWORD\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\n\n## Versioning\nThe BinLookup 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/BinLookup/v53/get3dsAvailability\n```## Going live\n\nTo authneticate to the live endpoints, you need an [API credential](https://docs.adyen.com/development-resources/api-credentials) from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v53/get3dsAvailability\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.", - "x-timestamp" : "2022-11-24T10:17:10Z", + "x-timestamp" : "2023-02-09T20:21:25Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", diff --git a/json/BinLookupService-v54.json b/json/BinLookupService-v54.json index 27f5f5e..11fdcd7 100644 --- a/json/BinLookupService-v54.json +++ b/json/BinLookupService-v54.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen BinLookup API", "description" : "The BIN Lookup API provides endpoints for retrieving information, such as cost estimates, and 3D Secure supported version based on a given BIN.\n\n## Authentication\nYou need an [API credential](https://docs.adyen.com/development-resources/api-credentials) to authenticate to the API.\n\nIf using an API key, add an `X-API-Key` header with the API key as the value, for example:\n\n ```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n\nAlternatively, you can use the username and password to connect to the API using basic authentication, for example:\n\n```\ncurl\n-U \"ws@Company.YOUR_COMPANY_ACCOUNT\":\"YOUR_BASIC_AUTHENTICATION_PASSWORD\" \\\n-H \"Content-Type: application/json\" \\\n...\n```\n\n## Versioning\nThe BinLookup 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/BinLookup/v54/get3dsAvailability\n```## Going live\n\nTo authneticate to the live endpoints, you need an [API credential](https://docs.adyen.com/development-resources/api-credentials) from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v54/get3dsAvailability\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.", - "x-timestamp" : "2022-11-24T10:17:10Z", + "x-timestamp" : "2023-02-09T20:21:25Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", diff --git a/json/CheckoutService-v37.json b/json/CheckoutService-v37.json index 739e010..1fe5535 100644 --- a/json/CheckoutService-v37.json +++ b/json/CheckoutService-v37.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v37/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v37/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=37) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:55Z", + "x-timestamp" : "2023-02-08T17:21:12Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -6601,7 +6601,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v40.json b/json/CheckoutService-v40.json index 96b56c3..8daa8e9 100644 --- a/json/CheckoutService-v40.json +++ b/json/CheckoutService-v40.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v40/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v40/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=40) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:56Z", + "x-timestamp" : "2023-02-08T17:21:14Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -6914,7 +6914,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v41.json b/json/CheckoutService-v41.json index debc97a..e6d1069 100644 --- a/json/CheckoutService-v41.json +++ b/json/CheckoutService-v41.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v41/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v41/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=41) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:57Z", + "x-timestamp" : "2023-02-08T17:21:14Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -6929,7 +6929,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v46.json b/json/CheckoutService-v46.json index 95dc8a9..edefbd1 100644 --- a/json/CheckoutService-v46.json +++ b/json/CheckoutService-v46.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v46/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v46/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=46) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:57Z", + "x-timestamp" : "2023-02-08T17:21:15Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -6929,7 +6929,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v49.json b/json/CheckoutService-v49.json index 684141d..22064dc 100644 --- a/json/CheckoutService-v49.json +++ b/json/CheckoutService-v49.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v49/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v49/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=49) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:57Z", + "x-timestamp" : "2023-02-08T17:21:15Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -7333,7 +7333,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v50.json b/json/CheckoutService-v50.json index c12b02e..b039459 100644 --- a/json/CheckoutService-v50.json +++ b/json/CheckoutService-v50.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v50/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v50/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=50) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:58Z", + "x-timestamp" : "2023-02-08T17:21:16Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -7360,7 +7360,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v51.json b/json/CheckoutService-v51.json index 57d9f45..fee52c5 100644 --- a/json/CheckoutService-v51.json +++ b/json/CheckoutService-v51.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v51/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v51/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=51) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:58Z", + "x-timestamp" : "2023-02-08T17:21:16Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -7357,7 +7357,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v52.json b/json/CheckoutService-v52.json index 16e82d9..525be24 100644 --- a/json/CheckoutService-v52.json +++ b/json/CheckoutService-v52.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v52/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v52/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=52) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:59Z", + "x-timestamp" : "2023-02-08T17:21:16Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -7357,7 +7357,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v53.json b/json/CheckoutService-v53.json index 998ce15..fd3f9d6 100644 --- a/json/CheckoutService-v53.json +++ b/json/CheckoutService-v53.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v53/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v53/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=53) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:59Z", + "x-timestamp" : "2023-02-08T17:21:17Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -7357,7 +7357,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v64.json b/json/CheckoutService-v64.json index 85dc9a0..70ff1f9 100644 --- a/json/CheckoutService-v64.json +++ b/json/CheckoutService-v64.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v64/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v64/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=64) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:25:59Z", + "x-timestamp" : "2023-02-08T17:21:17Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -7393,7 +7393,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v65.json b/json/CheckoutService-v65.json index d3d9e4f..18d70f4 100644 --- a/json/CheckoutService-v65.json +++ b/json/CheckoutService-v65.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v65/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v65/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=65) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:26:00Z", + "x-timestamp" : "2023-02-08T17:21:17Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -7412,7 +7412,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v66.json b/json/CheckoutService-v66.json index 0b0320e..81ac594 100644 --- a/json/CheckoutService-v66.json +++ b/json/CheckoutService-v66.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v66/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v66/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=66) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:26:00Z", + "x-timestamp" : "2023-02-08T17:21:18Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -7412,7 +7412,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v67.json b/json/CheckoutService-v67.json index 9c33eaa..bdd05c8 100644 --- a/json/CheckoutService-v67.json +++ b/json/CheckoutService-v67.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v67/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v67/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=67) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:26:00Z", + "x-timestamp" : "2023-02-08T17:21:18Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -7401,7 +7401,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", diff --git a/json/CheckoutService-v68.json b/json/CheckoutService-v68.json index 0dc4005..5213d56 100644 --- a/json/CheckoutService-v68.json +++ b/json/CheckoutService-v68.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v68/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v68/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=68) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:26:01Z", + "x-timestamp" : "2023-02-09T12:22:11Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -8510,7 +8510,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", @@ -9042,6 +9041,11 @@ } ] }, + "platformChargebackLogic" : { + "x-addedInVersion" : "68", + "description" : "Defines the behavior to be applied in case of a chargeback.", + "$ref" : "#/components/schemas/PlatformChargebackLogic" + }, "recurringExpiry" : { "description" : "Date after which no further authorisations shall be performed. Only for 3D Secure 2.", "type" : "string" @@ -9599,14 +9603,6 @@ "description" : "The shopper's country code.", "type" : "string" }, - "localizedShopperStatement" : { - "x-addedInVersion" : "68", - "additionalProperties" : { - "type" : "string" - }, - "description" : "This field allows merchants to use dynamic shopper statement in local character sets.\nThe local shopper statement field can be supplied in markets where localized merchant descriptors are used. Currently, Adyen only supports this in the Japanese market\n.The available character sets at the moment are:\n* Processing in Japan: **ja-Kana**\nThe character set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special characters.\nMerchants should send the Katakana shopperStatement in full-width characters. \nAn example request would be:\n> {\n \"shopperStatement\" : \"ADYEN - SELLER-A\",\n \"localizedShopperStatement\" : {\n \"ja-Kana\" : \"ADYEN - セラーA\"\n }\n}\nWe recommend merchants to always supply the field localizedShopperStatement in addition to the field shopperStatement.It is issuer dependent whether the localized shopper statement field is supported.\nIn the case of non-domestic transactions (e.g. US-issued cards processed in JP) the field `shopperStatement` is used to modify the statement of the shopper.\nAdyen handles the complexity of ensuring the correct descriptors are assigned.", - "type" : "object" - }, "merchantAccount" : { "description" : "The merchant account identifier, with which you want to process the transaction.", "type" : "string" @@ -10085,6 +10081,11 @@ } ] }, + "platformChargebackLogic" : { + "x-addedInVersion" : "68", + "description" : "Defines the behavior to be applied in case of a chargeback.", + "$ref" : "#/components/schemas/PlatformChargebackLogic" + }, "recurringExpiry" : { "description" : "Date after which no further authorisations shall be performed. Only for 3D Secure 2.", "type" : "string" @@ -10613,6 +10614,11 @@ "description" : "Required for the Web integration.\n\nSet this parameter to the origin URL of the page that you are loading the SDK from.", "type" : "string" }, + "platformChargebackLogic" : { + "x-addedInVersion" : "68", + "description" : "Defines the behavior to be applied in case of a chargeback.", + "$ref" : "#/components/schemas/PlatformChargebackLogic" + }, "recurringExpiry" : { "description" : "Date after which no further authorisations shall be performed. Only for 3D Secure 2.", "type" : "string" @@ -10873,6 +10879,9 @@ "type" : "string" } } + }, + "PlatformChargebackLogic" : { + }, "RatepayDetails" : { "additionalProperties" : false, diff --git a/json/CheckoutService-v69.json b/json/CheckoutService-v69.json index 92d3ba3..fd75ebe 100644 --- a/json/CheckoutService-v69.json +++ b/json/CheckoutService-v69.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v69/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v69/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=69) to find out what changed in this version!", - "x-timestamp" : "2023-02-06T16:26:01Z", + "x-timestamp" : "2023-02-09T12:22:12Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -8619,7 +8619,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", @@ -9162,7 +9161,7 @@ ] }, "platformChargebackLogic" : { - "x-addedInVersion" : "69", + "x-addedInVersion" : "68", "description" : "Defines the behavior to be applied in case of a chargeback.", "$ref" : "#/components/schemas/PlatformChargebackLogic" }, @@ -9759,14 +9758,6 @@ "description" : "The shopper's country code.", "type" : "string" }, - "localizedShopperStatement" : { - "x-addedInVersion" : "68", - "additionalProperties" : { - "type" : "string" - }, - "description" : "This field allows merchants to use dynamic shopper statement in local character sets.\nThe local shopper statement field can be supplied in markets where localized merchant descriptors are used. Currently, Adyen only supports this in the Japanese market\n.The available character sets at the moment are:\n* Processing in Japan: **ja-Kana**\nThe character set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special characters.\nMerchants should send the Katakana shopperStatement in full-width characters. \nAn example request would be:\n> {\n \"shopperStatement\" : \"ADYEN - SELLER-A\",\n \"localizedShopperStatement\" : {\n \"ja-Kana\" : \"ADYEN - セラーA\"\n }\n}\nWe recommend merchants to always supply the field localizedShopperStatement in addition to the field shopperStatement.It is issuer dependent whether the localized shopper statement field is supported.\nIn the case of non-domestic transactions (e.g. US-issued cards processed in JP) the field `shopperStatement` is used to modify the statement of the shopper.\nAdyen handles the complexity of ensuring the correct descriptors are assigned.", - "type" : "object" - }, "merchantAccount" : { "description" : "The merchant account identifier, with which you want to process the transaction.", "type" : "string" @@ -10251,7 +10242,7 @@ ] }, "platformChargebackLogic" : { - "x-addedInVersion" : "69", + "x-addedInVersion" : "68", "description" : "Defines the behavior to be applied in case of a chargeback.", "$ref" : "#/components/schemas/PlatformChargebackLogic" }, @@ -10792,7 +10783,7 @@ "type" : "string" }, "platformChargebackLogic" : { - "x-addedInVersion" : "69", + "x-addedInVersion" : "68", "description" : "Defines the behavior to be applied in case of a chargeback.", "$ref" : "#/components/schemas/PlatformChargebackLogic" }, diff --git a/json/CheckoutService-v70.json b/json/CheckoutService-v70.json index 4bda38d..c36a226 100644 --- a/json/CheckoutService-v70.json +++ b/json/CheckoutService-v70.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Checkout API", "description" : "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).\n\nThis API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [online payments documentation](https://docs.adyen.com/online-payments).\n\n## Authentication\nEach request to Checkout API must be signed with an API key. For this, [get your API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key) from your Customer Area, and set this key to the `X-API-Key` header value, for example:\n\n```\ncurl\n-H \"Content-Type: application/json\" \\\n-H \"X-API-Key: YOUR_API_KEY\" \\\n...\n```\n## Versioning\nCheckout 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://checkout-test.adyen.com/v70/payments\n```\n\n## Going live\n\nTo access the live endpoints, you need an API key from your live Customer Area.\n\nThe live endpoint URLs contain a prefix which is unique to your company account, for example:\n```\nhttps://{PREFIX}-checkout-live.adyenpayments.com/checkout/v70/payments\n```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** > **API URLs** > **Prefix**.\n\nWhen preparing to do live transactions with Checkout API, follow the [go-live checklist](https://docs.adyen.com/online-payments/go-live-checklist) to make sure you've got all the required configuration in place.\n\n## Release notes\nHave a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=70) to find out what changed in this version!", - "x-timestamp" : "2023-02-07T12:23:34Z", + "x-timestamp" : "2023-02-09T12:22:12Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -8828,7 +8828,6 @@ "dana", "paysafecard", "cashticket", - "isracard", "ikano", "karenmillen", "oasis", @@ -9381,7 +9380,7 @@ ] }, "platformChargebackLogic" : { - "x-addedInVersion" : "69", + "x-addedInVersion" : "68", "description" : "Defines the behavior to be applied in case of a chargeback.", "$ref" : "#/components/schemas/PlatformChargebackLogic" }, @@ -9974,14 +9973,6 @@ "description" : "The shopper's country code.", "type" : "string" }, - "localizedShopperStatement" : { - "x-addedInVersion" : "68", - "additionalProperties" : { - "type" : "string" - }, - "description" : "This field allows merchants to use dynamic shopper statement in local character sets.\nThe local shopper statement field can be supplied in markets where localized merchant descriptors are used. Currently, Adyen only supports this in the Japanese market\n.The available character sets at the moment are:\n* Processing in Japan: **ja-Kana**\nThe character set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special characters.\nMerchants should send the Katakana shopperStatement in full-width characters. \nAn example request would be:\n> {\n \"shopperStatement\" : \"ADYEN - SELLER-A\",\n \"localizedShopperStatement\" : {\n \"ja-Kana\" : \"ADYEN - セラーA\"\n }\n}\nWe recommend merchants to always supply the field localizedShopperStatement in addition to the field shopperStatement.It is issuer dependent whether the localized shopper statement field is supported.\nIn the case of non-domestic transactions (e.g. US-issued cards processed in JP) the field `shopperStatement` is used to modify the statement of the shopper.\nAdyen handles the complexity of ensuring the correct descriptors are assigned.", - "type" : "object" - }, "merchantAccount" : { "description" : "The merchant account identifier, with which you want to process the transaction.", "type" : "string" @@ -10476,7 +10467,7 @@ ] }, "platformChargebackLogic" : { - "x-addedInVersion" : "69", + "x-addedInVersion" : "68", "description" : "Defines the behavior to be applied in case of a chargeback.", "$ref" : "#/components/schemas/PlatformChargebackLogic" }, @@ -11017,7 +11008,7 @@ "type" : "string" }, "platformChargebackLogic" : { - "x-addedInVersion" : "69", + "x-addedInVersion" : "68", "description" : "Defines the behavior to be applied in case of a chargeback.", "$ref" : "#/components/schemas/PlatformChargebackLogic" }, diff --git a/json/StoredValueService-v46.json b/json/StoredValueService-v46.json index 37b5dd6..4a5ad0f 100644 --- a/json/StoredValueService-v46.json +++ b/json/StoredValueService-v46.json @@ -10,7 +10,7 @@ "x-publicVersion" : true, "title" : "Adyen Stored Value API", "description" : "A set of API endpoints to manage stored value products.", - "x-timestamp" : "2022-11-24T10:17:10Z", + "x-timestamp" : "2023-02-09T20:21:26Z", "termsOfService" : "https://www.adyen.com/legal/terms-and-conditions", "contact" : { "name" : "Adyen Developer Experience team", @@ -37,7 +37,7 @@ "operationId" : "post-changeStatus", "x-groupName" : "General", "x-sortIndex" : 0, - "x-methodName" : "changesTheStatusOfThePaymentMethod", + "x-methodName" : "changesStatusOfPaymentMethod", "security" : [ { "BasicAuth" : [ @@ -121,7 +121,7 @@ "operationId" : "post-checkBalance", "x-groupName" : "General", "x-sortIndex" : 0, - "x-methodName" : "checksTheBalance", + "x-methodName" : "checksBalance", "security" : [ { "BasicAuth" : [ @@ -289,7 +289,7 @@ "operationId" : "post-load", "x-groupName" : "General", "x-sortIndex" : 0, - "x-methodName" : "loadsThePaymentMethod", + "x-methodName" : "loadsPaymentMethod", "security" : [ { "BasicAuth" : [ @@ -373,7 +373,7 @@ "operationId" : "post-mergeBalance", "x-groupName" : "General", "x-sortIndex" : 0, - "x-methodName" : "mergeTheBalanceOfTwoCards", + "x-methodName" : "mergeBalanceOfTwoCards", "security" : [ { "BasicAuth" : [ diff --git a/yaml/BinLookupService-v40.yaml b/yaml/BinLookupService-v40.yaml index e5f385a..f7f4a28 100644 --- a/yaml/BinLookupService-v40.yaml +++ b/yaml/BinLookupService-v40.yaml @@ -22,7 +22,7 @@ info: \ is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v40/get3dsAvailability\n\ ```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** >\ \ **API URLs** > **Prefix**." - x-timestamp: '2022-11-24T10:17:09Z' + x-timestamp: '2023-02-09T20:21:24Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team diff --git a/yaml/BinLookupService-v50.yaml b/yaml/BinLookupService-v50.yaml index ba6e456..09a15d2 100644 --- a/yaml/BinLookupService-v50.yaml +++ b/yaml/BinLookupService-v50.yaml @@ -22,7 +22,7 @@ info: \ is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v50/get3dsAvailability\n\ ```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** >\ \ **API URLs** > **Prefix**." - x-timestamp: '2022-11-24T10:17:09Z' + x-timestamp: '2023-02-09T20:21:25Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team diff --git a/yaml/BinLookupService-v52.yaml b/yaml/BinLookupService-v52.yaml index 8b24714..57c511e 100644 --- a/yaml/BinLookupService-v52.yaml +++ b/yaml/BinLookupService-v52.yaml @@ -22,7 +22,7 @@ info: \ is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v52/get3dsAvailability\n\ ```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** >\ \ **API URLs** > **Prefix**." - x-timestamp: '2022-11-24T10:17:10Z' + x-timestamp: '2023-02-09T20:21:25Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team diff --git a/yaml/BinLookupService-v53.yaml b/yaml/BinLookupService-v53.yaml index fb2c71f..8a0324f 100644 --- a/yaml/BinLookupService-v53.yaml +++ b/yaml/BinLookupService-v53.yaml @@ -22,7 +22,7 @@ info: \ is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v53/get3dsAvailability\n\ ```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** >\ \ **API URLs** > **Prefix**." - x-timestamp: '2022-11-24T10:17:10Z' + x-timestamp: '2023-02-09T20:21:25Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team diff --git a/yaml/BinLookupService-v54.yaml b/yaml/BinLookupService-v54.yaml index a074692..e700b2f 100644 --- a/yaml/BinLookupService-v54.yaml +++ b/yaml/BinLookupService-v54.yaml @@ -22,7 +22,7 @@ info: \ is unique to your company account:\n```\n\nhttps://{PREFIX}-pal-live.adyenpayments.com/pal/servlet/BinLookup/v54/get3dsAvailability\n\ ```\n\nGet your `{PREFIX}` from your live Customer Area under **Developers** >\ \ **API URLs** > **Prefix**." - x-timestamp: '2022-11-24T10:17:10Z' + x-timestamp: '2023-02-09T20:21:25Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team diff --git a/yaml/CheckoutService-v37.yaml b/yaml/CheckoutService-v37.yaml index a2a6310..c9bb1a0 100644 --- a/yaml/CheckoutService-v37.yaml +++ b/yaml/CheckoutService-v37.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=37) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:55Z' + x-timestamp: '2023-02-08T17:21:12Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -5868,7 +5868,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v40.yaml b/yaml/CheckoutService-v40.yaml index b2b5b01..1b9756e 100644 --- a/yaml/CheckoutService-v40.yaml +++ b/yaml/CheckoutService-v40.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=40) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:56Z' + x-timestamp: '2023-02-08T17:21:14Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6245,7 +6245,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v41.yaml b/yaml/CheckoutService-v41.yaml index 89488d0..2089173 100644 --- a/yaml/CheckoutService-v41.yaml +++ b/yaml/CheckoutService-v41.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=41) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:57Z' + x-timestamp: '2023-02-08T17:21:14Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6255,7 +6255,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v46.yaml b/yaml/CheckoutService-v46.yaml index 8a60e3a..31fbd93 100644 --- a/yaml/CheckoutService-v46.yaml +++ b/yaml/CheckoutService-v46.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=46) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:57Z' + x-timestamp: '2023-02-08T17:21:15Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6255,7 +6255,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v49.yaml b/yaml/CheckoutService-v49.yaml index 068a0cc..31c9b4e 100644 --- a/yaml/CheckoutService-v49.yaml +++ b/yaml/CheckoutService-v49.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=49) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:57Z' + x-timestamp: '2023-02-08T17:21:15Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6589,7 +6589,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v50.yaml b/yaml/CheckoutService-v50.yaml index a82371c..5a25d1f 100644 --- a/yaml/CheckoutService-v50.yaml +++ b/yaml/CheckoutService-v50.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=50) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:58Z' + x-timestamp: '2023-02-08T17:21:16Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6621,7 +6621,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v51.yaml b/yaml/CheckoutService-v51.yaml index d918c79..7d28a05 100644 --- a/yaml/CheckoutService-v51.yaml +++ b/yaml/CheckoutService-v51.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=51) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:58Z' + x-timestamp: '2023-02-08T17:21:16Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6621,7 +6621,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v52.yaml b/yaml/CheckoutService-v52.yaml index a091460..ac55f29 100644 --- a/yaml/CheckoutService-v52.yaml +++ b/yaml/CheckoutService-v52.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=52) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:59Z' + x-timestamp: '2023-02-08T17:21:16Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6621,7 +6621,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v53.yaml b/yaml/CheckoutService-v53.yaml index 82a9671..000981e 100644 --- a/yaml/CheckoutService-v53.yaml +++ b/yaml/CheckoutService-v53.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=53) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:59Z' + x-timestamp: '2023-02-08T17:21:17Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6621,7 +6621,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v64.yaml b/yaml/CheckoutService-v64.yaml index 361b67b..128ae02 100644 --- a/yaml/CheckoutService-v64.yaml +++ b/yaml/CheckoutService-v64.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=64) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:25:59Z' + x-timestamp: '2023-02-08T17:21:17Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6667,7 +6667,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v65.yaml b/yaml/CheckoutService-v65.yaml index 5b84674..3d0dae1 100644 --- a/yaml/CheckoutService-v65.yaml +++ b/yaml/CheckoutService-v65.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=65) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:26:00Z' + x-timestamp: '2023-02-08T17:21:17Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6682,7 +6682,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v66.yaml b/yaml/CheckoutService-v66.yaml index 49e49a1..2e69e28 100644 --- a/yaml/CheckoutService-v66.yaml +++ b/yaml/CheckoutService-v66.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=66) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:26:00Z' + x-timestamp: '2023-02-08T17:21:18Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6682,7 +6682,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v67.yaml b/yaml/CheckoutService-v67.yaml index b303351..b621d6c 100644 --- a/yaml/CheckoutService-v67.yaml +++ b/yaml/CheckoutService-v67.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=67) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:26:00Z' + x-timestamp: '2023-02-08T17:21:18Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -6685,7 +6685,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis diff --git a/yaml/CheckoutService-v68.yaml b/yaml/CheckoutService-v68.yaml index 14cbd0a..b7eed79 100644 --- a/yaml/CheckoutService-v68.yaml +++ b/yaml/CheckoutService-v68.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=68) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:26:01Z' + x-timestamp: '2023-02-09T12:22:11Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -7861,7 +7861,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis @@ -8356,6 +8355,10 @@ components: - $ref: '#/components/schemas/WeChatPayDetails' - $ref: '#/components/schemas/WeChatPayMiniProgramDetails' - $ref: '#/components/schemas/ZipDetails' + platformChargebackLogic: + x-addedInVersion: '68' + description: Defines the behavior to be applied in case of a chargeback. + $ref: '#/components/schemas/PlatformChargebackLogic' recurringExpiry: description: Date after which no further authorisations shall be performed. Only for 3D Secure 2. @@ -8997,27 +9000,6 @@ components: countryCode: description: The shopper's country code. type: string - localizedShopperStatement: - x-addedInVersion: '68' - additionalProperties: - type: string - description: "This field allows merchants to use dynamic shopper statement\ - \ in local character sets.\nThe local shopper statement field can be supplied\ - \ in markets where localized merchant descriptors are used. Currently,\ - \ Adyen only supports this in the Japanese market\n.The available character\ - \ sets at the moment are:\n* Processing in Japan: **ja-Kana**\nThe character\ - \ set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special\ - \ characters.\nMerchants should send the Katakana shopperStatement in\ - \ full-width characters. \nAn example request would be:\n> {\n \"shopperStatement\"\ - \ : \"ADYEN - SELLER-A\",\n \"localizedShopperStatement\" : {\n \"\ - ja-Kana\" : \"ADYEN - \u30BB\u30E9\u30FCA\"\n }\n}\nWe recommend merchants\ - \ to always supply the field localizedShopperStatement in addition to\ - \ the field shopperStatement.It is issuer dependent whether the localized\ - \ shopper statement field is supported.\nIn the case of non-domestic transactions\ - \ (e.g. US-issued cards processed in JP) the field `shopperStatement`\ - \ is used to modify the statement of the shopper.\nAdyen handles the complexity\ - \ of ensuring the correct descriptors are assigned." - type: object merchantAccount: description: The merchant account identifier, with which you want to process the transaction. @@ -9443,6 +9425,10 @@ components: - $ref: '#/components/schemas/WeChatPayDetails' - $ref: '#/components/schemas/WeChatPayMiniProgramDetails' - $ref: '#/components/schemas/ZipDetails' + platformChargebackLogic: + x-addedInVersion: '68' + description: Defines the behavior to be applied in case of a chargeback. + $ref: '#/components/schemas/PlatformChargebackLogic' recurringExpiry: description: Date after which no further authorisations shall be performed. Only for 3D Secure 2. @@ -10073,6 +10059,10 @@ components: Set this parameter to the origin URL of the page that you are loading the SDK from.' type: string + platformChargebackLogic: + x-addedInVersion: '68' + description: Defines the behavior to be applied in case of a chargeback. + $ref: '#/components/schemas/PlatformChargebackLogic' recurringExpiry: description: Date after which no further authorisations shall be performed. Only for 3D Secure 2. @@ -10390,6 +10380,7 @@ components: description: 'Subscriber number. Maximum length: 15 characters.' maxLength: 15 type: string + PlatformChargebackLogic: {} RatepayDetails: additionalProperties: false properties: diff --git a/yaml/CheckoutService-v69.yaml b/yaml/CheckoutService-v69.yaml index 5002d84..6939004 100644 --- a/yaml/CheckoutService-v69.yaml +++ b/yaml/CheckoutService-v69.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=69) to find out what changed in this version!' - x-timestamp: '2023-02-06T16:26:01Z' + x-timestamp: '2023-02-09T12:22:12Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -7978,7 +7978,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis @@ -8483,7 +8482,7 @@ components: - $ref: '#/components/schemas/WeChatPayMiniProgramDetails' - $ref: '#/components/schemas/ZipDetails' platformChargebackLogic: - x-addedInVersion: '69' + x-addedInVersion: '68' description: Defines the behavior to be applied in case of a chargeback. $ref: '#/components/schemas/PlatformChargebackLogic' recurringExpiry: @@ -9167,27 +9166,6 @@ components: countryCode: description: The shopper's country code. type: string - localizedShopperStatement: - x-addedInVersion: '68' - additionalProperties: - type: string - description: "This field allows merchants to use dynamic shopper statement\ - \ in local character sets.\nThe local shopper statement field can be supplied\ - \ in markets where localized merchant descriptors are used. Currently,\ - \ Adyen only supports this in the Japanese market\n.The available character\ - \ sets at the moment are:\n* Processing in Japan: **ja-Kana**\nThe character\ - \ set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special\ - \ characters.\nMerchants should send the Katakana shopperStatement in\ - \ full-width characters. \nAn example request would be:\n> {\n \"shopperStatement\"\ - \ : \"ADYEN - SELLER-A\",\n \"localizedShopperStatement\" : {\n \"\ - ja-Kana\" : \"ADYEN - \u30BB\u30E9\u30FCA\"\n }\n}\nWe recommend merchants\ - \ to always supply the field localizedShopperStatement in addition to\ - \ the field shopperStatement.It is issuer dependent whether the localized\ - \ shopper statement field is supported.\nIn the case of non-domestic transactions\ - \ (e.g. US-issued cards processed in JP) the field `shopperStatement`\ - \ is used to modify the statement of the shopper.\nAdyen handles the complexity\ - \ of ensuring the correct descriptors are assigned." - type: object merchantAccount: description: The merchant account identifier, with which you want to process the transaction. @@ -9618,7 +9596,7 @@ components: - $ref: '#/components/schemas/WeChatPayMiniProgramDetails' - $ref: '#/components/schemas/ZipDetails' platformChargebackLogic: - x-addedInVersion: '69' + x-addedInVersion: '68' description: Defines the behavior to be applied in case of a chargeback. $ref: '#/components/schemas/PlatformChargebackLogic' recurringExpiry: @@ -10260,7 +10238,7 @@ components: the SDK from.' type: string platformChargebackLogic: - x-addedInVersion: '69' + x-addedInVersion: '68' description: Defines the behavior to be applied in case of a chargeback. $ref: '#/components/schemas/PlatformChargebackLogic' recurringExpiry: diff --git a/yaml/CheckoutService-v70.yaml b/yaml/CheckoutService-v70.yaml index 5026e2f..f30a652 100644 --- a/yaml/CheckoutService-v70.yaml +++ b/yaml/CheckoutService-v70.yaml @@ -80,7 +80,7 @@ info: Have a look at the [release notes](https://docs.adyen.com/online-payments/release-notes?integration_type=api&version=70) to find out what changed in this version!' - x-timestamp: '2023-02-07T12:23:34Z' + x-timestamp: '2023-02-09T12:22:12Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -8154,7 +8154,6 @@ components: - dana - paysafecard - cashticket - - isracard - ikano - karenmillen - oasis @@ -8668,7 +8667,7 @@ components: - $ref: '#/components/schemas/WeChatPayMiniProgramDetails' - $ref: '#/components/schemas/ZipDetails' platformChargebackLogic: - x-addedInVersion: '69' + x-addedInVersion: '68' description: Defines the behavior to be applied in case of a chargeback. $ref: '#/components/schemas/PlatformChargebackLogic' recurringExpiry: @@ -9348,27 +9347,6 @@ components: countryCode: description: The shopper's country code. type: string - localizedShopperStatement: - x-addedInVersion: '68' - additionalProperties: - type: string - description: "This field allows merchants to use dynamic shopper statement\ - \ in local character sets.\nThe local shopper statement field can be supplied\ - \ in markets where localized merchant descriptors are used. Currently,\ - \ Adyen only supports this in the Japanese market\n.The available character\ - \ sets at the moment are:\n* Processing in Japan: **ja-Kana**\nThe character\ - \ set **ja-Kana** supports UTF-8 based Katakana and alphanumeric and special\ - \ characters.\nMerchants should send the Katakana shopperStatement in\ - \ full-width characters. \nAn example request would be:\n> {\n \"shopperStatement\"\ - \ : \"ADYEN - SELLER-A\",\n \"localizedShopperStatement\" : {\n \"\ - ja-Kana\" : \"ADYEN - \u30BB\u30E9\u30FCA\"\n }\n}\nWe recommend merchants\ - \ to always supply the field localizedShopperStatement in addition to\ - \ the field shopperStatement.It is issuer dependent whether the localized\ - \ shopper statement field is supported.\nIn the case of non-domestic transactions\ - \ (e.g. US-issued cards processed in JP) the field `shopperStatement`\ - \ is used to modify the statement of the shopper.\nAdyen handles the complexity\ - \ of ensuring the correct descriptors are assigned." - type: object merchantAccount: description: The merchant account identifier, with which you want to process the transaction. @@ -9808,7 +9786,7 @@ components: - $ref: '#/components/schemas/WeChatPayMiniProgramDetails' - $ref: '#/components/schemas/ZipDetails' platformChargebackLogic: - x-addedInVersion: '69' + x-addedInVersion: '68' description: Defines the behavior to be applied in case of a chargeback. $ref: '#/components/schemas/PlatformChargebackLogic' recurringExpiry: @@ -10450,7 +10428,7 @@ components: the SDK from.' type: string platformChargebackLogic: - x-addedInVersion: '69' + x-addedInVersion: '68' description: Defines the behavior to be applied in case of a chargeback. $ref: '#/components/schemas/PlatformChargebackLogic' recurringExpiry: diff --git a/yaml/StoredValueService-v46.yaml b/yaml/StoredValueService-v46.yaml index 2e70895..5e33504 100644 --- a/yaml/StoredValueService-v46.yaml +++ b/yaml/StoredValueService-v46.yaml @@ -6,7 +6,7 @@ info: x-publicVersion: true title: Adyen Stored Value API description: A set of API endpoints to manage stored value products. - x-timestamp: '2022-11-24T10:17:10Z' + x-timestamp: '2023-02-09T20:21:26Z' termsOfService: https://www.adyen.com/legal/terms-and-conditions contact: name: Adyen Developer Experience team @@ -27,7 +27,7 @@ paths: operationId: post-changeStatus x-groupName: General x-sortIndex: 0 - x-methodName: changesTheStatusOfThePaymentMethod + x-methodName: changesStatusOfPaymentMethod security: - BasicAuth: [] - ApiKeyAuth: [] @@ -76,7 +76,7 @@ paths: operationId: post-checkBalance x-groupName: General x-sortIndex: 0 - x-methodName: checksTheBalance + x-methodName: checksBalance security: - BasicAuth: [] - ApiKeyAuth: [] @@ -174,7 +174,7 @@ paths: operationId: post-load x-groupName: General x-sortIndex: 0 - x-methodName: loadsThePaymentMethod + x-methodName: loadsPaymentMethod security: - BasicAuth: [] - ApiKeyAuth: [] @@ -224,7 +224,7 @@ paths: operationId: post-mergeBalance x-groupName: General x-sortIndex: 0 - x-methodName: mergeTheBalanceOfTwoCards + x-methodName: mergeBalanceOfTwoCards security: - BasicAuth: [] - ApiKeyAuth: []