Agentic Commerce Is Being Built Card-Shaped: Why Local Payment Methods Just Fought Back

Meta title: Agentic Commerce Needs Local Payment Methods

Meta description: See why local payment methods must be built into agentic commerce from the start, and what merchants should test across checkout, routing and reporting.

Suggested slug: agentic-commerce-local-payment-methods

Primary keyword: agentic commerce

Secondary keywords: local payment methods, agentic payments, alternative payment methods, AI payments, payment orchestration

Agentic commerce is being built card-shaped. Global card networks shipped the first frameworks for trusted agent-led transactions, giving card rails a head start in the protocols and integrations that agents can use to make payments.

That is not just a question for payment schemes. It is a practical merchant risk. If an agent can only complete checkout by card, a customer’s preferred local payment method may not be available. For merchants with a substantial mix of local methods, that turns agent traffic from a potential growth channel into a conversion leak.

On 21 October 2026, PPRO launched the Local Payments Council for Agentic Commerce with founding members BLIK, EPI, Bancontact Company and DIAS. Other schemes have committed to joining. Its purpose is to develop common technical standards so local payment methods can work securely and seamlessly in agent-led commerce, rather than being bolted on after the main protocols are established.

As PPRO CTO Alexander Matthey put it, the rules for local payments need to be in place “from the outset, rather than treated as an additional layer later on”.

Five building blocks for local methods

The council has identified five areas for its work. Each one affects whether an agent can complete a real purchase using the payment method a customer knows and trusts.

Out-of-band authorisation and session hand-off describe how approval works when the person is not interacting with the agent’s checkout. For European local schemes, this can mean the customer confirms a payment in their own banking app, outside the agent session. The hand-off must work without disrupting the purchase or requiring a merchant to build a custom flow for each method.

Agent identity and attestation help establish which agent is making a payment and how its identity can be recognised on a non-card rail. Without a workable way to identify an agent, local methods may be difficult to expose or process consistently.

Consent, mandates and delegated authority define what a customer has already allowed an agent to do. Operationally, merchants need the payment flow to respect those instructions, including any spending limits or purchase conditions.

Disputes and refunds need to work for agent-initiated transactions too. Merchants need to know how a completed purchase can be found and refunded through the relevant payment method, not just through a card process.

Discoverability and agent-surface eligibility determine whether a local method is visible to an agent at checkout at all. If an agent’s payment surface only presents card options, the customer cannot select a local method, however well the underlying payment technology works.

These questions sit alongside the growth opportunity. PPRO cites Shopify data that AI-referred shoppers convert nearly 50 per cent more and record 14 per cent higher average order values than shoppers arriving from organic search. That is a reason to prepare for agent traffic, not a guarantee that every merchant will see the same results. Conversion depends on whether an agent can complete the customer’s preferred checkout.

BLIK shows a local agent payment can work

The BLIK pilot in Poland offers a practical example. On 9 September 2026, an AI agent independently completed a purchase for a specific hand cream variant in the Your KAYA online store after monitoring its availability. When it came back into stock, the agent bought it for PLN 19.99.

The purchase followed a prior instruction from the customer. A six-digit BLIK code was confirmed in the customer’s banking app, while Juo enabled the agent chat in the store and PayU processed the payment. BLIK Vice President Monika Król said the agent “operates exclusively within boundaries previously defined by the user and cannot complete a transaction without the user's prior authorisation”.

The operational lesson is specific: an agent does not have to replace a familiar local payment method. The flow can connect an agent’s task to an authorisation experience in the banking app. The challenge is making that connection a standard capability, not a one-off pilot. BLIK’s availability as a dynamic payment method on Stripe, announced on 25 September, is another step in making it accessible to merchants.

Australia’s merchant choice question

In Australia, the discussion is already linked to debit routing and merchant choice. The RBA’s Review of Payments System Regulation summary records concerns from merchants, PSPs and issuers that agents could choose which card networks and PSPs receive transactions. If commercial arrangements shape those choices, a merchant’s preferred debit network or routing option could be bypassed.

Stakeholders also warned that early design choices may be difficult to reverse as agentic commerce scales, and that standards set by international companies could create barriers to competition in Australia. Stakeholders generally favoured monitoring and industry-led standards over immediate regulation.

Australian Payments Plus made the merchant choice issue more concrete: agentic AI used to initiate debit card payments should support least-cost routing from launch, rather than interrupting it. AP+ warned that delegating authority through scheme-specific passkeys or agent credentials could force a network choice before the merchant’s transaction and routing preferences are known. It also supported open, interoperable token portability.

The timing matters for Australian operators. With the card surcharge ban now in effect, acceptance costs sit inside advertised prices. If an agent’s chosen route removes a merchant’s ability to apply an available routing choice, the cost and competitive implications land in the merchant’s operating model.

Merchants can already see the broader strategic debate in Quantum Payments’ analysis of AI payment routing and the router’s influence over rails and network choice for credit cards. Agentic commerce brings those issues into a new checkout environment.

Merchant checklist: test your full payment mix

This is also where payment orchestration becomes practical. Merchants need a connected view of which methods are available, how an agent initiates a payment, and what happened afterwards. As we discuss in our analysis of agent-to-agent payments and emerging payment volume, new transaction flows create operational questions that extend beyond the moment of checkout.

Frequently asked questions

What is agentic commerce?

Agentic commerce is shopping in which an AI agent helps a customer discover, select or purchase products, based on the customer’s instructions. Depending on the arrangement, the customer may take part at checkout or delegate some steps in advance.

Why do local payment methods matter in agentic commerce?

Customers may prefer payment methods that are familiar and widely used in their market. If an agent cannot discover or complete a purchase with that method, the merchant risks losing a sale that could have converted through its usual checkout.

What does out-of-band authorisation mean?

It means the customer approves a payment outside the agent’s active checkout session, for example in their banking app. This matters for local schemes that already use a separate banking app to confirm payments.

What should merchants do first?

Map payment methods by channel, then ask your PSP which methods agents can discover and complete. Test an agent-led transaction on a leading local method and report its conversion and cost separately.

Conclusion

Agentic commerce will not be won by whichever protocol has the most announcements. It will be won by merchants whose full payment mix works inside it.

The next twelve months will help determine whether non-card rails are part of agent protocols from the start or left to catch up later. For merchants, the question is straightforward: can an agent complete checkout using the payment method the customer actually prefers?

Authoritative sources