BitGo Brings Lightning Payments Into Qualified Bitcoin Custody
BitGo launched Lightning Network access directly from its qualified-custody platform, using Voltage infrastructure to handle nodes, channels, keys, and liquidity for institutional clients. The service connected regulated Bitcoin custody with fast Lightning payments without requiring each institution to operate its own Lightning stack.
On December 17, 2025, BitGo announced that institutional clients could access the Bitcoin Lightning Network directly through its qualified-custody platform. The service was built with Voltage, which supplied automated Lightning infrastructure for node and liquidity management, while BitGo presented wallet creation and payment functions through institutional APIs.
The combination addressed a practical barrier to institutional Lightning use. Operating a production Lightning node requires more than holding Bitcoin keys: organizations must maintain highly available nodes, manage channels and liquidity, monitor connectivity, and integrate payment operations with internal security and accounting systems. Institutions that were comfortable keeping Bitcoin with a regulated custodian could therefore still find Lightning operationally burdensome.
BitGo's model attempted to bridge that gap. Clients could keep Bitcoin within an institutional custody relationship while gaining access to faster, lower-cost Lightning payments, with the underlying node and channel machinery abstracted behind managed infrastructure. That did not eliminate every Lightning custody tradeoff—the service was deliberately institutional and managed rather than a self-custodial consumer wallet—but it changed what regulated custody could be used for.
Historically, institutional Bitcoin custody had often been associated with passive holding, trading settlement, or collateral. Integrating Lightning introduced an active payments function. The launch therefore marked another step in the maturation of Bitcoin infrastructure: Lightning was increasingly being packaged not only for individual wallets and exchanges, but also for institutions that required regulated custody, security controls, and enterprise APIs.