# Agent Payments Protocol (AP2)

A person present, an agent shopping, insimbi as the merchant's payment processor.

Cohorts: Mm + Fi

**Designed.** Protocol support is designed. The flow follows the protocol's published specification, with insimbi on the merchant side. Every check and every settlement is written to the record.

**Agent Payments Protocol (AP2).** Designed. AP2 human-present journey, with insimbi as the merchant's payment processor.

Lanes: User (trusted surface), Shopping agent, Merchant, insimbi, Credentials provider and network

1. User (trusted surface) to Shopping agent: Give the agent a shopping task
2. Shopping agent to Merchant: Build a cart
3. Merchant to Shopping agent: Cart, signed by the merchant
4. Shopping agent to Credentials provider and network: Ask for an applicable payment method
5. Shopping agent to User (trusted surface): Show the cart and payment method
6. User (trusted surface) to Shopping agent: Approve: a signed Checkout Mandate
7. Shopping agent to Merchant: Submit the order with the Checkout Mandate and Payment Mandate
8. Merchant to insimbi: Authorize the payment
9. insimbi: Check the mandates against your rules, choose the rail
10. insimbi to Credentials provider and network: Authorization, with agent presence signals
11. Credentials provider and network to insimbi: Approved (or a challenge such as 3-D Secure)
12. insimbi to Merchant: Result, written to the record
13. Merchant to User (trusted surface): Order confirmed

- [All flows](/docs/flows/): Every sequence diagram, linked to its section.
- [Integrations](/integrations/#protocols): Every agent protocol and rail we connect.
- [MCP tools](/docs/mcp/): insimbi as tools for any MCP client.

Request access: sales@insimbi.net

_insimbi is in early access with design partners._