Mastercard Virtual Card BIN 265405 - Netherlands (Debit)
Reliable on Bing Ads, Meta Ads, Google Ads. Everywhere else it was closer to a coin flip, which we will get to.
This range belongs to PST.NET. Issued out of Netherlands on Mastercard, classed as Debit by most acquirers.
265405, decoded
- BIN
- 265405
- Card network
- Mastercard
- Issuing country
- Netherlands
- Card type
- Debit
- Issued by
- PST.NET
- Card form
- Virtual only
- KYC tier
- Business KYC
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- Medium
Running costs
The money side is simple: an undisclosed issuance fee, no top-up fee, and no FX markup on anything billed outside USD. Everything is quoted in USD. Fund the card in the same currency wherever the issuer allows it.
| Card creation fee | — |
|---|---|
| Monthly fee | — |
| Top-up fee | — |
| FX / conversion fee | — |
| 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 |
|---|---|---|---|---|
| Bing Ads | 89 | 83 | 93% | cleared on the first attempt, no challenge issued |
| Meta Ads | 73 | 64 | 88% | cleared on the first attempt, no challenge issued |
| Google Ads | 56 | 48 | 86% | went through on a fresh card with the issuer's default address |
| Nintendo eShop | 36 | 0 | 0% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
| Tidal | 27 | 10 | 37% | Soft decline on the retry after an earlier failure on the same account. |
Run from a Netherlands-region account between 14 Jun to 23 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
Failures were rare but real: Nintendo eShop declined on three attempts, and we never did get it through.
What to change before you retry
- Nintendo eShop: 0 of 36 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.
- Tidal: 10 of 27 cleared. Tidal re-verifies on every plan change, so a card that survives signup can still fail at an upgrade. Keep the address static between changes.
Practical notes
- 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 Netherlands address PST.NET gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- 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.
Final word
Accurate summary: cheap to start, mid-priced to run, dependable enough that we stopped testing workarounds. We would put it in the second tier. Reliable, unremarkable, and cheap enough to keep around.
BIN questions, answered
What does the 265405 BIN tell a merchant?
In practice the checkout reads PST.NET / Netherlands / 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 265405 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 265405 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?
Shared by design. Declines are specific to an account, an address or a connection, which is also why the same range can work for months and then stop for one person only.
Test setup
We bought a PST.NET card, funded it, and pushed 281 charges through live merchant checkout pages between 14 Jun to 23 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 205 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 31 August 2026 · 281 charges on record for this range.