LottoPH Deep Dive — Player Wallets, Agent Float + Commission, and Operator Payout Control

If you have ever tried to run a Philippine lotto desk with Facebook result screenshots, GCash chats, and a spreadsheet for winners, you already know the pain. The draws are public. The money is not. Players want instant balances and clear cutoffs before 2PM, 5PM, and 9PM. Street tellers need to sell walk-in tickets without waiting for you to approve every ₱100 sale. You need branding, risk controls, and a way to know who won — without auto-paying agent tickets into the wrong wallet.

LottoPH is RamerLabs’ white-label Philippine lotto Script built for that reality. It scrapes official PCSO results, runs player wallets and agent teller desks, settles player wins automatically, and leaves agent win payouts under your control. This post walks through the full product story and the operator workflow we just expanded — about fifteen hundred words of how it actually works on a live desk.

Try before you buy

The fastest way to understand LottoPH is to click through the live demo: pcso.ramerlabs.com. You can explore the player dashboard, the agent teller desk, and the admin console. Demo mode can block real betting while you showcase the UI to a partner; turn it off when you are ready for a live operation. The store product is a lifetime Script license with free lifetime updates from RamerLabs — buy once, activate with your license key, and deploy under your brand.

Product page: ramerlabs.com/product/lotto-ph/ · Price: $499 lifetime.

The problem LottoPH is built to solve

Philippine lotto operations sit at an awkward intersection of public data and private cash. Official numbers come from pcso.gov.ph. Stake and payouts usually still live in chat apps. That creates three failure modes operators know too well:

• Trust gaps — players cannot see a clean ticket history or wallet ledger.
• Teller chaos — agents sell on the street, remittance is informal, and nobody has a single source of truth for float versus commission.
• Payout risk — if every winning teller ticket auto-credits a system wallet, you can lose control of how cash leaves the business.

LottoPH treats those as product problems, not “just hire more staff” problems. The platform connects official results to bets, separates player money from teller economics, and gives admins an explicit Wins / Payouts list when an agent ticket hits.

Architecture in plain language

Under the hood LottoPH is a Node.js API with PostgreSQL (Neon-friendly), optional Redis caching, WebSocket push for fresh results, and a Passenger-friendly path for common cPanel hosts. A scraper reads the official PCSO search results HTML — not a fragile unofficial JSON dump — normalizes draw dates for Asia/Manila (so a calendar day does not silently shift in UTC), upserts draws, then settles pending tickets.

Cron can hit an internal scrape endpoint about every fifteen minutes. Admins can also run the scraper on demand after a draw is published. Settlement soft-matches draw times so evening games still resolve when PCSO rows omit a clean AM/PM stamp. That detail matters more than it sounds: mismatched times are how “pending forever” tickets happen in amateur scripts.

Player workflow

Players register (or use your seeded accounts), fund a wallet, and bet before cutoff. Deposits support GCash, Maya, and bank transfer. You configure the rails in Admin → Wallet: account numbers, names, and optional QR images. Players pick a method, send money, then submit a reference number and/or proof screenshot. Fraud guards reject duplicate references and enforce max deposits per hour plus a max amount per transaction — defaults you can tighten.

Betting is category-driven: exact 2D/3D/4D/6D, last-digit styles, and pick-set games such as Ultra 6/58, Grand 6/55, Superlotto 6/49, Megalotto 6/45, and Lotto 6/42. Categories are enabled and priced in Admin → Rewards. On Place Bet, choosing a category opens a popup form (draw, numbers, amount, Lucky Pick). Confirm, then success — with an option to print an e-ticket.

Hot / Cold analytics sit on the player dashboard, powered by the same statistics engine admins can rebuild. Lucky Pick samples from hot numbers for the selected game rules so the form is not blank guesswork.

By default, betting closes one hour before draw time. Pending bets can still be edited until that cutoff. When results land and settlement runs, player wins credit the player wallet automatically. Withdrawals back to mobile wallets still go through your approval queue so you stay in the cash loop where it matters.

Agent / teller desks — float and commission

This is the expansion many Philippine operators asked for. An agent is a teller account, not a downline recruiter. Admin → Agents creates the account with name, email, password, commission percent, and a GCash number used for commission cashouts. You can ban or unban agents, and update GCash later.

Agents have two balances on purpose:

1. Float — funded by Admin Instant Deposit (same wallet credit tool, agent user ID). Float is only for selling tickets. Stake debits float when a ticket is placed.
2. Commission — a separate wallet. On each sale, commission (stake × rate) credits here — not float. Agents request withdrawal to their registered GCash; you approve in the pending wallet queue after you send cash.

Why separate them? If commission mixed into float, tellers could spend earnings on more tickets without remitting, and your float liability becomes muddy. With separation, float is your prepaid sales credit; commission is the teller’s earnings ledger.

On Sell Ticket, the agent picks a category, opens the same style of popup (customer name optional, draw, numbers, amount), places the ticket, and can print an e-ticket for the walk-in. Insufficient float blocks the sale — which is how you cap exposure without babysitting every stake.

What happens when an agent ticket wins

This is the policy most desks care about. When settlement marks a player ticket won, the platform credits that player. When settlement marks an agent/teller ticket won, LottoPH records status won and the actual_win amount — but does not credit float or commission. You remain in control of the cash payout to the customer.

Use Admin → Wins / Payouts. Filter defaults to agent wins and shows ticket ID, agent name/email/ID, agent GCash, optional customer name, game and numbers, stake, win amount, and a note that you should contact the agent. That list is your payout work queue: call or message the teller, confirm the customer, send money the way your desk already operates, then move on.

Telegram settlement alerts also remind you that agent wins are not auto-credited, so ops chat and admin UI stay aligned.

Admin control surface

Beyond scraper and categories, the admin console now covers the operator day:

• Wallet — multi-rail payment settings, fraud limits, pending deposit/withdraw approvals (player and agent commission cashouts), Instant Deposit for float.
• Agents — create, GCash, ban/unban, float and commission balances, today’s sales snapshot.
• Wins / Payouts — agent vs player vs all wins.
• Themes + Branding — white-label site name, tagline, custom logo, plus theme presets.
• Alerts — Telegram bot token and chat ID; toggles for scrape results, win summaries, cutoff reminders, and all wallet transactions (deposit, withdraw, bet, win, commission, approve/reject).
• Tools — demo mode, license replace/deactivate, cache, statistics rebuild, export.
• Security — TOTP 2FA for admin accounts, with optional hard requirement via environment.

License gating is built in: unlicensed installs show an activation screen. Customers only paste a key — no license-server URLs in the UI. Lifetime updates are part of the RamerLabs Script offer.

Risk, demo, and go-live

Number controls let you block specific numbers or cap liability per number per draw so a hot combination cannot sink the desk. Demo mode shows a Live Demo posture on the landing page and blocks betting APIs — useful for sales calls — then flips to live copy and open betting when you disable it.

Printable e-tickets give walk-in customers something tangible without paper stubs from a separate POS. Cutoff reminders over Telegram warn your ops channel when betting is about to close for upcoming draws.

Who should buy LottoPH

LottoPH fits operators who want a branded Philippine lotto product, not a weekend PHP mashup. If you run online players plus street tellers, need GCash/Maya/bank intake, want commission cashouts under approval, and refuse to auto-credit agent jackpots into system balances without human follow-up, this workflow matches how many real desks already think — with software that keeps the ledger honest.

If you only need a public results scraper with no wallets, a lighter tool may suffice. If you need end-to-end betting, teller economics, branding, and ops alerts, LottoPH is aimed at you.

Getting started

1. Open the demo at pcso.ramerlabs.com and walk player → agent → admin.
2. Purchase on the LottoPH product page ($499 lifetime, free lifetime updates).
3. Deploy on your host, activate with your RamerLabs license key.
4. Set branding, payment rails, Telegram, create agents with GCash, fund float, then turn demo mode off when live.

Support: support@ramerlabs.com · Company: ramerlabs.com

Closing

Philippine lotto is public draws plus private cash discipline. LottoPH connects official PCSO results to player wallets and teller desks, separates float from commission, auto-credits player wins, and routes agent wins to an admin follow-up list instead of a silent wallet bump. Add multi-rail deposits, fraud limits, white-label branding, e-tickets, and Telegram for every money move, and you have an operator platform — not just another results table.

Try the demo. Then put your brand on it.

LottoPH — Official results. Instant bets. Teller desks. Operator control.
A product by RamerLabs