Four parties can refuse, and only one of them is us
A card payment passes through four hands before it succeeds, and any one of them can stop it. The reason most decline advice is useless is that it treats them as a single event.
- The merchant's checkout form. Before anything is sent anywhere, the page validates what you typed — the number, the expiry, and often a name and a billing address. A failure here never reaches us.
- The merchant's own rules. Some businesses refuse prepaid cards outright, or refuse them for one product line. This is a policy, not an error.
- The 3-D Secure step, when the merchant asks for one. A challenge that is not answered in time fails on its own.
- Us, the issuer. We check three things and nothing else: is the card active, does the balance cover the amount being authorised, and does that amount fit under the card's monthly cap.
That last line is worth reading twice, because it is the whole of our decision. We do not score you, we do not refuse a merchant category, and we do not block a country. If a payment failed and the balance, the card status and the cap were all fine, the refusal was not ours — and no amount of topping up will fix it.
Here is how to tell which hand it was.
| What you saw | Who refused | What to do about it |
|---|---|---|
| Refused by the form | The merchant | A field failed validation, or the merchant blocks prepaid cards outright. See the name and address fields. |
| "Insufficient funds" | Us | There is money on the balance, but the merchant asked to hold more than the price. See the hold. |
| "Card declined", no code | Us | The card is frozen, or its monthly cap is already used up. Both are visible on the card in your dashboard. |
| A code, then failure | The 3-D Secure step | The challenge expired before it was answered. Start the payment again for a fresh one. See 3-D Secure. |
| Only at one merchant | The merchant | That merchant refuses this card type. A wallet payment sometimes goes through where the raw number does not. |
The hold is bigger than the price
This is the single most common decline on a prepaid card, and the most confusing, because the balance looks sufficient right up until the moment it is not.
A card payment happens in two steps. First the merchant authorises an amount — money is set aside, nothing has moved yet. Later they capture what was actually owed. For an online purchase the two figures are identical and you never notice. For a whole family of merchants they are not, and the gap is deliberate:
| Where you pay | What is authorised | Balance you need |
|---|---|---|
| An online purchase | The exact price | The price |
| A $40 fuel stop | A figure set by the pump, well above the fuel you take | The authorised figure |
| A hotel, on arrival | The stay plus a margin for incidentals | The authorised figure |
| Car hire, at the desk | The rental plus a deposit | The authorised figure |
| A restaurant | The bill plus a tip allowance | The authorised figure |
Read the second row. A $40 tank of fuel can be refused on a $60 balance, because the pump did not ask for $40 — it asked to hold a figure large enough to cover whatever you might pump, and it asked for it before a drop came out. The fuel costs $40. The authorisation does not.
The arithmetic on our side is exactly this, with no discretion in it:
- the payment passes when balance ≥ the amount authorised;
- and, if that card carries a cap, when already spent + the amount authorised ≤ the cap.
Both use the authorised figure, not the ticket. So the practical rule for anywhere that holds — pumps, hotels, car hire, restaurants, and any deposit — is to leave real headroom on the balance rather than the exact price. Top-ups after the first start at $100, so the headroom is cheap to arrange and you get it back: what a merchant holds and does not capture is released, and it returns to your balance in full.
Two consequences people meet later. The release is the merchant's to make, not ours — a hotel that authorises on arrival typically releases days after you leave, and we cannot shorten that. And a hold counts against a monthly cap while it is open, so a capped card can decline its own subscription because a hotel is sitting on part of the ceiling.
The way to avoid all of it is boring and effective: pay at the desk rather than at the pump, and give merchants that hold their own card rather than the one your subscriptions use.
The name and address fields, when the card has neither
Our cards read NO NAME REQUIRED, because there is no name on the account to print. The account has no billing address either — none was ever collected. That is the point of the product, and it is also a checkout problem that no provider in this category documents. So, plainly:
- The name field. Most checkouts accept anything here; it is passed on but rarely verified. Where a merchant does check it, there is nothing to match.
- The billing address and postcode. Some merchants — mostly in the United States and the United Kingdom — run an address check on what you type. A card with no address on file cannot return a match. For most merchants that is a signal they weigh; for a few it is an automatic refusal, and there is no field you can fill in that changes it.
What actually works, in order:
- Pay with the card in a wallet instead. A card added to Apple Pay or Google Pay is presented as a device token, and the merchant's address check is not part of that flow. This is the fix for most of these declines, and it costs nothing to try — how to add the card.
- Fill the address in anyway where the form will not submit without one. Most merchants only record what you type; they never compare it to anything, because there is nothing on our side to compare it against.
- Move on. If a merchant hard-refuses on an address check, the payment cannot be made to work from your end. That is a real limitation of a card opened without an identity, and pretending otherwise would waste your afternoon.
The 3-D Secure step, and the ways it fails quietly
When a merchant asks for 3-D Secure, we send a six-digit code to your account email — never by SMS, because there is no phone number on the account. Three things go wrong here, and they look identical from the checkout page.
The challenge expired. A challenge has a short life by design; that is what stops an old code being replayed. Once it lapses, entering the code does nothing and the payment fails. The fix is to start the payment again, which opens a fresh challenge — not to hunt for the old email.
The code went to an address you cannot open. The email address is not a marketing channel here, it is the authorisation channel. If you signed up with an address you check once a month, every 3-D Secure payment will time out. Change it before you need it.
Two of your cards end in the same four digits. A challenge arrives identified by the last four digits of the card. If two active cards on the account share those four digits, we refuse the challenge rather than guess which card is paying — and the payment fails with no code sent at all. You may hold up to 5 cards, so the collision is uncommon but not impossible. If a 3-D Secure code never arrives at all, this is the thing to check that nobody thinks of: look at your card list, and delete or replace the duplicate.
If you check out from your own systems, none of the above needs an inbox: the code is readable
under the 3ds:read scope and resolvable with 3ds:write, so a script can
answer the challenge in the second it is opened. The
3-D Secure guide covers the whole flow, and the
API reference has the endpoints.
The refusals that happen before we see anything
Some merchants will not take this card, and no change on your side alters that. It is worth recognising the pattern so you stop retrying.
- Prepaid cards are refused as a class. Car hire, some airlines and some hotel groups require a card they can charge after you leave, and they identify prepaid cards from the number itself. The refusal is instant and identical every time.
- The purchase counts as quasi-cash. Money transfers, gambling deposits, gift-card purchases and buying crypto with a card are commonly blocked by the merchant or their acquirer, whatever card you present.
- The merchant wants a named account. Anything that will chase you for money later — contracts, deposits, post-paid billing — tends to insist on a card with an identity behind it. Ours does not have one.
- The merchant's own fraud score. A card with no history, used from an unusual location on a first order, sometimes fails a rule that has nothing to do with the card working.
The tell is consistency: a card that pays everywhere else and fails at one merchant, identically, on every attempt, has met a policy rather than a fault. Retrying is the one thing that cannot help — and on a fraud score, repeated attempts make the next one likelier to fail, not likelier to pass.
What to check, in order
Thirty seconds, in this sequence, resolves nearly all of them. The order matters: each step is cheaper than the one after it.
- Compare the balance to what was authorised, not to the price. If the merchant holds, assume the figure is higher than the ticket and add headroom.
- Check the card is active. A frozen card refuses everything, including a one-cent verification charge.
- Check the card's cap. Look at what has been spent against it, and remember an open hold is occupying part of it.
- Check your email for the 3-D Secure code, and if one arrived late, restart the payment to get a fresh challenge instead of reusing it.
- Pay through Apple Pay or Google Pay if the checkout demanded a name or a billing postcode. This is the step most people skip and it is the one that most often works.
- Try a different card on the account, or raise the cap on this one. A fresh virtual card costs $2 and is live immediately.
If all six pass and the payment still fails, the refusal was the merchant's. At that point the useful move is a different merchant or a different payment method, not another top-up.
Three declines that mean the card is working
Not every refusal is a fault, and treating these as bugs is how people disable the protection they asked for.
A frozen card declines everything. That is its entire job, it takes effect instantly, and it reverses in one tap. If you froze a card and forgot, the decline is the freeze reporting for duty.
A cap that refuses a renewal is doing what you set it to do. A subscription that comes back at a higher price is supposed to fail loudly rather than pass quietly — that is the reason to give each merchant its own capped card in the first place. Raise the cap if you accept the new price; leave it if you do not.
A deleted card declines permanently. Deleting is not pausing. If you might come back to a merchant, freeze instead — a frozen card still holds its slot and can be brought back.
And one that is not a decline at all: a merchant refund does not go back to the wallet you funded from. It returns to your balance, where it is spendable again and where it starts earning the balance rate the same evening.
Frequently asked questions
Why was my crypto card declined when I had enough balance?
Almost always because the merchant authorised more than the price. Fuel pumps, hotels, car hire and restaurants routinely hold a figure above the ticket, and the check runs against the authorised amount, not against what you expect to pay. Leave headroom on the balance rather than the exact price — what is held and not captured is released back to you.
What name and billing address do I use at checkout?
The cards read NO NAME REQUIRED, and there is no billing address on the account because none was collected. Most checkouts accept anything in those fields. Where a merchant runs an address check, nothing can match — pay through Apple Pay or Google Pay instead, which does not use that check.
Does a declined payment cost me anything?
No. There is no fee for a refused authorisation, and no fee for paying with the card at all. The only charge on the way in is 1% on a top-up. If an authorisation was placed and then not captured, the amount is released and returns to the balance in full.
The 3-D Secure code never arrived. What now?
Check three things in this order: that the account email is one you can actually open, that you are not entering a code from an earlier expired challenge — restart the payment to open a fresh one — and that no two active cards on the account end in the same four digits, because a challenge that cannot be attributed to one card is refused rather than guessed.
Why does one particular shop always decline my card?
That merchant refuses prepaid cards, or refuses that purchase category. Car hire, gambling deposits, money transfers and buying crypto with a card are the usual ones. The signature is that it fails identically every time while the card works everywhere else, and retrying cannot change it.
My subscription was declined even though nothing changed.
Look at the card cap before the balance. A renewal at a slightly higher price — a tax change, a currency conversion landing a few cents high — fails against a cap set exactly at the old amount. An open hold from another purchase on the same card also occupies part of the cap until the merchant releases it.
Product references and further reading
Published by CryptoCard. Product terms, eligibility and third-party features can change; use the linked reference for the current details.
Get your card
An email address, a first top-up from $100, and the card is live. No document, no phone number, and the first virtual card is free.