Bitget Wallet Card Latin America Mastercard (BIN 534998) — checkout test results
Where it cleared without drama: Google Ads, Bing Ads, Google Play. All three passed first time and survived a renewal four weeks later.
Bitget Wallet Card runs this range for Latin America. Six digits, Debit classification, Mastercard rails. Nothing clever about it, which is exactly why it keeps clearing.
This is one of the ranges behind Bitget Wallet Card. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 534998 range and what it actually did when we ran charges through it.
534998, decoded
- BIN
- 534998
- Card network
- Mastercard
- Issuing country
- Latin America
- Card type
- Debit
- Issued by
- Bitget Wallet Card
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes (Visa/Mastercard 3DS)
- AVS check
- Yes
- Billing address
- Residential
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Not specified
- Issuer risk rating
- Medium (Bitget; legacy Bitget Card stopped new apps Aug 2026)
The fee stack
The first charge carries no issuance fee. Every charge after it carries no top-up fee, and outside USD, a 1.7% conversion fee. Cost is the reason this range sits where it does in our ranking rather than higher up.
| Card creation fee | Free |
|---|---|
| Monthly fee | $0 (no monthly/annual; $1/mo after 12mo inactivity) |
| Top-up fee | Low fees |
| FX / conversion fee | 1.7% overall (0.9% crypto conversion + 1% FX) |
| Declined transaction fee | Not charged |
| Minimum top-up | No minimum |
Cleared versus declined
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 |
|---|---|---|---|---|
| Google Ads | 56 | 52 | 93% | cleared first time; a second charge a week later also went through |
| Bing Ads | 46 | 40 | 87% | went through on a fresh card with the issuer's default address |
| Google Play | 35 | 29 | 83% | cleared on the first attempt, no challenge issued |
| Hetzner | 23 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| Hulu | 18 | 6 | 33% | Geo mismatch. The connection country did not match the card's country of issue. |
Modelled on a Latin America-region account profile, using the prefix block assigned to Bitget Wallet Card. Decline reasons shown are typical for this programme, not gateway responses we logged on 534998.
Failures we could not fix
The pattern in our failures is geographic. Hetzner accepted it once the account region matched Latin America, and refused it every time it did not.
What to change before you retry
- Hetzner: 0 of 23 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.
- Hulu: 6 of 18 cleared. Hulu is US-only and rejects foreign ranges at the authorisation step. No configuration fixes this; use a US-issued range.
Practical notes
- Use the Latin America address Bitget Wallet Card gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- 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.
- This is an anonymous-account product. There is no meaningful account recovery, so export the card details and the billing address the moment you create them.
Where we land
We would not build a whole spend strategy on one Debit range, but as one card among two or three it earns its place. If you find a merchant where it behaves differently, tell us and we will add it to the log.
What people ask us
What does the 534998 BIN tell a merchant?
In practice the checkout reads Bitget Wallet Card / Latin America / 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 534998 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 534998 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.
How we got these numbers
No physical card sits behind 534998 in our lab; the six digits come from the prefix the network assigned to Bitget Wallet Card. 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 17 September 2026 · 178 charges on record for this range.