---
updatedAt: 2026-06-24T15:11:37.000Z
---

Fetch the complete documentation index at: https://docs.movmint.io/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.

# Sandbox Test

A scripted, guided test session with Movmint that verifies your integration pattern end to end before you go live.

## Overview

Before Movmint provisions Production access, you complete a **Sandbox Test**: a scripted verification of your integration, conducted together with the Movmint team — typically over the phone — against the Sandbox environment.

The purpose is to confirm that your integration pattern behaves correctly end to end: authentication, the flows you intend to use (Quote & Capture, FlowLink, and/or Prefunded Accounts), error handling, and reconciliation. Because it is scripted and guided, both you and Movmint know exactly what to expect and can confirm each step in real time.

## Before the session

To make the session efficient, have the following ready:

* A working integration against `https://api.sandbox.movmint.io` using your Sandbox `client_id` and `client_secret`.
* The ability to obtain an OAuth access token and call the endpoints relevant to your use case.
* Test funding available on the relevant test networks (e.g., testnet USDC on Ethereum Sepolia or Base Sepolia, testnet BTC on Bitcoin testnet3).
* Your reconciliation logic ready to consume `transaction_id` values and transaction-history responses.

## What the session covers

The script is tailored to the flows you plan to use in Production. A typical session walks through:

1. **Authentication** — obtaining and using a bearer token.
2. **Your primary flow**, for example:
   * **Quote & Capture** — request a quote, capture it before expiry, and confirm the resulting transaction and delivery instructions.
   * **FlowLink** — create a FlowLink, send a test deposit to the generated address, and confirm automatic conversion and delivery.
   * **Prefunded Accounts** — request a funding address, fund a balance, and use `CLIENT_BALANCE` as a source or target.
3. **Idempotency** — confirming that retried requests with the same `x-idempotency-key` are not double-processed.
4. **Error handling** — exercising expected error responses (expired quote, insufficient balance, unsupported corridor) and confirming your client handles them gracefully.
5. **Reconciliation** — matching Movmint transaction records against your own.

> 📘 **Why test networks matter**
> Sandbox uses test networks (Ethereum Sepolia, Base Sepolia, Bitcoin testnet3) and a test payment provider, so deposits and deliveries use testnet assets only. Make sure you can source testnet funds for the assets in your corridors ahead of the session.

## Outcome

When the scripted tests pass and Movmint signs off on your integration, you are cleared to move to **[Production](./production.md)**, where Movmint issues your Production credentials and switches you to the live environment.