> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cdp.coinbase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sandbox Transfer Simulations

> Reserved Payments API inputs for deterministic Sandbox successes and failures

Each entry below is a reserved input that forces a deterministic Sandbox outcome. Use this reference to test Payments API transfer handling without real recipients or funds.

> [!WARNING]
>
> Do not use these values outside Sandbox. A transfer to a reserved address in
> Live Mode sends real funds to an address no one controls, and your funds will
> be lost.

## Using the values

Send `POST /platform/v2/transfers` with a funded source account, then replace the target field for the case you want to test. Start from this request body and swap in the target fragment shown for your case:

```json theme={null}
{
  "source": {
    "accountId": "YOUR_ACCOUNT_ID",
    "asset": "usdc"
  },
  "target": {
    "network": "base",
    "address": "0x1111111111111111111111111111111111111111",
    "asset": "usdc"
  },
  "amount": "5.00",
  "asset": "usdc",
  "execute": true
}
```

Two kinds of failure appear below:

* **Synchronous:** the request is rejected with HTTP `400` or `422` and `errorType: "invalid_request"`. These are [API errors](https://docs.cdp.coinbase.com/api-reference/v2/errors.md#invalid-request), not transfer failures. Correct the input rather than retrying it unchanged.
* **Asynchronous:** the transfer is accepted with HTTP `200` and status `processing`, then reaches terminal status `failed` after approximately 500 ms. Poll [Get Transfer](https://docs.cdp.coinbase.com/api-reference/v2/rest-api/transfers/get-transfer.md) or handle the `payments.transfers.failed` [webhook](https://docs.cdp.coinbase.com/webhooks/transfers/overview.md).

Responses are excerpts; identifiers, timestamps, and other fields are omitted. Retry guidance concerns the same request or transfer, not a new test with a different magic value.

## Onchain addresses

Set `target.address` to one of these values, with the matching network and asset.

### Synchronous outcomes

| Reserved `target.address` | Simulates | HTTP / transfer status | Retryable |
| - | - | - | - |
| `0x1111111111111111111111111111111111111111` | Successful transfer | `200` / `completed` | Not applicable; succeeded. |
| `0x2222222222222222222222222222222222222222` | Invalid target | `400` / request rejected | No; correct the target. |
| `0x3333333333333333333333333333333333333333` | Invalid address for the network | `400` / request rejected | No; correct the address. |
| `0x4444444444444444444444444444444444444444` | Unsupported network | `400` / request rejected | No; use a different target. |

> [accordion] Successful transfer
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "network": "base",
>     "address": "0x1111111111111111111111111111111111111111",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response (HTTP `200`):
>
> ```json theme={null}
> {
>   "status": "completed"
> }
> ```

> [accordion] Invalid target
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "network": "base",
>     "address": "0x2222222222222222222222222222222222222222",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response (HTTP `400`):
>
> ```json theme={null}
> {
>   "errorType": "invalid_request",
>   "errorMessage": "'target' is invalid: must match one of [Account, Payment Method, Onchain Address, Email Instrument]. Account requires 'accountId'; Payment Method requires 'paymentMethodId'; Onchain Address requires 'network'; Email Instrument requires 'email'"
> }
> ```

> [accordion] Invalid address
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "network": "base",
>     "address": "0x3333333333333333333333333333333333333333",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response (HTTP `400`):
>
> ```json theme={null}
> {
>   "errorType": "invalid_request",
>   "errorMessage": "Invalid onchain address for network base."
> }
> ```

> [accordion] Unsupported network
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "network": "base",
>     "address": "0x4444444444444444444444444444444444444444",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response (HTTP `400`):
>
> ```json theme={null}
> {
>   "errorType": "invalid_request",
>   "errorMessage": "base is not a supported network."
> }
> ```

### Asynchronous failures

| Reserved `target.address` | Simulates | HTTP / transfer status | Retryable |
| - | - | - | - |
| `0x5555555555555555555555555555555555555555` | Asynchronous processing failure | `200` / `processing` → `failed` | No, this transfer is terminal; create a new transfer instead of retrying this one. |

> [accordion] Asynchronous processing failure
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "network": "base",
>     "address": "0x5555555555555555555555555555555555555555",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response (HTTP `200`):
>
> ```json theme={null}
> {
>   "status": "processing"
> }
> ```

A later Get Transfer read returns HTTP `200` with status `failed`. Webhooks fire in this order: `payments.transfers.quoted` and `payments.transfers.processing` (both best-effort), then `payments.transfers.failed`.

## Off-chain targets

Set `target.email` to one of these values.

### Email addresses

#### Synchronous outcomes

| Reserved `target.email` | Simulates | HTTP / transfer status | Retryable |
| - | - | - | - |
| `testuser1@domain.com` | Successful validation and execution | `200` / `completed` | Not applicable; succeeded. |
| `testuser2@domain.com` | Successful validation and execution | `200` / `completed` | Not applicable; succeeded. |
| `sandboxinvalidtarget@domain.com` | Invalid email target | `400` / request rejected, including validation-only requests | No; correct the email. |
| `sandboxexecutionfails@domain.com` | Validation passes, execution fails (synchronous `422`) | Validation-only: `200`; execute: `422` | No; use a different target. |

> [accordion] Successful transfer to user 1
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "email": "testuser1@domain.com",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response (HTTP `200`):
>
> ```json theme={null}
> {
>   "status": "completed"
> }
> ```

> [accordion] Successful transfer to user 2
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "email": "testuser2@domain.com",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response (HTTP `200`):
>
> ```json theme={null}
> {
>   "status": "completed"
> }
> ```

> [accordion] Invalid email target
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "email": "sandboxinvalidtarget@domain.com",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response (HTTP `400` for both execution and validation-only requests):
>
> ```json theme={null}
> {
>   "errorType": "invalid_request",
>   "errorMessage": "Target email is invalid."
> }
> ```

> [accordion] Synchronous execution failure
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "email": "sandboxexecutionfails@domain.com",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response with `execute: true` (HTTP `422`):
>
> ```json theme={null}
> {
>   "errorType": "invalid_request",
>   "errorMessage": "Sandbox: simulated execution failure."
> }
> ```
>
> To test validation instead, set `validateOnly: true` and `execute: false`. HTTP `200` returns validated details without a transfer status.

#### Asynchronous failures

| Reserved `target.email` | Simulates | HTTP / transfer status | Retryable |
| - | - | - | - |
| `sandboxasyncfailure@domain.com` | Execution accepted (`IN_PROGRESS`), then transitions to `FAILED` async | `200` / `processing` → `failed` | No, this transfer is terminal; create a new transfer instead of retrying this one. |

> [accordion] Asynchronous processing failure
>
> Target request:
>
> ```json theme={null}
> {
>   "target": {
>     "email": "sandboxasyncfailure@domain.com",
>     "asset": "usdc"
>   }
> }
> ```
>
> Response (HTTP `200`):
>
> ```json theme={null}
> {
>   "status": "processing"
> }
> ```

A later Get Transfer read returns HTTP `200` with status `failed`. Webhooks fire in this order: `payments.transfers.quoted` and `payments.transfers.processing` (both best-effort), then `payments.transfers.failed`.

## Related references

* [Transfers Quickstart](https://docs.cdp.coinbase.com/payments/transfers/quickstart.md) for runnable success requests.
* [Transfer validation](https://docs.cdp.coinbase.com/payments/transfers/validation.md) for validation-only behavior.
* [Failure reference](https://docs.cdp.coinbase.com/api-reference/v2/failures.md) for failure-code definitions and retry guidance.
* [Customer verification Sandbox values](https://docs.cdp.coinbase.com/customers-kyc/requirements.md#testing-in-sandbox) for KYC and capability simulations, which are separate from transfer test values.
