Planet Riches

Planet Riches is an intentionally narrow platform: rather than trying to cover every category, its published catalog is focused on slots.

For procurement, treat this profile as a comparison starting point. Request a current demo, build number, operator-account walkthrough and written commercial terms before selecting a deployment.

Slot-only focus, two-pot accounting, daily wheel, cashback wheel. These are the practical areas to test in a live demo rather than judging the product only by screenshots.

• Review player onboarding and account recovery.
• Inspect owner, manager and cashier permissions.
• Confirm reporting, audit logs and export options.
• Document support hours, escalation paths and planned maintenance.

The catalog is listed at 34 slot titles. That makes evaluation straightforward—operators can concentrate on theme quality, game pacing and promotional mechanics instead of category breadth.

Game counts are a snapshot of publicly described catalogs and can change as titles are added, removed or bundled differently by distributors. A current game manifest should be part of the buying process.

Published material describes a two-pot Entries/Winnings model plus Daily Wheel and Cashback Wheel promotions. Payment acceptance and redemption channels should be confirmed with the distributor.

Our directory does not assume that a platform accepts cards, ACH, cash, wallets or cryptocurrency unless a current provider explicitly documents that integration. Ask for a written funds-flow diagram covering purchase, credit issuance, redemption, refunds and reconciliation.

Android, iOS and browser access are commonly listed.

Test the player experience on the devices and networks your customers actually use, including login recovery, update behavior and low-bandwidth performance.

Operational fit matters as much as the game library. For Planet Riches, verify role-based access, terminal or location management, credit history, player-search tools, reporting, backups, support and incident response before launch.

For multi-location businesses, ask whether the backend can segment staff, balances and reports by shop or agent without sharing unnecessary permissions.