Mainnet Go-live Security Checklist

Complete this review with your engineering, security, and treasury owners before launching a mainnet integration. These are recommended launch checks, not controls that Voltage automatically enforces. Record an owner, date, and non-secret evidence for each item. Resolve failures before launch; document any approved exception and mitigation.

Every Payments integration

• Confirm the intended team, production environment, wallet, network, and backing model. Keep staging credentials separate.
• Review team members and roles. Remove unnecessary access and limit who can create keys or authorize payments.
• Create a dedicated environment-scoped API key per service with only the required permissions. See Payments Access.
• Keep keys server-side in approved secret storage. Confirm builds, logs, error reports, and browser responses do not expose secrets.
• Restrict production keys to stable service egress addresses where practical. Verify allowed and denied requests separately.
• Confirm TLS verification, bounded timeouts, and safe retry behavior. Reconcile an uncertain payment result before retrying a send.
• Verify webhook signatures, reject invalid events, and handle duplicate or delayed deliveries without duplicate fulfillment.
• Confirm final payment state on your server before fulfilling an order. Do not trust a browser callback as payment proof.
• Define payment approval, monitoring, reconciliation, and escalation owners. Agree on your own treasury limits and alerts.
• Rehearse failure handling in staging. Then coordinate a small, approved mainnet send/receive check and verify the recorded outcome.

Node-backed or direct LND integrations

You can skip this section if you are using a credit-backed wallet. This applies to customers who are using a node-backed wallet or using the legacy direct LND integration.

• Confirm the supported Node-backed setup with your Voltage advisor. Do not use retired self-serve provisioning instructions.
• Verify the effective node IP allowlist before funding. An empty list does not deny access.
• Review Payments key restrictions and node restrictions independently. Neither policy configures the other.
• Keep Admin and Super Admin credentials out of application backends. Inspect each integration’s actual macaroon permissions.
• Inventory credential consumers and shared root keys. Document replacement, revocation, and post-change verification without storing secret values in the checklist.
• Confirm node password, seed, and approved backup custody. Verify your recovery procedure safely with Voltage; never overwrite a funded node to test it.
• Confirm node/network identity and TLS. Monitor unexpected node activity, authentication failures, and balance changes.
• Assign liquidity, channel, and treasury ownership. Reconcile direct node activity with Payments records.

Sign off and keep it current

Record the launch decision, unresolved exceptions, and the people responsible for incident response. Repeat relevant checks after credential, team, endpoint, network, or deployment changes.

Before launch, confirm your established Voltage support route and escalation contacts with your advisor. If you suspect credential exposure, use that route immediately. Share affected identifiers and symptoms, never secrets.