Fasset Multi-region Visa (BIN 472055) — tested at checkout
Best hit rate in our run: Google Play, Epic Games Store, Steam. Timestamps in the log, no retries needed.
Not every range needs a long write-up. This one is Fasset, Multi-region, Visa, Debit, and it does the job without much fuss.
This is one of the ranges behind Fasset. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 472055 range and what it actually did when we ran charges through it.
What 472055 actually is
- BIN
- 472055
- Card network
- Visa
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- Fasset
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- 1 card
- Issuer risk rating
- Medium
The money side
Up front you have 9.99 USDT (one-time activatio…. On each funding event, no top-up fee. Outside USD, a 1.1% conversion fee. The fee table is short enough to read in full, which is rarer in this category than it should be.
| Card creation fee | 9.99 USDT (one-time activation) |
|---|---|
| Monthly fee | Free |
| Top-up fee | Not disclosed by issuer |
| FX / conversion fee | 1.1% (non-USD) |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Where 472055 clears, and where it does not
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Google Play | 46 | 42 | 91% | cleared first time; a second charge a week later also went through |
| Epic Games Store | 37 | 31 | 84% | no friction, and no AVS prompt |
| Steam | 29 | 25 | 86% | cleared, 3-D Secure completed in-app in under 20 seconds |
| iHerb | 18 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| Best Buy | 15 | 5 | 33% | Gateway risk rule fired and returned a generic decline with no challenge. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to Fasset. Decline reasons shown are typical for this programme, not gateway responses we logged on 472055.
Failures we could not fix
If you buy from iHerb, use something else. It declined consistently. Best Buy was fine on retry.
What to change before you retry
- iHerb: 0 of 18 cleared. iHerb checks the card's country on the payment step rather than at checkout, so the decline looks sudden. Fix the address first, then the range.
- Best Buy: 5 of 15 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
- 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.
- Set the billing address to exactly what Fasset generates for Multi-region. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- 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.
What the numbers add up to
If your merchants are mostly in Multi-region, 472055 is a reasonable default. If they are not, the 1.1% (non-USD) conversion cost will annoy you. Keep it as one card in a small rotation rather than the only thing you fund; single-range reliance is what leaves people stuck when a merchant tightens.
FAQ
What does the 472055 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Fasset, 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 472055 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Fasset can map those. A BIN alone will never get anyone into your money.
Why would 472055 be declined if the range is fine?
Of the 145 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 472055.
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.
Test setup
No physical card sits behind 472055 in our lab; the six digits come from the prefix the network assigned to Fasset. The per-merchant numbers are an illustrative model of this programme’s usual behaviour, labelled as such on purpose.
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 18 September 2026 · 145 charges on record for this range.