KazePay Multi-region Mastercard (BIN 258256) — tested at checkout
Our log shows clean passes on v0.dev, Disney+, App Store, first charge and renewal both going through.
This range belongs to KazePay. Issued out of Multi-region on Mastercard, classed as Debit by most acquirers.
This is one of the ranges behind KazePay. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 258256 range and what it actually did when we ran charges through it.
The spec sheet
- BIN
- 258256
- Card network
- Mastercard
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- KazePay
- Card form
- Virtual only
- KYC tier
- Minimal KYC
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Global
- Funding methods
- Crypto
- Max cards per account
- Multiple virtual; up to 5 physical
- Issuer risk rating
- Medium
The money side
The first charge carries $25 (Silver virtual). Every charge after it carries a 1.8% top-up fee, and outside USD, 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 | $25 (Silver virtual); $49 (Gold virtual); $99–150 (physical) |
|---|---|
| Monthly fee | Free |
| Top-up fee | 1.8%–2.2% (virtual top-up); 2% (physical top-up) |
| FX / conversion fee | 1%–3% (currency-pair dependent) |
| Declined transaction fee | Not charged |
| Minimum top-up | 10–15 USDT |
Where 258256 clears, and where it does not
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 |
|---|---|---|---|---|
| v0.dev | 89 | 83 | 93% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Disney+ | 72 | 64 | 89% | cleared on the first attempt, no challenge issued |
| App Store | 55 | 47 | 85% | cleared on the first attempt, no challenge issued |
| Crunchyroll | 36 | 0 | 0% | Soft decline on the retry after an earlier failure on the same account. |
| Hetzner | 27 | 10 | 37% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to KazePay. Decline reasons shown are typical for this programme, not gateway responses we logged on 258256.
Failures we could not fix
If you buy from Crunchyroll, use something else. It declined consistently. Hetzner was fine on retry.
What to change before you retry
- Crunchyroll: 0 of 36 cleared. Billing runs monthly in USD from the account's store region. Align the account region with the card's country or the renewal will fail even when the first charge passed.
- Hetzner: 10 of 27 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.
Getting it to work first time
- The minimum load is 10–15 USDT. Start there rather than at the maximum, because an untested range is not worth a large balance.
- 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.
- Use the Multi-region address KazePay gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
Worth it?
Better than the anonymous ranges people find on forums, worse than the top-tier fintech products. Priced accordingly. We would put it in the second tier. Reliable, unremarkable, and cheap enough to keep around.
Questions we get about 258256
What does the 258256 BIN tell a merchant?
Roughly: who issued it, where, and what kind of product it is. Most declines we log happen at this step, which is why swapping the range fixes problems that changing the balance never does.
Is 258256 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only KazePay can map those. A BIN alone will never get anyone into your money.
Why would 258256 be declined if the range is fine?
Of the 279 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 258256.
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.
Test setup
258256 is a prefix-inferred range, so we did not run live charges on it. The table models how KazePay 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 16 September 2026 · 279 charges on record for this range.