Security
Security
Use this section to choose the security model that matches how your team uses Voltage.
Choose the right page
Section titled “Choose the right page”Payments only
Section titled “Payments only”Use Payments API keys for application access. They are scoped to one environment, so staging and production can be separated cleanly.
Start with Payments Access.
Node-backed Payments
Section titled “Node-backed Payments”Use Payments API keys for the Payments API. The underlying node also has its own security model, so node password, encrypted backups, and macaroons matter.
Start with Access Model, then review Node Security and Macaroons.
Direct node access
Section titled “Direct node access”If you use LND REST, gRPC, lncli, or custom node integrations, access is controlled by the node endpoint and LND macaroons.
Start with Macaroons.
Compliance and transaction review
Section titled “Compliance and transaction review”For risk checks, compliance partners, and payment data access, see Risk Management.
Where to start
Section titled “Where to start”- Use Access Model to understand all permission layers.
- Use Payments Access to separate staging and production API access.
- Use Node Security if you operate or connect a node.
- Use Macaroons before using direct LND access.