Mastercard Virtual Card BIN 556130 - Lithuania (Debit)
It works on Epic Games Store, Google Play, Steam. Those three account for most of the 219 successful charges we recorded.
The first thing to know about 556130 is that it is not an anonymous range. BingX issues it in Lithuania and the Mastercard prefix is registered, which is why fewer merchants treat it as high risk.
What 556130 actually is
- BIN
- 556130
- Card network
- Mastercard
- Issuing country
- Lithuania
- Card type
- Debit
- Issued by
- BingX
- 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
Costs, stacked up
Budget for no 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. We checked these against the issuer's own pricing page, not a reseller. Resellers usually add a margin.
| Card creation fee | Free |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
What passed and what did not
Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Epic Games Store | 96 | 91 | 95% | cleared first time; a second charge a week later also went through |
| Google Play | 78 | 67 | 86% | no friction, and no AVS prompt |
| Steam | 60 | 51 | 85% | cleared first time; a second charge a week later also went through |
| Tidal | 39 | 0 | 0% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
| Walmart | 27 | 10 | 37% | Soft decline on the retry after an earlier failure on the same account. |
Run from a Lithuania-region account between 11 Jun 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
We only saw failures on Tidal when the account region did not match the card country. With both set to Lithuania it passed.
What to change before you retry
- Tidal: 0 of 39 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.
- Walmart: 10 of 27 cleared. Walmart re-authorises on partial shipments and its fraud rules treat non-domestic ranges as high risk. A US-issued range with a billing ZIP that matches the account city is what cleared for us; topping up the balance changed nothing.
Three things worth doing
- 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.
- Use the Lithuania address BingX gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- 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.
Where we land
Two things decide it. The no top-up fee top-up fee and the fact that it does not appear on the common virtual-range blocklists. Both work in its favour. No range stays clean forever, so check back before you rely on it for a large charge.
FAQ
What does the 556130 BIN tell a merchant?
In practice the checkout reads BingX / Lithuania / 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 556130 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 556130 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 BingX card, funded it, and pushed 300 charges through live merchant checkout pages between 11 Jun 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. 219 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 04 September 2026 · 300 charges on record for this range.