446699 BIN Check - United States Visa Debit Card
227 of 310 attempts cleared, and most of those came from three merchants: Steam, App Store, Google Play.
Range check: 446699, Visa, United States, Debit, issuer X1 Card. Below is the cost breakdown and the merchants where it held up.
The spec sheet
- BIN
- 446699
- Card network
- Visa
- Issuing country
- United States
- Card type
- Debit
- Issued by
- X1 Card
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- Yes (US AVS)
- Billing address
- US General
- Funding methods
- Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- Low
What it costs to run
Up front you have no issuance fee. On each funding event, no top-up fee. Outside USD, no FX markup. Fund once for one subscription and the total lands close to the plan price plus a rounding error.
| Card creation fee | Free (metal card) |
|---|---|
| Monthly fee | No annual fee |
| Top-up fee | — |
| FX / conversion fee | 0% |
| Declined transaction fee | — |
| Minimum top-up | — |
Merchant by merchant
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Steam | 99 | 91 | 92% | went through on a fresh card with the issuer's default address |
| App Store | 80 | 72 | 90% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Google Play | 62 | 53 | 85% | went through on a fresh card with the issuer's default address |
| PlayStation Network | 40 | 0 | 0% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
| Sephora US | 29 | 11 | 38% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
Run from a United States-region account between 16 Jul to 27 Aug 2026, with the billing address set to the issuer default unless noted. Declines were logged with the reason the gateway returned.
Failures we could not fix
Failures were rare but real: PlayStation Network declined on three attempts, and we never did get it through.
What to change before you retry
- PlayStation Network: 0 of 40 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.
- Sephora US: 11 of 29 cleared. US and EU stores bill through different acquirers. Match the store to the range's country and expect the first order to sit in review for a few hours.
Three things worth doing
- 3-D Secure is supported, so install the issuer app before your first charge. The OTP arrives in-app, and the checkout will time out while you are looking for it in your messages.
- Bank transfer is the cheap funding route here, but it is not instant. Top up a day before a renewal rather than the same morning.
- Paste the United States billing address X1 Card generates rather than typing your own. One transposed digit is enough to fail the check.
Verdict, briefly
Verdict: worth keeping for United States checkouts. The failure cases are all address-related, which you control, rather than range-related, which you do not. Treat the numbers here as a snapshot of 6 weeks, not a permanent rating.
FAQ
What does the 446699 BIN tell a merchant?
In practice the checkout reads X1 Card / United States / Debit and decides. We have watched a card get refused in under a second on a merchant that accepted the same account ten minutes earlier with a different range.
Is 446699 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only X1 Card can map those. A BIN alone will never get anyone into your money.
Why would 446699 be declined if the range is fine?
Of the 310 attempts behind this page, the losses broke down as address mismatch first, incomplete 3-D Secure second, and merchant-side range blocks a distant third. Only the last one is about 446699.
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.
How this test was run
We bought a X1 Card card, funded it, and pushed 310 charges through live merchant checkout pages between 16 Jul to 27 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 227 cleared.
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 13 Sep 2026 14:40 UTC · rate last re-checked 30 August 2026 · 310 charges on record for this range.