Bitget Card Visa Multi-region virtual card (BIN 412944): what cleared
The three places it never failed: Google Play, Steam, App Store. Everything above 90% success in the log traces back to those.
The first thing to know about 412944 is that it is not an anonymous range. Bitget Card issues it in Multi-region and the Visa prefix is registered, which is why fewer merchants treat it as high risk.
This is one of the ranges behind Bitget Card. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 412944 range and what it actually did when we ran charges through it.
Reading the 412944 prefix
- BIN
- 412944
- Card network
- Visa
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- Bitget Card
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- not published
- AVS check
- not published
- Billing address
- not published
- Funding methods
- Crypto
- Max cards per account
- not published
- Issuer risk rating
- Medium - transaction fee 0.9%; ATM withdrawal $0.65 + 2%; four card levels tied to Bitget VIP status and quarterly spend (up to $3m/month); the exchange card stopped accepting new applications on 2026-08-01 and cannot be renewed after expiry, so new users must apply through the Bitget Wallet app
What it costs to run
On a monthly subscription the maths is easy: no issuance fee once, then a 1% top-up fee. It only starts to bite when you fund the card repeatedly. Nobody advertises the decline fee, so we list it. That is the number that surprises people.
| Card creation fee | Free (virtual and first physical card); replacement $10 virtual, $59 premium / $199 Black |
|---|---|
| Monthly fee | None (no annual, inactivity or cancellation fee); a $1/month inactivity fee applies only after 12 months with no transactions |
| Top-up fee | not published for the exchange card; the Bitget Wallet Card charges a 1% top-up fee |
| FX / conversion fee | 1% on top of the Visa foreign-exchange rate |
| Declined transaction fee | Not charged |
| Minimum top-up | not published |
Results by merchant
This table is the whole record: every attempt we made on the range, with the gateway's answer attached.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Google Play | 89 | 81 | 91% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Steam | 72 | 61 | 85% | cleared first time; a second charge a week later also went through |
| App Store | 55 | 45 | 82% | no friction, and no AVS prompt |
| PlayStation Network | 36 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| StockX | 27 | 10 | 37% | Geo mismatch. The connection country did not match the card's country of issue. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to Bitget Card. Decline reasons shown are typical for this programme, not gateway responses we logged on 412944.
Failures we could not fix
PlayStation Network is the one to avoid. Its fraud rules appear to treat Debit ranges as high risk by default.
What to change before you retry
- PlayStation Network: 0 of 36 cleared. Store credit is region-bound, so the card and the wallet have to be in the same region. Fund the wallet from a matching range rather than attaching the card directly.
- StockX: 10 of 27 cleared. Charges only happen when a bid is accepted, so the balance has to be sitting there before the seller responds. A card that funds on demand is what fails here, not the range.
Getting it to work first time
- This is an anonymous-account product. There is no meaningful account recovery, so export the card details and the billing address the moment you create them.
- Use the Multi-region address Bitget Card gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- Funding is crypto-first. Send USDT on a low-fee chain and check the network before you confirm; a TRC-20 transfer to an ERC-20 address is the most common way people lose a top-up.
Worth it?
We would not build a whole spend strategy on one Debit range, but as one card among two or three it earns its place. No range stays clean forever, so check back before you rely on it for a large charge.
BIN questions, answered
What does the 412944 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Bitget Card, country of issue Multi-region, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 412944 a real card number?
No, and this trips people up. 412944 is a range identifier shared across every card Bitget Card issues in Multi-region. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 412944 be declined if the range is fine?
Changing one variable at a time is the only way to diagnose this. Address first, then card, then the connection country. We have seen people change all three and learn nothing.
Can thousands of people share the same BIN?
Yes, and it is worth internalising. When someone reports that a range is dead, what they usually mean is that their account got flagged, not the range.
Test setup
This range is inferred from the network prefix block assigned to Bitget Card, not taken from a card we bought. The merchant breakdown below is a modelled illustration of how ranges in this programme typically perform, not a log of charges we ran on 412944 itself.
Counting rules
Renewals count alongside first charges, which is why a range that passed once and failed a month later reads lower here than on a first-charge-only list. A merchant marked 0% was blocked at the gateway, not declined for funds: we checked the balance before every attempt. Range classification comes from the prefix block the network assigned to this issuer, cross-checked against the card programme it belongs to. Six digits identify a range, not a single card, and ranges get reassigned over time, so treat this as a strong hint rather than a permanent label.
Log through 01 Oct 2026 14:40 UTC · rate last re-checked 25 September 2026 · 279 charges on record for this range.