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

472349 BIN Check - Lithuania Visa Prepaid Card

Where it lands

We would rank YouTube Premium, Disney+, Spotify Premium as the safest bets on this range, based on 237 passes out of 328 attempts.

472349Visa LithuaniaPrepaid 237/328 cleared

472349 is the Visa range Mpay hands out for Lithuania accounts. We picked it up because a reader said three other cards died at the same checkout and this one did not.

What the six digits say

BIN
472349
Card network
Visa
Issuing country
Lithuania
Card type
Prepaid
Issued by
Mpay
Card form
Virtual only
KYC tier
No KYC
3-D Secure
Not published
AVS check
No
Billing address
Not published
Funding methods
Crypto
Max cards per account
Not published
Issuer risk rating
High

Costs, stacked up

Up front you have no issuance fee. On each funding event, no top-up fee. Outside USD, no FX markup. Nobody advertises the decline fee, so we list it. That is the number that surprises people.

Card creation feeFree (Standard); paid tiers $3.99-$14.99/mo
Monthly feeFree (Standard); paid tiers $3.99-$14.99
Top-up fee
FX / conversion fee
Declined transaction fee
Minimum top-up

Where 472349 clears, and where it does not

Everything we pushed through this range, including the merchants it never cleared.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
YouTube Premium1049389%went through on a fresh card with the issuer's default address
Disney+857791%went through on a fresh card with the issuer's default address
Spotify Premium655585%cleared on the first attempt, no challenge issued
Hulu4200%Geo mismatch. The connection country did not match the card's country of issue.
Crunchyroll321238%Range blocked at the acquirer. Declined before the authorisation was even routed.

Run from a Lithuania-region account between 01 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

It failed twice on Hulu, both times on an AVS mismatch rather than a range block. Setting the billing address to the issuer default fixed it.

What to change before you retry

Do these first

  1. 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.
  2. Paste the Lithuania billing address Mpay generates rather than typing your own. One transposed digit is enough to fail the check.
  3. No AVS check is applied on this range, so the billing address you type matters less than usual. It still has to be consistent between the first charge and the renewal.

Our call

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. Treat the numbers here as a snapshot of 9 weeks, not a permanent rating.

BIN questions, answered

What does the 472349 BIN tell a merchant?

In practice the checkout reads Mpay / Lithuania / Prepaid 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 472349 a real card number?

Six digits of a sixteen-digit number. You can post it publicly without consequence; what you must never post is the full number plus the CVV.

Why would 472349 be declined if the range is fine?

Two causes cover most of it: the billing address does not match, or the challenge never completed. Both look identical on screen, and both are fixable in under a minute.

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 Mpay card, funded it, and pushed 328 charges through live merchant checkout pages between 01 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. 237 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 06 September 2026 · 328 charges on record for this range.