Node-backed
2 min
use this path when your organization controls the lightning node and reserve that back voltage payments wallets the payments api remains the application interface, while your team retains node level custody and operational responsibilities start here complete node backed setup docid\ smmi0 ukgfgdchtsztlu5 use the staging environment docid\ ukhb7 3ektubbv hblw1t to validate the application flow before mainnet follow the shared developer guide docid\ l4sp3ernfdbslxqajxoeg for environments, wallets and accounts, payment requests, sending, receiving, payment history, and payments api webhooks review the access model docid\ j3t5kpxleklmfldwhdo7w , node security docid\ rlda4beej5rlbld3jm2ql , and macaroons docid\ gwvwanydfdd27zrsn32pc continue to node backed infrastructure docid\ zx2rflnnfmmh8ixlmcxba for direct lnd access, node lifecycle, liquidity, treasury, bitcoin core, and approved tooling define funding, monitoring, treasury, and credential ownership before production shared payments api node backed and credit backed implementations use the same payments api where endpoint behavior is shared use the path specific guides for differences in funding, custody, liquidity, and settlement responsibility staging environment docid\ ukhb7 3ektubbv hblw1t for non production environment testing wallet management docid\ lbzudo0gzuwudhwrfcd6i for wallets, accounts, balances, and policy behavior receiving docid uq9knquoc9sgq0kuogmy for payment requests and receives sending docid\ ijeswowxjhpgyt6fv1kk1 for payment sends voltage payments api docid\ ee9anjjlombmff1vx4ujw for payment history and the canonical endpoint and schema reference webhooks docid\ pdeh 4et9aqawca5q91na for payments api event delivery migrating to node backed payments docid\ brko wdxk1diopuqwmffs when moving from a credit backed deployment ownership boundaries your team controls the node credentials and funds voltage hosts and supports the infrastructure according to the agreed service boundary direct node activity and payments api activity must be operationally reconciled because node level movement can occur outside the payments api ledger