DOCSEARCHbyAlgolia
Submit Docs

Hellgate Cloud Platform

website·Indexed 33 days ago

https://developer.hellgate.io

A next-generation payment platform featuring a Composable Payment Architecture (CPA). The platform provides APIs and SDKs for Android, iOS, and Web to handle card tokenization, network tokens, and account information verification. It includes the Guardian product for token management and metadata inquiries, and supports authentication via API keys, OAuth2 bearer tokens, and mTLS.

Tokens
86.6K
Snippets
388
Records
676
Agent score
60%

What's inside Hellgate

  1. Overview of Hellgate Commerce Tokenization

    v2
    Hellgate Commerce allows developers to tokenize and manage cardholder data using a PCI DSS Level 1 certified service. It converts sensitive card data into non-sensitive tokens, reducing the security burden on the merchant. All tokens are stored in Guardian, a PCI-compliant tokenization vault. By default, Hellgate manages the Guardian instance, but users can 'Bring Your Own Guardian' (BYOG) by contacting support to connect an existing instance.

  2. Introduction to the Commerce Unified API for Payments

    v2
    The Commerce Unified API provides a centralized interface for managing payments, transactions, and payment methods. It utilizes a flow-based micro-kernel architecture, allowing developers to define custom payment flows tailored to specific business requirements and integrate with various payment processors, gateways, and services.

  3. Overview of Account Information Service (AIS)

    The Account Information Service (AIS) allows developers to verify a shopper's bank account ownership, holder name, and account identifiers (such as IBAN) in real-time. The service uses PSD2 account-information rails, requiring the shopper to authenticate with their bank and provide consent. This produces a point-in-time snapshot of the account rather than an ongoing data feed. Common use cases include setting up direct debits without micro-deposits or confirming payout accounts before disbursing funds.

  4. Overview of Hellgate Cloud Platform authentication methods

    Hellgate Cloud Platform services support three authentication mechanisms: API keys, OAuth2 access tokens (bearer JWTs), and mTLS. The supported method varies by product:

    • Guardian: OAuth2 (API keys are deprecated)
    • Specter: OAuth2
    • Link: OAuth2
    • Commerce v1: API key or mTLS
    • Commerce v2: API key

  5. Overview of Hellgate Cloud Platform composition patterns

    The Hellgate Cloud Platform provides two ways to implement payment stacks: composing individual standalone services or using 'Commerce', a pre-composed, opinionated payment orchestration service. Because Commerce is built from the same standalone components, users can transition from the composed product to a custom stack without being locked in.

  6. Overview of Guardian Tokenization Service

    Guardian is a fully PCI-compliant tokenization service provided as managed, dedicated infrastructure. It is part of the Composable Payment Architecture (CPA) and can be used as a standalone service. Guardian acts as a protective layer between services and sensitive data, removing sensitive data from the scope of other services to simplify PCI compliance and enable the free combination of services within the Hellgate Cloud Platform.

  7. Overview of the Link protocol meta-schema

    The Link protocol meta-schema (link-protocol-v1) allows users on Standalone instances to author and import custom protocols. Protocols are JSON documents validated against this meta-schema (JSON Schema draft 2020-12) at import time. Bundled instances are locked and do not support custom protocols.
    curl https://developer.hellgate.io/schemas/link-protocol/v1

  8. Overview of Hellgate Cloud Network Token Sandbox

    The Network Token Sandbox is a built-in environment for testing network token provisioning and cryptogram generation on Test tier deployments. It serves as the default backend for network token functionality across both Commerce and Guardian products, allowing developers to test the full lifecycle from provisioning to payment authorization.

  9. Overview of In-Car Payment Architecture

    v2

    In-car commerce is built using a decoupled architecture consisting of the following components:

    • In-Car Application: Third-party apps (e.g., parking, fueling) that use the Wallet Consumer SDK to interface with the car's wallet.
    • In-Car Wallet: A manufacturer-provided component that securely stores payment methods and manages transactions. It uses the Wallet SDK to abstract payment processing.
    • Application Backend: Handles the actual business logic and payment processing via payment gateways. The In-Car Wallet only handles shopper authentication.
    • Wallet Service: A Starfish-provided service that manages wallet assets and ensures secure transactions.
    • Payment Tokens: Upon successful user authentication, the In-Car Wallet generates a payment token. The app provider sends this token to their own backend to request final payment authorization.

  10. Overview of Hellgate Commerce V2 Domains

    Commerce V2 is a programmable platform-as-a-service on the Hellgate Cloud platform organized into four primary domains:

    • Payments: A unified API for processing payments, managing transactions, and handling payment methods. It can integrate with Tokens and Authentications or be used independently.
    • Tokens: Provides PCI DSS-compliant card payment processing by tokenizing cardholder data and managing network tokens to keep sensitive data off internal systems.
    • Authentications: Handles 3-D Secure and FIDO (Passkeys) for payment authentication, including integration with 3DS providers and delegated authentication for mobile wallets.
    • Mobile Wallets: SDKs that enable devices (specifically optimized for in-car payments) to function as payment wallets.

  11. Overview of Commerce customer payments

    v2
    Commerce allows developers to accept online payments directly from a website or application without lock-in to a specific payment processor. A complete implementation requires a back-end connection to the Commerce API and a front-end setup (via SDKs) to interact with customers. The system is designed around specific use-cases to reduce payload complexity and implementation errors.

  12. Overview of Hellgate Cloud Platform products

    The Hellgate Cloud Platform provides a suite of composable payment tools:

    • Commerce V2: A programmable PaaS API for Payments, Tokens, Authentications, and Mobile Wallets.
    • Guardian: A managed, PCI-compliant tokenization service that isolates sensitive payment data from other services.
    • Specter: A real-time fraud intelligence layer that assigns risk scores and blocks bad actors.
    • Link: A PSP abstraction layer providing a single interface to multiple acquirers and PSPs.
    • Hub (Coming Soon): An orchestration fabric for intelligent routing and automatic retries across the payment stack.
    • Pulse (Coming Soon): A real-time observability and metrics layer for transaction data and performance trends.