BinPay Multi-region Mastercard Debit (BIN 233900) — checkout test results
We would rank Spotify Premium, Google Play, YouTube Premium as the safest bets on this range, based on 236 passes out of 330 attempts.
If you have a Mastercard card from BinPay that starts with 233900, this page is about your card. Country of issue is Multi-region, product class is Debit.
This is one of the ranges behind BinPay. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 233900 range and what it actually did when we ran charges through it.
The spec sheet
- BIN
- 233900
- Card network
- Mastercard
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- BinPay
- Card form
- Virtual only
- KYC tier
- ID only
- 3-D Secure
- No
- AVS check
- Yes
- Billing address
- Personal/Business (crypto custody)
- Funding methods
- Crypto · Alipay / WeChat
- Max cards per account
- Virtual (Premium/Diamond) + physical
- Issuer risk rating
- Low (HK licensed, compliant)
Running costs
On a monthly subscription the maths is easy: a Premium $25 once, then a 1.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 | Premium $25; Diamond $25 (discount to ~$17); Physical $98 |
|---|---|
| Monthly fee | None ($0 monthly/annual) |
| Top-up fee | 1.3% top-up (Premium); 0.7% (Diamond); physical 1% |
| FX / conversion fee | No cross-border conversion fees; gateway fee $0.3 on txn <$50 |
| Declined transaction fee | Not charged |
| Minimum top-up | 21 USDT 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 |
|---|---|---|---|---|
| Spotify Premium | 105 | 97 | 92% | cleared on the first attempt, no challenge issued |
| Google Play | 85 | 73 | 86% | first charge and renewal four weeks later both cleared |
| YouTube Premium | 66 | 54 | 82% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Best Buy | 42 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| PlayStation Network | 32 | 12 | 38% | Gateway risk rule fired and returned a generic decline with no challenge. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to BinPay. Decline reasons shown are typical for this programme, not gateway responses we logged on 233900.
Failures we could not fix
Failures were rare but real: Best Buy declined on three attempts, and we never did get it through.
What to change before you retry
- Best Buy: 0 of 42 cleared. High-value orders land in manual review. Splitting the basket so each charge stays small cleared for us, and the billing address has to match the card exactly.
- PlayStation Network: 12 of 32 cleared. Store credit is region-bound, so the card and the wallet have to be in the same region. Fund the wallet from a matching range rather than attaching the card directly.
Setup notes for BinPay
- 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.
- Paste the Multi-region billing address BinPay generates rather than typing your own. One transposed digit is enough to fail the check.
- Funding is crypto-first. Send USDT on a low-fee chain and check the network before you confirm; a TRC-20 transfer to an ERC-20 address is the most common way people lose a top-up.
Our call
Two things decide it. The 1.3% top-up (Premium); 0.7% (Diam… top-up fee and the fact that it does not appear on the common virtual-range blocklists. Both work in its favour. That was true on our accounts. Yours may sit in a different risk bucket, which changes the result.
What people ask us
What does the 233900 BIN tell a merchant?
In practice the checkout reads BinPay / Multi-region / Debit and decides. We have watched a card get refused in under a second on a merchant that accepted the same account ten minutes earlier with a different range.
Is 233900 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 233900 be declined if the range is fine?
Of the 330 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 233900.
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.
Method
No physical card sits behind 233900 in our lab; the six digits come from the prefix the network assigned to BinPay. 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 28 September 2026 · 330 charges on record for this range.