Environments
Every tenant has two environments — Sandbox and Production — so a Company can build and test a configuration safely, then promote it when ready.
Sandbox vs Production
| Environment | Purpose |
|---|---|
| Sandbox | Build and test workflows, Trust Factor profiles, documents, and integrations without affecting live traffic. Limited in verifications and days (see below). |
| Production | The live environment serving real users. |
Configuration is kept separately per environment — IDV configuration, integration settings, workflows, and credentials all have independent Sandbox and Production values. The dashboard's environment switcher (top bar) selects which one you are viewing and editing; it defaults to Sandbox.
Sandbox limits
A tenant in Sandbox can start a limited number of verifications within a limited number of days — by default 150 verifications and 14 days, or the limits agreed with Innovatrics. Every session start counts, whichever channel starts it. When either limit is used up, starting a session is refused with 403 SANDBOX_LIMIT_REACHED and no workflow runs (the error message says whether the time or the verification limit was reached). The dashboard stays available and shows a Sandbox limit reached warning.
The block is lifted at once when Innovatrics extends the Sandbox (more verifications or more days) or moves the tenant to Production. Production is never limited this way.
Promoting to Production
The switch from Sandbox to Production is made by Innovatrics, not from the tenant's dashboard — contact your Innovatrics representative when you are ready to go live. The licensed features of the tenant stay exactly as they were in Sandbox. The switch is audited and one-way. Sandbox remains editable afterwards for continued testing, so promotion does not freeze experimentation.
Point the Capture & Workflow API at Sandbox during development using the environment's own credentials, and switch your backend to Production credentials at go-live — no code changes beyond the credentials.