Regions
Production
The Orchestrapay API is region-specific: every API key and payment intent
belongs to a region, and you call the host for that region. Your region is the
code embedded in your keys and IDs (for example eu1 in orch_sk_live_eu1_...
and pi_eu1_...).
| Region | Code | Production API base URL |
|---|---|---|
| USA (Ohio) | us1 | https://api-us1.orchestrapay.com |
| Europe (Frankfurt) | eu1 (default) | https://api-eu1.orchestrapay.com |
| Egypt (Cairo) | eg1 | https://api-eg1.orchestrapay.com |
https://api.orchestrapay.com is a convenience alias for the Europe host.
The @orchestrapay/sdk and @orchestrapay/react packages pick the correct
regional host automatically from your key, so you only need these hosts for raw
HTTP calls.
In production you can associate IP Addresses with API keys to be whitelisted.
CI/CD
Most gateways in the EMEA region do not provide a testing environment continuously available. We therefore encourage you to write tests with Orchestrapay using the sandbox gateways (Sandbox Gateway and Sandbox BNPL).
The sandbox gateways are available 24/7 with no limit on the number of transactions or tests you can run.