Voltage + BitGo: add Lightning through the account you already use

If you already use BitGo for Bitcoin custody, you don't have to begin your Lightning evaluation by looking for a replacement custody platform. Voltage powers Lightning infrastructure within BitGo through our partnership, so the first place to look is the BitGo account your team already uses. BitGo's partnership announcement

Your developers use BitGo's integration for this offering. Voltage's infrastructure supports it behind the scenes. That gives your team a way to add a Bitcoin payment option while building on its existing BitGo relationship.

The main decisions are which account path applies to you, what changes in your balance reporting, and which customer payments fit the current offering.

Find your starting point inside BitGo

BitGo's current documentation describes Go Lightning and dedicated custody Lightning wallets. They expose Lightning differently, so identify your account path before estimating the implementation.

For Go Lightning, BitGo says you don't need a separate Lightning wallet. After the relevant enterprise license is enabled, you can create invoices through your existing Go Account. The dedicated custody path involves creating a wallet and waiting for initialization, which the guide says can take up to 24 hours. BitGo's setup guide

That difference can change the work on your roadmap. A Go Account team should first investigate extending its current integration. A team using the dedicated wallet path needs to include wallet provisioning and the associated reporting in its plan. Your BitGo account team can confirm which option is available for your enterprise.

Know what the partnership handles for you

BitGo's partnership announcement describes a managed custody offering in which BitGo controls the keys and Voltage supplies automated node, channel, and liquidity management. Your team doesn't need to recreate that infrastructure to use the integration. Partnership responsibilities

The application still needs to make Lightning understandable to customers. Someone withdrawing Bitcoin needs to know which destination to provide, whether the requested amount is supported, and what happened to the payment. Support needs a record it can look up when that person asks for help.

That is where your implementation effort can go: adding the customer option, connecting BitGo's payment records to your own, and preparing support. The Voltage partnership announcement explains the infrastructure role behind this experience.

For this route, follow BitGo's Lightning APIs. A separate integration with the Voltage Payments API isn't required to use BitGo's offering, and our direct API setup instructions shouldn't be substituted for BitGo's guides.

Match the experience to the account's balance model

With Go Lightning, on-chain and Lightning funds appear in one overall Bitcoin balance. Amounts use satoshis, with 100 million satoshis in one bitcoin. BitGo documents valueSat for this path rather than millisatoshi amounts. Lightning balance reference

A dedicated Lightning wallet exposes a different view, including receiving capacity and spendable outgoing funds. Receiving capacity tells you how much the wallet can receive; it isn't an additional balance the business owns. Your reporting should preserve that difference.

For a product team, this affects the balance screen. For finance, it affects how balances are interpreted. If you use Go Lightning, don't introduce a separate customer-facing Lightning balance simply because a dedicated-wallet example has one. If you use the dedicated path, don't add receiving capacity to spendable funds when reporting assets. Use the fields documented for your account type.

Working through that mapping early can spare your team a confusing reconciliation problem after the first successful payment.

Choose a customer use case within the documented limits

BitGo currently documents a limit of $500 USD or less per individual Lightning transaction. Treat that as a product constraint when selecting an initial use case, and confirm the current limit with BitGo before launch. It is not a universal limit of the Lightning Network. BitGo Lightning overview

Small customer withdrawals are one example worth evaluating. A business that routinely needs larger transfers should discuss those requirements with BitGo before planning its customer experience around Lightning.

For incoming payments, BitGo's invoice guide covers amounts, memos, expiry, and invoice lookup. For outgoing payments, its payment guide distinguishes the Go Lightning and custody flows. Go Lightning includes a BitGo Express flow that builds, signs, and sends in one call, alongside a manual option. Your developers should use the path that matches the account you selected. Creating invoices, paying invoices

You can keep the initial customer experience narrow: one supported withdrawal option, a clear amount limit, and a result that support can trace. Expanding it becomes easier once your team understands how the account behaves.

Make the BitGo handoff specific

Before your engineers begin, bring your BitGo team the account type you use, the customer action you want to add, and the typical and largest payment amounts. Confirm license enablement, provisioning requirements, pricing, and the support process for that setup.

Then agree internally on what a successful rollout means. A completed payment is part of it. Your team should also be able to explain the resulting balance, find the invoice or payment record, and handle an expired request without confusing the customer. These are rollout recommendations, rather than results from a hands-on test performed for this article.

The opportunity here comes from the existing partnership: you can explore Lightning within BitGo while Voltage supports the underlying infrastructure. Start with BitGo's Lightning offering, or talk with Voltage about how the partnership fits your payment plans.

Based on primary documentation reviewed October 26, 2026. Account availability, limits, and commercial terms should be confirmed with BitGo for your enterprise.