BIN lookup · Visa · United Kingdom · log through 13 Sep 2026 14:40 UTC

Visa Virtual Card BIN 455606 - United Kingdom (Debit)

The one-paragraph answer

It works on App Store, Epic Games Store, Google Play. Those three account for most of the 174 successful charges we recorded.

455606Visa United KingdomDebit 174/240 cleared

Lightspark issues 455606 out of United Kingdom. Classed Debit, runs on Visa.

455606, decoded

BIN
455606
Card network
Visa
Issuing country
United Kingdom
Card type
Debit
Issued by
Lightspark
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Not published
AVS check
No
Billing address
Not published
Funding methods
Crypto · Bank transfer
Max cards per account
Not published
Issuer risk rating
Medium

Running costs

Budget for an undisclosed issuance fee, no top-up fee, and a no decline fee penalty on declined authorizations. That last one only matters if you are pushing a lot of small charges. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.

Card creation fee
Monthly fee
Top-up fee
FX / conversion fee
Declined transaction fee
Minimum top-up

Merchant by merchant

Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
App Store767193%cleared, 3-D Secure completed in-app in under 20 seconds
Epic Games Store625589%first charge and renewal four weeks later both cleared
Google Play484083%cleared on the first attempt, no challenge issued
StockX3100%3-D Secure challenge never completed. The order timed out waiting for the OTP.
Walmart23835%Gateway risk rule fired and returned a generic decline with no challenge.

Run from a United Kingdom-region account between 01 Jul to 26 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 StockX. It declined on all four attempts. Walmart was inconsistent, two passes out of five.

What to change before you retry

Getting it to work first time

  1. 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.
  2. This range does not advertise 3-D Secure. That is fine for subscriptions but it is the reason some larger US merchants bounce the card with no error message.
  3. Paste the United Kingdom billing address Lightspark generates rather than typing your own. One transposed digit is enough to fail the check.

Final word

If you only need one subscription this is more than enough. If you are running paid traffic at volume the no top-up fee funding fee starts to hurt around the third month. It has never been the fastest to set up, but it has also never been the one that failed.

What people ask us

What does the 455606 BIN tell a merchant?

In practice the checkout reads Lightspark / United Kingdom / 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 455606 a real card number?

It is the first six of sixteen digits. The remaining ten identify the account, and only Lightspark can map those. A BIN alone will never get anyone into your money.

Why would 455606 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.

What we did

We bought a Lightspark card, funded it, and pushed 240 charges through live merchant checkout pages between 01 Jul to 26 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 174 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 30 August 2026 · 240 charges on record for this range.