The standard case: instant
When the event is resolved in AUTO mode (95% of cases, especially for sports), the delay between the end of the event and your winnings arriving is typically less than 60 seconds.
Here's the timing:
- T+0: the event ends (final whistle, polls close, etc.).
- T+10s to T+40s: the external API refreshes its data and publishes the result.
- T+40s to T+60s: our system computes the resolution and releases the escrow.
- T+60s: you receive a push notification + your winnings appear in your wallet.
It's one of our strongest commitments: your winnings are yours immediately, with no artificial "verification" or "processing" delay.
Events that take longer
For events in SEMI-AUTO or MANUAL mode, the timeframe is longer:
SEMI-AUTO mode: 5 minutes to 4 hours. The time it takes the admin to validate the suggestion.
MANUAL mode: 24 hours to 7 days. The time it takes the admin to find, verify and enter the result with evidence.
You're always informed when an event takes longer than expected. Push notification: "The event [X] requires manual validation. Resolution expected within 48h. You'll be notified as soon as it's done."
Your KTK stays in escrow during that time. You can't touch it.
The dispute case
If someone (you or your opponent) disputes the resolution within 48 hours, the event moves to DISPUTED status. The timeframe stretches:
- 2 to 7 days for an admin to investigate the case.
- Final decision: the initial resolution is upheld or a new resolution is issued.
- You're notified at every step (investigation started, under review, decision issued).
While the dispute is ongoing, your KTK remains in escrow. You'll be credited or not depending on the final decision. Dispute processing time.
How to check the status
In the app, in My bets:
- Bet pending: clock icon.
- Bet being resolved: orange magnifier icon.
- Bet resolved (won): green trophy icon + amount won displayed.
- Bet resolved (lost): red X icon.
- Bet in dispute: yellow warning icon.
You can always tap the bet to see the full details, including the resolution source and the exact timestamp.