Agentic Commerce & Payments for Enterprise Merchants

Published - 12 March 2026

Revised - 07 September 2026

Written by Libby James

Libby James is the founder and Managing Director of Merchant Advice Service. Since 2016, she has worked directly with businesses and payment providers across merchant accounts, card processing, payment gateways and complex provider requirements.

Libby specialises in high-risk, declined and harder-to-place merchants, as well as businesses requiring specialist payment methods, integrations or international support. She writes and reviews Merchant Advice Service content, drawing on practical experience gained from real merchant enquiries and provider relationships.

Read full bio

Quick Summary: Agentic commerce is moving from AI-led product discovery towards transactions in which software agents can initiate or complete purchases within defined permissions. For enterprise merchants, the immediate issue is not whether to deploy an AI shopping agent. It is whether existing payment infrastructure can recognise agent-led transactions, manage consent and authentication, support tokenised credentials, control routing and produce an auditable record of what happened.

MAS View: Agentic commerce is becoming a payment-infrastructure question before it becomes a checkout-design question. Enterprises that understand their existing payment architecture now will be better placed to adopt new agentic channels without surrendering control of payments, customer data or provider choice.

Agentic Commerce and Payments

Agentic commerce describes buying journeys where artificial-intelligence agents can do more than recommend products. Depending on the model and permissions involved, an agent may search, compare, select and eventually initiate or complete a transaction on behalf of a consumer or business.

For enterprise commerce and payments teams, that changes the question from “How will AI change ecommerce?” to something much more practical:

Can our existing payment infrastructure support transactions where software becomes an active participant in the purchase?

That requires enterprises to think about payment credentials, customer consent, authentication, fraud, routing, checkout ownership, transaction data and the relationship between the merchant and its payment providers.

Find Your New Processor

Why Agentic Payments Matter More in 2026

Agentic commerce is no longer only a theoretical payments discussion.

During 2026, card networks, payment companies, banks and commerce platforms have continued developing infrastructure designed to distinguish agent-led transactions from conventional ecommerce payments and allow agents to transact within defined permissions.

In March 2026, Santander and Mastercard announced a live end-to-end payment executed by an AI agent in a controlled European banking environment. Mastercard has subsequently expanded Agent Pay activity across Europe, while payment companies including Stripe have developed token-based infrastructure intended to allow agents to initiate payments without exposing underlying card credentials.

This does not mean every enterprise merchant needs to rebuild its checkout immediately. It does mean payments teams should start understanding which parts of their current architecture could become constraints if agent-led commerce develops into a meaningful acquisition channel.

The MAS Agentic Payments Readiness Test

Merchant Advice Service uses the following framework when thinking about enterprise readiness for agent-led payments:

Checkout → Credentials → Consent → Authentication → Routing → Risk → Reporting → Portability

Area	What enterprise merchants should assess
Checkout	Can transactions be initiated through APIs or other machine-readable commerce flows without relying entirely on a human-facing checkout?
Credentials	How are payment credentials tokenised, stored and made available without exposing sensitive underlying payment data?
Consent	Can the business evidence what the customer authorised the agent to do, including any transaction, merchant or spending limits?
Authentication	Can the payment stack distinguish a permitted agent-led transaction from bot activity, account takeover or unauthorised automation?
Routing	Does the merchant retain control over PSP, acquirer and payment-method routing as new agentic channels emerge?
Risk	How will fraud rules, authorisation logic, disputes and transaction monitoring respond to new agent-led behaviour?
Reporting	Will transaction data clearly show how a payment was initiated, authenticated, routed and completed?
Portability	Can the business change providers or architecture later without losing critical tokens, customer relationships or payment flexibility?

MAS View: Enterprise readiness for agentic commerce is less about choosing an AI shopping tool and more about whether the existing payment infrastructure can recognise, authenticate, control and report agent-initiated transactions without giving up merchant control.

How Agentic Commerce Changes the Payment Journey

Traditional ecommerce usually assumes that a person participates directly in product selection and checkout. The customer navigates the website, chooses a payment method and completes the required authentication.

Agentic commerce can separate those stages.

An AI agent may discover the product, evaluate different sellers, construct the basket and initiate the transaction while operating within permissions previously granted by the customer.

That creates a different payment problem.

The merchant may need to understand not only who is paying, but also:

which agent initiated the transaction;
what authority the customer gave it;
which payment credential was used;
how the transaction was authenticated;
what spending or merchant restrictions applied;
which PSP or acquirer processed the payment; and
how that information will be evidenced if the transaction is later disputed.

This is why agentic commerce touches much more than the front-end customer experience.

Tokenisation Is Likely to Be Fundamental

Allowing software agents unrestricted access to underlying card credentials would create obvious security and control problems.

Tokenisation offers a different model. Payment credentials can be represented by tokens with controls around where, how or for how long they may be used.

Network and payment-provider developments increasingly point towards token-based models designed specifically for agent-led transactions.

For established businesses, the immediate question should therefore be how mature the existing tokenisation architecture already is.

Businesses should understand:

who currently controls their payment tokens;
whether tokens can be used across multiple channels;
whether the architecture supports network tokens;
whether tokens remain portable if the PSP changes;
how stored credentials are governed; and
whether future agent-specific credentials could be introduced without rebuilding the entire payment stack.

For a deeper explanation, read our guides to network tokenisation and why agentic commerce may require multi-tokenisation.

Find Your New Processor

Consent and Authentication Become Different Problems

Agentic transactions create an important distinction between customer identity and transaction execution.

The customer may still own the account and payment credential, but software could be taking the action that causes the purchase to occur.

Enterprise merchants therefore need to consider how the payment environment will establish:

that the customer authorised the agent;
what the agent was allowed to purchase;
the value or frequency permitted;
whether additional authentication was required;
whether the agent remained inside the customer's instructions; and
what evidence survives if the transaction is disputed.

This is not simply a technical question. It can affect fraud, customer service, disputes, chargebacks and the evidence available to payment providers.

Authorisation Rates Could Become an Agentic Commerce Issue

Enterprise merchants already monitor payment authorisation performance closely. Agent-led transactions could introduce additional data, credentials and authentication patterns into that environment.

If issuers, networks, gateways or fraud systems cannot confidently understand a transaction, legitimate purchases may be declined alongside fraudulent ones.

This makes transaction recognition and good-quality payment data strategically important.

Enterprises preparing for agent-led commerce should understand how their existing provider handles authentication, tokenisation, fraud signals and issuer-facing transaction data, alongside the wider techniques discussed in our guide to improving enterprise payment authorisation rates.

Why Payment Orchestration Could Matter More

Agentic commerce should not automatically require a business to move to multiple PSPs or introduce an orchestration platform.

However, businesses should be cautious about building a new commerce channel that makes them more dependent on a single payment route.

If agent-led transactions develop differently across payment networks, wallets, PSPs, acquirers and markets, larger merchants may need the ability to route transactions based on factors including geography, payment method, risk, cost and performance.

A flexible payment orchestration layer can help enterprises retain more control over that decision-making.

The strategic objective is not complexity for its own sake.

It is avoiding an architecture that becomes expensive or disruptive to change later.

Does Your Current Payment Provider Support the Direction of Travel?

Enterprise merchants do not necessarily need to change payment providers because agentic commerce is developing.

They should, however, understand their provider's roadmap.

Useful questions include:

How is the provider approaching agent-initiated transactions?
Which card-network agentic-payment models will it support?
How are agent credentials or tokens represented?
How will agent-initiated transactions appear in reporting?
What authentication and fraud signals will be available?
Can the merchant retain routing control?
Can agentic payment functionality coexist with the existing gateway or API?
What happens to payment tokens if the merchant later changes provider?

The answers are particularly important for businesses making long-term decisions about gateways, APIs, token vaults or ecommerce architecture today.

When Could Agentic Commerce Expose Limitations in Your Current Payment Stack?

The strongest reason to review payment infrastructure is not the arrival of a particular AI product. It is discovering that the existing architecture has become difficult to adapt.

Potential warning signs include:

payment logic that is tightly coupled to one checkout or PSP;
limited API capability;
tokens that cannot easily be migrated;
little control over routing or retry logic;
poor transaction-level reporting;
inflexible fraud rules;
limited international acquiring options; or
a provider roadmap that does not align with the business's future commerce requirements.

These issues may already affect ordinary ecommerce today. Agentic commerce simply gives enterprise merchants another reason to identify them before they become more expensive to solve.

Businesses considering a significant change to their payment architecture may also find our guides to payment API integration and changing payment provider with a custom API useful.

Find Your New Processor

Enterprise Use Cases for Agentic Payments

Some of the earliest commercially useful agentic-payment models are likely to be environments where the rules of the transaction can be clearly defined.

B2B procurement

An agent could identify approved suppliers, compare pricing and reorder products within procurement policies, spending limits and predefined commercial rules.

Travel and expense

Agents could search travel inventory, compare options and make bookings within corporate travel policies or customer instructions.

Subscriptions and replenishment

Agent-led systems could monitor usage and initiate permitted purchases or replenishment transactions where clear consent and billing rules exist. Businesses operating recurring models should also consider the wider issues covered in our subscription payment processing guide.

Marketplaces

Agentic commerce may become particularly relevant to marketplaces because agents could compare multiple sellers, products, delivery conditions and payment options within one buying journey. Marketplace operators still need to consider the underlying questions around seller onboarding, payment flows and payouts covered in our marketplace payment gateway guide.

Machine-to-machine commerce

Longer term, agent-led commerce may extend beyond consumer shopping into software or connected systems purchasing services or resources programmatically within defined rules.

The Risks Enterprise Merchants Need to Plan For

The opportunity comes with risks that extend beyond conventional ecommerce fraud.

Risk	Enterprise consideration
Unauthorised agent action	Can the merchant evidence what the customer allowed the agent to do?
Agent impersonation	How will legitimate agents be distinguished from malicious automated traffic?
Payment disputes	What evidence will explain the customer's intent and the agent's action?
Credential exposure	Can tokenisation prevent agents from accessing unrestricted payment credentials?
Checkout disintermediation	How much control does the merchant retain if discovery and checkout move outside its website?
Provider dependency	Does adopting an agentic-payment model make future PSP migration harder?
Data fragmentation	Can transactions still be reconciled and analysed across different commerce channels?

What Enterprise Payments Teams Should Do Now

Most businesses do not need to launch an agentic checkout simply because the technology exists.

They do need to understand whether decisions being made about payment infrastructure today will leave them flexible enough to support new commerce channels tomorrow.

A practical readiness review should include:

Map the current payment architecture. Identify gateways, PSPs, acquirers, token vaults, ecommerce platforms, fraud systems and payment APIs.
Understand token ownership. Establish where stored credentials sit and how portable they are.
Review API capability. Determine whether payment and checkout functions can support machine-readable workflows.
Assess provider roadmaps. Ask existing providers what agentic-payment capabilities they are developing or supporting.
Review authentication and fraud. Understand how agent-led activity could be recognised and controlled.
Protect routing flexibility. Avoid unnecessarily locking a new channel to one provider.
Define reporting requirements. Decide what transaction-level evidence the business will need for reconciliation, risk and disputes.
Test controlled use cases first. Start where permissions, values and commercial rules can be tightly defined.

Should an Enterprise Merchant Change Payment Provider for Agentic Commerce?

Not necessarily.

Changing provider purely because agentic commerce is developing could create unnecessary cost and implementation work.

The better starting point is to understand whether the existing provider and payment architecture can support the direction the business expects to travel.

A provider review becomes more relevant where agentic commerce exposes wider limitations such as poor API flexibility, restricted token portability, limited routing control, weak international support or an infrastructure roadmap that no longer fits the merchant.

For larger merchants, any comparison should therefore look beyond headline transaction pricing.

The provider needs to fit the commercial model, payment architecture, integrations, geographic requirements, risk profile and future technology strategy of the business.

Find Your New Processor

What This Means for Enterprise Merchants

Agentic commerce is unlikely to replace conventional ecommerce overnight. But it is creating a new transaction model that enterprise payment teams can no longer treat purely as an AI experiment.

The most important preparation is not choosing the latest agentic platform.

It is making sure the underlying payment environment remains adaptable.

Tokenisation, consent, authentication, routing, fraud controls, APIs, reporting and provider portability are the foundations that will determine how easily an enterprise can participate as the market develops.

Businesses with flexible payment infrastructure will have more choice about when and how they adopt agent-led commerce. Businesses locked into brittle payment architectures may discover that the biggest obstacle is not artificial intelligence at all — it is their existing payment stack.

Related Merchant Advice Service Guidance

Sources & Further Reading

Mastercard — Santander and Mastercard complete Europe's first live end-to-end payment executed by an AI agent, March 2026.
Mastercard — Europe is Building the Foundations for Trusted Agentic Commerce, June 2026.
Mastercard — Agent Pay for Machines, June 2026.
Stripe — Supporting Additional Payment Methods for Agentic Commerce, March 2026.
Stripe — Agentic Commerce documentation and Shared Payment Tokens.

Editorial & Commercial Disclosure

Merchant Advice Service provides independent information and guidance about merchant accounts, payment gateways and payment-provider selection. We are not a payment processor, acquirer or card scheme.

MAS may receive a commission or referral fee from some payment providers where a business proceeds following an introduction. This does not determine the educational content, frameworks or provider-selection principles used in this guide.

Agentic-commerce technology, card-network standards and payment-provider capabilities are developing quickly. Businesses should confirm current functionality, geographic availability, commercial terms and technical requirements directly with the relevant provider before making infrastructure decisions.

FAQs

Does my business need to change payment provider to support agentic commerce?

Not necessarily. The first step should be to assess whether your existing provider can support the direction agentic commerce is taking, including APIs, tokenisation, authentication, reporting and future agent-initiated payment models. Changing provider becomes more relevant where the existing payment stack limits flexibility or the provider’s roadmap does not align with your future requirements.

How can I tell if our payment stack is ready for agentic commerce?

Review the payment journey across checkout, credentials, consent, authentication, routing, fraud controls, reporting and portability. Businesses with flexible APIs, strong tokenisation, clear transaction data and the ability to change or add payment providers are generally better positioned than businesses whose checkout is tightly tied to one provider.

What should enterprise merchants ask their payment provider about agentic commerce?

Ask how the provider plans to identify agent-initiated transactions, which card-network agentic-payment models it expects to support, how agent credentials will be tokenised, what authentication data will be available, how transactions will appear in reporting and whether existing payment APIs will need to change.

Will agentic commerce require us to rebuild our checkout?

Not necessarily. Some agentic transactions may continue to use existing payment infrastructure, while others could originate outside the merchant’s conventional website or checkout. The more important question is whether your payment functions can be securely accessed through APIs and other machine-readable workflows without creating unnecessary dependency on one platform or provider.

Could agentic payments affect our authorisation rates?

Potentially. New transaction patterns, credentials and authentication signals may affect how issuers and fraud systems assess payments. Enterprise merchants should monitor whether agent-initiated transactions can be clearly identified and whether their payment provider can pass useful authentication and transaction data through the payment chain.

How should fraud controls change for agent-led transactions?

Fraud systems may need to distinguish authorised AI-agent activity from malicious bots, account takeover and automated fraud. Merchants should consider how customer permission, agent identity, spending limits, device or behavioural data and transaction context can be incorporated into existing risk controls.

What reporting will businesses need for agentic payments?

Enterprise merchants should be able to establish how a transaction was initiated, what authority was given, which credential was used, how it was authenticated, which provider processed it and whether an agent was involved. This information may become important for reconciliation, customer service, fraud investigations and disputes.

Could agentic commerce increase our dependence on one PSP or gateway?

It could if new agentic functionality is implemented through proprietary APIs, token vaults or credentials that cannot easily be moved elsewhere. Businesses should consider portability before adopting new payment infrastructure and understand what happens to tokens, transaction data and integrations if they later change provider.

Do enterprise merchants need payment orchestration for agentic commerce?

Not automatically. Orchestration becomes more relevant where a business already uses multiple PSPs, acquirers or payment methods, or wants greater control over routing as agentic channels develop. The objective should be flexibility and resilience rather than adding technical complexity unnecessarily.

What should enterprise payments teams do now if agentic commerce is not yet a major sales channel?

Start with an infrastructure review rather than a major implementation. Map your providers, APIs, gateways, tokenisation, fraud tools and stored credentials; establish who owns critical payment data and tokens; understand provider roadmaps; and identify areas where the current payment stack may be difficult to adapt later.

Which businesses are most likely to encounter agentic commerce first?

Use cases are likely to develop fastest where purchasing rules can be clearly defined, such as travel, B2B procurement, subscriptions and replenishment, marketplaces and other environments where an agent can act within predetermined customer or corporate permissions.

When should an enterprise merchant carry out a payment-provider review because of agentic commerce?

A review is worth considering when agentic requirements expose wider weaknesses in the current payment setup — for example limited API capability, poor token portability, restricted routing, inadequate transaction reporting, weak international coverage or a provider roadmap that no longer supports the business’s longer-term commerce strategy.

Written or reviewed by Libby James, founder of Merchant Advice Service and specialist in merchant payments and complex provider requirements.

In this article

Share this article with others: