Mesh Payments Visa United States (BIN 483897) — which merchants passed
The range did well against App Store, Epic Games Store, Google Play. We logged 146 successful authorizations out of 200 attempts across the test window.
Mesh Payments issues 483897 out of United States. Classed Credit, runs on Visa.
This range sits inside the Mesh Payments. The card page covers what it costs to open and reload, what the sign-up asks for, and every other range we have logged under this issuer — this page goes one level deeper, into what the 483897 range itself did at checkout.
The spec sheet
- BIN
- 483897
- Card network
- Visa
- Issuing country
- United States
- Card type
- Credit
- Issued by
- Mesh Payments
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- Yes (US AVS)
- Billing address
- US/EU
- Funding methods
- Bank transfer
- Max cards per account
- Unlimited
- Issuer risk rating
- low
The money side
The first charge carries no issuance fee. Every charge after it carries no top-up fee, and outside USD, no FX markup. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.
| Card creation fee | Free |
|---|---|
| Monthly fee | $0 (Pro free up to 3 users; Premium $13/user/mo) |
| Top-up fee | 0% |
| FX / conversion fee | Not disclosed by issuer |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Merchant by merchant
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| App Store | 64 | 60 | 94% | first charge and renewal four weeks later both cleared |
| Epic Games Store | 52 | 46 | 88% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Google Play | 40 | 34 | 85% | cleared first time; a second charge a week later also went through |
| PlayStation Network | 26 | 0 | 0% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
| StockX | 18 | 6 | 33% | Gateway risk rule fired and returned a generic decline with no challenge. |
Modelled on a United States-region account profile, using the prefix block assigned to Mesh Payments. Decline reasons shown are typical for this programme, not gateway responses we logged on 483897.
Failures we could not fix
The weak spot is PlayStation Network, which declined every time. Everything else was either clean or fixed by correcting the billing address.
What to change before you retry
- PlayStation Network: 0 of 26 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.
- StockX: 6 of 18 cleared. Charges only happen when a bid is accepted, so the balance has to be sitting there before the seller responds. A card that funds on demand is what fails here, not the range.
Practical notes
- 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.
- 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 Mesh Payments gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
Where we land
Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. Ranked on cost alone it sits mid-table. Ranked on consistency it moves up a few places.
BIN questions, answered
What does the 483897 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Mesh Payments, country of issue United States, product class Credit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 483897 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 483897 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?
That is the normal case. Every Credit card Mesh Payments issues in United States carries the same six digits. Two people on 483897 can get opposite results at the same checkout, which is why a single review is never conclusive.
What we did
No physical card sits behind 483897 in our lab; the six digits come from the prefix the network assigned to Mesh Payments. 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 29 September 2026 · 200 charges on record for this range.