Skip to main content
Zennopay exposes isolated sandbox and live environments. They share API contracts but do not share credentials, balances, beneficiaries, payouts, or configuration.

​
Canonical base URLs

All endpoints are mounted under /v1, for example:

​
Supported alternate hosts

Existing integrations may continue to use: Both hostname families serve the same environment and API contract. New integrations should use the canonical .com URLs. The host is not part of the HMAC canonical request, so switching between equivalent hosts does not change request signing.

​
Isolation rules

  • A sandbox key is rejected by live, and a live key is rejected by sandbox.
  • The server and API-key context bind the environment. For Platform Payouts, optional X-Zennopay-Mode: test|live is only an assertion; it cannot promote a test key to live.
  • IDs are environment-scoped. Do not reuse a sandbox beneficiary, payment intent, or payout ID in live mode.
  • Sandbox execution never falls back to a live rail.

​
Before live traffic

Live credentials, source-network allowlisting, balances, destination routes, beneficiary protection, compliance/risk controls, and webhook verification must be enabled for the account. Missing dependencies fail closed. A passing sandbox flow does not itself enable live mode.