Quiet news day on the network side, so today is about the layer underneath: who vouches for the agent, which protocol the merchant integrates against, and what a stablecoin issuer has to hold in reserve when the rules land on Saturday.

Nuvei put the payment inside the agent

On 2 July, Nuvei ran a live agentic proof of concept with Visa, Arvato Systems and the fashion brand Kings and Priests, in which a merchant's own agent initiated the purchase and took the payment inside the agent, with no hand-off to a separate checkout flow [1]. It settled on live Visa rails with a tokenised credential inside Visa Intelligent Commerce, under shopper-set guardrails such as spend caps and approved categories, with multiple European issuers authorising [1].

The word worth stealing from the announcement is Know Your Agent. Nuvei is building a registry that credentials agents, validates the consumer's mandate, scores agent reputation and keeps the actions auditable [1]. That is KYC re-pointed at software, and it is the piece nobody's demo has.

Three protocols, one merchant integration

The other half of the Nuvei plan is a compatibility layer so a merchant integrates once and accepts agents speaking ACP, AP2 or MCP, routed across networks, with certification against both Visa Intelligent Commerce and Mastercard Agent Pay [1]. General availability is targeted for the second half of 2026, including the KYA registry, agent risk scoring and a developer sandbox [1]. Three competing protocols and a translation layer is not a standard. It is the interregnum before one.

The OCC has put a number on it

Ahead of Saturday's GENIUS Act deadline, the OCC's proposed rule sets a five million dollar minimum capital floor for new federally approved stablecoin issuers, with a tiered liquidity framework requiring ten per cent same-day redemption capability [2]. The FDIC has confirmed token holders do not get deposit insurance, whether or not the issuer is bank-affiliated [2]. Comment periods have closed and six agencies now have to reconcile six proposed frameworks into final rules by 18 July [3].

Read from the rails

Every payments system eventually asks the same question: when this goes wrong, who do I call, and what did they agree to? Card rails answered it with the issuer, the scheme and the merchant of record. Agentic commerce has been trying to skip that step, and Nuvei's registry is the first honest admission that you cannot. An agent needs an identity, a mandate you can point to, and a log you can replay.

Ten years in operations taught me that a payment you cannot reconstruct is a payment you cannot defend. That is what the KYA idea is really for. Not fraud prevention on the way in, but the ability to answer, three weeks later, why this agent bought this thing on this mandate. If you are building agent checkout and you have no audit trail of the mandate, you have built a demo.

An agent without a credential is not a customer. It is an anonymous request with a card number attached.

Building in agentic commerce or payments?

This is the intersection I work in. Book thirty minutes and we will scope the build worth doing.

Book an AI consultation