Every report on this desk starts from a specific claim, quoted from wherever a casino platform actually made it — a homepage banner, a terms page, a support article. We don’t paraphrase the claim into something easier to argue with. If a platform says “instant e-wallet withdrawals,” that’s the exact phrase the report is checked against.
The four stages we check
A payment claim almost always compresses several separate steps into one word. We check them separately, because a platform can be genuinely fast at one and slow at another:
- Identity verification. Whether the documentation required is disclosed upfront or only surfaces after a withdrawal is requested, and whether the review is automated or manual.
- Internal review. A platform’s own risk and fraud checks, which run regardless of payment method and can add time that has nothing to do with the payment rail itself.
- Processor batching. Many payment processors run withdrawals on a fixed schedule (once or twice a day) rather than continuously — a real constraint that adds delay even when every other stage is fast.
- Rail settlement. How long the payment method itself takes to actually move money once a processor releases it — the part most claims are technically describing, and the smallest part of the real wait in most cases.
What we won’t do
We don’t publish a specific payout-time figure for a specific operator unless we can point to where that figure comes from — a platform’s own published terms, or a documented pattern across multiple independent reports. We don’t run star ratings or numeric scores; a number implies a precision we can’t actually verify for every reader’s situation, since verification load and payment method both change the real answer. We don’t accept payment for a favourable claim about payout speed, and we don’t let commission arrangements change what a report says a platform’s terms actually require — see how this desk is funded.
When we revisit a report
Payment processing arrangements change without much notice — a platform can switch processors, tighten verification requirements, or adjust a wagering term without publishing a changelog. Reports on this desk carry a visible “Last updated” date, and we revisit a report when we have a specific reason to believe the underlying terms have changed, not on a fixed schedule that would let a stale figure sit unflagged.
How we correct a report
How do you correct a mistake?
If a report contains a factual error — a wrong figure, an outdated term, a misread policy — we fix it as soon as it’s confirmed and note the correction date at the top of the piece. We don’t quietly edit a published claim without a visible trail; a substantive correction updates the “Last updated” date shown on the report itself.
What counts as a correction versus an update?
A correction fixes something that was wrong when published — a misquoted term, a factual error. An update reflects something that changed after publication — a platform revised its processing window, for instance. Both get the same visible “Last updated” treatment; we don’t distinguish them differently for a reader, because either way the current version is what matters.
How do I flag something?
Email [email protected] with the report link and what looks wrong, ideally with a link to the source you’re checking it against. We read every message that comes in through that address.