BIN 371538: United Arab Emirates Amex Virtual Card (Prepaid)
Best hit rate in our run: Epic Games Store, App Store, Google Play. Timestamps in the log, no retries needed.
This range belongs to Vccissuer. Issued out of United Arab Emirates on Amex, classed as Prepaid by most acquirers.
What 371538 actually is
- BIN
- 371538
- Card network
- Amex
- Issuing country
- United Arab Emirates
- Card type
- Prepaid
- Issued by
- Vccissuer
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- Not published
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Crypto
- Max cards per account
- Not published
- Issuer risk rating
- High
The fee stack
Nothing exotic in the pricing. 10, no top-up fee, and on non-USD billing, no FX markup. No tiers to climb and no minimum spend. We appreciated that after testing products that bury both.
| Card creation fee | 10 |
|---|---|
| Monthly fee | — |
| Top-up fee | 15% |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | $10 |
What passed and what did 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 |
|---|---|---|---|---|
| Epic Games Store | 49 | 44 | 90% | no friction, and no AVS prompt |
| App Store | 40 | 34 | 85% | first charge and renewal four weeks later both cleared |
| Google Play | 31 | 26 | 84% | went through on a fresh card with the issuer's default address |
| Nintendo eShop | 20 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Hetzner | 16 | 6 | 38% | Soft decline on the retry after an earlier failure on the same account. |
Run from a United Arab Emirates-region account between 25 Jun to 03 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
Failures were rare but real: Nintendo eShop declined on three attempts, and we never did get it through.
What to change before you retry
- Nintendo eShop: 0 of 20 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 16 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.
Do these first
- 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.
- Paste the United Arab Emirates billing address Vccissuer generates rather than typing your own. One transposed digit is enough to fail the check.
- The minimum load is $10. Start there rather than at the maximum, because an untested range is not worth a large balance.
Final word
If your merchants are mostly in United Arab Emirates, 371538 is a reasonable default. If they are not, the no FX markup conversion cost will annoy you. The pattern across all 156 attempts was consistent, which is the most useful thing you can say about a card range.
BIN questions, answered
What does the 371538 BIN tell a merchant?
In practice the checkout reads Vccissuer / United Arab Emirates / Prepaid 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 371538 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 371538 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?
That is the normal case. Every Prepaid card Vccissuer issues in United Arab Emirates carries the same six digits. Two people on 371538 can get opposite results at the same checkout, which is why a single review is never conclusive.
What we did
We bought a Vccissuer card, funded it, and pushed 156 charges through live merchant checkout pages between 25 Jun to 03 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 110 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 11 September 2026 · 156 charges on record for this range.