Shyamji Exchange — Admin Panel Business Requirements Document

The Admin Login screen is used by the Owner only. Admin, Super Master and Master each authenticate through their own agent URL rather than this shared login screen.

Features included

Login flow

Not included

Forgot Password link OTP Verification Two-Factor Authentication Remember Me

The Dashboard is the landing page after login. It gives an at-a-glance operational snapshot of balances, live exposure, downline composition, betting and casino activity, device mix, top performers and login activity — every widget respects an independently selectable date range.

2.1 Balance Summary & Live Events

The Live Events panel lists in-play matches with bets placed, filterable by Sport (default "All"); each card shows the platform's live P/L per selection (green/red) alongside the current back/lay price ladder. An empty state reads "No bets placed on live events yet."

2.2 User Management

Filterable by Day (default "Last 7 Days"); an arrow shortcut opens the full downline report.

2.3 Game Analytics

Filterable by Game (default "All") and Day (default "Last 7 Days").

2.4 Casino Analytics

Filterable by Day (default "Last 7 Days").

2.5 Business Snapshot

Date range business rules

• Day selector offers Last 7 Days, Today, and Custom Range.
• Custom Range reveals an mm/dd/yy → mm/dd/yy picker plus a Quick Select dropdown: Today, Yesterday, Last 7 days, Last 30 days, Last 90 days, This month.
• Every widget on the Dashboard recalculates independently for its own selected range.

2.6 Device Breakdown (Current In)

Donut chart of active sessions by device, with a Total Devices count and a Desktop / Mobile legend showing count and percentage share. Filterable by Day.

2.7 Top User

Combo bar + line chart plotting Bets Count (bars) against User Winning (line) per username, filterable by Category (e.g. Sports) and Day.

2.8 Top Categories

Bar chart of Bets Count by sport / category (tennis, soccer, cricket, casino), filterable by Day.

2.9 Login Summary

Filterable by Day (default "Last 7 Days").

2.10 Bonus Analytics

Filterable by Day. Ties into the Bonus Management module (§10).

Not included

Widget drag-reorder / customization Per-widget export Auto-refresh interval setting

A fixed left sidebar on the dark maroon canvas gives access to every module. Expandable groups (chevron icon) reveal their sub-items; the active item is highlighted with a red gradient pill.

Business rules

• Sidebar can be collapsed/expanded via the hamburger icon in the top bar.
• Expandable groups show a chevron and reveal sub-items inline, pushing the list below down.
• The active item / group is highlighted with the brand red gradient.
• Logout always sits at the bottom of the list, separated by a divider.

Downline Management is the core operational area: every level of the reseller hierarchy — Admin, Super Master, Master, and the End User — is listed, drilled into, and acted upon from here, with a Settlement view for fund transfers between adjacent levels.

4.1 Hierarchy Overview

• Clicking a level in the Downline submenu lists every account created directly under the currently logged-in node at that level.
• Clicking an account's username drills one level down — e.g. opening an Admin reveals the Super Masters created under that Admin, and so on down to Users.
• Settlement (§4.7) sits alongside the hierarchy levels for direct fund transfer between the current node and its immediate downline.

4.2 Admin / Super Master / Master Listing

Admin, Super Master and Master share one listing layout — only the role label, "+ Add [Role]" button and populated rows differ.

KPI strip

Table columns

Controls

• Search by [Role] name.
• Status filter (default "All").
• Date range filter (mm/dd/yy → mm/dd/yy).
• "+ Add Admin" / "+ Add Super Master" / "+ Add Master" button, top right.
• Refresh icon to reload the listing.
• Count-per-page selector (default 10) with Previous / Next pagination.

4.3 User Listing (End User)

The End User listing shares the same KPI strip and action set as §4.2, with a wider set of columns reflecting real-money player activity rather than downline roll-up figures.

Additional / differing columns

"Credit Reference", "Downline Bal.", "Total Bal.", "Upline P/L" are not shown here as a User has no further downline. The "+ Add User" button replaces "+ Add Admin/Master".

4.4 Row Action Pop-ups

Four pop-ups are reached from every listing row's action icons (§4.2 / §4.3) and behave identically at every hierarchy level — Admin, Super Master, Master, and direct End User.

4.4.1 Deposit

4.4.2 Withdraw

4.4.3 Sport Permission

Per-sport toggle list: Cricket, Soccer, Tennis, Grayhound, HorseRacing, Casino — each with an Active/Inactive status label and an on/off toggle, submitted together via the Submit button.

4.4.4 Change Status

Single-select radio group: Active, Inactive, Suspended, Bet Lock, confirmed via Submit.

Business rules

• Deposit / Withdraw require the account's Transaction Password, separate from the login password.
• Deposit / Withdraw amounts flow through the Downline Bal. / Total Bal. roll-up shown in the listings (§4.2 / §4.3).
• Sport Permission controls which sports a downline account (and its own downline) can accept bets on.
• Suspended and Bet Lock statuses block login (Module 01) and/or new bet placement respectively — exact distinction to be confirmed.
• These four pop-ups are identical whether triggered from an Admin/Super Master/Master row or directly from a User row.

4.5 Downline Profile Detail — Admin / Super Master / Master

Opening "Profile" on an Admin, Super Master or Master row opens a 3-tab detail view: Account Summary, Transaction History, Activity Log.

Account Summary

Shows the Account Details chain (Owner → the selected account, each with a role badge) and a Profile panel with Phone Number, Domain and a masked Password field with a Change Password action.

Transaction History

Export to Excel / PDF / CSV icons, a refresh icon, and a date range filter sit above the table.

Activity Log

4.6 End User Profile Detail

Opening "Profile" directly on an End User row expands the tab set to 5 tabs — Account Summary, Bet List, Betting Pnl, Account Statement, Activity Log — since a User is a real player rather than a reseller node.

Account Summary

Full Name, Email and Primary number show as "--" placeholders when not set by the user.

Bet List

Sports / Casino top-level toggle, a Sport filter (e.g. "Cricket"), export icons, refresh, date range filter and pagination.

Betting Pnl

• Rows group by Event, each showing total Stake and Player P/L; a row expands to its Market Name breakdown.
• Clicking a market name opens a modal listing every individual settled bet for that market (Bet ID, Status, Bet Taken/Settle, Event, Market, Type, Stake, P/L, IP).
• Search by event name; Sports / Casino toggle; export, refresh and date range controls.

Account Statement

Full ledger for this User, split into two sub-tabs: Sports Transaction (every bet-settlement entry — S. No., Date/Time, Type Debit/Credit, Remark naming the event/market, Credit, Debit, Balance) and D/W Transaction (deposits and withdrawals — S. No., Date/Time, Remark, Deposit, Withdraw, Balance, From/To). Both share Search, a Type filter (All/Debit/Credit), date range, export and pagination controls.

Activity Log

Same structure as the Downline Activity Log in §4.5: Date/Time, Login Status, IP Address, masked ISP / City-State-Country with a reveal icon.

4.7 Settlement

Purpose

Gives the logged-in account a single view of balance, exposure and P/L across its immediate downline, for reviewing and transferring funds without opening each profile individually.

Table columns

Controls

• Search User field to filter the list.
• "Bulk Transfer" button, top right, acts on all checked rows.
• Count-per-page selector with Previous / Next pagination.

Risk Management surfaces live platform-wide exposure per market, so the operator can spot lopsided books and lock or hedge a market before it settles. It drills from a cross-sport summary down to a single event's odds ladder, matched-bet list, and per-user liability.

5.1 Risk Management Summary

• Only markets currently carrying exposure are listed; the Amount column shows the platform's net liability for that market, negative in red.
• Sports tabs filter the list to that sport only; Cricket is the default.
• Clicking an Event / Market Name row opens the Event Risk Detail (§5.2) for that match.

5.2 Event Risk Detail — Market Ladder

Layout

Business rules

• Fancy / Session markets not yet opened for booking show locked back/lay pills.
• AD / SM / MA columns identify which downline level (Admin / Super Master / Master) placed each matched bet.
• A back-arrow returns to the Risk Management Summary (§5.1).

5.3 Full Bet List

Lists every matched bet for the market in focus: Runner, Size, Stake, Bettor, AD, SM, MA columns, with a Count-per-page selector and Previous / Next pagination.

5.4 User Book

• Platform Users / Hierarchy Users toggle switches the scope of the liability breakdown.
• Table lists each bettor against a column per runner, showing that user's net P/L on each outcome (negative in red, positive in green).

5.5 Market Book List

Clicking "Book" on an individual Session / Fancy line (from the market ladder, §5.2) opens this modal showing Runner Name and Profit/Loss for every possible outcome of that specific line — e.g. each run-count outcome for "50 Over Run ENG 2", with the platform's resulting P/L (green positive, amber/red negative) if that outcome settles.

Not included

Manual market lock/unlock from this screen Bulk risk alerts / thresholds

My Reports is the reporting hub: sports and casino bet lists, five profit/loss breakdowns (by downline, event, player, casino downline, casino players), and a multi-category Business Report. Every report shares a common pair of scope toggles — Platform Users (everyone under the logged-in node) and Hierarchy Users (grouped by the immediate downline chain, drillable) — plus a date range filter and Excel / PDF / CSV export icons.

6.1 Bet List

Table columns

Controls

• Search by username, Status filter, Sports filter, date range (defaults to the last 7 days).
• Platform Users / Hierarchy Users toggle, top right.
• Export to Excel / PDF / CSV, refresh, Count-per-page and Previous / Next pagination.

6.2 Casino Bet List

Table columns

Search by username, date range, Status filter, Platform Users / Hierarchy Users toggle, export and pagination — same pattern as Bet List.

6.3 P/L Report By Downline

Table columns

• Each row expands (chevron) to reveal the next level down — e.g. expanding "test9940" (Master) reveals "testuser" beneath it — with the same three P/L columns.
• Search by username, date range, export and pagination.

6.4 P/L Report By Event

Table columns

• Sports / Casino toggle, Game filter, search by event name, date range.
• Expanding an event reveals its Market Name breakdown (S.No, Market Name, Stake, Player/Downline/Upline P/L); clicking a market name opens the individual bet list for that market in a modal (Platform Users / Hierarchy Users, Status filter, date range, pagination).

6.5 P/L Report By Player

Table columns

Search by username, date range, export and pagination.

6.6 P/L Report By Casino Downline

Same layout and expand-to-next-level behaviour as P/L Report By Downline (§6.3) — Username, Player P/L, Downline P/L, Upline P/L — scoped to casino activity only.

6.7 P/L Report By Casino Players

Same layout as P/L Report By Player (§6.5) — Username / Parent (Hierarchy) / User P/L — scoped to casino activity only.

6.8 Business Report

Business Report groups platform activity into categories, selected via a Category dropdown: Deposit, Withdraw, Logged in User, Active User, SignUp, Idle Users. Each category keeps the Platform Users / Hierarchy Users toggle and date range filter; Hierarchy Users adds a Parent column throughout.

Deposit

Every deposit transaction made by a user in the selected date range, split into First Deposit (a user's very first deposit) and Refill Deposit (any deposit after that).

Withdraw

Every withdrawal transaction made by a user in the selected date range.

Logged in User

Every user who logged in during the selected date range, regardless of whether they transacted or bet.

Active User

An Active User is any user who performed a deposit, withdrawal, or placed a bet that has since settled, within the selected date range.

SignUp

Every new user registration completed within the selected date range.

Idle Users

Users who deposited at some point but have shown no deposit, withdrawal or settled-bet activity within the selected date range.

Business rules

• Category dropdown fully replaces the table's column set and heading (e.g. "Business Reports Deposit", "Business Reports Idle Users") — it is not a filter on one shared table.
• Platform Users / Hierarchy Users, date range, search, export and pagination controls persist across every category.

Not included (across §6.1–6.8)

Scheduled / emailed reports Saved custom report views Cross-report comparison charts

Event Management is where the operator turns matches on/off for betting, marks them Popular/Inplay, and tunes stake/rate limits per market — either per event (Bet Config) or platform-wide (Bet Config / Default Setting).

7.1 Events

Tabs & filters

Table columns

Market row expansion

Expanding an event's chevron reveals its individual markets (e.g. "Over/Under 2.5 Goals", "Match Odds", "Over/Under 1.5 Goals", "Over/Under 0.5 Goals"), each with its own on/off status toggle independent of the event-level Status column.

Bet Setting modal (per event)

This modal overrides the platform-wide Match Odds defaults (§7.2) for this specific event only.

Bet Suspended confirmation

Confirms before suspending betting on the named event: "Are you sure you want to suspend betting for the [Event Name]" — Cancel / Confirm.

Upcoming tab

Same table layout as InPlay/InActive Matches, scoped to fixtures that have not yet started.

Business rules

• InActive Matches / InPlay / Upcoming are mutually exclusive tabs based on match state; only one is active at a time.
• Deactivating an event's Status toggle blocks new bet placement on that event and all its markets.
• Deactivating a market's own toggle (inside the expanded row) blocks betting on that market only, leaving sibling markets and the event itself active.
• The bulk Activate/Deactivate control applies the selected action to every checked row at once.
• Per-event Bet Setting (via the modal) overrides the platform default for that market type (§7.2) only for that specific event.

7.2 Bet Config (Default Setting)

Bet Config sets the platform-wide default stake/rate limits applied to every event unless overridden per event (§7.1).

Sections

Business rules

• Each of the three market types (Match Odds, Bookmaker, Session) carries its own independent set of limits.
• These values are the fallback applied to newly created events; a per-event override (§7.1 Bet Setting modal) takes precedence once set.
• Bet Delay staggers odds acceptance to reduce timing-arbitrage risk on fast-moving markets.

Not included

Per-sport default overrides Casino-specific limits (see Module 08)

Casino Control turns casino inventory on/off at three levels of granularity — category, provider, and individual game — and lets the operator edit a game's metadata. Three tabs (Category Level / Provider Level / Game Control) switch between them; the tab selection persists as the operator drills in and back out.

8.1 Category Level

Every casino game category is listed as a tile with an external-link icon; clicking a tile drills into that category's game list.

Category drill-down

Flow

Business rules

• The back-arrow (‹) beside the category name returns to the Category Level tile grid.
• Toggling a game off inside a category hides it from end users platform-wide, independent of the Game Control listing (§8.3) — same underlying Status flag.
• Count-per-page selector and Previous/Next pagination apply within a category's game list.

8.2 Provider Level

Unlike Category Level, each provider row carries a Status toggle directly in the grid — a provider can be switched off without drilling in.

Provider drill-down

Flow

Business rules

• Switching a provider's top-level Status off disables every game from that provider platform-wide, regardless of each game's individual toggle.
• Drilling into a provider allows finer control — disabling specific games from that provider while the provider itself stays active.
• Providers with large catalogs (e.g. JDB Gaming) paginate their game list (Count selector, Previous/Next, numbered pages).

8.3 Game Control

Game Control is the flat, single-table view of the entire casino catalog — the same games as §8.1/§8.2, searchable and filterable in one place, with per-game edit access.

Controls

Table columns

Edit Game modal

Business rules

• Game Code and Provider are fixed at import time from the provider feed and cannot be edited here.
• Game Name, Category and Thumbnail Image can be corrected/localized without affecting the underlying provider mapping.
• Priority controls the game's sort order within its category/lobby placement — lower number surfaces first (exact ordering direction to be confirmed).
• The Status toggle in this table is the same underlying flag toggled from §8.1 (Category Level) and §8.2 (Provider Level) — changing it in one place is reflected in all three.

Not included

Bulk edit / bulk category reassignment New game creation from this screen (provider feed driven) Game-level RTP / demo mode configuration

Content Management controls the marketing surfaces shown to end users — site/app banners, promotional banners, alert notifications and the support contact block — via three tabs: Banner Management, Notification Management, Support Contact Management.

9.1 Banner Management

Table columns

Add Banner modal

Business rules

• A new banner is created Active by default; the row Action toggles it Inactive/Active without deleting it.
• Deleting a banner via the trash icon is expected to prompt a confirmation (per platform convention elsewhere in the admin) — to be confirmed once that dialog is shared.
• Banner Type and Platform together determine where the banner renders (e.g. MainBanner + WebBanner = top web banner; HomeBanner + AppBanner = app home screen banner).

9.2 Add Promotional Banner

Reached via "+ Add Promotional Banner" on the Banner Management tab; opens a full-page form rather than a modal.

9.3 Notification Management

Table columns

Add Notification modal

9.4 Support Contact Management

Two support channel cards — WhatsApp Support and Telegram Channel — each with a "Click to Connect" action that opens its configuration modal. Configured channels also appear in the table below.

Table columns

Configuration modals

Business rules

• Only one channel of each type (WhatsApp / Telegram) is expected to be marked Default/Active at a time — this is what end users see on the support surface.
• Both cards are always shown; the modal reached depends on which card's "Click to Connect" is clicked.

Bonus Management configures every promotional bonus a player can earn — Joining, Deposit and Referral — and controls how each bonus is locked, unlocked (turnover) and released. Policy Management lists and creates these bonus policies; Bonus Statement (§10.4) is the resulting player-level ledger.

10.1 Policy Management — Listing

Controls

Table columns

Business rules

• Only one bonus policy per category is typically Active at a time within an overlapping date range (visible in the reference data — the newest Active row supersedes older Inactive ones of the same category), though multiple can coexist if date ranges don't overlap.
• Deleting a policy is expected to prompt a confirmation — to be confirmed once that dialog is shared.

10.2 Create New Bonus

"Create" opens a category-specific form. Selecting the Category at the top reshapes the rest of the form — Joining and Deposit share most fields; Referral replaces the deposit-driven fields with referrer/referee-specific ones.

Fields common to all categories

Joining Bonus — form

Per your note: Joining Bonus requires signup followed by a first deposit to trigger.

Deposit Bonus — form

Referral Bonus — form

Per your note: Referral bonus can be configured to pay the referrer only, the referee only, or both, and can trigger either on signup or on the referred user's first deposit.

Dropdown reference

10.3 Turnover Formula & Multiplier — How Release Works

Worked example, as specified: a user deposits 1,000, and a 10% bonus policy is active. The user receives a 100 bonus, credited locked to their Bonus Wallet — it cannot be used for play or withdrawal until its turnover requirement is met.

Step 1 — Turnover Formula sets the required playthrough

Two formula options; the policy picks one. Multiplier (1, 3, 5, 10, 15, 20, 35, 40, 45, 50) is set per policy.

Until the user's cumulative qualifying stake reaches this target, the ₹100 stays locked — visible in the wallet, unusable for play or withdrawal.

Step 2 — Installments release the bonus in chunks as turnover is completed

Set Installments = 3 against the 300 target (Formula A) — each third of turnover unlocks a third of the bonus:

Same proportional logic applies under Formula B, just against its larger target (3,300 ÷ 3 installments = 1,100 turnover per release step).

Step 3 — Approval Method decides whether release is automatic

Business rules

• The bonus amount itself is always credited to the user's Bonus Wallet immediately and shown as locked; only the wagering requirement changes when it becomes usable.
• Turnover is accumulated from qualifying stakes only — Bet Type (ALL/Back/Lay), Minimum/Maximum Odd, and Select Categories (Sports/Casino) on the policy define which bets count toward turnover.
• Expire in days sets a deadline from the bonus grant — if turnover is not completed in time, the remaining locked bonus is expected to be forfeited (to be confirmed).
• Select Claim Period (Day / Month / time range) restricts when a user may claim this bonus in the first place, independent of the turnover/release mechanics above.

10.4 Bonus Statement

Bonus Statement is the player-level ledger of every bonus awarded platform-wide — this is where the turnover progress described in §10.3 is tracked per user, and where a Manual-approval installment (§10.3 Step 3) is actioned.

Controls

Table columns

View Installments

Expands the row into one line per installment: Installment No., Amount, Total Turnover Required (cumulative), Release Date, and Status (e.g. Expired) — this is the same installment breakdown described in §10.3 Step 2, and where a Manual-approval policy's release would be actioned once the installment's turnover is met.

Business rules

• A bonus reaching its Expire At date without completing turnover moves to Expired — remaining installments show Expired with no Release Date.
• Claimed indicates the bonus's full turnover was completed and released to the user.
• Approval Type filter distinguishes Auto-released rows from ones awaiting Manual admin approval per installment (§10.3 Step 3).

Banking Management is where player-initiated deposit and withdrawal requests are reviewed and approved/rejected, and where the platform's own receiving accounts (UPI / Bank Account) are configured.

11.1 Deposit/Withdraw Request

Deposit and Withdraw share one screen, switched by a top-level Deposit/Withdraw toggle; each further splits into All / UPI / Bank Account payment-method tabs, since the two methods carry different columns.

Deposit — All

Deposit — UPI

Deposit — Bank Account

Controls

Table columns — Deposit, All

The UPI tab replaces Account Type with a payment-proof Screenshot thumbnail; the Bank Account tab keeps Account Type and adds the Screenshot column alongside it.

Withdraw — All

Withdraw — UPI (empty)

Withdraw — Bank Account

Table columns — Withdraw

Business rules

• Approving a Deposit credits the player's balance for the requested amount; approving a Withdraw debits it and marks the transfer as sent.
• Rejecting either leaves the player's balance unaffected.
• Pending requests show "--" in Upd. At until an action is taken.
• Every approve/reject action is expected to write an entry into Account Statement (§13) and Business Report → Deposit/Withdraw (§6.8) — to be confirmed.
• UPI deposit/withdraw rows carry a Screenshot as payment proof; Bank Account rows instead carry full bank detail columns.

11.2 Manage Accounts

Manage Accounts configures the platform's own receiving accounts referenced as "QR1"/"QR2"/etc. in §11.1 — split into two tabs, Manage QR (UPI) and Manage Account (bank transfer).

Manage QR

Add QR modal

Manage Account

Add Bank Account modal

Business rules

• The "+ Add QR" / "+ Add ACCOUNT" button (top right) swaps label depending on the active tab.
• Min/Max Amount ranges are expected to route an incoming deposit request (§11.1) to the matching receiving account automatically — to be confirmed.
• Multiple QR/Account rows can be marked Default simultaneously, based on the reference listing (both rows checked ✓).

Export Report History is the central log of every export triggered elsewhere in the admin (Bet List, Casino Bet List, Account Statement, Activity Log, etc.) — tracking generation progress and hosting the download links so operators don't wait on-screen for large files.

Controls

Table columns

Business rules

• Every export button elsewhere in the admin (Bet List, Account Statement, Activity Log, etc., §4/§13/§14) writes an entry here rather than downloading directly, so large exports can generate asynchronously.
• The download Action is only clickable once Status reaches Completed; Pending/Failed rows have no active download.
• Failed exports are expected to offer a retry — to be confirmed once that state is shown.

Account Statement is the logged-in account's own full ledger, split into two tabs: Deposit/Withdraw (fund movements with the downline) and Game Transaction (bet-level wins/losses across every player under this account).

13.1 Deposit/Withdraw

Controls

Table columns

13.2 Game Transaction

Shares the same Context / Type / Search / date-range / export controls as §13.1. Table columns differ to reflect individual bet outcomes rather than fund transfers.

Table columns

Business rules

• Deposit/Withdraw and Game Transaction are mutually exclusive tabs; only one is shown at a time.
• Context filter values differ per tab context (Won/Lost/Rollback/Bet for Game Transaction vs. Deposit/Withdrawal-oriented tags for §13.1) — the reference screenshot shows one shared control; exact per-tab option set to be confirmed.
• "From/To" (§13.1) has no equivalent in Game Transaction since bets are single-player events, not transfers.

Activity Log (Owner) is the logged-in account's own login history — same structure as the Downline/End User Activity Log tabs (§4.5/§4.6), scoped to this account.

Table columns

Controls

• Date range filter (mm/dd/yy → mm/dd/yy).
• Export to Excel / PDF / CSV icons, refresh icon.
• Count-per-page selector with pagination.

Change Password lets the logged-in account update its own login password from a simple settings form.

Fields

Validation

• Current Password must match the account's existing password.
• New Password and Confirm Password must match.
• On success, the account continues its session with the new password (or is logged out and required to re-authenticate — to be confirmed).

Logout ends the current admin session, pinned as the last sidebar item (§3), and returns to the Login screen (Module 01).

• Clicking Logout immediately terminates the session and redirects to Login — no confirmation dialog.
• The session token is invalidated server-side, so back-navigation cannot restore the authenticated view.