-
Notifications
You must be signed in to change notification settings - Fork 0
Frequently Asked Questions
Common questions about the CLINK payment plugin.
CLINK (Common Lightning Interface for Nostr Keys) is a protocol for Lightning Network payments that uses Nostr for transport. Unlike LNURL or Bolt12, it doesn't require a web server for your Lightning node.
| Feature | CLINK | LNURL | Bolt12 |
|---|---|---|---|
| Web server required | No | Yes | No |
| Nostr integration | Native | No | No |
| Privacy | High | Medium | Medium |
| Setup complexity | Low | High | Medium |
Yes! CLINK uses:
- Cryptographic signatures
- NIP-44 encryption
- Ephemeral keys for privacy
- No pre-shared secrets
Medusa v2.x. v1 support is experimental.
Yes, or a wallet that supports CLINK:
- ShockWallet (iOS/Android)
- Lightning.Pub (self-hosted)
- ZEUS (iOS/Android)
The plugin is free and open source (GPL-3.0). You only need a Lightning wallet.
All currencies supported by CoinGecko/Kraken:
- USD, EUR, GBP, JPY, and 50+ others
Lightning payments settle in:
- Typically 1-3 seconds
- Maximum ~10 seconds
Lightning network fees are minimal:
- Usually 0.1-1% of the amount
- Often just a few sats
No, this uses Lightning Network for instant payments. Regular Bitcoin transactions are too slow for checkout.
- Customer pays first invoice manually
- Gets
ndebit1...string from wallet - Pastes in subscription settings
- Future payments process automatically
Yes! Customers can:
- Disable auto-renewal anytime
- Remove their nDebit
- Pay manually instead
The plugin will:
- Retry payment
- Notify customer
- Allow manual payment
- Check invoice hasn't expired
- Verify Nostr relay connection
- Enable debug mode
- Check logs
- Check currency source
- Verify exchange rate API
- Try fixed rate temporarily
- Verify installation
- Check config syntax
- Restart Medusa
Yes! The plugin returns invoice data that you can display however you want.
Yes! The plugin works with Medusa Cloud deployments.
Yes! The architecture supports custom sources. See Contributing guide.
- Check existing issues
- Create new issue with:
- Steps to reproduce
- Expected vs actual behavior
- Environment details
- Logs (if available)
- Check discussions
- Create feature request issue
- Describe use case and proposed solution