ProfileVerify KYCRankDepositWithdrawTransactionsBetting HistoryMessagesResponsible GamingCompliance SafetyImplementation StatusAdmin ReadinessAbout
FAQCustomer SupportGame RulesTermsPrivacyAML PolicyKYC PolicyPayment PolicyDispute Policy
HomeGamesSlotsPokerSocialLeaderboard
EMTREE.LIVE
Operations

Admin Readiness

A non-live operations dashboard blueprint for compliance reviews, wallet risk, AML alerts, support cases, game incidents, reports, and audited admin actions.

ScopePH / PHP
Access21+ gated
SafetyAudit logged
KYC Cases0

Manual review queue ready

Withdrawals0

Risk queue ready

AML Alerts0

Monitoring hooks planned

Build Items28/102

Implementation tracker

Compliance

KYC Review

Manual review for identity mismatch, rejected documents, duplicate accounts, and underage risk.

Payments

Withdrawal Review

Risk queue for name mismatch, new payout method, large amount, unusual velocity, or support flags.

Risk

Device And AML

VPN/proxy checks, impossible travel, duplicate accounts, unusual velocity, and suspicious activity route to review.

Operations

Game Incidents

Round lookup, seed proof, settlement status, reconnect issues, and dispute investigation.

Admin Queues

QueueVolumePriorityOwner
KYC Review0HighCompliance
Withdrawal Risk0HighPayments
AML Alerts0CriticalAML Officer
Device Risk0HighSecurity
Payment Owner Match0HighPayments
Support Tickets0MediumSupport
Game Incidents0HighOperations

Provider And Launch Setup

BlockerReasonOwnerNext Step
Finish Vercel environment variables for production.env.example lists required keys.FounderConfirm Production and Preview values in Vercel project settings.
Keep GitHub connected to Vercel auto-deployRepo can be pushed, Vercel connection lives in dashboard.FounderConfirm main branch deploys automatically in Vercel.
Keep DNS ownership clearGoDaddy registrar and Vercel DNS model documented in setup docs.FounderDo not edit records in GoDaddy while Vercel nameservers own DNS.
Maintain staging or preview deployment before production changesVercel Preview environment can be used.Founder / EngineeringTest major changes on Vercel Preview before promoting production.
Run all required Supabase SQL filessupabase/schema.sql, auth-account-schema.sql, and profile-storage-schema.sql exist.Founder / EngineeringRun updated SQL in Supabase SQL Editor and save migration history.
Legal review before real-money launchReadiness blocks real-money launch.Founder / LegalHire qualified PH gaming counsel before accepting real funds.
Official payment provider integration laterReal payment APIs require merchant/legal approval.Founder / PaymentsSecure Maya/GCash approved gambling merchant route.
Vercel and Supabase env vars complete.env.example documents expected keys.Founder / EngineeringSet values in Vercel and local .env.local without committing secrets.
Supabase URL redirects correctNEXT_PUBLIC_AUTH_REDIRECT_URL and NEXT_PUBLIC_SITE_URL are documented.FounderSet Supabase Auth URL and redirect URLs to emtree.live plus local dev.
Database schema applied and RLS testedSQL files are ready.Founder / EngineeringRun SQL in Supabase and test as multiple users.
Register/login/verify/reset/support/profile upload testedEmail and storage depend on Resend/Supabase setup.Founder / EngineeringRun end-to-end test after external setup is verified.
Test signup with fresh email and confirm 6-digit verification arrivesRequires live production email test after deploy.Founder / EngineeringUse a never-before-used email after redeploy.
Confirm login after verification and forgot-password emailDepends on email delivery and Supabase redirects.Founder / EngineeringTest both local and production URLs.
Run Supabase SQL schemasUpdated SQL files are in repo.Founder / EngineeringRun all schema files in Supabase SQL Editor.
Test profile avatar uploadRequires storage bucket/policies applied.EngineeringRun storage SQL, then upload a small PNG/JPG.

Feature Quality Self Review

FeatureImplementedSelf CheckCompetitor CheckNext Improvement
Verify emtree.live domain in Resend.Marked as complete because the user confirmed the Resend domain is done.Is it made properly? The app uses Resend, but production email still needs live signup/reset testing.Competitors feel more reliable because email flows are invisible when they work; EMTREE must prove this through fresh production tests.Run fresh-email signup and password reset tests after each auth change.
Add backend foundations for missing roadmap features.Added feature-expansion-schema.sql with admin roles, notifications, support lifecycle, wallet review, risk, social, rank, and future-game tables.Is it made properly? The schema is idempotent and RLS-first, but it must be run in Supabase and tested with real users.Top operators win by making account, wallet, support, and risk state coherent across every page; this schema is the first coherent layer.Convert SQL into tracked migrations and add RLS tests.
Wire deposit and withdrawal requests to backend.Added server-side wallet intent API that records payment intents and review notifications without processing real money.Is it made properly? It blocks live processing unless KYC/wallet gates pass and keeps real payment rails disabled.Competitors show wallet status and history quickly; EMTREE now has a visible wallet history panel but still needs provider-grade processing.Add provider webhooks only after legal/payment approval.
Add friend, block, report, invite, and presence backend primitives.Added social API and database tables for friend requests, blocks, reports, table invites, and presence.Is it made properly? It is moderation-first and avoids voice/game money coupling.The social angle can beat ordinary casino lobbies, but only if friend tables, reports, and voice permissions feel native.Add real-time subscriptions and admin moderation UI.
Prepare future games for server-authoritative implementation.Added game algorithm versions, player nonces, fairness verification API, and game-round event schema.Is it made properly? It creates the contract, but real games must move RNG and settlement fully server-side.Provably fair competitors earn trust by showing proof without making it feel technical; EMTREE has the checker, but needs round-linked proof UI.Build server round-create/lock/settle APIs before any real-money game.
Redesign generic pages beyond one large banner.Page-specific hero context, wallet/support/admin/social/fairness panels, and professional operational cards are now wired into key pages.Is it made properly? The pages now carry useful state and actions, but a full mobile visual QA pass is still needed.Competitors often win on density and speed; EMTREE is moving from static banners toward dense account/action surfaces.Continue replacing static tables with live data panels and stronger mobile interactions.
Build protected admin queue visibility.Added /api/admin/queues and an admin queue panel for KYC, payments, risk, support, reports, closures, email changes, and monitoring.Is it done? Visibility is scaffolded; approve/reject/restrict actions are not live yet because money/admin decisions require role permissions and audit reasons.Mature operators have internal tooling that keeps compliance work fast; this starts that direction but needs decision workflows.Add role-scoped admin actions, 2FA, dual approval for money movement, and immutable action logs.
Make customer support trackable.Support tickets can now be fetched for logged-in users and shown on the support page.Is it done? Intake and history exist; reply/status update tools for admins are still needed.Competitors often hide support behind chat widgets; EMTREE can feel more trustworthy by showing ticket history and references clearly.Add admin replies, status changes, attachment review, and SLA labels.
Add email change and account closure flows.Security settings now include email change request, email token confirmation, and account closure request.Is it done? The flow is present, but production email and Supabase service-role settings must be verified.Competitors make sensitive account controls findable but gated; EMTREE now exposes them in the right account area.Add cancellation, support escalation, and clearer pending-request history.
Follow the brand guide.The UI continues using Norwester, Atkinson Hyperlegible, navy/green/off-white/gold, and restrained sportsbook-style surfaces.Is it done? The key pages are aligned, but every legacy page needs a final typography and spacing scan.The brand guide pushes EMTREE toward premium sportsbook clarity, which differentiates it from loud casino clutter.Keep gold rare, reduce decorative noise, and make every account page feel operational and fast.

Roadmap Execution Tracker

PhaseItemStatusNext Step
Phase 1Public home pageDoneHome, lobby, rank strip, games, slots, payment rail
Phase 1Age gate and jurisdiction pre-checkScaffolded21+ and PH controls surfaced; backend enforcement next
Phase 1Responsible play hubDoneLimits, cool-off, self-exclusion, and safety copy
Phase 1Account shellDoneLogin, register, reset, profile, KYC, wallet shell
Phase 1Support and policy pagesDoneSupport form, FAQ, terms, privacy, game rules
Phase 1Audit log model designDoneSupabase schema includes audit_events
Phase 2KYC provider integrationNot ConnectedProvider contract and upload flow required
Phase 2Geolocation verificationNot ConnectedProvider API needed before live money
Phase 2Session limits and cooling-off controlsSchema Readyresponsible_limits table defined
Phase 2AML transaction monitoring hooksSchema Readyaml_flags and payment risk fields defined
Phase 2Immutable event loggingSchema Readyaudit_events table defined
Phase 2Admin review workflowsScaffoldedAdmin queues, cases, and review pages ready for wiring
Phase 3Licensed game provider integrationNot ConnectedGame/provider approval required
Phase 3Wallet ledger with double-entry accountingSchema Readywallets and ledger_entries defined
Phase 3Bonus rules enginePlannedNeeds bonus tables and wagering policy approval
Phase 3Wagering requirements trackingPlannedNeeds bonus/wager ledger once bonuses are approved
Phase 3Withdrawal risk reviewSchema Readypayment_intents, aml_flags, admin_cases defined
Phase 3Tax and reporting exportsPlannedNeeds legal/tax rules and report formats
Phase 4Fraud dashboardsPlannedUse AML, device, payment, and support events
Phase 4Compliance reportingPlannedRequires approved operating procedures
Phase 4Customer support toolingIn BuildResend support form and support_tickets schema ready
Phase 4Incident response playbooksDocumentedDocs folder contains planning materials
Phase 4Automated policy checks before launchScaffoldedReadiness API blocks real-money launch

Launch Blockers

BlockerStatusRequired BeforeOwner
PAGCOR/legal route not approvedOpenReal moneyFounder / Legal / Ops
Maya/GCash gambling merchant approval not completeOpenReal moneyFounder / Legal / Ops
KYC provider and manual review workflow not liveOpenReal moneyFounder / Legal / Ops
AML monitoring and reporting workflow not liveOpenReal moneyFounder / Legal / Ops
Device/VPN/proxy risk scoring not liveOpenReal moneyFounder / Legal / Ops
Payment-owner match workflow for Maya/GCash not approvedOpenReal moneyFounder / Legal / Ops
Terms, privacy, AML, KYC, payment, dispute, and underage policies not counsel-approvedOpenReal moneyFounder / Legal / Ops
Game RNG/math/certification not completeOpenReal moneyFounder / Legal / Ops
Real-money launch switch remains disabledOpenReal moneyFounder / Legal / Ops
01

Review

Admin opens a KYC, withdrawal, support, AML, or game incident case.

02

Evidence

System shows user, device, payment, ledger, game, support, and risk references.

03

Decision

Approve, reject, hold, escalate, restrict, or request more information.

04

Audit

Every admin action stores actor, reason, timestamp, before/after state, and audit hash.

Launch Gate

Admin actions need controls

Real operations require role permissions, two-factor admin login, dual approval for money changes, immutable logs, and regular audit exports.

EMTREE.LIVEKeep it fun. Real-money features require licensing, KYC, AML, geolocation, and responsible-play controls before launch.