Block has joined the x402 Foundation and contributed Bitcoin Lightning support to the open payment standard, extending x402 with a Bitcoin-native settlement option for software-driven commerce. In its official announcement, the company said Lightning is suited to the instant, low-cost and high-volume payments it expects agentic commerce to require. The contribution brings Lightning into x402’s payment architecture rather than creating a separate Block-controlled payment protocol.
x402 is designed around HTTP’s 402 “Payment Required” response, allowing a client to encounter a priced digital resource, satisfy its payment requirements and retry the request without relying on a conventional subscription or checkout flow. The x402 Foundation began operating under the Linux Foundation in July after Coinbase contributed the protocol to the independent organization. That model is intended to give software agents, APIs and applications a common payment layer that can support multiple networks and forms of value. The architecture fits a broader push toward crypto-native settlement for autonomous AI agents without making any single blockchain mandatory.
Lightning Enters x402 as a Payment Scheme
The technical contribution is already visible in x402’s official repository. A September 23 commit added the exact payment scheme for Bitcoin Lightning under the lnbtc namespace to x402 V2. Under the specification, a resource server generates a fresh BOLT11 invoice, the client pays it and returns the resulting payment preimage, and a facilitator verifies that the preimage matches the invoice’s payment hash before the protected request proceeds. The specification therefore binds payment to a particular request while using BTC over Lightning as the settlement asset.
The design also carries constraints that matter for automated systems. The current scheme supports BTC, BOLT11 invoices and an upfront payment flow, meaning settlement occurs before the requested resource is delivered. Routing fees are paid separately by the payer, while the specification provides no native refund path if a refund later becomes necessary. Lightning support should therefore be understood as a defined settlement mechanism, not as a guarantee that every machine payment becomes frictionless or reversible.
Those characteristics make the integration relevant to emerging agent economies where software may purchase data, API calls or other digital services programmatically. Other models are already experimenting with onchain identity, work discovery and escrow for AI-agent marketplaces, while cross-chain agent infrastructure is combining execution and payments across multiple networks. Lightning adds another settlement choice to that developing stack, particularly for workflows involving small BTC-denominated payments.
Adoption Will Depend on Production Use
The distinction between infrastructure and adoption remains important. x402’s public dashboard currently shows tens of millions of transactions across the protocol over its rolling 30-day window, but those aggregate figures span the wider x402 ecosystem and cannot be attributed to the newly added Lightning scheme. Likewise, a merged specification does not establish how many resource servers, facilitators or AI agents have implemented lnbtc in production.
Block’s move nevertheless places Bitcoin alongside a growing set of payment rails being considered for machine-driven economic activity. Similar infrastructure discussions are emerging around AI-driven microtransactions and stablecoin settlement and around onchain payment systems for distributed computing resources. Block itself has also participated in open agentic-AI infrastructure through the Agentic AI Foundation, reinforcing the company’s interest in standards that allow independently built software systems to interact. The common thread is interoperability between agents, services and payment mechanisms rather than dependence on one proprietary platform.
The next meaningful milestone will be observable production usage of the Lightning scheme. Live services advertising lnbtc, compatible client and facilitator implementations, and measurable Lightning-settled x402 transactions would provide evidence that the specification is becoming an operating payment rail rather than remaining primarily a protocol capability.