Skip to documentation content
Carden

Environments

Keep Carden keys, QuickBooks companies, Stripe modes, and Square modes aligned between test and production.

On this page

What the environment controls

ContextMeaning
OrganizationThe merchant whose data is accessed.
IntegrationThe merchant's provider-specific Carden configuration.
EnvironmentThe test or production records and settings for that integration.
API keyOne organization, integration, environment, and set of authorized scopes.

The dashboard selection helps a person navigate, but it never changes the scope of a key already deployed in a backend.

Create a test path

  1. Create a non-production Carden key.
  2. Connect a QuickBooks sandbox company when testing source-backed work.
  3. Use Stripe test mode or Square sandbox in the merchant backend.
  4. Prepare known invoice data and send a test report.
  5. Exercise duplicate reports, denied access, refunds, and delivery timeouts.

Move to production

  • Authorize the intended live QuickBooks company.
  • Create production Carden keys with only required scopes.
  • Deploy keys through the service secret manager.
  • Run a limited provider payment and confirm the report in production.
  • Verify dashboards and exports keep test activity separate.

Resolve a mismatch

Compare the deployed key's merchant, provider, and environment with the dashboard context. Then check QuickBooks realmId, Stripe mode or Square environment, Carden request ID, provider IDs, and report event ID.

Stop a producer that sent merchant data to the wrong context and contact Carden for remediation. Copying records between tenants can break the audit trail.