Contract rules
    Sports event confusion
    Trust and escalation

    What Happens if the Player Doesn’t Play on Prediction Markets?

    This is the fast guide to voids, injuries, scratches, postponements, and combo-leg chaos. The ugly truth is that prediction markets settle on the listed rule, not on what feels fair in the moment.

    Quick answer

    Before assuming a void, check whether the contract treated this as a scratch, an in-game injury, or a cancellation — those three paths can resolve differently. On Kalshi, Robinhood, and Coinbase, the resolution criteria are spelled out in each contract's published rule text — read that section before judging the outcome.

    Fairness and rule consistency are not the same thing.
    Same event story does not guarantee the same settlement path.
    A brutal rule is different from a broken one.

    Pick your scenario

    Start with the event story you are staring at, then check the written rule before deciding whether this is normal, ambiguous, or worth escalating.

    Fast answer table

    The user expectation is usually cleaner than the actual rule. This table makes the split obvious before you call support or assume fraud.

    Never played

    Depends on contract

    What users expect: It should void automatically.

    What may happen: Sometimes it voids, sometimes it settles normally, and sometimes the answer depends on the exact participation trigger.

    What decides it: Whether the contract defines participation, appearance, minutes, starts, or official stats as the trigger.

    Escalate when: Escalate when support cannot point to the published rule language that governed the no-show case.

    Injured mid-event

    Usually normal

    What users expect: It should void because the player did not finish.

    What may happen: A mid-event injury often settles normally if the contract only required an official appearance or stat line to count.

    What decides it: Whether the rule cares about starting, recording stats, completing the event, or hitting a threshold after the start.

    Escalate when: Escalate when the platform applied a threshold that is missing or contradictory in the published terms.

    Postponed

    Depends on contract

    What users expect: It either voids right away or waits forever.

    What may happen: Many contracts publish a reschedule window or cutoff, so a postponement can remain live, settle later, or void after the stated deadline.

    What decides it: The postponement clause, reschedule window, and official event-time cutoff in the contract terms.

    Escalate when: Escalate when the platform resolves outside its own published reschedule window or cannot explain the new cutoff.

    Canceled

    Escalate if mismatch

    What users expect: Cancellation means a refund, full stop.

    What may happen: Cancellation often voids, but some contracts still depend on how the market defines cancellation versus postponement or shortened completion.

    What decides it: Whether the platform rule distinguishes cancellation, abandonment, and delayed completion as separate states.

    Escalate when: Escalate when the published cancellation rule says void and the settlement does something else.

    Combo/parlay leg issue

    Depends on contract

    What users expect: One dead leg should just disappear and the rest should stand cleanly.

    What may happen: Combo logic is often harsher and more product-specific than straight contracts, so one dead leg can recalculate odds, void the combo, or trigger a venue-specific rule path.

    What decides it: The combo-leg treatment language, especially whether the product recalculates, removes, or voids legs when one becomes non-actionable.

    Escalate when: Escalate when the combo settlement differs from the written combo rules or support cannot explain the recalculation path.

    Current scenario: Never played

    The athlete is listed, but never logs an official appearance.

    What users expect: It should void automatically.

    What may actually happen: Sometimes it voids, sometimes it settles normally, and sometimes the answer depends on the exact participation trigger.

    What decides it: Whether the contract defines participation, appearance, minutes, starts, or official stats as the trigger.

    Scenario-specific rule checks

    • Does the contract define appearance, starts, or official participation?
    • Does the rule say no appearance voids the market or treat a no-show as a losing outcome?
    • Is there a specific source of truth for player participation?

    The core product lesson

    Three concrete inputs decide how a non-participation market settles. Verify each one on the contract page before deciding the outcome is wrong:

    • The contract's trigger words (for example: starts, appearances, official participation).
    • The named official source the contract uses to confirm the event outcome.
    • The combo/parlay handling rule published for that specific market.

    That is why the right question is not does this feel wrong? It is what did the contract say would happen?

    Why this feels like a scam

    Sportsbook house rules and prediction-market contract terms are written and published separately — confusing one for the other is the most common reason a settlement feels unfair.

    Sportsbook intuition is not the same thing as contract wording.
    A player scratch, an injury, and a canceled event are not interchangeable states.
    Combo products can treat one dead leg very differently from a straight contract.
    Users often remember the story of the event, while the platform settles the literal rule text.

    Platform reality check

    Kalshi

    depends on contract

    Users must read the contract wording, source language, and event definition because exchange contracts settle on the listed terms rather than sportsbook intuition.

    exchange-style sports and event contracts • verified 2026-04-15

    Official source

    Robinhood

    depends on underlying contract

    Wrapper experiences can make settlement feel more opaque, but the underlying contract wording still decides whether a no-show, postponement, or cancellation voids.

    wrapped prediction market access • verified 2026-04-15

    Official source

    Coinbase

    depends on underlying contract

    Surface-level payout and balance views can confuse users, but official terms still govern whether the event became non-actionable or settled normally.

    wrapped event contract access • verified 2026-04-15

    Official source

    Normal, ambiguous, or broken?

    This is the core trust split. Not everything painful is broken, but not every ugly settlement should be waved away either.

    Normal but unintuitive

    Confirm the player started or recorded official participation, and confirm the contract only required that threshold.
    Confirm the rule published a postponement window, and confirm the market stayed live inside that window.
    Confirm the settlement still matches the contract's listed resolution criteria, even when those criteria differ from typical sportsbook house rules.

    Legitimate depends-on-contract zone

    Re-read the contract's trigger words (starts, appearances, minutes, or official participation) before judging the settlement.
    Check whether the contract distinguishes postponement, cancellation, and shortened completion as separate resolution paths.
    Check whether the combo product publishes a separate dead-leg rule that differs from the straight market version.

    Actual support or escalation case

    The published rule says void, but the market settled another way.
    The platform applied a participation threshold that does not appear in the official rule text.
    Support cannot point to the exact clause that governed the outcome.
    The published settlement source conflicts with the outcome the platform used.

    Contract wording checklist

    Before you call the settlement fraudulent, verify the trigger language that actually governed the market.

    Did the rule mention starts, appearances, minutes, innings, or official participation?

    Did the rule define how postponement, cancellation, or abandonment works?

    Did the rule specify the source of truth for whether the player officially participated?

    Did the combo product publish separate dead-leg handling from straight markets?

    Pre-trade checklist

    If non-participation risk matters to you, check these before clicking buy instead of after the outcome feels brutal.

    Check whether the rule mentions starts, appearances, minutes, attempts, or official participation.

    Check whether combo logic differs from the straight market version of the same idea.

    Check whether postponement triggers a delayed settlement window or a void.

    Check which official source decides participation and final event status.

    Assume your fairness instinct is weaker than the written rule until proven otherwise.

    FAQ

    The goal is not to make you love the rule. The goal is to help you tell the difference between a rule you hate and a real support-worthy mismatch.

    If this page solved the settlement panic but opened a new question, use the next guide that matches the confusion you actually have.