MemberPass Is Now Subscriby!

Hi everyone,

We’re thrilled to announce that MemberPass is officially rebranding to Subscriby.

Over the last few months the platform has evolved far beyond a simple “pass” or gateway. With our recent architectural rewrite—delivering a 50–60% increase in processing speed—and the rollout of our new AI and agentic workflow features, we are powering the next generation of top-tier Telegram communities. We wanted a brand name that reflects exactly who this platform is built for: elite creators and their most dedicated subscribers.

While our name and logo are changing, our core mission—and the underlying infrastructure that powers your community—remains exactly the same. Your payment gateway connections, active subscribers, and Telegram bots are fully intact and operating normally.

Because we manage active payment routing and API infrastructure for your businesses, ensuring a zero-downtime transition is our top priority. Here is exactly how we are handling the migration so your revenue never skips a beat.

⚠️ Read This First: Four Breaking Changes

Almost everything about this move is invisible to you. Four things are not, because they live in systems we do not control or in formats that had to change with the name. Each one has a workaround, and none of them affect your subscribers or your money.

1. API tokens must be re-minted

Personal access tokens changed prefix from mpt_ to sbt_. Existing tokens no longer authenticate—any script, server, or automation using one will start receiving 401 Unauthorized.

What to do: mint a replacement under Settings → API Tokens and paste it wherever the old one was used. Pick the same abilities; nothing else about the token model changed.

2. Webhook signature headers were renamed

If you verify our webhook signatures—and you should—three header names changed:

• MP-Signature → SB-Signature

• MP-Event-Id → SB-Event-Id

• MP-Event-Name → SB-Event-Name

The signing scheme is unchanged: t=<timestamp>,v1=<hmac-sha256> over "{timestamp}.{raw_body}", same 5-minute replay tolerance. Event Names, Event IDs, and payload bodies are all unchanged too. For most people this is a one-line edit in the verifier.

3. Gateway webhook URLs you configured yourself

We repointed Stripe and PayPal for you automatically. Five gateways store the webhook URL inside your own dashboard, so only you can change those:

• Skrill

• Paystack

• Razorpay

• CoinPayments

• CeyPay

What to do: replace the host app.memberpass.net with app.subscriby.net and leave the path exactly as it is. Until you do, the old domain keeps accepting those deliveries—we deliberately do not redirect webhook traffic, because gateways do not reliably follow redirects and a lost webhook is lost money.

4. The platform bot has a new username

Telegram does not allow a bot username to be changed, so the platform bot is now @TrySubscribyBot. The old bot still exists and still works—see the section below.

The 90-Day Domain Coexistence Period

We know that updating your social media bios, YouTube descriptions, and Zapier/n8n workflows takes time. You do not need to panic or update everything today.

• Your live links are safe. The memberpass.net domain remains fully active as a silent router for the next 90 days.

• Seamless redirects. Any customer who clicks an old MemberPass checkout or portal link is instantly and securely routed to the matching page on your new Subscriby URL, preserving the full path and any query parameters.

• API and webhooks keep firing. All existing webhook endpoints continue to deliver correctly throughout the transition window.

The old domain will be decommissioned on 12 November 2026. Before that date, please:

• Update the public-facing checkout links in your social bios and Linktrees to your new Subscriby URLs.

• Update any custom webhook URLs in your automation tools (Zapier, n8n, Make) and the five gateway dashboards listed above.

• Re-mint your API tokens and update your signature header names.

Moving Your Channels to the New Bot

This is the part we worked hardest to make painless. Both bots run side by side, and the platform knows about both. Nothing is duplicated—a subscriber is never approved twice and never receives two messages. For each of your channels and groups exactly one bot is responsible, and until you move it, that is the old bot.

To move one across:

• Open @TrySubscribyBot and send /start. It recognises you immediately—your account, projects, and plans are already there.

• Tap Reconnect a Channel or Reconnect a Group and pick a chat. Telegram adds the new bot as an administrator with exactly the same permissions the old one had.

• That’s it. Subscribers, invite links, and expiry handling carry over untouched, and the old bot goes quiet in that chat straight away.

You do not have to remove the old bot. Once a chat is reconnected the old bot stops acting there, so leaving it in place is harmless. One warning though: do not remove the old bot from a channel before reconnecting it—until then, it is the bot admitting and removing your subscribers.

Integrations

• Zapier: your existing Zaps keep working. Reconnect the account with a new sbt_ token when convenient.

• n8n: the package is now n8n-nodes-subscriby. Existing workflows on n8n-nodes-memberpass keep running—it stays published as a deprecated alias pointing at the new API—but move across when you can.

• MCP: the registry entry is now net.subscriby/mcp at https://mcp.subscriby.net. Reinstall from the new entry and paste in a new token.

• REST API: the base URL is now https://api.subscriby.net/v1.

One More Thing

Changing the session cookie name as part of this migration means everyone will be signed out once. Sign back in with the same credentials—nothing else about your account changes.

A full migration checklist, with copy-paste examples for the header rename and the bot walkthrough, lives at docs.subscriby.net/guide/reference/rebrand-migration.

Thank you for continuing to build your communities with us. We have completely optimized the backend engine, and Subscriby is built to help you scale faster than ever.

Get started at subscriby.net