How Do Video Lottery Terminals Work: The Four Layers
A VLT is not one device deciding one outcome. It is a chain, and every link in the chain has a different owner. Read the table as a specification checklist: if any row is unresolved, the build is unresolved.
| Layer | What it does | Who owns it | What the buyer must fix |
|---|---|---|---|
| 1. Player terminal | Presents the game, takes the wager, prints or credits the result | Supplied by the manufacturer, operated by the venue | Cabinet, display, deck, acceptor and printer models |
| 2. Connection | Carries each transaction to the central system and back | Specified by the lottery or gaming board | Protocol, network path and failover behaviour |
| 3. Central system | Resolves the outcome (in central-determination markets), hosts the game library and enforces limits | The lottery or its system vendor | Which layer determines results — terminal or central |
| 4. Accounting | Meters play per game, splits revenue by statute and reports to the regulator | The regulator, operated by the lottery | Reporting fields the terminal must expose |
Are VLTs Random? RNG in the Terminal vs the Central System
"Are VLTs random" has three different correct answers, because three models exist. A page that answers with one of them is only right for part of the market.
| Model | Where the result is produced | What that means for a build | Typical setting |
|---|---|---|---|
| Terminal RNG | Inside the cabinet, on the approved platform | The terminal carries an approved RNG and its own audit trail | Many VLT programmes and most casino slots |
| Central determination | In the central system; the terminal requests a result | The cabinet is a presenter; the outcome path is a network transaction | Lottery-run programmes that keep the outcome with the lottery |
| Fixed result pool | Pre-generated pool, drawn like a scratch card | The terminal has no outcome role at all; verification is on the pool | Some lottery jurisdictions |
In all three, the outcome of a wager is independent of the previous wager — that is what "random" means operationally. What changes is where the audit sits, and therefore what the testing scope covers.
Why a Video Lottery Central System Exists
The central system is not there to make the games fairer; it is there so the state can see what happened. Four functions explain almost every requirement a supplier receives:
- Monitoring: which terminal is live, which game is loaded, whether a door is open.
- Revenue integrity: metering at the source rather than trusting a venue reconciliation.
- Control: limits, session rules, shutdown of a terminal or a game across the network.
- Reporting: the statutory split between lottery, venue and — at racetracks — racing.
Because the system controls the network, the supplier's customer is often the lottery rather than the venue. That single fact changes procurement, acceptance and support: see video lottery terminal hardware for how the build sheet follows from it.

One Session, Step by Step
- Identify the player or the terminal. Depending on the market, play is anonymous at the terminal or tied to a card or account.
- Take the wager. Cash, ticket or card is accepted; the credit is held at the terminal or at the system, per the programme rules.
- Request the outcome. Either the terminal draws from its approved RNG, or it requests a result from the central system.
- Present and record. The result is shown, the meters increment, and the event is logged locally and — where the programme requires it — at the system.
- Cash out. The terminal issues a ticket or credits the account. Whether cash is dispensed at the machine is a jurisdiction rule, not a hardware preference.
Can the Winning Percentage Be Changed?
This is a permissions question before it is a technical one, and the honest answer is deliberately narrow.
- Who sets it: in lottery-run programmes the payout range is set in legislation or by the regulator; in casino markets the operator selects from approved paytables.
- Who can change it: nobody at the venue, in either model. A change is a configuration change on an approved build, and it is submitted to the regulator or its lab.
- What the supplier does: builds the configuration, documents it, and supplies the evidence the submission needs. The approval is not the supplier's to grant.
That is why "can you change the RTP on this terminal" is answered with a jurisdiction and an approval path, not with a number.
Hold, Payout and Rules: What the Numbers Mean
| Term | What it measures | Who publishes it |
|---|---|---|
| Coin-in / turnover | Total amount wagered, including re-wagered credits | Operator or regulator reporting |
| Net win / hold | Wagered minus prizes paid, as a percentage | Regulator's revenue reports |
| Payout / RTP | The share returned to players over the long run under the approved math | The approved paytable and the market's rules |
These three are not interchangeable, and a page that quotes one as if it were another is unusable for a specification. In New York, for example, the Commission publishes video lottery revenue reports and states that the proceeds go to the State Lottery fund for education aid — a statutory arrangement, not a machine setting.
What Triggers a Re-test
Four changes usually reopen the file. The exact answer is the regulator's, but the pattern is consistent:
| Change | Why it matters | What to prepare |
|---|---|---|
| New board, display or peripheral model | Changes the tested hardware configuration | Updated BOM and interface note |
| Firmware or game-package version | The approved build is version-specific | Build hash and release note |
| New game added to the library | Game-level approval is separate from terminal approval | Game math and rules documentation |
| Protocol or central-system version | Changes the transaction path itself | Interface specification and test plan |
Build Implications for a Terminal Cabinet
Three practical consequences follow, and they are the same in every jurisdiction:
- The cabinet is a presenter, so service access matters more than styling. A terminal that cannot be serviced in place becomes a network outage.
- The payment path is part of the specification. Acceptor, printer and card reader models drive cut-outs, harness and power budget.
- The build record is the product. Which board, which firmware, which peripherals — the file that proves it is what a submission is made of.
How those parts are grouped and quoted is on video lottery terminal hardware; what the category itself means is on what is a VLT machine.
Frequently Asked Questions
How do video lottery terminals work?
In four layers: the terminal presents the game and takes the wager, a protocol link carries the transaction, a central system resolves the result (in central-determination markets) and hosts the game library, and an accounting layer meters play and reports revenue. Which layer produces the outcome depends on the jurisdiction.
Are VLTs random?
The outcome of each wager is independent of the previous one in all three common models — terminal RNG, central determination, or a fixed result pool. What differs is where the result is produced and therefore where the audit and testing scope sits.
Can the winning percentage be changed on a VLT?
Not at the venue. In lottery-run programmes the payout range is set by legislation or the regulator; in casino markets the operator chooses from approved paytables. A change is a configuration change on an approved build, submitted to the regulator or its laboratory — the supplier builds and documents it, and the approval is not the supplier.
Can you pull money back out of a video lottery machine?
Cash-out behaviour is a jurisdiction rule. Some programmes issue a ticket that is redeemed at a cage or kiosk rather than dispensing cash at the terminal; others allow cash. The terminal is built to the rule of the market it ships into, so the answer belongs in the specification, not in a generic statement.
Does a VLT work without a connection to the central system?
No. The connection is what makes it a terminal. If the link drops, the terminal is designed to stop accepting play rather than to keep resolving results locally — the exact behaviour is defined by the programme, and the failover path is part of the technical submission.
Regulatory detail differs by jurisdiction and changes over time. Where a specification version or an effective date is named on this page, confirm it against the regulator's own publication before a build is released.
Specify a Terminal Against Your Market
Send the destination jurisdiction, the central system you must connect to, and the game mix you intend to run. The reply names the termination layer, the protocol options and the evidence the submission will need.
Request a Terminal Review →