When an AIagent buys,prove thecustomersaid yes.

AI agents now book hotels, tickets and goods. When a customer says "I never approved that", the business loses the money. Mandate Ledger checks her permission before payment, asks her only when it's unclear, and seals a record her bank can verify.

Sample booking HB-20417fictional
Harbour Hotel, Austin, 2 nightsHeld, then approved from a text link with Face ID
Sealledger entry 4183

Sample booking HB-20417, Harbour Hotel, Austin, 2 nights. Recomputed seal: 622a8472eaf2e799a2a97dd2dc5e55386943840942cecc2a5ce84d32209e909b

$640.00
Checkingthe seal

Checked live in your browser. Add one cent to the price and the seal breaks.

An AI agent books.Did she say yes?Nobody asked.She disputes. You pay.

With Mandate Ledger, the payment waits until her permission is checked. No permission, no charge.

The click used to prove she meant it. Agents removed the click. We put the proof back.

Sarah's AI assistant books her a $640 hotel room in Austin. Two weeks later she doesn't remember approving it, and her bank takes the money back. The hotel has no proof: the device and clicks were the agent's, not hers.

  • $36.9BChargebacks forecast worldwide for 2026, before agents add to them.Mastercard, citing Datos Insights
  • $190B to $385BUS online spending that could run through AI agents by 2030.Morgan Stanley
  • Not settledWho pays when an agent purchase is disputed for reasons other than fraud. Until it is, the business usually carries the loss.Worldpay

About $0 in chargebacks worldwide since you opened this page.

Agents started paying in 2025. The rules are being written now.

  1. The rails are live.Visa, Mastercard, Google and OpenAI all launched ways for AI agents to pay in 2025.
  2. Identity is solved, consent is not.Networks can tell which agent is buying. None checks each purchase against what the customer allowed before the money moves.
  3. Old evidence doesn't fit.From 24 October 2026, Visa's dispute evidence rule still needs a match on the cardholder's own device or IP address. On an agent order, those belong to the agent. Visa rules

Whoever records the customer's yes at checkout sets the evidence standard.

Spotted.An AI agent reaches checkout. We read its signed check (Visa's Trusted Agent Protocol, Mastercard Agent Pay or Web Bot Auth), so you know which agent it is and who it's booking for. 14:02:04
Held.Your payment provider holds the money but doesn't take it yet. 14:02:05
Checked.We compare the booking with what she allowed: her saved rules or her signed instruction to the agent. Price, dates, room type, cancellation terms. 14:02:06
Approved.Clearly inside her rules: approved silently. Unclear ("free cancellation" not confirmed) or outside them: a text link to her phone, and she approves this exact booking with Face ID. 14:02:09
Sealed.Her approval, the booking, the price and what the agent was shown are sealed together before any money moves. 14:02:12
Paid.The hotel takes the payment and confirms the stay. 14:02:14
Proven.If she questions the charge, the sealed record is ready for her bank, so it can be answered before it becomes a dispute. 19 Nov

Didn't approve? The hold is released and she is never charged. No refund, no dispute, no fee.

Built for everyone between the agent and the bank.

We sell through payment providers, so one integration reaches thousands of businesses.

  • Payment providers and acquirers

    Agent orders put your merchants' dispute rates at risk. Add a consent check and network-ready evidence to every agent checkout, under your brand.

    Partner with us
  • Travel, ticketing and digital goods

    Where agents buy first, and where disputes cost most. Take agent bookings without inheriting their chargebacks.

    Become a design partner
  • Chargeback and fraud teams

    The one piece of evidence you can't collect yourself: the customer's own approval, sealed before the charge.

    See the record file
  • AI agent builders

    Get let in, not blocked. Businesses trust agents whose purchases carry the customer's approval.

    See how records are signed

Try it: a dispute just arrived.

Pick a record and check it the way her bank would. Sample data, real checks.

Visa fraud dispute: "I didn't authorize this"$640.00Reply due 9 Dec 2026

Proof made for the tools banks already use.

Record file

Booking
#HB-20417
Found by
the payment ID
Contains
agent, approval, booking, what the agent was shown, payment
Sealed
before payment
Checks run
11, every result shown
Verify
anyone can, without us
Works todayDownload the record file and verify it yourself.
NextDelivered to banks through Visa and Mastercard's pre-dispute services, and through payment provider APIs.

Built to reach her bank when she first questions the charge, so many disputes never start. See the record format

What the record proves, and what it doesn't

We prove.

  • She approved this exact booking
  • Her approval came before the payment was taken
  • Nothing has changed since
  • Which agent and which of her devices signed it
  • What the agent was shown, so you can spot a misleading listing

We don't.

  • Decide the disputeHer bank does.
  • Hold or move moneyYour payment provider does.
  • Promise you'll win
  • Prove who was holding the phone
See every limit

We build on the networks, not against them.

The networks prove which agent is buying and what she allowed in general. We check each purchase against it before payment, and give you one record across all of them.

Network or protocolWhat it tells usWhat we add
Visa Trusted Agent ProtocolWhich agent is checking outHer approval for this exact booking
Mastercard Agent Pay and Verifiable IntentWhat she allowed in generalA check of this booking against it, sealed before payment
Google AP2Her signed instruction to her agentOne record that also works for Visa and Mastercard orders
OpenAI and Stripe ACPThe order detailsProof she approved them, and what the agent was shown

Neutral by design: every network, every agent, any payment provider.

Starting at checkout. Built for everything agents do for people.

  1. Now

    Consent check before payment, and a sealed record for every agent purchase

  2. Next

    Records sent to banks before disputes start; checks for misleading listings; recovering losses when an agent breaks the rules

  3. Then

    Guaranteed agent orders; company purchasing agents with spending policies

  4. Vision

    The consent layer for anything an AI agent does on someone's behalf: bookings, subscriptions, account changes, contracts

Early, and moving. Prototype live, with real signature checks.

Questions we get asked.

Will it slow down checkout?
Only for agent bookings outside her saved rules or where the match is unclear. That takes one tap. Everything else is silent.
Do you handle money or card numbers?
No. Your payment provider holds and takes the money. We see the booking, the agent and the approval.
Which payment providers can it work with?
Any that can hold a payment and take it later, which most travel providers already do. Tell us yours on the form.
What if the agent doesn't identify itself?
It goes through your normal checkout, as today.

Be ready before the holiday disputes arrive.

Disputes on holiday bookings land in the new year. Join as a design partner now, free for 90 days.

  1. Turn it on through your payment provider, or add our checkout step.
  2. Agent payments wait until her approval is checked.
  3. Every booking gets a sealed record, ready for her bank.
You are a optional
Do AI agents already book or buy from you? optional

We use these details only to reply to you. Privacy