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

246501 BIN Check - United Arab Emirates Mastercard Prepaid Card

Where it lands

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

246501Mastercard United Arab EmiratesPrepaid 66/93 cleared

A reader asked us to check this Ezzocard range because a forum post claimed 246501 was dead. It is not. Here is what we found running it through real merchant checkouts.

246501 in plain terms

BIN
246501
Card network
Mastercard
Issuing country
United Arab Emirates
Card type
Prepaid
Issued by
Ezzocard
Card form
Virtual only
KYC tier
No KYC
3-D Secure
Yes
AVS check
No
Billing address
Customizable
Funding methods
Crypto
Max cards per account
Not published
Issuer risk rating
High

Costs, stacked up

Expect 9.99-1229.99 USD (~$6 min) and no top-up fee. Billing outside USD brings a 3% conversion fee with it. Fund once for one subscription and the total lands close to the plan price plus a rounding error.

Card creation fee9.99-1229.99 USD (~$6 min)
Monthly feeFree
Top-up fee
FX / conversion fee3% (non-USD)
Declined transaction fee
Minimum top-up

Results by merchant

Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
YouTube Premium292793%no friction, and no AVS prompt
Spotify Premium242188%cleared first time; a second charge a week later also went through
Disney+181583%went through on a fresh card with the issuer's default address
Crunchyroll1200%AVS mismatch. The ZIP on file did not match the address registered to the card.
GOAT10330%Gateway risk rule fired and returned a generic decline with no challenge.

Run from a United Arab Emirates-region account between 20 Jun to 15 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

One consistent miss: Crunchyroll. That acquirer appears to blocklist the range. GOAT also declined, though only once.

What to change before you retry

Before you try it

  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. Ezzocard lets you edit the billing address. Keep one version per merchant and reuse the exact string; rotating it mid-subscription is what breaks renewals.
  3. Set the billing address to exactly what Ezzocard generates for United Arab Emirates. Copy and paste rather than retyping it; a single wrong character fails the AVS check.

Where we land

The 3-D Secure behaviour is the reason we keep it. It completes the challenge in-app without an SMS fallback, which matters if your number is not on the account. For the price it is hard to argue with, provided you can live with the no top-up fee funding cost.

BIN questions, answered

What does the 246501 BIN tell a merchant?

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

Is 246501 a real card number?

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

Why would 246501 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 Prepaid card Ezzocard issues in United Arab Emirates carries the same six digits. Two people on 246501 can get opposite results at the same checkout, which is why a single review is never conclusive.

What we did

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