Use the sandbox environment
Authenticate with a sandbox secret key. The base URL is the same as live — the environment is determined by the key.Test Payment Gateway
Every sandbox project ships with a built-in Test Payment Gateway, wired to a dedicatedtest payment method and routed automatically — there is no gateway account to configure.
Attempt a sandbox payment with method_code set to test; the last two digits of the
payer phone number select the outcome.
Simulate scenarios
The outcome is driven by the last two digits of the payer phone number, so any valid number from any country works — only the ending matters:- ends in
01→ pending - ends in
02→ failed - any other ending → success
+225…01 is also pending, a +225…02 is also
failed).
| Scenario | Example phone number | Result |
|---|---|---|
| Successful payment | +1 415 555 0100 | Attempt and intent reach completed. |
| Pending payment | +1 415 555 0101 | Attempt stays processing; it resolves to completed on verification / reconciliation. |
| Failed payment | +1 415 555 0102 | Attempt becomes failed with a failure reason. |
The Test Payment Gateway and its
test method exist only in sandbox — they never appear in
live. Use a number ending in 01 or 02 to exercise the pending and failed paths.Test with a provider’s sandbox
To test against a real provider, add a sandbox gateway account with that provider’s sandbox credentials and route to it. Provider-specific test phone numbers, cards and OTPs come from each provider’s own sandbox documentation.Test webhooks
Pointwebhook_url at a publicly reachable URL (use a tunnel such as ngrok in local dev).
Orqex delivers the same events in sandbox; verify your handler by re-fetching the payment.
See Webhooks.