Test your integration
Every account starts in Test mode. It behaves like live, on testnets, at no cost.
| Test mode | Live mode | |
|---|---|---|
| Money | Testnet coins with no value | Real USDT and USDC |
| Network codes | tron_nile, ethereum_sepolia, … |
tron, ethereum, … |
| API Keys | gw_test_… |
gw_live_… |
| Fee and Prepaid Balance | None | 2.1% of what arrives |
| Second factor | Not needed | Needed to change addresses and keys |
| Limits | None | Rise with age and volume |
Nothing crosses between Modes. Each has its own addresses, keys, Checkouts, Payments and references. The test Pairs are listed in the quickstart.
Callbacks on your own machine
Section titled “Callbacks on your own machine”A Callback URL must be https on a public host, in Test mode too. Put a tunnel in front of your local server and use its address. Send test Callback then checks the whole path.
Cases to run
Section titled “Cases to run”| Case | How | Expect |
|---|---|---|
| Exact payment | Send the amount the page shows. | payment.confirmed, match_result exact. |
| Short payment | Send a little less, within tolerance. | match_result under, and the true amount. |
| Overpayment | Send up to 10% more. | match_result over. |
| Late payment | Let a Checkout expire, then send its exact amount. | expired becomes paid, match_result late. |
| Duplicate Callback | Press Resend on a delivery. | Your server answers 2xx and credits nothing twice. |
| Bad signature | Send a wrong Gateway-Signature. |
Your server refuses it. |
| Unmatched | Send to a test address with no Checkout open. | Nothing is credited. It waits in Unmatched. |
| Unique Amount | Leave the Pair one test address. | The page asks for an amount such as 5.0001. |
| Method unavailable | Ask for a Pair with no test address. | 422 NO_ADDRESS_FOR_PAIR. |
| Retry | Repeat a POST with the same Idempotency-Key. |
The same Checkout, Idempotency-Replayed: true. |
| Missed Callback | Stop your endpoint, pay, call GET /v1/payments. |
The Payment is listed. Retries arrive later. |
Test mode has no balance, so BALANCE_EXHAUSTED cannot happen there. Handle it like NO_ADDRESS_FOR_PAIR.
When every case passes, go live.