Visa, Mastercard and Ant make KYA interoperability a payment-network problem
The September 10 KYA signal is no longer only merchant consent or wallet spending limits. Reuters, carried by The Straits Times and Business Recorder, reports that Ant International, Mastercard and Visa have begun collaborating on a Know-Your-Agent interoperability framework for trusted AI agents across payment ecosystems.
Daily signal: Discord channel 1468032405695627386 was readable for the source-priority check. The last-24-hour messages surfaced self-hosted company OS work with Claude Code and Codex agents, procedural execution structures for LLM agents, Microsoft ASCII-smuggling spam, autonomous-car safety, Apple product news, and general technology research, but no direct regulator or exchange KYA adoption notice. Web fallback limited to the last 24 hours found payment-network KYA interoperability, Coinbase agent accounts, PCI Pal MCP payments, Binance Agent OS, Aave MCP, and blockchain-payment infrastructure signals. The payment-network story explicitly uses Know-Your-Agent, but it is an industry interoperability initiative, not enacted regulation.
Why this matters for KYA
The Straits Times report says Ant International, Mastercard and Visa launched an initiative to develop common standards to identify and verify AI agents that can make purchases on behalf of users. The companies described a Know-Your-Agent interoperability framework that would let card networks, digital wallets, agent platforms and online marketplaces recognize trusted AI agents across payment ecosystems while keeping their own approval and risk-management processes.
This is a material shift in the KYA timeline. Earlier agentic-payment controls were mostly local: a wallet issuer set a spending limit, a merchant accepted a signed intent, a protocol required a payment proof, or an exchange assigned an AI agent to a subaccount. Interoperability creates a harder control question: when an agent moves from one wallet, card network, marketplace, or platform to another, what proof should travel with it?
The framework is also notable because it builds on three existing payment-agent primitives: Visa's Trusted Agent Protocol, Mastercard Verifiable Intent and Ant International's Agentic Mobile Protocol. Those names point to adjacent layers of the same evidence file. A trusted-agent record identifies the non-human actor; verifiable intent ties the action to a user-approved purpose; a mobile-agent protocol defines how agent actions can operate in app and wallet environments. KYA becomes the common control file that can translate those layers for risk teams.
The Reuters-carried report adds that the collaboration will run through BuildFin.ai, a platform convened by the Monetary Authority of Singapore for financial-services AI solutions. That does not make the framework a MAS rule. It does, however, give the initiative an APAC financial-sector venue and makes it relevant for banks, wallets, payment firms, marketplaces and compliance teams planning cross-network agentic commerce.
The surrounding September 10 signals point in the same direction. CoinTurk reports Coinbase is developing Coinbase for Agents, with AI systems connecting through an MCP server and receiving segregated subaccounts, daily transaction limits and per-agent caps. CFOTech reports PCI Pal launched an MCP server so banks and contact centres can let AI-led interactions access payment functions while keeping card data outside AI systems and preserving PCI-DSS controls. FutureCIO reports Binance Agent OS brings together APIs, wallet capabilities, x402 payments, Skill Hub and MCP support, with permissions, limits, dedicated subaccounts and revocation. PANews reports Aave launched an official MCP server that lets AI agents access real-time protocol data and prepare transactions while users retain signing control.
None of these supporting items should be described as a regulator or exchange adopting formal KYA unless the source says so. The stronger point is that agent identity, mandate, wallet scope, tool access, audit trails and jurisdictional responsibility are converging across card networks, wallets, exchanges, DeFi protocols and payment software. KYA is becoming an interoperability artifact.
Screenshot-ready KYA compliance comparison table
| KYA dimension | Single-network agent posture | Interoperable payment-network posture | Evidence reviewers should expect |
|---|---|---|---|
| Operator identity | The wallet, marketplace, merchant or agent platform identifies the AI agent only inside its own environment. | The KYA record carries a stable agent identifier, platform issuer, wallet or card credential, marketplace role, approval status and accountable operator across participating ecosystems. | Agent ID, operator entity, platform certificate or registry entry, wallet/card token reference, marketplace ID, approval status, owner contact, suspension and revocation history. |
| Agent mandate | User intent is captured as a local checkout approval, shopping instruction, app permission or payment limit. | The mandate travels as a verifiable intent object that states user, purpose, merchant or category, amount, frequency, validity window, allowed substitutions and dispute route. | Mandate version, signed intent, consent screen, purpose label, merchant/category scope, amount cap, expiry, renewal, revocation event, exception approval and complaint path. |
| Wallet and custody | The agent is funded through one wallet, card token, exchange subaccount, stablecoin balance or local payment credential. | The payment network can recognize which funding source, custody model, spending limit, signer rule, settlement rail and recourse model applies before accepting agent-initiated payment. | Funding source, tokenized credential, wallet or subaccount scope, daily and per-transaction cap, signer rule, settlement proof, refund route, chargeback or no-recourse flag, reconciliation log. |
| Tool and venue access | The agent's tool scope is hidden inside one MCP server, API key, merchant integration, browser session or exchange product. | Each tool, merchant, marketplace, card network, wallet endpoint, exchange API, MCP server and protocol call is allow-listed, authenticated, risk-rated and visible to the relying party. | Allowed tools, MCP server identity, API scope, merchant and marketplace endpoint, exchange or DeFi venue, OAuth/session scope, denied-call log, risk label, terms reference. |
| Audit trail | The record shows a local payment receipt, order ID, trade, card authorization, x402 proof or prepared transaction. | The audit trail links user intent, agent identity, relying network, merchant response, payment credential, policy verdict, settlement evidence and post-transaction outcome. | Invocation ID, timestamp, intent object, policy decision, network authorization, fraud or source-verification verdict, payment proof, receipt, delivery check, refund/dispute status. |
| Security and abuse | Prompt injection, fake merchant pages, credential leakage, unauthorized MCP tools and disguised automation are controlled by separate local systems. | The framework lets participants share enough trust and risk signals to block suspicious agents without disclosing unrelated model reasoning or personal data. | Trust score or status, source-verification result, MCP or tool scan, credential TTL, data-minimization record, blocked-action reason, anomaly alert, kill switch, incident ticket. |
| Jurisdiction fit | The same agent flow is reused across markets even though card rules, wallet licensing, consumer consent, data localization, refunds and AI governance differ. | The KYA file records customer location, merchant location, network rules, wallet role, data host, consent standard, records retention, dispute owner and liability owner by jurisdiction. | Jurisdiction matrix, payment-service role, BuildFin.ai or local sandbox note where relevant, privacy basis, merchant terms, records-retention rule, customer redress route, liability assignment. |
The compliance lesson
A Know-Your-Agent interoperability framework changes KYA from an internal control checklist into a relying-party problem. A card network, wallet, marketplace or merchant will not want to rebuild every agent review from scratch. It will want a compact and trustworthy record showing that the agent is known, approved for the task, operating under a bounded mandate, using a permitted payment credential, and producing enough evidence for fraud, disputes and regulatory review.
The hard design choice is how much of the agent file should travel. Too little evidence turns KYA into a badge. Too much evidence exposes model reasoning, user data, merchant strategy or security telemetry to counterparties that do not need it. The useful middle layer is an interoperable control envelope: identity, mandate, payment scope, tool scope, policy verdict, receipt, revocation status and jurisdiction tags.
For APAC teams, the BuildFin.ai reference matters because it places the work near financial-sector AI experimentation rather than generic e-commerce automation. Banks, payment institutions, wallet operators and marketplaces should assume that agentic commerce will need machine-readable controls before it reaches scale.
Practical KYA checklist
- Define which agent identity attributes must be portable across wallets, card networks, marketplaces and agent platforms.
- Separate agent recognition from agent authorization: a known agent still needs a task-specific mandate, amount limit, merchant scope and expiry.
- Make user intent verifiable without exposing the full prompt, model chain of thought, browsing history or unrelated account data.
- Bind every payment credential, wallet scope, exchange subaccount, x402 proof or MCP payment function to a named agent and revocable authority.
- Preserve enough audit evidence for disputes: who authorized the agent, what the agent was allowed to do, what it did, what network approved it, and what merchant delivered.
- State the caveat clearly: the September 10 payment-network source describes a KYA interoperability initiative, not a finalized regulatory rule.
Bottom line
Visa, Mastercard and Ant International put the KYA question at network scale: can one ecosystem trust another ecosystem's agent without losing its own risk controls? The answer will depend on interoperable evidence for operator identity, agent mandate, wallet and custody, tool and venue access, audit trail, security and abuse, and jurisdiction fit.
Sources reviewed: Discord channel 1468032405695627386 for the last-24-hour source-priority check; The Straits Times / Reuters and Business Recorder coverage of Ant International, Mastercard and Visa collaborating on a Know-Your-Agent interoperability framework; CoinTurk coverage of Coinbase for Agents; CFOTech coverage of PCI Pal MCP payments; FutureCIO coverage of Binance Agent OS; PANews coverage of Aave MCP; Crypto Economy coverage of blockchain-payment infrastructure. These are industry, product, developer and market signals, except where the payment-network story explicitly describes a KYA interoperability initiative.