L402 is an innovative payment protocol developed by Lightning Labs that combines the Lightning Network with the HTTP 402 “Payment Required” status code, creating a system for pay-per-request access to online services.

In practice, it enables servers to require a Lightning payment before granting access to APIs, datasets, or digital resources. Unlike traditional authentication methods that rely on accounts or API keys, L402 treats proof of payment as the credential that unlocks access, offering a streamlined and secure payment mechanism for AI agents.

The L402 protocol leverages several foundational technologies to establish a secure, scalable, and seamless payment-based authentication system. Each component contributes to enabling frictionless interactions between clients (such as AI agents) and service providers.

Lightning Network Micropayments

The Lightning Network functions as the underlying payment layer for L402, making microtransactions feasible. As a second-layer scaling solution for Bitcoin, the Lightning Network enables near-instant payments with minimal fees. This combination of speed and cost-efficiency is particularly advantageous for micropayments, which are typically required in AI-driven environments.

Within L402, these micropayments often represent the cost of accessing a single API call or retrieving a small dataset. Each request may cost only a few satoshis, a fraction of a cent, allowing AI agents to perform thousands of transactions efficiently without incurring significant overhead.

Lightning Invoices: The Payment Requests

Every Lightning payment begins with a Lightning invoice, a structured data object specifying the amount, destination node, and a cryptographic hash used for payment verification. When a server requests payment for a resource, it generates an invoice and returns it to the client as part of the HTTP 402 response.

The invoice functions as both a payment request and an authentication trigger. Upon payment, the client receives a cryptographic value known as a preimage, which becomes a key element in validating access to the requested resource.

Macaroons: Programmable Authorization Tokens

Macaroons provide a flexible and decentralized authorization framework. These cryptographic tokens can include embedded conditions, or “caveats,” specifying constraints such as expiration times, allowed endpoints, or usage limits.

In L402, servers issue macaroons alongside Lightning invoices. Once the payment is completed, the macaroon, in combination with the payment preimage, grants conditional access to the requested resource. The ability to embed restrictions directly in the token allows distributed systems to enforce fine-grained permissions without relying on a central authority.

Payment Preimages as Proof of Settlement

Upon completion of a Lightning payment, the payer receives a cryptographic preimage corresponding to the hash in the original invoice. By revealing this preimage, the client proves that the payment has been settled.

In L402, the client sends both the macaroon and the preimage when retrying the request. The server verifies the preimage against the invoice’s hash and confirms the macaroon’s conditions. Successful verification unlocks access to the requested service or data, creating a secure and automated payment-for-access workflow.

The process of how L402 functions resembles a typical HTTP request cycle, but with an additional step that requires payment before access is granted.

When a client (e.g., an AI agent) first attempts to access a paid resource (e.g., to download a specific dataset from a research firm), it sends a standard HTTP request to the server. From the client’s perspective, this request might look no different from any other API call. However, if the resource requires payment, the server does not immediately return the requested data. Instead, it responds with an HTTP 402 “Payment Required” status code.

The response contains two important pieces of information. The first is a Lightning invoice specifying the price of accessing the resource. The second is a macaroon that represents conditional authorization. Together, these elements form a payment challenge.

Once the client receives the invoice, it uses a Lightning wallet or node to complete the payment. This process sends the required number of satoshis through the Lightning Network to the server’s node. After the payment settles, the client receives the payment preimage associated with the invoice.

With the payment complete, the client retries the original HTTP request. This time, however, the request includes both the macaroon and the preimage in the authorization header. These values serve as proof that payment has been made.

The server then performs a cryptographic verification. It checks that the preimage matches the hash embedded in the invoice and confirms that the macaroon’s conditions are satisfied. If everything is valid, the server processes the request and returns the requested data or service response.

Both L402 and x402 address the growing need for automated payment mechanisms that allow AI agents to autonomously access payment rails.

L402 integrates payments directly into web authentication via the Bitcoin Lightning Network. When a client requests a protected resource, the server issues a 402 Payment Required response with a Lightning invoice. Once the invoice is settled, the client presents proof of payment to gain access. L402 excels in scenarios that demand high-frequency micropayments, such as AI workflows executing thousands of API calls in rapid succession, due to its speed and minimal transaction costs.

x402, by contrast, leverages onchain transactions instead of Lightning channels. Payments are sent directly to a blockchain address or smart contract, and the gateway verifies settlement before granting access. This approach prioritizes transparency and verifiable onchain settlement, making it well-suited for environments that require integration with smart contracts or decentralized finance (DeFi) infrastructure.

In essence, L402 emphasizes efficiency and microtransaction scalability, while x402 provides robust onchain settlement guarantees. Both models serve complementary roles in a machine-driven economy, enabling AI agents to transact autonomously while supporting diverse operational priorities.

As AI agents become increasingly autonomous and interconnected, real-time machine-to-machine payments are critical for seamless service access. By combining the Lightning Network with HTTP authentication mechanisms, the L402 protocol facilitates instant micropayments as a prerequisite for API access, data retrieval, or computational resources.

As adoption grows, L402 could play a significant role in shaping the next phase of the internet, one where information and value move together seamlessly, enabling a truly programmable economy powered by both AI and DeFi infrastructure.