462278 VCC - United Kingdom Visa Virtual Card Review
71 of 103 attempts cleared, and most of those came from three merchants: Steam, Google Play, App Store.
We keep coming back to 462278 when a merchant blocks the well-known virtual ranges. It comes from Onboard in United Kingdom and does not sit on the usual blocklists.
462278 in plain terms
- BIN
- 462278
- Card network
- Visa
- Issuing country
- United Kingdom
- Card type
- Debit
- Issued by
- Onboard
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Global
- Funding methods
- Crypto
- Max cards per account
- Multiple
- Issuer risk rating
- Medium
The money side
Three lines decide it. Issuance: no issuance fee. Funding: no top-up fee. Conversion: no FX markup. We checked these against the issuer's own pricing page, not a reseller. Resellers usually add a margin.
| Card creation fee | Free |
|---|---|
| Monthly fee | Free |
| Top-up fee | — |
| FX / conversion fee | — |
| Declined transaction fee | — |
| Minimum top-up | — |
The test results
Everything we pushed through this range, including the merchants it never cleared.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Steam | 32 | 29 | 91% | first charge and renewal four weeks later both cleared |
| Google Play | 26 | 22 | 85% | went through on a fresh card with the issuer's default address |
| App Store | 20 | 16 | 80% | first charge and renewal four weeks later both cleared |
| Target | 13 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| Hulu | 12 | 4 | 33% | Gateway risk rule fired and returned a generic decline with no challenge. |
Run from a United Kingdom-region account between 15 Jun to 24 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
Target 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
- Target: 0 of 13 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.
- Hulu: 4 of 12 cleared. Hulu is US-only and rejects foreign ranges at the authorisation step. No configuration fixes this; use a US-issued range.
Before you try it
- Set the billing address to exactly what Onboard generates for United Kingdom. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- Funding is crypto-first. Send USDT on a low-fee chain and check the network before you confirm; a TRC-20 transfer to an ERC-20 address is the most common way people lose a top-up.
- 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.
Where we land
Worth having as a backup rather than a primary. When a merchant blocks the popular ranges, 462278 is usually still open. The pattern across all 103 attempts was consistent, which is the most useful thing you can say about a card range.
BIN questions, answered
What does the 462278 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 462278 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 462278 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 Debit card Onboard issues in United Kingdom carries the same six digits. Two people on 462278 can get opposite results at the same checkout, which is why a single review is never conclusive.
Test setup
We bought a Onboard card, funded it, and pushed 103 charges through live merchant checkout pages between 15 Jun to 24 Aug 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 71 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 29 August 2026 · 103 charges on record for this range.