BIN lookup · Mastercard · EEA (Europe) · log through 13 Sep 2026 14:40 UTC

222686 VCC - EEA (Europe) Mastercard Virtual Card Review

The gist

Reliable on Steam, Google Play, Epic Games Store. Everywhere else it was closer to a coin flip, which we will get to.

222686Mastercard EEA (Europe)Debit 201/286 cleared

The first thing to know about 222686 is that it is not an anonymous range. MyFin issues it in EEA (Europe) and the Mastercard prefix is registered, which is why fewer merchants treat it as high risk.

222686, decoded

BIN
222686
Card network
Mastercard
Issuing country
EEA (Europe)
Card type
Debit
Issued by
MyFin
Card form
Virtual only
KYC tier
ID only
3-D Secure
Yes
AVS check
No
Billing address
EEA
Funding methods
Bank transfer
Max cards per account
200 (Premium/Pre); 2 (standard)
Issuer risk rating
Low-Medium

What you pay, line by line

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
Monthly feeFree (Standard); Advanced ~€5.14; Premium ~€10.23/€10 per mo
Top-up fee
FX / conversion fee0%
Declined transaction fee
Minimum top-up

Merchant by merchant

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

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Steam918189%cleared, 3-D Secure completed in-app in under 20 seconds
Google Play746486%first charge and renewal four weeks later both cleared
Epic Games Store574681%no friction, and no AVS prompt
PlayStation Network3700%Soft decline on the retry after an earlier failure on the same account.
StockX271037%AVS mismatch. The ZIP on file did not match the address registered to the card.

Run from a EEA (Europe)-region account between 08 Jun to 17 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

Failures were rare but real: PlayStation Network declined on three attempts, and we never did get it through.

What to change before you retry

Do these first

  1. 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.
  2. Use the EEA (Europe) address MyFin gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
  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.

Verdict, briefly

Overall a solid Debit range for EEA (Europe)-region accounts. Not the cheapest, but predictable, and predictability is what actually saves you time. The pattern across all 286 attempts was consistent, which is the most useful thing you can say about a card range.

What people ask us

What does the 222686 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 222686 a real card number?

No, and this trips people up. 222686 is a range identifier shared across every card MyFin issues in EEA (Europe). It is printed on the front of the card, which tells you how sensitive it is not.

Why would 222686 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?

That is the normal case. Every Debit card MyFin issues in EEA (Europe) carries the same six digits. Two people on 222686 can get opposite results at the same checkout, which is why a single review is never conclusive.

Test setup

We bought a MyFin card, funded it, and pushed 286 charges through live merchant checkout pages between 08 Jun to 17 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 201 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 22 August 2026 · 286 charges on record for this range.