Bence Halász, payments analyst

Why the cashier and not the games

My working years were spent in the back office of a payment provider, where most of the job consisted of untangling transactions that had stopped somewhere. That is where the idea behind this site was formed: delay almost never originates where the user looks for it. Customers blamed their bank, the bank blamed the provider, the provider blamed the merchant — and the log usually showed an item that had sat eleven hours in an approval queue and then settled in three seconds.

Carrying that habit into online gambling produced this site. Most writing about casinos discusses catalogues and promotions, yet players judge an operator by whether the money moves. So the scope here is deliberately narrow: measure how long funds take to travel, and describe the places where the journey stops.

How the log is compiled

Two timestamps per entry. The first is when a withdrawal request left the account; the second is when the amount appeared on the receiving side. Intermediate status changes are recorded wherever the cashier exposes them, because those are what reveal which leg consumed the time — approval, dispatch or arrival.

Figures are published as medians, never averages. A single item that slipped into a weekend lifts an average until it no longer describes anyone experience. A median answers the question people actually ask: what happens if I press the button now. Where an operator publishes a stated window, it is labelled as a stated window and kept separate from measured data.

Four values recorded for every channel

• Length of the approval leg, split between weekdays and weekends.
• Real arrival time in forint, distinguishing the instant payment rail from batch clearing on banking days.
• Actual deduction: not the advertised fee but the gap between the amount sent and the amount credited, exchange spread included.
• Reason for rejection, when there was one: name mismatch, return-path rule, missing document, wrong network.

Editorial limits

No licence number is printed here unless it can be traced in the regulator public register. No invented player testimonials appear, with or without names and towns; recurring experiences are presented as a typology instead. And nothing on this site predicts winnings — outcomes are not plannable, whereas cashier behaviour is, and that is the subject.

A quieter fourth rule sits behind those: a measurement that cannot be repeated does not enter the log. One anecdote never becomes a median.

What this site cannot do

Requests arrive asking me to release a stuck withdrawal. That is impossible from here. This is not the operator, it holds no balances and has no access to any player account. What it can offer is sequence: what to gather, whom to contact, and when escalation becomes reasonable — set out under stuck payouts and complaints.

The same boundary applies to harm. When stake size or time spent has become a problem, the answer is a limit rather than a log: the options are summarised on the responsible gambling and self-exclusion pages.

Corrections and updates

Numbers that no longer hold are worth reporting. A date, a channel and the two timestamps are enough to tell whether an isolated case or a shifted median is in front of us. Editorial principles and contact details sit on the about page, and the funding model is disclosed in full under affiliate disclosure.

Maintenance is simple. If a channel median moves persistently, the table changes and the date of the change is noted in that section. Anything that cannot be re-measured is removed. The starting point for all of it is the payment methods index.