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

542026 VCC - United Kingdom Mastercard Virtual Card Review

The gist

It works on TikTok Ads, Google Ads, Meta Ads. Those three account for most of the 163 successful charges we recorded.

542026Mastercard United KingdomPrepaid 163/229 cleared

Short entry for a range that punches above its weight. 542026 comes from Spendge, United Kingdom, Mastercard, Prepaid. It is the card we hand people who have already failed twice elsewhere.

What the six digits say

BIN
542026
Card network
Mastercard
Issuing country
United Kingdom
Card type
Prepaid
Issued by
Spendge
Card form
Virtual only
KYC tier
Business KYC
3-D Secure
No
AVS check
No
Billing address
Not published
Funding methods
Bank transfer
Max cards per account
Multiple (platform-specific cards)
Issuer risk rating
Medium

What it costs to run

Nothing exotic in the pricing. an undisclosed issuance fee, no top-up fee, and on non-USD billing, no FX markup. Nobody advertises the decline fee, so we list it. That is the number that surprises people.

Card creation fee
Monthly fee
Top-up fee
FX / conversion fee
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
TikTok Ads736893%went through on a fresh card with the issuer's default address
Google Ads595085%first charge and renewal four weeks later both cleared
Meta Ads453782%cleared on the first attempt, no challenge issued
Tidal2900%Soft decline on the retry after an earlier failure on the same account.
PlayStation Network23835%AVS mismatch. The ZIP on file did not match the address registered to the card.

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

The pattern in our failures is geographic. Tidal accepted it once the account region matched United Kingdom, and refused it every time it did not.

What to change before you retry

Three things worth doing

  1. You can hold several cards at once (Multiple (platform-specific cards)). Split them by merchant, not by amount. It makes a failed charge far easier to trace.
  2. 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.
  3. Use the United Kingdom address Spendge gives you, verbatim. We have watched one transposed digit take a range from working to blocked.

Verdict, briefly

Verdict: worth keeping for United Kingdom checkouts. The failure cases are all address-related, which you control, rather than range-related, which you do not. The pattern across all 229 attempts was consistent, which is the most useful thing you can say about a card range.

BIN questions, answered

What does the 542026 BIN tell a merchant?

In practice the checkout reads Spendge / United Kingdom / Prepaid and decides. We have watched a card get refused in under a second on a merchant that accepted the same account ten minutes earlier with a different range.

Is 542026 a real card number?

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

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

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.

What we did

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