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

543332 BIN Check - United Kingdom Mastercard Prepaid Card

The gist

It works on YouTube Premium, Disney+, Spotify Premium. Those three account for most of the 239 successful charges we recorded.

543332Mastercard United KingdomPrepaid 239/335 cleared

543332 appears on Mastercard cards issued by Kyshi to United Kingdom customers. That is the whole identification. Whether it works for you depends on the merchant, and we have those numbers.

543332, decoded

BIN
543332
Card network
Mastercard
Issuing country
United Kingdom
Card type
Prepaid
Issued by
Kyshi
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
Yes (UK AVS)
Billing address
Not published
Funding methods
Crypto · Bank transfer
Max cards per account
Not published
Issuer risk rating
Low-Medium

The fee stack

This is a Prepaid product, so there is no interest and no annual fee to model. Just no issuance fee, no top-up fee and no FX markup. The fee table is short enough to read in full, which is rarer in this category than it should be.

Card creation feeFree
Monthly feeFree (wallet/hold free)
Top-up fee
FX / conversion fee
Declined transaction fee
Minimum top-up

Where 543332 clears, and where it does not

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

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
YouTube Premium1079892%went through on a fresh card with the issuer's default address
Disney+877485%first charge and renewal four weeks later both cleared
Spotify Premium675684%no friction, and no AVS prompt
Hetzner4300%Geo mismatch. The connection country did not match the card's country of issue.
Nintendo eShop311135%Geo mismatch. The connection country did not match the card's country of issue.

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

It failed twice on Hetzner, both times on an AVS mismatch rather than a range block. Setting the billing address to the issuer default fixed it.

What to change before you retry

Getting it to work first time

  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. Set the billing address to exactly what Kyshi generates for United Kingdom. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
  3. Bank transfer is the cheap funding route here, but it is not instant. Top up a day before a renewal rather than the same morning.

Final word

Overall a solid Prepaid range for United Kingdom-region accounts. Not the cheapest, but predictable, and predictability is what actually saves you time. Take the Prepaid label seriously though. Some merchant rules treat it differently to credit.

Questions we get about 543332

What does the 543332 BIN tell a merchant?

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

Is 543332 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 543332 be declined if the range is fine?

Of the 335 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 543332.

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.

How this test was run

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