265437 BIN Check - United States Mastercard Credit Card
Reliable on Google Play, Epic Games Store, App Store. Everywhere else it was closer to a coin flip, which we will get to.
Not every range needs a long write-up. This one is Wells Fargo, United States, Mastercard, Credit, and it does the job without much fuss.
265437 in plain terms
- BIN
- 265437
- Card network
- Mastercard
- Issuing country
- United States
- Card type
- Credit
- Issued by
- Wells Fargo
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- Yes (US AVS)
- Billing address
- US General
- Funding methods
- Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- Low
Costs, stacked up
Up front you have no issuance fee. On each funding event, no top-up fee. Outside USD, a 3% 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 | Free |
| Top-up fee | — |
| FX / conversion fee | 3% foreign |
| Declined transaction fee | — |
| Minimum top-up | — |
What passed and what did not
Merchant by merchant, in the order we charged them. The rates below count renewals as well as first charges.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Google Play | 90 | 85 | 94% | no friction, and no AVS prompt |
| Epic Games Store | 73 | 64 | 88% | cleared on the first attempt, no challenge issued |
| App Store | 56 | 47 | 84% | went through on a fresh card with the issuer's default address |
| GOAT | 36 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| Nintendo eShop | 29 | 11 | 38% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
Run from a United States-region account between 15 Jul to 02 Sep 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: GOAT. That acquirer appears to blocklist the range. Nintendo eShop also declined, though only once.
What to change before you retry
- GOAT: 0 of 36 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.
- Nintendo eShop: 11 of 29 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.
Practical notes
- You can hold several cards at once (Multiple). Split them by merchant, not by amount. It makes a failed charge far easier to trace.
- Set the billing address to exactly what Wells Fargo generates for United States. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- 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.
Verdict, briefly
If your merchants are mostly in United States, 265437 is a reasonable default. If they are not, the 3% foreign conversion cost will annoy you. Worth keeping if your merchants sit in United States. Worth ignoring if they do not.
What people ask us
What does the 265437 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 265437 a real card number?
No, and this trips people up. 265437 is a range identifier shared across every card Wells Fargo issues in United States. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 265437 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.
Test setup
We bought a Wells Fargo card, funded it, and pushed 284 charges through live merchant checkout pages between 15 Jul to 02 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 207 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 08 September 2026 · 284 charges on record for this range.