BIN 408823 (Lithuania, Visa) - What It Works On
Tested across 7 weeks. Google Play, Epic Games Store, Steam held at or above 150 passes, and the failures clustered on two merchants only.
408823 is the Visa range Avalanche Card 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
- 408823
- Card network
- Visa
- Issuing country
- Lithuania
- Card type
- Debit
- Issued by
- Avalanche Card
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Not published
- AVS check
- No
- Billing address
- Self-custody
- Funding methods
- Crypto
- Max cards per account
- Not published
- Issuer risk rating
- Medium
The money side
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. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.
| Card creation fee | Free |
|---|---|
| Monthly fee | — |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
Where 408823 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 |
|---|---|---|---|---|
| Google Play | 67 | 61 | 91% | cleared first time; a second charge a week later also went through |
| Epic Games Store | 54 | 48 | 89% | went through on a fresh card with the issuer's default address |
| Steam | 42 | 34 | 81% | cleared on the first attempt, no challenge issued |
| GOAT | 27 | 0 | 0% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
| Nintendo eShop | 21 | 7 | 33% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
Run from a Lithuania-region account between 13 Jul to 31 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
The weak spot is GOAT, which declined every time. Everything else was either clean or fixed by correcting the billing address.
What to change before you retry
- GOAT: 0 of 27 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.
- Nintendo eShop: 7 of 21 cleared. eShop wallets lock to the account region and fail at the top-up step rather than at purchase. Change the account region first, then attach the card.
Before you try it
- 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.
- 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.
- Set the billing address to exactly what Avalanche Card generates for Lithuania. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
Worth it?
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 408823 BIN tell a merchant?
In practice the checkout reads Avalanche Card / 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 408823 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 408823 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.
How we got these numbers
We bought a Avalanche Card card, funded it, and pushed 211 charges through live merchant checkout pages between 13 Jul to 31 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 150 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 07 September 2026 · 211 charges on record for this range.