Guide · Sport
The in-play delay is there to keep the price honest
In-play betting adds a short delay between the tap and the acceptance. The delay exists so the bet is matched against a price that already includes the thing that just happened on the pitch, not the thing a courtside feed saw first.
7 min readUpdated By the Turnkeyxgaming team
Faster is not fairer
A player with a low-latency picture can bet a goal before a television viewer, and before your price, has moved. The delay is the book's attempt to stop taking that bet at the old price. Shortening it increases the chance you accept a stale price. That cost does not show up as a single complaint. It shows up as in-play margin that is worse than pre-match for no operational reason.
Cash-out during the delay needs a rule you can explain. Either the cash-out is also delayed, or it is refused while a bet is pending. Accepting a cash-out on a price you have not confirmed is the same hole. Tell the client to show 'pending' rather than a spinner that looks like a freeze.
The length of the wait belongs in the sportsbook configuration for that sport. It is not a constant you publish as a fairness slogan, and it is not a VIP perk. A shorter delay for high-value accounts is a stale price with a loyalty badge on it. Log the price at tap and the price at acceptance so trading can see how often the delay actually moved the market. If it never moves, the configuration is worth a look. If it often moves, the delay is doing the job players experience as slowness.
What the client has to show during the wait
The delay is a trading control. The interface's job is to make the pending state obvious, including for cash-out.
- The bet shows as pending from the tap until acceptance or refusal. A silent spinner reads as a frozen app.
- The price on screen is the price being considered, and it can change before acceptance. Do not promise the tapped price.
- Cash-out waits the same way, or it is refused while a bet is pending. It does not fill at an unconfirmed price.
- There is no account setting that skips the delay for VIPs, traders, or staff.
- Acceptance and refusal are both explicit. A timeout from the client is not an acceptance.
Explain the wait
- 01
Pending state
Show that the bet is waiting. Do not show a silent spinner.
- 02
Do not skip it
Do not add a VIP setting that removes the delay.
- 03
Cash-out
Apply the same delay, or refuse cash-out while a bet is pending.
Taking the delay off does not feel like a favour for long
The cost shows up as in-play margin that is worse than pre-match, not as a single ticket. A courtside picture will keep beating a television price if you accept the tap immediately. Leave the wait in place.
The goal that arrived between the tap and the answer
A player put 300 on over 2.5 goals at 1.85, in play, at 62:14 on the match clock. The delay held the bet while the price was checked. At 62:19 the trading feed suspended the market, because a goal had gone in at 62:09 and the courtside feed had it before the television picture the player was watching. The bet was refused two seconds later, and the player wrote in to say the app had taken the bet and then cancelled it.
The refusal was correct and the interface made it look like theft. A pending state from the tap, worded so the price may still move, plus a refusal that says the market changed, would have been readable. What must not happen is a refusal that arrives after the button has already animated like a confirmation. The press is a request, not an acceptance, and the screen should not pretend otherwise while the answer is still being formed.
The same window has to cover cash-out. On this brand a cash-out of 870 was accepted during the delay on another market, at a quote that predated a goal by four seconds, because the cash-out path read the last quoted price instead of the current one. That loss did not arrive as a complaint; it arrived as a market that traded badly for a week. One pending state, shared by the bet slip and the cash-out control and reading the same source, is the only version that holds.
What the log needs for every delayed bet
- The price shown at the tap and the price at the answer, so trading can see whether the wait moved anything at all.
- The market state at both moments, including any suspension, carrying the feed's timestamp rather than the server's.
- Whether the player had a cash-out open in another window or tab at the same time, which is where the expensive versions of this failure live.
- The screen state exactly: pending, accepted, refused or timed out. A client timeout is not an acceptance and must not be stored as one.
- The delay configuration version for that sport, so a later change to the number does not rewrite what was applied to this bet.
- The sentence the player was shown, because a refusal worded like a payment failure produces a different queue and a longer ticket.
FAQ
Questions operators ask
Is the delay the same length for every sport?
No. Latency and the value of a single event differ. The figure belongs in the sportsbook configuration for that sport, not in a blog post as a universal number.
Why was my in-play bet refused when the button accepted the tap?
The tap only starts the wait. During it the price can move or the market can suspend. Refusal after a pending state means the book did not take the bet at a stale price. It is not a failed payment.
Should the delay be identical for football and tennis?
No. How fast a score changes, and what one point is worth, differ by sport. Set the wait in that sport's configuration. A single number copied across the coupon is how a fast market stays unprotected.
A high-value player asks for the delay to be shortened on their account. Is that ever acceptable?
It hands one account a price the rest of the market has already left, and the cost lands in in-play margin with no line item to explain it. If the player wants faster decisions, the honest answer is a tighter price for everyone, decided by trading. An account flag that skips the wait is a stale price with a loyalty badge on it.
The bet is refused after the wait. Should the client offer the new price automatically?
No. A new price is a new bet, and accepting it on the player's behalf stakes money they did not agree to spend. Show the current price and let them tap again. Where the market is suspended, say so and disable the control, rather than leaving a button that looks live and does nothing.
Keep reading
Related pages
- Product · SportsbookSportsbookAdd pre-match, in-play, esports and virtual sport as a wallet iframe, or take the odds feed and build a betslip your traders run.Read
- Data · Football dataFootball dataFootball fixtures, prices, scores and results for a coupon you render and settle yourself. This is data, not a hosted book.Read
- Guide · ExchangeLay liabilityWhy a lay bet reserves more than the stake, when that reservation is released, and how the wallet should show it to finance.Read
- Product · Sports dataSports dataFixtures, pre-match and live odds, scores and results for operators who build their own sportsbook front end and settle bets themselves.Read
Get a written quote and sandbox access
Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.