A payment hub is a centralised software platform that receives payment instructions from many sources, processes them in a common way and sends them out over the appropriate payment rails. Banks use payment hubs to replace the separate systems they historically ran for each payment type, and large companies use similar platforms to route all their outgoing payments to their banks through one point. A hub typically validates and enriches each instruction, applies sanctions and fraud checks, converts it into the required message format and selects the rail on which it should travel.
The idea grew out of the complexity of bank payment operations. Over decades many banks built separate processing "silos" for wires, ACH, cheques, cards and cross-border transfers, each with its own rules, screening and connections. A hub consolidates the shared functions into a single engine, sometimes called a payment engine or payments platform. On the corporate side the comparable structure is the payment factory, which centralises a group's payment processing, often alongside an in-house bank.
How a payment hub works
Designs differ, but a hub generally takes each payment through a series of steps:
- Intake. Instructions arrive from online banking, branch systems, corporate files, APIs and other internal applications, and are converted into one internal format.
- Validation and enrichment. The hub checks that mandatory data is present and correct, looks up routing codes and account details, and adds missing information such as bank identifiers.
- Control checks. Each payment passes sanctions screening, fraud scoring, limit checks and, where needed, approval workflows.
- Routing. Rules choose the rail according to currency, value, urgency, cost and cut-off times, for example a domestic instant payment, a high-value wire or a cross-border message.
- Formatting and dispatch. The payment is translated into the message standard the rail requires and sent, with status updates fed back to the channel that created it.
Payments that fail validation drop into repair queues, where operations staff correct them. The share of payments processed end to end without manual intervention, known as straight-through processing (STP), is one of the main measures of a hub's effectiveness.
Rails and message standards
A bank payment hub in the United States might connect to the Fedwire Funds Service and CHIPS for high-value payments, to ACH operators, to the RTP network and FedNow for instant payments, and to the Swift network for correspondent banking. A bank in the euro area would connect instead to T2 and to SEPA clearing and instant payment systems. Each rail has its own formats, operating hours and rules, and the hub hides that variety from the channels that create payments.
Message translation has become a central task with the adoption of ISO 20022. Major high-value systems, including T2, CHAPS and Fedwire, moved to ISO 20022 between 2023 and 2025, and Swift ended its coexistence period for cross-border payment instructions in November 2025. A hub that stores payments in a rich internal data model can carry structured data, such as remittance details and full party information, from end to end instead of cutting it down to fit older formats.
Benefits and implementation challenges
Banks adopt payment hubs to cut the cost of running duplicate systems, to add new rails faster, and to apply consistent controls and reporting across all payment types. A single view of payment flows also helps with intraday liquidity management, customer enquiries and regulatory reporting. For companies, routing all payments through one platform improves visibility and control over cash and reduces the number of bank connections each subsidiary must maintain.
The obstacles are mainly practical. Moving long-established flows off legacy payment systems is risky because payments cannot be interrupted, so many projects run for several years and migrate one rail at a time. The hub must integrate with the core banking system, screening tools and accounting systems, and it becomes a single point of failure that needs strong resilience and failover. Banks must also decide whether to build, license or use a cloud-hosted service, weighing control over the system against the cost and speed of delivery.
The term overlaps with several others. A payment switch usually refers to the routing engine for card or ATM transactions, while payment orchestration describes merchant-side platforms that route card and alternative payments across several acquirers and gateways. A payment hub, by contrast, sits inside a bank or corporate treasury and focuses on account-based payments across clearing and settlement systems, although modern hubs increasingly take on several of these roles.