What should I do after a failed charge?
Stop — don't hammer retry. The cause won't disappear, and rapid failures can trip the merchant's risk system. Open the card detail page's transaction list, read the decline reason (limit / balance / wrong details), fix it, then try once.
After a payment fails, the two least useful instincts are to click again immediately or to switch to a different card right away. For a subscription charge to succeed, it has to clear three gates in order: the merchant's front-line risk controls (which check your account and IP, not the card), the card network's format validation, and the issuer's mechanical check (card details + limit + balance). A failure isn't bad luck; it is deterministically stuck at one of these gates. So the right answer to "what should I do" is not to retry and hope, but to first pinpoint which gate it died at, and then act only on that one.
Work through it in this order, instead of retrying on instinct
- Stop immediately; don't click a second time yet — the cause hasn't been pinpointed, and retrying only deepens the problem.
- Open the transaction list on the card detail page and locate the failure record for this charge.
- Check whether there is a record: if there is, fix it according to the three card-side causes; if there is none, first check the limit yourself, then investigate the account (see the two tables below).
- Once you've fixed the right thing, try only once more.
- If it still fails after a correct fix, stop and submit a support ticket; don't fall into a loop of repeated retries.
Whether there's a record in the transaction list determines whether the request reached the issuer
Whether the transaction list contains a failure record for this charge is the watershed of the entire diagnosis. If there is a record, the request made it through the merchant's risk controls and reached the issuer, the problem is on the card side, and you can fix it yourself. If there is no record, the request never got past the merchant's gate, fixing the card is pointless, and you should redirect your attention to the account and network.
| Transaction list status | Did the request reach the issuer? | The real root cause | Correct action (switch card / retry?) |
|---|---|---|---|
| A failure record exists and states a reason | Yes | A mechanical card-side problem: one of limit, balance, or card details | Fix it on the same card according to the stated reason (raise the limit / top up the balance / recopy the details), then try again; no need to switch cards |
| No record at all in the transaction list | No | First check yourself whether the card limit covers this charge including tax (estimate $22 for a subscription, $25 for a past-due back-charge); if the limit is enough but there's still no record, the merchant's front-line risk controls have blocked your account | If the limit is too low, top up the card first; if the limit is enough, go fix the account / network environment — switching cards or continuing to retry won't help |
Failures that reached the issuer have only three mechanical causes
| Failure cause | Approximate share | Typical appearance in the transaction list | Targeted fix |
|---|---|---|---|
| Insufficient limit / balance | About 45% + 35% | The card's available limit / balance isn't enough to cover this charge including tax | Top up the card from your platform balance to make up the shortfall (2% fee, credited in real time); top up until it covers this charge, then try again |
| Wrong card details | About 20% | One of the card number / expiry date / CVV / billing address is entered wrong | Go back to the card detail page and recopy each field one by one using the copy button next to it; don't type them by hand |
Here is a counterintuitive fact that has been confirmed by checking every transaction one by one: card-side mechanism-based declines are all zero — merchant category blocks, issuer risk-control declines, and AVS billing-address verification failures have never occurred. In other words, as long as the request reaches the issuer, the failure cause falls into one of the three above, and all three you can fix yourself, with no need to switch cards.
Retrying the same charge over and over is definitely useless and only raises your account's risk score
All three gates are mechanical judgments: if the input doesn't change, the result won't change. A moment ago it failed because the limit was a little short, one digit of the CVV was copied wrong, or the account had already been flagged as risky by the merchant — click again without changing any input and none of that changes. Worse, the same card being declined repeatedly at the same merchant gets logged by the merchant's risk model, raising your account's risk score and, in severe cases, temporarily freezing the account. So there is only one correct action: pinpoint the cause, fix it, and try once more; if it still fails, stop and submit a support ticket. Treat 2-3 attempts as an absolute ceiling, not a recommended action — you shouldn't click even once before you've pinpointed the cause, and blindly trying a third or fourth time only drags a problem you could have self-fixed into a harder one.
Independent-limit cards charge $0.60 per failure; shared-limit cards are free
Whether a fee is incurred depends on the card tier. Shared-limit cards (the platform's main card tier) incur no fee when declined; independent-limit cards charge $0.60 per failure, which is the upstream issuer's cost passed through at face value — we add nothing. This is also a practical reason not to retry blindly: on an independent-limit card, every additional failed attempt is another $0.60. Keep the limit and balance topped up and copy the details correctly, and this fee simply never arises.