406619 BIN Check - Singapore Visa Debit Card
Reliable on Steam, App Store, Google Play. Everywhere else it was closer to a coin flip, which we will get to.
Short entry for a range that punches above its weight. 406619 comes from Mercuryo Spend, Singapore, Visa, Debit. It is the card we hand people who have already failed twice elsewhere.
What the six digits say
- BIN
- 406619
- Card network
- Visa
- Issuing country
- Singapore
- Card type
- Debit
- Issued by
- Mercuryo Spend
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Global
- Funding methods
- Crypto
- Max cards per account
- Multiple
- Issuer risk rating
- Medium
What you pay, line by line
Compared with the rest of the directory this sits mid-table. no issuance fee to open, no top-up fee to fund, and no FX markup on conversion. For a single card that is acceptable. Multiply it across five and it stops being acceptable.
| Card creation fee | Free |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
The test results
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Steam | 65 | 59 | 91% | first charge and renewal four weeks later both cleared |
| App Store | 53 | 48 | 91% | cleared first time; a second charge a week later also went through |
| Google Play | 41 | 34 | 83% | cleared on the first attempt, no challenge issued |
| GOAT | 26 | 0 | 0% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
| Nike US | 21 | 7 | 33% | Geo mismatch. The connection country did not match the card's country of issue. |
Run from a Singapore-region account between 16 Jun to 01 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
Failures were rare but real: GOAT declined on three attempts, and we never did get it through.
What to change before you retry
- GOAT: 0 of 26 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.
- Nike US: 7 of 21 cleared. Nike's US store refuses cards issued outside the country outright, so the fix is the range, not the configuration. A domestic-issued range clears; a foreign one never will.
Do these first
- 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.
- Paste the Singapore billing address Mercuryo Spend generates rather than typing your own. One transposed digit is enough to fail the check.
- 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.
Worth it?
Nothing here is a dealbreaker, but nothing is a standout either. It does the job on Singapore-region checkouts. Nothing here makes it the best option, and nothing makes it a bad one.
What people ask us
What does the 406619 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Mercuryo Spend, country of issue Singapore, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 406619 a real card number?
No, and this trips people up. 406619 is a range identifier shared across every card Mercuryo Spend issues in Singapore. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 406619 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?
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
We bought a Mercuryo Spend card, funded it, and pushed 206 charges through live merchant checkout pages between 16 Jun to 01 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 148 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 03 September 2026 · 206 charges on record for this range.