Yes, Adyen does enforce region-based restrictions in both testing (test/sandbox) and live environments for POS terminals—especially in terms of:
🌍 1. Terminal Shipment & Activation
• Adyen terminals are region-locked at the time of shipping.
• When you order a terminal, it’s registered to a specific region or country.
• The terminal can only be activated in the region it was intended for unless special exceptions are made.
Example:
A V400m shipped for use in the U.S. cannot be activated in Europe unless Adyen explicitly configures it for multi-region use.
🔐 2. Store Configuration (Merchant Account Level)
• Each store/merchant account is tied to a specific country code (e.g., US, GB, AU).
• Your terminal’s configuration must match the region of the store it’s linked to in Adyen.
• Attempting to use a terminal in the wrong country may block activations or transactions.
🧪 3. Testing (Test Environment) Limitations
• Even in test mode, terminals are assigned to specific regions.
• You can simulate transactions, but network behavior and local scheme rules may not reflect the real-world setup in other regions.
• Certain payment methods (e.g., Interac in Canada, Girocard in Germany) may not be available in the test environment or may only work within specific region setups.
🚫 4. Connectivity Rules and Restrictions
• Some mobile or Wi-Fi networks may block or throttle Adyen’s services, especially if used outside the approved deployment country.
• Firewalls, DNS, or VPNs in restricted regions may interfere with activation or log uploads.
✅ Best Practices
• Always order terminals specific to the region where they will be used.
• If your platform operates across countries (e.g., U.S. + Canada), request multi-region enablement during onboarding with Adyen.
• For test environments, ensure your stores and accounts match the test region and consult Adyen for region-specific terminal behavior.