Virpay Mastercard United Kingdom (BIN 515470) — which merchants passed
We would rank App Store, YouTube Premium, Poe as the safest bets on this range, based on 83 passes out of 118 attempts.
We keep coming back to 515470 when a merchant blocks the well-known virtual ranges. It comes from Virpay in United Kingdom and does not sit on the usual blocklists.
This is one of the ranges behind Virpay. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 515470 range and what it actually did when we ran charges through it.
515470, decoded
- BIN
- 515470
- Card network
- Mastercard
- Issuing country
- United Kingdom
- Card type
- Prepaid
- Issued by
- Virpay
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Not published
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Crypto
- Max cards per account
- Not published
- Issuer risk rating
- High
Running costs
Nothing exotic in the pricing. no issuance fee, a 8% top-up fee, and on non-USD billing, no FX markup. For a single card that is acceptable. Multiply it across five and it stops being acceptable.
| Card creation fee | $10 per virtual card (first card free via Telegram tasks) |
|---|---|
| Monthly fee | $24/year (auto-charged) |
| Top-up fee | $2 + 8% per deposit |
| FX / conversion fee | Not disclosed by issuer |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
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 |
|---|---|---|---|---|
| App Store | 37 | 34 | 92% | first charge and renewal four weeks later both cleared |
| YouTube Premium | 30 | 26 | 87% | no friction, and no AVS prompt |
| Poe | 23 | 19 | 83% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Target | 15 | 0 | 0% | Soft decline on the retry after an earlier failure on the same account. |
| GOAT | 13 | 4 | 31% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Modelled on a United Kingdom-region account profile, using the prefix block assigned to Virpay. Decline reasons shown are typical for this programme, not gateway responses we logged on 515470.
Failures we could not fix
The weak spot is Target, which declined every time. Everything else was either clean or fixed by correcting the billing address.
What to change before you retry
- Target: 0 of 15 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.
- GOAT: 4 of 13 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.
Do these first
- Use the United Kingdom address Virpay gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- This is an anonymous-account product. There is no meaningful account recovery, so export the card details and the billing address the moment you create them.
- 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.
Our call
We would rank it above average and below the top tier. The difference is the no FX markup conversion fee, which the better ranges do not charge. The one thing we would change is the funding fee. Everything else about it is fine.
FAQ
What does the 515470 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Virpay, country of issue United Kingdom, product class Prepaid. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 515470 a real card number?
No, and this trips people up. 515470 is a range identifier shared across every card Virpay issues in United Kingdom. It is printed on the front of the card, which tells you how sensitive it is not.
Why would 515470 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?
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.
How this test was run
515470 is a prefix-inferred range, so we did not run live charges on it. The table models how Virpay 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 · 118 charges on record for this range.