BIN 233239: United Arab Emirates Mastercard Virtual Card (Credit)
Our log shows clean passes on Google Play, Epic Games Store, App Store, first charge and renewal both going through.
Range check: 233239, Mastercard, United Arab Emirates, Credit, issuer FAB Travel Card. Below is the cost breakdown and the merchants where it held up.
Reading the 233239 prefix
- BIN
- 233239
- Card network
- Mastercard
- Issuing country
- United Arab Emirates
- Card type
- Credit
- Issued by
- FAB Travel Card
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Customizable
- Funding methods
- Not published
- Max cards per account
- Up to 4
- Issuer risk rating
- Medium
Costs, stacked up
Expect a AED 30 and no top-up fee. Billing outside USD brings a 1% conversion fee with it. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.
| Card creation fee | AED 30 |
|---|---|
| Monthly fee | Free (if reload within 90 days) / AED 10 per quarter |
| Top-up fee | — |
| FX / conversion fee | ~1% markup |
| Declined transaction fee | — |
| Minimum top-up | AED 100 |
Cleared versus declined
Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Google Play | 40 | 36 | 90% | no friction, and no AVS prompt |
| Epic Games Store | 33 | 29 | 88% | cleared, 3-D Secure completed in-app in under 20 seconds |
| App Store | 25 | 20 | 80% | went through on a fresh card with the issuer's default address |
| Walmart | 16 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Nike US | 14 | 5 | 36% | Geo mismatch. The connection country did not match the card's country of issue. |
Run from a United Arab Emirates-region account between 25 Jun 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
If you buy from Walmart, use something else. It declined consistently. Nike US was fine on retry.
What to change before you retry
- Walmart: 0 of 16 cleared. Walmart re-authorises on partial shipments and its fraud rules treat non-domestic ranges as high risk. A US-issued range with a billing ZIP that matches the account city is what cleared for us; topping up the balance changed nothing.
- Nike US: 5 of 14 cleared. Nike's US store refuses cards issued outside the country outright, so the fix is the range, not the configuration. A domestic-issued range clears; a foreign one never will.
Three things worth doing
- FAB Travel Card lets you edit the billing address. Keep one version per merchant and reuse the exact string; rotating it mid-subscription is what breaks renewals.
- The minimum load is AED 100. Start there rather than at the maximum, because an untested range is not worth a large balance.
- Set the billing address to exactly what FAB Travel Card generates for United Arab Emirates. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
Verdict, briefly
This is the range I would give someone who has never used a virtual card. Low balance requirement and the failure modes are easy to diagnose. We would put it in the second tier. Reliable, unremarkable, and cheap enough to keep around.
The things people actually ask
What does the 233239 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer FAB Travel Card, 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 233239 a real card number?
Six digits of a sixteen-digit number. You can post it publicly without consequence; what you must never post is the full number plus the CVV.
Why would 233239 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?
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.
Test setup
We bought a FAB Travel Card card, funded it, and pushed 128 charges through live merchant checkout pages between 25 Jun 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. 90 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 · 128 charges on record for this range.