DuPay Mastercard Multi-region (BIN 248534) — which merchants passed
Reliable on Poe, Leonardo.ai, Claude.ai. Everywhere else it was closer to a coin flip, which we will get to.
Range check: 248534, Mastercard, Multi-region, Debit, issuer DuPay. Below is the cost breakdown and the merchants where it held up.
This range sits inside the DuPay. 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 248534 range itself did at checkout.
Reading the 248534 prefix
- BIN
- 248534
- Card network
- Mastercard
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- DuPay
- Card form
- Virtual only
- KYC tier
- No KYC
- 3-D Secure
- yes
- AVS check
- no
- Billing address
- virtual
- Funding methods
- Crypto · Alipay / WeChat
- Max cards per account
- multiple
- Issuer risk rating
- medium (compliance link opaque; card stability mixed)
What you pay, line by line
Three lines decide it. Issuance: no issuance fee. Funding: a 1.5% top-up fee. Conversion: a 1% conversion fee. We checked these against the issuer's own pricing page, not a reseller. Resellers usually add a margin.
| Card creation fee | $0-$10 (by card type) |
|---|---|
| Monthly fee | $0-$3 (some cards) |
| Top-up fee | 1.5%-3% USDT |
| FX / conversion fee | ~1% FTF |
| Declined transaction fee | Not charged |
| Minimum top-up | $5-$10 USDT |
Where 248534 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 |
|---|---|---|---|---|
| Poe | 100 | 95 | 95% | cleared on the first attempt, no challenge issued |
| Leonardo.ai | 81 | 69 | 85% | cleared on the first attempt, no challenge issued |
| Claude.ai | 62 | 51 | 82% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Nike US | 40 | 0 | 0% | Geo mismatch. The connection country did not match the card's country of issue. |
| StockX | 30 | 11 | 37% | Geo mismatch. The connection country did not match the card's country of issue. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to DuPay. Decline reasons shown are typical for this programme, not gateway responses we logged on 248534.
Failures we could not fix
If you buy from Nike US, use something else. It declined consistently. StockX was fine on retry.
What to change before you retry
- Nike US: 0 of 40 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.
- StockX: 11 of 30 cleared. Charges only happen when a bid is accepted, so the balance has to be sitting there before the seller responds. A card that funds on demand is what fails here, not the range.
Three things worth doing
- 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.
- The minimum load is $5-$10 USDT. Start there rather than at the maximum, because an untested range is not worth a large balance.
- Set the billing address to exactly what DuPay generates for Multi-region. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
Final word
Worth having as a backup rather than a primary. When a merchant blocks the popular ranges, 248534 is usually still open. We will keep it in the rotation and re-test it in a month.
Questions we get about 248534
What does the 248534 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer DuPay, 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 248534 a real card number?
No, and this trips people up. 248534 is a range identifier shared across every card DuPay issues in Multi-region. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 248534 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?
Yes, and it is worth internalising. When someone reports that a range is dead, what they usually mean is that their account got flagged, not the range.
How this test was run
No physical card sits behind 248534 in our lab; the six digits come from the prefix the network assigned to DuPay. 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 21 September 2026 · 313 charges on record for this range.