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

# Production

Moving from Sandbox to live access: what changes, what stays the same, and your go-live checklist.

## Overview

Once your **[Sandbox Test](./sandbox-test.md)** is signed off, Movmint provisions your **Production** credentials and moves you to the live environment. Production behaves identically to Sandbox in every API respect — the difference is that it runs against mainnet networks and live payment rails, so real funds move and real value is at stake.

## What changes when you go live

|             | Sandbox                                                     | Production                                       |
| ----------- | ----------------------------------------------------------- | ------------------------------------------------ |
| Base URL    | `https://api.sandbox.movmint.io`                            | `https://api.movmint.io`                         |
| Credentials | Sandbox `client_id` / `client_secret`                       | **New** Production `client_id` / `client_secret` |
| Networks    | Testnets (Ethereum Sepolia, Base Sepolia, Bitcoin testnet3) | Mainnets                                         |
| Funds       | Test assets only — nothing settles                          | **Real funds settle**                            |

Everything else — endpoints, request and response schemas, status codes, idempotency semantics, and compliance screening — is the same. In practice, going live means swapping two things in your configuration: the **base URL** and your **credentials**.

> ❗️ **Production uses separate credentials**
> Your Sandbox `client_id` and `client_secret` do **not** work in Production. Movmint issues distinct Production credentials. Store them separately from your Sandbox credentials, and never use Production credentials in test or CI environments.

## Go-live checklist

Before sending live traffic, confirm:

* [ ] Production `client_id` and `client_secret` are stored securely (secrets manager / environment variables), separate from Sandbox.
* [ ] Your base URL is configurable per environment and points to `https://api.movmint.io` in Production.
* [ ] You request and cache access tokens correctly, and refresh them before `expires_in` elapses.
* [ ] You send a unique `x-idempotency-key` (UUID) on every write request and reuse it on retries.
* [ ] You persist the `transaction_id` (and `quote_id` / `flowlink_id` where relevant) from every operation for reconciliation and support.
* [ ] You handle the documented error responses for each endpoint (e.g., `400`, `402`, `404`, `409`, `410`).
* [ ] Your monitoring and alerting are wired to detect failed or stuck transactions.

## Operational notes

* **Parity with Sandbox.** Movmint keeps Sandbox and Production in lockstep; Sandbox is updated whenever Production is updated (except during emergency patches). Code validated in Sandbox should behave identically in Production.
* **Limits.** Your per-transaction and volume limits are defined by your Product subscription, configured during [Business Onboarding](./business-onboarding.md). Contact Business Development to adjust them.
* **Support.** Keep the `transaction_id` handy for any support inquiry — it uniquely identifies each transaction across Movmint's systems.

## Next steps

You're live. Continue to the flow that fits your use case:

* **[Authentication & Authorization](../../Authentication%20&%20Authorization/authentication/index.md)** — obtain and use access tokens.
* **[FX Services](../../FX%20Services/fx-services/index.md)** — Quote & Capture.
* **[Prefunded Accounts](../../Prefunded%20Accounts/prefunded-accounts/index.md)** — hold and use ledger balances.
* **[FlowLink](../../FlowLink/flowlink/index.md)** — automated straight-through conversions.