Mastercard Virtual Card BIN 233713 - United Arab Emirates (Debit)
Strongest results on Steam, Google Play, Epic Games Store. Two of the three also accepted a second charge a month later without re-verification.
There is not much to say about a BIN until you test one, so we ran 233713 from Kazepay Card against a live checkout and kept the log. Results below, including the two places it failed.
Reading the 233713 prefix
- BIN
- 233713
- Card network
- Mastercard
- Issuing country
- United Arab Emirates
- Card type
- Debit
- Issued by
- Kazepay Card
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Not published
- AVS check
- No
- Billing address
- Custodial
- Funding methods
- Crypto
- Max cards per account
- Not published
- Issuer risk rating
- Medium
The fee stack
Budget for a Not disclosed (FAQ: varies by…, no top-up fee, and a no decline fee penalty on declined authorizations. That last one only matters if you are pushing a lot of small charges. We checked these against the issuer's own pricing page, not a reseller. Resellers usually add a margin.
| Card creation fee | Not disclosed (FAQ: varies by type) |
|---|---|
| Monthly fee | — |
| Top-up fee | — |
| FX / conversion fee | — |
| 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
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Steam | 59 | 55 | 93% | cleared on the first attempt, no challenge issued |
| Google Play | 48 | 41 | 85% | cleared on the first attempt, no challenge issued |
| Epic Games Store | 37 | 31 | 84% | no friction, and no AVS prompt |
| Nintendo eShop | 24 | 0 | 0% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
| Hetzner | 17 | 6 | 35% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
Run from a United Arab Emirates-region account between 02 Jul to 27 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
Two merchants gave us trouble, Nintendo eShop and Hetzner. In both cases the decline came back as an issuer block rather than an address problem, which is not something you can fix from your side.
What to change before you retry
- Nintendo eShop: 0 of 24 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.
- Hetzner: 6 of 17 cleared. Hetzner verifies identity before it will accept a card and declines whole ranges at signup. Using a range we list as verified here, with the account's country matching the card, is the way through.
Setup notes for Kazepay Card
- 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.
- Set the billing address to exactly what Kazepay Card generates for United Arab Emirates. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- This is an anonymous-account product. There is no meaningful account recovery, so export the card details and the billing address the moment you create them.
Final word
If you only need one subscription this is more than enough. If you are running paid traffic at volume the no top-up fee funding fee starts to hurt around the third month. The one thing we would change is the funding fee. Everything else about it is fine.
Questions we get about 233713
What does the 233713 BIN tell a merchant?
In practice the checkout reads Kazepay Card / United Arab Emirates / Debit and decides. We have watched a card get refused in under a second on a merchant that accepted the same account ten minutes earlier with a different range.
Is 233713 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Kazepay Card can map those. A BIN alone will never get anyone into your money.
Why would 233713 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 Kazepay Card card, funded it, and pushed 185 charges through live merchant checkout pages between 02 Jul to 27 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 133 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 30 August 2026 · 185 charges on record for this range.