Mastercard Virtual Card BIN 527251 - United States (Prepaid)
Strongest results on v0.dev, Cursor, GitHub Copilot. Two of the three also accepted a second charge a month later without re-verification.
This range belongs to Cryptaacard. Issued out of United States on Mastercard, classed as Prepaid by most acquirers.
Reading the 527251 prefix
- BIN
- 527251
- Card network
- Mastercard
- Issuing country
- United States
- Card type
- Prepaid
- Issued by
- Cryptaacard
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- Yes
- AVS check
- Yes (US AVS)
- Billing address
- US billing address included
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- High
Costs, stacked up
Expect $100 (MC Classic/Visa Univers… and no top-up fee. Billing outside USD brings no FX markup with it. Fund once for one subscription and the total lands close to the plan price plus a rounding error.
| Card creation fee | $100 (MC Classic/Visa Universal); $200 (Visa Gold/Reloadable); $300 (Visa Platinum) |
|---|---|
| Monthly fee | — |
| Top-up fee | 5 (topup fee per pricing page) |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
Results by merchant
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 |
|---|---|---|---|---|
| v0.dev | 86 | 77 | 90% | cleared on the first attempt, no challenge issued |
| Cursor | 70 | 60 | 86% | cleared, 3-D Secure completed in-app in under 20 seconds |
| GitHub Copilot | 54 | 46 | 85% | cleared first time; a second charge a week later also went through |
| Target | 35 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Walmart | 25 | 9 | 36% | Soft decline on the retry after an earlier failure on the same account. |
Run from a United States-region account between 10 Jun to 19 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
Target 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
- Target: 0 of 35 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.
- Walmart: 9 of 25 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.
Three things worth doing
- You can hold several cards at once (Multiple). Split them by merchant, not by amount. It makes a failed charge far easier to trace.
- Paste the United States billing address Cryptaacard generates rather than typing your own. One transposed digit is enough to fail the check.
- Bank transfer is the cheap funding route here, but it is not instant. Top up a day before a renewal rather than the same morning.
Worth it?
Nothing here is a dealbreaker, but nothing is a standout either. It does the job on United States-region checkouts. For the price it is hard to argue with, provided you can live with the 5 (topup fee per pricing page) funding cost.
What people ask us
What does the 527251 BIN tell a merchant?
In practice the checkout reads Cryptaacard / United States / 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 527251 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Cryptaacard can map those. A BIN alone will never get anyone into your money.
Why would 527251 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.
How we got these numbers
We bought a Cryptaacard card, funded it, and pushed 270 charges through live merchant checkout pages between 10 Jun to 19 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 192 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 24 August 2026 · 270 charges on record for this range.