← Demo hub Torch compliance guide →

How a kiosk operates Client perspective

1. What this is

From the player’s point of view, a Kiosk Systems unit is a fixed terminal at a specific retail location. The customer uses it to access their account, optionally acquire digital gallery items (NFTs), receive sweepstakes entries tied to that visit, and—when they choose—reveal those entries to see any prizes. Cash handling, identity checks, and prize payout logistics are part of the in-store experience; outcomes are determined on the central server, not on the device.

2. Arrival and context

Each physical kiosk is enrolled with the platform using a kiosk API key and hardware identity. That pairing tells the system which store and which machine the session belongs to. Everything the customer does—purchases, free entries, reveals, and redemptions—is recorded under that location so accounting and compliance stay store-specific.

3. Account and sign-in

The customer signs in or registers as a user (profile, contact method, optional PIN/password depending on flow). The kiosk UI is the front end to the same account they can use from play-at-home experiences where enabled; sweepstakes and entry rules still respect per-location separation when they are on the floor unit.

4. No purchase necessary

The on-screen experience includes required no-purchase-necessary (NPN) messaging. Customers may obtain sweepstakes entries without buying anything—for example via a free entry path on the kiosk subject to the platform’s timing and fraud-prevention rules (such as limits per account over time). A purchase does not increase the odds of winning. Paid and free paths are designed so the promotion remains a legal sweepstakes, not pay-to-play gambling.

Exact copy and intervals for free entry are configured for compliance; operators should keep kiosk UI and posted rules aligned with counsel-approved text.

Diagram — path to a free entry

5. Purchase, entries, and credits

When the customer buys a digital item (NFT) with cash at the machine, the system records the sale and awards sweepstakes entries as a promotional benefit. The platform uses entry credits—batches tied to the user and that location—rather than materializing every single entry row at once. The standard earning rate on this platform is 100 entries per $1 spent on eligible NFT purchases (as implemented in the entry service).

Balances and history the customer cares about (entries available to reveal, vault items, cash wallet if used) are shown in the kiosk UI and can also appear in the player portal where deployed.

6. Vault (digital collectibles)

Purchased NFTs land in the customer’s vault—their owned gallery. The vault is part of the entertainment and value proposition of the visit; it is separate from the sweepstakes reveal flow, though both may be surfaced in the same session.

7. Reveal and prizes

When the customer chooses to use entries, the app consumes entry credits and asks the server to process reveals. Prize assignment uses cryptographically secure randomness on the server; the kiosk does not decide outcomes locally. The on-device experience is an NFT-themed reveal (not slot reels, spinning prize wheels, or other gambling-style affordances as a matter of product and compliance design).

Predetermination and presentation

Consistent with the platform’s Missouri-oriented architecture, the result for a given entry is fixed by the server before the reveal animation runs; any randomness shown on screen is for presentation. Player choices in skill-style mini-experiences are honored where the product supports them without changing the assigned prize tier.

8. Redemption and larger prizes

When a prize is cash or needs to be paid at the store, redemption is handled through location workflows (portal/staff tools). The system maintains an audit trail. For high-value prizes, tax and identity requirements (for example W-9 / 1099 thresholds) apply as configured—customers may need to complete disclosures before payout.

Diagram — artwork, game reveal, prize at location

9. Why the store matters

Locations do not share entry pools or balances. Entries, credits, reveals, and redemptions earned at one store stay with that store’s books and obligations. A customer who visits multiple locations has separate context per site; the UI and APIs are built to prevent cross-location mixing. That mirrors how the business and legal model assign responsibility for prizes to the location where play occurred.