229244 VCC - United Arab Emirates Mastercard Virtual Card Review
Our log shows clean passes on App Store, Steam, Google Play, first charge and renewal both going through.
229244 is the Mastercard range Sendbit hands out for United Arab Emirates accounts. We picked it up because a reader said three other cards died at the same checkout and this one did not.
229244, decoded
- BIN
- 229244
- Card network
- Mastercard
- Issuing country
- United Arab Emirates
- Card type
- Debit
- Issued by
- Sendbit
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Not published
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Not published
- Max cards per account
- Not published
- Issuer risk rating
- Medium
Running costs
Three lines decide it. Issuance: $1.5. Funding: no top-up fee. Conversion: no FX markup. For a single card that is acceptable. Multiply it across five and it stops being acceptable.
| Card creation fee | $1.5 |
|---|---|
| Monthly fee | Free (no monthly fee; third-party) |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | 3 |
The test results
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| App Store | 57 | 54 | 95% | no friction, and no AVS prompt |
| Steam | 47 | 42 | 89% | went through on a fresh card with the issuer's default address |
| Google Play | 36 | 30 | 83% | cleared on the first attempt, no challenge issued |
| Nike US | 23 | 0 | 0% | Soft decline on the retry after an earlier failure on the same account. |
| Target | 18 | 6 | 33% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Run from a United Arab Emirates-region account between 30 Jun to 01 Sep 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
Nike US rejected it outright. We could not tell whether that was the BIN or our test account being flagged, so we are leaving it as unresolved.
What to change before you retry
- Nike US: 0 of 23 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.
- Target: 6 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.
Getting it to work first time
- The minimum load is 3. Start there rather than at the maximum, because an untested range is not worth a large balance.
- Use the United Arab Emirates address Sendbit gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- 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.
Our call
Worth having as a backup rather than a primary. When a merchant blocks the popular ranges, 229244 is usually still open. That was true on our accounts. Yours may sit in a different risk bucket, which changes the result.
What people ask us
What does the 229244 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Sendbit, 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 229244 a real card number?
No, and this trips people up. 229244 is a range identifier shared across every card Sendbit issues in United Arab Emirates. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 229244 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?
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 Sendbit card, funded it, and pushed 181 charges through live merchant checkout pages between 30 Jun to 01 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 132 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 03 September 2026 · 181 charges on record for this range.