top of page

The RBA just made dual-network debit a design rule for agentic checkout

2 days ago
7 min read

TL;DR: The RBA’s Payments System Board has reiterated that dual-network debit should be available in every form factor, including those used in agentic commerce, to support merchant choice. That expectation matters because an agent’s payment credential can be provisioned against a single network, silently removing the merchant’s routing decision before checkout. The design obligation therefore reaches beyond the agent developer to issuers, acquirers and the businesses provisioning and presenting credentials. Meanwhile, new fee disclosures create a timetable for testing whether payment reforms are reducing merchant costs. Operators building agent checkout should make credentials dual-network capable before the first formal data and compliance questions arrive.

What the Board actually said about agentic commerce

The Board’s 19 November 2026 update did not announce a new rule; it reiterated an existing expectation and explicitly applied it to agentic commerce form factors.

The statement is significant because agentic commerce is evolving rapidly and attracting investment, while payment credentials and checkout designs are being determined now. The Board noted the potential implications for competition, efficiency and safety, and said the RBA is engaging with industry and other regulators. It then reiterated that dual-network debit functionality “should be available in all form factors, including those that may be used in agentic commerce transactions, to support merchant choice.”

That is a merchant-choice condition placed on a payment channel before it exists at scale. It is not a ban, a new standard or a consultation. But it signals that agent-enabled checkout is not exempt from the RBA’s expectation just because a credential is presented through a new interface.

The wider Review of Payments System Regulation is also relevant: stakeholders raised issues including mobile wallets, three-party card schemes, account-to-account payments and agentic commerce. The RBA will publish its priorities by the end of the year.

Why dual-network debit is the hard part of agentic checkout

Dual-network debit is difficult to preserve when a payment credential is designed around one network from the outset.

In Australia, a debit transaction can carry a routing decision. Merchant choice matters because the route selected can affect the cost of acceptance. Least-cost routing is the practical expression of that choice: eligible debit transactions can be routed through the available network that is less costly for a merchant to accept.

Agentic checkout complicates that model because its payment credential may be provisioned into a particular form. A commissioned credential, a card-on-file token bound to one scheme or a single-network virtual card may each be a legitimate product design. But from the merchant’s perspective, each can create a closed loop: the payment reaches checkout with the network already selected.

That selection can happen silently at provisioning, not at the moment the agent pays. Once a credential is issued or presented as network-specific, the merchant may have no practical way to reroute it. The Board’s expectation therefore turns a wallet-design question into an acceptance obligation.

The tension resembles a broader wallet-design issue: mobile wallet adoption and interoperability depend on how payment credentials connect across systems. Agentic commerce adds another requirement: preserving the merchant’s choice of debit network, not merely making a credential usable.

An agent interface of light enclosing a sealed credential node beside two unopened payment channels

What happens to a merchant’s routing choice when an agent pays

If an agent presents a credential tied to one network, the merchant’s routing choice may disappear before the transaction reaches the point of sale.

That is the architectural collision. The merchant may still accept the payment, but acceptance is not the same as retaining choice over the route. The credential’s network binding can determine the path before the merchant’s systems have an opportunity to apply routing logic.

This distinction matters for retail payment strategy. Agentic checkout is often discussed as an interface or automation challenge: how an agent selects a product, confirms a purchase and submits payment. The more consequential payments question may be how the credential is created, which network it supports, and whether the merchant can still influence routing.

There is a useful distinction between an agent’s purchase instructions and the credential that funds the purchase. The agent can receive a customer’s authorisation while still using a network-specific credential. The approval step does not, by itself, restore debit routing choice. For a closer look at a different credential-and-acceptance design, see our analysis of the ChatGPT Wallet acceptance specification.

A routing fork suspended in a dark data structure, with one branch bright and another dimmed

Where the obligation actually lands

The operational burden falls on the organisations that issue, acquire, provision and present payment credentials, rather than on the agent developer alone.

An agent developer may not have access to a debit routing table, while a card scheme has little reason to volunteer a choice that could direct a transaction elsewhere. The issuer controls what credential is made available; the acquirer and payment acceptance layer influence how transactions are handled; and the provider provisioning a credential into an agent can determine whether network choice survives in the first place.

For a PayFac or ISO, that makes onboarding and integration decisions critical. If the credential model is settled during onboarding without asking whether it preserves dual-network capability, the requirement can be quietly skipped. A merchant might only discover the restriction after routing options are no longer available.

This is not the same issue as who distributes acceptance or supplies the device. Our coverage of Mastercard Accept examines that adjacent question; here, the focus is whether credential design leaves merchants able to choose a debit network.

The measurement regime arriving with it

The RBA is pairing its merchant-choice expectation with a growing evidence base for monitoring merchant costs.

The Board welcomed new quarterly data on merchant service fees, interchange fees and scheme fees, and said it will use the data over the year ahead to monitor whether reforms are delivering lower payment costs, particularly for small businesses. Four dates establish the timetable.

Quarterly large-acquirer merchant service fee data are already being published, and the September 2026 quarter is explicitly pre-reform, which makes the next publication in early 2027 the first read on fees after the reforms. From 30 January 2027, large acquirers will also publish a quarterly measure of interchange pass-through, for four quarters. Statistical Table C11 begins publishing interchange pass-through data in February 2027. And from April 2027, all acquirers must provide more detailed monthly merchant service fee statements, compliant for statement periods commencing on or after 1 April.

The RBA’s published merchant service fee data show averages by acquirer, split between small businesses, medium-sized businesses and all merchants. A large acquirer is defined as one that acquired more than $10 billion in designated-scheme card transactions over the preceding four quarters. For more context on the disclosures, see our guide to Australia’s first acquirer fee tables.

Together, these disclosures make cost and pass-through more auditable than arguable. They do not prove that a particular merchant’s routing decision was preserved, but they strengthen the commercial context in which providers will need to explain their costs and payment choices.

A dark abstract measurement dashboard of glowing quarterly bars and a thin ascending line

What the Board said about month one of no surcharges

The Board reported a high level of compliance in 2025/26 and said merchants had broadly stopped surcharging transactions over designated card networks after the schemes implemented no-surcharge rules in October.

That is the Board’s assessment, not an independent survey of every merchant’s pricing. Whether individual businesses changed prices is a separate question. For a merchant-side view of early responses, see our review of the first month without card surcharges.

The distinction matters for agentic checkout because merchants cannot assume a surcharge will compensate for a payment route they did not choose. Acceptance cost, routing flexibility and credential design are therefore increasingly connected commercial questions.

What operators should do before the year-end priorities land

Operators should make dual-network capability a design decision before the RBA publishes its Review priorities and before early-2027 data begins arriving.

Start by mapping the full credential lifecycle: who provisions it, whether it can support both debit networks, what routing information is available, and which party presents the transaction to the network. Test the merchant’s ability to retain routing choice across agent, wallet and virtual-card form factors, rather than assuming that conventional contactless payments and agent checkout behave identically.

PayFacs and ISOs should make these questions part of merchant onboarding, integration design and provider due diligence. Issuers and acquirers should identify where a credential becomes network-specific and whether merchant choice can be retained through the full transaction path. Product teams should also record how choices are made, so that future fee and routing questions can be answered with evidence rather than assumptions.

The sequencing risk is straightforward: the expectation exists now, the RBA’s Review priorities are due by year-end, and the first post-reform fee data arrives in early 2027. An operator building agent checkout in the first quarter of 2027 will be building into both an expectation and a measurement regime. The cheaper move is to design for dual-network capability before the first audit or merchant challenge, not retrofit it afterwards.

The interesting thing about the Board’s sentence is how ordinary it sounds. It is not a new standard; it is an existing expectation applied to a new form factor. That is precisely how an obligation can become embedded before anyone has costed it. The question for Australian issuers, acquirers and PayFacs is not whether agentic checkout arrives, but whether their credential design lets merchants choose the rail when it does.

Frequently asked questions

What did the RBA say about dual-network debit in agentic commerce?

The Payments System Board reiterated its expectation that dual-network debit functionality should be available in all form factors, including those that may be used in agentic commerce transactions, to support merchant choice.

Why can an agent payment credential affect least-cost routing?

If a credential is provisioned against one network, that can determine the route before the merchant can make a routing decision. Dual-network capability is therefore a credential-design and acceptance issue, not only an agent-interface issue.

When will the first post-reform merchant service fee data be available?

The RBA says the next merchant service fee publication, expected in early 2027, will show how fees changed following the reforms. The September 2026 quarter data predate those changes.

What should PayFacs and ISOs check first?

They should establish whether credentials provisioned into agent checkout retain dual-network capability, who controls routing and how the transaction is presented to the network. Those questions belong in onboarding and integration design.

Sources

 
 
bottom of page