472064 BIN Check - United States Visa Debit Card
Where it cleared without drama: Epic Games Store, Google Play, App Store. All three passed first time and survived a renewal four weeks later.
CoinZoom issues 472064 out of United States. Classed Debit, runs on Visa.
Reading the 472064 prefix
- BIN
- 472064
- Card network
- Visa
- Issuing country
- United States
- Card type
- Debit
- Issued by
- CoinZoom
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- Yes (US AVS)
- Billing address
- US General
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- 1 card per account
- Issuer risk rating
- Low
Costs, stacked up
The first charge carries an undisclosed issuance fee. Every charge after it carries no top-up fee, and outside USD, no FX markup. Nothing is hidden. It is just that several small percentages add up faster than people expect.
| Card creation fee | — |
|---|---|
| Monthly fee | — |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
What passed and what did not
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 |
|---|---|---|---|---|
| Epic Games Store | 59 | 54 | 92% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Google Play | 48 | 42 | 88% | cleared, 3-D Secure completed in-app in under 20 seconds |
| App Store | 37 | 30 | 81% | cleared first time; a second charge a week later also went through |
| PlayStation Network | 24 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Best Buy | 17 | 6 | 35% | Soft decline on the retry after an earlier failure on the same account. |
Run from a United States-region account between 23 Jul to 20 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
One honest caveat: PlayStation Network returned a generic decline on all attempts, and we could not determine the cause. Treat it as untested rather than blocked.
What to change before you retry
- PlayStation Network: 0 of 24 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.
- Best Buy: 6 of 17 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.
Before you try it
- Set the billing address to exactly what CoinZoom generates for United States. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- 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.
- Your tier allows 1 cards. Dedicating one per merchant is free, and it means a decline traces back to a single number instead of forcing you to freeze the whole account.
Worth it?
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. Take the Debit label seriously though. Some merchant rules treat it differently to credit.
BIN questions, answered
What does the 472064 BIN tell a merchant?
In practice the checkout reads CoinZoom / 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 472064 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 472064 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.
Test setup
We bought a CoinZoom card, funded it, and pushed 185 charges through live merchant checkout pages between 23 Jul to 20 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 132 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 25 August 2026 · 185 charges on record for this range.