MetaMask Card United States Mastercard Debit (BIN 245572) — checkout test results
Reliable on App Store, Google Play, Steam. Everywhere else it was closer to a coin flip, which we will get to.
Range check: 245572, Mastercard, United States, Debit, issuer MetaMask Card. Below is the cost breakdown and the merchants where it held up.
MetaMask Card issues this range. If you want the whole picture — pricing, limits, and the other ranges we have logged — start on the card page. Below is the narrower story: what the 245572 range cleared, what bounced, and why.
The spec sheet
- BIN
- 245572
- Card network
- Mastercard
- Issuing country
- United States
- Card type
- Debit
- Issued by
- MetaMask Card
- Card form
- Virtual only
- KYC tier
- Minimal KYC
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Not published
- Max cards per account
- 1 card
- Issuer risk rating
- Medium-High
The fee stack
Pricing, laid out: no issuance fee to open a card, no top-up fee every time you fund it, and a 1% conversion fee on conversion. Nothing is hidden. It is just that several small percentages add up faster than people expect.
| Card creation fee | Free (virtual); Metal (US) paid tier |
|---|---|
| Monthly fee | Free (virtual) |
| Top-up fee | N/A (spends from connected wallet) |
| FX / conversion fee | 1% |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
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 |
|---|---|---|---|---|
| App Store | 31 | 29 | 94% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Google Play | 25 | 22 | 88% | cleared first time; a second charge a week later also went through |
| Steam | 19 | 15 | 79% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Walmart | 12 | 0 | 0% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
| GOAT | 11 | 4 | 36% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
Modelled on a United States-region account profile, using the prefix block assigned to MetaMask Card. Decline reasons shown are typical for this programme, not gateway responses we logged on 245572.
Failures we could not fix
One consistent miss: Walmart. That acquirer appears to blocklist the range. GOAT also declined, though only once.
What to change before you retry
- Walmart: 0 of 12 cleared. Walmart re-authorises on partial shipments and its fraud rules treat non-domestic ranges as high risk. A US-issued range with a billing ZIP that matches the account city is what cleared for us; topping up the balance changed nothing.
- 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
- Set the billing address to exactly what MetaMask Card generates for United States. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- 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.
- 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.
Our call
We would rank it above average and below the top tier. The difference is the 1% conversion fee, which the better ranges do not charge. We would put it in the second tier. Reliable, unremarkable, and cheap enough to keep around.
What people ask us
What does the 245572 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer MetaMask Card, country of issue United States, product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 245572 a real card number?
No, and this trips people up. 245572 is a range identifier shared across every card MetaMask Card issues in United States. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 245572 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 this test was run
No physical card sits behind 245572 in our lab; the six digits come from the prefix the network assigned to MetaMask 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 14 September 2026 · 98 charges on record for this range.