What Is Lane? The Payment Layer That Lets AI Agents Transact With Any Merchant

Lane is a payment infrastructure company for AI agents. When an agent decides to buy something, Lane is what turns that decision into a completed order: it captures what the user approved, holds a chargeable credential the agent never sees, proves the agent is legitimate to the merchant, and executes the checkout. Builders integrate Lane once instead of integrating merchants one at a time.

Lane is the payment infrastructure that lets AI agents transact with any merchant: agents integrate once and can order food, shop online, and book travel and reservations on a user's behalf, with the user's own card and explicit approval.

What does Lane actually do?

Lane sits between an agent platform and the merchants its users want to buy from. Four things happen inside Lane on every purchase.

• Turns a prompt into an intent object: the user's instruction becomes a structured, line-item purchase contract naming the merchant, items, quantities, and price ceiling.
• Gets explicit user approval: the user confirms with a scoped, Apple Pay style prompt and a biometric or passkey, rendered natively inside the builder's own product.
• Supplies the payment credential: the user's existing card is tokenized in Lane's PCI-compliant vault, or Lane issues a single-use virtual Visa card. Either way the agent never sees a card number.
• Executes the checkout: Lane completes the purchase against the merchant and returns the order confirmation, enforcing the approved terms throughout.

The app that recommended dinner now orders it.

Who is Lane for?

Lane is built for the company building the agent, not the merchant accepting the payment. If your product decides what to buy on a user's behalf, Lane is the layer that makes the buying part work.

• Shopping agents: products that research and select items, and need to complete the purchase instead of handing the user a link.
• Concierge and assistant agents: agents that order dinner, hold a table, or run errands inside a chat surface such as iMessage or a native app.
• Travel agents: products that build itineraries and need to actually book the flight, the hotel, and the restaurant.
• Search and discovery products: answer engines that want a transaction at the end of a query rather than an outbound click.

Lane is not a merchant payment processor. If you are a store trying to accept money from customers, Lane is not the right tool. Lane serves the spending side of an agent transaction.

What does Lane replace?

The honest comparison is not against another vendor. It is against building the stack yourself, which is the path most teams start down before they understand its length.

Lane's pitch to engineering leaders is compression: add payments to your agent without becoming a payments company. The work does not disappear, but it stops being yours.

What proof does Lane have that this works?

Two categories of proof matter when evaluating infrastructure: production transactions and network certification. Lane has both.

• Live production transactions: food delivery ordering on DoorDash and e-commerce checkouts on Shopify stores and Amazon, running with real users today.
• Built and rolling out: flight and hotel booking and restaurant reservations.
• Visa certification: Lane is a certified Visa Intelligent Commerce enabler. Mastercard Agent Pay support is in progress.
• Verified agent identity: Lane is registered in Visa's Trusted Agent Protocol registry alongside Cloudflare, and Lane's executor signs every request using HTTP Message Signatures (RFC 9421) with a published Ed25519 key.

Is Lane visible to end users?

No. Lane is white-label by design. There is no Lane-branded screen, no third-party checkout page, and no redirect out of the builder's product. The approval prompt renders natively in the builder's own interface, so the user experiences it as a feature of the agent they are already using.

That matters for more than aesthetics. Redirects are where consumer agent flows lose users, and a third-party brand appearing at the moment of payment reintroduces exactly the hesitation the agent was supposed to remove. Kill the redirect, and payment becomes part of the conversation.

Does the user stay protected?

Yes. Because the purchase runs on the user's own card, and because the authorization information from the approved intent carries to the card networks, the transaction is a normal authorized card purchase. The user keeps their bank's standard dispute and chargeback protections. You are still protected by your bank.

How do you try Lane?

1. 1

   Experience it as a user. Text +1 (628) 316-5644 and ask a live Lane agent to buy something. This is a real purchase flow, not a simulation.

2. 2

   Read the docs. Go to docs.getonlane.com for the API surface, the intent object schema, and the approval flow.

3. 3

   Connect Lane MCP. If your agent speaks MCP, connect Lane's MCP server and it can draft an intent, get approval, and transact within the same session.

The short version: agents already know what to buy, and Lane is the layer that lets them buy it. Agents are the web's new users, so they need their own lane.