Univers V-Commerce Protocol · UVCP

Hand back

The assistant has done what it can. It returns the person to the store, to a page on the store's own address, and stops.

Capability

com.univershq.vcommerce.handback

Version

2026-09-25

Schema

https://vcommerce.univershq.com/2026-09-25/schemas/handback.json

Builds on

Universal Commerce Protocol 2026-08-25, over MCP

Permission

com.univershq.vcommerce.handback:write, through Identity

Why it exists

Most commerce protocols treat the moment an assistant stops as a failure to convert. In a house, it is the moment the errand succeeded.

Almost everything an assistant is good at happens before the payment: finding, comparing, remembering, ruling things out. What stays with the person is the card, the account and the decision. So handing back is declared as a capability in its own right rather than left as the absence of a purchase, because a house wants to know it happened and an assistant should know it is the expected end.

Where the person is sent

On the store's own origin, always. An assistant that sends somebody anywhere else has not handed them back, whatever it reports, and a store's answer never names an address it does not serve.

The answer

{
  "ok": true,
  "url": "https://example-store.com",
  "waiting": 2,
  "message": "The person completes the purchase themselves, in this store's own checkout."
}

waiting is how many pieces are waiting for the store to collect: what this run left for the person, not the whole of their basket. Zero is an ordinary answer and does not mean the run was wasted. An assistant that only read and compared has still done the work.

What it does not do

It does not pay, price, reserve or promise. It does not carry the person's details anywhere. It ends the assistant's part and says where the person continues.

What a store must hold to offer it