How It Works
Node-backed
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
Section titled “Start here”- Complete Node-backed Setup.
- Use the Staging Environment to validate the application flow before mainnet.
- Follow the shared Developer Guide for environments, wallets and accounts, payment requests, sending, receiving, payment history, and Payments API webhooks.
- Review the Access Model, Node Security, and Macaroons.
- Continue to Node-backed Infrastructure 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
Section titled “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 for non-production environment testing.
- Wallet Management for wallets, accounts, balances, and policy behavior.
- Receiving for payment requests and receives.
- Sending for payment sends.
- Voltage Payments API for payment history and the canonical endpoint and schema reference.
- Webhooks for Payments API event delivery.
- Migrating to Node Backed Payments when moving from a Credit-backed deployment.
Ownership boundaries
Section titled “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.