Payment Hub
What Is a Payment Hub?
A payment Hub is the central orchestration platform that unifies all of a merchant's payment services—card acquirers, alternative payment methods, fraud tools, token vault, and observability—under a single, programmable interface. Instead of maintaining direct, point-to-point integrations between each service and the merchant's backend, a payment Hub provides one API surface that abstracts and coordinates the entire payment stack, applying routing logic, compliance controls, and business rules in a configurable layer.
Core Functions of a Payment Hub
Multi-Provider Orchestration
The Hub receives payment requests and routes them to the optimal provider based on configurable rules: acquirer cost, historical performance for that card type, provider availability, fraud risk score, and geographic eligibility. Multi-provider orchestration enables competitive pricing leverage across acquirers, failover resilience, and access to payment methods that no single PSP offers comprehensively.
Configurable Payment Flow Management
A payment Hub manages the full transaction lifecycle as a configurable flow: tokenisation, fraud evaluation, 3DS orchestration, authorisation, capture, and settlement webhook processing. Business rules are encoded in the Hub's flow engine, not in the merchant's application code—enabling non-engineering teams to optimise payment performance operationally rather than through software deployments.
Stable, Versioned API Surface
From the merchant's perspective, the Hub exposes a single, versioned API that remains stable regardless of changes to the underlying provider landscape. Adding a new acquirer, adopting a new payment method, or replacing a fraud service are Hub-side configuration changes that do not require the merchant to update their integration.
Payment Hub vs. Monolithic Payment Gateway
A monolithic gateway handles all functions within a single, tightly coupled system. This simplifies initial integration but creates lock-in: the merchant cannot replace the fraud component with a better option without replacing the entire stack. A payment Hub is modular by design—each component can be sourced from the best-fit provider and composed through the Hub's integration layer. The gateway asks "which of our processors should handle this?"; the Hub asks "which provider in the market is optimal for this transaction?".
Hellgate Hub
Hellgate Hub is the orchestration core of the Composable Payment Architecture (cpa). It provides a visual flow builder for no-code payment logic configuration, a REST API for programmatic integration, and native composition with Guardian (tokenisation), Specter (fraud), Link (PSP abstraction), and Pulse (observability). Hub is deployed as dedicated, managed infrastructure per client—ensuring isolation, performance SLAs, and compliance posture appropriate for regulated enterprise environments, without the noisy-neighbour effects of shared SaaS architectures.
