Notes from the meeting above
Payment retries and idempotency before charging again
Decisions
- Idempotency (protection against double charges) must be handled before retries are added.
- The team will sync again on Friday.
Action items
- Implement idempotency for payments by saving a unique key per order before calling Stripe and reusing it on every retryYou, by Friday
src/payments/charge.tssrc/queue/consumer.tsprisma/schema.prisma - Check the refunds endpoint for the same double-processing riskYou
Plus 3 open questions and a follow-up message, ready to send.

