Bet delay
Bet Delay
Delay Policy
We always seek to keep the bet delay at the minimum possible value to maximize user experience and player engagement. At the same time, we ensure the delay is sufficient to protect our B2B clients from after-goal betting and other integrity risks. This balance is continuously monitored and adjusted based on real-time trading conditions and risk assessments.
Our system allows highly flexible bet delay configuration to optimize both risk management and user experience.
- Per match: Set delays for individual matches.
- Per market: Apply different delays to specific markets within a match.
- Per user group: Tailor delays for different user segments.
This enables tailored delay policies based on the risk profile, popularity, trading conditions of each event or market, or characteristics of user groups. For example, high-profile matches or volatile markets may have longer delays, while low-risk scenarios can have minimal delay.
Combined Delays: How They Work
Some clients prefer to maintain control over bet delays on their own side, applying custom delays according to their risk management policies or operational needs. This setup is fully supported by our platform. While we recommend delegating delay management to DataBet for optimal security and guaranteed results, you are free to implement your own delay logic on your side if desired.
In practice, the delay configured by DataBet is typically shorter than the delays applied by most clients. Our system is designed to minimize latency, leveraging official data sources and real-time trading conditions to keep delays as short as possible. Some of the clients, however, choose to add additional delay on their side for more flexibility over their configuration on their side.
A common misconception is that delays from both the client and DataBet are simply added together (e.g., 6s on the client side + 9s from DataBet = 15s total). This is not correct.
Do delays stack?
No, delays do not simply stack. The system uses the original bet creation timestamp from the client to calculate only the remaining delay required on DataBet's side. If the client's delay is equal to or greater than DataBet's configured delay, no additional delay is applied by DataBet. This ensures the total delay is never more than necessary and always meets the required minimum for security and integrity.
Example Timing Scenarios:
| Client Delay Applied | DataBet Delay Configured | DataBet Delay Applied |
|---|---|---|
| 0s | 9s | 9s |
| 6s | 9s | 3s |
| 9s | 9s | 0s |
| 12s | 9s | 0s |
Why Our Delay Is Essential
Clients typically do not have full visibility into real-time trading conditions or data feed health. Our delay mechanism provides a critical safeguard in scenarios like:
- Data Feed Instability: Even during top-tier matches, data feeds can drop or lag unexpectedly. When that happens, our traders may switch to manual handling or immediately suspend the event. To protect market integrity, our system can dynamically increase the delay.
- After-Goal Bets: If the total delay is misconfigured, clients risk accepting "After-goal" bets, when a user places a bet during or right after a major event (e.g., a goal, red card, penalty), but before the market is updated.
Our system ensures that this buffer exists — even when the client has applied a dynamic or static delay on their end — and, thanks to timestamp-based compensation, the user experience is not negatively impacted.