Your card isn't broken. This merchant blocks your card's BIN.How to tell when a virtual card is refused by a merchant's BIN rules, and the three routes out

Short version first: when your virtual card keeps getting declined at one overseas merchant (say the ChatGPT / OpenAI checkout, some sites that collect through Stripe, or certain streaming services), a lot of the time it's neither a broken card nor your bank blocking it. It's that this merchant has put the prepaid or virtual-card BIN range on a blacklist. The same card swipes fine elsewhere and just won't go through here. Get that straight first and you'll know whether to change the card or change the route, instead of hammering retry on the same card. This guide is for people whose card works fine elsewhere but keeps getting refused by one or two specific merchants. If your card fails everywhere, that's more likely an issuer-side problem, so read the other guide first. This one covers the diagnosis and the routes out only; it makes no compliance call for any country or region.

First, tell apart "your card declined" from "this merchant won't take this card"

A decline comes in two kinds. The source is completely different, and so is the fix. Confuse the two and you'll spend effort in the wrong direction.

• Issuer side: your card is declined. Your bank or issuer's risk system stopped the transaction. This kind of decline usually "follows the card": it may ask you to verify in the banking app, report "insufficient funds", or flag "suspected risky transaction", and it can hit the same way on another site too. How to read those errors and add a verification step is covered in more detail in the other guide, "Your card is fine, the overseas site just won't take it", so it isn't repeated here.
• Merchant side: this one won't take your type of card. Your card is perfectly fine, the funds are there, and your issuer is happy to let it through, but this merchant, under its own rules, simply won't accept a card of your type. The tell-tale sign is "the same card swipes fine elsewhere and only fails here". It "follows the merchant", not your card.

One line to tell them apart: if the decline follows the card, it's usually issuer side; if it follows one particular merchant, it's usually merchant side. This guide only covers the latter, the case where a virtual card gets blocked by one merchant's card-range rules. To confirm whether it's really an issuer problem, read Your card is fine, the overseas site just won't take it first.

Why merchants specifically block prepaid and virtual-card BINs

To make sense of this, start with what a BIN is. The first few digits of a card number (usually the first six to eight) are the BIN, the bank identification number. It doesn't just reveal which bank issued the card; it also broadly reveals whether the card is a credit, debit or prepaid card, and whether it came from an outfit that specialises in issuing virtual cards. From those few digits, a merchant and its risk system can tell "what type of card just walked in" and apply rules by type.

So why single out prepaid and virtual cards? Because that kind of card has a worse risk profile in a merchant's eyes. Here's the mechanism, without inventing numbers. A few common reasons:

• Chargebacks and fraud are harder to handle. Prepaid and one-time virtual cards aren't easily tied to a real identity, and once one is used for fraud or a malicious chargeback, the merchant has a harder time recovering the loss. To hold down that kind of bad debt, some just take fewer of these cards at the source.
• One-time cards get abused. Some people use mass-generated virtual cards to keep claiming "first month free" or "new user" offers, or to get around subscription and regional limits. To close that gap, merchants often block by BIN range, sweeping up the good cards with the bad.
• Default rules from the risk vendor. Many sites don't write their own risk logic; they plug in a third party (something like Stripe's Radar). Those tools often ship with rules that are stricter on prepaid and high-risk BINs, and if the merchant leaves the defaults on, your card runs straight into them.

So it isn't personal. This merchant, or the risk vendor behind it, has set a default barrier against a whole class of card ranges. You did every step right and the card still gets held at the door; the problem is the card's "type", not what you did.

How to tell whether what you hit is a BIN block

One decline on its own won't tell you which kind it is; you have to read a few signals together. When these three all hold, it's basically a merchant-side BIN block:

• The same card swipes fine on other sites and other merchants. That says the card and the issuer are both fine, and the trouble is concentrated on "this one".
• The error is "please use a different payment method" or "we can't accept this card", not "insufficient funds", "verification needed" or "declined by your bank". The former is the merchant saying "we don't take this kind of card"; the latter is the issuer-side wording.
• Switching to a different-BIN card goes through. Especially if moving from a "prepaid or virtual-card BIN" to a "credit or debit BIN" then swipes, that pretty much confirms the range is being blocked.

The flip side, as a reminder: if you've tried several different-BIN cards on the same device and the same account and they all get declined, or the error explicitly names "your bank", then it's more likely not a plain merchant BIN block, and you should go back to the issuer-side line to check rather than keep fighting this one merchant.

Decode: what "please use a different payment method" is really saying

That decline line on the checkout page tends to be phrased vaguely, but in the virtual-card case it often hides a very specific meaning. Here's the most common one, taken apart.

Three routes out: change the card, change the method, go stablecoin

Once you've confirmed it's a BIN block, forcing the same card gets you nowhere; only three routes actually change the outcome. Each has its own cost, so pick by your situation rather than insisting on one.

• Route one: switch to a card on a different BIN type. The point is to move from the "prepaid BIN" in your hand to a "credit or debit BIN" the merchant is more likely to accept. When picking a provider, ask straight out: which BIN does its card run on, is it a prepaid range, and can it swipe at the kind of merchant you're paying. Don't compare on price alone; the BIN type and where it works are what matter here. How to ask and what to check is in Choosing a virtual card provider: don't look at price alone. The cost: you may have to find a new provider and top up again, and a service that issues "cleaner" ranges usually has a higher bar.
• Route two: switch to another method the merchant officially accepts. Many sites list their officially supported payment methods on the checkout page or in the help centre (other card networks, certain wallets, or platform balance). Rather than fight a blocked card range, switch to one on the official list. OpenAI's billing help page, for instance, spells out which payment methods it supports, and following that is the least hassle. The cost: an officially accepted method isn't guaranteed to be available where you live, and you may have to set something else up.
• Route three: when the merchant clearly supports crypto, go stablecoin or Binance Pay. If this merchant clearly states on its checkout page or in its help docs that it takes crypto, or supports some crypto payment, that route sidesteps the card-range issue entirely, because it never touches a bank card's BIN. This one usually means holding a stablecoin like USDT first. The cost and the prerequisite are spelled out below, and don't treat it as a cure-all: only use it when the merchant says so, since pushing a merchant that doesn't take crypto down this route makes no sense.

Run down this list before you change card or route

Whether you plan to change card or change method, tick these off before you start and you'll save most of the wasted effort.

• Confirm the card swipes fine on another site first, ruling out a "card or issuer" problem, before deciding it's this merchant's BIN block.
• Before switching provider, ask straight out which BIN the new card runs on (credit, debit or prepaid), and whether it clearly supports the merchant you're paying.
• Open the target merchant's official checkout page or help centre, see which payment methods it officially lists, and favour those on the list.
• Only consider the stablecoin route when the merchant clearly supports crypto; if you're unsure, don't rush into it.
• Whichever route you take, test a small amount you can afford to lose first, and scale up only once it works.
• Don't get led along by "pay an unlock fee and it'll swipe" or "let me pay it for you".

A few questions people ask

The same card works on other sites, so why won't this one take it?

Because the refusal happens on the merchant's side, not on your card. This merchant, or the risk system it uses, has put your card's BIN range on a restricted list, usually aimed at prepaid and virtual cards. The card and the issuer are both fine; this one merchant just won't take it under its own rules, which is why another site is usually fine.

What happens if I keep retrying the same card?

It won't get past a BIN block, and it can make things worse. A string of failures in a short window can look like fraud to your issuer's risk system, which may lock the card temporarily, turning a this-merchant-won't-take-it problem into a this-card-works-nowhere problem. The right move is to test a small amount on a different-BIN card, not to keep tapping retry on the same one.

Will switching to another virtual card definitely go through?

Not necessarily. It comes down to whether the new card's BIN is a type this merchant is willing to accept. If you just swap to another card on the same prepaid or virtual-card BIN, it may well be blocked too; a credit or debit BIN stands a better chance. So before switching, ask the provider which BIN the card runs on and whether it supports the merchant you're paying, and don't expect any random swap to sail through.

Sources to check: this guide gives no specific fees, decline rates or "it'll definitely swipe" promises, and makes no compliance call for any country or region. Whether a given merchant takes a given card type and which methods it supports go by that merchant's official checkout page or help centre at the time; which BIN a provider issues goes by the provider's own notes; for local compliance, consult a professional where you are. Updated 2026-07-04.

References

• OpenAI Help Center: Billing & payment
• Binance: official fee schedule (spot trading)

These are the platforms' own official pages, for verification only; the exact rules and fees follow each official page at the time.