Mastercard Virtual Card BIN 236971 - United States (Debit)
The range did well against Epic Games Store, Google Play, App Store. We logged 201 successful authorizations out of 279 attempts across the test window.
236971 appears on Mastercard cards issued by Stripe Issuing to United States customers. That is the whole identification. Whether it works for you depends on the merchant, and we have those numbers.
236971, decoded
- BIN
- 236971
- Card network
- Mastercard
- Issuing country
- United States
- Card type
- Debit
- Issued by
- Stripe Issuing
- Card form
- Virtual only
- KYC tier
- Face scan
- 3-D Secure
- Yes
- AVS check
- Yes (US AVS)
- Billing address
- US/EU/UK
- Funding methods
- Crypto · Alipay / WeChat · Bank transfer
- Max cards per account
- Unlimited (API)
- Issuer risk rating
- Low
Costs, stacked up
Compared with the rest of the directory this sits mid-table. a Not applicable (platform) to open, no top-up fee to fund, and no FX markup on conversion. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.
| Card creation fee | Not applicable (platform) |
|---|---|
| Monthly fee | 100 |
| Top-up fee | — |
| FX / conversion fee | 0.5% |
| Declined transaction fee | — |
| Minimum top-up | — |
Cleared versus declined
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 |
|---|---|---|---|---|
| Epic Games Store | 89 | 83 | 93% | first charge and renewal four weeks later both cleared |
| Google Play | 72 | 62 | 86% | cleared on the first attempt, no challenge issued |
| App Store | 55 | 46 | 84% | went through on a fresh card with the issuer's default address |
| PlayStation Network | 36 | 0 | 0% | Soft decline on the retry after an earlier failure on the same account. |
| Target | 27 | 10 | 37% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
Run from a United States-region account between 23 Jul to 27 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. Target also declined, though only once.
What to change before you retry
- PlayStation Network: 0 of 36 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.
- Target: 10 of 27 cleared. Target runs an address check on first orders. Set the card's billing address to the issuer default, use a ZIP in the same state as the account, and place the order from a stable connection.
Setup notes for Stripe Issuing
- Alipay and WeChat top-ups are supported, which makes this one of the easier ranges to fund without touching crypto. Keep individual top-ups small while you are testing.
- 3-D Secure is supported, so install the issuer app before your first charge. The OTP arrives in-app, and the checkout will time out while you are looking for it in your messages.
- Use the United States address Stripe Issuing gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
Where we land
It is the kind of card you forget about until a checkout fails, and then it is the one that works. Buy the card, run one small charge, and decide from that rather than from this page.
The things people actually ask
What does the 236971 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Stripe Issuing, 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 236971 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 236971 be declined if the range is fine?
Of the 279 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 236971.
Can thousands of people share the same BIN?
That is the normal case. Every Debit card Stripe Issuing issues in United States carries the same six digits. Two people on 236971 can get opposite results at the same checkout, which is why a single review is never conclusive.
What we did
We bought a Stripe Issuing card, funded it, and pushed 279 charges through live merchant checkout pages between 23 Jul to 27 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 201 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 30 August 2026 · 279 charges on record for this range.