442672 BIN Check - United States Visa Debit Card
215 of 299 attempts cleared, and most of those came from three merchants: Epic Games Store, App Store, Google Play.
We keep coming back to 442672 when a merchant blocks the well-known virtual ranges. It comes from Hi.com in United States and does not sit on the usual blocklists.
What the six digits say
- BIN
- 442672
- Card network
- Visa
- Issuing country
- United States
- Card type
- Debit
- Issued by
- Hi.com
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Global
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- Medium
The fee stack
The signup cost is easy to compare and mostly irrelevant. What follows you around is no top-up fee, with no FX markup sitting behind it. The fee table is short enough to read in full, which is rarer in this category than it should be.
| Card creation fee | Free |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
Results 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 |
|---|---|---|---|---|
| Epic Games Store | 95 | 86 | 91% | first charge and renewal four weeks later both cleared |
| App Store | 77 | 70 | 91% | cleared first time; a second charge a week later also went through |
| Google Play | 59 | 48 | 81% | no friction, and no AVS prompt |
| Hulu | 38 | 0 | 0% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
| Sephora US | 30 | 11 | 37% | Geo mismatch. The connection country did not match the card's country of issue. |
Run from a United States-region account between 09 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
Do not expect much luck on Hulu. It declined on all four attempts. Sephora US was inconsistent, two passes out of five.
What to change before you retry
- Hulu: 0 of 38 cleared. Hulu is US-only and rejects foreign ranges at the authorisation step. No configuration fixes this; use a US-issued range.
- Sephora US: 11 of 30 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.
Setup notes for Hi.com
- Use the United States address Hi.com gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- 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.
- 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.
Worth it?
If your merchants are mostly in United States, 442672 is a reasonable default. If they are not, the no FX markup conversion cost will annoy you. Treat the numbers here as a snapshot of 7 weeks, not a permanent rating.
FAQ
What does the 442672 BIN tell a merchant?
In practice the checkout reads Hi.com / 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 442672 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Hi.com can map those. A BIN alone will never get anyone into your money.
Why would 442672 be declined if the range is fine?
Of the 299 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 442672.
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.
Method
We bought a Hi.com card, funded it, and pushed 299 charges through live merchant checkout pages between 09 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. 215 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 29 August 2026 · 299 charges on record for this range.