01PROPOSED
The agent asks for one thing.
Your product's agent proposes an action: a merchant, an amount, a reference. Nothing has been approved yet, so nothing about it can be trusted.
Revenue from agents.
Proof for every action.
Attesso is the authorization layer for agentic commerce. A person approves the limits once with a passkey. Every agent action after that is checked against those limits and signed into one record anyone can verify. You keep your payment provider and your execution rail.
One record. Four states.
From what the agent proposes to what anyone can check, without trusting the platform or us.
02APPROVED
A person approves the limits. Once.
The customer sees the exact bounds and signs them with a passkey. Not a blanket permission and not a checkbox: one signature over the limits that apply from here on.
Passkey approval happens on the approval surface, or inside your own app. The bounds are what get signed, not a policy label.
03EXECUTED
Every action is checked against them.
The agent acts. Attesso decides against the signed bounds, allows one execution, and records what was asked, what was allowed, and what happened.
No executor calls and no money movement. Your payment provider and your rail stay where they are.
04VERIFIED
Anyone can check it without trusting us.
The record carries its own signature and digest. A client, an auditor, an insurer or a regulator verifies it against published keys, offline, years later.
Every payment shape, one provable record
From the first approval to every action after it, one record. The same mandate, the same decision, the same evidence. Only the execution mode and the rail change.
~/one-time-payment
The agent requests one specific purchase. Attesso allows or denies it against the approved bounds.
~/recurring-payment
A recurring mandate carries a per-period budget and stays active until its term runs out.
~/scheduled-payment
Future-dated authority stays scheduled until its start time arrives, then becomes active.
~/budget-bounded-payout
The integrator moves the money on its own rail. Attesso reserves the amount against the mandate first.
~/refund-reporting
Full and partial refunds are appended to the signed record as labelled external reports.
~/audit-trail
Every state change lands in one signed evidence bundle that anyone can verify.
Our position
The permission record for agentic commerce.
Every layer of an agent's action already has an independent record. The itinerary lives with the airline, the payment with the network. Permission is the last layer still held by the platform's word. Attesso turns it into a record: who allowed what, which action was decided, and why, in a form a third party can verify without trusting the platform or us.
See how the protocols compare
Attesso runs inside your product.
No consumer app. No consumer account. One approval, then every action is checked and signed behind your flow.
See the embedded modelFrom agent intent to signed proof.
The customer defines the permission. Attesso verifies the agent's request and produces signed evidence that proves it. The integration is plain HTTPS: create a mandate, submit the proposed action, commit the outcome.
See the implementation path~/customer-controlled
The customer sets the limit. The agent stays inside it.
~/independently-verifiable
Signed evidence records what was approved and what the agent requested.
~/keep-your-payment-provider
Add agent authorization without replacing your existing payment rail.
Built for agents that act while you're away.
A traveler approves a bounded mandate before boarding: this route, this cabin, up to this price, until Friday. When the airline moves the flight, the booking agent rebooks inside exactly those limits, and every decision comes back as signed evidence.
Put one signed mandate between your agent and its next payment.
Every step, from the customer's approval to that payment, comes back signed.