👋 Welcome back, Admin
Manage products, keys, reseller services and settings from one place.
📦
—Mapped Products🔑
—Key / Delivery Logs👥
—Members🤝
—Resellers⚡ Quick Actions
🛡️ Connection Status
Checking API…
Counts are populated only where the deployed API exposes a supported endpoint.
🕘 Recent Activity
No activity loaded yet.
📢 Broadcast to All Users
Send a text message and optional photo notification to all users in the bot user list.
📝 Message Composer
No photo selected.
⚠️ Review the message before sending. Broadcast sends a notification to all users; delivery may fail for users who blocked the bot.
📊 Last Broadcast Result
No broadcast sent from this panel yet.
📦 Manage Product
Configure multiple durations, user prices, reseller prices, and supplier mappings for each product.
➕ Add Product
⏱️ Duration & Pricing
Each plan has separate Bot Duration and Remote Duration. Bot Duration is shown in the bot menu and used for pricing. Remote PID and Remote Duration are sent to the supplier API exactly as entered.
🧾 Product List
| Product | Remote PID | Bot Duration | Remote Duration | 👤 User Price | 🤝 Reseller Price | Status | Action |
|---|---|---|---|---|---|---|---|
| Login and refresh products. | |||||||
🔑 Live Key Delivery Logs
Review delivery records from the API.
Press Refresh Logs. If endpoint is not implemented by the Worker, it will show the API response.
🗃️ ID Stock
Inventory / stock overview.
Stock data requires a supported API endpoint.
➕ Add Stock Record
🔗 Product Links
Active products and their channel links. Copy or open each link.
Loading active product links…
🎟️ Manage Keys
Live key delivery overview, customer purchase history and product sales.
🔑 Key Delivery Overview
Loading live key analytics…
🔑 Live Customer Key Purchase History
Total: — Orders
| USER (ID) | PRODUCT & PLAN | PRICE PAID | DELIVERED KEY | DATE & TIME |
|---|---|---|---|---|
| Loading purchase history… | ||||
📈 Today's Key Sales by Product
Total: — keys · ₹—
| PRODUCT | KEYS SOLD TODAY | AMOUNT |
|---|---|---|
| Loading today's sales… | ||
📦 Lifetime Orders By Product
| PRODUCT | STATUS | TOTAL KEYS SOLD | ACTION |
|---|---|---|---|
| Loading lifetime orders… | |||
🛡️ Reseller API Authentication
Manage API authentication configuration.
Configuration status is available from supported Worker routes only. Secrets must never be displayed in the browser.
🔐 Update API Credentials
Credentials are write-only. Leave secret fields blank to keep existing values.
💳 UPI Payment Setup
Live gateway status and customer deposit review.
💰 Total Deposits
—
⏳ Pending Review
—
✅ Approved Today
₹—
🛡️ Gateway
—
Loading gateway status…🔐 Active Payment Gateway (Read Only)
Loading current Store & Settings gateway configuration…
Gateway configuration is read-only here. Change it only in Store & Settings. API keys are never displayed.
👤 Live Customer Deposit History
Press Refresh Deposits to load live records.
🏪 Store Settings
Public store appearance and contact settings.
Store settings need a supported Worker route.
🛠️ Store Details
👥 Members & Wallets
All discovered users, live wallet balances, and controlled balance actions.
Loading members…
💸 Wallet Adjustment
Enter a positive amount to add or a negative amount to remove. Confirmation is required before saving.
No adjustment applied.
🤝 Resellers
Reseller accounts and status.
Reseller management requires a supported Worker route.
➕ Add Reseller
⚙️ Bot & Supplier Settings
Secrets are write-only and are not returned in plaintext. FamGateway credentials are used by the API only; never put them in Bot environment/code.
🔐 Protected Settings
⚠️ Changing Telegram bot token also requires updating BOT_TOKEN in the bot runtime and restarting/redeploying the bot. Worker settings alone cannot restart an external bot container.
🧾 Purchase History
Orders and transaction records.
Purchase history requires a supported Worker route.
👤 My Profile
Current admin session.
🔐 Session Information
Authenticated admin session.
📡 API Status
Check health and endpoint availability.
Tap Test Connection.
🧭 API Route Notes
This page can call only routes implemented in the deployed Worker. If a section says “route not found”, the Worker backend must implement that route before the feature can persist data. No fake success is shown.