Environment Overview
| Environment | Purpose | Data | Billing |
|---|---|---|---|
| Staging | Development and initial integration testing | Sandbox (mock ICP data) | No charges |
| Pre-Production | Final validation before go-live | Near-production (controlled test data) | No charges |
| Production | Live operations with real customers | Real ICP government data | Credits consumed per transaction |
Staging
The staging environment is your primary development and testing workspace. It connects to a sandbox ICP database where you can create and manage test residents with configurable data. Use staging to:- Integrate and test SDK flows (Web, Android, iOS)
- Test API calls against mock data
- Create sandbox residents with specific scenarios (expired visas, out-of-UAE status, etc.)
- Validate your end-to-end journey flow before moving to pre-production
Sandbox Mode must be enabled in your organization settings for the staging environment. See Getting Access for onboarding steps.
Pre-Production
The pre-production environment mirrors the production setup and is used for final validation before go-live. It connects to controlled test data that closely resembles real government records.| Resource | Value |
|---|---|
| Dashboard | Provided during onboarding |
| API Domain | Provided during onboarding |
- Perform end-to-end acceptance testing
- Validate network connectivity and routing through production-grade infrastructure
- Run load and performance tests
- Verify SDK behavior with near-real data
- Conduct UAT (User Acceptance Testing) with stakeholders
Production
The production environment serves live customers with real identity verification against ICP government databases. All API calls consume credits and are billed accordingly.| Resource | Value |
|---|---|
| Dashboard | Provided during onboarding |
| API Domain | Provided during onboarding |
- All API transactions are billed (see Billing Rules)
- Real government data — handle with care and in compliance with data protection regulations
- Monitor credit balance via the Balance & Metering dashboard section
- API keys and credentials are environment-specific and must not be shared across environments
Progression Path
Complete your SDK and API integration using sandbox data. Create test residents to cover all verification scenarios (success, failure, edge cases).
Migrate your integration to the pre-production environment. Run full acceptance tests, validate network paths, and confirm end-to-end flows.
Each environment has its own API keys, dashboard credentials, and network endpoints. Ensure your application configuration correctly targets the intended environment.