Mastercard Virtual Card BIN 538384 - Brazil (Debit)
The range did well against Steam, Epic Games Store, Google Play. We logged 185 successful authorizations out of 258 attempts across the test window.
The first thing to know about 538384 is that it is not an anonymous range. Nubank issues it in Brazil and the Mastercard prefix is registered, which is why fewer merchants treat it as high risk.
538384, decoded
- BIN
- 538384
- Card network
- Mastercard
- Issuing country
- Brazil
- Card type
- Debit
- Issued by
- Nubank
- 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
The money side
The first charge carries no issuance fee. Every charge after it carries no top-up fee, and outside USD, a 2.38% conversion fee. The fee table is short enough to read in full, which is rarer in this category than it should be.
| Card creation fee | Free |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | 2.38% IOF + FX fee |
| Declined transaction fee | — |
| Minimum top-up | — |
The test results
Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Steam | 82 | 76 | 93% | cleared first time; a second charge a week later also went through |
| Epic Games Store | 67 | 59 | 88% | went through on a fresh card with the issuer's default address |
| Google Play | 51 | 41 | 80% | no friction, and no AVS prompt |
| PlayStation Network | 33 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| Nike US | 25 | 9 | 36% | Soft decline on the retry after an earlier failure on the same account. |
Run from a Brazil-region account between 10 Jul to 28 Aug 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
One consistent miss: PlayStation Network. That acquirer appears to blocklist the range. Nike US also declined, though only once.
What to change before you retry
- PlayStation Network: 0 of 33 cleared. Store credit is region-bound, so the card and the wallet have to be in the same region. Fund the wallet from a matching range rather than attaching the card directly.
- Nike US: 9 of 25 cleared. Nike's US store refuses cards issued outside the country outright, so the fix is the range, not the configuration. A domestic-issued range clears; a foreign one never will.
Do these first
- Paste the Brazil billing address Nubank generates rather than typing your own. One transposed digit is enough to fail the check.
- 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.
- Watch the 2.38% conversion fee. Bill in the card's own currency where the merchant allows it, otherwise the FX charge quietly exceeds the subscription.
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 538384 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 538384 a real card number?
No, and this trips people up. 538384 is a range identifier shared across every card Nubank issues in Brazil. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 538384 be declined if the range is fine?
Changing one variable at a time is the only way to diagnose this. Address first, then card, then the connection country. We have seen people change all three and learn nothing.
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 Nubank card, funded it, and pushed 258 charges through live merchant checkout pages between 10 Jul to 28 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 185 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 01 September 2026 · 258 charges on record for this range.