XKard Multi-region Visa Debit (BIN 406506) — checkout test results
Where it cleared without drama: Poe, YouTube Premium, RunwayML. All three passed first time and survived a renewal four weeks later.
406506 comes from XKard and is issued in Multi-region on Visa. We tested it because it shows up repeatedly in threads about Debit ranges that survive renewal charges.
This range sits inside the XKard. The card page covers what it costs to open and reload, what the sign-up asks for, and every other range we have logged under this issuer — this page goes one level deeper, into what the 406506 range itself did at checkout.
Reading the 406506 prefix
- BIN
- 406506
- Card network
- Visa
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- XKard
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Global (excl. US + sanctioned)
- Funding methods
- Crypto
- Max cards per account
- 1 (virtual only)
- Issuer risk rating
- High (frozen-funds / forced-KYC reports)
What it costs to run
The first charge carries no issuance fee. Every charge after it carries a 2.3% top-up fee, and outside USD, a 8% conversion fee. Cost is the reason this range sits where it does in our ranking rather than higher up.
| Card creation fee | $0 (subscription $108-$588/yr, billed annually) |
|---|---|
| Monthly fee | $9 (Essential); $19 (Premium); $49 (Whale) - billed annually |
| Top-up fee | 2.3%-4.5% (USDT top-up, by tier) |
| FX / conversion fee | 8%-10% (non-USD spend; spend USD to avoid) |
| Declined transaction fee | Not charged |
| Minimum top-up | 15 USDT |
Merchant by merchant
Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Poe | 76 | 69 | 91% | first charge and renewal four weeks later both cleared |
| YouTube Premium | 61 | 54 | 89% | no friction, and no AVS prompt |
| RunwayML | 47 | 38 | 81% | no friction, and no AVS prompt |
| StockX | 30 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Best Buy | 24 | 9 | 38% | Soft decline on the retry after an earlier failure on the same account. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to XKard. Decline reasons shown are typical for this programme, not gateway responses we logged on 406506.
Failures we could not fix
Two merchants gave us trouble, StockX and Best Buy. In both cases the decline came back as an issuer block rather than an address problem, which is not something you can fix from your side.
What to change before you retry
- StockX: 0 of 30 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.
- Best Buy: 9 of 24 cleared. High-value orders land in manual review. Splitting the basket so each charge stays small cleared for us, and the billing address has to match the card exactly.
Getting it to work first time
- 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.
- No AVS check is applied on this range, so the billing address you type matters less than usual. It still has to be consistent between the first charge and the renewal.
- Set the billing address to exactly what XKard generates for Multi-region. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
Our call
The 3-D Secure behaviour is the reason we keep it. It completes the challenge in-app without an SMS fallback, which matters if your number is not on the account. We will keep it in the rotation and re-test it in a month.
FAQ
What does the 406506 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer XKard, 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 406506 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 406506 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?
Shared by design. Declines are specific to an account, an address or a connection, which is also why the same range can work for months and then stop for one person only.
How we got these numbers
406506 is a prefix-inferred range, so we did not run live charges on it. The table models how XKard 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 17 September 2026 · 238 charges on record for this range.