My subscription charge failed — is the card broken?
Almost certainly not. We audited every failed AI-merchant charge on the platform: zero were issuer declines, zero AVS failures, zero merchant-category blocks. All were user-side: limit too low (~45%), insufficient balance (~35%), typos in card details (~20%) — each fixable in minutes.
"Your card was declined" — that one line is all the merchant tells you. It never says where along the way the charge actually died, so "the card is bad" becomes the most natural guess. But every charge, from the moment you click pay to the moment it settles, has to clear three gates in a row. Each gate checks something different and leaves a different trail. Once you can see all three, you can pinpoint your case and fix it in a few minutes.
Every charge has to clear three gates
| Gate | Who is gatekeeping | What it checks | Failures that die here |
|---|---|---|---|
| Gate 1 | Merchant front-end risk control (OpenAI / Stripe, etc.) | Account age, IP quality, behavioral patterns — it screens the account, not the card | One kind of zero-record failure: the request never even reaches the card (the other kind of zero-record failure happens at Gate 3, see below) |
| Gate 2 | Card network and payment channel | Whether the card number format is valid and can be routed to the issuer — pure format validation, no checking whether the details are genuine | Only hard defects like a malformed card number; usually leaves no record either |
| Gate 3 | Issuer | Verifying and comparing: whether the card details (expiry, CVC) match; whether this charge falls within the remaining limit and the card balance | Limit too low ~45%, insufficient balance ~35%, mistyped card details ~20%; note: a limit pre-check decline may leave no charge record |
The candidates that would truly mean "the card is bad" — an issuer risk decline, an AVS address-verification failure, a merchant-category block — are not a fourth gate. They happen inside that same single authorization decision at Gate 3, the issuer. And our full audit found all three at exactly zero cases, with a 100% card-verification pass rate. In other words, the card-side failures that actually occur come down to just three mechanical causes — limit, balance, and typos — and not a single one is a card killed by risk control. There is also no SMS verification step anywhere on this path (charging cards in this range needs no SMS verification code), so "I never got the verification code" is not among the candidate causes either.
The issuer only does a mechanical check — there is no gray area
When the issuer receives a charge request, it does just two mechanical things: verify and compare. It verifies the card details — whether the expiry and CVC match what is on record; and it compares the amount — whether this charge exceeds the remaining limit or the card balance. If everything matches, it approves; if any single item fails, it declines. There is no credit assessment, no risk scoring, no "depends on the mood."
A real case: a card with a $17.64 limit passes card verification in full, buys $10 of API credit successfully (leaving $7.64), then fails to buy $16, and fails again trying $10. The same $10 that went through the first time won't go through the second time — that isn't a broken card, it's that 7.64 < 10; the earlier successful charge itself consumed the limit. This case has one more key detail: neither of the two failures left even a single record in the account statement — the issuer's limit pre-check declined them outright, without producing an authorization record at all. So "zero records in the statement" cannot be read directly as "the request never reached the card"; check the limit first, then draw a conclusion.
This is also why a subscription should be estimated at the tax-inclusive amount you actually pay: a US $20 plan actually costs $20–22 to pay (some states charge sales tax), and certain past-due back-charge forms can reach $25. A card capped right at $20 will most likely die on the tax.
Retry storms: the one move that turns a small problem into a big one
On the issuer side, the outcome is deterministic: if you haven't changed the card details and haven't topped up the limit or balance, you'll get the same "decline" a hundred times over. But on the merchant risk-control side, the same card failing repeatedly in a short window is exactly the signature of "card testing" by a fraudster, and back-to-back declines drive up the account's risk score — in bad cases getting it temporarily frozen. A real case: the same cause is declined 8 times in 7 minutes; after stopping to adjust the limit, the same amount goes through on the first try 5 minutes later — none of the first 8 was "almost approved," they were just piling up a risk score. Cards with an independent limit are also charged an extra $0.60 per failure (the upstream cost passed through at cost; cards with a shared limit are exempt), so 8 back-to-back declines is nearly $5 thrown away for nothing.
Targeted fixes: a checklist you can run in a few minutes
- Locate it first: open the account statement on the card details page and match against three situations. (1) There's a failure record (with a specific reason) = it reached the issuer, so it's a limit, balance, or typo problem — fix it per items 2–4. (2) Completely zero records: run the zero-cost self-check first — is the remaining limit enough for this charge's tax-inclusive estimate (figure $22 for a subscription, reserve up to $25 for a past-due back-charge)? If not, the issuer's limit pre-check blocked it without leaving a record (the $17.64 case above is exactly this), so top up per item 2. (3) Limit confirmed to be ample yet still zero records = merchant front-end risk control blocked the account (account too new, poor IP); switching cards won't help — switch to a clean network first and use an account with a payment history. The account-side pass rate is outside the card's control.
- Limit too low (~45%): the card limit is a one-time total pool, separate from your platform balance, and every successful charge draws it down. If the remaining limit is below this charge (estimate $22 for a subscription, reserve up to $25 for a past-due back-charge), top up the card first — 2% service fee, credited instantly.
- Insufficient balance (~35%): the shortfall is usually $5–40; just top up the small difference, which also takes effect instantly.
- Mistyped card details (~20%): the issuer can catch this one and will leave a failure record in the statement. Go back to the card details page and paste each item — card number, expiry, CVC — using the copy button rather than typing by hand; mind the month / year order on the expiry; make sure the billing address matches, character for character, the one on record on the card details page (every card comes with a real US billing address that you can view and edit); and watch out for the browser autofilling an old address.
- After fixing, try only once: if it fails again, the cause has most likely changed to a different one — go back to item 1 and locate it again; once you hit 2–3 cumulative failures, stop and investigate rather than clicking repeatedly.