Free checklist · Payments engineering

Your checkout can charge a customer twice.

Wi-Fi drops, the app retries, and now you're refunding, apologising and paying dispute fees. Here are the 5 fixes Stripe uses, with the code to copy them.

What's inside

  • Idempotency keys: retries replay the first response instead of charging again
  • Hosted card fields: card numbers never touch your server
  • Double-entry ledger: every transaction sums to zero, so lost money gets caught
  • Verified webhooks: fake "paid" events get rejected, retries get deduped
  • Checkout-first rate limits: reports slow down before checkout ever does
  • A 10-minute yes/no audit to find your gaps