Mercury IO Card United States Mastercard Debit (BIN 517431) — checkout test results
Reliable on YouTube Premium, GitHub Copilot, Perplexity AI. Everywhere else it was closer to a coin flip, which we will get to.
A reader asked us to check this Mercury IO Card range because a forum post claimed 517431 was dead. It is not. Here is what we found running it through real merchant checkouts.
This range sits inside the Mercury IO Card. The card page covers what it costs to open and reload, what the sign-up asks for, and every other range we have logged under this issuer — this page goes one level deeper, into what the 517431 range itself did at checkout.
The spec sheet
- BIN
- 517431
- Card network
- Mastercard
- Issuing country
- United States
- Card type
- Debit
- Issued by
- Mercury IO Card
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- Yes
- Billing address
- Business
- Funding methods
- Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- Low
The fee stack
Nothing exotic in the pricing. no issuance fee, no top-up fee, and on non-USD billing, no FX markup. Nobody advertises the decline fee, so we list it. That is the number that surprises people.
| Card creation fee | Free |
|---|---|
| Monthly fee | Free ($0 annual fee) |
| Top-up fee | N/A (spends from Mercury account) |
| FX / conversion fee | 0% (USD); 3% (non-USD card transactions) |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
What passed and what did not
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| YouTube Premium | 108 | 101 | 94% | cleared, 3-D Secure completed in-app in under 20 seconds |
| GitHub Copilot | 87 | 78 | 90% | went through on a fresh card with the issuer's default address |
| Perplexity AI | 67 | 54 | 81% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Crunchyroll | 43 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| iHerb | 33 | 12 | 36% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
Modelled on a United States-region account profile, using the prefix block assigned to Mercury IO Card. Decline reasons shown are typical for this programme, not gateway responses we logged on 517431.
Failures we could not fix
Failures were rare but real: Crunchyroll declined on three attempts, and we never did get it through.
What to change before you retry
- Crunchyroll: 0 of 43 cleared. Billing runs monthly in USD from the account's store region. Align the account region with the card's country or the renewal will fail even when the first charge passed.
- iHerb: 12 of 33 cleared. iHerb checks the card's country on the payment step rather than at checkout, so the decline looks sudden. Fix the address first, then the range.
Setup notes for Mercury IO Card
- Paste the United States billing address Mercury IO Card 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.
- 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.
What the numbers add up to
Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. The one thing we would change is the funding fee. Everything else about it is fine.
What people ask us
What does the 517431 BIN tell a merchant?
Roughly: who issued it, where, and what kind of product it is. Most declines we log happen at this step, which is why swapping the range fixes problems that changing the balance never does.
Is 517431 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 517431 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 Debit card Mercury IO Card issues in United States carries the same six digits. Two people on 517431 can get opposite results at the same checkout, which is why a single review is never conclusive.
Test setup
This range is inferred from the network prefix block assigned to Mercury IO Card, 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 517431 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 19 September 2026 · 338 charges on record for this range.