Fiat24 Switzerland Mastercard BIN 263734 review — live charge results
Where it cleared without drama: Steam, Google Ads, Claude.ai. All three passed first time and survived a renewal four weeks later.
A reader asked us to check this Fiat24 range because a forum post claimed 263734 was dead. It is not. Here is what we found running it through real merchant checkouts.
This is one of the ranges behind Fiat24. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 263734 range and what it actually did when we ran charges through it.
263734, decoded
- BIN
- 263734
- Card network
- Mastercard
- Issuing country
- Switzerland
- Card type
- Debit
- Issued by
- Fiat24
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Swiss IBAN (multi-currency)
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- 1 (virtual only per account NFT)
- Issuer risk rating
- Medium (issuer-controlled, uninsured deposits)
The money side
Expect no issuance fee and a 1% top-up fee. Billing outside USD brings a 1.5% conversion fee with it. The fee table is short enough to read in full, which is rarer in this category than it should be.
| Card creation fee | Free (virtual); NFT mint fee 1-15,000 F24 token by tier |
|---|---|
| Monthly fee | Free |
| Top-up fee | 1% (Standard crypto top-up); 0.25-0.5% (Premium/Ultimate) |
| FX / conversion fee | 1-1.5% (non-EUR Mastercard); ~1.75% crypto-to-EUR conversion |
| Declined transaction fee | Not charged |
| Minimum top-up | $10 (activation balance) |
The test results
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 | 39 | 36 | 92% | cleared on the first attempt, no challenge issued |
| Google Ads | 31 | 26 | 84% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Claude.ai | 24 | 19 | 79% | no friction, and no AVS prompt |
| StockX | 15 | 0 | 0% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
| Nintendo eShop | 14 | 5 | 36% | Gateway risk rule fired and returned a generic decline with no challenge. |
Modelled on a Switzerland-region account profile, using the prefix block assigned to Fiat24. Decline reasons shown are typical for this programme, not gateway responses we logged on 263734.
Failures we could not fix
It failed twice on StockX, both times on an AVS mismatch rather than a range block. Setting the billing address to the issuer default fixed it.
What to change before you retry
- StockX: 0 of 15 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.
- Nintendo eShop: 5 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.
Three things worth doing
- 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.
- 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 Switzerland address Fiat24 gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
What the numbers add up to
We would not build a whole spend strategy on one Debit range, but as one card among two or three it earns its place. Take the Debit label seriously though. Some merchant rules treat it differently to credit.
Questions we get about 263734
What does the 263734 BIN tell a merchant?
In practice the checkout reads Fiat24 / Switzerland / 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 263734 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Fiat24 can map those. A BIN alone will never get anyone into your money.
Why would 263734 be declined if the range is fine?
Of the 123 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 263734.
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.
What we did
No physical card sits behind 263734 in our lab; the six digits come from the prefix the network assigned to Fiat24. 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 23 September 2026 · 123 charges on record for this range.