Environment overview
When to use each environment
- Building and iterating on client applications using simulated data
- Validating core flows end-to-end: account creation, conversions, transfers, webhook handling
- Testing failure scenarios and retry logic without financial risk | | Production | - Running live user flows with real conversions and transfers
- Meeting audit, reporting, and uptime requirements for business-critical use cases
- Performing final integration validation with real data and assets |
Authentication & API access
Both environments use the same authentication model (API keys + optional JWT signing), but credentials are environment-specific and cannot be shared between Sandbox and Production. For implementation details, see API authentication.Chains, assets, and on-chain behavior
Network support
Behavioral differences
For complete chain and asset details, see Supported chains and assets.
Compliance and identity verification
Compliance requirements differ significantly between environments to enable efficient testing while maintaining production security.Compliance comparison
Production compliance requirements
Full regulated identity verification:- End users and businesses provide real documents and information
- Reviews can result in approvals, rejections, or requests for additional information
- Identity decisions affect account limits, transaction eligibility, and ongoing monitoring
Fiat operations and settlement
Fiat conversion behavior differs fundamentally between environments.Fiat operations comparison
Example flows
Data persistence and reliability
Need help? Contact support at try@bastion.io or reach out to your sales representative.