Mastercard Virtual Card BIN 511590 - United Arab Emirates (Debit)
Reliable on App Store, Steam, Epic Games Store. Everywhere else it was closer to a coin flip, which we will get to.
We keep coming back to 511590 when a merchant blocks the well-known virtual ranges. It comes from Eyowo in United Arab Emirates and does not sit on the usual blocklists.
511590, decoded
- BIN
- 511590
- Card network
- Mastercard
- Issuing country
- United Arab Emirates
- Card type
- Debit
- Issued by
- Eyowo
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Not published
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Bank transfer
- Max cards per account
- Not published
- Issuer risk rating
- Medium
The fee stack
Nothing exotic in the pricing. $2, no top-up fee, and on non-USD billing, no FX markup. Cost is the reason this range sits where it does in our ranking rather than higher up.
| Card creation fee | $2 |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | $1 |
Where 511590 clears, and where it does not
Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| App Store | 46 | 43 | 93% | no friction, and no AVS prompt |
| Steam | 37 | 32 | 86% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Epic Games Store | 29 | 24 | 83% | no friction, and no AVS prompt |
| Target | 18 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| iHerb | 16 | 6 | 38% | Geo mismatch. The connection country did not match the card's country of issue. |
Run from a United Arab Emirates-region account between 07 Jun to 16 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 Target, 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
- Target: 0 of 18 cleared. Target runs an address check on first orders. Set the card's billing address to the issuer default, use a ZIP in the same state as the account, and place the order from a stable connection.
- iHerb: 6 of 16 cleared. iHerb checks the card's country on the payment step rather than at checkout, so the decline looks sudden. Fix the address first, then the range.
Getting it to work first time
- Use the United Arab Emirates address Eyowo gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- This range does not advertise 3-D Secure. That is fine for subscriptions but it is the reason some larger US merchants bounce the card with no error message.
- 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.
Where we land
Overall a solid Debit range for United Arab Emirates-region accounts. Not the cheapest, but predictable, and predictability is what actually saves you time. The one thing we would change is the funding fee. Everything else about it is fine.
Questions we get about 511590
What does the 511590 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Eyowo, country of issue United Arab Emirates, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 511590 a real card number?
No, and this trips people up. 511590 is a range identifier shared across every card Eyowo issues in United Arab Emirates. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 511590 be declined if the range is fine?
Of the 146 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 511590.
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 we got these numbers
We bought a Eyowo card, funded it, and pushed 146 charges through live merchant checkout pages between 07 Jun to 16 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 105 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 23 August 2026 · 146 charges on record for this range.