Environments
Keep merchant identity, Carden keys, QuickBooks companies, and Stripe modes aligned.
On this page
What an environment scopes
An environment separates integration configuration and activity within a merchant organization. API authorization binds a request to an organization and environment, and the integration key determines which service can act there. A UI filter is a view of that context; it is not a replacement for API authorization.
| Identifier | Purpose |
|---|---|
| Organization | The merchant whose data and configuration are being accessed. |
| Integration | The provider-specific connection or API workflow belonging to the merchant. |
| Environment | The test/sandbox or production context attached to that integration and key. |
| Base URL | The origin of the Carden deployment; it does not override a key's environment. |
Use the environment names displayed in your workspace. Keep a small deployment inventory that maps each backend service to its Carden key, Carden environment, QuickBooks company, and Stripe mode.
Set up a test path
- Choose the non-production integration context and create a key there.
- Authorize a QuickBooks sandbox company if testing the accounting connection.
- Use your own Stripe test-mode configuration in your backend; none of those credentials are sent to Carden.
- Send a known test invoice and report. Check the environment in Carden, not just the HTTP status.
- Test duplicate reports, authorization errors, later refunds, and report timeouts.
Move to production deliberately
- Confirm live QuickBooks consent for the intended merchant company.
- Create a new production-scoped Carden key with minimal allowed scopes.
- Deploy the correct Carden base URL and key to the intended service through your secret-management process.
- Keep Stripe live-mode authentication and webhook configuration under your own operational controls.
- Run a limited, approved payment flow and confirm durable report delivery and merchant scoping.
- Verify that reports, dashboards, and downstream analysis do not mix test and production volume.
Resolve a context mismatch
If a report appears missing, compare the key's merchant and environment with your dashboard selection. Include the Carden request ID, event ID, and integration name in your investigation. If you sent real merchant data into the wrong context, stop that producer and contact Carden about remediation; do not copy records across organizations as a workaround.
Report deduplication includes environment. Sending the same eventId with another environment's key does not verify the original delivery and may create a separate record.