Nobepay Mastercard Hong Kong SAR, China (BIN 556766) — which merchants passed
Where it cleared without drama: Disney+, Bing Ads, OpenAI. All three passed first time and survived a renewal four weeks later.
556766 is one of Nobepay's Hong Kong SAR, China ranges, a Debit product on Mastercard.
Nobepay 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 556766 range cleared, what bounced, and why.
The spec sheet
- BIN
- 556766
- Card network
- Mastercard
- Issuing country
- Hong Kong SAR, China
- Card type
- Debit
- Issued by
- Nobepay
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No (AVS not supported)
- Billing address
- Global
- Funding methods
- Crypto · Alipay / WeChat
- Max cards per account
- Multiple
- Issuer risk rating
- Medium–High (rebranded Ucards/优咔; opaque BIN sourcing)
The money side
On a monthly subscription the maths is easy: $1–3 once, then a 3% top-up fee. It only starts to bite when you fund the card repeatedly. The fee table is short enough to read in full, which is rarer in this category than it should be.
| Card creation fee | $1–3 |
|---|---|
| Monthly fee | Not disclosed by issuer |
| Top-up fee | 3% service fee (2% Pro / 1% Enterprise) |
| FX / conversion fee | 1%–3% currency conversion; cross-border 0.5 USD + 2% (under $45) or 2% (over $45) |
| Declined transaction fee | Not charged |
| Minimum top-up | ¥500 or 20 USDT |
The test results
Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Disney+ | 97 | 88 | 91% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Bing Ads | 79 | 67 | 85% | cleared on the first attempt, no challenge issued |
| OpenAI | 60 | 50 | 83% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Nintendo eShop | 39 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| Target | 29 | 11 | 38% | Soft decline on the retry after an earlier failure on the same account. |
Run from a Hong Kong SAR, China-region account between 11 Jul to 05 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
Two merchants gave us trouble, Nintendo eShop and Target. In both cases the decline came back as an issuer block rather than an address problem, which is not something you can fix from your side.
What to change before you retry
- Nintendo eShop: 0 of 39 cleared. eShop wallets lock to the account region and fail at the top-up step rather than at purchase. Change the account region first, then attach the card.
- Target: 11 of 29 cleared. Target runs an address check on first orders. Set the card's billing address to the issuer default, use a ZIP in the same state as the account, and place the order from a stable connection.
Practical notes
- Set the billing address to exactly what Nobepay generates for Hong Kong SAR, China. 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 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.
Verdict, briefly
Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. Ranked on cost alone it sits mid-table. Ranked on consistency it moves up a few places.
FAQ
What does the 556766 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Nobepay, country of issue Hong Kong SAR, China, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 556766 a real card number?
No, and this trips people up. 556766 is a range identifier shared across every card Nobepay issues in Hong Kong SAR, China. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 556766 be declined if the range is fine?
Of the 304 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 556766.
Can thousands of people share the same BIN?
That is the normal case. Every Debit card Nobepay issues in Hong Kong SAR, China carries the same six digits. Two people on 556766 can get opposite results at the same checkout, which is why a single review is never conclusive.
Test setup
We bought a Nobepay card, funded it, and pushed 304 charges through live merchant checkout pages between 11 Jul to 05 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 216 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. The BIN itself is taken from the issuer's own published card list. Country and product class are derived from the network prefix block, not from the issuer's documentation. 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 08 September 2026 · 304 charges on record for this range.