Quick answer: For a state lottery Android app with iLottery (or iLottery going live soon), complete the IARC questionnaire so you receive an IARC certificate ID. In the US, the rating you care about is ESRB: Adults Only (AO) with content descriptor Real Gambling. Do not route lottery ticket purchases through Google Play Billing, and do not mark “purchase digital goods” just because players buy tickets. That badge and billing path get apps rejected.
I’ve helped several states clear this rejection path even while Google’s public gambling application form chart still reads as if official lottery apps are not allowed. The chart lagging behind policy reality is not a reason to stall your IARC. Get the certificate ID. Once you have it, you are golden.
This guide is for lottery product, digital, compliance, and vendor teams shipping official state lottery apps on Google Play — especially teams adding or expanding iLottery.
Why IARC matters once iLottery is in the binary
Results-only and ticket-check apps can limp along with a soft content story. The moment players can wager, pay for chances, or buy tickets toward cash prizes inside the official app, IARC has to tell the truth about real-money gambling.
Wrong answers create two expensive problems:
- Wrong rating or missing Real Gambling — the store listing does not match what the app does.
- False “In-App Purchases” / digital goods signaling — usually from answering Yes to digital goods or wiring ticket sales through Play Billing. That path rejects.
At Lissiland we treat this as a Stability problem, not an ASO experiment. You cannot Expand into iLottery acquisition while Play Console still thinks your commerce model is a consumer IAP game.
Related reading: How to use Google Play Console analytics for lottery apps.
The real goal: an IARC certificate ID
Teams over-focus on every regional rating badge. For US state lottery apps, the outcome that matters is simple:
- IARC certificate ID assigned — this is the finish line. Once you have it, you are golden.
- ESRB: Adults Only (AO) — the US rating you care about.
- Content descriptor: Real Gambling
- No “In-App Purchases” on the listing merely because users buy lottery tickets or wagers
If your build also sells conventional digital goods (subscriptions, cosmetic packs, credits sold through Play Billing, and similar), answer the digital-goods questions honestly for those products. Ticket commerce alone is not that category.
Ignore the chart lag (with eyes open)
Google’s gambling contact / application materials still include a chart that reads as if many lottery and gambling scenarios are not allowed. Official state lottery teams still get stuck there in Slack and legal review.
That chart has not kept up with how regulated US lottery apps actually clear Play Console when licensing, geo-restriction, age gating, and declarations are done correctly. I’ve walked several states through the rejection loop anyway. Do not wait for Google to redraw the public chart before you complete IARC for an app that already has iLottery live, or that is weeks from go-live.
Lottery read: The chart is a support artifact. The certificate ID is the operational artifact. Fund the questionnaire, not the wait.
Category and gambling answers (copy this path)
Start from All Other App Types, then move into gambling. Exact Console wording can shift slightly; the intent below is what produces AO + Real Gambling for an iLottery app.
Gambling
- Does the app contain gambling themes? → Yes
- Select: Gambling themes; Playable casino games, lotteries, or racetrack betting
- Do not select: Playable bingo; Other games using in-app currency/tokens
- Are gambling themes a strong/prominent focus of the app? → Yes
- Can the lottery/gambling activities reward cash or something of significant monetary value? → Yes
- Can users wager, pay entrance fees, purchase additional chances, or make purchases related to winning cash rewards? → Yes
Online content
- Does the app feature or promote online content? → Yes
Promotion or sale of age-restricted products or activities
- Is the promotion or sale of age-restricted goods or activities a focus of the app? → Yes
- Alcohol or tobacco? → No
- Other age-restricted activities/items? → Yes (this is for the lottery / gambling activity)
Miscellaneous: where apps get rejected
This block is where well-meaning teams sabotage themselves.
- Does the app share the user's precise physical location with other users? → No
- Does the app allow users to purchase digital goods? → No (for a standard iLottery ticket / wager purchase path that is not Play Billing digital goods)
- Does the app feature cash rewards or other rewards convertible to cash? → Yes
- Select: Cash Convertible Rewards
- Do not select: NFTs / transferable digital assets
- Can users wager, purchase, pay entrance fees, buy additional chances, or otherwise make purchases toward cash rewards? → Yes
Play Billing rule: If you use Google Play Billing for lottery tickets or wagers, or you mark the questionnaire as if ticket sales are digital goods / IAP, expect rejection. Official lottery ticket commerce is not a consumer IAP product. Route payments the regulated lottery way. Keep the questionnaire aligned with that reality.
Only flip digital goods to Yes if the actual build sells conventional digital goods through Play. Then the listing may correctly show In-App Purchases for those items — not because someone bought a Powerball ticket.
Other content (keep it clean)
For a typical official lottery app without violent, sexual, or UGC social features:
- Does the downloaded app contain ratings-relevant content? → Yes
- Violence / blood / gore → No
- Fear or horror → No
- Sexuality or nudity → No
- Offensive language → No
- Controlled substances / drugs → No
- Crude humor → No
- Does the app allow users to share user-generated content? → No
For online content:
- Violence → No
- Sexual content → No
- Offensive language → No
- Drugs / controlled substances → No
- Is the app primarily a web browser or search engine? → No
- Is the app primarily news or educational content? → No
If your app does have UGC, chat, or social uploads, answer those honestly and treat moderation as release infrastructure — same Stability logic as on iOS.
Expected result
When the questionnaire is correct, you should see:
- ESRB: Adults Only 18+ (AO) for the US
- Content descriptor: Real Gambling
- An IARC certificate ID assigned to the app
- No In-App Purchases badge caused only by lottery ticket / wager purchases
That certificate ID is the operational win. Listing polish and weekly Play Console habits come after. See State lottery mobile app analytics in Google Play Console once the rating story is clean.
Action checklist for state lottery Android teams
- Confirm iLottery scope in the binary you are rating: live today, or go-live soon. Same honesty either way.
- Complete IARC with the gambling / cash / age-restricted path above. Do not soft-pedal real-money activity.
- Answer digital goods No unless you truly sell conventional Play Billing digital goods.
- Do not use Play Billing for lottery tickets or wagers.
- Verify AO + Real Gambling and capture the IARC certificate ID.
- Do not stall on the public gambling chart if your licensing and geo model are otherwise sound. The certificate is the unlock.
- Align legal / vendor / product on one questionnaire narrative before the next release train.
FAQ: IARC and state lottery apps on Google Play
What is the single most important IARC outcome?
Getting an IARC certificate ID assigned. For US state lottery apps with iLottery, that pairs with ESRB Adults Only (AO) and Real Gambling. Once the certificate ID exists, you are golden on the rating step.
Does Google’s gambling application chart mean lottery apps are banned?
The public chart often still reads as not allowed. That has not stopped correctly declared, licensed state lottery apps from clearing when teams complete IARC and commerce declarations properly. Do not treat the chart screenshot as the final operating truth.
Should ticket purchases count as digital goods or In-App Purchases?
No, not for standard lottery ticket or wager purchases outside conventional Play Billing digital goods. Marking Yes — or using Play Billing for tickets — is a common rejection path.
Is Adults Only only a US concern?
For US state lottery distribution, AO (Adults Only) is the rating outcome you care about. Complete the full IARC questionnaire so the certificate covers the territories Play Console expects, but do not over-optimize secondary badges at the expense of the US AO + Real Gambling result.
Does this apply before iLottery launches?
Yes. If iLottery is going live soon and the rated binary will include wagering or ticket purchase toward cash prizes, rate the app for that reality before go-live — not after the first rejection.
Where do I start if Play Console already rejected us?
Re-open content ratings / IARC, walk the questionnaire path in this article, remove Play Billing from ticket flows if it was added, and resubmit until you have a certificate ID with AO + Real Gambling and no false IAP badge.
Bottom line
State lottery iLottery on Google Play is not mysterious. It is a questionnaire and a payments boundary.
Tell IARC the truth: gambling focus, cash rewards, age-restricted lottery activity, online content. Do not pretend ticket sales are Play Billing digital goods. Ignore the outdated “not allowed” chart long enough to finish the form. Get the IARC certificate ID. Land AO with Real Gambling.
Wrong answers look like compliance theater. Right answers look like Stability.
Want a second set of eyes on your Play Console IARC answers, declarations, or iLottery go-live rating plan? Email me. cbluford@lissiland.com