02 / Context
Context
A large Telegram project: digital product catalogue, paid subscriptions, multiple access levels and 100,000+ users. Manual ops can’t scale — each product has its own terms, access rules and renewal paths.
It also needed crypto payments, acquisition tracking and automated reactions to unpaid orders, expired access or product exit. Acquisition ran through a network of bot mirrors.
03 / Product
Product
Telegram bot + backend + admin: digital catalogue, subscriptions, crypto payments and access in one loop. The user picks a product and term, pays in crypto and automatically gets materials or private Telegram spaces.
- showcases and product cards with their own prices and terms;
- several concurrent subscriptions per user;
- auto payment confirm → grant access → revoke on expiry;
- UTM / referrals / mirrors as entry points into one catalogue;
- funnels, unpaid-order follow-ups and renewal reminders;
- CRM: users, payments, subscriptions, segments, campaigns, analytics.
04 / How it works
How it works
Entry via campaign, referral or product link (including a mirror). The system keeps UTM and context, shows the showcase. Pick product and term → crypto payment details → tx confirm → purchase and access without a manager.
Backend polls expiry: before end — renewal reminders and offers; after — revoke per product rules. The bot shows active purchases and links into available spaces.
05 / Mirrors and scale
Mirrors and scale
A mirror network: several Telegram entry points into one catalogue and CRM. That scales acquisition and survives individual bot bans without losing products, subscriptions or payment history.
Architecture for 100,000+ users, a large catalogue and payment event volume: PostgreSQL as source of truth, Aiogram for async flows, product logic separated from the bot UI.
06 / Admin and analytics
Admin and analytics
The team runs catalogue, pricing, subscriptions, payments, access, funnels and campaigns from one panel. A user card holds Telegram data, UTM, orders, payments, active and ended access; admins can extend or revoke manually when needed.
End-to-end analytics ties source → view → order → payment → renewal. Revenue, AOV, product/channel split, unpaid orders and churn are visible.
07 / Outcome
Outcome
A scalable info-product sales loop: payment, grant and revoke run automatically; catalogue and messaging from admin; finance and marketing in one analytics surface instead of manual tx reconciliation.