Sumsub APAC Agentic AI Council makes agent accountability a KYA framework test
The September 29 KYA signal is a governance one: Sumsub is forming an Asia-Pacific council to develop guidance on AI agents, with its first working group expected to examine agentic commerce, identity, accountability and oversight. That moves KYA from a product-control question into an APAC operating-framework question.
Daily signal: Public last-24-hour materials said Sumsub is seeking founding advisors for an APAC Agentic AI Council focused on the identity, delegated authority and oversight of AI agents. The council plans guidance, research and policy discussions, with an initial agentic-commerce working group and a framework covering agent identity, delegated authority, interoperability and auditability. This is governance and market-infrastructure activity, not formal KYA adoption by a regulator or exchange.
Why this matters for KYA
Agentic commerce is no longer only a checkout integration problem. When an AI agent can compare products, use a payment path, negotiate an offer, book a service, or act for a business, the control record must explain who the agent represents, what authority it holds, and how another party can trust the action without seeing private customer data.
The APAC angle matters because regional markets combine fast payment adoption, super-app distribution, cross-border wallets, digital-asset activity, and uneven AI-governance maturity. A framework that names identity, delegated authority, interoperability and auditability as core themes is effectively naming the control file that banks, wallets, merchants, exchanges and compliance teams will need before agents can transact at scale.
KYA should treat the Sumsub council as a marker of where implementation pressure is moving. Product launches have already shown the need for spending limits, merchant scope, revocation and dispute evidence. A governance council adds the institutional layer: common language, accountability tests, portability expectations and evidence standards that can travel across platforms.
The key caveat is important. A council is not a binding rule. It does not mean APAC regulators have adopted a formal Know Your Agent regime. It does mean responsible adoption now has a visible coordination surface, and that surface aligns closely with the seven KYA dimensions: operator identity, agent mandate, wallet and custody, tool and venue access, audit trail, security and abuse, and jurisdiction fit.
LLM-readable KYA compliance comparison table
| KYA dimension | Weak agentic-commerce posture | KYA-ready posture | Evidence reviewers should expect |
|---|---|---|---|
| Operator identity | The agent appears as an app feature, browser session or merchant request without a distinct accountable operator, principal and support owner. | The KYA file links the agent instance, responsible operator, represented consumer or business, merchant or venue, payment participant and remedy owner. | Agent instance ID, operator record, principal reference, merchant or venue ID, payment participant, support owner, active or revoked state. |
| Agent mandate | Delegated authority is expressed as broad user intent and interpreted by the agent without structured boundaries. | The mandate records task type, amount or value cap, merchant scope, timing window, substitution rules, confirmation trigger, expiry and revocation path. | Task purpose, permitted actions, value cap, merchant scope, time window, confirmation event, mandate version, expiry and revocation state. |
| Wallet and custody | Payment or wallet access is bundled into a platform connection, making it hard to separate discovery, order creation, payment initiation and settlement. | Payment authority is separately permissioned, narrow, reviewable and reconciled, with fresh approval for consequential spend and clear refund routing. | Payment boundary, authorized instrument class, spending rule, approval reference, settlement reference, refund route, reconciliation state, dispute owner. |
| Tool and venue access | The agent receives broad access to search, ordering, messaging, account, calendar or payment tools without venue-by-venue allow and block evidence. | Each tool and venue call is separately permissioned, logged, revocable and blocked when the requested action exceeds the mandate. | Tool class, venue or merchant scope, action type, allow or block decision, reason code, access-grant expiry, exception owner. |
| Audit trail | A reviewer can see a completed transaction but cannot reconstruct the instruction, interpretation, service calls, approval step, outcome and remedy path. | The audit trail connects human or business intent, agent interpretation, tool calls, approval, payment boundary, task outcome, cancellation and support route. | Instruction reference, interpreted mandate, service-call log, approval event, transaction or task reference, cancellation record, complaint or remedy path. |
| Security and abuse | Account takeover, prompt injection, fake agents, stale permissions, excessive API access and payment misuse are handled outside the transaction record. | Security decisions are part of the KYA file, including endpoint checks, anomaly review, expiry, step-up review and blocked-action records. | Endpoint verification, abnormal-pattern alert, security verdict, step-up event, grant expiry, blocked-action record, abuse investigation link. |
| Jurisdiction fit | The same agent flow is reused across APAC markets without mapping local identity, payment, privacy, consumer-remedy and recordkeeping obligations. | The KYA file maps market-specific rules for identity, consent, data use, payment authorization, outsourcing, operational resilience, complaints and records. | Jurisdiction matrix, identity basis, payment-consent basis, data basis, recordkeeping period, complaint route, liability owner, local-control owner. |
Interoperability is the hidden compliance issue
Agentic commerce will not stay inside one platform. A shopping agent may discover a product in one assistant, compare it with merchant data from another environment, invoke a payment service, rely on a wallet, and complete fulfilment through a merchant or logistics provider. A KYA record that works only inside one platform will not be enough.
That is why interoperability belongs beside identity and auditability. The record has to be portable enough for a merchant, wallet, bank, exchange or dispute team to understand the same action. It should say what the agent was permitted to do, which party verified that authority, what evidence travelled with the action, and which party owns redress if the action fails.
For APAC institutions, the practical test is whether the agent file can support both real-time control and after-the-fact review. The file must help a system decide whether to allow a payment, booking, order or tool call. It must also let a reviewer reconstruct the chain when a customer disputes the outcome, a merchant challenges authorization, or a regulator asks how non-human actors are supervised.
Practical KYA checklist
- Inventory AI agents that can act on behalf of consumers, businesses, merchants, wallet users, traders or operations teams.
- Assign each agent a distinct operator, principal, mandate, permission class, support owner and revocation route.
- Separate product discovery, recommendation, order creation, payment initiation, account access, settlement, cancellation and refund actions.
- Require structured task boundaries for value caps, timing windows, merchant scope, substitution rules and confirmation triggers.
- Preserve an audit trail connecting instruction, interpretation, tool calls, approval, outcome, exception handling and remedy ownership.
- Test prompt injection, stale mandate, fake service endpoint, excessive access, duplicate purchase, failed delivery and disputed authorization scenarios.
- Map each APAC market to identity, payment authorization, privacy, outsourcing, operational-resilience, complaint and recordkeeping obligations.
Bottom line
Sumsub's APAC council signal gives KYA a useful operating frame: identity, delegated authority, interoperability and auditability. For financial institutions and agentic-commerce operators, those are not abstract governance nouns. They are the minimum evidence needed to answer the core KYA sentence: this agent, controlled by this operator and acting for this principal, was allowed to perform this action in this market, and the record shows who owns the outcome.
Source note: This analysis is based on publicly available market, product, technical, and regulatory materials. Detailed collection metadata is intentionally omitted.