BIN 512605: United Arab Emirates Mastercard Virtual Card (Debit)
Tested across 5 weeks. Meta Ads, Google Ads, Bing Ads held at or above 182 passes, and the failures clustered on two merchants only.
If you have a Mastercard card from Crospay that starts with 512605, this page is about your card. Country of issue is United Arab Emirates, product class is Debit.
512605 in plain terms
- BIN
- 512605
- Card network
- Mastercard
- Issuing country
- United Arab Emirates
- Card type
- Debit
- Issued by
- Crospay
- Card form
- Virtual only
- KYC tier
- Varies
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Multiple (40+ card types)
- Issuer risk rating
- Medium-High
The fee stack
Pricing, laid out: a Varies (tiered, as low as 0.5… to open a card, no top-up fee every time you fund it, and no FX markup on conversion. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.
| Card creation fee | Varies (tiered, as low as 0.5%) |
|---|---|
| Monthly fee | — |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
The test results
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 |
|---|---|---|---|---|
| Meta Ads | 80 | 74 | 92% | first charge and renewal four weeks later both cleared |
| Google Ads | 65 | 57 | 88% | cleared first time; a second charge a week later also went through |
| Bing Ads | 50 | 42 | 84% | went through on a fresh card with the issuer's default address |
| GOAT | 32 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| PlayStation Network | 24 | 9 | 38% | Geo mismatch. The connection country did not match the card's country of issue. |
Run from a United Arab Emirates-region account between 04 Aug to 08 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
GOAT 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
- GOAT: 0 of 32 cleared. Same mechanic as StockX: funds are captured on seller acceptance. Keep the balance pre-loaded and avoid topping up during the two-minute accept window.
- PlayStation Network: 9 of 24 cleared. Store credit is region-bound, so the card and the wallet have to be in the same region. Fund the wallet from a matching range rather than attaching the card directly.
Do these first
- Our risk rating for this issuer is on the high side. Keep balances low and do not park money on the card between charges.
- 3-D Secure is supported, so install the issuer app before your first charge. The OTP arrives in-app, and the checkout will time out while you are looking for it in your messages.
- Set the billing address to exactly what Crospay generates for United Arab Emirates. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
Verdict, briefly
Overall a solid Debit range for United Arab Emirates-region accounts. Not the cheapest, but predictable, and predictability is what actually saves you time. Nothing here makes it the best option, and nothing makes it a bad one.
BIN questions, answered
What does the 512605 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Crospay, 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 512605 a real card number?
No, and this trips people up. 512605 is a range identifier shared across every card Crospay issues in United Arab Emirates. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 512605 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.
Test setup
We bought a Crospay card, funded it, and pushed 251 charges through live merchant checkout pages between 04 Aug to 08 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 182 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 10 September 2026 · 251 charges on record for this range.