Node-backed Setup

node backed connects a customer controlled lightning node and reserve to the shared voltage payments api use this path when your organization needs direct ownership of node credentials, approved recovery material, treasury operations, and lightning liquidity what you own your organization owns node credentials, approved backup and recovery procedures, api credentials and macaroons, treasury policy, liquidity targets, monitoring, and internal production approvals voltage provides the hosted infrastructure and integration support defined for your account confirm the exact operating and support boundary during onboarding; do not assume voltage has access to move funds or administer the node before kickoff assign named owners for the node, payments integration, credentials, treasury, liquidity, incident response, and production approval confirm the intended bitcoin network and payments environment for each implementation stage define how node credentials, approved backup and recovery material, macaroons, api keys, and tls material will be generated, stored, rotated, and accessed agree on funding, liquidity, reconciliation, and escalation procedures before customer funds are introduced phase 1 qualify the operating model confirm that node backed is the correct model for the required custody, control, and operational responsibilities document which actions are customer operated and which actions, if any, voltage is authorized to perform under the current support agreement phase 2 build in staging use the staging environment docid\ ukhb7 3ektubbv hblw1t to validate the shared payments api workflow before production test wallet creation, authentication, payment requests, sending, receiving, payment history and status reads, failure handling, and payments api webhooks keep credentials environment scoped and separate staging data from production data phase 3 provision the lightning node use the current in product node provisioning workflow for your team product labels and navigation can change, so follow the interface presented to your account instead of relying on historical screenshots or dashboard paths create and securely store the approved node credentials and recovery material verify that the node is available and synchronized before associating it with a payments wallet phase 4 connect payments to the node use the current wallet creation or wallet configuration flow to associate the approved team node with the intended payments environment verify the selected network, environment, node, and wallet before completing the association do not reuse production credentials in staging phase 5 configure access use access model docid\ j3t5kpxleklmfldwhdo7w , node security docid\ rlda4beej5rlbld3jm2ql , payments access docid\ txpojpm5pxe1ksxjbt2an , and macaroons docid\ gwvwanydfdd27zrsn32pc to design least privilege access create only the credentials required by each application or operator store macaroons, api keys, tls material, and node connection details as secrets rotate or revoke access when ownership changes or exposure is suspected do not share unrestricted credentials by email, chat, tickets, or documentation a support credential is required only when explicitly agreed for a defined support workflow phase 6 validate the payment lifecycle exercise the same application paths that will run in production confirm wallet policy, quote handling, payment requests, sends, receives, payment history, status transitions, idempotency, webhook verification, reconciliation, and retry behavior webhooks docid\ pdeh 4et9aqawca5q91na are the supported event path for payments integrations phase 7 fund and operate liquidity define the initial funding source, approved destination wallets, minimum and maximum operating balances, channel and liquidity targets, approval thresholds, and emergency withdrawal process use liquidity management docid\ tl26pm7dfmfxzvzzbczo5 for the operating model reconcile payments api activity with direct node and treasury records alert on balance drift, failed payments, channel health, stale data, and credential or node availability problems tools and integrations docid\ uixuvwnqjahlq2wg8vncw are optional node interfaces they are not required steps in the node backed onboarding flow phase 8 production readiness complete a production review covering ownership, backups and recovery, credential isolation, node health, funding, liquidity, monitoring, webhook delivery, reconciliation, incident response, and rollback procedures run a controlled send and receive test with production credentials and verify the result through both payments and node records before increasing limits or volume responsibility boundary customer responsibilities operate credentials and recovery material, approve treasury movements, fund the node, define liquidity policy, monitor application and node behavior, reconcile records, and maintain incident contacts voltage responsibilities provide the contracted hosted infrastructure and payments integration surface, maintain the documented product interfaces, and perform only the support actions authorized for the account continue node backed docid\ qm0cy6sxnklcmgmv4cwep for the payments journey and ownership boundary node backed infrastructure docid\ zx2rflnnfmmh8ixlmcxba for node lifecycle, direct lnd access, liquidity, bitcoin core, and tools developer guide docid\ l4sp3ernfdbslxqajxoeg for wallets, payment requests, sends, receives, payment history, and webhooks configuration docid 9e9fmbsr1zz4nbvl47afl , rest docid\ ccwymsz2axxdlr4lyhqpd , grpc docid\ zf545syqrbuqiufluhlpt , and resources docid\ uldxo3 oydlivaxfda5lk for supported direct node connection options tools and integrations docid\ uixuvwnqjahlq2wg8vncw for optional node interfaces webhooks docid\ pdeh 4et9aqawca5q91na for payments event delivery