Lottery Software Development: Draw, iLottery, Retailer and Raffle Software for Licensed Operators

Updated October 2026 · Written and maintained by the Progression Agency strategy team

Lottery software development is the build of the systems a licensed lottery runs on: draw management, a certified random number generator or draw-machine records, ticket and entry handling, player accounts and wallets, retailer terminals, prize payouts, back-office reporting and the responsible-gaming controls a regulator expects. We build that software for licensed lottery operators, their technology suppliers and licensed charities that run regulated raffles, and we prepare the documentation the lab asks for before go-live. We do not hold licenses, run draws or market gambling to the public; the operator and its regulator decide what the system must do.

What does lottery software development cover?

Lottery development covers every system a licensed lottery depends on, from the draw calendar and the random number generator to retailer terminals, player wallets and the controls a regulator expects. It is the build and not the license: the operator holds the license, runs the draws and answers to the regulator.

Who we build for

We build for state and national lotteries’ technology suppliers, licensed private operators, licensed charity and society lotteries, and retailer networks. The players are adults of legal playing age in the jurisdiction, and the buyers are businesses. If your organization does not hold a license, or is applying for one, the license comes first and the software follows.

What a software developer does not do

A developer does not hold the license, run the draws, set the prize table or market to players. We do not build prediction or number-picking tools, which are consumer products aimed at players and are outside this page. We also do not build for unlicensed operators or for offshore evasion of a local rule. Card-game platforms are scoped separately.

Lottery development company or platform vendor?

A software development company builds to your rules, while a platform vendor licenses you a finished product that you configure. Neither is better by default. Decide which fits by what you need to control, how fast you must launch and who will own the code.

How does an online lottery system work?

An online lottery system takes a ticket sale, records the entry, closes sales at the published time, runs the draw, publishes the result, matches winners and pays prizes, with an audit trail behind every step. Each step is owned by one module.

From ticket to draw to prize

The nine steps below are the spine of a draw game. A regulator can ask to follow one ticket from sale to payout, so each record must be written once, in order, and never silently changed.

1. Sale: the player or retailer buys an entry.
2. Entry record: the system writes the entry before the sale is confirmed.
3. Draw close: sales stop at the published time.
4. Draw: a certified generator or a recorded draw machine produces the numbers.
5. Results: the result is published once.
6. Winner match: entries are compared to the result.
7. Claim: the winner claims, with identity checks as the rules require.
8. Payout: the wallet or payments module pays, and tax form data is captured where it applies.
9. Audit: every step stays in the log.

Draw games, instant games and fast-play games

Draw games run on a schedule, so the software needs a calendar and a close time. Instant games reveal a result at purchase, so they need certified game math and secure inventory or generation of outcomes. Fast-play games sit between: frequent draws with short cycles, which stress the draw scheduler and the reporting layer. Each type has its own certification path.

Where retail sales fit

Retail terminals feed the same central system as online sales. A ticket sold in a store and one sold online appear in the same entry record, the same draw and the same audit log, so the operator can settle with retailers and report to the regulator from one source of truth.

Lottery management software: the modules

Lottery management software is a set of modules, not one program. The table lists the ones most platforms need, what each does and who uses it. A lottery management system for a charity raffle uses fewer of them than a state iLottery platform.

Draw management and scheduling

Lottery draw software holds the draw calendar, the close time for each draw and the publication of results. It must stop sales at the published close time, record which number source was used and prevent any edit after publication. An audit trail shows who configured the draw and when.

Player accounts and wallets

Each player has an account with age and identity checks as the jurisdiction requires. The wallet is a separate ledger: deposits, purchases and winnings are each recorded, and there are no transfers between players. Limits and self-exclusion read from the same account, so a restriction applies on every channel.

Prize claims and payouts

Small prizes may pay automatically, while larger ones go through a claim workflow with identity checks. For raffles and lotteries, the IRS instructions for Forms W-2G and 5754, revised in January 2026, say regular gambling withholding at 24% applies when winnings minus the wager are more than $5,000, and that the reporting threshold adjusts yearly for inflation for years after 2025. The platform captures the winner’s details and the form data; the operator’s tax adviser confirms the current threshold.

Lottery management software development for retailer networks

Lottery management software development for retailers connects terminals, agents and commissions to the central system. Lottery retail management software has to keep working when a store’s connection drops, then reconcile cleanly when it returns.

Terminals, agents and commissions

The retailer module holds each agent’s profile, terminals, sales and commission rules. Roles and permissions separate a store owner from a clerk and from a regional manager. A commission engine applies the operator’s published rules to each sale, so statements match what the retailer sees on the terminal.

Validation, settlement and reconciliation

At the counter, a terminal validates a winning ticket, and the central system records the claim and the payout. Settlement compares what the terminal reports with what the center holds, flags differences and produces the daily statement. Reconciliation reports are the retailer team’s main tool.

Instant ticket inventory and field service

Where instant tickets are physical, the software tracks inventory by pack: ordered, delivered, activated and settled. A field service view lists store visits, terminal faults and stock counts, so representatives know where to go and what to bring. Our retail software and kiosk software pages describe the related terminal and point-of-sale work.

Random number generators and draw integrity

Lottery random number generator software must produce numbers no one can predict or alter, and it must leave a record that a regulator can check. Which source is used is the regulator’s decision; the software records whichever is chosen.

Certified RNG or a physical draw machine

Some jurisdictions draw with a certified software generator, others with a physical draw machine under observation, and many use both for different games. The regulator decides. Our job is to integrate the certified generator or to capture the draw-machine record, bind it to the draw, and store it where it cannot be edited. We integrate a certified generator; we do not self-certify one.

How RNG output is tested

NIST’s SP 800-22 test suite and its SP 800-90A recommendation are common reference points. SP 800-22 describes statistical tests for random and pseudorandom number generators, and NIST states that no set of statistical tests can absolutely certify a generator; SP 800-90A specifies deterministic random bit generators. The test lab and the regulator set the actual requirement for a lottery, and the lab runs its own tests.

Audit logs a regulator can follow

An audit log is append-only: each entry carries the time, the actor, the action and the before and after values, and no one can edit or delete a line. Servers keep synchronized clocks so the order of events can be reconstructed. Change records link each release to the approved version. A regulator should be able to pick one draw and follow it end to end.

Online software development and iLottery

Online lottery development builds the web and mobile channel through which a licensed operator sells draw games and instant games. An online lottery platform adds accounts, wallets, location and age checks, and responsible-gaming controls to the core draw system. The word online lottery software covers all of it.

Online draw sales, subscriptions and syndicates where allowed

Typical online features are single-draw purchases, repeat purchases on a schedule, and shared entries, each only where the license and the rules allow it. Each feature has its own consent, limit and refund logic. A subscription must be easy to cancel and must respect a player’s limits and any self-exclusion.

Instant games online

An online instant game reveals a result at purchase. The game math must be certified before launch, and the outcome must come from a certified source on the server, never from the player’s device. The published rules and the prize table come from the operator and must match what the software pays.

Federal law and online lottery sales in the US

The documents, without advice: in 2011 the Justice Department’s Office of Legal Counsel concluded that the Wire Act, 18 U.S.C. § 1084, does not reach wire communications unrelated to a sporting event or contest, so it did not bar New York and Illinois from selling lottery tickets over the internet to in-state adults. A 2018 opinion read the Act more broadly, and in 2021 the First Circuit held in New Hampshire Lottery Commission v. Rosen that the Wire Act applies only to interstate wire communications related to sporting events or contests. Federal law also has a chapter on lotteries with an exception for state-conducted lotteries. Each operator’s own regulator and counsel decide what the software has to do.

Age and location checks

Where a jurisdiction limits sales to adults inside its borders, the platform checks age at registration and checks the device’s location at purchase. Our sportsbook guide explains the mechanics in its geolocation section, and the same techniques apply to a lottery.

Lottery app development

Lottery app development covers apps for licensed operators: ticket checkers, results, account and companion apps, and full purchase apps where the license and the store allow them. Store rules, not just code, decide what an app can do.

Ticket checker, results and companion apps

A checker app scans a ticket’s code and tells the holder whether it won, using the same entry record as the retail terminal. A results app shows published draws. A companion app may show account balances, limits and claims status. All of them read from the operator’s central system and none holds the logic that decides a winner. Our apps are built as iOS apps, Android apps or cross-platform apps, with UI and UX design for clear, accessible screens.

Store rules for lottery apps

Apple’s guideline 5.3.4 says apps that offer real money gaming or lotteries must have the necessary licensing and permissions where the app is used, must be geo-restricted to those locations and must be free on the App Store, and 5.3.3 bars in-app purchase for credit used in real money gaming; see Apple’s review guidelines. Google Play allows lottery apps only from licensed operators that complete its application process, are free to download, do not use Play In-app Billing, block minors and unlicensed locations and show responsible gambling information; see Google Play’s real-money gambling policy. Our sportsbook guide already covers the app store rules in detail.

Notifications players control

Notifications are opt-in. A player chooses what to receive and can turn it off, and no message goes to a self-excluded player. A results notification for a ticket the player holds is service information; promotional messages follow the regulator’s advertising rules and the operator’s own policy.

Lottery game developers: game logic and prize math

Lottery game developers turn an operator’s approved rules into code: the number matrix, the prize table, the draw schedule and the payout logic. Lottery game development is exact work, because the published rules and the software must agree to the cent.

Game rules written as a specification first

Before a line of game code, the rules are written as a specification: how many numbers, from what range, how matches are counted, what each tier pays, and what happens to unclaimed prizes. The specification is what the test lab checks the software against, so it is a deliverable in its own right.

Prize structures, odds and the published rules

The prize structure and odds come from the operator and its regulator. Odds are shown as the operator publishes them, and we do not create odds, advice on picking numbers, or any claim about improving a player’s chances. If the published rules and the software disagree, the software is wrong.

Instant-win game software for licensed operators

Instant-win games are a licensed lottery product here, with outcomes generated and recorded on the server and game math certified before release. Promotional instant-win sweepstakes run by brands are a different regulated activity and are outside this page.

Certification and standards by jurisdiction

Certification is done by independent test labs against the standards a regulator adopts. We prepare the documentation the lab asks for; the lab certifies and the regulator approves.

GLI standards and independent test labs

Gaming Laboratories International says it tests gaming devices and systems against the standards of the relevant jurisdictions, that each jurisdiction can set its own, and that many use GLI standards as a starting point. Its published standards include GLI-19 for interactive gaming systems, GLI-31 for electronic raffle systems, GLI-14 for finite scratch ticket and pull-tab systems and the GLI-GSF security framework. Which one applies depends on the product and the regulator.

The WLA Security Control Standard

The World Lottery Association publishes the WLA Security Control Standard for the lottery sector; the 2024 edition was ratified by its General Assembly on October 24, 2024. The WLA site lists certified lotteries and certified suppliers. Whether a client’s regulator or procurement asks for it is the client’s call.

UK Gambling Commission technical standards

In Great Britain the Gambling Commission’s remote gambling and software technical standards are set under sections 89 and 97 of the Gambling Act 2005; the page was last updated on October 31, 2025. A remote lottery system for a licensed Great Britain operator is built and tested to them.

Malta Gaming Authority and other regulators

The Malta Gaming Authority publishes a licensee register that can be searched by licensee name, authorization status, URL or gaming service. Other regulators publish their own rules, and we claim no approval from any of them. For operators in a given jurisdiction, we work from that regulator’s published text.

Responsible gaming built into lottery software

Responsible gaming in lottery software means controls that work on every channel and that a regulator can test: limits, cool-off periods, self-exclusion and age checks. The regulator sets the list; the software makes each item configurable and auditable.

Limits, cool-offs and self-exclusion

A player can set deposit and spending limits, take a cool-off, or exclude themselves for a period. Limits tighten at once and loosen only after a delay. A self-excluded account cannot buy, receive promotions or open a new account with the same identity. The operator chooses the values within the rules it is bound by.

Age verification at registration and at payout

Age is checked at registration through the operator’s chosen vendor and checked again when a large prize is claimed. Nothing on this page is aimed at, or sold to, minors, and the software refuses an account that cannot be verified as an adult.

Responsible gaming frameworks and help lines

The World Lottery Association publishes Responsible Gaming Principles and a Responsible Gaming Framework with certification levels for its member lotteries. In the US, the National Council on Problem Gambling runs the National Problem Gambling Helpline at 1-800-MY-RESET. Platforms show help-line information where the regulator requires it and link to the operator’s own resources.

KYC, AML, payments and security

A lottery platform handles identity, money and personal data, so identity checks, payment controls and security testing are built in from the first design. The operator’s compliance team decides the policies; the software enforces them.

Identity checks and watch lists

Identity and watch-list checks run through the vendor the operator chooses, called by the platform at registration, at payout and when risk rules fire. The results and decisions are logged, and a human reviews a hit before an account is blocked or a prize is held.

Deposits, payouts and card security

Card details are handled by the payment provider so the platform does not store them. The PCI Security Standards Council publishes PCI DSS, which it revised in a limited update as version 4.0.1, and the operator’s provider is assessed against it. Payout rules, such as the same account for deposits and withdrawals, come from the operator’s policy.

Security testing, uptime and disaster recovery

Security testing, including penetration tests by an independent firm, belongs before lab submission and after major changes. Backups, failover and a recovery plan are written down and tested, because a draw cannot be rerun. Related services include website security and cloud hosting; where a regulator requires data in its jurisdiction, the hosting region is set in the written scope.

Custom, white label or a licensed platform?

Custom software is built to your rules, white label is someone else’s product with your brand on it, and a licensed platform is that product under your own configuration. The license and compliance duties stay with the operator in all three.

What is white label software, and how does white label work?

White label software is a finished product that a vendor lets you rebrand and run as your own. The vendor keeps the code and you pay a fee or share. It speeds launch, and it does not move your duties: you still need the license, still answer to the regulator and still run the responsible gaming program. Our white label development page covers the web side.

White label versus private label

White label is a product sold to many buyers under their own names, while private label is made for one buyer under that buyer’s name.

Custom lottery system development

Custom lottery system development suits an operator whose rules, games or integrations do not fit a product. The table sets out the trade-offs. Our guide to custom or off-the-shelf software goes through the general decision.

Lottery software providers: how to compare them

Compare lottery software providers on what they can prove: certifications they hold, references you can call, exit terms and uptime commitments in writing. A lottery platform provider that says only that it is the best has told you nothing.

Questions for a lottery platform provider

Which standards has the platform been tested against, and where can the certificates be checked? Do we get source access or escrow? Can we export our data in a standard format? What are the uptime terms, with what remedies? Who owns the changes we pay for? Verifiable answers matter more than a presentation.

How state lotteries buy systems

State lotteries buy through public procurement. The New York State Gaming Commission, for example, publishes its solicitations as requests for proposals and invitations for bid, with schedules for questions and deadlines, and points vendors to the state Contract Reporter. The North American Association of State and Provincial Lotteries, NASPL, counts 53 lottery organizations as members. Technology suppliers usually reach a state lottery as a bidder or a subcontractor.

Best lottery development company: what the claim should prove

Anyone can say they are the best lottery development company. The claim should come with verifiable certifications, regulators they have worked with and references you can contact, not a ranking. This page describes the work, the scope limits and how we quote, so you can judge us on those.

Raffle software for licensed charities

Raffle software lets a licensed charity or society sell entries, run the draw, publish winners and keep records. Charity lottery software needs the same care as a lottery platform at a smaller scale, and every rule depends on the charity’s license.

Online raffles and 50/50 draws where state law allows

Whether a charity may sell raffle tickets online, or run a 50/50 draw, depends on the state and on the charity’s license or registration. Charity lottery software and 50/50 raffle software compute the pot, take the sale and record the draw; the charity and its counsel confirm the rules before any ticket is sold. We list no states here.

UK society lotteries and the Gambling Commission

The Gambling Commission’s fundraising and lotteries guidance says running lotteries or raffles with ticket sales over £20,000 each, or £250,000 in a calendar year, needs a license from it, while smaller ones register with the local authority, and the fundraising guide adds that an online lottery, including one on social media, needs a Gambling Commission license. Software for a British society lottery is built to the requirements as the Commission publishes them.

Tax forms for raffle prizes

The IRS Publication 3079, Tax-Exempt Organizations and Gaming, covers raffles run by exempt organizations, and the W-2G instructions say their requirements apply to church raffles and charity drawings. Raffle software can collect the winner’s name, address and taxpayer identification number and prepare the form data; the charity files the forms and checks the current thresholds.

Promoting the raffle

This page covers the build. Promotion of a charity draw belongs with fundraising marketing and nonprofit marketing, and the organization’s site with nonprofit websites.

Integrations a lottery platform needs

A lottery platform is a hub: it talks to payment providers, identity and location vendors, fraud tools, CRM and the data warehouse. Each integration has an owner and a failure plan.

Payment, wallet and payout providers

Payment connections handle deposits, refunds and payouts. Each call is idempotent so a retry never pays twice, and each reconciles to the wallet ledger daily. A provider outage must leave the system in a known state.

KYC, geolocation and fraud vendors

The operator chooses the vendors, and the platform wraps each behind a common interface so a vendor can change without a rebuild. Vendor results are stored with the decision made on them.

CRM, bonus engine and data warehouse

A CRM holds opted-in contact and service history. Where the jurisdiction allows bonuses, a bonus engine applies approved rules and respects player limits; where it does not, it stays off. A data warehouse feeds regulator reports and the operator’s analytics. Our API development and CRM development pages cover the building blocks, and cloud applications the platform they run on.

How a lottery platform build project runs

The project starts with the regulator’s requirements and ends with change control after launch, and the lab and regulator, not the build team, set most of the dates. Progression writes the scope down before building.

Requirements and a regulator map

Discovery means interviewing the people who run the lottery today, mapping the process as it actually works, and mapping each regulator requirement to a module. The output is a written scope with priorities. Our custom software development page describes the discovery approach we use.

Architecture, build and QA

Architecture settles the module boundaries, the data model, security, backups and logging. Builds run in phases, with automated tests on every change and code reviewed before it merges, the practices our software page describes. Game math and the draw sequence get their own test packs. See our software development life cycle and agile delivery pages. A first release can cover one module or one game.

Test lab submission and go-live

For the lab, we prepare the documentation it asks for: specifications, data models, test evidence and change records. The lab tests, the regulator reviews, and the operator decides when to go live under its license. A certification round that finds an issue means a fix and a resubmission, which is why the plan has no fixed date.

Monitoring and change control after launch

After launch every change is recorded, tested and, where the rules require, resubmitted. Monitoring watches draw close, results publication, payment queues and error rates. Support is an ongoing plan, sized to the system. If you need more hands, dedicated developers or software outsourcing are alternatives, and software consulting can review an existing platform first.

How AI assistants answer questions about lottery software vendors

Operators ask assistants which vendors build certified draw systems or iLottery platforms. The assistants repeat published, checkable facts, so a vendor that states its standards, process and limits in plain text is easier to name accurately.

What operators and charities ask

Typical questions are who builds lottery management software, what a charity needs for an online raffle, which standards a lottery platform must meet, and whether a vendor can work in a given jurisdiction. Answers cite regulator and standards bodies’ pages, vendor pages that state scope and limits, and independent listings.

What a vendor should publish

A vendor should publish the standards it works to, the process from requirements to go-live, who holds the license, and what it will not build. A vendor that claims certifications should link to a page where they can be checked. Our related guides on casino SEO and AI search for casinos cover marketing and visibility for operators, which is a separate engagement.

What does lottery platform build cost?

Lottery development is quoted after a written scope, because modules, jurisdictions, certification rounds and integrations change the work more than anything else. Progression publishes no price for it, and we do not quote a range before scoping.

How much does it cost to develop a lottery app?

There is no honest single number. A ticket checker app that reads from an operator’s existing system is a small scope, while a purchase app with accounts, wallet, location checks and responsible-gaming controls is a platform. The cost is set by the written scope and by how many certification rounds the regulator requires.

What drives the cost

The main drivers are the number of modules, the number of jurisdictions and regulators, the number of certification rounds, integrations with payment, identity and location vendors, hosting and the support plan.

How we quote

We start with discovery, write a scope with priorities, and propose a phased build, so each phase has a clear output before the next starts. Third-party costs such as test lab fees, vendor licenses and hosting are paid by the operator to those parties.

Related services for lottery and gaming software

These pages cover the work around a lottery or raffle platform.

• Sports betting app development: sportsbook and fantasy builds
• Custom software development
• Web app development
• Fintech software for payments and wallets
• Blockchain apps
• Ecommerce apps
• Education software
• Regulated healthcare software
• Casino SEO
• AI search for casinos
• Nonprofit websites
• Fundraising marketing
• Custom or off-the-shelf software
• UI and UX design

Frequently asked questions