Cadence — 2024
Cadence
Payment orchestration layer with idempotent retries across five processors.
The problem
Failed charges were silently double-billing customers when a processor timed out mid-capture and the retry fired against a fresh idempotency key.
What we did
Introduced a durable state machine per payment intent, with processor-agnostic idempotency keys persisted before the outbound call rather than after.
Stack
- Node.js
- PostgreSQL
- Temporal
- Terraform
- AWS
Double-charge incidents
→ 0
Auth success rate
+6.2pp
Processor failover
<900ms