MemberPass

How MemberPass Works

End-to-end walkthrough of the MemberPass flow — creator setup, subscriber signup, automated member management, and the money path.

By the end of this page, you'll understand how a MemberPass-powered membership goes from empty project to paying, automated community — and who does what along the way.

The flow, at a glance

  1. Creator sets up a project, plans, payment methods, and connects a Telegram bot.
  2. Subscriber discovers the project via a bot deep-link or portal page, picks a plan, pays.
  3. MemberPass receives the payment confirmation, creates a subscription, and instructs the bot to grant access.
  4. Subscriber taps a unique invite link and joins the paid Telegram destinations.
  5. MemberPass keeps everyone honest — renews on schedule, removes expired members, and keeps the creator's dashboard in sync.

The subscriber never sees MemberPass as a brand. They see your bot, your channel, your plans. MemberPass is the plumbing.

Creator-side setup (one time)

Register as a creator by chatting with @MemberPassAppBot on Telegram. The bot sends you to a signup form that's pre-filled with your Telegram identity. See Creating an account.

Activate a creator plan (Free / Starter / Growth) and add a payment method on file. Even the Free plan requires a card because per-transaction fees apply. See Activate your subscription.

Create a project — name, handle (for the portal URL), banner, and description. See Creating a project.

Create a Telegram bot via @BotFather and paste its token into MemberPass. See Connect your bot.

Define resources — link your private Telegram channels, groups, or supergroups to the project so MemberPass knows what it's protecting. See Resources.

Enable payment methods — pick from nine providers (Stripe, PayPal, Skrill, CoinPayments, Paystack, Razorpay, CeyPay, Telegram Stars, Access Codes). See Payment methods.

Build subscription plans — pricing tier + billing cycle + trial rules + which resources each plan unlocks. See Subscription plans.

Share your bot or portal URL on social media, in your existing channels, or via direct deep-links. See Sharing your project.

Once that's done (typically a single afternoon), subscribers can start joining on their own.

Subscriber-side flow (recurring)

Subscriber taps your bot link (e.g. t.me/YourBotName) or visits your portal page (e.g. my.memberpass.net/your-handle).

On the bot: they see your welcome message, agree to terms, and pick a plan from an interactive list. On the portal: they sign in (Telegram OAuth, Google, or email magic link), browse plan cards, and click Subscribe Now.

They pick a payment method from those you've enabled. The portal shows web-based providers; the bot also shows Telegram Stars.

The payment provider takes over — subscriber enters card details (Stripe, PayPal, etc.), or confirms an in-app purchase (Telegram Stars), or sends crypto (CoinPayments, CeyPay).

On payment confirmation, MemberPass's webhook receives the event, creates a subscription record, and triggers the bot to generate unique single-use invite links for every Telegram resource the plan unlocks.

The bot sends a "Your Subscription Resources" message with Join buttons. The subscriber taps each button and is automatically added to the destination.

From the subscriber's perspective, the whole flow is a few taps and a payment — typically under a minute. Behind the scenes, MemberPass is orchestrating webhooks, invite links, membership grants, and audit logging.

The ongoing lifecycle

Once a subscriber is inside, here's what happens over time.

Renewals

For recurring plans, the payment provider charges their saved method at each cycle and MemberPass updates the subscription's renewal dates automatically. No manual work on your end.

Failed payments

If a renewal charge fails, the provider enters its own retry policy. During retries the subscription's status is Past Due and access continues. If retries exhaust, status flips to Unpaid then Expired, and the bot removes the subscriber from your Telegram resources.

Cancellations

When a subscriber taps Cancel (on the portal or in the bot), a confirmation job queues. Access continues until the cycle-end date, after which the bot removes them and flips the status to Expired.

Unauthorised joins

If someone sneaks into a private Telegram resource without a valid subscription — for example through a leaked invite link — MemberPass's periodic consistency check detects them and removes them.

Re-subscribes

A churned member can subscribe again through the normal flow anytime. It becomes a fresh subscription record; their history on your project (including the previous churn) stays visible for audit.

The money path

Subscribers pay directly to your payment provider account — Stripe, PayPal, Razorpay, etc. MemberPass doesn't hold your revenue.

Where funds flow

Your provider deposits the funds into your account per its own payout schedule. Rough expectations: Stripe is typically 2–7 days; PayPal is usually faster; crypto providers settle nearly instantly but are one-way (no automatic refund path).

How MemberPass is paid

MemberPass's cut — the transaction fee — is collected in one of two ways depending on your provider:

  • Deducted at the time of charge for Stripe (Direct Charge model), so you receive net proceeds with the fee already taken.
  • Accumulated and invoiced monthly (or when a usage threshold is hit) for every other provider.

Your creator-plan subscription is billed separately by MemberPass through Stripe.

What MemberPass does automatically

The boring-but-critical operational work:

  • Registers and maintains Telegram webhooks so the bot hears every event in real time.
  • Generates unique, single-use invite links per subscriber per resource.
  • Monitors for unauthorised members and removes them on a periodic sweep.
  • Unbans previously-kicked subscribers cleanly before re-inviting them (so Telegram doesn't throw errors).
  • Keeps payment provider product/price catalogues in sync when you change plans.
  • Sends subscriber-facing notifications — trial-ending reminders, renewal-failure notices, and more — via the bot.
  • Tracks every lifecycle event in the per-subscription activity timeline for audit and support.

What you still do manually

  • Content — obviously. Create the posts, host the calls, answer the questions.
  • Marketing — share the bot link, run ads, engage your audience.
  • Moderation — Telegram's built-in admin tools (delete messages, ban bad actors via /ban) are still your job.
  • Refunds — issue via the payment provider when needed. MemberPass reflects the status; the decision and execution are yours.
  • Support — subscribers ask you questions; you answer them. MemberPass is infrastructure, not a customer-service layer.

Ready to build?

On this page