How can banks recognize AI shopping? Mastercard tests a new Agent Pay score

When an AI agent starts a purchase, how can the bank issuing the buyer's card understand what is happening?

On September 30, 2026, Mastercard announced a probability score indicating whether a transaction was initiated by an AI agent. Testing has begun in the United States. The score supplies context for issuers assessing a payment; it does not, by itself, prove that the buyer authorized the purchase. Mastercard announcement

For merchants, that distinction matters. This article explains what the score addresses, how it differs from consent, and what to ask a payment provider before planning an implementation.

Mastercard adds context to agentic commerce payments

Agentic commerce includes purchases in which an AI agent carries out steps on a person's behalf. A bank assessing such a transaction may need context about how it began, alongside the information it already uses to make a payment decision.

The announcement expands the trust and intelligence services associated with Mastercard Agent Pay, the company's approach to agentic payments. It should not be read as a merchant integration guide or a claim that every checkout already supports the new capability.

The score estimates whether an AI agent initiated a transaction

The announced score concerns the likely origin of a transaction: was it initiated by an AI agent? Mastercard positions it as information for card issuers. It is not a published probability that the transaction is fraudulent. Official announcement

An agent can initiate a legitimate purchase, but knowing that an agent acted does not establish what the customer allowed it to buy. Those questions require different evidence.

US testing does not establish availability elsewhere

The September announcement specifies testing in the United States. It does not establish general availability for Japanese merchants, or support under every Mastercard acceptance agreement. The reviewed materials do not provide a Japanese launch date or a public score threshold merchants can configure. Official announcement

Start with the payment provider responsible for your actual checkout. Ask which capabilities are available under your contract and whether access would require participation in a trial.

Agent initiation, customer consent, and payment approval are different

Three questions often become blurred: did an agent initiate the transaction, did the customer authorize that purchase, and should the issuer approve the payment? A useful implementation needs to keep their answers separate.

A request to search is not necessarily permission to buy

Consider a customer asking an assistant to find a pair of shoes. The request may permit a search without allowing the assistant to spend money. Even permission to buy could carry conditions about the product or price.

Mastercard's Agent Pay materials discuss verified customer intent and explicit consent. The newly announced probability score should not be interpreted as a replacement for those controls. Agent Pay product overview

Question	Example of relevant information
Did an agent initiate the transaction?	Information about its likely origin
Did the customer allow this purchase?	The scope and record of the customer's permission
Should the payment be approved?	Transaction information and risk assessed by the issuer

This is an explanatory comparison, not Mastercard's API field specification.

Five aspects of trust help frame the wider problem

Mastercard describes five pillars for trust in agentic commerce: identity, intent, controls, trusted execution, and intelligence. Together, they address who is acting, what they are trying to do, the limits on their actions, safe execution, and informed decisions. Mastercard trust framework

For a merchant, the practical question is which of these checks the purchase process actually performs. Ask where the customer's permission is recorded and who can retrieve it if the customer disputes what happened.

A travel booking illustrates why payment context matters

The following is a hypothetical example, not a reported merchant result. Imagine a customer asking an agent to arrange a flight and hotel for one trip.

Separate payments can belong to one customer request

The customer has made one request, but the airline and hotel may require separate payments. Looking at either transaction alone does not explain how both relate to the trip.

Information about the customer's instructions can supply that context. Mastercard's announcement also uses travel arrangements to illustrate why related purchases need to be understood together. It does not report a measured improvement in approval rates for this example. Official announcement

Further confirmation is not the same as payment approval

If the hotel exceeds the agreed budget, the customer may need to approve the change. That approval still does not guarantee that the card payment will succeed.

In a merchant's operational records, distinguish a purchase waiting for the customer's response from a declined payment or an order that failed after payment approval. Each situation calls for a different response. This is an operational suggestion, not a claim about the screens or processing sequence that Agent Pay provides.

What merchants should ask before adopting agentic payments

A product announcement is a starting point for questions about your checkout, contract, and support process. The following checklist is an editorial suggestion, rather than an official Mastercard enrollment procedure.

Confirm availability and the information your provider returns

Topic	Questions for your payment provider
Availability	Does our contract and checkout qualify? Is a trial required?
Returned information	Can we receive agent-related information or reasons for additional review?
Consent records	Who keeps the customer's authorization record, and who can investigate a complaint?
Implementation	What changes, costs, and prerequisites apply to our store?
Cancellations and returns	Does an agent-initiated order change the support process or required records?

Use your current checkout and contract as the basis for the discussion. If a provider says support is planned, record that separately from a confirmed availability date.

Locate the interruption using order and payment records

A purchase that fails to become revenue did not necessarily fail at card authorization. The visitor may have left before checkout, rejected the delivery conditions, or encountered a problem after a successful payment.

Where records can be matched, compare checkout progress, the payment result, and completed orders. A successful payment without a completed order points to a different investigation from a declined payment. Do not treat both as a single conversion problem.

AgentSignal's information about AI-related traffic and on-site behavior serves a different purpose from issuer authentication and payment approval. Combine relevant site observations with order and payment records when investigating what happened to a purchase.

The immediate preparation is practical: clarify what your provider supports and make sure you can identify where an order stopped.