You check the balance. It’s there. You try to start a subscription or place an order, and the card declines a charge for $0. Strange, but not random.
The merchant is checking that your card exists, can respond, and has enough available balance for a later payment. The check itself may request no money at all. Your card still needs to pass it.
What a pre-authorisation actually does
A pre-authorisation is a request sent through the card network before a payment is completed. It asks the issuer to confirm that the card is valid and that funds are available. If the request concerns a real purchase, the issuer may place an authorisation hold against the amount.
A hold isn’t the same as a completed charge. It temporarily reduces the amount available to spend while the merchant decides whether to capture the payment. If the merchant doesn’t complete the transaction, the held amount is released rather than taken.
That distinction matters with prepaid cards. Your balance is the money available for card activity. A merchant can ask for a verification response even when it doesn’t plan to collect anything at that moment. If the card can’t meet the network’s check, the response may be a decline.
So a $0 authorisation doesn’t mean the merchant tried to take $0 and failed to find $0. It means the card didn’t pass the verification step attached to the request.
Why merchants send a $0 verification request
Many online services want to check a payment method before they let you start using the service. This is common when you create an account, begin a trial, add a card to your wallet, or prepare a recurring payment.
The merchant may use the response to confirm that:
- the card number is valid and active;
- the card can be used for online payments;
- the payment method is connected to a live account;
- future charges have a reasonable chance of going through.
Sometimes the request appears as a $0 authorisation. Sometimes the merchant sends a small temporary authorisation instead. The exact flow depends on the merchant and the card network, but the purpose is similar: check the card before relying on it.
MPay has specifically flagged this behaviour with ChatGPT, Claude, Spotify, Netflix, and Amazon. These services may verify your card before completing a payment, even when the amount shown is $0.
And this isn’t an MPay quirk. It’s Visa network behaviour that can affect every prepaid card. MPay cards are funded from your available balance, so a verification request can expose the difference between having enough for the purchase and having enough for the merchant’s complete payment flow.
Why an empty balance can decline $0
Here’s the awkward part. A prepaid card with no available balance may fail a $0 verification request even though no purchase amount is being collected.
The card network and merchant aren’t necessarily asking only, “Can we collect zero?” They’re checking whether the card is ready to support the account or transaction. The issuer may need available funds on the card for the verification process or for a related authorisation step.
That’s why a card can work at one merchant and fail at another. A one-off checkout may send a straightforward payment for the order total. A subscription service may first verify the card, then create a recurring billing agreement, then attempt the first payment. Your balance has to survive the opening check before the actual charge gets a chance.
A failed $0 authorisation doesn’t prove that your card is broken. It usually means the available balance was too close to empty for that merchant’s flow.
If you’re unsure how your card details are displayed, MPay’s practical tip is simple: tap the card, hit CHECK, and then view the CVV and expiry details. Keeping those details hidden until you need them is sensible. It won’t replace an available balance, though.
Subscriptions need more breathing room
Subscription services tend to run these checks more often than one-off merchants because they’re starting an ongoing billing relationship. The merchant needs a payment method it can use again later, not only a card that works for one checkout today.
ChatGPT, Claude, Spotify, and Netflix are familiar examples. A service may verify your card when you sign up, then charge the subscription on its billing date. If the card balance is exactly empty, or only just covers the first charge, the initial verification can still fail.
For a subscription, keep a buffer above the recurring charge. The buffer should remain available after the expected payment, not disappear the moment the payment is due. There isn’t a universal amount to recommend because subscription prices, merchant checks, exchange details, and your own card activity vary. The useful rule is practical: don’t fund the card to the exact last cent and expect every verification step to approve.
This also helps when two events happen close together. A verification request may appear around the time the actual recurring payment is attempted. With no room left, one can interfere with the other. With spare balance, the card has a better chance of getting through both steps.
Check the service’s billing date and keep the balance topped up before then. You don’t need to guess at an invented MPay limit. You need enough available funds for the subscription and a sensible cushion beyond it.
One-off purchases still need a cushion
A one-off order is usually easier to judge, but “the order total” may still be too precise. Amazon and other merchants can verify a card before the final payment, and an order can change when shipping, substitutions, or adjustments are involved.
For a one-off purchase, keep enough for the full order total plus a small available balance. MPay’s own guidance is to keep a small balance available for smoother payments when merchants perform a $0 check.
That doesn’t mean parking a large amount on the card. It means avoiding a balance that lands exactly at zero after the expected charge. If the order costs $40, a card funded with exactly $40 has no room for a verification step or a modest change in the final amount. A little headroom is the sensible approach.
And if a temporary hold appears, don’t immediately treat it as a second charge. A held amount is set aside while the merchant completes or cancels the payment. When the merchant doesn’t capture it, the hold is released rather than taken. The timing can vary by merchant and network, so check the app if your available balance looks different after a declined or abandoned payment.
What to do when the $0 check fails
- Check the card’s available balance, not only the amount you intended to spend.
- Add enough USDT or USDC to leave room beyond the expected payment. USDC top-ups are supported on BEP20, ERC20, and Base.
- Try the merchant’s payment flow again after the balance updates.
- Check whether the merchant has saved an old card number, expiry date, or CVV.
- If the card still declines, check the app and the merchant’s own billing settings before repeating the payment several times.
For a closer look at topping up, see how MPay cards work. You can also review the MPay FAQ for supported wallets, chains, and card availability.
Don’t send funds on an unsupported network. MPay accepts USDT through BEP20, ERC20, and TRC20, and USDC through BEP20, ERC20, and Base. Other networks and crypto assets won’t be credited.
The fix is less dramatic than the decline makes it feel. Keep a buffer beyond the actual charge, especially for subscriptions. A $0 request can still require an available balance, and a prepaid card with nothing left has no room to prove it works.
