Complaints and disputed situations
Most disagreements with an operator are not fraud. They are a bonus condition read differently by two parties, a withdrawal held while a verification check completes, or a payment that left one system and has not yet appeared in another. The order in which those situations are handled matters more than the volume of the complaint, and this page sets out that order for the Latvian market.
The escalation ladder
| Step | Who handles it | What it is for |
|---|---|---|
| 1. Support desk | Operator’s first line | Facts: status of a payment, which check is outstanding, what the term says |
| 2. Internal escalation | Operator’s complaints function | A formal, written review when the first line cannot resolve it |
| 3. Supervisory inspection | State regulator (IAUI) | Conduct measured against licence conditions |
Skipping steps is the most common mistake. A regulator asked to intervene before the operator has been given a documented chance to answer will usually send the case back down the ladder, and the weeks spent are lost. Working upward in order also generates exactly the paper trail the higher step needs.
Step one: ask a precise question
The first message should be narrow enough to be answerable. „My withdrawal is not here" invites a template. „Withdrawal requested on the 3rd, reference ending 4471, still shown as processing — which check is outstanding and what is the expected completion?" invites a fact. Ask for a ticket number and keep it; without one, the second step has nothing to attach to.
Step two: put it in writing
A formal complaint is a summary, not an argument. What happened, in date order. What was expected, quoting the operator’s own term. What was received instead. What outcome is sought. Attach the evidence rather than describing it. Emotion adds nothing at this stage and occasionally obscures the point that would otherwise carry the case.
Step three: the supervisory inspection
Latvia’s Lotteries and Gambling Supervisory Inspection issues gambling licences and supervises the operators holding them. Where an operator has acted against the conditions of its licence, this is the body with authority to examine that. Two boundaries are worth understanding before filing. The inspection supervises licensed operators — if the site in question is absent from the register of licences and instead appears on the list of blocked domains, the protective framework was never engaged in the first place. And it is a supervisor, not a collection agency: it examines conduct rather than negotiating a commercial settlement on a reader’s behalf.
Evidence that actually helps
- Dated screenshots of the cashier, the balance and the transaction list.
- Payment references from the bank or wallet side, which exist independently of the operator’s records.
- The bonus terms as they appeared at the moment of acceptance, not as they read today.
- Support transcripts in full, with ticket numbers, rather than selected quotes.
Situations that are not disputes
A first withdrawal delayed by identity verification is the licence working as designed, not misconduct — the background is under withdrawals. Bonus funds lost because the wagering condition was not completed within its term is the condition operating as published; the arithmetic is explained under wagering requirements. And an account restricted after a self-exclusion request is the register doing precisely what it exists to do, as described under self-exclusion.
Where this site stops
laimz.biz cannot intervene. We hold no money, cannot see an account, cannot compel a decision and are not a party to the contract between reader and operator. Describing the route accurately is the whole of our contribution, and it is deliberately the same route we would use ourselves.