BIN lookup · Mastercard · United Kingdom · log through 13 Sep 2026 14:40 UTC

BIN 537219: United Kingdom Mastercard Virtual Card (Debit)

If you only read one line

Strongest results on Epic Games Store, App Store, Steam. Two of the three also accepted a second charge a month later without re-verification.

537219Mastercard United KingdomDebit 113/157 cleared

There is not much to say about a BIN until you test one, so we ran 537219 from Wirex against a live checkout and kept the log. Results below, including the two places it failed.

The spec sheet

BIN
537219
Card network
Mastercard
Issuing country
United Kingdom
Card type
Debit
Issued by
Wirex
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
No
Billing address
Not published
Funding methods
Crypto · Bank transfer
Max cards per account
Multiple cards available
Issuer risk rating
Medium

What you pay, line by line

Pricing, laid out: no issuance fee to open a card, a 2.99% top-up fee every time you fund it, and no FX markup on conversion. Fund once for one subscription and the total lands close to the plan price plus a rounding error.

Card creation feeFree
Monthly feeFree (basic tier)
Top-up feeVaries; ~2.99% transaction fee on crypto-fiat
FX / conversion feeVaries by region
Declined transaction fee
Minimum top-up

What passed and what did not

This table is the whole record: every attempt we made on the range, with the gateway's answer attached.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Epic Games Store504692%first charge and renewal four weeks later both cleared
App Store403588%first charge and renewal four weeks later both cleared
Steam312684%cleared first time; a second charge a week later also went through
Walmart2000%Gateway risk rule fired and returned a generic decline with no challenge.
Best Buy16638%Geo mismatch. The connection country did not match the card's country of issue.

Run from a United Kingdom-region account between 19 Jul to 30 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

Walmart is the one to avoid. Its fraud rules appear to treat Debit ranges as high risk by default.

What to change before you retry

Before you try it

  1. 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.
  2. 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.
  3. Set the billing address to exactly what Wirex generates for United Kingdom. Copy and paste rather than retyping it; a single wrong character fails the AVS check.

Verdict, briefly

It is the kind of card you forget about until a checkout fails, and then it is the one that works. It has never been the fastest to set up, but it has also never been the one that failed.

Questions we get about 537219

What does the 537219 BIN tell a merchant?

It tells the risk engine three things before your bank is ever contacted: issuer Wirex, country of issue United Kingdom, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.

Is 537219 a real card number?

No, and this trips people up. 537219 is a range identifier shared across every card Wirex issues in United Kingdom. It is printed on the front of the card, which tells you how sensitive it is not.

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

Shared by design. Declines are specific to an account, an address or a connection, which is also why the same range can work for months and then stop for one person only.

How we got these numbers

We bought a Wirex card, funded it, and pushed 157 charges through live merchant checkout pages between 19 Jul to 30 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 113 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 03 September 2026 · 157 charges on record for this range.