Configuration

Set up notifications so you and your subscribers stay informed.

How Notifications Work

Subscriptions Manager has a two-level notification system:

1

Global Settings

Configure your notification credentials once. These are your defaults.

→

2

Per-Plan Settings

Each plan can use global defaults or override with custom settings.

ℹ️

Important

Subscribers only see contact options you've configured. If you only set up Email, subscribers will only see the Email option at checkout. If you configure Email + Telegram, they can choose either.

---

Notification Channels

Channel	Use Case	Requirements
Email	Professional communication, receipts	SMTP server credentials
Telegram	Instant alerts, quick support	Bot token + Chat ID
Webhook	System integrations, automation	URL that accepts POST
Nostr	Privacy-focused, decentralized	Your nsec private key

---

Setting Up Global Notifications

Click the gear icon (⚙️) in the extension to open Settings.

Email (SMTP)

1

Enable Email

Toggle on Email Notifications.

2

Enter SMTP Details

Field	Example	Description
SMTP Server	smtp.gmail.com	Your email provider's SMTP host
SMTP Port	587	Usually 587 (TLS) or 465 (SSL)
Username	you@gmail.com	Your email login
Password	••••••••	App password (not regular password)
From Address	noreply@yourdomain.com	Sender address shown to recipients

3

Test & Save

Click Test to send a test email to yourself. If it arrives, click Save.

💡

Gmail Users

Use an App Password, not your regular Gmail password. Go to Google Account → Security → 2-Step Verification → App passwords.

---

Telegram

1

Create a Bot

1. Open Telegram and search for @BotFather
2. Send /newbot and follow the prompts
3. Copy the bot token (looks like 123456789:ABCdef...)

2

Get Your Chat ID

1. Start a chat with your new bot (send any message)
2. Visit: https://api.telegram.org/bot<YOUR_TOKEN>/getUpdates
3. Find "chat":{"id":123456789} — that's your chat ID

3

Configure in Settings

Field	Value
Bot Token	Your token from BotFather
Chat ID	Your numeric chat ID

---

Webhook

For integrating with external systems (Zapier, n8n, custom backends).

Field	Description
Webhook URL	Full URL that accepts POST requests
Webhook Secret	(Optional) Signs payloads with HMAC-SHA256

Payload format:

{
  "event_type": "payment_received",
  "message": "Payment received for Pro Plan...",
  "timestamp": 1704067200
}

If you set a secret, verify the X-Subscription-Signature header.

---

Nostr

For decentralized, privacy-focused notifications via direct messages.

Field	Description
Private Key	Your nsec or hex private key (encrypted in DB)

⚠️

Your Nostr private key is stored encrypted. Use a dedicated key for this purpose, not your main identity.

Create a dedicated Nostr key:

• NostrID — Quick online generator
• Nostr Key Generator — Local Python script

---

Per-Plan Notification Settings

When creating or editing a plan, you have two options:

Option 1: Use Global Defaults

Leave plan notification settings empty. The plan will use whatever you configured in Global Settings.

Global: Email ✓, Telegram ✓
  └── Plan A: (no override) → Uses Email + Telegram
  └── Plan B: (no override) → Uses Email + Telegram

Option 2: Custom Per-Plan

Override global settings for specific plans.

Global: Email ✓, Telegram ✓
  └── Premium Plan: Email ✓, Telegram ✓, Nostr ✓  (adds Nostr)
  └── Basic Plan: Email ✓ only  (removes Telegram)

Why use per-plan settings?

• Premium plans might offer more contact options
• Basic plans might be email-only to reduce support load
• Different plans for different audiences (crypto-native vs. traditional)

---

What Subscribers See

At checkout, subscribers only see contact methods you've actually configured:

Your Configuration	Subscriber Sees
Email only	Email field
Email + Telegram	Email field + Telegram Chat ID field
All four channels	All four contact fields

💡

The more contact options you provide, the better subscriber experience. Some users prefer Telegram for quick alerts, others want email receipts.

---

Notification Events

Choose which events trigger notifications in Global Settings:

Event	Merchant Notified	Subscriber Notified
New subscription	✅	✅ Confirmation
Payment received	✅	✅ Receipt
Payment failed	✅	✅ Alert + grace period info
Subscription renewed	✅	—
Subscription cancelled	✅	✅ Confirmation
Subscription expired	✅	✅ Resubscribe link
Expiring soon	(optional)	✅ Reminder

---

Troubleshooting

Notifications not arriving?

1. Test first — Use the Test button in Settings before relying on real events
2. Check spam — Email notifications might be in spam folder
3. Verify credentials — Double-check bot tokens, SMTP passwords
4. Check LNbits logs — Look for notification errors in server logs

Subscriber didn't receive notification?

1. Verify the contact method is enabled for the plan
2. Check if subscriber entered correct contact info
3. Telegram: Subscriber must have started a chat with your bot first
4. Nostr: Subscriber's NIP-05 identifier must be resolvable

---

You're Ready!

✅

Setup Complete

Your subscription business is configured:

• ✅ Extension installed
• ✅ Plan created
• ✅ Notifications configured

Share your subscribe link and start earning!

Learn MoreDive deeper into managing subscribers

→