localcard Mastercard Multi-region (BIN 517013) — which merchants passed
Tested across 11 weeks. Disney+, Epic Games Store, App Store held at or above 183 passes, and the failures clustered on two merchants only.
517013 is the Mastercard range localcard hands out for Multi-region accounts. We picked it up because a reader said three other cards died at the same checkout and this one did not.
This is one of the ranges behind localcard. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 517013 range and what it actually did when we ran charges through it.
The spec sheet
- BIN
- 517013
- Card network
- Mastercard
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- localcard
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- No
- AVS check
- Yes
- Billing address
- Personal (no phone, no KYC for virtual)
- Funding methods
- Crypto · Alipay / WeChat
- Max cards per account
- Virtual + physical per user
- Issuer risk rating
- Medium (young platform Oct 2024; higher fees)
What you pay, line by line
On a monthly subscription the maths is easy: $30 virtual (higher than peer… once, then a 4% top-up fee. It only starts to bite when you fund the card repeatedly. No tiers to climb and no minimum spend. We appreciated that after testing products that bury both.
| Card creation fee | $30 virtual (higher than peers); physical ~$198 |
|---|---|
| Monthly fee | None (no monthly fee) |
| Top-up fee | ~4% combined top-up (USDT only) |
| FX / conversion fee | ~1% spend + ~1% cross-border + FX loss (~3% total) |
| Declined transaction fee | Yes |
| Minimum top-up | Not disclosed by issuer |
Merchant by merchant
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Disney+ | 82 | 73 | 89% | no friction, and no AVS prompt |
| Epic Games Store | 66 | 58 | 88% | cleared first time; a second charge a week later also went through |
| App Store | 51 | 43 | 84% | cleared on the first attempt, no challenge issued |
| Tidal | 33 | 0 | 0% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
| Hulu | 25 | 9 | 36% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to localcard. Decline reasons shown are typical for this programme, not gateway responses we logged on 517013.
Failures we could not fix
Failures were rare but real: Tidal declined on three attempts, and we never did get it through.
What to change before you retry
- Tidal: 0 of 33 cleared. Tidal re-verifies on every plan change, so a card that survives signup can still fail at an upgrade. Keep the address static between changes.
- Hulu: 9 of 25 cleared. Hulu is US-only and rejects foreign ranges at the authorisation step. No configuration fixes this; use a US-issued range.
Getting it to work first time
- Paste the Multi-region billing address localcard generates rather than typing your own. One transposed digit is enough to fail the check.
- 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.
- Funding is crypto-first. Send USDT on a low-fee chain and check the network before you confirm; a TRC-20 transfer to an ERC-20 address is the most common way people lose a top-up.
Verdict, briefly
We would rank it above average and below the top tier. The difference is the ~1% spend + ~1% cross-border… conversion fee, which the better ranges do not charge. The one thing we would change is the funding fee. Everything else about it is fine.
BIN questions, answered
What does the 517013 BIN tell a merchant?
In practice the checkout reads localcard / Multi-region / Debit 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 517013 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only localcard can map those. A BIN alone will never get anyone into your money.
Why would 517013 be declined if the range is fine?
Of the 257 attempts behind this page, the losses broke down as address mismatch first, incomplete 3-D Secure second, and merchant-side range blocks a distant third. Only the last one is about 517013.
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.
How we got these numbers
This range is inferred from the network prefix block assigned to localcard, not taken from a card we bought. The merchant breakdown below is a modelled illustration of how ranges in this programme typically perform, not a log of charges we ran on 517013 itself.
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 01 Oct 2026 14:40 UTC · rate last re-checked 21 September 2026 · 257 charges on record for this range.