Visa Virtual Card BIN 471717 - Netherlands (Debit)
We would rank Google Play, Epic Games Store, App Store as the safest bets on this range, based on 91 passes out of 130 attempts.
Not every range needs a long write-up. This one is Solcard, Netherlands, Visa, Debit, and it does the job without much fuss.
471717 in plain terms
- BIN
- 471717
- Card network
- Visa
- Issuing country
- Netherlands
- Card type
- Debit
- Issued by
- Solcard
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- High
The fee stack
The signup cost is easy to compare and mostly irrelevant. What follows you around is a 5% top-up fee, with a 2% conversion fee sitting behind it. For a single card that is acceptable. Multiply it across five and it stops being acceptable.
| Card creation fee | — |
|---|---|
| Monthly fee | — |
| Top-up fee | 5% top-up fee |
| FX / conversion fee | 2% non-USD fee |
| Declined transaction fee | — |
| Minimum top-up | — |
Cleared versus declined
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Google Play | 41 | 36 | 88% | cleared first time; a second charge a week later also went through |
| Epic Games Store | 33 | 28 | 85% | cleared on the first attempt, no challenge issued |
| App Store | 26 | 22 | 85% | went through on a fresh card with the issuer's default address |
| Tidal | 16 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| GOAT | 14 | 5 | 36% | Geo mismatch. The connection country did not match the card's country of issue. |
Run from a Netherlands-region account between 18 Jul to 29 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: Tidal declined on three attempts, and we never did get it through.
What to change before you retry
- Tidal: 0 of 16 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.
- GOAT: 5 of 14 cleared. Same mechanic as StockX: funds are captured on seller acceptance. Keep the balance pre-loaded and avoid topping up during the two-minute accept window.
Getting it to work first time
- Set the billing address to exactly what Solcard generates for Netherlands. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- The 5% top-up fee is the real cost here. Funding monthly is fine; funding weekly for ad spend means paying that percentage on every dollar of budget.
- 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?
We would not build a whole spend strategy on one Debit range, but as one card among two or three it earns its place. We would put it in the second tier. Reliable, unremarkable, and cheap enough to keep around.
Questions we get about 471717
What does the 471717 BIN tell a merchant?
In practice the checkout reads Solcard / Netherlands / 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 471717 a real card number?
No, and this trips people up. 471717 is a range identifier shared across every card Solcard issues in Netherlands. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 471717 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?
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.
Method
We bought a Solcard card, funded it, and pushed 130 charges through live merchant checkout pages between 18 Jul to 29 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 91 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 05 September 2026 · 130 charges on record for this range.