Block, the payments company co-founded and led by Jack Dorsey, has joined the x402 Foundation and contributed Bitcoin Lightning support to the open payment protocol that AI agents, web services and applications use to pay each other automatically. The move, announced on September 24, brings the largest corporate Bitcoin Lightning implementation directly into a standard that has so far been dominated by dollar-linked stablecoins, and it gives the agentic payments ecosystem its first serious non-stablecoin settlement option at scale.
What Block actually shipped
According to Block’s announcement, the company brought Lightning payments into x402 as part of its work on agentic commerce, describing Lightning as purpose-built for instant, low-cost, high-volume payments. The technical addition was already visible in x402’s public development repository before the corporate announcement: a September 23 commit records “exact Lightning on lnbtc,” using the lnbtc network identifier specification. That commit provides an independent public record of the Lightning specification entering the project immediately before Block disclosed its participation.
x402 was created by Coinbase and uses the HTTP 402 “Payment Required” response, a status code that has sat unused in the web’s specification for decades, to let software request and settle payments during an ordinary web interaction. A server can return payment instructions when an AI agent requests a paid API, dataset or other digital service. The agent pays and retries the request with proof of payment, all without a checkout page or human intervention.
Block’s contribution introduces Bitcoin Lightning as another payment option inside that framework. The company did not publish transaction volumes, merchant deployments or AI-agent usage figures specifically tied to its Lightning implementation, so the immediate impact is infrastructural rather than measured in transaction counts.
Steve Lee’s billions-of-payments bet
Steve Lee, head of Block’s Bitcoin development initiative Spiral, made the forward-looking case for the technology. He said agents “will make billions of small payments,” adding that such activity would need payment rails designed for frequent, inexpensive transactions. The statement represents Block’s expectation for agentic commerce rather than measured current Lightning demand, and it echoes arguments Bitcoin developers have made for years: machine-to-machine payments favor a network where fees are denominated in fractions of a cent and settlement is effectively instant.
The x402 protocol itself already carries substantial activity from existing payment methods. Its official site reported 75.41 million transactions and 24.24 million USD in volume, with 94,060 buyers and 22,000 sellers, during the previous thirty days as of Block’s announcement. Those figures cover x402 as a whole and should not be read as Bitcoin Lightning statistics.
Breaking the stablecoin monopoly on agent payments
Stablecoins have supplied the overwhelming majority of x402’s payment activity to date. Circle reported that USDC accounted for 99.3 percent of x402 payment volume measured during its second quarter, a figure that applied specifically to x402 activity in Circle’s data and not to every AI-agent payment system in existence. Lightning gives developers an option that settles in Bitcoin instead of a dollar-linked token, a meaningful distinction for applications that want exposure to, or simply neutrality in, a non-fiat-denominated asset.
Erik Reppel, x402’s creator and a member of its Technical Steering Committee, said the protocol was designed so different networks could be added without tying the standard to one payment rail. Recent weeks have demonstrated that design principle in practice. AI-agent payment support through x402 reached Cardano’s software stack in September, with an initial TypeScript release and a facilitator tested on the network’s pre-production environment. Autonomous payment infrastructure on Casper mainnet uses an x402 facilitator to let AI agents purchase online services. Agentic payment activity on the XRP Ledger passed one million x402 transactions by July, alongside Ripple-backed tooling for AI projects on the network.
A Linux Foundation standard with heavyweight backing
Coinbase originally developed x402 before contributing it to the Linux Foundation. The x402 Foundation was announced in April as a neutral oversight body and became operational in July with 40 organizations. Its launch roster listed Amazon Web Services, Google, Coinbase, Mastercard, Visa, Stripe, Circle, Ripple, Shopify and the Solana Foundation among premier members. Under the foundation model, x402 remains network and currency agnostic, allowing different settlement systems to plug into a common interaction between client and server.
Block’s membership ties the protocol to the company’s existing autonomous-software work. Block said it has contributed goose, its open-source AI agent, helped establish the Agentic AI Foundation and participated in the Universal Commerce Protocol initiative, a separate open-source standard connecting consumer-facing AI systems with merchant infrastructure covering product discovery and checkout. x402 serves a different layer: the payment request and settlement interaction over HTTP, including cases where an autonomous application purchases a single API call without a conventional checkout flow.
Why it matters for Bitcoin
For Bitcoin, the integration is a rare instance of the asset being wired into machine-native payments infrastructure at the protocol level rather than through a wrapper or bridge product. Lightning’s capacity for repeated micropayments matches the usage pattern agents are expected to produce: thousands of small transactions per task, each settled in seconds. If agentic commerce grows the way foundation members expect, Bitcoin now has a seat at a table that stablecoins were beginning to monopolize.
Bitcoin trades near 83,714 USD at the time of writing, with Ethereum at 2,686.80 USD and Solana at 119.70 USD as of the 14:46 UTC price snapshot on September 25, 2026.
Disclaimer: This article is for informational purposes only and does not constitute financial advice.
The part worth watching is Lightning inbound liquidity. Agents paying agents means thousands of tiny channels, and routing that volume is still the unsolved bit of the Dorsey thesis.
splicing might save the channel management pain but yeah, routing thousands of micro channels is where the dorsey thesis meets cold reality
inbound liquidity is the real bottleneck. thousands of agent channels with no routing balance is lightning 2018 all over again, hope the foundation budgeted for it
inbound liquidity plus routing fees on micro channels. agents paying 20 sats a call will bleed more to routing than the payment itself at first
this is what spider wallets solve, one managed channel instead of thousands of starved agent channels. foundation should push it as the default pattern or routing eats everyone alive
the sept 23 lnbtc commit showing up before the corporate announcement is a nice bit of transparency. first real non stablecoin rail in x402, huge for agents that dont want usdc exposure
Block joining the x402 Foundation matters more than the Lightning code itself. Corporate backing is what gets a protocol into actual procurement systems.
procurement yes, but dorsey has been pushing this thesis for years. at least now there is a spec commit and not just tweets about it
ai agents paying each other over lightning while my bank still takes 3 days for a sepa transfer. wild times
agents settling lnbtc in seconds while sepa takes three days. the real competition is legacy rails and they dont even know it
first real non stablecoin rail in x402 and the discourse is already usdc vs lnbtc tribalism. both legs work, that was the design
the sept 23 lnbtc commit showing up in the public repo before the announcement is such a chill move. ship first, press release later
First real non-stablecoin rail in x402 matters more than people think. Agent payments denominated in btc instead of dollars is a different bet entirely.
denomination is the interesting bit. an agent holding lnbtc between jobs eats vol it never chose, usdc quoting exists because machines hate float
Agents quoting jobs in sats and settling in lnbtc at least skip the float window entirely. Any rail that avoids USDC volatility is a diversification win.
agents holding lnbtc between jobs eating vol is the exact reason quoting stays in usdc with settlement in btc. split the unit of account from the rail and both camps win
unless the agent swaps lnbtc into usdc after each job through a provider. machines hate float but the rail itself doesnt have to hold it
Denominated in BTC matters for operators who already run Lightning nodes and think in sats. For everyone else USDC quoting stays the default, this widens the option set.
HTTP 402 sat unused for literal decades and now its the backbone of machine to machine payments. tim berners-lee unintentionally seeded this lol
decades of 402 sitting in the spec and the unlock was agents needing to pay each other. berners-lee seeded it, dorsey wired it to lnbtc lol
berners-lee gets the seed credit, coinbase wired 402 into x402, dorsey bolted lightning on. three companies and one dead status code, very normal payments history
the sept 23 lnbtc commit landing in the public repo days before any announcement is how you signal seriousness. dorsey shipping instead of tweeting for once
lnbtc commit lands sept 23, block announcement a day later. ship first and announce later is the correct order, more of this please