After rollout, the order already carries the mandate.
The signed trace, the verify decision, and the checkout-session record sit on the order. Measure accept / review / decline on your own traffic. We do not publish a lift number.
Four jobs the mandate already covers.
Accept an in-scope agent order
A signed-in-scope agent can still look like a bot to velocity checks. Verify plus checkout-sessions give checkout a mandate to accept.
Keep returns on the same trace
The original order already has the agent identity, verification record, and checkout-session. Returns do not start from a blank ticket.
Send review with the mandate attached
A review recommendation arrives with the signed trace on the order, not an “is this a bot?” queue.
The same two calls, whether someone is watching
verify and checkout-sessions run the same at 3am as at noon. They do not wait for a human to classify the traffic.
Before rollout.
Do we need to change anything on the human checkout path?
No. KYA runs when you send it a kya_id or a trace_jwt. Human sessions are unchanged.
Can we measure this on our traffic?
Yes, after rollout. We do not publish a lift number. Measure accept / review / decline against your own checkout.
What if an agent's principal revokes authority mid-session?
Operators can revoke traces and rotate credentials, and merchants can re-check identity and policy on the next request. If a dispute workflow is opened, the existing trace and verification records can be used as supporting evidence.
Wire verify and checkout-sessions into the path you already run.
Neither call moves the card. Measure accept / review / decline on your own traffic.