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.
The live endpoints are set up automatically. To view your live endpoints:
- Log in to your live Customer Area.
- Go to Developers > API URLs.
On the API URLs and Response page, you can see the configured data centres and prefixes for your company account.
If you need to connect to a certain data center of the Adyen payments platform (for example, US or AU data centers), you can also set up location-based live endpoints. To use location-based live endpoints, contact our Support Team.
Live endpoints structure
The table below shows the structure of test and live endpoints.
Classic payments endpoints
In the live endpoint examples:
[version]– The version number, always starting with "v" (for example, v52). To learn more about API versioning for classic and new APIs, see Versioning.
[method]– The endpoint name.
[prefix]– A string composed of a hex-encoded random part and your company name. Get the prefix from your live Customer Area under Developers > API URLs > Prefix.
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 front-end resources
We recommend that you load the front-end resources through the Adyen Web npm package.
Alternatively, you can embed the Adyen Web script and stylesheet into your HTML file. When embedding the script and stylesheet, make sure you use a region-specific URL that matches the region of your live endpoints:
|Live - EU||https://checkoutshopper-live.adyen.com/checkoutshopper/sdk/[version]/adyen.js
|Live - APSE||https://checkoutshopper-live-apse.adyen.com/checkoutshopper/sdk/[version]/adyen.js
|Live - AU||https://checkoutshopper-live-au.adyen.com/checkoutshopper/sdk/[version]/adyen.js
|Live - US||https://checkoutshopper-live-us.adyen.com/checkoutshopper/sdk/[version]/adyen.js
In the endpoint examples:
[version]– The JS SDK version number.
Subresource Integrity hashes
We recommend that you implement Subresource Integrity (SRI) to ensure that the files you are loading from Adyen have not been manipulated or tampered with by malicious actors.
To use the SRI hash, you need to add an
integrity attribute when specifying
<link> elements. Browsers will also check for the
crossorigin attribute to ensure that the origin allows Cross-Origin Resource Sharing (CORS). If a browser detects that the file's hash does not match the specified hash, the browser will not load the resource. To know which browsers support SRI, refer to this browser compatibility list.
For example, here is how you specify version 4.2.0
<script src="https://checkoutshopper-live.adyen.com/checkoutshopper/sdk/4.2.0/adyen.js" integrity="sha384-SGA+BK9i1sG5N4BTCgRH6EGbopUK8WG/azn/TeIHYeBEXmEaB+NT+410Z9b1ii7Z" crossorigin="anonymous"></script>
<link rel="stylesheet" href="https://checkoutshopper-live.adyen.com/checkoutshopper/sdk/4.2.0/adyen.css" integrity="sha384-oT6lIQpTr+nOu+yFBPn8mSMkNQID9wuEoTw8lmg2bcrFoDu/Ae8DhJVj+T5cUmsM" crossorigin="anonymous">
Live URL prefix
Get the prefix from your live Customer Area under Developers > API URLs > Prefix.
For example, if this was your prefix for your live URL:
Then your live URL for the
/payments endpoint on Checkout API v69 would be:
Maximum Transmission Unit (MTU)
We strongly recommend setting the Maximum Transmission Unit (MTU) to 1500 bytes on the network interfaces connecting to Adyen endpoints. The MTU defines the maximum permissible size of the packets passing through the interface. As most of the public internet assumes a maximum packet size of 1500 bytes, configuring the MTU to larger values can lead to connectivity and stability issues.