# Node-backed Infrastructure

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](/voltage-payments-api) 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](/voltage-infrastructure-api) for node lifecycle automation after confirming the current endpoint and credential requirements.

## Infrastructure topics

### Node lifecycle

Use [Development Sandbox](/development-sandbox) 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](/node-security) and [Macaroons](/macaroons).

### LND integration

Start with [Configuration](/configuration), then use [REST](/rest) or [GRPC](/grpc) for maintained direct-node connection guidance. WebSocket setup stays with Configuration.

### Liquidity and treasury

Use [Liquidity Management](/liquidity-management) 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](/bitcoin-core) and [Tools and Integrations](/tools-and-integrations) 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.