Block has joined the x402 Foundation and added Bitcoin Lightning Network support to an open payments protocol designed for autonomous software and web services. The move expands settlement options beyond stablecoins and traditional payment methods, positioning the company to shape how AI agents might pay for individual services in the future.

What Is x402 and Why Does It Matter for AI Agents?

The x402 protocol repurposes an existing web standard, the HTTP 402 "Payment Required" response code, to enable payments during ordinary web interactions. When a client requests a paid API, dataset, or digital resource, a server returns payment instructions; the client then supplies proof of payment with a follow-up request. This design sidesteps the need for checkout pages or subscription models, which could streamline how autonomous software accesses services.

Coinbase originally developed x402 before contributing it to the Linux Foundation, which announced the x402 Foundation in April 2026. The foundation was created as a vendor-neutral home for the protocol, with published supporters including American Express, AWS, Circle, Cloudflare, Coinbase, Google, Mastercard, Shopify, Solana Foundation, Stripe, and Visa. Block's membership adds a large payments company with both merchant-facing products and a longstanding Bitcoin focus.

Why Bitcoin Lightning Instead of Stablecoins?

Block's contribution adds Bitcoin's Lightning Network, which processes transfers through payment channels before final settlement on Bitcoin. The company framed Lightning as suited to frequent, low-value transactions where speed and fees matter. This aligns with Block's strategic view that software agents may increasingly pay for individual services instead of relying on subscriptions or conventional checkout pages.

"Lightning is suited to frequent, low-value transactions where speed and fees matter," noted Steve Lee, who leads Block's Bitcoin initiative Spiral, framing the contribution as part of the company's effort to make Bitcoin useful for everyday payments.

Steve Lee, Bitcoin Initiative Lead at Block

However, the announcement does not mean Square sellers or Cash App users can immediately make x402 Lightning payments. Block did not provide a launch date for integrations with Square, Cash App, Bitkey, or its other consumer products. The practical near-term change is at the protocol level: developers now have a documented path for adding Lightning alongside existing payment options.

How to Implement x402 Payments in Your Service

Developers considering x402 adoption should understand the practical requirements and trade-offs involved:

• Payment Network Selection: Developers must decide which assets to accept, whether Bitcoin Lightning, stablecoins, or other settlement systems supported by the protocol.
• Failure and Refund Handling: Teams need to design systems that manage payment failures, reversals, and refunds, which differ across payment networks.
• Agent Spending Controls: Organizations must establish safeguards for autonomous software before it can spend on a user's behalf, including spending limits and approval workflows.
• Operational Infrastructure: Lightning introduces specific operational requirements around payment channels, liquidity management, and invoice handling that differ from card or stablecoin systems.

A common payment request format could reduce the need for every agent platform and merchant service to build a separate connection to each payment network. However, technical availability does not guarantee commercial adoption.

What Happens Next: From Standards to Real Transactions?

The next test is whether Block turns its standards work into production tools used by merchants or consumers. Evidence would include public integrations, transaction data attributable specifically to Lightning-based x402 payments, and clear safeguards for agent spending. Block said it plans to continue contributing Lightning support, participate in foundation working groups, and develop additional agentic-commerce tools, but no timeline has been announced.

Until those details arrive, the verified development is narrower but meaningful: Block has entered the foundation and contributed a Bitcoin-native settlement option to an open protocol intended for machine-readable commerce. The move signals that major payments infrastructure companies are preparing for a future in which autonomous software makes frequent, small transactions, even if that future has not yet arrived at scale.