KERNEL, the San Francisco company that runs cloud browsers for AI agents, made KERNEL agent payments generally available on 10 November 2026, letting agents pay on merchants’ existing checkout pages without card numbers reaching the developer’s application or the agent’s model context, with Stripe and Agentcard as integration partners. KERNEL says more than 4,000 companies use its browsers, and the merchant does not need to integrate anything. Fintechbits found no earlier coverage of KERNEL in its archive, and the release gives no pricing. KERNEL raised $22 million in seed and Series A funding led by Accel in October 2025, according to its own blog.
How KERNEL agent payments work
According to the KERNEL release, most merchants accept payment only through ordinary web checkouts. When an agent types card details into a page, those details can leak into its context, logs and screen recordings, which risks pulling the agent’s developer into PCI DSS scope.
KERNEL’s answer is Vaults, a feature that grants a browser session permission to use a payment method without returning the credential to the developer or the agent. KERNEL either fills the approved credential directly into the checkout or handles it at the network layer after the browser sends its request.
With Link by Stripe, the user approves a purchase within limits the developer sets, Link issues a one-use credential to KERNEL’s vault, and KERNEL fills it into the checkout. With Agentcard, KERNEL holds the checkout request at browser egress while Agentcard creates a merchant- and amount-bound authorisation, gets user approval and executes the payment.
Steve Kaliski, principal software engineer at Stripe, said: “Many online tasks ultimately end in a payment. KERNEL gives agents a secure environment to complete those transactions.”
Two approaches to agent checkout
The industry is split on how agents should pay. Card networks and large processors are building agent-specific protocols that merchants adopt, with tokens tied to an agent’s identity. KERNEL’s approach works with the web as it is, on any checkout page, which gives it far more reach immediately but less structure.
Fintechbits has followed the network-led route, including in its look at Visa’s agentic commerce benchmark. The two approaches are likely to coexist for years, because most merchants will not rebuild checkouts quickly. A long tail of small and mid-sized merchants runs on hosted checkout pages they barely control, and agents that want to buy from them need a way to use those pages as they are.
Agentcard’s model is worth noting. It ties each authorisation to a specific merchant and amount and asks the user to approve it, which limits what a misbehaving agent can do. Stripe’s Link route uses one-use credentials within limits the developer sets. Both are forms of spending control, and spending control is likely to be what regulators and card networks ask about first.
Fintechbits analysis
Why KERNEL Agent Payments Solve the Developer’s Problem, Not the Merchant’s
KERNEL agent payments solve a real and specific problem: developers do not want card numbers flowing through language models, logs and recordings. Keeping the credential in a vault and filling it at the last step is good security design, and one-use credentials from Link narrow the damage if something goes wrong.
The merchant side is less settled. A merchant seeing a KERNEL browser at checkout cannot easily tell an authorised agent from a bot, and fraud systems may block it. Disputes are another open issue: when an agent buys the wrong thing, who is liable? Fintechbits examined that question in its piece on agentic payments liability.
Stripe’s involvement is the strongest signal. Link already holds millions of saved payment methods, and making them usable by agents through partners like KERNEL extends Stripe’s reach into agent commerce without waiting for merchants to adopt new protocols.
Frequently asked questions
What are KERNEL agent payments?
KERNEL agent payments, available from 10 November 2026, let AI agents running in KERNEL cloud browsers pay on ordinary merchant checkouts without card numbers reaching the agent or developer.
Do merchants need to integrate with KERNEL?
No. The release says the merchant website does not need to integrate with KERNEL, because KERNEL fills credentials into existing checkouts or handles them at the network layer.
Which payment partners work with KERNEL?
Stripe, through Link one-use credentials, and Agentcard, which creates merchant- and amount-bound authorisations, are the launch integration partners.
What to Watch Next
The measure to watch is merchant acceptance. If fraud systems start recognising KERNEL sessions as legitimate agents, or a large retailer says it welcomes them, KERNEL agent payments will move from developer tool to commerce channel.



