---
type: Article
name: "UCP and the checkout handoff: what changes when a purchase completes inside the conversation."
id: "https://selfe.ai/insights/protocols-and-agent-checkout/ucp-and-the-checkout-handoff-what-changes-when-a-purchase-completes-inside-the-c"
url: "https://selfe.ai/insights/protocols-and-agent-checkout/ucp-and-the-checkout-handoff-what-changes-when-a-purchase-completes-inside-the-c"
publisher: "did:web:selfe.ai"
description: "Every other protocol in this hub gets a purchase ready. UCP is the one that completes it: the point where a business hands back a confirmed order without sending the customer off to finish the job on a website."
datePublished: "2026-09-15T10:32:57.331Z"
author: The Selfe team
---

# UCP and the checkout handoff: what changes when a purchase completes inside the conversation.

> Every other protocol in this hub gets a purchase ready. UCP is the one that completes it: the point where a business hands back a confirmed order without sending the customer off to finish the job on a website.

## In short

- UCP is the step that completes a purchase inside an agent's own interface, not a website redirect.
- It only runs once identity, authorisation and live pricing have already been established elsewhere.
- The result is a confirmed order the business's system recognises as final, not a promise made in conversation.

UCP gets described as "checkout for agents", which makes it sound bigger than it is. It's specifically the last step, and it only works because everything before it already did its own job.

## What used to happen at this exact point

Everything else in this hub gets a purchase to the point of being ready. This is the protocol that finishes it.

An AI agent could do everything right, find the option, confirm it's genuinely available, even establish that the spend is authorised, and still hit the same wall: handing the person off to a normal web checkout to finish there instead. That's where a lot of otherwise-successful agent journeys used to fall over, at the last step rather than the first.

## What UCP changes

UCP defines a structured checkout call an agent's own interface can complete directly: the item or booking, the confirmed price, the delivery or arrival detail, a reference to the payment authorisation already established. The business's system responds with a confirmed order, and whatever detail the agent still needs to relay back, a booking reference, a check-in time, without either side leaving its own interface.

## What still has to be true before UCP can run

UCP only makes sense once everything else has already checked out: the agent's identity verified, the spend authorised, and the price and availability confirmed against live data. It doesn't check any of that itself, and it doesn't need to, because the item, the confirmed price, the delivery detail and a reference to the payment authorisation are already established by the time its own handshake begins. That's what makes it the last step rather than a new one: it turns an already-verified transaction into one the business's own systems recognise as done, not a fresh place to sell or another set of checks to pass.

## One handoff a business never has to build itself.

Selfe handles the UCP handoff as part of every completed transaction it processes, so a business's booking or order system receives a confirmed, verified transaction the same way it would from any other channel, without building a separate checkout flow for agents.

## Does UCP replace a business's existing checkout?

No, it sits alongside it, as the path for a transaction that started with an agent rather than a person browsing directly.

## What does a business receive?

A structured, confirmed order or booking, the same core information its own systems already expect.

## Act on this

- [Check whether an agent can buy from you](https://selfe.ai/agentic-commerce/buyability-check) — the free readiness scan.
- [Discover venues](https://selfe.ai/api/registry/discover) — `POST`, semantic browse across the registry.
- [Match a bookable answer](https://selfe.ai/api/registry/match) — `POST` with dates and party size.
- [Verify Selfe's identity](https://selfe.ai/.well-known/did.json) — `did:web:selfe.ai`.
- [Agent card](https://selfe.ai/.well-known/agent-card.json) — how to connect over A2A or MCP.