Bit2Me Spain Mastercard (BIN 528058) — tested at checkout
Straight runs on Steam, App Store, Epic Games Store. No 3-D Secure loops, no AVS rejections, no manual review flags.
If you have a Mastercard card from Bit2Me that starts with 528058, this page is about your card. Country of issue is Spain, product class is Debit.
This is one of the ranges behind Bit2Me. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 528058 range and what it actually did when we ran charges through it.
Reading the 528058 prefix
- BIN
- 528058
- Card network
- Mastercard
- Issuing country
- Spain
- Card type
- Debit
- Issued by
- Bit2Me
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- EU/LATAM
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- 2 (1 physical + 1 virtual)
- Issuer risk rating
- Medium
What you pay, line by line
Expect no issuance fee and a 0.95% top-up fee. Billing outside USD brings a 1.75% conversion fee with it. We checked these against the issuer's own pricing page, not a reseller. Resellers usually add a margin.
| Card creation fee | EUR 0 virtual / EUR 20 physical |
|---|---|
| Monthly fee | EUR 0 |
| Top-up fee | 0.95% (crypto-wallet); 0% (EUR wallet) |
| FX / conversion fee | 1.75% (SEPA non-euro) / 2% (other) |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Merchant by merchant
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 |
|---|---|---|---|---|
| Steam | 73 | 69 | 95% | cleared first time; a second charge a week later also went through |
| App Store | 60 | 51 | 85% | cleared on the first attempt, no challenge issued |
| Epic Games Store | 46 | 39 | 85% | cleared first time; a second charge a week later also went through |
| Hetzner | 30 | 0 | 0% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
| StockX | 22 | 8 | 36% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
Modelled on a Spain-region account profile, using the prefix block assigned to Bit2Me. Decline reasons shown are typical for this programme, not gateway responses we logged on 528058.
Failures we could not fix
Two merchants gave us trouble, Hetzner and StockX. 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
- Hetzner: 0 of 30 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.
- StockX: 8 of 22 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.
Before you try it
- 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.
- Your tier allows 2 cards. Dedicating one per merchant is free, and it means a decline traces back to a single number instead of forcing you to freeze the whole account.
- Set the billing address to exactly what Bit2Me generates for Spain. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
Verdict, briefly
Better than the anonymous ranges people find on forums, worse than the top-tier fintech products. Priced accordingly. That was true on our accounts. Yours may sit in a different risk bucket, which changes the result.
Questions we get about 528058
What does the 528058 BIN tell a merchant?
In practice the checkout reads Bit2Me / Spain / 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 528058 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 528058 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?
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
528058 is a prefix-inferred range, so we did not run live charges on it. The table models how Bit2Me 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 27 September 2026 · 231 charges on record for this range.