Product comparison
| Product | Component 1 | Component 2 | Example win |
|---|---|---|---|
| Scorecast | Named first goalscorer | Exact correct score | Player A first, final score 2-1 |
| Wincast | Named first goalscorer | Match result | Player A first, home win |
A scorecast is narrower because one exact score must occur. A wincast accepts every qualifying score that produces the selected match result, subject to the same goalscorer rule.
Score-by-score settlement
For “Player A first and 2-1” scorecast:
| First eligible scorer | Final score | Result |
|---|---|---|
| Player A | 2-1 | Win |
| Player A | 3-1 | Loss |
| Player B | 2-1 | Loss |
| No qualifying scorer | 0-0 | Follow no-goalscorer/fallback rule |
Both components must match unless the product defines a fallback. Betfair's current football rules include scorecast and wincast definitions plus product-specific fallback settlement.
Participation and own goals
The current Betfair example ignores own goals for first-goalscorer settlement and defines what happens when a selected player does not participate or enters after the first goal. bet365's current scorecast rules provide a separate operator example covering non-participants, own goals, and abandoned matches.
Do not transfer one operator's fallback to another. Record player participation, entry time, first eligible scorer, final score, and the accepted rule.
Return examples
For an illustrative GBP 4 scorecast at decimal odds 26.00:
Gross return = 4 * 26 = 104
Net profit = 104 - 4 = 100
For an illustrative GBP 4 wincast at decimal odds 9.00:
Gross return = 4 * 9 = 36
Net profit = 36 - 4 = 32
The price difference reflects different payoffs but does not establish which is better value.
Estimate the joint event
P(Player A first AND score 2-1) is not automatically P(Player A first) multiplied by P(2-1). The events overlap: if Player A scores first, the score path and remaining outcomes change. OpenStax explains that multiplication of marginal probabilities requires independence.
Use a direct joint model or sum compatible event paths. Expected value then weights the complete win, loss, void, dead-heat, and fallback payoffs using the method described by OpenStax.
Verification checklist
- Identify scorecast or wincast.
- Copy the exact scorer and score or result component.
- Confirm participation, own-goal, no-goalscorer, and dead-heat rules.
- Confirm fallback settlement for non-participants and abandoned matches.
- Estimate the joint event directly.
- Preserve the accepted product version, price, and stake.
Build a fallback payoff table
Before calculating expected value, list net return for the normal win, normal loss, non-participant, player entering after the first goal, own goal before an eligible scorer, 0-0, abandoned match, and dead-heat states. Apply the exact fallback rule to each row. Do not replace a voided scorer component with the score or result component unless the accepted contract says so.
Test the implementation with deliberately awkward fixtures: selected player starts but another player scores first; selected player enters after an own goal; selected player never appears; selected player scores first but the exact score misses; and the score matches but the selected player scores second. Only the states satisfying every required component should receive the normal combined return.
Preserve the operator's original combined price. Reconstructing a scorecast by multiplying separately displayed scorer and score prices can produce a different product, margin, and dependence treatment.
Next step
Use First Goalscorer Betting for the next part of this topic.
Continue learning
- Next guide: Asian Goal Lines Explained
- Related guide: Alternative Football Betting Markets
- Definition: Scorecast
Assumptions and limitations
Prices and players are illustrative. DraftKings' soccer rules, Betfair, and bet365 are operator examples. They do not establish a universal scorecast or wincast contract.
GambleAware
GamCare
Gambling Therapy
GAMSTOP