Blog / Agentic commerce

Payments made by an AI agent: who answers when an order goes wrong?

In eighteen months, card networks, Google, OpenAI, Stripe and Coinbase published what an agent needs to pay. These tools prove what was authorised. They do not say what the company was entitled to let its agent decide, nor who answers for a purchase nobody really wanted.

By Vincent Dorange, , 3 min read

14 Jul 2026

the x402 Foundation starts at the Linux Foundation to standardise agent payments

On 14 July 2026 the Linux Foundation announced the operational launch of the x402 Foundation, which will standardise a protocol born at Coinbase to pay directly over the web through the HTTP 402 "Payment Required" status code 1. It is the latest piece of an infrastructure built in eighteen months. Mastercard unveiled Agent Pay on 29 April 2025 2 and Visa its Intelligent Commerce programme the next day 3. Google published the Agent Payments Protocol (AP2) on 16 September 2025 4, Stripe and OpenAI the Agentic Commerce Protocol (ACP) on 29 September 5, and the Universal Commerce Protocol (UCP) followed in January 2026 6.

What these tools settle

They do not all play the same part. In its opinion of 17 July 2026, France's competition authority singles out UCP and ACP as the two main protocols of agentic commerce: the first relies on the merchant declaring its capabilities and the payment methods it accepts; the second asks the merchant to join a programme and expose interfaces that go all the way to the order and the payment 6. AP2 and x402 carry the payment itself. Visa and Mastercard, for their part, are adapting their networks so that agents are registered and consumers set limits and conditions.

AP2 is the most instructive for anyone who cares about governance. It has users sign mandates that first record their constraints, such as a budget or accepted payment methods, then the authorisation of a specific purchase 4. The mandates chain together into a verifiable trail, whether or not the user is present at the moment of purchase. Its documentation itself raises the underlying question: who is accountable if a transaction turns out to be fraudulent or wrong, the user, the agent's developer, the merchant, the issuer or the payment provider?

What payment law says

French law reasons in terms of the payer's consent. Article L133-6 of the Monetary and Financial Code treats a transaction as authorised if the payer consented to its execution, and allows a series of transactions to be authorised as a whole 7. For an unauthorised transaction, Article L133-18 requires the provider to refund immediately, at the latest by the end of the next business day, unless it suspects fraud and informs the Banque de France 7. Article L133-19 leaves the payer liable for up to €50 when the instrument was lost or stolen before it was blocked, and for all losses in case of fraud or gross negligence on the payer's part 7.

These rules were written for a person holding a card. An agent that buys within the limits of a signed mandate carries out a transaction the payer consented to, even if the result disappoints. An agent that exceeds its mandate raises a question that neither the protocols nor the texts settle clearly yet: is it an unauthorised transaction, or negligence by whoever drafted an overly broad mandate? Until the courts answer, a company's best protection remains a carefully written mandate, together with proof that it was enforced.

What the ACF asks you to write before paying

The Agentic Commerce Framework® starts from the decision before the tool. Before an agent is connected to a payment protocol, it asks for the agent's mandate to be written: the purchases it may make alone, those it must submit to a human, the figure-based limits of each, and the decisions that are never delegated. The criticality of each decision, computed as (impact × frequency × irreversibility) ÷ 10, shows where to place human approval. An irreversible payment to an unknown supplier is not handled like a subscription renewal.

The same reasoning applies to a merchant whose agent answers a customer's agent: a goodwill gesture, a late return accepted or a price conceded are delegated decisions like any other. They need a named owner, whom the ACF calls the DDAO, along with an audit trail that lets each of them be traced on the day an order is disputed.

Sources

Links to the official texts and original publications.

  1. 1Linux Foundation Announces Operational Launch of x402 Foundation, Linux Foundation, 14 July 2026.
  2. 2Mastercard unveils Agent Pay, Mastercard, 29 April 2025.
  3. 3Visa Intelligent Commerce, Visa, 30 April 2025.
  4. 4Agent Payments Protocol (AP2), Google, AP2 project, announced on 16 September 2025.
  5. 5Developing an open standard for agentic commerce, Stripe, 29 September 2025.
  6. 6Opinion 26-A-05 on the competitive functioning of the AI agent sector (in French), Autorité de la concurrence, 17 July 2026.
  7. 7French Monetary and Financial Code, Articles L133-6, L133-18 and L133-19 (in French), Légifrance, wording from Ordinance No. 2017-1252 of 9 August 2017.

Glossary terms used in this article

AI agent mandateNon-delegable decisionsDecision criticalityDDAO (Delegated Decision Agent Officer)AI audit trail

Vincent Dorange, creator of the Agentic Commerce Framework®

Also worth reading

95%

of organisations surveyed faced at least one agent-related incident in 12 months

Governance

95% of organisations have already had an AI agent incident, says Gartner

25

organisations interviewed; none lets its agents act with unrestricted autonomy

Governance

AI agents at work: what the OECD learned from 25 organisations

4 levers

transaction caps, budgets, approved counterparties and escalation rules, per Circle

Agentic economy

Agentic economy: agents that spend within delegated permissions

All articles