Skip to content
WallBettingRead the market
Read the market

Changed odds: compare the offered selection with the accepted ticket

The price visible while browsing is not necessarily the price recorded when a wager is accepted.

4 min read
01

Browsing and acceptance are different price moments

The price visible while browsing is not necessarily the price recorded when a wager is accepted. In Zora, a market can update between opening the event, adding a selection and confirming the slip. Treat those as separate moments. The transaction record, rather than an earlier screenshot, shows the price associated with an accepted ticket.

The event menu, the unfinished slip and the account ticket can reflect separate stages. A price may move before submission, during processing or before a requested confirmation. Do not treat a highlighted earlier selection as a receipt. Read the final summary and any message that asks you to accept changed terms. The selected line can move as well as the price, especially in totals and handicaps, so preserve both. This review does not claim a universal setting or fixed processing delay for Zora. The important boundary is whether the account actually records the wager and which terms that accepted record contains.

02

Recalculate the same stake with both quoted prices

An invented example uses a €10 stake. At 2.10 the potential gross return is €21; at 1.95 it is €19.50. That difference matters even though the team and market name have not changed. A displayed return can also change because the stake, line or selection changed, so compare all fields before attributing the difference only to price movement.

For the invented ten-unit example, the net profit of an ordinary win would be eleven units at 2.10 and nine and a half at 1.95. That distinction follows after subtracting the same original stake from each gross amount. If the stake changes too, isolate the inputs before comparing totals. A lower displayed potential return might reflect fewer units committed, a different price, a removed leg or a changed product. Recalculate from the accepted fields rather than attributing every change to unfavourable odds movement. The exercise explains arithmetic and does not establish that either invented price was offered or should have been accepted for a real event.

Whole and half total lines shown in the same football market
Whole and half total lines shown in the same football marketPublic Zora interface · 9 November 2026 · English version.An interface illustration, not a live price or an account test.
03

Read any change-acceptance control precisely

If the interface presents a setting or prompt about accepting changed odds, read its precise scope. It might distinguish certain changes, require confirmation or apply to the current slip. Do not assume a saved preference on one device has the same effect on another. When no clear confirmation appears, inspect the account history before submitting a replacement wager.

If a preference concerns automatic acceptance of certain changes, read exactly which changes it covers and whether it applies to the current slip. Do not infer the behaviour from a short icon or assume that one device's remembered choice controls another session. When a prompt appears, compare the new price and line with the selection you intended. You can decide not to submit if the changed offer no longer matches that intention. Repeated tapping is not a substitute for understanding the prompt. If no clear confirmation arrives, inspect history first so a replacement request does not accidentally become a second separate wager.

04

Keep the final accepted fields together

For a useful record, retain the final selection summary, stake, accepted odds, timestamp and status. If support needs to investigate, describe the sequence and the specific field that differs. An unaccepted betslip and an accepted ticket are not interchangeable evidence, and a more favourable earlier price does not establish what was actually contracted.

For a query, distinguish the earlier observed quote from the accepted ticket's value and record the approximate sequence. Include the event, market, line, stake, reference and status. A screenshot may document what was displayed at a moment, but it does not by itself prove the terms of a later accepted transaction. Ask which price was accepted and whether a change-confirmation step was recorded. Avoid replacing the original description with today's menu, where the price or even the available line may be different. The useful evidence stays tied to the single request whose acceptance or return you want explained.