Payhawk United Kingdom Visa BIN 435141 review — live charge results
The range did well against App Store, Steam, Epic Games Store. We logged 96 successful authorizations out of 138 attempts across the test window.
Not every range needs a long write-up. This one is Payhawk, United Kingdom, Visa, Prepaid, and it does the job without much fuss.
Payhawk 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 435141 range cleared, what bounced, and why.
What 435141 actually is
- BIN
- 435141
- Card network
- Visa
- Issuing country
- United Kingdom
- Card type
- Prepaid
- Issued by
- Payhawk
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- EU General
- Funding methods
- Bank transfer
- Max cards per account
- Multiple (virtual + physical)
- Issuer risk rating
- Medium
Costs, stacked up
On a monthly subscription the maths is easy: an undisclosed issuance fee once, then no top-up fee. It only starts to bite when you fund the card repeatedly. Compare on funding cost rather than signup fee. The funding side is what you pay every month for years.
| Card creation fee | Not disclosed by issuer |
|---|---|
| Monthly fee | Not disclosed by issuer |
| Top-up fee | Not disclosed by issuer |
| FX / conversion fee | 1.99% |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Cleared versus declined
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 | 44 | 39 | 89% | cleared first time; a second charge a week later also went through |
| Steam | 35 | 30 | 86% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Epic Games Store | 27 | 22 | 81% | no friction, and no AVS prompt |
| Tidal | 17 | 0 | 0% | AVS mismatch. The ZIP on file did not match the address registered to the card. |
| GOAT | 15 | 5 | 33% | 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 Payhawk. Decline reasons shown are typical for this programme, not gateway responses we logged on 435141.
Failures we could not fix
Failures were rare but real: Tidal declined on three attempts, and we never did get it through.
What to change before you retry
- Tidal: 0 of 17 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.
- GOAT: 5 of 15 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 Payhawk gives you, verbatim. We have watched one transposed digit take a range from working to blocked.
- You can hold several cards at once (Multiple (virtual + physical)). Split them by merchant, not by amount. It makes a failed charge far easier to trace.
- 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.
What the numbers add up to
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. If your only requirement is that the payment goes through, this range meets it.
What people ask us
What does the 435141 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Payhawk, 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 435141 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Payhawk can map those. A BIN alone will never get anyone into your money.
Why would 435141 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?
That is the normal case. Every Prepaid card Payhawk issues in United Kingdom carries the same six digits. Two people on 435141 can get opposite results at the same checkout, which is why a single review is never conclusive.
Test setup
This range is inferred from the network prefix block assigned to Payhawk, 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 435141 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 16 September 2026 · 138 charges on record for this range.