Hub connects your entire payment stack.

Hub is Hellgate's orchestration fabric – the component that connects your entire payment stack. It links acquirers, PSPs, and fraud-prevention tools into one coordinated system, with intelligent routing, automatic retries, and failover across providers.

Hub is PSP-agnostic and rule-based, so payment teams control how each transaction flows – which provider it goes to, when to retry, and when to step up authentication – from a single control point rather than in scattered application code.

→ Explore Hub

A payment gateway connects your checkout to a single acquirer and passes the transaction through. A payment orchestration layer sits above multiple gateways and acquirers, deciding in real time which route each transaction should take. Hub is Hellgate's orchestration fabric: it applies routing rules, handles failover, integrates fraud scoring from Specter, and gives you one API across all your providers.

The difference is intelligence and portability: a gateway is a pipe; orchestration is the logic that controls which pipe to use, and when to switch.

→ Glossary: Payment Orchestration

Yes. Hub is PSP-agnostic by design and built for multi-PSP, multi-acquirer setups. You can add providers per market or use case, route transactions to the best option for each, and fail over automatically when one provider degrades or declines.

For enterprises, running several PSPs behind one orchestration layer means better geographic coverage, higher acceptance rates, and negotiating leverage – without maintaining separate integrations in your own code.

→ See multi-PSP orchestration

Highly. Hub flows are rule-based: you define how transactions are routed, when retries fire, which provider is primary vs. fallback, and when to enforce steps such as 3-D Secure – all as configurable policies rather than hard-coded logic. AI-native flow support is on the roadmap.

Because CPA keeps concerns separate, you can rearrange these flows – for example, run fraud before or after authorization – without rewriting your integration.

→ See flow customization

Not directly – and that's intentional. In line with CPA, Hub orchestrates but doesn't bundle fraud or KYC into itself. Instead, it integrates those capabilities as separate services: fraud decisioning through Specter, and third-party fraud/KYC providers through Link.

This keeps each concern independent, so you can choose or swap your fraud and identity providers without disturbing your orchestration logic.

→ See how Specter adds fraud intelligence

Yes. Hub can orchestrate flows for your own payment engine or a third-party stack – Commerce is not required. As a standalone CPA component, Hub's job is routing and coordination, so it sits on top of whatever executes the actual authorization.

This lets enterprises that already have a payment engine gain orchestration, routing, and failover without replacing what they've built.

→ Run Hub with your own engine

Hub lifts acceptance in several ways: intelligent routing sends each transaction to the provider most likely to approve it; automatic retries and failover recover transactions when a provider declines or degrades; and it can enforce authentication or network tokens where they improve approval odds.

Combined with local acquiring in key markets, this reduces avoidable declines – a direct revenue gain for high-volume merchants where even small approval-rate improvements are material.

→ See how Hub lifts acceptance

Hub consumes the Specter Score – a real-time risk score assigned to each transaction – and executes configurable policies based on it: allow, block, step up to 3-D Secure, or route differently. Because Specter integrates natively as a CPA component rather than a bolted-on third-party API, its scoring feeds directly into Hub's routing and decisioning with no added latency.

You define the thresholds and rules; Hub enforces them in the payment flow.

→ See Specter + Hub decisioning

Yes. Merchants define their own routing rules, retry logic, and risk thresholds in Hub. You decide which provider handles which transaction, the conditions that trigger a fallback, and the score thresholds at which fraud policies act. Rules are managed centrally rather than embedded in application code.

This gives payment and risk teams direct control to tune performance, cost, and risk appetite as conditions change – without a release cycle.

→ Configure routing and thresholds

Yes. By abstracting acquirers and PSPs behind one orchestration layer – and, via Link, behind stable API contracts – Hub lets you add, remove, or switch providers without re-building your integration. Your payment logic lives in Hub, not in a single vendor's platform.

That portability preserves negotiating leverage and resilience: if a provider's pricing or performance changes, you can shift volume rather than being trapped.

→ How CPA removes lock-in

For enterprises running several acquirers, Hub centralises what would otherwise be fragmented logic: unified routing across all acquirers, automatic failover between them, consistent retry behaviour, and one integration surface instead of many. It supports single-merchant, platform, and ecosystem models, so multi-entity and multi-market structures are handled coherently.

The result is higher acceptance, lower operational overhead, and the flexibility to optimise cost and performance per market.

→ Hub for multi-acquirer enterprises

Hub is part of the Hellgate Cloud Platform and is rolling out for general access alongside Specter, Link, and Pulse, complementing Guardian and Commerce which are already available. Real payment volume already flows through Hellgate's orchestration and abstraction layers today.

If you want to evaluate Hub for your stack, the fastest path is to talk to Hellgate about access and a scoped pilot for your use case.

→ Book a demo to discuss Hub access