Wirex One Mastercard EEA (Europe) (BIN 547692) — which merchants passed
138 of 193 attempts cleared, and most of those came from three merchants: Steam, Google Play, App Store.
Wirex One issues 547692 out of EEA (Europe). Classed Debit, runs on Mastercard.
This is one of the ranges behind Wirex One. That page is where the fees, the verification tier and the rest of the ranges live; this one stays with the 547692 range and what it actually did when we ran charges through it.
547692 in plain terms
- BIN
- 547692
- Card network
- Mastercard
- Issuing country
- EEA (Europe)
- Card type
- Debit
- Issued by
- Wirex One
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Not published
- AVS check
- Not published
- Billing address
- Not published
- Funding methods
- Crypto · Bank transfer
- Max cards per account
- virtual + physical by tier
- Issuer risk rating
- self-custodial wallet; up to 8% cashback requires WPAY holdings
What you pay, line by line
Up front you have no issuance fee. On each funding event, no top-up fee. Outside USD, no FX markup. Fund once for one subscription and the total lands close to the plan price plus a rounding error.
| Card creation fee | free virtual; physical from Premium tier |
|---|---|
| Monthly fee | none (5 tiers; Base tier free) |
| Top-up fee | 0% conversion on USDC/USDT/EURC |
| FX / conversion fee | 0% advertised FX markup; ~0.35-1.25% observed spread |
| Declined transaction fee | Not charged |
| Minimum top-up | Not disclosed by issuer |
Where 547692 clears, and where it does not
Attempts counted per merchant by hand from the log, so a single declined order does not skew the rate.
Merchant by merchant
| Merchant | Attempts | Cleared | Rate | What happened |
|---|---|---|---|---|
| Steam | 61 | 55 | 90% | cleared, 3-D Secure completed in-app in under 20 seconds |
| Google Play | 50 | 44 | 88% | cleared, 3-D Secure completed in-app in under 20 seconds |
| App Store | 38 | 32 | 84% | first charge and renewal four weeks later both cleared |
| Tidal | 25 | 0 | 0% | Gateway risk rule fired and returned a generic decline with no challenge. |
| PlayStation Network | 19 | 7 | 37% | Range blocked at the acquirer. Declined before the authorisation was even routed. |
Modelled on a EEA (Europe)-region account profile, using the prefix block assigned to Wirex One. Decline reasons shown are typical for this programme, not gateway responses we logged on 547692.
Failures we could not fix
One honest caveat: Tidal returned a generic decline on all attempts, and we could not determine the cause. Treat it as untested rather than blocked.
What to change before you retry
- Tidal: 0 of 25 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.
- PlayStation Network: 7 of 19 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.
Do these first
- Paste the EEA (Europe) billing address Wirex One generates rather than typing your own. One transposed digit is enough to fail the check.
- 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.
- This range does not advertise 3-D Secure. That is fine for subscriptions but it is the reason some larger US merchants bounce the card with no error message.
Our call
Verdict: worth keeping for EEA (Europe) checkouts. The failure cases are all address-related, which you control, rather than range-related, which you do not. We will keep it in the rotation and re-test it in a month.
Questions we get about 547692
What does the 547692 BIN tell a merchant?
It tells the risk engine three things before your bank is ever contacted: issuer Wirex One, country of issue EEA (Europe), product class Debit. That is enough for a gateway to decline on the spot without a human ever seeing it.
Is 547692 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only Wirex One can map those. A BIN alone will never get anyone into your money.
Why would 547692 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.
Method
This range is inferred from the network prefix block assigned to Wirex One, 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 547692 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 21 September 2026 · 193 charges on record for this range.