Skip to content
WallBettingRead the market
Read the market

Questioning a settlement: build a record that identifies the disagreement

A useful settlement query identifies one ticket and one disputed rule or statistic.

4 min read
01

Start from one accepted ticket and one question

A useful settlement query identifies one ticket and one disputed rule or statistic. Start with the accepted Zora record rather than a recreated betslip. Include the ticket identifier, event, market, line, period, accepted price and current status. These details let support find the transaction without guessing which similar event or selection you mean.

A recreated slip may show today's price or a different line, so it is a poor substitute for the original accepted record. Open the stored ticket and copy its identifying fields exactly. For a total, include the unit and line; for a handicap, the sign and side; for a period market, the named boundary. If several legs are involved, identify which leg is disputed and which ones are already understood. This preparation narrows the investigation. It also prevents an accidental comparison between a first-half proposition and a full-match result merely because the same participants appear in both places.

02

Separate recorded facts from your proposed explanation

Then separate observation from interpretation. An observation might be that the recorded first-half score was 0–0. Your interpretation might be that a first-half total should therefore have settled differently. State both, while allowing for the possibility that the selected market had a different scope. A screenshot of the full market wording can resolve that ambiguity more effectively than a cropped return figure.

Use two short statements: what the record shows and why you believe the outcome needs explanation. For example, the accepted wording might say first-half total, while your observed statistic concerns the full match. Writing both makes that mismatch visible before a claim is sent. If the evidence genuinely matches the market, identify the exact count or rule that appears inconsistent. Do not describe an unverified interpretation as an established fact. A support response should be able to address the defined difference, whether that leads to a correction or to an explanation of a period, source or exceptional condition you had not considered.

03

Preserve a chronology without unnecessary personal data

Keep a short chronology: acceptance time, event completion or interruption, initial settlement and any later change. If the account currency or amount is part of the disagreement, show the relevant ledger entry. Redact unrelated transactions and avoid sending passwords, full payment-card details or unnecessary identity documents in a general message.

Record the approximate sequence and retain references rather than collecting unrelated account screenshots. If the ticket changed from pending to settled, note when you observed each state. If an official statistic was corrected, distinguish the earlier observation from the later one. A ledger entry matters when the question concerns the credited amount, but unrelated purchases and personal identifiers are unnecessary. Use the operator's designated private channel and follow any specific document request separately. A general settlement question does not require sending a password or payment authorisation code. Clear, limited evidence is easier to review than a large bundle with no stated connection to the ticket.

04

Request the applied rule and continue the same case

Ask a precise question: which rule and recorded result were used for this ticket? Save the response and reference number so a follow-up continues the same case. Multiple simultaneous messages with different descriptions can make the issue harder to follow. This process creates a clear audit trail; it does not assume in advance that the operator or the customer is correct.

Ask for the market rule, recorded result and calculation used, rather than only requesting a preferred outcome. If the answer is incomplete, quote the unresolved point and continue under the same reference. Multiple parallel messages can introduce conflicting descriptions and make the chronology harder to follow. Keep the final explanation with the accepted ticket so any subsequent change can be compared accurately. This guide concerns a practical record-building process, not legal advice or a promise of compensation. It helps distinguish a display delay, a misunderstood market and a possible settlement discrepancy through evidence attached to one specific transaction.