By Nina Ellis · Fictional AI writer for The Closing Line
Rules and documentation checked October 16, 2026.
The game has finished. Your Kalshi market says closed. The payout is still missing. Those three observations can belong to the same ordinary sequence: trading closes, the outcome is determined, and settlement pays the position. A closing time alone does not tell you that every step is complete.
Kalshi's market lifecycle documentation separates a closed market awaiting determination from a determined market awaiting settlement. This guide follows that distinction for single-event prediction contracts. It is not a guide to perpetual futures or combos.
Put the event and the contract on separate timelines
Start with the question the contract actually asks. A game finishing, a statistic appearing on a scoreboard, and the specified source confirming the result are different checkpoints. The contract's terms identify the outcome criteria and the information source Kalshi uses to determine it. Market outcomes.
Then open the market's Timeline and Payout section. Kalshi documents two kinds of closure: one tied to the outcome occurring and one tied to a listed date and time. Read the explanatory text below the payout line; don't treat the largest timestamp as a complete description of the rule. Timeline and Payout.
For a sports contract, keep the exact line beside the event. A team winning, winning by more than a specified margin, and the teams exceeding a combined total are separate questions. Our NFL moneyline, spread, and total guides explain those distinctions. Here, the useful question is narrower: which checkpoint does this particular contract still need?
A hypothetical evening, from final whistle to cash
This is a synthetic timeline, not a real market, observed delay, or expected service time. All times are Eastern Daylight Time, UTC−4, on October 16, 2026. Imagine an ordinary binary contract asking whether fictional Harbor City scores more than 20.5 points in its scheduled game. Assume its full rules require the league's official final statistics.
- 8:58 p.m. — The game ends. A scoreboard shows Harbor City with 24 points. That is the event observation in this example; we have not yet checked the stipulated source.
- 9:00 p.m. — Trading closes. The hypothetical contract's close time arrives. That ends the trading window; it does not turn the scoreboard into a completed settlement.
- 9:20 p.m. — The official report appears. It lists 24 points. The relevant source is now available, but this example still has no completed payout to inspect.
- 9:35 p.m. — The outcome is determined YES. The settlement process follows. We still distinguish the result from the payment.
- 10:05 p.m. — Settlement completes. Only now does this example record the settled position and its cash payout.
The invented gaps show why a single clock is inadequate. Changing the report time changes the sequence even if the final score stays the same. A different contract might close earlier, use a different source, or specify a later determination point. Copy the method, not these times.
What “closed,” “determined,” and “settled” tell you
Closed: the trading window has ended. Kalshi's lifecycle documentation says new orders are not accepted after close. You cannot assume a plan to sell can still be carried out merely because the payout has not arrived.
Determined: the result has been set, while settlement is still pending. The same documentation describes a settlement timer and a period in which a result may be disputed.
Settled: positions have been paid out. Kalshi's API calls the completed state finalized; that technical label matters if you are comparing an app display with an API record. You do not need to learn the API to read the market page. Market lifecycle.
Kalshi says settlement timing varies with market type, source availability, and review requirements. A source being available is a checkpoint, not a payout deadline. Market settlement.
Make a small record before guessing what is delayed
Use this worksheet for the exact contract you hold:
- Contract: title, market identifier, side, and exact threshold or line.
- Rule: the measured outcome, named verification source, and any exceptional condition that applies.
- Times: event date, trading close, stated determination or expected payout time, and the timezone for each.
- Evidence: the source report's date and status, the market's displayed result, and the time you last checked them.
- Account: whether the position remains open or has a recorded settlement and cash entry.
Treat those as separate fields. Writing “game finished” under every heading hides the question you need answered. If the source report is missing, record that gap. If a later rule-defined time has not arrived, record the next checkpoint instead of inventing a delay.
Kalshi's rules summary identifies the measured value, timeline, and verification source, but it is not the complete contract. Use View full rules for the full text. The worksheet is an editorial reading aid; it does not replace those terms. Rules summary.
When a pending result needs another check
Kalshi's current FAQ says a market can remain open while official confirmation is pending. An open market therefore does not, by itself, show that the payout criteria failed. For a standard single-outcome market with no update more than roughly 12 hours after the event ends, Kalshi advises checking the rules first. If the rules appear satisfied and the market is still pending after any stated later determination time, contact Kalshi through in-app chat with the market title and relevant source details. This is support guidance, not a guaranteed settlement time. Market FAQ.
When contacting support, the worksheet makes the question concrete: “This contract names this source; the report was published at this time; the market still shows this status.” That is more useful than a screenshot of an unrelated scoreboard.
A cash payout is separate from a bank withdrawal
A settled position and a withdrawal are different records. Kalshi's bank-withdrawal guidance describes a separate transfer process, with bank arrival typically taking a few business days. Its security-hold guidance says deposit holds apply to the original deposited amount, and directs users to the account's withdrawal screen for availability. Check those screens when the cash is present but a transfer is the unresolved step. Bank withdrawals, security holds.
Carry the timeline into an automated rule
If you are evaluating automation, write the entry cutoff and intended exit separately from the expected settlement time. Commercial disclosure: The Closing Line has a commercial interest in referrals to Bot for Kalshi. Its documented builder workflow lets you review supported price/time conditions and the market, side, quantity, price limit, and exit before starting a bot. Paper mode models the workflow without sending Kalshi orders; it does not establish live fills or settlement timing.
That review helps make your instructions explicit. It does not replace Kalshi's outcome source or settlement process. Keep the next official checkpoint beside the rule, and verify the actual market and account records before treating the position as settled.
About the author
Nina Ellis is a fictional AI editorial persona created by The Closing Line. The name represents a consistent sports and event-context writing voice, not a real person, reporter, or independent financial professional. The Closing Line is responsible for this content and its corrections. Questions or corrections.