Settings
Change workspace, integration, key, and webhook configuration while preserving the financial audit trail.
On this page
Before a change
- Confirm merchant and environment.
- Identify the backend or teammate that depends on the setting.
- Record owner, intended result, and recovery plan.
- Test scopes, mappings, and webhooks outside production first.
Settings to review
| Area | Check |
|---|---|
| Workspace | Merchant identity and operational contacts. |
| Access | Who can manage members, integrations, and keys. |
| QuickBooks | Company, consent, sync, invoice source, and mappings. |
| Source links | QuickBooks and each payment destination share the intended merchant and environment. |
| Stripe / Square | Carden keys, scopes, and report activity; provider credentials remain merchant-owned. |
| Webhooks | Destination, selected events, signing secret, and delivery state. |
Rotate a Carden key
- Create a replacement in the same context with minimum scopes.
- Deploy it through the secret manager.
- Confirm new requests and old outbox events succeed.
- Revoke the old key and verify it no longer works.
- Review recent activity if exposure is possible.
Outbox retries retain their original event IDs after credential rotation.
Keep financial settings factual
Approve product codes and units only when they describe the merchant's actual item. Preserve source tax, shipping, discounts, quantities, and references rather than filling unsupported fields with defaults.
A mapping change creates a new invoice revision and never rewrites a preparation snapshot attached to a previous payment.