Three environments. Three kinds of evidence.
Choose the right setting for each evaluation step, from synthetic exploration to approved provider testing and production review.
Keep identities, data and credentials apart.
Environment identity is part of the financial domain. Records and capability requests must belong to the expected environment. Deployment configuration is checked against the database’s recorded environment. Credentials alone do not enable an operation.
| Context | Purpose | Required evidence |
|---|---|---|
| Demo | Synthetic workflows; no real funds. | Simulation capability and isolated fixtures. |
| Sandbox | Authorized provider test identities and operations. | Exact provider scope and sandbox acceptance. |
| Production | Approved real operations only. | Program approval, reviewed deployment and operational acceptance. |
Activation is an explicit decision.
Capability grants bind an environment, provider connection, organization, asset and operation. Production capability evidence includes separate requester and approver identities. Partner metadata or a provider logo does not change those grants.
An environment-specific release must confirm the actual source, schema, authentication settings, provider configuration and client compatibility. A successful local build is not evidence of that release.