To communicate with the Adyen API you should submit HTTP POST requests to corresponding endpoints. These endpoints differ for test and live accounts, and also depend on the data format (SOAP, JSON, or FORM) you use to submit data to the Adyen payments platform.
This topic explains how to set up endpoints when you switch your integration from test to live. If you are using Hosted Payment Pages, the corresponding live endpoints are described in Hosted Payment Pages API.
Our API is versioned using the URL of the endpoint, for example:v40/authorise.
While we endeavor to maintain backwards compatibility, we version the API when a change will create compatibility issues. We maintain older versions of the API which you can continue to use until you are ready to upgrade.
We strongly recommend you always specify the endpoint version to avoid issues with backwards compatibility. If you don't specify the version number in the endpoint URL, the Adyen payments platform will use the default version instead, which is subject to change.
Live endpoints structure
When you switch from test to live, you must also replace test endpoints with corresponding live URLs. For this, you need to set up your own custom endpoints for live payments.
The table below shows the structure of test and live endpoints.
Standard payments endpoints
In the live endpoint examples:
- [version] – The service version number, always starting with "v" (for example, "v40").
- [method] – The endpoint name.
- [random] – A random string of hex-encoded bytes to make the hostname unpredictable.
- [company name] – The company name to be included in the URL endpoint. If the name is too long, it is shortened. If the name includes underscores or hyphens, any underscores and/or hyphens are stripped.
Each company account is provided with a unique hostname to communicate with Adyen's APIs. By connecting to this merchant-specific hostname, Adyen has more control over the routing of transactions. This allows Adyen to improve service robustness and availability for our merchants.
By default all transactions for a merchant-specific endpoint are routed to the same infrastructure as the standard endpoint, however in case of an infrastructure problem on the standard endpoint, especially if the cause is outside of Adyen's scope of control, alternative routing can be enabled to backup infrastructure and new infrastructure can be provisioned on demand.
Checkout JS endpoints
|n the endpoint examples:
- [version] – The JS SDK version number.
Set up live endpoints
To set up endpoints for live payments, contact Support Team.
If you already have live endpoints set up for you, follow the steps below to view current settings:
- Log in to the Customer Area (Live).
- Go to Account > API URLs.
- On the API URLs and Response page, you can see the configured endpoints for your company account.
In addition, you can set up location-based live endpoints, so that you can connect to a certain data center of the Adyen payments platform (for example, US or AU data centers).
To use location-based live endpoints, contact Support Team.
Live URL prefix
For example, if this was your live URL:
Then the live URL prefix would be