Nihao.cash Mastercard Multi-region (BIN 523743) — which merchants passed
Tested across 11 weeks. App Store, Google Play, Steam held at or above 192 passes, and the failures clustered on two merchants only.
Nihao.cash runs this range for Multi-region. Six digits, Debit classification, Mastercard rails. Nothing clever about it, which is exactly why it keeps clearing.
This is one of the ranges behind Nihao.cash. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 523743 range and what it actually did when we ran charges through it.
The spec sheet
- BIN
- 523743
- Card network
- Mastercard
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- Nihao.cash
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- No
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Crypto · Alipay / WeChat · Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- High
Running costs
The first charge carries an undisclosed issuance fee. Every charge after it carries a 1% top-up fee, and outside USD, no FX markup. Nothing is hidden. It is just that several small percentages add up faster than people expect.
| Card creation fee | Not disclosed by issuer |
|---|---|
| Monthly fee | Free (no monthly fee) |
| Top-up fee | 1% |
| FX / conversion fee | Not disclosed by issuer |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Where 523743 clears, and where it does not
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| App Store | 86 | 78 | 91% | first charge and renewal four weeks later both cleared |
| Google Play | 69 | 60 | 87% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Steam | 53 | 44 | 83% | went through on a fresh card with the issuer's default address |
| iHerb | 34 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Sephora US | 27 | 10 | 37% | Soft decline on the retry after an earlier failure on the same account. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to Nihao.cash. Decline reasons shown are typical for this programme, not gateway responses we logged on 523743.
Failures we could not fix
If you buy from iHerb, use something else. It declined consistently. Sephora US was fine on retry.
What to change before you retry
- iHerb: 0 of 34 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.
- Sephora US: 10 of 27 cleared. US and EU stores bill through different acquirers. Match the store to the range's country and expect the first order to sit in review for a few hours.
Practical notes
- Set the billing address to exactly what Nihao.cash generates for Multi-region. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- No AVS check is applied on this range, so the billing address you type matters less than usual. It still has to be consistent between the first charge and the renewal.
- 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.
Final word
Two things decide it. The 1% top-up fee and the fact that it does not appear on the common virtual-range blocklists. Both work in its favour. We will keep it in the rotation and re-test it in a month.
What people ask us
What does the 523743 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Nihao.cash, 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 523743 a real card number?
No, and this trips people up. 523743 is a range identifier shared across every card Nihao.cash issues in Multi-region. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 523743 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?
That is the normal case. Every Debit card Nihao.cash issues in Multi-region carries the same six digits. Two people on 523743 can get opposite results at the same checkout, which is why a single review is never conclusive.
What we did
523743 is a prefix-inferred range, so we did not run live charges on it. The table models how Nihao.cash 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 25 September 2026 · 269 charges on record for this range.