ACP-style checkout handoff

Let ACP-style checkout start after negotiation is done.

ACP-style commerce focuses on catalog, cart, checkout, payment handoff, and order lifecycle. WATP focuses on the B2B conversation before that: quotes, counters, approvals, and final terms.

Woo checkout handoff liveACP bridge snapshot testedNo OpenAI or Stripe partnership claimed

ACP-style layers own

Checkout and order execution

Catalog, cart/session setup, payment surfaces, and order lifecycle belong to the checkout ecosystem the merchant chooses.

WATP owns

Quote-to-terms negotiation

WATP turns B2B demand into final terms that are stable enough to create a checkout or order handoff.

Today

Bridge logic is local and tested

connectors/acp maps HASH_CONCLUDED to an injectable checkout function. The cross-protocol demo uses mocks; Woo payment_url is validated live.

Practical flow

Agent or buyer creates WATP demand.

Supplier returns proposal and optional counters.

HASH_CONCLUDED contains terms and audit continuity.

ACP-style adapter creates checkout or order session.

What this does not claim

The current WATP bridge proves the adapter shape. It does not claim native access, certification, partnership, or production approval from OpenAI, Stripe, or any ACP operator.

WATP HASH_CONCLUDED
  -> final_terms
  -> checkoutFn(final_terms)
  -> ACP-style handoff