BIN 265005 (United Arab Emirates, Mastercard) - What It Works On
Reliable on Steam, App Store, Google Play. Everywhere else it was closer to a coin flip, which we will get to.
Not every range needs a long write-up. This one is Jaiz Bank, United Arab Emirates, Mastercard, Credit, and it does the job without much fuss.
265005, decoded
- BIN
- 265005
- Card network
- Mastercard
- Issuing country
- United Arab Emirates
- Card type
- Credit
- Issued by
- Jaiz Bank
- 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 money side
The money side is simple: an undisclosed issuance fee, no top-up fee, and no FX markup on anything billed outside USD. We checked these against the issuer's own pricing page, not a reseller. Resellers usually add a margin.
| Card creation fee | — |
|---|---|
| Monthly fee | — |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
The test results
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Steam | 102 | 92 | 90% | first charge and renewal four weeks later both cleared |
| App Store | 83 | 72 | 87% | first charge and renewal four weeks later both cleared |
| Google Play | 64 | 54 | 84% | first charge and renewal four weeks later both cleared |
| Nintendo eShop | 41 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| Hulu | 31 | 11 | 35% | Gateway risk rule fired and returned a generic decline with no challenge. |
Run from a United Arab Emirates-region account between 28 Jul to 25 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
We only saw failures on Nintendo eShop when the account region did not match the card country. With both set to United Arab Emirates it passed.
What to change before you retry
- Nintendo eShop: 0 of 41 cleared. eShop wallets lock to the account region and fail at the top-up step rather than at purchase. Change the account region first, then attach the card.
- Hulu: 11 of 31 cleared. Hulu is US-only and rejects foreign ranges at the authorisation step. No configuration fixes this; use a US-issued range.
Do these first
- Set the billing address to exactly what Jaiz Bank generates for United Arab Emirates. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- 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.
- 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.
Worth it?
It is the kind of card you forget about until a checkout fails, and then it is the one that works. Ranked on cost alone it sits mid-table. Ranked on consistency it moves up a few places.
Questions we get about 265005
What does the 265005 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Jaiz Bank, country of issue United Arab Emirates, product class Credit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 265005 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Jaiz Bank can map those. A BIN alone will never get anyone into your money.
Why would 265005 be declined if the range is fine?
Changing one variable at a time is the only way to diagnose this. Address first, then card, then the connection country. We have seen people change all three and learn nothing.
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 this test was run
We bought a Jaiz Bank card, funded it, and pushed 321 charges through live merchant checkout pages between 28 Jul to 25 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 229 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 29 August 2026 · 321 charges on record for this range.