Environments
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 |
|---|---|---|
| Europe (Frankfurt) | eu1 (default) | https://api-europe.orchestrapay.com |
| Egypt (Cairo) | eg1 | https://api-egypt.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.
Staging
API: https://api-staging.orchestrapay.com
MyBNPL & MyGateway
In staging, we provide 2 fictitious gateways that will allow you to integrate the Payment API without having any real underlying gateway API key.
You can create a Payment Intent with these demo gateways, both have embedded success/cancel options to test your webhooks:
MyBNPL
MyBNPL is a fictitious Buy Now Pay Later that allows the customer to select a repayment tenure, multiple loan options and have to authenticate through a fictitious OTP.
MyGateway
MyGateway is a fictitious card gateway that's single stepped.
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 fictitious MyGateway.
Orchestrapay maintains staging environments available 24/7 and there are no limit on how many transactions or tests you can run.