Sandboxes are isolated test environments on the public API. There is no separate sandbox hostname: normal /v1/... requests go to https://api.withflintpay.com, and the sandbox-bound flint_test_... key you authenticate with decides which sandbox handles the request. Every developer merchant gets one default sandbox automatically; create additional sandboxes for CI, partner QA, or pre-release testing.
The default sandbox is prepared for test card payments automatically at sign-up. For a short time after, its accept_card_payments capability can be pending. If an earlier attempt to set up a sandbox's test payments failed, the next attempt starts a fresh setup instead of staying stuck, and the sandbox doesn't need a reset. Before relying on a sandbox for card payments, check GET /v1/capabilities?capability=accept_card_payments and wait for ready.
Test keys are permanently bound to one sandbox environment at creation, so there is no per-request sandbox header to manage. Resetting a sandbox archives that environment, clears its data, and returns a replacement with a new sandbox ID. The replacement retains the stable provider-account lineage, but you must issue new test keys because keys for the archived environment stop authorizing requests. The default sandbox cannot be archived or reset.
See the Testing guide for the runtime testing loop, including test cards and simulating payment outcomes.
