Plasbit Multi-region Visa (BIN 421673) — checkout test results
Tested across 11 weeks. Epic Games Store, App Store, Google Play held at or above 127 passes, and the failures clustered on two merchants only.
Range check: 421673, Visa, Multi-region, Debit, issuer Plasbit. Below is the cost breakdown and the merchants where it held up.
This range sits inside the Plasbit. 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 421673 range itself did at checkout.
421673 in plain terms
- BIN
- 421673
- Card network
- Visa
- Issuing country
- Multi-region
- Card type
- Debit
- Issued by
- Plasbit
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Bank transfer
- Max cards per account
- Multiple
- Issuer risk rating
- Medium
The money side
Nothing exotic in the pricing. no issuance fee, no top-up fee, and on non-USD billing, a 1.5% conversion fee. We checked these against the issuer's own pricing page, not a reseller. Resellers usually add a margin.
| Card creation fee | Free (issuance EUR/USD 0; plastic free delivery) |
|---|---|
| Monthly fee | Free (standard €1 virtual / €2 plastic monthly waived) |
| Top-up fee | 0% (loading fee waived) |
| FX / conversion fee | 1.5% (outside card currency) |
| Declined transaction fee | EUR/USD 25 chargeback |
| 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 |
|---|---|---|---|---|
| Epic Games Store | 57 | 52 | 91% | cleared first time; a second charge a week later also went through |
| App Store | 46 | 40 | 87% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Google Play | 35 | 29 | 83% | cleared, 3-D Secure completed in-app in under 20 seconds |
| GOAT | 23 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| PlayStation Network | 18 | 6 | 33% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
Modelled on a Multi-region-region account profile, using the prefix block assigned to Plasbit. Decline reasons shown are typical for this programme, not gateway responses we logged on 421673.
Failures we could not fix
GOAT rejected it outright. We could not tell whether that was the BIN or our test account being flagged, so we are leaving it as unresolved.
What to change before you retry
- GOAT: 0 of 23 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.
- PlayStation Network: 6 of 18 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.
Before you try it
- Paste the Multi-region billing address Plasbit generates rather than typing your own. One transposed digit is enough to fail the 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.
- 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.
Worth it?
If you only need one subscription this is more than enough. If you are running paid traffic at volume the 0% (loading fee waived) funding fee starts to hurt around the third month. If you find a merchant where it behaves differently, tell us and we will add it to the log.
FAQ
What does the 421673 BIN tell a merchant?
In practice the checkout reads Plasbit / Multi-region / 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 421673 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 421673 be declined if the range is fine?
Of the 179 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 421673.
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.
How we got these numbers
This range is inferred from the network prefix block assigned to Plasbit, not taken from a card we bought. The merchant breakdown below is a modelled illustration of how ranges in this programme typically perform, not a log of charges we ran on 421673 itself.
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 14 September 2026 · 179 charges on record for this range.