Logs
Trace source, preparation, payment, and report activity with stable identifiers and safe diagnostics.
On this page
Save correlation identifiers
| Identifier | Purpose |
|---|---|
| x-carden-request-id | One Carden HTTP request. |
| preparation.id | One immutable source-backed preparation. |
| snapshotId / revision | The invoice state and source-and-mapping revision used. |
| attemptId | One actual payment attempt. |
| eventId | One immutable payment observation. |
| Provider object and event IDs | Stripe or Square records associated with the attempt. |
Keep the complete relationship in the merchant backend. Carden Logs index audit fields such as event type, message, entity ID, request ID, and actor; they do not provide a universal search index over every report field.
Investigate in order
- Select merchant and environment.
- Start from the merchant attempt record and saved Carden IDs.
- Identify source, preparation, provider execution, report delivery, or settlement as the failed stage.
- Compare the result with that stage's source of truth.
- Correct and retry only the safe failed operation.
Keep logs safe
- Record stable IDs, status codes, safe error codes, and timezone-aware timestamps.
- Redact API keys, authorization headers, OAuth tokens, webhook secrets, payment sources, and provider client secrets.
- Store raw source or settlement evidence only in approved access-controlled systems.
- Limit exports and logs that contain merchant or customer business data.
Prepare a support request
Provide merchant, environment, provider, operation, request ID, event or sync-run ID, time range with timezone, and expected result. Share redacted examples through the agreed support channel.