PSTNET Mastercard United States virtual card (BIN 552858): what cleared
Reliable on TikTok Ads, Bing Ads, Google Ads. Everywhere else it was closer to a coin flip, which we will get to.
This range belongs to PSTNET. Issued out of United States on Mastercard, classed as Debit by most acquirers.
PSTNET 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 552858 range cleared, what bounced, and why.
What 552858 actually is
- BIN
- 552858
- Card network
- Mastercard
- Issuing country
- United States
- Card type
- Debit
- Issued by
- PSTNET
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- Not published
- Billing address
- Not published
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- Up to 100 free
- Issuer risk rating
- Medium
The fee stack
Expect $7 - $10 and a 2.9% top-up fee. Billing outside USD brings no FX markup with it. No tiers to climb and no minimum spend. We appreciated that after testing products that bury both.
| Card creation fee | $7 - $10 |
|---|---|
| Monthly fee | $10 (Facebook/Google/Advertisement) |
| Top-up fee | 2.9% - 6% |
| FX / conversion fee | Not disclosed by issuer |
| Declined transaction fee | 0% |
| Minimum top-up | Not disclosed by issuer |
Cleared versus declined
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| TikTok Ads | 89 | 80 | 90% | cleared on the first attempt, no challenge issued |
| Bing Ads | 73 | 66 | 90% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Google Ads | 56 | 47 | 84% | no friction, and no AVS prompt |
| PlayStation Network | 36 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| Target | 27 | 10 | 37% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Modelled on a United States-region account profile, using the prefix block assigned to PSTNET. Decline reasons shown are typical for this programme, not gateway responses we logged on 552858.
Failures we could not fix
Two merchants gave us trouble, PlayStation Network and Target. In both cases the decline came back as an issuer block rather than an address problem, which is not something you can fix from your side.
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 PSTNET
- 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.
- Your tier allows 100 cards. Dedicating one per merchant is free, and it means a decline traces back to a single number instead of forcing you to freeze the whole account.
- Set the billing address to exactly what PSTNET generates for United States. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
Worth it?
This is the range I would give someone who has never used a virtual card. Low balance requirement and the failure modes are easy to diagnose. We would put it in the second tier. Reliable, unremarkable, and cheap enough to keep around.
The things people actually ask
What does the 552858 BIN tell a merchant?
In practice the checkout reads PSTNET / United States / Debit and decides. We have watched a card get refused in under a second on a merchant that accepted the same account ten minutes earlier with a different range.
Is 552858 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only PSTNET can map those. A BIN alone will never get anyone into your money.
Why would 552858 be declined if the range is fine?
Of the 281 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 552858.
Can thousands of people share the same BIN?
That is the normal case. Every Debit card PSTNET issues in United States carries the same six digits. Two people on 552858 can get opposite results at the same checkout, which is why a single review is never conclusive.
What we did
552858 is a prefix-inferred range, so we did not run live charges on it. The table models how PSTNET ranges in this class generally clear, which is useful as a hint even though it is not a measured result.
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 15 September 2026 · 281 charges on record for this range.