UUPAY Multi-region Mastercard (BIN 527720) — checkout test results
Reliable on Netflix, App Store, Spotify Premium. Everywhere else it was closer to a coin flip, which we will get to.
The first thing to know about 527720 is that it is not an anonymous range. UUPAY issues it in Multi-region and the Mastercard prefix is registered, which is why fewer merchants treat it as high risk.
This range sits inside the UUPAY. 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 527720 range itself did at checkout.
527720 in plain terms
- BIN
- 527720
- Card network
- Mastercard
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- UUPAY
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- No
- AVS check
- No
- Billing address
- Yes
- Funding methods
- Crypto · Alipay / WeChat · Bank transfer
- Max cards per account
- Multiple tiers
- Issuer risk rating
- Medium (issuer/BIN not fully public)
What it costs to run
Up front you have $10 (promo: 1 USDT, refunded…. On each funding event, a 1% top-up fee. Outside USD, a 1% conversion fee. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.
| Card creation fee | $10 (promo: 1 USDT, refunded 1 USDT) |
|---|---|
| Monthly fee | $0 (no annual fee) |
| Top-up fee | 0-1% (promo 0%, standard ~1%) |
| FX / conversion fee | 1% FX; 0.9% exchange |
| Declined transaction fee | $0.3 USDT (<30 USDT) / $0.5 USDT (failed auth) |
| Minimum top-up | 1% (standard) / Free (promo) |
Where 527720 clears, and where it does not
This table is the whole record: every attempt we made on the range, with the gateway's answer attached.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Netflix | 90 | 83 | 92% | cleared on the first attempt, no challenge issued |
| App Store | 73 | 65 | 89% | cleared on the first attempt, no challenge issued |
| Spotify Premium | 56 | 47 | 84% | went through on a fresh card with the issuer's default address |
| Nintendo eShop | 36 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| Hetzner | 29 | 11 | 38% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to UUPAY. Decline reasons shown are typical for this programme, not gateway responses we logged on 527720.
Failures we could not fix
One consistent miss: Nintendo eShop. That acquirer appears to blocklist the range. Hetzner also declined, though only once.
What to change before you retry
- Nintendo eShop: 0 of 36 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.
- Hetzner: 11 of 29 cleared. Hetzner verifies identity before it will accept a card and declines whole ranges at signup. Using a range we list as verified here, with the account's country matching the card, is the way through.
Setup notes for UUPAY
- Use the Multi-region address UUPAY gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- The minimum load is 1% (standard) / Free (promo). Start there rather than at the maximum, because an untested range is not worth a large balance.
- You can hold several cards at once (Multiple tiers). Split them by merchant, not by amount. It makes a failed charge far easier to trace.
Verdict, briefly
Overall a solid Debit range for Multi-region-region accounts. Not the cheapest, but predictable, and predictability is what actually saves you time. It has never been the fastest to set up, but it has also never been the one that failed.
The things people actually ask
What does the 527720 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer UUPAY, 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 527720 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 527720 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 UUPAY issues in Multi-region carries the same six digits. Two people on 527720 can get opposite results at the same checkout, which is why a single review is never conclusive.
How this test was run
No physical card sits behind 527720 in our lab; the six digits come from the prefix the network assigned to UUPAY. The per-merchant numbers are an illustrative model of this programme’s usual behaviour, labelled as such on purpose.
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 11 September 2026 · 284 charges on record for this range.