Development Sandbox

start with the payments api staging environment docid\ ukhb7 3ektubbv hblw1t to validate application payment workflows before moving real funds or production traffic for node backed workflows that require direct lnd access, confirm that a supported non production node environment is available confirm the test environment use the sandbox when you need to validate lnd api connectivity test macaroon based authentication create invoices and send payments test node balance and liquidity reads exercise payment state behavior before using mainnet funds rehearse the move from test credentials to production credentials choose the integration boundary use the payments api for application workflows such as wallets, payment requests, sends, receives, history, and payments webhooks use staging environment docid\ ukhb7 3ektubbv hblw1t for current payments test network guidance when a node backed bitcoin sandbox is connected to a payments wallet, choose mutinynet bitcoin mutinynet usd is only for usd line of credit testing, and voltage cash is the experimental stablecoin test wallet rather than a node backed bitcoin wallet use direct lnd interfaces only for node operations your implementation owns keep direct lnd credentials separate from payments api keys, and keep all non production credentials separate from production provision and connect for a supported non production node backed environment provision the environment through the current supported workflow record the environment, node, and operating owner collect the connection material described in configuration docid 9e9fmbsr1zz4nbvl47afl create the least privilege credential required by the client store payments api keys, macaroons, and tls material in the approved secret system test the smallest read only connection before using payment or channel permissions do not infer direct node support, dashboard labels, ports, funding behavior, or credential delivery from historical sandbox documentation credential and funding controls confirm how test funds and channel capacity are provided for the current supported environment before attempting a payment use only the maintained faucet, funding, and test resource guidance confirm the resulting balance through the payments api or the relevant direct lnd view before testing payments validate node operations for workflows that require direct node access, verify node information and sync state rest, websocket, or grpc connection behavior tls and certificate handling least privilege macaroon scope also verify on chain and channel balances inbound and outbound liquidity monitoring, alerting, and operator escalation application state can be reconciled with the node view payments api and direct lnd credentials remain separate use configuration docid 9e9fmbsr1zz4nbvl47afl , rest docid\ ccwymsz2axxdlr4lyhqpd , grpc docid\ zf545syqrbuqiufluhlpt , liquidity management docid\ tl26pm7dfmfxzvzzbczo5 , node security docid\ rlda4beej5rlbld3jm2ql , and macaroons docid\ gwvwanydfdd27zrsn32pc for maintained setup and operating guidance do not copy historical remote command syntax exercise the payment lifecycle verify the same lifecycle the production application will use create or select the test wallet generate a payment request through the payments api send and receive test payments confirm terminal state through the payments api confirm payments webhook delivery and reconciliation compare application state with the relevant direct lnd view only when node level diagnosis is required production readiness treat the move to mainnet as a production change, not only an endpoint and credential swap before going live provision the production environment through the current approved workflow replace all sandbox identifiers, endpoints, credentials, and network assumptions verify production liquidity and treasury ownership validate fee, limit, policy, and reconciliation controls repeat the send, receive, webhook, and monitoring checks record the go live owner, rollback plan, and escalation path verify backup and recovery responsibilities for node backed infrastructure related pages staging environment docid\ ukhb7 3ektubbv hblw1tconfiguration docid 9e9fmbsr1zz4nbvl47aflrest docid\ ccwymsz2axxdlr4lyhqpdgrpc docid\ zf545syqrbuqiufluhlptmacaroons docid\ gwvwanydfdd27zrsn32pcnode security docid\ rlda4beej5rlbld3jm2qlliquidity management docid\ tl26pm7dfmfxzvzzbczo5resources docid\ uldxo3 oydlivaxfda5lk