Chat → action
Once an agent can move money, "did it answer well?" stops being the risk. "Was it authorised to charge, refund, or remit?" becomes the risk.
Your AI agent can take the order. KYE Protocol™ proves it was allowed to take the money.
Agentic commerce has moved from chat to action: agents now send payment links, confirm orders, issue refunds, change subscriptions, and trigger cross-border payouts. The KYE™ Commerce & Payments Authority Pack™ governs the moment those actions become consequential — it proves, before the money moves, that the agent was authorised, within scope, under the right policy and jurisdiction, and seals an offline-verifiable Evidence Pack™. Stand it up in an 8–12 week pilot and cut payment-dispute exam-prep from days to minutes.
KYE™ Commerce & Payments Authority Pack™, at a glance
Demo dataYou learn: What this pack governs and how. You can: Run through it.
-
Payment authority
KYE Protocol™
An agent may request or capture a payment only when the customer, product, price, merchant scope and spend limit all resolve to a valid delegation — not because it holds an API key.
-
Refund & chargeback authority
KYE Protocol™
An agent may refund, cancel, or compensate only within the delegated refund/cancellation policy — and every chargeback ships with a signed a scheme can verify. evidence record
-
Cross-border & remittance authority
KYE Protocol™
A payout or remittance resolves sanctions-screening authority, travel-rule data, , jurisdiction and consent at the action boundary — all signed, before the transfer is final. FATF SCA
-
Outbound-contact & consent authority
KYE Protocol™
A collections or dunning agent may call or message a customer only when consent, purpose, channel and jurisdiction rules are satisfied — proven, not assumed.
How this widget is built
- Demonstrates
- KYE™ authority packs
- Components
- The regulated actions
- Their authority
- Their evidence
- Flow
- Each action the pack governs, in order. Architecture diagram
- Used on
- /foundry/commerce-payments-authority-pack/: On every pack's page.
The problem: a secured agent can still take a money action no one authorised
A checkout agent can be perfectly authenticated, scoped to least privilege, and fully logged — and still send a payment request, refund an order, or push a remittance that no one actually had the authority to approve for that customer, at that price, into that jurisdiction. Logs tell you it happened; they do not prove it was allowed. That gap is where chargebacks, mis-priced orders, sanctioned payouts, and consent breaches live.
Disputes need proof, not logs
A card scheme, a regulator, or a customer asks An audit trail records the event; KYE Protocol™ proves the action was admissible and replays the decision from published keys. who authorised this?
Four money actions, four authorities — resolved at the boundary
The Pack binds each consequential commerce action to a delegated authority that is checked the moment it happens, then sealed. You keep your payment service provider; KYE Protocol™ adds the authority decision and the proof on top.
Payment authority
An agent may request or capture a payment only when the customer, product, price, merchant scope and spend limit all resolve to a valid delegation — not because it holds an API key.
Refund & chargeback authority
An agent may refund, cancel, or compensate only within the delegated refund/cancellation policy — and every chargeback ships with a signed a scheme can verify. evidence record
Cross-border & remittance authority
A payout or remittance resolves sanctions-screening authority, travel-rule data, , jurisdiction and consent at the action boundary — all signed, before the transfer is final. FATF SCA
Outbound-contact & consent authority
A collections or dunning agent may call or message a customer only when consent, purpose, channel and jurisdiction rules are satisfied — proven, not assumed.
Where the boundary is: KYE Protocol™ governs the action, your PSP moves the money
This Pack is deliberately not a payment processor. KYE Protocol™ does not hold funds, settle, or replace Stripe, Adyen or Wise — and it never will. It is the Authority Governance™ layer above the processor: the processor executes the transfer; KYE Protocol™ decides whether the agent was allowed to initiate it and proves that decision afterwards. You add an authority gate and an evidence trail to the payment stack you already run.
- Reuses your stack. Works over your existing PSP, checkout, and commerce-agent platform — no migration, no re-platforming.
- Standards-mapped. Cross-border authority is mapped to PSD2/PSD3 SCA, the FATF travel rule, and sanctions-screening obligations across 249 frameworks.
- Finality you can defend. A high-risk or irreversible payout can require a second approver or be held from Authority Finality™ until authority is re-anchored — contestable later, never deniable.
For platforms, PSPs, and commerce teams
If you build or operate AI commerce agents, you carry the liability when one charges, refunds, or remits incorrectly. The Pack gives you a defensible answer — for every money action, who authorised it, for whom, under what limits, under which policy, at what moment — that a card scheme, a regulator, or a board will accept.
Commerce-agent platforms & marketplaces
Offer your customers authority + proof on every agent-initiated order, refund and payout — a governance layer you can sell, not rebuild.
PSPs & remittance providers
Differentiate on provable authorisation for agentic payments and cross-border flows, with an Evidence Pack™ your compliance team can replay offline.
Start a governed pilot Explore the KYE™ Sector Pack Foundry™
Honest boundary. The KYE™ Commerce & Payments Authority Pack™ governs whether an agentic money action may proceed and proves it; it does not move, hold, or settle funds, does not decide whether a transaction is fraudulent, and does not replace your payment service provider, sanctions vendor, or compliance program. KYE Protocol™ governs actions and authorities, not outcomes.
Canonical KYE™ surfaces referenced on this page: KYE Protocol™.