Your Payments Go to Your Wallet.
SatsRail requests an invoice from your wallet provider, or derives a fresh address from your watch-only key for on-chain, and confirms when it is paid. The customer pays your receiving wallet directly. SatsRail can see payments but never spend them or hold the funds.
You choose who controls the receiving wallet. For self-custody, choose Blink’s Spark account or your own Alby Hub. Check the account type when using a hosted wallet service. An on-chain wallet is watch-only in SatsRail, so its keys stay with you.
Already Have Another Wallet?
Try its Lightning Address in SatsRail first. You can also add the same wallet for on-chain, with its watch-only key. A Lightning Address needs to support both requesting invoices and checking whether they have been paid. Being able to receive Lightning payments alone is not enough.
Technical requirements
SatsRail uses LUD-16 for Lightning Addresses, LUD-06 for LNURL-pay invoices, and LUD-21 for payment verification. Your provider must return a verification URL and a valid settlement preimage. Alby Hub is one option; it is not a required integration layer. On-chain wallets need only a watch-only zpub or output descriptor for native SegWit (bc1q) or Taproot (bc1p) addresses.