// case study 04/05 · payments · backend · now

Backends that never double-charge

result

100% data integrity across production migrations, each one validated by a parallel run before cutover. Zero-downtime releases.

problem
Bank GIRO collections and refunds, plus migrations on data that can't be wrong.
approach
Idempotency keys, queued retries, reconciliation; parallel-run validation before every cutover.

Key decisions

Stack

NestJSPostgreSQLRedisNSQ

see idempotency, locks and retries animated →