Skip to main content

Payments Enters Beta!

It’s been a little while since our last major drop, but the Hellgate® team has been hard at work! After an intense first quarter of building, we’re thrilled to unveil a powerful new update — Payments is now available in Beta!

Hellgate Payments

Hellgate has long been a front-runner in secure, token-based payment systems. With strong compliance capabilities — including PCI DSS — and support for both traditional and network tokens, we're powering the future of payments. We've built significant momentum operating token-centric ecosystems and mobile wallet integrations, and our on-premise version of Hellgate (aka Hellgate One) is already running at global scale as a trusted payment orchestration platform.

Now, we’re taking things even further. With this Beta release, we’re bringing powerful payment processing capabilities to the cloud version of Hellgate. This means our customers can now orchestrate payments in the cloud with the same unmatched flexibility and reliability they've come to expect — and more.

Processor Independence

Our abstracted payment layer gives you a clean semantic API. Hellgate® Tokens handle compliance and 3-D Secure support, enabling full processor independence out of the box.

Flow-based Orchestration

At the heart of Hellgate® Payments is our flow-based orchestration engine. This powerful tool allows you to design and manage complex payment flows with ease. Process highly sophisticated payment scenarios, with multiple steps and under conditional execution paths.

Efficient Processor Integration

Hellgate Payments is built for processor independence, letting you switch providers without reworking your payment flows. Our architecture supports major processors like Worldpay, Deutsche Bank, and Adyen — and makes it easy to integrate new ones with minimal effort. That means you stay flexible, competitive, and in control.

Additional Changes

It has been a while and many more smaller things have been update and fixes have been made available.

Hellgate® Platform (18ebfbf)

Improvements
  • Added endpoint to check the CVC2 status of a token
  • Allow to consume the CVC2 after authorization
  • Unification of failure details across endpoints
  • Improved handling of proxy forward errors
  • Allow to scope API keys to sub-merchants in eco-system operating model
  • Improved support of device data for wallet services
  • Move authentication data inside the card_holder data attributes in authentication responses
  • Improved validations on reference data
  • Improved support for Diners Club on our authentications
Bugfixes
  • Remove retries on failing card-art requests to the schemes
  • Various small bugfixes and fixed typos
  • Proxy does not send extra content-type header
  • Integration fix for VISA network tokens to accept certain empty values
  • Tokens Webhook: Keep scheme backward compatible

Hellgate® SDKs (v3.5.3)

Improvements
  • Cards: Encrypt additional_data payload on tokenize
  • Cards: User can refresh CVC2 code of a token from WebSDK
Bugfixes
  • Cards: Fix masked input behaviour
  • Cards: Reject cardHandler.process() promise if BE responds 40x / 50x status code
  • Cards: Await cardHandler.process() throws exceptions if card date is not complete or invalid
  • Cards: Show full CVC code up to 4 digits
  • Cards: Card scheme validation by default
  • Cards: UnionPay card number input