Manage shop access, subscription plans and verified payments from your private admin workspace.
A clear record of every change.
Shop accounts stay separate.
Use your platform administrator account.
Only authorised platform administrators can use this workspace. Shop owner accounts cannot sign in here.
Loading shop records…
Shop access and recorded payments at a glance.
Review access, set individual pricing and record renewals.
Upcoming renewals use the later paid or trial end plus grace, from now through the next 7 days. Free, suspended and expired shops are excluded; blocked shops have their own filter.
Set standard prices. Individual shops can have an agreed price.
Choose the default access rules for shop billing.
An expired shop may continue using its cached entitlement while offline until its recorded expiry and grace period end. Refresh after changes to distribute the latest policy.
Check server readiness and send a test to one selected shop.
This sends a generic test message only to current registered devices for the chosen shop. It does not change a subscription or payment.
“Accepted” means Firebase accepted a send request. It does not prove the phone displayed it or that a person read it.
These optional alerts go to the shop owner's app. They never send automatic messages to customers. A share activity event means requested or opened; it does not prove a customer message was sent, delivered or read.
Both alerts start off in a new installation. The saved policy, Firebase readiness, eligible devices and app permissions determine whether an owner can receive an alert. This policy is independent of subscriptions, payments and referral rules.
A requested share, opened reminder hand-off or scheduled due alert is activity evidence only. It is never proof of a customer message sent or delivered, an owner reading an alert, or a payment being received. No private customer message contents are shown.
Change your password after the first sign in.
Changing the password signs out all administrator sessions. Shop accounts and subscriptions keep their existing settings.
Send email verification and recovery codes from an approved SMTP server.
The registered shop image and each amount-specific bill QR are separate.
Only persisted outcomes are shown. Successful, failed and refunded provider outcomes are unavailable until a supported provider supplies verified evidence.
Choose a shop to inspect its registered payment profile.
Registered shop owners are referral participants. Retail credit customers are separate.
Date filters use Asia/Kolkata. The through date includes that complete day. Subscription analytics uses these report filters except owner explorer search. Search affects only the owner list; it does not change report metrics. Receipt and reward record pages have their own explicitly labelled filters.
Report scope loads with these metrics. Owner explorer search affects the owner list only.
Owner explorer search affects this list only.
Direct APK subscriptions renew manually. This page never charges a bank account or creates automatic recurring billing.
Saving a pending receipt does not activate paid access or award credit. Review the persisted receipt, confirm money received, and explicitly verify it below.
This receipt list filters by shop and payment state. Date, plan and referral report filters apply on the analytics pages. A confirmed receipt has verification evidence marked owner_verified; that evidence is separate from later refund status.
Provider refunds return money through the provider. Pending or unknown requests are not confirmation of money returned. Use the saved request ID to recheck after a refresh.
Every balance comes from persisted ledger entries. No cash withdrawals, transfers or automatic subscription-price deductions.
Credit liabilities and recovery holds are current server balances for the selected owner, not credits earned within a date window. The record list filters only by owner and reward state.
An adjustment creates a new ledger entry. It never edits or deletes the original reward history.
Collected receipts, paid entitlement and referral credit are distinct measures. Report filters are shared with Referrals; owner explorer search affects the owner list only.
Report scope loads with these metrics and tables. Owner explorer search is excluded.
Prepare PhonePe and Google Play for the app subscription. Shop customer UPI payments remain separate.
New installations start with checkout and both providers off. These controls show the saved server policy; changes require review and an operator reason. Prices and qualifying referral plans stay under your existing monthly plan controls.
PhonePe setup · Applicable PhonePe pricing · Play setup requirements · Hosting terms
Loads the saved rules and monthly plans. This checklist never changes them.
Referral credit is non-cash service credit under the saved qualifying-payment rules. No account, plan mapping or checkout flag automatically enables the referral program, creates a reward or backfills historical payments.
Changes apply prospectively. Historical payments and reward calculations keep their recorded rule snapshots.
Google Play purchasing is not configured for this direct APK. Owner verification is a manual receipt review, not provider verification. Credits cannot be applied to a Play subscription price.
These calendar-month plans are separate from legacy day-duration plans. Changing a monthly plan does not alter recorded receipts or existing custom-price controls.