MemberPass is now Subscriby
What the rebrand changes, what keeps working untouched, and the short checklist of things you need to update yourself.
MemberPass is now Subscriby. Same platform, same team, same infrastructure — new name, new logo, and a new home at subscriby.net.
Your projects, subscribers, payment connections and payout history are all exactly where you left them. Nothing was migrated, rebuilt or reset. This page is only about the handful of places where the old name is baked into something on your side, and what you need to do about each.
The old domain stops working on 12 November 2026. Until then every old link keeps resolving, so nothing breaks while you work through the checklist below. After that date, links and webhook URLs still pointing at the old domain will fail.
What keeps working with no action from you
- Every existing link. Old checkout and portal links redirect to the matching page on the new domain, preserving the path and query string.
- Your Stripe, PayPal and other gateway connections. Untouched.
- Active subscriptions and subscribers. Untouched. Nobody is re-charged, nobody loses access.
- PayPal webhooks. Re-registered automatically against the new domain.
- Your Telegram project bots. Their webhooks were repointed for you.
- Your channels and groups. They keep working through the transition — see the bot section below.
Breaking changes that need your attention
These are the parts that cannot be redirected, because they live in systems we do not control or in formats that had to change with the name.
API tokens must be re-minted
Token prefixes changed from mpt_ to sbt_. Existing tokens no longer
authenticate. Any script, server or automation using one will start getting
401 Unauthorized.
Mint a replacement in the dashboard under Settings → API Tokens, then paste it wherever the old one was used. Scopes and abilities work exactly as before, so pick the same ones.
Webhook signature headers were renamed
If you verify our webhook signatures — and you should — the header names changed:
| Old header | New header |
|---|---|
MP-Signature | SB-Signature |
MP-Event-Id | SB-Event-Id |
MP-Event-Name | SB-Event-Name |
The signing scheme itself is unchanged: t=<timestamp>,v1=<hmac-sha256> over "{timestamp}.{raw_body}", with the same 5-minute replay tolerance. Only the header names moved, so this is usually a one-line change in your verifier.
The payload body, Event Names and Event IDs are all unchanged. Your handlers do not need rewriting — only the header lookup and the token.
API and webhook base URLs
Old: https://api.memberpass.net/v1
New: https://api.subscriby.net/v1
Old: https://mcp.memberpass.net
New: https://mcp.subscriby.net
Update the URL in your Claude Desktop, ChatGPT Desktop, Cursor or VS Code MCP
config, and paste in a new sbt_ token.
Endpoints you registered with us are unaffected — we call your URL, and that has not changed.
What does need changing is any gateway webhook URL you configured yourself in your own gateway dashboard. See the checklist below.
The n8n node was republished
The n8n package is now n8n-nodes-subscriby, with renamed node types and a renamed credential. Existing workflows built on the old package keep running for now: n8n-nodes-memberpass stays published as a deprecated alias pointing at the new API.
To move across, install n8n-nodes-subscriby, re-create the credential with a new sbt_ token, and swap the nodes in your workflows. Your trigger webhook URLs are re-registered by n8n when you save the workflow.
The MCP registry entry moved
net.memberpass/mcp is deprecated in favour of net.subscriby/mcp. If you installed the server from the registry, reinstall from the new entry.
Your checklist
Mint a new API token
Settings → API Tokens. Replace the old mpt_ token everywhere it is used: scripts, servers, Zapier, n8n, Make, MCP clients.
Update your webhook verifier
Change MP-Signature to SB-Signature (and the two MP-Event-* headers if you read them). Nothing else about verification changes.
Update gateway webhook URLs you configured yourself
Stripe and PayPal were handled for you. These gateways store the URL inside your dashboard, so only you can change them:
- Skrill
- Paystack
- Razorpay
- CoinPayments
- CeyPay
Replace the host app.memberpass.net with app.subscriby.net, leaving the path exactly as it is. Until you do, the old domain keeps accepting those deliveries — but only until 12 November 2026.
Move your channels and groups to the new bot
Open the new bot and follow the prompt. See the section below.
Update your public links
Swap the old domain for subscriby.net in your social bios, Linktree, YouTube descriptions and pinned posts. Old links redirect until 12 November 2026, so there is no rush — but do it before that date.
The platform bot changed
Telegram does not allow a bot's username to be changed, so the platform bot is now @TrySubscribyBot. The old bot still exists and still works.
Both bots run side by side, and the platform knows about both, so nothing is duplicated: a subscriber is never approved twice and never gets two messages. For each of your channels and groups, exactly one bot is responsible, and until you move it, that is the old bot.
Open @TrySubscribyBot
Send it /start. It recognises you immediately — your account, projects and plans are already there.
Tap the reconnect button for each channel or group
The bot shows a keyboard with Reconnect a Channel and Reconnect a Group. Pick a chat and Telegram adds the new bot as an administrator with the same permissions the old one had.
Done — nothing to set up again
Subscribers, invite links and expiry handling carry over untouched. 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 it is harmless. You can remove it whenever you like, or leave it until we retire it.
Do not remove the old bot from a channel before reconnecting it to the new one. Until a chat is reconnected, the old bot is the one admitting and removing subscribers there.
Still stuck?
Email [email protected] with your project handle and what you are seeing. If it concerns a payment or webhook, include the Event ID — it makes tracing much faster.
How is this guide?