# Mastercard and Antom test what AI agents can pay for

> Mastercard and Antom report a coffee purchase with Verifiable Intent and a business payment pilot. Here’s what each shows about approval and spending limits.

- Source: https://www.agentic-commerce.sh/en/news/mastercard-antom-agent-pay-singapur/
- Author: Stefan Hamann
- Updated: 2026-11-21
- Language: en

## The coffee is paid for. What was the agent allowed to order?

A cup of coffee takes seconds to pay for. In the purchase Mastercard and Ant International announced on 19 November, the interesting bit happened earlier. The customer had set out what the agent could do. The agent then bought the coffee. The payment used Mastercard Agent Pay with Verifiable Intent, with Antom supporting acceptance. The companies say the transaction created a record of the approval that could be verified afterwards.

The same question comes up with the suitcase in [Chapter 8 of my book](https://www.agentic-commerce.sh/book/en/08-from-the-offer-to-the-service-that-follows/). The traveller approves a specific offer. The delivery date matters as much as the price, and the shop and payment provider need to connect the eventual purchase to that decision. A coffee makes this easy to picture. If something in the order changes on the way through, what can the assistant still do with the approval it already has?

## What does the coffee purchase show about Mastercard Agent Pay?

[Ant International’s announcement](https://www.ant-intl.com/en/news/detail/mastercard-and-ant-international-advance-trusted-agentic-commerce-in-asia-pacific/) describes a live transaction based on an instruction captured before the agent acted. It does not give the merchant, price or the exact limits of that instruction. [Verifiable Intent](https://verifiableintent.dev/) describes how to link delegation to the scope a person approved, in a form that can be checked cryptographically afterwards. The public specification is still labelled draft v0.1. The coffee purchase is a concrete use of Mastercard and Antom’s integration. The announcement gives no date for broad merchant availability.

[Yeahka and Mastercard showed a separate flow at the Singapore FinTech Festival](https://web26.bernama.com/en/press/news.php?id=2637045). An assistant found somewhere to order bubble tea, showed the choices and toppings, then initiated the payment through YeahPay after the customer confirmed. The small decisions are where this gets interesting for merchants. Change the size or add a topping and the price may change. Give the agent the exact variant and total, and make sure there’s a way to check them against what the customer approved.

## What did the Agent Pay for Machines pilot test?

The other result announced in Singapore concerned a business buying digital services. Antom says it completed a pilot with Mastercard Agent Pay for Machines, or AP4M. It reports that an agent used its own credentials and policy controls to buy digital services within the business’s rules. Mastercard [introduced AP4M in June](https://s25.q4cdn.com/479285134/files/doc_news/Mastercard-Launches-Agent-Pay-for-Machines-to-Unlock-Super-Fast-Always-On-Payments-2026.pdf). The completed partner pilot is the development here. The companies give no details about which service the agent bought or when this setup would be widely available.

Imagine an agent checking addresses for a team. The business authorises one provider and a monthly allowance. It still has to decide if the agent can buy individual checks or sign up for a bundle next month. [AWS Marketplace’s x402 payments](https://www.agentic-commerce.sh/en/news/aws-marketplace-agentcore-x402/) address a different part of that purchase. Eligible requests can land on the company’s existing AWS bill. Either way, I want to be able to follow a line on the bill back to the job the team asked the agent to do.

## What I’d test before enabling agent payments

Take a simple purchase and change exactly one condition after approval. A larger coffee could add a surcharge. A one time digital service could turn into a subscription. The merchant needs to see which amount and item or service were approved. The payment provider should know which limits it can enforce. If the changed offer falls outside the original approval, the agent should stop and bring the new choice back to the customer.

My [guide to shopping agent spending limits](https://www.agentic-commerce.sh/en/guides/who-enforces-a-shopping-agent-budget/) takes that test through to the payment confirmation. I’d also ask someone in support to find the case from the order number alone. If they can bring the original approval, the order and the payment together, they can still explain what happened after the conversation has moved on.

## Source and further reading

[Read the original announcement ↗](https://www.ant-intl.com/en/news/detail/mastercard-and-ant-international-advance-trusted-agentic-commerce-in-asia-pacific/)

[Read the related Agentic Commerce guide ↗](https://www.agentic-commerce.sh/en/guides/who-enforces-a-shopping-agent-budget/)

[The Agentic Commerce handbook ↗](https://www.agentic-commerce.sh/book/en/)
