Skip to content
Last updated

Use the following credentials and test data when testing in the sandbox environment.


Mobile verification

When prompted for a mobile number during checkout, the sandbox accepts a PIN of 7203 for any number. Use one of the pre-approved Australian test numbers below — an actual SMS is sent to whatever number you enter, so do not use a real number.

Mobile numberPIN
+61 4915776447203
+61 4915781487203
+61 4915789577203
+61 4915792127203
+61 4915746327203
+61 4915794557203
+61 4915701567203
+61 4915701597203

Credit / debit card

FieldValue
Card number4111 1111 1111 1111
ExpiryAny future date (e.g., 12/29)
CVVAny 3-digit number (e.g., 123)
NameAny name

KYC testing

When prompted for identity verification:

  • Use realistic-looking information — test names, addresses, and dates of birth.
  • Do not use placeholder values like "Test Test" or "123 Fake Street" — these may trigger additional review.
  • Use test document images if prompted for document upload (contact Banxa for test document assets).

Local payment methods

Some payment methods require a national identity number. Use the following test values:

CountryIdentity typeTest value
BrazilCadastro de Pessoas Físicas (CPF)10112075088
ChileRol Único Nacional760864285
ColombiaCédula de Ciudadanía1077650154
MexicoCURPHEGG560427MVZRRL04
South AfricaNational ID8001015009087
ThailandThai identity card number4854701245289
United StatesSSN222608111

Bank transfers (off-ramp / AUD)

Use these details for AUD off-ramp testing. The account name must match the name submitted during KYC — any account number is accepted in sandbox.

FieldValue
NameSame name submitted during KYC
BSB032-050
Account Number111111

Wallet addresses

You can use any valid-format wallet address for testing. Example:

NetworkExample address
Ethereum (ETH)0xe3BDEFdAeFF070925eB7FfC49F9B30c647Cb751e
Bitcoin (BTC)bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq

No crypto is actually transferred in sandbox. The checkout will simulate the transaction flow.


Triggering specific order statuses

To test how your integration handles different order outcomes, you can engineer specific scenarios in the sandbox:

ScenarioHow to trigger
completeComplete the full checkout flow with valid test credentials
expiredLeave the checkout URL without completing — wait for expiry
cancelledClick "Cancel" or close the checkout before completing
declinedUse a card number that triggers decline (contact Banxa for test decline cards)

Webhooks in sandbox

Webhooks are delivered in sandbox just as in production. Use a tool like webhook.site or ngrok to receive and inspect webhook payloads during local development.

Configure your sandbox webhook URL in the Partner Dashboard under the Sandbox environment setting.