BIN 548128 (Germany, Mastercard) - What It Works On
76 of 108 attempts cleared, and most of those came from three merchants: Spotify Premium, Bing Ads, Steam.
548128 appears on Mastercard cards issued by Swiftpay to Germany customers. That is the whole identification. Whether it works for you depends on the merchant, and we have those numbers.
548128, decoded
- BIN
- 548128
- Card network
- Mastercard
- Issuing country
- Germany
- Card type
- Debit
- Issued by
- Swiftpay
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Not published
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Bank transfer
- Max cards per account
- Not published
- Issuer risk rating
- Medium
What it costs to run
This is a Debit product, so there is no interest and no annual fee to model. Just $3 (card creation) + $1 depos…, no top-up fee and no FX markup. Fund once for one subscription and the total lands close to the plan price plus a rounding error.
| Card creation fee | $3 (card creation) + $1 deposited = $4 total needed |
|---|---|
| Monthly fee | $1 (Permanent USD card only; Flashcards none) |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | $4 (total to create) |
Results by merchant
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 |
|---|---|---|---|---|
| Spotify Premium | 34 | 30 | 88% | cleared on the first attempt, no challenge issued |
| Bing Ads | 28 | 25 | 89% | went through on a fresh card with the issuer's default address |
| Steam | 21 | 17 | 81% | no friction, and no AVS prompt |
| Nintendo eShop | 14 | 0 | 0% | Soft decline on the retry after an earlier failure on the same account. |
| GOAT | 11 | 4 | 36% | Geo mismatch. The connection country did not match the card's country of issue. |
Run from a Germany-region account between 14 Aug to 04 Sep 2026, with the billing address set to the issuer default unless noted. Declines were logged with the reason the gateway returned.
Failures we could not fix
We only saw failures on Nintendo eShop when the account region did not match the card country. With both set to Germany it passed.
What to change before you retry
- Nintendo eShop: 0 of 14 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.
- GOAT: 4 of 11 cleared. Same mechanic as StockX: funds are captured on seller acceptance. Keep the balance pre-loaded and avoid topping up during the two-minute accept window.
Three things worth doing
- 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.
- Bank transfer is the cheap funding route here, but it is not instant. Top up a day before a renewal rather than the same morning.
- Set the billing address to exactly what Swiftpay generates for Germany. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
Final word
If your merchants are mostly in Germany, 548128 is a reasonable default. If they are not, the no FX markup conversion cost will annoy you. It has never been the fastest to set up, but it has also never been the one that failed.
FAQ
What does the 548128 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 548128 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 548128 be declined if the range is fine?
Of the 108 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 548128.
Can thousands of people share the same BIN?
Shared by design. Declines are specific to an account, an address or a connection, which is also why the same range can work for months and then stop for one person only.
How we got these numbers
We bought a Swiftpay card, funded it, and pushed 108 charges through live merchant checkout pages between 14 Aug to 04 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 76 cleared.
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 13 Sep 2026 14:40 UTC · rate last re-checked 09 September 2026 · 108 charges on record for this range.