Skip to content
All news

Running a lotto vertical without a second back-office

· sixteen87 Team · 4 min read

A dark glass clock face without numerals beside blank gold spheres

Lotto has its own rhythm: scheduled draws, cut-offs, liability and prize tiers. None of that requires a separate platform if the wallet and the operator console already speak lotto.

Lotto products are attractive to operators for a simple reason: they reach players who would never call themselves gamblers. A weekly draw, a syndicate with colleagues or a quick pick on the way home are habits, not sessions. The catch is that lotto runs on a different clock from casino and sportsbook. Sales open and close on a schedule, results arrive at a fixed time, and prize liability builds up between draws rather than settling bet by bet.

Historically that meant a dedicated supplier with a dedicated back-office, a separate wallet and a separate reporting pack. It works, but every join between systems is a place where a balance can disagree or a limit can be missed.

What the platform has to understand

  • Draw calendars with sales cut-offs and time zones per game
  • Ticket purchases as ordinary wallet transactions, including multi-draw and subscription purchases
  • Results from an external feed or an internal RNG, with a manual review path
  • Prize tiers that are fixed, pari-mutuel or a mix, with rollover and cap rules
  • Liability exposure per draw, visible before the draw closes

The operator’s day

In the sixteen87 Command Centre a lotto draw is an object like a campaign or a sports event. It has a schedule, a state and a set of rules. Before cut-off, the operator sees sales and exposure per tier. After the result is ingested, settlement runs automatically: winning tickets are credited to the wallet up to a threshold, larger wins open a review item with the ticket and the result attached, and the lobby publishes the outcome without anyone editing a page.

Because tickets and wins are wallet entries, every responsible-gaming limit already applies. A deposit limit set for the casino covers lotto purchases. A self-exclusion stops ticket sales on the spot. Syndicates split prizes with the same ledger precision as a bonus conversion, so a shared win is provable to the cent for every member.

Instant and fast draws

Fast draws run every few minutes and behave more like an instant game than a weekly lotto. They need tighter spend caps, RNG certification appropriate to the licence and a results display that is readable at a glance. Treating them as a category with their own limits, rather than an exception to the rules, keeps them safe and keeps the reporting clean.

The result is a lotto vertical that adds reach without adding a system. One wallet, one console, one set of limits and one reporting pack, with lotto’s own rhythm respected inside it.

Written by the sixteen87 Team.

More from the team

· 4 min read

Why wagering requirements should be weighted by game category

A single multiplier treats a high-volatility slot and a low-margin table game as if they cost the operator the same. They do not. Here is how category weighting fixes the maths without confusing the player.

Read article

See it on your own brand

We will show you the platform features behind this article running on a demo environment.