Home

Hellgate CPA

Commerce

Commerce

Payment Engine

Commerce is the fast lane into Hellgate CPA.

Commerce is the opinionated payment service for fast-moving teams. Designed for those who want best-practice orchestration patterns out of the box. Commerce handles routing, retries, and provider abstraction with no infrastructure overhead based on the powerful Hellgate CPA infrastructure.

Talk to Sales

No Acquirer or PSP should dictate your roadmap

Teams burn cycles wiring up acquirers, chasing down failed retries, and patching compliance gaps, only to find themselves locked into a single PSP’s rules and roadmap.

The result?

Slower launches, brittle integrations, and a mounting stack of operational overhead that distracts from actually growing the business.

Single Acquirer or PSP lock-in
Complex infrastructure
Scalability bottleneck

Introducing Hellgate Commerce:
No lock-in, no mess - just reliable, ready-made orchestration.

1
Initiate

Your app calls Commerce through a single API or headless SDK, starting the payment or refund lifecycle without complex setup.


2
Route

Commerce applies rule-based logic to route transactions across acquirers and PSPs, automatically handling retries, 3-D Secure, and provider abstraction.

3
Settle

Compliance and observability are built in, giving you full transparency into payment outcomes without the infrastructure overhead.

No-Hassle Compliance

Stay ahead of regulations without building a compliance team. Commerce bakes in orchestration patterns that minimize risk and reduce operational overhead

Turnkey Orchestration

Spin up best-practice payment flows instantly. Commerce gives you routing, retries, and provider abstraction out of the box—no heavy infrastructure build required.

End-to-End Observability

Gain full visibility into every payment event. From routing decisions to retries, Commerce provides transparent metrics and monitoring for continuous optimization

Rule-Based Routing

Dynamically route transactions across acquirers and PSPs with flexible business logic. Optimize success rates while keeping full control of how payments move through your system

Optimized Integrations

Skip the complexity of piecemeal integrations. Commerce ships with pre-built, high-throughput connections to leading providers, ensuring speed to market and reliability at scale

Headless SDKs for Fast Integration

Integrate sleekly into your frontend stack. Commerce’s headless SDKs make it simple to embed payments into your product experience without slowing down your roadmap

Hellgate Commerce is perfect…

Hellgate Commerce is perfect…

For teams wanting orchestration and a payment engine out of the box

Commerce combines routing, retries, provider abstraction, and observability in a single turnkey layer. No need to wire up acquirers or build complex orchestration logic - your team gets proven payment patterns from day one

For SaaS, scale-ups and eCommerce players who want and need speed

When growth depends on fast execution, Commerce eliminates the drag of custom infra and vendor lock-in. Go live quickly, expand globally with pre-built integrations, and keep payments reliable at scale.

If you're tired of figuring out compliance and want a turnkey solution that just works

Commerce handles the heavy lifting of compliance, including acquirer-agnostic 3-D Secure and PCI-aligned orchestration. That means fewer late-night fire drills and more focus on building your product.

For product leaders who want control,

not lock-in

Commerce is acquirer-agnostic and built on the composable CPA framework, giving you freedom to scale without being boxed in by a single PSP. It’s the payment engine for teams that want to move fast today and keep their options open for tomorrow

Use-cases

SaaS

SaaS platforms scaling globally

Expand into new regions without re-building your payment stack. Commerce handles acquirer routing and compliance, so you can focus on customer growth instead of integrations.

eCommerce

High-Growth eCommerce Stores

Reduce checkout failures and boost conversion by routing transactions dynamically across multiple PSPs. No more lost revenue from single-provider setups.


Marketplaces

Marketplaces & Platforms

Support multi-merchant and ecosystem models out of the box. Commerce abstracts providers while giving you flexible orchestration for complex operating models.


Boost Conversion

Scale Globally

Stay Flexible

Cut Vendor Lock-In

Move Faster

See Commerce in action

Built on
Hellgate CPA Infrastructure

Built on
Hellgate CPA Infrastructure

Built on
Hellgate CPA Infrastructure

Hellgate's Composable Payment Architecture (CPA) enables businesses to choose the modules they need or combine them with their existing engine, PSPs, or providers.

Hellgate® CPA

Commerce

Payment Engine

Hub

Orchestration Fabric

Guardian

PCI Vault & Tokenization

Specter

Fraud Intelligence layer

Link

PSP Abstraction

Pulse

Observability & Metrics

Commerce payment engine processes transactions through Hub, applying routing and logic rules to execute payments and manage provider flows in real time. Guardian provides tokenization & compliance when needed.

Hellgate® CPA

Commerce

Payment Engine

Commerce payment engine processes transactions through Hub, applying routing and logic rules to execute payments and manage provider flows in real time. Guardian provides tokenization & compliance.

Hub

Orchestration Fabric

Guardian

PCI Vault & Tokenization

Specter

Fraud Intelligence layer

Link

PSP Abstraction

Pulse

Observability & Metrics

Hellgate® CPA

Commerce

Payment Engine

Hub

Orchestration Fabric

Guardian

PCI Vault & Tokenization

Specter

Fraud Intelligence layer

Link

PSP Abstraction

Pulse

Observability & Metrics

Commerce payment engine processes transactions through Hub, applying routing and logic rules to execute payments and manage provider flows in real time. Guardian provides tokenization & compliance when needed.

Built for developers
from day one.

Commerce integrates through a single API and headless SDKs, making it simple to embed payments directly into your product. Whether you’re adding Commerce as your first engine or replacing legacy orchestration, you get clean abstractions without the infra burden.

One consistent API across PSPs and acquirers

Headless SDKs for seamless front-end integration

Live, cluster-specific API references

Examples and best-practice orchestration patterns out of the box

See Commerce in action

const { Hellgate } = window;
const client = await Hellgate.init('d5529f03-e84a-4a43-867c-b3412a097e63', {
  base_url: 'https://sandbox.hellgate.io',
});

// get the handler for card payments
const cardHandler = await client.use('CARD');

// create the one-line form
const cardForm = cardHandler.createForm({
  // customize styles
  style: {
    fonts: ['https://fonts.googleapis.com/css2?family=Nunito:wght@300;400;500;600;700;800&display=swap'],
    base: {
      fontFamily: 'Nunito, sans-serif',
      color: '#111',
      fontSize: '16px',
      '::placeholder': { color: '#6b7280' },
    },
  },
});
const cardholderField = cardHandler.createTextField();

// and mount it
cardForm.mount('#my-form-element');
cardholderField.mount('#cardholder-element');

// use an existing button to process the data
const submitButton = document.getElementById('my-submit-button');

submitButton.addEventListener('click', async () => {
  try {
    const result = await cardHandler.process({
      // the value from cardholderField will be extracted automatically
      cardholder_name: cardholderField,
    });

    const resultElement = document.getElementById('result');
    const errorElement = document.getElementById('error');

    // handle the result
    if (result.status === 'success' || result.status === 'pending') {
      resultElement.textContent = 'Processing has been successfully completed';
      errorElement.textContent = '';
    } else {
      // processing failed, failure reason could be found in the data attribute
      resultElement.textContent = '';
      errorElement.textContent = result.data.reason;
    }
  } (err) {
    // something went wrong before processing could begin (e.g., a network issue or an internal backend error)
  }
});

Acquirer-Agnostic 3-D Secure

Built-In Compliance Patterns

End-to-End Transparency

Stay protected
without slowing down.

Commerce bakes in the compliance guardrails teams usually have to build themselves.

From acquirer-agnostic 3-D Secure to PCI-DSS compliant orchestration patterns, every transaction is handled with security and regulation in mind.

That means fewer risks, fewer surprises, and no late-night compliance fire drills.


FAQ

FAQ

FAQ

What is Hellgate Commerce?

Commerce is Hellgate's unified payment engine – a programmable platform-as-a-service that handles payments, tokens, authentications, and mobile wallets through a single, consistent API. It is the CPA-based implementation of the platform, composing independent services (such as Guardian for tokenization) into a complete payment-processing product.

Commerce is designed for merchants and platforms that want one API to accept, authenticate, and manage card payments across channels and markets, without stitching together multiple point solutions.

→ Explore Commerce

Label

What payment operations does Commerce support?

Commerce is organised around four domains: Payments (one-off, recurring, and unscheduled, with capture, void, and refund), Tokens (tokenize and manage cardholder data, including network tokens), Authentications (3-D Secure for card-not-present transactions), and Mobile Wallets (including branded in-car wallets).

Both customer-initiated and merchant-initiated (off-session) flows are supported, covering subscriptions, installments, and unscheduled charges.

→ See Commerce capabilities

Label

Is Commerce PCI compliant?

Yes. Commerce is fully PCI compliant, achieved through Guardian, Hellgate's PCI DSS Level 1 certified tokenization service. Card data is captured and stored inside a certified cardholder data environment operated by Hellgate, so raw PANs never need to touch your own systems.

The practical benefit is a dramatically reduced PCI scope for your business – often qualifying for a lighter self-assessment questionnaire instead of a full audit.

→ How Guardian delivers PCI compliance

Label

What operating models does Commerce support?

Commerce supports three operating models: single merchant (one business accepting payments), platform (a business managing payments on behalf of sub-merchants), and ecosystem (complex multi-party arrangements across markets and entities).

This range makes Commerce suitable for marketplaces, platforms, and enterprises with multiple legal entities or business units that need consistent payment logic across all of them.

→ Read about operating models

Label

How fast can I integrate Commerce?

Commerce is built for fast integration: SDKs for iOS, Android, and Web, a consistent REST API, webhooks, and comprehensive documentation mean most teams integrate in days rather than weeks. A test (sandbox) account can be created for free to build and validate flows before going live.

Because Commerce follows CPA principles, you can start with the flows you need and extend later without re-architecting.

→ Create a test account

Label

Do I need Commerce to use Guardian, Hub, or Specter?

No. Commerce is optional. Guardian, Hub, Specter, and Link are all standalone CPA components that you can adopt independently of Commerce and compose with your own payment engine or a third-party stack.

Commerce is the ready-made, composed option for teams that want a complete payment engine out of the box; if you already have one, you can still use the individual Hellgate services around it.

→ Compose only what you need

Label

Does Commerce support 3-D Secure authentication?

Yes. Commerce handles EMV 3-D Secure (3DS) authentication for card-not-present transactions, both integrated into a payment and as a standalone authentication service. It supports one-off, recurring, and installment authentication flows, and provides configuration and failure handling so you can meet Strong Customer Authentication (SCA) requirements.

Standalone 3DS lets you authenticate through Hellgate even when you authorize elsewhere – useful in composable setups.

→ Read about 3-D Secure in Commerce

Label

Can Commerce run on shared or dedicated infrastructure?

Both. Commerce V2 can run on dedicated, single-tenant infrastructure – provisioned exclusively for your organisation with physical data isolation – or on a shared, multi-tenant Commerce V2 service available for both test and production tiers.

The shared service is fast to onboard and cost-effective when full isolation is not a hard requirement; dedicated is the choice when data sovereignty, regulatory compliance, or strict performance SLAs apply.

→ Compare shared vs. dedicated Commerce

Label

Does Commerce support recurring and unscheduled payments?

Yes. Commerce supports the full range of merchant-initiated transactions: initial and subsequent recurring payments (subscriptions, installments) and unscheduled off-session charges (top-ups, usage-based billing). It stores the credentials-on-file and network-token context needed to keep these payments authorising over time.

This is critical for subscription, mobility, and usage-based businesses where declined renewals directly hit revenue.

→ See merchant-initiated payments

Label

What SDKs does Commerce provide?

Commerce ships native SDKs for iOS and Android, plus a headless Web SDK for browser-based payment experiences. The SDKs handle sensitive card capture and tokenization on the client side, so raw card data is collected securely and kept out of your servers, supporting a reduced PCI scope.

The headless Web SDK gives full control over your checkout UI while Hellgate manages the secure session and card flow.

→ Browse the SDKs

Label

Can Commerce handle in-car and wallet payments?

Yes. Commerce includes mobile-wallet capabilities and supports branded in-car wallet implementations, letting automotive and mobility businesses embed secure payments directly into the vehicle for fuel, EV charging, parking, tolls, and connected-car services.

In-car flows combine tokenization and strong authentication (such as FIDO) so transactions initiated from the vehicle stay secure and compliant with global standards.

→ Build in-car payment experiences

Label

How does Commerce handle network tokens?

Commerce supports network tokens as an add-on: scheme-issued tokens that replace the raw card PAN. Network tokens improve authorization rates, reduce fraud, and keep subscriptions alive when a customer's card is reissued, because the token is automatically kept up to date by the scheme.

Commerce can request network tokens and payment-data bundles (including cryptograms) for use in your acquirer integration, without exposing sensitive card details.

→ Learn about network tokens

Label

Can I migrate existing tokens from another provider into Commerce?

Yes. Commerce supports token import, including backing up card payment methods from third-party vaults such as Stripe, so you can move your stored credentials onto Hellgate for use with any processor. Import runs are trackable, and reconciliation reports let you verify that migrated tokens map correctly.

This removes a major barrier to switching – you keep your existing customers' saved cards without asking them to re-enter details.

→ See token migration

Label

Do I need Commerce to use Hub or Guardian?

No. Commerce is optional. Guardian, Hub, Specter, and Link are all standalone CPA components you can adopt independently of Commerce and compose with your own payment engine or a third-party stack.

Commerce is the ready-made, composed option for teams that want a complete payment engine out of the box; if you already have one, you can still use the individual Hellgate services around it.

→ Compose only what you need

Label

See Commerce in action

Let our product specialists guide you through the product, touch upon all functionalities relevant for your individual use case and answer all your questions directly.

Talk to an engineer

Contact Sales

See Commerce in action

Let our product specialists guide you through the product, touch upon all functionalities relevant for your individual use case and answer all your questions directly.

Talk to an engineer

Contact Sales

See Commerce in action

Let our product specialists guide you through the product, touch upon all functionalities relevant for your individual use case and answer all your questions directly.

Talk to an engineer

Contact Sales