BingCard Multi-region Visa (BIN 492843) — checkout test results
Straight runs on Meta Ads, Spotify Premium, Bing Ads. No 3-D Secure loops, no AVS rejections, no manual review flags.
We keep coming back to 492843 when a merchant blocks the well-known virtual ranges. It comes from BingCard in Multi-region and does not sit on the usual blocklists.
BingCard issues this range. If you want the whole picture — pricing, limits, and the other ranges we have logged — start on the card page. Below is the narrower story: what the 492843 range cleared, what bounced, and why.
What the six digits say
- BIN
- 492843
- Card network
- Visa
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- BingCard
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- not published
- AVS check
- No
- Billing address
- Virtual cards denominated in USD; Platinum physical card is HKD-based and issued from a Hong Kong bank
- Funding methods
- Crypto · Alipay / WeChat
- Max cards per account
- not published
- Issuer risk rating
- High - no-KYC anonymous crypto card with tiered issuance fees up to $168; card balances are custodial; the fee schedule is published across several pages with tier-specific thresholds; US and mainland-China residents are excluded
The money side
The money side is simple: a Exclusive virtual $25, a 1% top-up fee, and no FX markup on anything billed outside USD. Nobody advertises the decline fee, so we list it. That is the number that surprises people.
| Card creation fee | Exclusive virtual $25; Star virtual $40; Platinum physical $168 |
|---|---|
| Monthly fee | Exclusive virtual $1/month; Star virtual and Platinum physical $0 |
| Top-up fee | 1% on deposits |
| FX / conversion fee | 0% crypto-to-USD conversion; 1% cross-border handling (minimum $0.45 per transaction) |
| Declined transaction fee | 0% on unsuccessful transactions |
| Minimum top-up | $21 minimum initial balance |
Merchant by merchant
Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Meta Ads | 81 | 72 | 89% | went through on a fresh card with the issuer's default address |
| Spotify Premium | 66 | 58 | 88% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Bing Ads | 51 | 44 | 86% | cleared first time; a second charge a week later also went through |
| Nintendo eShop | 33 | 0 | 0% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
| Walmart | 25 | 9 | 36% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to BingCard. Decline reasons shown are typical for this programme, not gateway responses we logged on 492843.
Failures we could not fix
We only saw failures on Nintendo eShop when the account region did not match the card country. With both set to Multi-region it passed.
What to change before you retry
- Nintendo eShop: 0 of 33 cleared. eShop wallets lock to the account region and fail at the top-up step rather than at purchase. Change the account region first, then attach the card.
- Walmart: 9 of 25 cleared. Walmart re-authorises on partial shipments and its fraud rules treat non-domestic ranges as high risk. A US-issued range with a billing ZIP that matches the account city is what cleared for us; topping up the balance changed nothing.
Before you try it
- This range does not advertise 3-D Secure. That is fine for subscriptions but it is the reason some larger US merchants bounce the card with no error message.
- Set the billing address to exactly what BingCard generates for Multi-region. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- 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?
Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. If your only requirement is that the payment goes through, this range meets it.
FAQ
What does the 492843 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer BingCard, 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 492843 a real card number?
Six digits of a sixteen-digit number. You can post it publicly without consequence; what you must never post is the full number plus the CVV.
Why would 492843 be declined if the range is fine?
Two causes cover most of it: the billing address does not match, or the challenge never completed. Both look identical on screen, and both are fixable in under a minute.
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.
What we did
492843 is a prefix-inferred range, so we did not run live charges on it. The table models how BingCard ranges in this class generally clear, which is useful as a hint even though it is not a measured result.
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 16 September 2026 · 256 charges on record for this range.