# Sandbox Test Data

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

## Email verification (OTP)

Banxa validates the customer's email address. In sandbox, enter any email address; on the next page, enter the code `7203`. No email is actually sent in sandbox.

| Field | Value |
|  --- | --- |
| Email address | Any email address |
| Verification code | `7203` |


## Credit / debit card

| Field | Value |
|  --- | --- |
| Card number | `4111 1111 1111 1111` |
| Expiry | Any future date (e.g., `12/29`) |
| CVV | Any 3-digit number (e.g., `123`) |
| Name on card | Must match the name entered at the billing details step |


Cardholder name must match billing details
The name on the card is not free text in sandbox. Enter the same name you supplied during the billing details step, otherwise the payment will fail.

## 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.
- If prompted for document upload, any legible document image is accepted in sandbox — no special test assets are required.


## Local payment methods

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

| Country | Identity type | Test value |
|  --- | --- | --- |
| Brazil | Cadastro de Pessoas Físicas (CPF) | `10112075088` |
| Chile | Rol Único Nacional | `760864285` |
| Colombia | Cédula de Ciudadanía | `1077650154` |
| Mexico | CURP | `HEGG560427MVZRRL04` |
| South Africa | National ID | `8001015009087` |
| Thailand | Thai identity card number | `4854701245289` |
| United States | SSN | `222608111` |


## 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.

| Field | Value |
|  --- | --- |
| Name | Same name submitted during KYC |
| BSB | `032-050` |
| Account Number | `111111` |


## Wallet addresses

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

| Network | Example 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:

| Scenario | How to trigger |
|  --- | --- |
| `complete` | Complete the full checkout flow with valid test credentials |
| `expired` | Leave the checkout URL without completing — wait for expiry |
| `cancelled` | Close or exit the checkout before completing |


## Webhooks in sandbox

Webhooks are delivered in sandbox just as in production. Use a tool like [webhook.site](https://webhook.site) or [ngrok](https://ngrok.com) to receive and inspect webhook payloads during local development.

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