Agent verification
Signed requests are checked against the agent's published keys and its operator's credential before the cart is priced.
Commerce
E-commerce merchants
Agents are arriving at checkout; merchants must tell them from bots and keep the order provable.
Shopping agents browse, compare and buy for their users. Merchants have spent years blocking automated traffic, and now need to accept the agents their customers send while keeping fraud and chargebacks under control. Public specifications such as ACP and AP2 describe how agents check out; AgenticOpenFinance adds agent verification, mandate scope and evidence around each order.
What agents do
What you build on AgenticOpenFinance
Agentic checkout
The merchant accepts a payment credential scoped to its store, the cart amount and a short expiry.
Order evidence
Cart, confirmation, token scope and agent identity are sealed with the order for chargeback handling.
Returns and refunds
Refunds go back to the original credential, and the agent's principal is notified.
Policy for agent orders
Rules cap basket size, restrict categories or require the customer's confirmation for first orders.
Value chain
The actors in this chain
AgenticOpenFinance connects them with one identity check, one mandate model, one policy and one evidence trail.
ShopperShopping agentMerchantPayment service providerCard issuerFraud team
Typical flow
A governed agent flow, step by step
- Agent arrives
- Signature verified
- Cart built
- Scoped token issued
- Order confirmed
- Evidence sealed
- Fulfilment or refund
Live demo
See it in the terminal
A buyer agent's €2,150.00 is held until the seller agent's conditions are met, then released (demo). Demo data
DemoAll companies, people, agents and amounts are fictional. Protocol names refer to public specifications; naming one is not a partnership or an endorsement.
Glossary