How It Works
Credit-backed Setup
Use this path when Voltage provides the line of credit that backs your Payments wallets. Your application uses the shared Voltage Payments API without operating the underlying Lightning node.
Before you start
Section titled “Before you start”- Coordinate with your Voltage contact to confirm that the Credit-backed model is appropriate for your organization.
- Complete required business, underwriting, and contracting steps through the current onboarding process.
- Assign owners for API credentials, payment operations, webhooks, reconciliation, and production approval.
- Treat customer-specific eligibility, pricing, collateral, legal terms, and jurisdiction requirements as authoritative only in approved commercial documentation.
Implementation path
Section titled “Implementation path”- Start with the Credit-backed.
- Build and validate in the Staging Environment. Choose Mutinynet Bitcoin for a Bitcoin line of credit or Mutinynet USD for a USD line of credit. Voltage Cash is the experimental stablecoin test wallet and is not used for either of these credit-backed workflows.
- Configure environment-scoped Payments Access.
- Create wallets through Wallet Management and integrate the shared payment lifecycle through the Developer Guide.
- Implement Sending, Receiving, and Webhooks.
- Validate wallets, payments, quotes, wallet policies, assets, lines of credit, webhook events, reconciliation, and failure handling for your use case.
- Complete a production-readiness review before using live credentials or customer funds.
Credit-backed boundaries
Section titled “Credit-backed boundaries”Credit-backed customers do not manage node passwords, LND macaroons, channels, direct LND interfaces, or node treasury operations. Those responsibilities belong to the Node-backed path.
Technical documentation explains product integration. It does not replace underwriting decisions, contracts, pricing, credit terms, compliance review, or customer-specific operating requirements.