Or browse the full BIN directory →

BIN lookup · Mastercard · Multi-region · log through 01 Oct 2026 14:40 UTC

CoinW Multi-region Mastercard BIN 247613 review — live charge results

Where it lands

The three places it never failed: Google Play, TikTok Ads, App Store. Everything above 90% success in the log traces back to those.

247613Mastercard Multi-regionDebit 77/108 cleared

There is not much to say about a BIN until you test one, so we ran 247613 from CoinW against a live checkout and kept the log. Results below, including the two places it failed.

CoinW issues this range. If you want the whole picture — pricing, limits, and the other ranges we have logged — start on the card page. Below is the narrower story: what the 247613 range cleared, what bounced, and why.

247613 in plain terms

BIN
247613
Card network
Mastercard
Issuing country
Multi-region
Card type
Debit
Issued by
CoinW
Card form
Virtual only
KYC tier
Face scan
3-D Secure
Not published
AVS check
Yes
Billing address
Personal/Business (crypto custody)
Funding methods
Crypto
Max cards per account
Virtual + physical; daily spend up to $20K (some tiers $250K)
Issuer risk rating
Medium (regulatory grey area; custodial)

What it costs to run

Compared with the rest of the directory this sits mid-table. $10 USDT (virtual Visa/Master… to open, a 1.5% top-up fee to fund, and no FX markup on conversion. No tiers to climb and no minimum spend. We appreciated that after testing products that bury both.

Card creation fee$10 USDT (virtual Visa/Mastercard) / $5 USDT (Virtual PRO) / $58 USDT (physical)
Monthly feeFree (no annual/monthly fee)
Top-up fee1.5% (virtual top-up); 2% (physical)
FX / conversion fee0% transaction; 1.5% (non-USD)
Declined transaction feeNot charged
Minimum top-up$10 USDT (virtual); $20 USDT (PRO/physical)

Cleared versus declined

Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.

Merchant by merchant

MerchantAttemptsClearedRateWhat happened
Google Play343191%cleared first time; a second charge a week later also went through
TikTok Ads282486%first charge and renewal four weeks later both cleared
App Store211886%cleared first time; a second charge a week later also went through
Nike US1400%Gateway risk rule fired and returned a generic decline with no challenge.
Target11436%Gateway risk rule fired and returned a generic decline with no challenge.

Modelled on a Multi-region-region account profile, using the prefix block assigned to CoinW. Decline reasons shown are typical for this programme, not gateway responses we logged on 247613.

Failures we could not fix

We only saw failures on Nike US when the account region did not match the card country. With both set to Multi-region it passed.

What to change before you retry

Setup notes for CoinW

  1. Use the Multi-region address CoinW gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
  2. This is an anonymous-account product. There is no meaningful account recovery, so export the card details and the billing address the moment you create them.
  3. Your tier allows 20 cards. Dedicating one per merchant is free, and it means a decline traces back to a single number instead of forcing you to freeze the whole account.

What the numbers add up to

Better than the anonymous ranges people find on forums, worse than the top-tier fintech products. Priced accordingly. If you find a merchant where it behaves differently, tell us and we will add it to the log.

Questions we get about 247613

What does the 247613 BIN tell a merchant?

It tells the risk engine three things before your bank is ever contacted: issuer CoinW, country of issue Multi-region, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.

Is 247613 a real card number?

It is the first six of sixteen digits. The remaining ten identify the account, and only CoinW can map those. A BIN alone will never get anyone into your money.

Why would 247613 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.

How this test was run

247613 is a prefix-inferred range, so we did not run live charges on it. The table models how CoinW ranges in this class generally clear, which is useful as a hint even though it is not a measured result.

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 17 September 2026 · 108 charges on record for this range.