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

523449 BIN Check - United Arab Emirates Mastercard Credit Card

In short

189 of 255 attempts cleared, and most of those came from three merchants: App Store, Google Play, Epic Games Store.

523449Mastercard United Arab EmiratesCredit 189/255 cleared

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

523449 in plain terms

BIN
523449
Card network
Mastercard
Issuing country
United Arab Emirates
Card type
Credit
Issued by
FAB Global Digital Card
Card form
Virtual only
KYC tier
ID + proof
3-D Secure
Yes
AVS check
No
Billing address
Not published
Funding methods
Not published
Max cards per account
Not published
Issuer risk rating
Medium

What it costs to run

Pricing, laid out: no issuance fee to open a card, no top-up fee every time you fund it, and no FX markup on conversion. 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
Top-up fee
FX / conversion fee0% (multi-currency up to 15)
Declined transaction fee
Minimum top-up

Merchant 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
App Store817694%no friction, and no AVS prompt
Google Play666091%no friction, and no AVS prompt
Epic Games Store514486%went through on a fresh card with the issuer's default address
Nintendo eShop3300%3-D Secure challenge never completed. The order timed out waiting for the OTP.
GOAT24938%Soft decline on the retry after an earlier failure on the same account.

Run from a United Arab Emirates-region account between 01 Jun to 17 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 Nintendo eShop, 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. 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. Use the United Arab Emirates address FAB Global Digital Card gives you, verbatim. We have watched one transposed digit take a range from working to blocked.

Our call

Verdict: worth keeping for United Arab Emirates checkouts. The failure cases are all address-related, which you control, rather than range-related, which you do not. Nothing here makes it the best option, and nothing makes it a bad one.

BIN questions, answered

What does the 523449 BIN tell a merchant?

Roughly: who issued it, where, and what kind of product it is. Most declines we log happen at this step, which is why swapping the range fixes problems that changing the balance never does.

Is 523449 a real card number?

It is the first six of sixteen digits. The remaining ten identify the account, and only FAB Global Digital Card can map those. A BIN alone will never get anyone into your money.

Why would 523449 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.

How we got these numbers

We bought a FAB Global Digital Card card, funded it, and pushed 255 charges through live merchant checkout pages between 01 Jun to 17 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 189 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 · 255 charges on record for this range.