BIN 243019: United Kingdom Mastercard Virtual Card (Debit)
We would rank Steam, Google Play, Epic Games Store as the safest bets on this range, based on 96 passes out of 135 attempts.
243019 is one of bunq's United Kingdom ranges, a Debit product on Mastercard.
243019, decoded
- BIN
- 243019
- Card network
- Mastercard
- Issuing country
- United Kingdom
- Card type
- Debit
- Issued by
- bunq
- Card form
- Virtual only
- KYC tier
- ID + proof
- 3-D Secure
- Yes
- AVS check
- No
- Billing address
- Not published
- Funding methods
- Not published
- Max cards per account
- Not published
- Issuer risk rating
- Medium
What you pay, line by line
This is a Debit product, so there is no interest and no annual fee to model. Just a Included in plan, no top-up fee and a 0.5% conversion fee. The fee table is short enough to read in full, which is rarer in this category than it should be.
| Card creation fee | Included in plan |
|---|---|
| Monthly fee | Free €0 / Core €3.99 / Pro €9.99 / Elite €18.99 |
| Top-up fee | — |
| FX / conversion fee | ~0.5% (ZeroFX) |
| Declined transaction fee | — |
| Minimum top-up | — |
The test results
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 |
|---|---|---|---|---|
| Steam | 43 | 39 | 91% | first charge and renewal four weeks later both cleared |
| Google Play | 35 | 30 | 86% | cleared first time; a second charge a week later also went through |
| Epic Games Store | 27 | 23 | 85% | no friction, and no AVS prompt |
| Hulu | 17 | 0 | 0% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
| Tidal | 13 | 4 | 31% | 3-D Secure challenge never completed. The order timed out waiting for the OTP. |
Run from a United Kingdom-region account between 23 Jun to 08 Sep 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
One consistent miss: Hulu. That acquirer appears to blocklist the range. Tidal also declined, though only once.
What to change before you retry
- Hulu: 0 of 17 cleared. Hulu is US-only and rejects foreign ranges at the authorisation step. No configuration fixes this; use a US-issued range.
- Tidal: 4 of 13 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.
Getting it to work first time
- Set the billing address to exactly what bunq generates for United Kingdom. Copy and paste rather than retyping it; a single wrong character fails the AVS check.
- 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.
- 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.
Worth it?
If your merchants are mostly in United Kingdom, 243019 is a reasonable default. If they are not, the ~0.5% (ZeroFX) conversion cost will annoy you. Ranked on cost alone it sits mid-table. Ranked on consistency it moves up a few places.
FAQ
What does the 243019 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 243019 a real card number?
It is the first six of sixteen digits. The remaining ten identify the account, and only bunq can map those. A BIN alone will never get anyone into your money.
Why would 243019 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?
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.
Test setup
We bought a bunq card, funded it, and pushed 135 charges through live merchant checkout pages between 23 Jun to 08 Sep 2026. Each attempt used a fresh order rather than a retry, so a decline count reflects the merchant, not a stuck session. 96 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 12 September 2026 · 135 charges on record for this range.