One authority for commerce
Prices, balances and access rights are decided by one backend rather than duplicated in the website and bot, preventing channel-specific drift.
Case 02 · Multi-channel paid reports
Notes of a Numerologist: one commerce engine across web and Telegram.
A production platform for expert-led personalized products: public calculations, user accounts, payment entitlements, durable report jobs and delivery through both a website and Telegram.
02customer channels
03payment paths
37schema revisions
Technical scope: website and Telegram, with YooKassa, shared wallet balance and Telegram Stars payment paths. Schema revision count reflects the current documented platform state.
01 · The challenge
Expert businesses often stitch together a landing page, messenger, payment links and manually produced files. Pricing, access rights, retries and customer support then drift between channels.
The engineering objective was to make the backend authoritative: one product catalog, one entitlement model and one durable report pipeline, while customers can enter from the web or Telegram.
02 · Engineering scope
What the system had to own.
Public calculation modules and mobile-first product discovery
Phone-first authentication and user cabinet
Orders, purchases, wallet balance and owner-scoped access
YooKassa website checkout and verified webhook boundaries
Telegram bot, Stars and shared-balance checkout
Versioned calculation sources and backend pricing authority
Durable report workers, artifact storage and PDF delivery
Booking, admin pricing and operational recovery workflows
03 · Product surfaces
Real screens from the working product.
04 · Product system
One operational chain, explicit boundaries.
- 01Website or Telegram
- 02Backend product catalog
- 03Order and payment boundary
- 04Entitlement and wallet
- 05Calculation and report job
- 06PDF and account delivery
05 · Hard decisions
Where product quality became an engineering problem.
Idempotent payment boundaries
Provider requests, webhook handling and fulfillment are designed so retries cannot silently create duplicate value or deliver the wrong order.
Fenced report workers
Calculation and report workers publish results only while holding the current lease, protecting completed customer artifacts from stale attempts.
06 · Evidence
What can be inspected.
- Live responsive website with public calculation catalog
- Telegram bot integrated with the same backend catalog
- Versioned calculation and content truth sources
- Payment, balance, entitlement and report delivery contracts
- Admin-editable products, prices and booking workflows
Current stage
The technical platform, database and workers are live. Commercial checkout remains gated where seller details, legal document versions or operational ownership require final approval.