How it works

A direct flow from Telegram audience to paid access.

This page matches the actual product flow: creator setup, Telegram verification, Stripe Checkout, webhook delivery, and automated access control.

Core model

Fans subscribe to access exclusive digital content and community updates.

Creators manage their own content and communities.

The platform takes a small service fee from creator earnings.

Step 01

Creator sets up the community

The creator connects Telegram, chooses the VIP channel, verifies bot permissions, and sets a subscription price.

Telegram identity is connected to the creator account.

The VIP channel is selected and the bot must be admin with invite and restrict permissions.

The creator gets a public landing page to share with fans.

Step 02

The fan opens the creator page, verifies Telegram identity on the web, and then enters Stripe Checkout.

The landing page shows the creator name, price, and join action.

Telegram verification happens before checkout starts.

Checkout metadata includes the creator and Telegram user identity needed for access delivery.

Step 03

Stripe Checkout creates the payment and Stripe Connect routes funds with a 10% platform fee and the remainder to the creator.

Fan payments are processed by the platform through Stripe Checkout.

Destination charges split the payment automatically.

Creators receive payouts through Stripe Express once onboarding is complete.

Step 04

After successful payment, the backend activates the subscription and creates a short-lived single-use invite link.

Webhook signatures are validated before events are processed.

The bot generates an invite link with a short expiry and one-member limit.

The user receives Telegram access without manual creator work.

Step 05

Renewals, failed payments, cancellations, and disputes update subscription state and VIP access automatically.

Successful renewals keep access active.

Failed payments, cancellations, and disputes trigger removal from the VIP channel.

A worker also removes expired members and logs access changes.