Choose the game before the numbers
Selecting a country and game gives the interface the right number count, valid range, and bonus-number rules before you start tapping.
Product logic
How the exact-match lookup is designed
Lotto Facts is deliberately narrower than a typical lottery checker. It searches for an exact historical main-number combination in the draw archive for the chosen game, then shows any supporting details the API returns.
Enter only the main numbers
The current API matches exact main-number combinations. Bonus balls are displayed in the result cards when the archive contains them, but they are not part of the input.
Read the result in context
Every match should show the draw date, the winning numbers, any bonus numbers, jackpot information when available, and prize breakdown data when the archive has it.
What the current product does not do
It does not validate live tickets, calculate partial matches, or promise prize outcomes. Those claims would misrepresent the current API.
The frontend is therefore built to explain the rule set before the user searches, not after the result comes back.
FAQ
How the checker behaves
These answers reinforce the exact-match model and reduce false expectations.
Why does the checker ask me to choose a game first?
Every lottery uses different number counts and ranges. Selecting a game first keeps the checker accurate and avoids misleading searches.
Why did I get no result?
A zero-result lookup means Lotto Facts did not find that exact historical main-number combination for the chosen game in the current archive.
Do the results tell me whether I won a prize?
No. Lotto Facts is a historical exact-match archive, not a live ticket validation or prize checker.