Sandbox testing
The sandbox is a full copy of the production surface that accepts test keys only (environments). Everything you build is provable there:
| What to prove | How |
|---|---|
| Auth & signing | GET /health returns your org code; failures → echo-signature |
| Case ingestion | POST /cases?dryRun=1 → zero row errors → commit → cases visible |
| Webhook receiver | POST /webhooks/test fires a signed ping and returns the result synchronously |
| Dedupe | Replay a delivered event (delivery log) — your receiver must report it as a duplicate, not re-apply |
| Sequence handling | Push + confirm quickly — events can arrive out of order; verify your books stay correct |
| Payments (Mode B) | Your mint endpoint gets called; your payments/confirm closes the case; 409 on a repeated reference |
| Recovery | Poll GET /cases/updates and reconcile it against what your webhooks stored |
The fastest way to see the whole lifecycle is the reference implementation — run it with your sandbox keys and watch every panel light up.