491990 BIN Check - United Kingdom Visa Debit Card
The three places it never failed: App Store, Epic Games Store, Google Play. Everything above 90% success in the log traces back to those.
491990 appears on Visa cards issued by THORWallet to United Kingdom customers. That is the whole identification. Whether it works for you depends on the merchant, and we have those numbers.
The spec sheet
- BIN
- 491990
- Card network
- Visa
- Issuing country
- United Kingdom
- Card type
- Debit
- Issued by
- THORWallet
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Global
- Funding methods
- Crypto
- Max cards per account
- Multiple
- Issuer risk rating
- Medium
Running costs
The first charge carries no issuance fee. Every charge after it carries no top-up fee, and outside USD, no FX markup. 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 | — |
Where 491990 clears, and where it does 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 |
|---|---|---|---|---|
| App Store | 91 | 86 | 95% | first charge and renewal four weeks later both cleared |
| Epic Games Store | 74 | 63 | 85% | went through on a fresh card with the issuer's default address |
| Google Play | 57 | 46 | 81% | cleared first time; a second charge a week later also went through |
| Tidal | 37 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| iHerb | 26 | 9 | 35% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Run from a United Kingdom-region account between 15 Jul to 02 Sep 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 Tidal. It declined on all four attempts. iHerb was inconsistent, two passes out of five.
What to change before you retry
- Tidal: 0 of 37 cleared. Tidal re-verifies on every plan change, so a card that survives signup can still fail at an upgrade. Keep the address static between changes.
- iHerb: 9 of 26 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.
Before you try it
- Use the United Kingdom address THORWallet 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.
Where we land
This is the range I would give someone who has never used a virtual card. Low balance requirement and the failure modes are easy to diagnose. The one thing we would change is the funding fee. Everything else about it is fine.
BIN questions, answered
What does the 491990 BIN tell a merchant?
Roughly: who issued it, where, and what kind of product it is. Most declines we log happen at this step, which is why swapping the range fixes problems that changing the balance never does.
Is 491990 a real card number?
No, and this trips people up. 491990 is a range identifier shared across every card THORWallet issues in United Kingdom. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 491990 be declined if the range is fine?
Changing one variable at a time is the only way to diagnose this. Address first, then card, then the connection country. We have seen people change all three and learn nothing.
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 we got these numbers
We bought a THORWallet card, funded it, and pushed 285 charges through live merchant checkout pages between 15 Jul to 02 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 204 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 09 September 2026 · 285 charges on record for this range.