Rizful

• Name: Rizful
• URL: https://rizful.com/
• Category: hosted Lightning wallet service / Nostr Wallet Connect payment control plane / Nostr-onboarding infrastructure
• Tags: bitcoin-ecosystem nostr-ecosystem
• Summary: Rizful is a hosted Lightning wallet with Nostr Wallet Connect and onboarding glued on top. The useful part is the account, receive-only NWC, and app-connectivity layer, not the easy-zaps pitch. Small but real control plane.
• What it does:
  • Provides hosted Lightning wallet accounts with user-chosen @rizful.com Lightning addresses for receiving sats and Nostr zaps
  • Onboards users into Lightning and Nostr by documenting account setup, Lightning-address selection, and client connections for apps like Jumble, YakiHonne, Primal, Damus, Alby, and Amethyst
  • Exposes Nostr Wallet Connect (NWC) connection strings, including receive-only codes that can accept payments without granting spend authority
  • Encourages use of receive-only NWC codes in e-commerce, gaming, social, and other app integrations where a service only needs to receive Lightning payments
  • Supports server-side developer integrations where applications create invoices and subscribe to payment notifications through NWC without running their own Lightning node
  • Emphasizes conventional account security with email/password and optional two-factor authentication instead of asking users to log into the wallet itself with their Nostr private key
• Key claims:
  • The homepage says Rizful was designed for security, does not allow login via Nostr, does not ask for a user’s Nostr private key, and instead relies on email/password plus optional two-factor authentication
  • The “Rizful First Steps” guide says Rizful is the easiest way to get started with Lightning payments and Nostr zaps
  • That same onboarding guide walks users through choosing a Lightning address, connecting Nostr clients, and even requesting a test zap, which makes the product look like an onboarding and wallet-control surface rather than just a static receive address
  • The read-only NWC guide says a receive-only NWC code is safe to share with untrusted apps because it can receive payments but cannot send them
  • The read-only guide explicitly lists e-commerce platforms, gaming platforms, and social zap receivers as intended downstream uses for Rizful’s NWC connectivity
  • The Rails integration guide says Rizful is a hosted Lightning wallet that exposes an NWC API, and it emphasizes that developers can create invoices and react to payments without running a Lightning node or payment processor
  • The same Rails guide argues that NWC reduces vendor lock-in because a developer can swap Rizful for Alby Hub or a self-hosted node by changing one environment variable, which reinforces that Rizful is operating at the open-standard wallet-service layer rather than inventing a closed proprietary integration model
• Whitepaper: No canonical standalone Rizful whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site and the first-party Megalith Lightning Docs covering onboarding, NWC permissions, and server-side checkout integration; see ../whitepapers/rizful-primary-sources-2026-05-03.md.
• Sources:
  • https://rizful.com/
  • https://docs.megalithic.me/using-rizful/your-first-steps-with-rizful/
  • https://docs.megalithic.me/using-rizful/get-read-only-nwc-code-from-rizful/
  • https://docs.megalithic.me/rizful-tips-and-tricks/accept-bitcoin-payments-in-ruby-on-rails/

Internal linkages

• Best upward reads: alby and nostr-wallet-connect.

Control surface

• Practical authority sits in account issuance, Lightning-address namespace, login and recovery policy, NWC permission scope, and how much app onboarding Rizful keeps inside its own hosted flow.

• Read it as hosted wallet connectivity over stronger Bitcoin and NWC rails, not as a category anchor.

• Last reviewed: 2026-06-05 UTC