One event, one product contract
DraftKings' current market rules define a same-game parlay as legs from the same event and describe how void or push legs can reduce and reprice the product. bet365's related-contingency explanation illustrates why related selections can be rejected as an ordinary multiple but permitted in a separately priced builder.
Those are operator examples. Preserve the actual product label and rule edition rather than assuming every same-match product behaves identically.
Minimum contract
| Field | Question |
|---|---|
| Event and period | Regulation time, half, extra time, or another scope? |
| Leg definition | Exact result, total, player event, line and data source? |
| Participation | Must the player start, appear, or reach a minutes threshold? |
| Dependence | Which legs share score state, player time or team strength? |
| Void or push | Is a leg removed, repriced, or does the full product void? |
| Corrections | Which result or statistics feed is final? |
| Price | What combined price was accepted by the product? |
Do not multiply standalone prices
If a team win makes a selected player goal more or less likely, the legs are not independent. OpenStax's independence condition is therefore not met.
For a quoted illustrative same-game price of 4.50 and a GBP 10 stake:
Gross return if every required live leg wins = 10 * 4.50 = GBP 45
Net profit = 45 - 10 = GBP 35
This calculation reproduces the quoted payoff. It does not validate the price or the joint probability.
Player and event settlement
Player legs can depend on lineups, substitutions, positions and a named data provider. Betfair's current football rules are one operator example covering listed player-stat definitions and participation. Another product may use different conditions.
Reconciliation checklist
- Archive the accepted combined price and complete leg list.
- Record confirmed lineups and actual participation where relevant.
- Reconcile every event against the named result source.
- Identify void or push legs and reproduce any revised price.
- Keep product settlement separate from a model's joint probability.
- Compare the final return with the accepted receipt.
Next step
Use Correlated Parlay for the next part of this topic.
Test a void or push before relying on the display
Create a reconciliation case before using a same-game product in analysis. Record the original quoted price, then choose one leg and apply the product's documented non-participant, void or push state. Verify whether the whole product voids, the leg is removed and the remainder repriced, or another defined rule applies.
| Saved field | Why it matters |
|---|---|
| Original product ID and price | Identifies the accepted contract |
| Original and final leg list | Shows what changed |
| Participation and event evidence | Supports the void decision |
| Revised price and return | Allows cash reconciliation |
| Rule URL and access date | Preserves the settlement basis |
Do not infer the revised price by dividing out a standalone price. A same-game product can use a joint pricing model, so the remaining combination may not equal any simple arithmetic reconstruction. Treat an operator's revised receipt as a product result and evaluate the probability model separately.
Continue learning
- Next guide: When to Cash Out an Accumulator
- Related guide: Why Accumulators Lose
Assumptions and limitations
The price and stake are illustrative. Product availability, eligible combinations, pricing, void treatment and data providers vary by operator, jurisdiction, event and date.
GambleAware
GamCare
Gambling Therapy
GAMSTOP