Stripe API bugs that only appear with real traffic
Most of these come from retries, concurrency or volume, which a developer clicking through checkout alone never produces.
A retry charges the customer twice
How you'll know: A request timed out, your code tried again, and now there are two payments for one order.
Fix: Send an Idempotency-Key header on every POST, generated once per order or action (a UUID works). Stripe returns the first result for a repeat. Keys can be up to 255 characters, are kept for at least 24 hours, and Stripe rejects a reuse with different parameters.
Signature checks fail only in production
How you'll know: The webhook endpoint returns 400 for every event, though the same code passed against the CLI.
Fix: Your framework parsed the JSON before Stripe's library saw it. Verification needs the raw request body. Also check you're using the signing secret for this endpoint in live mode; sandbox and live have different ones.
Events arrive out of order, or twice
How you'll know: An invoice.paid lands before the invoice.created it depends on, or an order gets fulfilled twice.
Fix: Stripe doesn't promise order and can deliver an event more than once. Store each event ID you've processed and skip repeats. If you need the related object, fetch it from the API rather than waiting for its event. In live mode Stripe keeps retrying a failed delivery for up to three days.
Webhook payloads don't match your SDK
How you'll know: Fields your code expects are missing or renamed in events, though API responses look fine.
Fix: Each webhook endpoint has its own API version. It defaults to your account's version unless you set one when you create the endpoint, and the version your code sends per request doesn't change it. Typed SDKs such as .NET, Java and Go need the endpoint's version to match the SDK's, so set it explicitly and change it on purpose.
429 errors in a sale or a backfill
How you'll know: Requests fail with 429 Too Many Requests, and the Stripe-Rate-Limited-Reason header says which limit you hit.
Fix: The global limit is 100 requests a second in live mode and 25 in a sandbox, with most single endpoints capped at 25. Back off with jitter and queue bulk jobs. Don't load-test in a sandbox: its lower limits fail tests production would pass.
Polling instead of listening
How you'll know: A job checks every open PaymentIntent every few minutes to see if it's paid.
Fix: Stripe expects read requests to average no more than 500 per transaction over 30 days (with at least 10,000 a month allowed). Webhooks tell you when something changes, so you only read what moved.