Your Card Was Declined but There's No Transaction Record — Pre-Auth Rejection vs Issuer Decline (2026)
The card has funds, the card is active, the subscription still fails — and there is no charge record anywhere. That is not a broken card. The rejection happened at the merchant's checkout page and the authorization request never reached the issuer. Here is how to tell in three minutes.
1. First, check whether a charge record exists
This single step decides everything that follows. Open your card's transaction history and look for the attempt. If there is no record at all — not even a declined one — the authorization request never left the checkout page: that is a pre-auth rejection. If you can see a declined entry with an amount, merchant name and a decline code, the request reached the issuer. The two have opposite fixes, and getting this backwards costs hours.
2. Pre-auth rejection: the card usually isn't the problem
Before submitting an authorization, checkout pages run their own validations. Any one failing means an instant reject with no charge attempted. The four common ones: (1) the billing name or address is incomplete, or differs from the one you used with this merchant before; (2) your network exit country is far from the card's country — e.g. a US card used from Asia; (3) you're on a datacenter or hosting IP, which scores far worse than residential; (4) 3-D Secure was started but never completed.
3. How to check your network exit
Open ipinfo.io and read two fields. `country` should match the card's country. `org` should not contain IDC, Data Center, Cloud, Amazon or Google Cloud — those indicate a hosting IP, which payment risk engines score poorly. Switch to a residential line in the matching country, then open the merchant site in a private window and pay again. This alone resolves a large share of "the card is fine but payment won't go through".
4. Billing details must be real, complete and consistent
This card is not tied to a personal address, and cocodot does not provide or assign any address. On the checkout page, enter the address you actually use as your billing address, fill in every field, and keep using the same one with the same merchant — never an address found online, someone else's or a made-up one. Many platforms, AI subscriptions especially, check billing details at checkout and reject outright when they are incomplete or keep changing. Related: use your real name when the card is issued. Cards opened with placeholder names like TEST or ABC almost always fail validation, and because it's a pre-auth rejection there is no record to debug.
5. Issuer decline: check the balance covers the FULL amount
Insufficient balance is a common cause, with one trap people miss: many merchants run a small verification charge when a card is added (commonly $0.01–$1) and that one really settles. So the card ends up slightly short of what you funded — fund $20, verification takes $0.05, $19.95 remains, and a $20 subscription now fails forever by five cents while the error only says "declined". Leave a little headroom instead of funding the exact subscription amount.
6. "Authorization approved" does not mean "payment completed"
An approved entry isn't the finish line. Authorization only means the issuer agreed the charge may proceed; the merchant can still void it afterwards, typically when a second risk check fails. The real test is whether the card's settled amount changed. If an authorization shows approved but the card balance never moved, the payment did not complete. Judge by actual settlement, never by authorization status.
7. Don't retry repeatedly after a decline
Repeated failures on the same charge get flagged by the merchant's risk system, and each retry makes the next one less likely to pass — in bad cases the account gets restricted. Correct order: use step 1 to classify the decline, fix billing details and network for pre-auth, fund the card for issuer declines, and only then consider trying a different card BIN. Change one thing, try once.
Two kinds of declines, opposite fixes
| Pre-auth rejection | Issuer decline | |
|---|---|---|
| Where it happens | Merchant checkout (validation) | Issuer (authorization) |
| Charge record | None, anywhere | Yes — amount, merchant, decline code |
| Usual cause | Billing mismatch / country mismatch / datacenter IP / 3DS not completed | Insufficient balance / restricted MCC / risk hold |
| Does a different BIN help? | Usually not — the card isn't the problem | Sometimes — rules differ by BIN |
| Do this first | Fix billing details + change network exit | Fund the card, then read the reason |