Environments
Switch between testing and production hosts for every example.
Supported hosts
Challanwala examples in this site support two selectable environments:
| Status | Meaning | Notes |
|---|---|---|
| Testing | https://cms-staging.challanwala.com | Uses the staging-only `/api/v1/staging` namespace, self-serve dummy keys, and deterministic test data. |
| Production | https://cmsapi.challanwala.com | Use for live organization traffic once your integration is ready to go live. |
Testing environment
https://cms-staging.challanwala.com
/api/v1/staging
Recommended while wiring up and validating your integration.
How environment switching works
- The selected environment is shared across the docs site.
- Endpoint examples automatically update the host and the route namespace everywhere.
- Request bodies, headers, and response shapes stay the same unless stated otherwise.
- Production examples resolve to
/api/v1/organization-api/.... - Testing examples resolve to
/api/v1/staging/....
Recommended rollout pattern
- Start with the testing environment.
- Verify metadata and challan search flows.
- Validate payment-link creation and webhook handling.
- Switch your integration to the production environment when ready.
Testing uses a replica API
The staging environment is a Hono-based testing replica. It mirrors the external contract, but returns dummy data and completes payments in a simulated flow for validation purposes.
Keep environment-specific secrets separate
If your internal deployment process separates testing and production credentials, keep them isolated and avoid copying secrets between runtime environments.