# Universal Commerce Protocol (UCP)

Discovery, payment handlers and complete checkout.

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.

**Universal Commerce Protocol (UCP).** Designed. UCP discovery, payment handlers and complete checkout.

Lanes: Platform (agent), Business, insimbi, Payment handler

1. Platform (agent) to Business: GET /.well-known/ucp
2. Business to Platform (agent): Profile: version, services, capabilities, payment handlers
3. Platform (agent) to Business: Create checkout
4. Business to Platform (agent): Checkout, advertising the payment handlers it accepts
5. Platform (agent) to Payment handler: Execute the handler to get a token or credential
6. Payment handler to Platform (agent): Token
7. Platform (agent) to Business: Complete checkout with the token
8. Business to insimbi: Authorize
9. insimbi: Check your rules, choose the rail, write the record
10. insimbi to Business: Result (or a challenge for strong authentication)
11. Business to Platform (agent): Checkout completed

- [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._