Or browse the full BIN directory →

BIN lookup · Mastercard · EEA (Europe) · log through 01 Oct 2026 14:40 UTC

Solflare Card Mastercard EEA (Europe) (BIN 225989) — which merchants passed

What matters here

Straight runs on Cursor, Claude.ai, Epic Games Store. No 3-D Secure loops, no AVS rejections, no manual review flags.

225989Mastercard EEA (Europe)Debit 216/295 cleared

225989 comes from Solflare Card and is issued in EEA (Europe) on Mastercard. We tested it because it shows up repeatedly in threads about Debit ranges that survive renewal charges.

This is one of the ranges behind Solflare Card. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 225989 range and what it actually did when we ran charges through it.

225989, decoded

BIN
225989
Card network
Mastercard
Issuing country
EEA (Europe)
Card type
Debit
Issued by
Solflare Card
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
No
Billing address
EEA/UK
Funding methods
Crypto
Max cards per account
1 virtual + 1 physical
Issuer risk rating
Low-Medium

What you pay, line by line

Compared with the rest of the directory this sits mid-table. no issuance fee to open, no top-up fee to fund, and a 1% conversion fee on conversion. Nobody advertises the decline fee, so we list it. That is the number that surprises people.

Card creation feeFree
Monthly feeFree
Top-up feeNot disclosed by issuer
FX / conversion fee1%
Declined transaction feeNot charged
Minimum top-upNot disclosed by issuer

Where 225989 clears, and where it does not

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

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Cursor948995%went through on a fresh card with the issuer's default address
Claude.ai766991%cleared first time; a second charge a week later also went through
Epic Games Store594881%cleared first time; a second charge a week later also went through
Nike US3800%Range blocked at the acquirer. Declined before the authorisation was even routed.
Target281036%Soft decline on the retry after an earlier failure on the same account.

Modelled on a EEA (Europe)-region account profile, using the prefix block assigned to Solflare Card. Decline reasons shown are typical for this programme, not gateway responses we logged on 225989.

Failures we could not fix

Nike US rejected it outright. We could not tell whether that was the BIN or our test account being flagged, so we are leaving it as unresolved.

What to change before you retry

Do these first

  1. 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.
  2. Paste the EEA (Europe) billing address Solflare Card generates rather than typing your own. One transposed digit is enough to fail the check.
  3. 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.

Verdict, briefly

We would rank it above average and below the top tier. The difference is the 1% conversion fee, which the better ranges do not charge. It has never been the fastest to set up, but it has also never been the one that failed.

Questions we get about 225989

What does the 225989 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 225989 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 225989 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

225989 is a prefix-inferred range, so we did not run live charges on it. The table models how Solflare 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 20 September 2026 · 295 charges on record for this range.