Node-backed Infrastructure
4 min
use this section when your implementation requires direct control of the lightning node underneath voltage payments it covers infrastructure and operational responsibilities that do not apply to a credit backed implementation choose the right interface use the voltage payments api docid\ ee9anjjlombmff1vx4ujw for application wallets, payment requests, sends, receives, payment history, and payments api webhooks use direct lnd interfaces for node information, balances, channels, liquidity operations, and other node level workflows use the voltage infrastructure api docid\ mkkcrwcnbxlczedmvyyls for node lifecycle automation after confirming the current endpoint and credential requirements infrastructure topics node lifecycle use development sandbox docid\ ijbwdu3cmhkjefgp ured for non production node backed checks provision, configure, monitor, update, restart, and retire node infrastructure with clear customer and voltage ownership boundaries security and backups protect node credentials, approved backup and recovery material, tls material, and macaroons start with node security docid\ rlda4beej5rlbld3jm2ql and macaroons docid\ gwvwanydfdd27zrsn32pc lnd integration start with configuration docid 9e9fmbsr1zz4nbvl47afl , then use rest docid\ ccwymsz2axxdlr4lyhqpd or grpc docid\ zf545syqrbuqiufluhlpt for maintained direct node connection guidance websocket setup stays with configuration liquidity and treasury use liquidity management docid\ tl26pm7dfmfxzvzzbczo5 to define who monitors on chain and channel balances, manages inbound and outbound liquidity, approves treasury movement, and responds to low capacity conditions bitcoin core and tools use bitcoin core docid\ ucsnnuis0gdzhaotkvmed and tools and integrations docid\ uixuvwnqjahlq2wg8vncw only when those products are part of your supported deployment tooling guidance is limited to thunderhub and terminal web and does not replace upstream project documentation important boundaries direct node activity can occur outside the payments api ledger and must be reconciled operationally