Single Bet or Accumulator: How Betting Coupons Differ Inside the System
Learn how singles and accumulators differ in coupon structure, combined odds, wins, losses, voids, and settlement inside a betting system.
A single bet and an accumulator look almost identical to the user: they select outcomes, enter a stake, and confirm the bet. Inside the betting system, however, they follow two different settlement scenarios.
A single contains one outcome, so its result depends on one event. An accumulator, also known as a parlay, combines several outcomes in one coupon. Their odds are multiplied, but every included selection must win for the coupon to win.
The difference affects more than the potential payout. The system must handle the coupon structure, odds changes, voids, cancelled matches, and the final bet status differently.
What Is a Single Bet?
A single is a coupon with one selected outcome.
For example:
- match: Team A vs Team B;
- outcome: Team A to win;
- odds: 1.80;
- stake: 100;
- potential payout: 180.
The calculation uses this formula:
Payout = stake x odds
100 x 1.80 = 180If the outcome wins, the user receives 180. This amount consists of the original stake of 100 and a profit of 80.
If the outcome loses, the entire single receives a losing status. If the outcome is settled as a void, the stake is normally returned to the user.
What Is an Accumulator?
An accumulator is one coupon containing several outcomes.
For example:
| Event | Selected outcome | Odds |
|---|---|---|
| Match 1 | First team to win | 1.80 |
| Match 2 | Over total | 2.10 |
| Match 3 | Both teams to score | 1.65 |
The combined odds are calculated by multiplication:
1.80 x 2.10 x 1.65 = 6.237With a stake of 100, the potential payout is:
100 x 6.237 = 623.70The defining condition of an accumulator is that every included selection must win. If even one outcome loses, the entire coupon loses.
The exact rules for rounding combined odds and payouts are determined by the betting system configuration.
Main Differences Between a Single and an Accumulator
| Parameter | Single | Accumulator |
|---|---|---|
| Number of outcomes | One | Two or more |
| Combined odds | Odds of one outcome | Product of all outcome odds |
| Winning condition | The selected outcome must win | Every selected outcome must win |
| Effect of a loss | The bet loses | One loss closes the entire coupon as lost |
| Void | The stake is normally returned | The outcome is normally settled at odds of 1.00 |
| Coupon settlement | After one event is settled | After all included events are settled |
How Coupons Are Stored Inside the System
Logically, every coupon consists of a general section and a list of selected outcomes.
The general section may store:
- coupon ID;
- user ID;
- coupon type;
- stake;
- currency;
- combined odds;
- potential payout;
- creation time;
- current status.
The selections inside the coupon are stored separately:
- match ID;
- unique outcome code;
- odds at the time of acceptance;
- outcome status;
- settlement result.
A single contains one selection in this list. An accumulator contains several.
Coupon
|-- total stake
|-- combined odds
|-- overall status
`-- selected outcomes
|-- outcome 1
|-- outcome 2
`-- outcome 3This structure allows the system to settle every outcome separately and then determine the overall coupon result.
What the System Checks Before Accepting a Bet
Between selecting an outcome and confirming the coupon, the odds may change or become temporarily blocked.
The backend should therefore verify again:
- that the match still exists;
- that the selected outcome remains available;
- that the blocked flag is not active;
- whether the odds have changed;
- whether the stake is within the permitted limits;
- whether the user has sufficient balance;
- whether the selected outcomes may be combined in one accumulator.
A bet must not be accepted using only the data stored in the user’s browser. Current odds and outcome availability must be confirmed by the server.
What Happens When One Outcome Is Voided
For a single, a void normally means that the stake is returned.
In an accumulator, the voided selection usually receives settlement odds of 1.00 and stops affecting the combined odds.
For example:
1.80 x 2.10 x 1.65 = 6.237If the second selection is voided:
1.80 x 1.00 x 1.65 = 2.97The accumulator remains active, but its potential payout decreases. The exact behavior depends on the rules of the specific betting system.
When an Accumulator Is Settled
An accumulator cannot be finally settled after only the first match has ended.
While some events remain unfinished, the coupon stays active:
- the first selection has won;
- the second is waiting for a result;
- the third has not started yet;
- the overall coupon status is pending settlement.
If one selection loses, the system may immediately mark the entire accumulator as lost. If every selection wins or is voided, the final payout is calculated.
How the Sports Line Is Connected to a Coupon
The Sports Odds API provides matches, markets, odds, and technical outcome identifiers. The sports line itself does not accept bets or calculate winnings.
When an odd is selected, the system must store not only its display name but also its unique identifier. SportAPI uses oc_pointer for this purpose.
The sequence works as follows:
- Sport Line API returns the match and its odds.
- The user selects an available outcome.
- The
oc_pointeris added to the coupon. - The backend checks the odds and blocked state again.
- The coupon is submitted to the bet placement system.
- After the events finish, Coupon API settles every outcome.
- The final coupon status is created from those results.
Singles and accumulators can be submitted through the same API. They differ in the number of selected outcomes and in the logic used to determine the final result.
Particularly Dangerous Implementation Errors
When developing the system, do not:
- calculate the payout only on the frontend;
- trust odds received from the browser;
- find an outcome by its name instead of its technical ID;
- allow the user to select a blocked odd;
- mark an accumulator as won before every outcome is settled;
- treat a void as a loss;
- credit a payout again when a webhook is repeated;
- overwrite accepted odds with values from the current sports line.
An accepted coupon must retain the odds confirmed by the system when the bet was placed. Later sports line updates must not rewrite coupon history.
Frequently Asked Questions
Which is better: a single or an accumulator?
An accumulator offers higher potential combined odds, but one losing selection causes the entire coupon to lose. A single depends on only one result.
Can an accumulator contain two selections?
Yes. An accumulator normally starts with two events, although the specific restrictions are set by the betting system.
What happens if a match in an accumulator is cancelled?
The selection may be settled as a void at odds of 1.00. The exact decision depends on the bookmaker’s rules and the reason for the cancellation.
Can outcomes from the same match be combined in one accumulator?
Not always. Correlated outcomes may be prohibited or handled through a separate Same Game Builder.
Does Sport Line API settle coupons by itself?
No. It provides the sports line and technical outcome identifiers. A separate Coupon API is used for bet placement and settlement.
What to Remember
Singles and accumulators may use the same matches and odds, but they are settled differently inside the system.
In a single, one outcome directly determines the coupon result. With an accumulator, the system must wait for every outcome to be settled, process any voids, and only then determine the final payout.
SportAPI connects the sports line to the coupon system through unique outcome identifiers. If you are developing a sportsbook website, you can connect Sport Line API for matches and odds and use the bet placement and settlement API to create, accept, and automatically settle singles and accumulators.