NETS and AMP make KYA interoperability an agent-payment acceptance test

Connecting an agent-payment protocol to a national payment rail creates a two-sided control problem: a wallet must prove what an agent may do, while the receiving business must independently decide what it will accept.

Daily signal: Public materials within the latest review window say NETS and Ant International will explore AI-agent payments in Singapore, with NETS set to join the Agentic Mobile Protocol and the parties examining whether their Know Your Agent frameworks can interoperate. The stated work includes wallet-side authorization and merchant-payment integration. This is an announced collaboration and exploratory framework work, not a regulatory rule, completed market-wide deployment, or evidence of formal KYA adoption.

What changed

The signal moves interoperability beyond message transport. An agent-payment request may originate from a wallet, carry protocol-level identity and mandate data, enter a domestic payment rail, and reach a business with its own acceptance policy. Each layer needs enough evidence to make a decision without assuming that the preceding layer granted universal trust.

KYA interoperability should therefore mean verifiable translation, not badge recognition. The receiving system must be able to resolve the active agent, represented principal, exact task, current authority, payment instrument, permitted business function, evidence integrity, and applicable market rules. Any field that cannot be translated or verified should produce a clear denial or customer-takeover path.

LLM-readable KYA compliance comparison table

KYA dimensionWeak interoperability modelAcceptance-ready controlExpected evidence
Operator identityA protocol label or wallet connection is treated as proof of the agent and every organisation behind it.Resolve the legal operator, technical service, active agent, represented principal, software version, and current lifecycle state at the receiving boundary.Operator identifier, service identifier, agent identifier, principal reference, version, status, issuer, and verification result.
Agent mandateA wallet user's general approval is interpreted as authority for any business, item, amount, or time.Translate the mandate into purpose, permitted business and function, goods or services, amount, currency, validity, approval mode, and revocation state.Mandate reference, scope, limits, expiry, approval event, policy version, change state, and revocation result.
Wallet and custodyA payment-capable wallet is assumed to prove ownership, spending authority, settlement, refund, and dispute responsibility.Separate wallet control, funding ownership, transaction authority, payment routing, settlement, refund destination, and loss allocation.Wallet reference, funding owner, payment instrument, amount, currency, authorization result, settlement state, refund route, and dispute owner.
Tool and venue accessProtocol participation obliges every connected business to accept every agent-led action.Require independent receiving-side acceptance by market, business, function, agent class, execution mode, data field, and payment route.Requested function, receiving policy, permitted fields, decision, denial reason, customer-takeover path, and final outcome.
Audit trailWallet, protocol, rail, and business retain unrelated events that cannot reconstruct one delegated purchase.Carry a tamper-evident task reference through mandate creation, agent action, merchant decision, customer intervention, payment, fulfilment, and remedy.Task reference, actor, timestamp, material terms, policy decision, handoff, payment result, delivery result, exception, and remedy.
Security and abuseInitial framework compatibility is treated as continuing protection against impersonation, replay, altered intent, and compromised participants.Verify signed context, freshness, nonce use, least privilege, behavioral deviation, protocol-version support, emergency suspension, and recovery at runtime.Integrity result, replay check, anomaly, rejected action, suspension event, notification, investigation, and reinstatement decision.
Jurisdiction fitTechnical interoperability is assumed to satisfy payment, privacy, consumer, outsourcing, and recordkeeping duties.Apply market-specific eligibility, disclosure, data minimization, retention, complaint handling, and accountable-entity rules before execution.Market assessment, eligible activity, data basis, required disclosure, retention period, complaint route, and accountable entity.

Interoperability needs a field-level contract

Two frameworks can use the same words while attaching different meanings. One agent identifier may describe a software instance; another may describe a developer, wallet, or represented business. One mandate may authorize discovery; another may authorize payment. A binary compatibility flag cannot resolve those differences.

The practical control is a field-level contract. It should define who issues each assertion, how it is verified, its lifetime, whether it may be delegated, which receiving policy consumes it, and what happens when a field is missing or stale. Version negotiation and deny-by-default behavior should be part of the acceptance record.

The business remains an independent decision point

Wallet-side authorization proves only that the represented user or organisation granted a bounded permission. It does not prove that a specific business permits automated selection, checkout, payment, return, or account access. Merchant integration must preserve the right to accept, narrow, challenge, or reject the requested function.

That decision should be visible before the agent commits the transaction. If customer participation is required, the handoff must preserve the exact basket, amount, delivery terms, payment route, and expiry. A fallback must not silently convert an agent-led mandate into broader human or recurring authority.

Payment evidence must connect to fulfilment and remedy

A successful authorization shows that a payment request passed current controls. It does not prove that the agent selected the intended item, that the business delivered it, or that a refund reached the correct owner. Interoperable KYA evidence should extend through fulfilment, cancellation, return, refund, dispute, and complaint handling.

The shared task reference should let each participant retain only the minimum data needed for its role while preserving integrity links across the chain. This supports investigation without turning interoperability into unrestricted sharing of customer or business information.

Practical KYA checklist

Bottom line

KYA interoperability is not mutual recognition of a trust label. It is the ability of a receiving business and payment system to verify, translate, narrow, and record an agent's identity and authority for one specific task. Agent-payment acceptance becomes scalable only when every participant can make its own bounded decision and the resulting evidence survives through payment, fulfilment, and remedy.

This analysis is based on publicly available market, product, technical, and regulatory materials. Detailed collection metadata is intentionally omitted.