Block has introduced the implementation of Lightning Network for the x402 protocol, originally created as a way to use HTTP code 402 for automatic payment of digital resources. The mechanism assumes that the server responds to a request with a message about the need for payment and issues an invoice, after which the client makes the payment and provides cryptographic confirmation. Upon successful verification, the server grants access to the requested data or service. This approach is designed not only for people but also for software agents that need to independently pay for APIs, computing resources, and other digital services. x402 appeared in the Coinbase ecosystem and was later transferred to the Linux Foundation. In 2026, Google, AWS, Stripe, Mastercard, and Visa joined the initiative, and the integration of Lightning added second-layer Bitcoin network payments to the supported infrastructure.
For automated systems, small amounts, high processing speed, and the absence of complex identification procedures before each operation are important. In Lightning, payments occur off the main blockchain, allowing the network to be used for frequent microtransactions. According to data provided in the source material, over the past 30 days, 75.41 million transactions totaling $24.24 million have passed through x402, with an average payment of about 32 cents. This transaction structure differs from traditional card settlements, where small operations can be economically inefficient due to fees and payment infrastructure features. Previously, USDC dominated x402: it accounted for 99.3% of transaction volume. Lightning support expands the available settlement mechanisms and allows Bitcoin to be used for the same micropayment scenarios.
The new implementation is currently in practical testing. Block's code is written in Python and must be tested on real Lightning nodes before full use. The company has also not announced timelines for integrating the technology into Cash App, Square, or Bitkey. A separate issue is related to scaling: a large number of payments from AI agents will require sufficient channel throughput and available incoming liquidity. If a software agent accesses one API thousands of times per hour, routing failures or lack of liquidity may hinder operations. Therefore, the publication of the code is a technical stage in the development of x402 but does not yet confirm the readiness of the infrastructure for mass use of automatic micropayments. Further testing will show how resilient this model will be under real load.
Related articles
