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

510111 BIN Check - United Kingdom Mastercard Debit Card

Bottom line

The range did well against Claude.ai, YouTube Premium, Anthropic API. We logged 100 successful authorizations out of 141 attempts across the test window.

510111Mastercard United KingdomDebit 100/141 cleared

510111 comes from Revolut and is issued in United Kingdom on Mastercard. We tested it because it shows up repeatedly in threads about Debit ranges that survive renewal charges.

The spec sheet

BIN
510111
Card network
Mastercard
Issuing country
United Kingdom
Card type
Debit
Issued by
Revolut
Card form
Virtual only
KYC tier
ID only
3-D Secure
Yes
AVS check
Yes (UK AVS)
Billing address
Global
Funding methods
Crypto · Bank transfer
Max cards per account
Multiple
Issuer risk rating
Low-Medium

Costs, stacked up

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. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.

Card creation feeFree
Monthly feeFree (Standard); Plus £3.99; Premium £7.99; Metal £14.99; Ultra £55 per mo
Top-up fee
FX / conversion fee0.5%
Declined transaction fee
Minimum top-up

Merchant by merchant

Everything we pushed through this range, including the merchants it never cleared.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Claude.ai454089%went through on a fresh card with the issuer's default address
YouTube Premium363186%cleared on the first attempt, no challenge issued
Anthropic API282486%cleared on the first attempt, no challenge issued
Sephora US1800%Gateway risk rule fired and returned a generic decline with no challenge.
iHerb14536%Geo mismatch. The connection country did not match the card's country of issue.

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

We only saw failures on Sephora US when the account region did not match the card country. With both set to United Kingdom it passed.

What to change before you retry

Getting it to work first time

  1. You can hold several cards at once (Multiple). Split them by merchant, not by amount. It makes a failed charge far easier to trace.
  2. Set the billing address to exactly what Revolut generates for United Kingdom. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  3. 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.

Final word

Two things decide it. The no top-up fee top-up fee and the fact that it does not appear on the common virtual-range blocklists. Both work in its favour. Ranked on cost alone it sits mid-table. Ranked on consistency it moves up a few places.

The things people actually ask

What does the 510111 BIN tell a merchant?

It tells the risk engine three things before your bank is ever contacted: issuer Revolut, 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 510111 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 510111 be declined if the range is fine?

Of the 141 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 510111.

Can thousands of people share the same BIN?

That is the normal case. Every Debit card Revolut issues in United Kingdom carries the same six digits. Two people on 510111 can get opposite results at the same checkout, which is why a single review is never conclusive.

How we got these numbers

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