Troubleshooting
    April 20268 min read

    Kalshi Troubleshooting Hub

    Every common Kalshi question that looks like a bug but is actually mechanics — account restrictions, payouts that change with size, winning positions paying less than $1, and commodity charts that don't match the rulebook.

    Common Issues

    10+

    Avg Resolution

    <24h

    Support

    24/7

    Read Time

    8 min

    Quick Summary

    The key takeaway from this page

    Most Kalshi issues stem from deposit delays, state restrictions, or order-matching edge cases. This page covers the top problems and their fixes.
    §2 · Status / bug credibility

    Bug, outage, or account-specific issue?

    When something looks wrong, separate platform-wide status signals from account-specific records before escalating. A display mismatch, delayed cash line, or blocked transfer needs a different evidence lane than a confirmed settlement dispute.

    Evidence lane first

    Do not collapse every weird screen into “Kalshi bug.” Check whether the signal is official, account-specific, support-confirmed, or only social chatter before deciding what to do next.

    Source/status ladder

    1

    Official in-app/web status or logged-in notices

    Trust action: Check first for incidents or account holds before assuming your individual records are wrong.

    Whether the platform is flagging an incident, maintenance window, degraded feature, account hold, or transfer notice in the product surface you actually use.

    2

    Account records

    Trust action: Reconcile these records before assuming funds are gone.

    Cash balance, portfolio value, trading history/documents, order confirmations, cashout confirmations, and settlement records show the account-specific trail.

    3

    Logged-in support channel

    Trust action: Send a concise evidence packet if official records do not match.

    Support can inspect account-specific records that public pages and screenshots cannot prove.

    4

    Social/forum reports

    Trust action: Use as signal only, never as settlement or account proof.

    Other users may reveal a pattern worth checking, but public chatter does not prove your account state, settlement, or cash ledger.

    Credible bug report packet

    Bring support records, not vibes.

    • Market, event, or ticker if visible
    • Timestamp and timezone for the issue
    • Whether it appears in the app, web, or both
    • Screenshots of cash balance, portfolio value, trading history/documents, and confirmation state
    • Exact error text or status label
    • Whether it reproduces after refresh, relogin, or switching app/web
    • Which official status, account, or support surfaces disagree

    Do not do this

    These moves make support and recovery harder.

    • Do not create a second account to bypass a restriction or display issue.
    • Do not share passwords, private keys, 2FA codes, or account recovery details.
    • Do not trust DMs claiming to be support or offering expedited recovery.
    • Do not assume social posts prove your account state.
    • Do not retry deposits or withdrawals blindly if the platform says a transfer is processing.

    Status matcher

    App glitch or display mismatch
    Account records plus app/web comparison
    Refresh, relogin, compare app against web, then check cash, portfolio value, history, and confirmation surfaces.
    Escalate when the official account records still disagree after you capture screenshots and timestamps.
    Platform-wide incident suspected
    Official in-app/web status or logged-in notices
    Look for official product notices first; use social reports only as a prompt to verify official surfaces.
    Escalate only if the incident clears but your account records still do not reconcile.
    Account review or restriction
    Logged-in notice plus support channel
    Read the restriction notice, avoid opening another account, and send support the requested identity or account context.
    Escalate if support does not respond or the restriction blocks cash access without a clear next step.
    Withdrawal or deposit processing issue
    Transfer status and support channel
    Capture the transfer status, timestamp, bank/payment surface if relevant, and whether cash is visible but transfer is blocked.
    Escalate if processing language disappears or conflicts with cash/history records.
    Cashout or settlement mismatch
    Cashout confirmation, trading history, market settlement state, and portfolio value
    Use the cashout reconciliation checklist before treating the issue as a platform bug.
    Escalate when confirmation, history, portfolio value, and cash balance still do not match.
    §1 · Why is my account restricted?

    Why is my Kalshi account restricted?

    Five common causes — what each means, typical resolution timeline, and what to do next. Kalshi is CFTC-regulated, which means you have formal recourse if support doesn't resolve it.

    ✅ Kalshi support is generally responsive — most issues resolve via email.

    ✅ CFTC regulation means you have formal recourse if support fails.

    ⚠️ Do not create a second account to bypass a restriction — it makes things worse.

    ⚠️ Kalshi cannot legally discuss the specific reason for a risk review — this is normal.

    §2 · Not a bug — order-book mechanics

    Why does my Kalshi payout change when I size up?

    Bigger size can mean worse execution, not broken math. On an order-book market, your effective payout can deteriorate when a larger order stops filling at the best visible quote and starts consuming worse-priced liquidity.

    The thesis: when you increase order size on a prediction market, you are often no longer buying only the best visible price. Bigger orders can walk the book, widen the blended average entry, and change the all-in economics even if the headline market number looks similar.

    You are hitting multiple price levels.
    The visible quote is not infinite size.
    Fees and spread affect the all-in cost.
    Market orders hide the path your order takes.

    Order-book walkthrough

    A simplified YES ask stack. A 120-contract market order walks all three levels and settles at a blended average — not 41¢.

    1

    20 contracts @ 41¢

    Best level — first to fill

    2

    40 contracts @ 43¢

    Second level — fills next

    3

    60 contracts @ 46¢

    Third level — the tail of a bigger order

    Blended fill: (20×41 + 40×43 + 60×46) / 120 = 44.17¢ average — not the 41¢ top-of-book quote you saw first.

    Four reasons the display can feel misleading

    Top-of-book is not the full-size price

    The first number on screen is only the best currently available slice. It is not a promise that your whole order can fill there.

    Fees are not the only cost

    Fees still matter, but they are only part of the story. A worse average fill can hurt more than the fee line itself.

    Market orders prioritize immediacy

    If you tell the market to fill now, the platform will keep grabbing available liquidity until the order is done. That speed can cost you price quality.

    Screenshots hide the blended fill

    A screenshot often shows the headline quote or a single visible level, not the weighted-average price your actual order received across multiple levels.

    What to do next time

    • Inspect depth before you size up.
    • Use limit orders when you want price control.
    • Break larger size into smaller entries if the book looks thin.
    • Compare total cost and blended entry, not just the headline odds.
    §3 · Cashout / balance reconciliation

    Kalshi says my cashout was paid, but my cash balance is missing — what should I check?

    A cashout or settlement can touch several different surfaces: portfolio value, cash balance, trading history, settlement or payout records, and withdrawal eligibility. Reconcile the state before assuming funds are missing.

    30-second answer

    Do not treat one “paid,” “cashed out,” or “settled” label as the whole ledger. Compare cash balance, total portfolio value, trading history, market settlement state, and withdrawal availability before escalating.

    If the records still do not reconcile, use Kalshi's logged-in support messenger with a detailed issue description and screenshots of each surface.

    Receipt checklist

    1

    Capture the market or event identifier before contacting support.

    Support needs to know which market, settlement, or trade record to inspect.

    Kalshi Help Center — Contact Kalshi Support
    Kalshi API Documentation — Portfolio API
    2

    Compare cash balance against total portfolio value.

    Cash and portfolio value are different account surfaces; portfolio value can include open positions.

    Kalshi Help Center — Cash
    Kalshi Help Center — Portfolio
    3

    Check trading history or documents for the related trade record.

    The history/document surface can provide the receipt trail when the portfolio display is unclear.

    Kalshi Help Center — Trading History
    Kalshi API Documentation — Portfolio API
    4

    Check the market page and settlement/payout state before assuming cash is missing.

    Settlement and payout state can differ from open-position valuation or withdrawal availability.

    Kalshi Help Center — Market FAQs
    Kalshi API Documentation — Portfolio API
    5

    If the records still do not reconcile, use logged-in Kalshi support with screenshots and a concise timeline.

    Kalshi directs users to the support messenger while logged in and asks for a detailed issue description.

    Kalshi Help Center — Contact Kalshi Support

    State matcher

    The market or confirmation says paid, but cash balance does not show the expected amount.
    Settlement/cash/history records need reconciliation.
    Compare cash balance, portfolio value, trading history, and settlement/payout records before escalating.
    Cash is visible, but withdrawal is not available or does not complete.
    Withdrawal eligibility or transfer processing issue, not necessarily missing funds.
    Move to Kalshi deposit/withdrawal help and contact logged-in support if the transfer state is unclear.
    The number changed after cashing out or attempting to sell, but no clear cash line appears.
    Open-position valuation, sell/cashout execution, or order-book liquidity may be involved.
    Route the reader to payout-drop/cashout mechanics if the issue is price received, not missing balance.
    History appears blank, zero, or inconsistent with the visible confirmation.
    Evidence packet needed for support review.
    Collect screenshots of market, portfolio cash, history/documents, confirmation state, timestamp, and device/app/web surface.

    What this is not

    • This page does not claim Kalshi lost or stole funds.
    • This page does not promise a fixed reconciliation timeline.
    • This page does not replace Kalshi support or legal advice.
    • This page does not explain combo cashout math; link that case to /kalshi-cashout-math-multi-leg-parlay.
    • This page does not explain lower-than-expected exit value; link that case to /why-did-my-prediction-market-payout-drop.

    Support evidence packet

    • Market or event name/ticker if visible
    • Cashout, order, trade, or settlement confirmation if visible
    • Portfolio cash balance screenshot
    • Trading history or document screenshot
    • Market page settlement/payout state screenshot
    • Timestamp and timezone
    • Whether the issue appears on app, web, or both
    §4 · Scalar / fair-market-price settlement

    Why did my winning Kalshi position pay less than $1?

    Kalshi settles some non-participation cases using the last traded fair market price — not $1, not $0, not a void. Here's why, how, and what to check before you trade.

    At a glance

    • Normal resolution: $1 (YES wins) or $0 (NO wins).
    • Scalar resolution: any value between $0.01 and $0.99 (indicated by a blue arrow next to the position in-app).
    • Trigger: DNP, ejection, postponement, or rule-defined "no official stat line" after listing.
    • Source: help.kalshi.com/en/articles/13823820-combos

    The resolution paths Kalshi uses

    Every Kalshi contract settles through one of these paths. Which path applies is always defined in the specific contract's Rules tab — do not infer from the market title.

    YES settles at $1.00
    $1.00
    Official stat line met under contract rule
    NO settles ($1.00 for NO, $0.00 for YES)
    $0.00 / $1.00
    Stat line missed, or DNP when contract rule specifies DNP = NO
    Scalar — last traded fair market price
    $0.01 – $0.99
    Non-participation when contract rule specifies scalar path (blue arrow indicator in-app)
    50/50 non-standard payout
    $0.50
    Specific contract-defined edge cases

    Worked case — DNP triggers scalar settlement

    Illustrative calculation — no named individual, no real dollar-amount attribution. Check each contract's Rules tab for the actual resolution path.

    Contract

    Player prop (generic)

    Entry

    YES @ $0.45, 100 contracts

    Event

    Player ruled OUT pre-game

    Settlement

    Last traded fair price before ruling — illustrative: $0.42

    Calculation

    100 contracts × $0.42 = $42.00 payout — entry cost was $45.00, so net −$3.00.

    Contract Rules tab specified FMV path, not $0/$1.

    Pre-trade checklist

    • Open the contract's Rules tab on kalshi.com before trading (not the wrapper's order ticket).
    • Look for the 'scalar' or 'fair market price' resolution language — it is explicit when present.
    • A blue arrow next to the position in-app indicates scalar settlement is in play.
    • If the contract is a player-prop or participation-dependent market, assume a non-participation path exists until the Rules tab tells you otherwise.
    • If trading through a wrapper (Webull, Robinhood, etc.), the order ticket may not surface the scalar rule — the authoritative source is kalshi.com.
    §5 · Commodity rollover mechanics

    Kalshi oil contracts: why the chart can show a different month than the resolution

    Kalshi commodity markets resolve against a specific contract month named in the published rulebook. The forecast graph and price graph on the market page are visualizations of trader sentiment — not the resolution source. On rollover day, those two can point at different underlying futures.

    At a glance

    • The rulebook is authoritative. It names the contract month, the resolution source, and the last trading day.
    • The forecast graph is not a tracker. Per help.kalshi.com, it is a visualization of trader sentiment.
    • Rollover can advance the contract month before the chart's window does. The rulebook wins, not the chart.
    • Always open the rulebook from the market detail page before trading a commodity contract.

    What Kalshi says about its charts

    Kalshi's own help center explicitly describes both the forecast graph and the price graph as visualizations of trader sentiment — not real-time trackers of the underlying contract that resolves the market.

    Forecast graph

    help.kalshi.com/en/articles/13823829-forecast-graph

    “When analyzing market predictions, it's important to understand that a forecast graph is not a real-time data tracker. Instead, it serves as an insightful visualization of traders' current expectations regarding future market conditions. The forecast (based on trades made) represents an accumulation of information, reflecting traders' insights and where they believe the market will most likely expire at.”

    Price graph

    help.kalshi.com/en/articles/13823830-price-graph

    “Price graphs serve as visual tools that encapsulate the collective forecasts of traders. They don't offer absolute probabilities. Instead, they represent the consensus beliefs of market participants about how likely they think an event is to occur.”

    Rollover day: chart shows old month, rulebook points to new month

    Setup: You open a Kalshi oil market on the day futures contracts roll. The forecast graph shows historical price action tied to the expiring front-month contract.

    Entry: You place a YES limit looking at the chart's current trajectory.

    Outcome: The market resolves against the NEXT contract month per the rulebook. Your chart-based read was tracking the wrong underlying.

    Takeaway: The chart is not a resolution tracker. Open the Rules tab from the market detail page — it names the specific contract month, resolution source (e.g., ICE end-of-day top-row), and last trading day.

    Check before trading a commodity contract

    • Open the Rules tab from the market detail page on kalshi.com — the rulebook is authoritative.
    • Confirm the specific contract month named in the rulebook (e.g., "June 2026 Brent crude contract"), not just the market title.
    • Confirm the resolution source (e.g., ICE end-of-day top-row, CME settlement price) — wrappers don't always surface this.
    • Confirm the last trading day. If rollover is imminent, the chart you're looking at may already be tracking the wrong month.
    §6 · When to escalate to the CFTC

    The formal recourse lane

    Because Kalshi is CFTC-regulated, you have a formal complaint path if support doesn't resolve a material issue within a reasonable window. This is not a substitute for first working through support — it is the lane after support has failed.

    Triggers for escalation

    • Kalshi has not responded to your support request within 10 business days.
    • Funds held without explanation or a clear timeline.
    • Account closed without cause, or with a generic 'compliance reasons' answer and no way to appeal.
    • You believe you were treated materially differently from other users with the same profile.

    What to include in a CFTC complaint: your Kalshi account email, the dates/details of the issue, the support tickets you filed and their ticket IDs, screenshots of the disputed positions or restrictions, and a clear statement of what outcome you're seeking.

    What the CFTC will and won't do: The CFTC enforces regulations and investigates patterns — it does not adjudicate individual disputes or order restitution in a single support-style ticket. But a pattern of unresolved complaints at a regulated entity is exactly what triggers real oversight action.

    §8 · FAQ

    Frequently asked

    Continue exploring