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.
Old links stop redirecting on 14 November 2026. Until then everything resolves as before, so nothing breaks while you work through the checklist below.
After that date memberpass.net keeps running for one thing only —
accepting payment-gateway webhooks — until it is switched off entirely on
14 August 2027. Checkout links, portal links and app URLs on the old
domain stop working in November, not next August, so treat November as your
deadline for everything except the gateway dashboards.
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
The n8n node was republished
The n8n package is now n8n-nodes-subscriby. Existing workflows built on n8n-nodes-memberpass keep running — it stays installable and still talks to the legacy API host — but it is frozen at 1.4.0 and receives no further updates. It stops working on 14 November 2026: the old package reaches us through the legacy REST API, and only payment-gateway webhooks survive on that domain past November.
Every published version of n8n-nodes-memberpass is now deprecated on npm, so
installing it prints a warning pointing here. Nothing about the old package
changes before 14 November 2026, and nothing about it works after — so treat
that date, not the install warning, as your deadline.
Because the npm package name is new, its version restarts at 1.0.0. That is not a downgrade from [email protected]; it does everything the old package did.
Every identifier changed, and n8n cannot re-point a node across package names:
| Old | New | |
|---|---|---|
| npm package | n8n-nodes-memberpass | n8n-nodes-subscriby |
| Action node | n8n-nodes-memberpass.memberPass | n8n-nodes-subscriby.subscriby |
| Trigger node | n8n-nodes-memberpass.memberPassTrigger | n8n-nodes-subscriby.subscribyTrigger |
| Credential | memberPassApi | subscribyApi |
| Trigger webhook path | memberpass | subscriby |
So the move is a rebuild, not an upgrade:
- Install
n8n-nodes-subscriby(self-hosted for now — see the n8n page for why Cloud has to wait). - Create a new Subscriby API credential with an
sbt_token. The oldmemberPassApicredential cannot be re-used by the new nodes. - Copy your workflow, and in the copy replace each MemberPass node with its Subscriby equivalent, re-selecting the same resource and operation.
- Activate the copy. n8n registers a fresh webhook endpoint on save — the production URL changes, because the path segment changed.
- Only once the copy is confirmed working, deactivate the original.
Do step 5 last. Both workflows can run side by side, so there is no window where events are dropped — but if you deactivate the old one first, the new trigger's webhook endpoint may not be registered yet.
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 14 August 2027.
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 14 November 2026 — after that they stop resolving, so this is the one item on the list with a hard three-month deadline rather than a year.
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.
That first message also moves your own notifications across. Subscription activations, cancellations, payment failures and access-code exports are sent to whichever bot your account is attached to, and until you open the new one that is still the old bot. You do not have to do anything else for it — opening the bot once is enough, and it happens whether you go on to reconnect any channels or not.
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.
Still getting messages from the old bot? Open @TrySubscribyBot and send it any message. Your notifications follow whichever bot your account is attached to, and one message is all it takes to move them — separately from reconnecting your channels, which is why they can lag behind.
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?