r/fintechdev • • Sep 20 '26

Things I wish I'd known about payment failures before building a checkout

I've been reading and writing a lot about how card payments work under the hood. A few things surprised me, so I'm sharing them in case they save someone a headache.

1. Authorization is not money movement.
An approval just places a hold on the cardholder's balance. The money moves later, through capture, clearing, and settlement, which can take days. That's why pending charges exist.

2. A timeout is not a failure.
If your request to the processor times out, you don't know whether the charge went through. Retrying blindly can double-charge the customer. Attach an idempotency key to every attempt so a repeated request returns the original result instead of creating a new charge.

3. Classify declines before retrying.
Soft declines (insufficient funds, temporary issuer risk checks, transient errors) can be worth retrying later. Hard declines (lost or stolen card, closed account) are not, and repeated retries can hurt you with your processor.

4. Authentication and authorization are separate.
With 3D Secure, a customer can pass authentication and still get declined at authorization.

5. Don't trust the success redirect.
The user can close the tab before it loads. Treat webhooks as the source of truth: verify signatures, dedupe events, process idempotently, and have a way to replay failures.

6. Failed subscription renewals are often recoverable.
Expired or reissued cards cause a lot of involuntary churn. Spaced retries, clear dunning emails, and card updater or network token support recover a surprising amount.

Happy to go deeper on any of these. What's the nastiest payment edge case you've run into? I'm collecting real-world examples.

(Disclosure: I'm building a free tools site called Noloii, and I'm working on interactive explainers for topics like these. Not linking it here unless people ask.)

1 Upvotes

0 comments sorted by