Sandbox testing
Use sandbox to validate your Trade API integration without moving production funds. Sandbox credentials, resources, balances, and payment details are isolated from production and have no monetary value.
Run the required workflows for representative clients. Tests use the partner
access token with /clients/{clientId} resource paths; accounts, balances,
permissions, registered external accounts, and activity belong to the selected
client.
What sandbox validates
Sandbox is intended to validate:
- authentication, allowlisting, headers, and idempotency;
- partnership authentication and client resource scoping;
- Axiym account, registered external-account, deposit, conversion, and withdrawal workflows;
- asynchronous status and webhook handling; and
- Axiym account-statement reconciliation.
It does not replace production validation of bank connectivity, operational processes, or controls outside the Trade API.
How workflows behave
| Workflow | Sandbox approach | What to verify |
|---|---|---|
| External-account registration | Register an owned sandbox bank account or test-network wallet and wait for activation. | Ownership scope, review states, notifications, and stored destinationId. |
| Conversion | Convert Axiym-provided test balance between permitted sandbox Axiym accounts. | Quote and confirmation handling, statuses, idempotency, and both ledger entries. |
| Blockchain deposit | Send the configured test asset from a registered test wallet over the network confirmed by Axiym. | Registered origin, deposit detection, notifications, Axiym account credit, and transaction hash. |
| Blockchain withdrawal | Withdraw the configured test asset to the active registered test wallet. | Registered recipient, statuses, notifications, Axiym account debit, and transaction hash. |
| Bank deposit | Use the Axiym-provided simulation for a payment originating from the registered test bank account. | Registered origin, reference matching, deposit statuses, notifications, and Axiym account credit. |
| Bank withdrawal | Use the Axiym-provided simulation to send funds to the active registered test bank account. | Registered recipient, withdrawal statuses, notifications, and Axiym account debit. |
Never send real funds to sandbox bank details, and never use a production blockchain address or network for a sandbox test.
What Axiym confirms during setup
Before testing external payment workflows, confirm with Axiym:
- which Axiym accounts and conversion directions are provisioned;
- which sell-side Axiym account contains the test balance;
- the supported blockchain test network and test asset;
- the external bank-account and wallet details permitted for registration;
- how simulated bank deposits and withdrawals are initiated;
- which success and failure outcomes can be exercised; and
- how test balances are replenished or reset.
The specific bank fixtures, scenario controls, network, asset, and reset process are intentionally not hard-coded in this guide. Use the values issued for your sandbox environment.
Recommended test sequence
- Complete the first conversion quickstart using the funded Axiym account that matches the selected pair's sell side.
- Configure webhooks and verify that duplicate or delayed deliveries are safe.
- Register an owned external test account and wait for it to become active.
- Test a deposit originating from that registered account using the configured rail.
- Create a withdrawal back to an active registered external account and follow it to a terminal state.
- Reconcile every completed operation against the affected Axiym account statement.
- Exercise the available failure and retry scenarios before requesting production access.
Before production
Repeat environment-specific configuration with production credentials, allowlists, Axiym accounts, permissions, registered external accounts, and payment details. Do not copy sandbox identifiers or fixtures into production configuration.
For bank integrations, separately validate real connectivity and operational reconciliation. For blockchain integrations, confirm the production network, asset, address format, and monitoring process before transferring funds.