Payments Orchestration Australia: The Strategic Layer You Can’t Ignore
Most Australian businesses did not decide to run a complex payments stack. They accumulated one.
A primary acquirer was chosen years ago. Then a second gateway was bolted on to reach a market the first could not serve well. A buy-now-pay-later option was added because the ecommerce team asked for it. A wallet or two followed because customers expected them. Each addition was sensible on its own. Together they produced something nobody designed: a sprawl of providers, each with its own integration, its own settlement file, its own fee structure, its own dashboard, and its own failure modes. It is a payment stack in the literal sense, layers added over time, but not in the designed sense, and payment acceptance across it is only as strong as its weakest, least-monitored provider.
The way most organisations manage that sprawl is reactive. A provider's approval rate dips, and someone notices weeks later in a report. Costs creep up after a fee change buried in a scheme notice. An outage takes down checkout, and the response is a frantic manual switch to a backup. Each problem is handled when it surfaces, by hand, by whoever is closest. This is not a strategy. It is a series of interruptions.
Payments orchestration is the architectural answer to that reactivity. It is a layer that sits above your individual providers and makes the decisions that are currently being made manually, or not at all: which acquirer to route a given transaction through, when to retry and where, how to fail over when a provider degrades, and how to optimise continuously for cost and conversion rather than reacting after the fact.
For Australian organisations specifically, the case has sharpened in the last eighteen months, because three regulatory and infrastructure shifts are landing at once, the RBA's 2026 card reforms, the transition away from BECS, and the completed migration to ISO 20022. Each of these is hard to navigate with a manually managed provider sprawl and considerably easier to navigate from an orchestration layer. That is what has moved orchestration, for Australian businesses, from a nice-to-have to something closer to the architecture that makes everything else achievable. It is the reason payments orchestration in Australia is now a board-level conversation rather than a technical one. Payments orchestration Australia-wide has shifted from an efficiency project to a strategic priority.
What payments orchestration actually is
It is worth being precise, because the term is used loosely and often conflated with a gateway.
A payment gateway connects your checkout to a single acquirer or processor and authorises transactions through it. It is essential plumbing, but it is narrow: one road to one destination. Payment gateway orchestration sits a level above one or more gateways and coordinates across all of them. It owns the routing logic, the failover rules, the retry strategy, and the consolidation of data from every provider into one view.
The distinction matters because they solve different problems. A gateway answers "how does this transaction reach an acquirer?" Orchestration answers "which of my acquirers should this transaction reach, given cost, the customer's card, the destination, current provider performance, and what happens if that provider says no?" The first is a connection. The second is a decision engine.
In practice an orchestration layer brings four capabilities that a single-gateway setup cannot. Smart routing directs each transaction to the provider most likely to approve it at the lowest cost. Automatic failover reroutes transactions when a provider degrades or goes down, so an outage at one acquirer does not become an outage at your checkout. Intelligent retries re-attempt a declined or failed transaction through a different path rather than simply giving up. And unified data pulls settlements, fees, decline reasons and chargebacks from every provider into a single place, so the fragmented reporting that makes optimisation impossible becomes a single legible picture. Together these turn payment routing optimisation from a periodic manual review into something the layer does on every transaction.
The reactive stack versus the orchestrated one
The difference is easiest to see in how each handles the situations that actually cost money.
When a provider has an outage, the reactive stack loses transactions until a human notices and manually redirects traffic, often after customers have already abandoned. The orchestrated stack detects the degradation and fails over automatically, and most customers never know anything happened.
When a transaction is declined for a soft reason, a transient issuer problem, a timeout, the reactive stack treats it as a lost sale, or retries blindly down the same failing path. The orchestrated stack retries intelligently through an alternative acquirer, recovering revenue that would otherwise have simply vanished.
When acceptance costs drift upward, the reactive stack finds out at month-end, if at all, because the cost is buried across several providers' statements. The orchestrated stack routes for cost continuously and surfaces the drift immediately, because all the fee data lands in one place. That is where real payment cost reduction comes from,not a single hard renegotiation, but continuous dynamic routing to the cheapest viable path.
And when the business wants to add a new payment method or enter a new market, the reactive stack faces another bespoke integration and another silo. The orchestrated stack adds it behind the existing abstraction, and every downstream system inherits it without change.
None of these is exotic. They are the ordinary events of running payments at scale. The orchestration layer simply moves the response to them from manual and after-the-fact to automatic and continuous, which is the difference between reactive payment provider switching and a stack that switches itself.
Why this matters more in Australia right now
Every developed payments market is moving toward orchestration. What makes the Australian case unusually urgent is the specific convergence of change happening here between 2025 and 2027. Three threads are worth understanding, because orchestration touches each.
The RBA's 2026 card reforms
The RBA card reforms are the most immediate of the three. On 31 March 2026 the Reserve Bank of Australia published the Conclusions Paper for its Review of Merchant Card Payment Costs and Surcharging. The decisions are substantial. From 1 October 2026 the RBA will remove surcharging across the designated eftpos, Mastercard and Visa networks, lower the caps on domestic interchange fees, and introduce transparency measures requiring acquirers to publish their fees and their interchange pass-through. A cap on foreign-card interchange and some further transparency measures follow on 1 April 2027. The RBA estimates the interchange changes alone will lower merchants' card payment costs by around $910 million a year.
The strategic consequence is easy to miss. When surcharging ends, merchants that previously passed acceptance costs to customers must absorb them into margin. Acceptance cost stops being a pass-through and becomes a direct cost of doing business. That change instantly raises the value of every basis point of cost optimisation, and cost-based routing across multiple acquirers is exactly what an orchestration layer does. The reform does not just permit optimisation; it makes not optimising expensive.
Least-cost routing sits inside the same reform, and the current RBA position needs stating precisely rather than from assumption. In the March 2026 paper the Board kept the existing expectations-based approach to least-cost routing for in-person, card-present transactions rather than mandating it, with 84 per cent of merchants having it enabled as at December 2025. Least-cost routing for online and mobile-wallet transactions was not mandated; it was deferred to a further consultation expected in mid-2026. Around 90 per cent of Australian debit cards are dual-network, and the RBA's own research has found merchants with least-cost routing enabled pay materially less on debit acceptance. So least-cost routing in Australia is, for in-person transactions, a lever largely in your own hands today, and least-cost routing Australia settings are worth auditing now, while online routing is an area to prepare for rather than assume, and orchestration is what makes acting on either a configuration change rather than a project.
The transition away from BECS
The second thread is account-to-account. The Bulk Electronic Clearing System has carried Australia's batch payments; salaries, direct debits, bulk files, for more than three decades. The intended direction is migration to the real-time New Payments Platform and its PayTo service.
The timeline, though, is a live lesson in its own right. In November 2023 the industry set June 2030 as the target end date for decommissioning BECS. On 16 December 2025 AusPayNet removed that target date, having concluded that the majority of BECS members no longer believed it was achievable without a clear roadmap developed first. The direction is unchanged, the industry still intends to move to modern alternatives, but the date is gone until the sequencing is worked out.
For a business, the practical implication is that account-to-account payments will exist in a prolonged period of coexistence: BECS direct debit and NPP-based PayTo both running, for years, with recurring collection gradually shifting toward the real-time rail. Managing two account-to-account rails in parallel, and steering flows between them as adoption grows, is precisely the kind of routing-and-coexistence problem an orchestration layer is built to handle. Hard-wiring to one rail in this environment is a bet the industry itself has declined to make.
The ISO 20022 migration
The third thread is data. The global migration to the ISO 20022 messaging standard completed its coexistence period for cross-border payments on 22 November 2025, moving payment messages to a structured, data-rich format in place of legacy free-text fields. Richer, structured payment data is what makes intelligent routing and clean reconciliation possible in the first place, a routing engine is only as good as the data it can read, and a reconciliation process is only as clean as the references it receives. An orchestration layer is the natural place to capture and use that richer data consistently across providers, rather than having each integration handle it differently.
Taken together, these three threads point the same way. Each is easier to absorb as a configuration change at an orchestration layer than as a fresh project against a manually managed sprawl. An organisation that has to run a programme every time the rules change will spend the next two years running programmes. An organisation with an orchestration layer absorbs most of it as routing and configuration.
Beyond cost: resilience, conversion and reach
Cost optimisation is the most quantifiable benefit, but for many organisations it is not the largest.
Payment resilience is often the one that matters most to the board. A single-acquirer setup has a single point of failure: if that provider has a bad day, your revenue has a bad day. Acquirer diversification behind an orchestration layer turns a provider outage from a business incident into a non-event, because traffic reroutes automatically. For financial services, insurance, retail and telco organisations where payment availability is close to a critical operation, that resilience increasingly intersects with regulatory expectation as well as commercial sense.
Payment conversion is the one that compounds quietly. Every transaction recovered by an intelligent retry, every customer not lost to a checkout outage, every approval won by routing to the acquirer most likely to say yes, is revenue that a reactive stack simply forfeits. At scale these are not rounding errors; they are a meaningful share of the transactions the business worked to win in the first place. This is where orchestration and checkout optimisation meet: the smoothest checkout in the world still loses the sale if the transaction behind it is routed to a provider that declines it.
Reach is the strategic one. When adding a payment method or entering a market is a configuration change rather than a bespoke integration, the payments layer stops being a constraint on commercial ambition and starts being an enabler of it. The business can move at the speed of its strategy rather than the speed of its next integration, which, for any organisation serious about digital payments in Australia and beyond, is the difference between leading a market and following it. In a digital payments Australia landscape reshaped by regulation and real-time rails at once, that speed is itself a competitive advantage.
What this is not
Intellectual honesty matters here, because orchestration is over-sold as often as it is under-adopted.
It is not a single product you buy and switch on. It is an architectural layer that has to be designed around your provider mix, your markets, your card mix and your risk posture. Routing rules that are wrong cost money as surely as no routing at all, route purely for cost and you can suppress approval rates; route purely for approval and you can overpay. The value is in the calibration, not the switch.
It is also not only for the largest enterprises. The threshold that makes orchestration worthwhile is not company size but provider complexity: a genuine multi-acquirer strategy, more than a couple of payment methods, or operations across more than one market. Many mid-sized Australian businesses have quietly crossed that threshold without re-examining an architecture that was set when they had a single provider.
And it does not require ripping out what you have. A well-designed orchestration layer builds a logic layer around existing providers rather than replacing them, which is what makes adopting it an incremental decision rather than a big-bang one.
What Australian leaders should be asking
A short set of questions tends to reveal whether orchestration is overdue. If your primary acquirer had a two-hour outage tomorrow, what would happen to your revenue, and how quickly could you reroute? If the honest answer involves a human noticing and a manual switch, you are carrying a resilience risk you could design out.
Can you see your total cost of acceptance, and your approval rate, across all providers in one place, or is each locked in its own dashboard? If you cannot see it whole, you cannot optimise it.
When surcharging ends in October 2026 and acceptance cost lands in your margin, what will you actually do to manage that cost, and is cost-based routing across acquirers even available to you today?
How long does it take you to add a new payment method or acquirer, days, or a quarter? That number is a direct measure of how much your current architecture constrains your strategy.
And who owns payments as a strategic layer, rather than as a set of provider relationships and integrations maintained in different corners of the business?
Getting payments orchestration right in Australia
The outcome worth aiming for is a payments layer that behaves like infrastructure rather than a collection of accidents: resilient by design, optimising continuously for cost and conversion, absorbing regulatory change as configuration, and adding methods and markets at the speed of the business. In the Australian context, over the next two years, that same layer is also what turns the RBA reforms, the BECS transition and the ISO 20022 shift from three separate programmes into changes the architecture largely absorbs on its own.
Getting there is a strategic decision before it is a technical one. It depends on an honest map of your current provider sprawl, a clear view of where cost, resilience and conversion are actually leaking, and routing logic calibrated to your business rather than borrowed from a template. It is consulting work as much as engineering work, which is precisely the framing most vendor-led orchestration content misses.
This is where implementation experience counts. Conexxia works with Australian financial services, insurance, retail and telco organisations on payments orchestration strategy, mapping the existing stack, designing the routing and failover logic, and sequencing adoption so it delivers resilience and cost benefits without a disruptive migration. It is the anchor of a broader payments consulting practice that runs from payments infrastructure modernisation and payments operations through to cross-border payments and payments compliance and risk, so the orchestration layer connects to everything around it, payment operations, reconciliation and compliance included, rather than becoming another silo.
None of this requires committing to a platform to begin. Most organisations start by mapping what they already run, seeing their true cost and approval rate across every provider in one place for the first time, and letting that picture show where an orchestration layer would pay for itself first.
If your payments stack is something you accumulated rather than designed, the reforms arriving through 2026 and 2027 are a good reason to design it, before the next change forces another scramble.
Aftab Khan
Head of Payments Consulting
On a mission to help change the world, one experience at a time
I collaborate with progressive businesses to deliver successful business outcomes in 4 key areas: Increasing Revenues, Improving Operational Efficiencies, Regulatory Compliance and Elevating Customer Experience, leading to sustainable business growth.
Comments