Verify. Enforce. Keep the record.
/api/v1/verify for identity and recommendation. /api/v1/checkout/sessions for the signed mandate. Pre-dispute against the X-KYA-Trace-ID if the order is challenged. Your processor stays where it is.
What you call. What you get back.
Verify before authorization
Resolve the agent to its operator. Get accept / review / decline, trust_score, and reasons before the card is touched.
Enforce the signed trace
Fail orders outside scope, spend cap, audience, wallet, or MCC. The operator issued that mandate upstream; this call enforces it.
Open a pre-dispute on the same trace
The signed trace, verification record, and checkout-session trail attach to the alert. Operators get a response clock before chargeback.
Merchant questions.
Do I have to switch payment processors?
No. KYA sits on the verification path, not the money-movement path. /api/v1/verify is a recommendation. /api/v1/checkout/sessions enforces the signed trace. Your processor stays where it is.
What if an agent has no KYA credentials?
You decide. Policy can allow, challenge, or decline uncredentialed agent traffic the same way you already decide what to do with anonymous web sessions.
Does this slow down human checkout?
KYA runs when you send it a kya_id or a trace_jwt. Human checkouts are untouched.
Wire verify and checkout-sessions into the path you already run.
No processor swap. Shopify or custom API.