Environments
BINKPAY separates concerns along two independent axes: region and mode. Your API key encodes both, so there is no base URL to switch.
Axis 1 · Region
Egypt or Global
Fixed at onboarding. Decides payment methods, settlement currency and regulator.
Axis 2 · Mode
Sandbox or production
Chosen per request by the key you authenticate with. No separate base URL.
Egypt and Global
A company account is provisioned for one region at onboarding, which fixes the available payment methods, the settlement currency and the regulatory jurisdiction.
The switcher at the top of these docs changes the examples you are reading, not your live account. Your region is fixed at onboarding.
Sandbox and production
Every account has both key pairs. Sandbox requests never move real money and accept the test card and wallet numbers from the Testing guide.
| Key | Mode | Where it runs | Effect |
|---|---|---|---|
sk_test_… | Sandbox | Server only | No real money moves |
sk_live_… | Production | Server only | Real funds |
pk_test_… | Sandbox | Client-side | Safe to expose |
pk_live_… | Production | Client-side | Safe to expose |
Base URL and what the key actually controls
Every route is served under https://binkpay.net/api/v1. For the one endpoint that currently accepts an API key (the developer probe), the key's prefix decides sandbox vs. production. For every other resource in the API Reference — Payments, Payouts, Refunds, Cards, Customers, Invoices — there is no separate sandbox/production key today; access is by dashboard session. See Authentication for the full split.
Was this page helpful?