Give your team the context behind an agent order.
Link the signed trace and checkout decision to your order. Use those records to review a purchase, handle a return, or respond to a complaint.
Use the records during order review.
Accept an in-scope agent order
Check the registered agent and compare its order with the signed purchase limits. Your store decides whether to proceed.
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.
Review an order with its purchase limits
Save the verification result and trace reference with the order so a reviewer can inspect the purchase limits.
Apply checks to unattended agent orders
Your integration can request verification and checkout checks when an agent submits an order. Route results according to your store policy.
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?
During a pilot, measure accept, review, and decline results on your own checkout traffic.
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.
Review a checkout integration with us.
Choose the checks and records your team needs, then evaluate the results during a pilot.