Webhooks

Idempotency, retries, and signatures — the core of a real workflow system.

How we're different

Workflows are idempotent.
State lives in the database.
Every action is logged.

Trust rule: AI drafts, humans approve sensitive actions.

Principles

Idempotency: the same event processed twice must not create two cases.
Retries: transient failures should be safe to retry.
Signatures: validate source authenticity when available.

Local MVP endpoint

For the MVP, Stripe webhook handling is simplified; production deployments enforce signatures and idempotency keys.

POST /api/chargewise/webhook/stripe

Recommended patterns

Store processed event IDs per integration.
Write audit event for every webhook received.
Retry with backoff and dead-letter queues for poison messages.