OVpay Missed Check-Outs: Why You Got Charged €20 and How to Get It Back

Tapped your card on a Dutch train and got billed the maximum fare anyway? Here's why the system thinks you never checked out, and the exact correction flow that gets your money back.

Somewhere in your first months of Dutch public transport, it will happen: you'll glance at your bank app and find a €20 charge for a fifteen-minute train ride, or €4 for a two-stop tram hop. You're sure you tapped out. The system is sure you didn't. This is the missed check-out charge — the single most common OVpay complaint among newcomers — and the money is very much recoverable, provided you know the flow, the deadlines, and the one distinction (missed check-out versus failed check-in) that decides where your claim needs to go.

How OVpay works, and where the old card fits in

Dutch public transport runs on tap-in, tap-out. You hold your contactless debit or credit card — or the same card in your phone's wallet — against a reader when you board and again when you leave, and the fare is calculated from the distance between those two taps. That's OVpay, and it works on trains, trams, metros, and buses nationwide.

It's replacing the OV-chipkaart, the stored-value smart card that ran Dutch transport for nearly twenty years. The phase-out is genuinely underway now: anonymous OV-chipkaart sales stopped on 1 July 2026, and the card is scheduled for full retirement by late 2027, replaced by an account-based "OV-pas" for anyone who doesn't want to travel on a bank card — including an anonymous version, and a digital one that lives in your phone. Existing OV-chipkaarts keep working until then, and subscriptions like off-peak discounts still largely live on the OV-chipkaart or an OVpay-linked account depending on the operator. If you're arriving in 2026, the practical summary is: your bank card already works everywhere, and the plastic card era is winding down around you.

The relevant design detail for this guide: because fares are distance-based, the system only knows what to charge you when it sees both taps. One tap on its own is an open journey — and an open journey eventually gets closed for you, at a price you won't like.

Why the maximum-fare charge happens even when you're sure you tapped

When the system never registers a check-out, it can't compute a fare, so it charges the maximum possible one for that mode: €20 on the train, €4 on bus, tram, and metro (as of 2026). This isn't a fine — nobody's accusing you of fare-dodging — it's the fallback price for a journey with no known endpoint.

The frustrating cases are the ones where you genuinely did tap. Common culprits:

You tapped, but not on your carrier's pole. Larger stations host multiple operators — NS plus a regional carrier like Arriva — with separate, near-identical card readers on the same platform. Tap the wrong one and you've checked out with a company you never travelled with, while your real journey stays open.
You mixed devices. A physical card and that same card in Apple Pay or Google Wallet are different tokens to the system. Check in with the plastic, check out with the phone, and OVpay sees two half-journeys — both eventually billed at maximum fare. Same for checking in with your phone and out with your smartwatch.
The tap didn't register. A hurried swipe, a reader mid-reboot, an open gate you walked through behind someone — the beep you half-heard on a noisy platform wasn't necessarily your beep.
You tapped twice. On trams and buses, tapping the same reader again a moment later can read as an immediate check-out. You then travel four stops effectively unchecked-in, and things get untidy from there.

Getting your money back: the correction flow

The fix is a self-service correction, and it's less painful than most Dutch admin. You file it in the OVpay app, on ovpay.nl, or via uitcheckgemist.nl — the long-standing "missed check-out" portal that now handles OVpay disputes as well as old OV-chipkaart ones. You tell the form where you actually boarded and alighted, it recalculates the real fare, and the difference comes back to the card or account you travelled on.

Three timing rules matter:

You can't file immediately. Corrections open six hours after the journey, once the transaction has settled into your travel history. Filing the moment you spot the charge just won't work yet; make a note and come back that evening.
You have 60 days from the date of travel. Miss the window and the maximum fare stands.
There's an annual cap. NS limits you to three corrections per year, and other carriers apply similar limits. The system tolerates the occasional slip; it isn't designed to absorb a weekly habit.

For the form itself, precision helps: the exact stations or stops and the rough time. This is why the single best habit (more below) is checking your trip history the same day — you'll still remember which stop you got off at, which turns a ten-minute puzzle into a thirty-second form.

If a correction gets rejected or the situation is genuinely tangled — multiple legs, multiple cards, a charge you don't recognise at all — the carrier's customer service is the next step, with your OVpay travel history as evidence.

Failed check-ins are a different animal

Now the other direction: you had a valid ticket — say a QR-code e-ticket you scanned at the gate — but OVpay or the carrier's system claims you never checked in, and a charge or fine follows. This is a failed check-in, and it deliberately skips the self-service flow above. Uitcheckgemist.nl can't help you here, because there's no journey to recalculate.

Instead you go to the specific carrier whose gate or reader failed — NS, GVB (Amsterdam), RET (Rotterdam), HTM (The Hague), or the regional operator — through their customer service channel. Bring receipts, not stories: a screenshot of your OVpay app history showing the gap, the ticket confirmation email, a bank statement showing the charge, timestamps that line up. Carriers are generally reasonable once they see genuine payment-system evidence, because reader failures are a known problem on their side, not yours. If a gate ever misbehaves in the moment, a quick photo of its display is the single most persuasive attachment you can send later.

Double charges, and the tram-and-bus quirks

A few patterns look like billing errors but usually aren't:

The "double charge" that isn't. When you check in, your bank may show an immediate reservation — a pending authorisation — while the actual settled amount for the day's travel arrives a day or so later as a combined charge. For a short window, both are visible and it looks like you've paid twice. The pending one drops off on its own. Only if two settled charges cover the same journey do you have a real claim, and that goes through the correction flow or the carrier.

Transfers are one journey — within limits. Changing buses or trams on the same card counts as a continued journey rather than a fresh fare, as long as the transfer happens within about 35 minutes. Tap out of the first vehicle, tap into the next, and the pricing stitches them together. What breaks this is switching cards or devices mid-journey — the second leg starts a new journey on a new token, at a new base fare.

Trams and buses bill differently from trains. On the train, the €20 fallback is painful enough to notice immediately. On a tram, the €4 fallback is close enough to a normal fare that many people never spot it — which is exactly why it's worth actually reading your travel history rather than skimming your bank statement, where a €4 here and there disappears into the noise.

Habits that make this a non-issue

After a few months, residents stop getting these charges almost entirely. The habits that get you there:

One card, one device, the whole journey. Pick the physical card or the phone and stick with it for check-in and check-out — ideally for all your travel, so your history lives in one place.
Watch the screen, not just the beep. Readers show a checkmark or "goede reis" (have a good trip) on a successful tap. On busy platforms, the beep you hear is often someone else's.
Know your pole. At stations shared by multiple carriers, check the logo on the reader before tapping. NS readers for NS trains, the regional operator's for theirs.
Check your trip history the same day you travel. Ten seconds in the OVpay app. A missing check-out caught same-day is trivial to correct; one discovered on day 59 is a memory test.
Mind the gates that stand open. An open gate at a station still wants a tap. Walking through without one is the classic "I never even knew" missed check-out.

If you've just landed and are still assembling the basics — bank card that works contactless, Dutch SIM for the apps — the first 30 days checklist and getting a Dutch SIM cover that groundwork; a working Dutch bank account also makes the refunds land somewhere sensible.

FAQ

How long does the refund take once I file a correction? Typically a few working days to land back on the card or account you travelled with, though it can stretch a little longer around busy periods. The correction confirmation arrives faster than the money — that's normal.

I used my foreign bank card. Does the correction flow still work? Yes — OVpay doesn't care where the card was issued, and refunds go back to the same card. Watch out for your home bank's foreign-transaction fees turning a €16 refund into slightly less, but the flow itself is identical.

What if I genuinely forgot to check out and it was my fault? Same flow, no confession required. The correction form recalculates the fare you should have paid, and that's the amount you pay. Just remember the three-per-year cap — the system forgives occasional human error, not a habit.

Do I still tap out on the train if I have a subscription or discount? Always. Discounts are applied to the calculated fare, and there's no calculated fare without a check-out. Subscription holders who skip the tap get the same maximum-fare treatment as everyone else.