AP2 handoff

Negotiate first, then authorize payment.

AP2 is about authorization and mandates for agent-led payments. WATP sits before that moment: it discovers suppliers, records multi-turn B2B terms, and produces a concluded state that a payment layer can use.

payment_url validated liveHandoff boundary documentedAP2 adapter not a live rail yet

AP2 owns

Payment consent and mandate semantics

The payment layer should prove authorization, consent, and the rules for charging an agent-initiated transaction.

WATP owns

The negotiated business terms

WATP turns demand, proposals, counters, and approval states into an auditable chain before any authorization should be requested.

Today

Checkout handoff is real

Production Woo suppliers can return official payment_url after HASH_CONCLUDED. AP2-specific mandate generation remains a future payment-adapter responsibility.

Practical flow

1.

Buyer agent creates demand and supplier filters.

2.

WATP runs proposals and counters with guardrails.

3.

HASH_CONCLUDED freezes price, quantity, delivery, and terms.

4.

A PSP or merchant adapter can create AP2-style authorization.

What this does not claim

WATP is not a payment network, not an escrow product, and not an AP2 certification. It can supply the auditable B2B negotiation evidence that a compliant payment layer may need before it asks for authorization.

HASH_CONCLUDED
  -> final terms
  -> payment_url or mandate adapter
  -> AP2-style authorization layer