Adyen has announced the decommissioning of cross-regional connections between Cloud Terminal API endpoints.
Beginning October 1, 2025, support for cross-regional connections will be discontinued, and the feature will be fully decommissioned on February 1, 2026.
Important:
To avoid service disruptions, you’ll need to update your configuration in NewStore to use regional endpoints. As a result, all Adyen payment transactions must be processed through regionally local endpoints rather than the current generic Live endpoint.
Why Adyen is making this change:
Faster and more reliable API connectivity
Quicker transaction response times
Prevents interruptions after February 1, 2026
After that date, cross-regional requests will be blocked by default and only allowed if your local region is unavailable.
ALERT: Retailers unable to meet the deadline MUST reach out to Adyen to request an extension.
How are NewStore customers impacted?
NewStore customers may be connecting to Adyen via one or more of the following endpoints:
Current LIVE Terminal API Endpoint(s):
https://terminal-api-live.adyen.com - This represents the Europe (EU) endpoint
https://terminal-api-live-us.adyen.com - This represents the Unitied States (US) endpoint
https://terminal-api-live-au.adyen.com - This represents the Australia (AU) endpointCurrent TEST Terminal API Endpoint (this will remain in place)
https://terminal-api-test.adyen.com/Moving forward, the TEST endpoint will remain unchanged, and retailers and partners can continue to use this for Sandbox and Staging configurations.
ALL LIVE endpoints must be reviewed and updated to the use the new, region-specific URLs, based on the guidance provided by Adyen within the retailers merchant account setup within Adyen.
Caution:
The Adyen documentation and the URL examples within the Adyen guide specify using regional endpoints that end with “/sync”. This is NOT needed nor supported for the NewStore configuration. When entering the updated endpoints within the NewStore PSP_Adyen configuration do not use “/sync” on the end of the URL.
Who Must Take Action?
NewStore and Adyen have done an analysis of merchant traffic hitting current Adyen endpoints and have identified the retailers and stores where the current API endpoint being hit is incorrect.
NewStore will be opening proactive customer support tickets for each retailer, with a listing of stores currently using an incorrect API endpoint, along with the correct regional endpoint that must be used going forward.
IMPORTANT:
If you are a merchant that ONLY has stores within Europe, you need to ensure the top-level of the PSP Adyen configuration in NewStore is using the Europe endpoint.
If you are a merchant that ONLY has stores within the United States, you need to ensure the top-level of the PSP Adyen configuration in NewStore is using the United States (US) endpoint.
If you are a merchant that ONLY has stores within Australia, you need to ensure the top-level of the PSP Adyen configuration in NewStore is using the Australia (AU) endpoint.
If you are a merchant that ONLY has stores within East Asia, you need to ensure the top-level of the PSP Adyen configuration in NewStore is using the East Asia (APSE) endpoint.
If you are a merchant with stores across MULTIPLE REGIONS, you MUST make specific store level configuration changes to ensure those stores are using the correct terminal API endpoints by updating the specific “store_mapping” section within the PSP Adyen configuration in NewStore.
Adyen Regional Endpoints:
Region | Live Endpoint URL |
|---|---|
Europe* | |
United States | |
Australia | |
East Asia | |
Important: *The terminal API endpoint for Europe will remain the same as it exists today. Retailers that ONLY have stores in Europe will not be impacted by this change.
For test stores and NewStore staging instances, continue using the Adyen test endpoint:
https://terminal-api-test.adyen.comReference: Adyen Cloud Terminal API Documentation
Making the necessary configuration changes
Step 1: Identify the Required Endpoint
Log in to your Adyen Customer Area.
Go to In-Person Payments > Terminal settings > Integrations.
Find the assigned Terminal API endpoint for each merchant account region.
Match the endpoints to your NewStore store location(s).
Step 2: Update Your Configuration in NewStore
Before you begin:
Work with your internal development team or your NewStore Implementation partner.
Understand that ALL API changes being made for this configuration MUST be made in the Live/Production area for NewStore. Adyen does not support these regional endpoints in their test area.
Caution:
We recommended that retailers change the configuration for 1 store per region, run a transaction, and then once the endpoint connectivity is confirmed, apply the changes to additional store configurations.
Ensure you have access to modify PSP_Adyen at the store level.
How to Update
Identify all Live store locations that must be updated and note their expected or required terminal API endpoint from your Adyen Merchant account.
When making an update to the NewStore PSP_Adyen configuration:
- Locate the
“pos"section under the PSP_Adyen configuration in NewStore.- If you are applying a configuration at a global or top level - such as for all stores being located in a single region, you may update the
“terminal_api_url":within the POS section of the configuration.For example, if all stores are within the US region, the configuration update would be:
“terminal_api_url":“https://terminal-api-live-us.adyen.com"
- If you are making store-level configuration changes, locate the
“store_mapping"section underPOSand add or update theterminal_api_urlparameter to the correct regional endpoint.Example, As a retailer with 1 store in Europe and 1 store in Australia, the following would be the correct configuration for
PSP_Adyen:
"pos": {
"authorization_type": "PreAuth",
"credentials": {},
"environment": "test",
"terminal_api_url": "https://terminal-api-live.adyen.com",
"payment_subject": "Giovanna Dodici",
"store_mapping": [
{
"adyen_store_id": "1001",
"store_id": "DE01"
},
{
"adyen_store_id": "1201",
"store_id": "AU02",
"terminal_api_url": "https://terminal-api-live-au.adyen.com",
"merchant_config": {}
Save the updated configuration for each store.
Test transactions at each location to confirm successful connection and processing.
NOTE
In the above API example, there are 2 entries for the terminal_api_url. The first entry is the DEFAULT top-level endpoint. This endpoint is used for ALL store configurations when there are no endpoints defined within a store_mapping section. When endpoints are configured under the store_mapping level, those endpoints are used and overwrite the top-level configuration. In this configuration - Store 1001 will use the EU endpoint and Store 1201 will use the AU endpoint.
Tip: If a merchant has a high number of stores in one region, and a lower number in another region, the PSP_Adyen configuration can be configured such that the majority of the stores use the top-level terminal API URL and ONLY the locations with fewer stores will have the store-level configuration updated.Sample Configuration Scenario:
Retailer footprint sample and configuration:
15 stores in Europe
5 stores in Australia
Set top-level endpoint to cover all (15) European stores to:
terminal_api_url→https://terminal-api-live.adyen.comOverride endpoint for all (5) Australian stores with:
terminal_api_url→https://terminal-api-live.au.adyen.com
Timeline Reminder
Now – Sept 30, 2025: Review and update configurations.
Oct 1, 2025: Cross-regional support ends and gradual deprecation begins.
Feb 1, 2026: Cross-regional connections fully blocked.
Need Help?
Reach out to Adyen support or your specific Adyen point of contact for terminal API specific questions.
Reach out to the NewStore Support for assistance