THE QUICK ANSWER
Check whether the battle actually started and how many participants remained. Closing the page is not the documented cancellation action.
01
An open lobby and a started battle have different rules
Key-Drop says a battle begins automatically when it has the required participants. Its help permits leaving before the start; after that point the battle is considered played and cannot be left.
Open the original battle and record its state. A loading page or a tab you closed does not establish that the lobby remained unstarted.
Can this be a cancellation issue?
Has not started
Inspect current participants.
Only one participant
The help describes cancellation and balance return.
Already started
The help says the battle cannot be left.
Unexpected balance
Match the action response to the original entry.
Original rule map; it does not assert the state of a live lobby.
Original explanation · not an account screenshot02
Cancellation requires only one user in the battle
The official rule allows the last remaining participant to cancel when there is only one user in the battle. It says the participation funds then return automatically to balance.
That is narrower than “any waiting battle can be cancelled.” Keep the participant count and cancellation response for the moment you tried the action. Do not infer eligibility from an earlier view of the lobby.
03
Entry can be charged before any cases open
The article says participation funds are deducted when you join, and when you create and enter a battle. A balance deduction can therefore belong to a waiting entry rather than a completed case result.
For a missing refund, compare the entry deduction with a confirmed cancellation and its return. A battle that started before the action needs a result check instead of an unstarted-lobby refund assumption.
The records around a cancelled entry
Entry
Participation funds deducted.
Lobby state
Time and number of users recorded.
Cancellation
Keep the explicit response.
Return
Match any refund to that entry and battle ID.
Use the original battle rather than a newly created copy when tracing a refund.
Original explanation · not an account screenshot| Waiting, only you remain | Check the documented cancellation option and response. |
|---|---|
| Waiting, other users remain | Do not assume the one-user cancellation condition is met. |
| Started | Use the recorded result; leaving is no longer available under the help rule. |
04
Keep the original battle ID
Key-Drop asks for the battle ID beside the Provably Fair button when reporting a battle problem. Save that ID, your entry amount, the times and the last displayed participant count.
If the response differs from the balance movement, describe that specific mismatch. An invitation to a similar battle is not the original record.
BEFORE YOU CONTINUE
Quick checklist
- Check waiting or started state on the original battle.
- Record the participant count at the attempted action.
- Match cancellation confirmation with the balance return.
- Send the battle ID beside Provably Fair to official support.
Official sources
Official operator documentation reviewed on 26 October 2026. The checks below distinguish documented rules from suggested evidence to keep.
Public documentation only. No sign-in, payment, game, withdrawal or personal account test was performed. Recordkeeping suggestions are StrikePot editorial guidance.
Need the details for a particular website?
The code directory records each partner’s code, referral method and offer status. Use the relevant partner page when your question also involves one of those details.
Partner pages may include affiliate links. A listing does not confirm a reward or account eligibility.
