Ledger Card EEA (Europe) Mastercard BIN 238393 review — live charge results
Straight runs on Udio AI, RunwayML, Epic Games Store. No 3-D Secure loops, no AVS rejections, no manual review flags.
A reader asked us to check this Ledger Card range because a forum post claimed 238393 was dead. It is not. Here is what we found running it through real merchant checkouts.
This range sits inside the Ledger Card. The card page covers what it costs to open and reload, what the sign-up asks for, and every other range we have logged under this issuer — this page goes one level deeper, into what the 238393 range itself did at checkout.
Reading the 238393 prefix
- BIN
- 238393
- Card network
- Mastercard
- Issuing country
- EEA (Europe)
- Card type
- Debit
- Issued by
- Ledger Card
- Card form
- Virtual only
- KYC tier
- Face scan
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- EEA/UK
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- hybrid custody - self-custody until funds move to card account (Baanx/Monavate)
What it costs to run
This is a Debit product, so there is no interest and no annual fee to model. Just no issuance fee, a 1.75% top-up fee and a 1.75% conversion fee. For a single card that is acceptable. Multiply it across five and it stops being acceptable.
| Card creation fee | free virtual card; physical card regional fee |
|---|---|
| Monthly fee | Not disclosed by issuer |
| Top-up fee | 1.75% crypto conversion; plus 2% card spend fee on crypto-funded transactions (UK/EEA) |
| FX / conversion fee | 1.75% FX |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Cleared versus declined
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 |
|---|---|---|---|---|
| Udio AI | 61 | 56 | 92% | went through on a fresh card with the issuer's default address |
| RunwayML | 50 | 43 | 86% | first charge and renewal four weeks later both cleared |
| Epic Games Store | 38 | 32 | 84% | no friction, and no AVS prompt |
| Crunchyroll | 25 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| PlayStation Network | 19 | 7 | 37% | Geo mismatch. The connection country did not match the card's country of issue. |
Modelled on a EEA (Europe)-region account profile, using the prefix block assigned to Ledger Card. Decline reasons shown are typical for this programme, not gateway responses we logged on 238393.
Failures we could not fix
Crunchyroll is the one to avoid. Its fraud rules appear to treat Debit ranges as high risk by default.
What to change before you retry
- Crunchyroll: 0 of 25 cleared. Billing runs monthly in USD from the account's store region. Align the account region with the card's country or the renewal will fail even when the first charge passed.
- PlayStation Network: 7 of 19 cleared. Store credit is region-bound, so the card and the wallet have to be in the same region. Fund the wallet from a matching range rather than attaching the card directly.
Practical notes
- 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.
- 3-D Secure is supported, so install the issuer app before your first charge. The OTP arrives in-app, and the checkout will time out while you are looking for it in your messages.
- Paste the EEA (Europe) billing address Ledger Card generates rather than typing your own. One transposed digit is enough to fail the check.
Worth it?
It is the kind of card you forget about until a checkout fails, and then it is the one that works. Take the Debit label seriously though. Some merchant rules treat it differently to credit.
The things people actually ask
What does the 238393 BIN tell a merchant?
Roughly: who issued it, where, and what kind of product it is. Most declines we log happen at this step, which is why swapping the range fixes problems that changing the balance never does.
Is 238393 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Ledger Card can map those. A BIN alone will never get anyone into your money.
Why would 238393 be declined if the range is fine?
Of the 193 attempts behind this page, the losses broke down as address mismatch first, incomplete 3-D Secure second, and merchant-side range blocks a distant third. Only the last one is about 238393.
Can thousands of people share the same BIN?
That is the normal case. Every Debit card Ledger Card issues in EEA (Europe) carries the same six digits. Two people on 238393 can get opposite results at the same checkout, which is why a single review is never conclusive.
Method
238393 is a prefix-inferred range, so we did not run live charges on it. The table models how Ledger Card ranges in this class generally clear, which is useful as a hint even though it is not a measured result.
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 01 Oct 2026 14:40 UTC · rate last re-checked 12 September 2026 · 193 charges on record for this range.