How can we enhance this page for you?
We are constantly evolving. Your feedback helps us build more intuitive and informative product pages.
Highlights
Single Integration Layer
Define one versioned API contract and bind it to any PSP or provider through declarative backends. Integration becomes configuration, not code. New providers are onboarded without touching the caller, so your integration effort stops multiplying with every vendor.
Provider Switching Without Rebuild
Re-point the same contract to a different backend, or run several side by side, without the caller ever knowing. Customers re-point rather than re-build, turning a migration into your configuration instead of their project.
Declarative Mapping
Adapter logic lives in versioned templates and a filter chain, not in per-vendor code or deploys. Each imported protocol generates its own OpenAPI 3.1 specification, so every integration is documented and reproducible from the start.
Data Sovereignty and Control
Every invocation is logged with timing and provider response, and message bodies can be JWE-encrypted with rotatable keys. Credentials and keys rotate without downtime, and outbound calls are SSRF-guarded. Your connectivity layer stays under your control, hosted in the EU.
Overview
Vendor
Delivery method
Software as a Service (SaaS)
Categories
Business Applications, DevOps, Infrastructure Software + 1 more categories
Product description
Link is the protocol-abstraction runtime of Hellgates Composable Payment Architecture and the PSP and provider connectivity layer of the platform. It sits between an API and whatever fulfils it: you define a versioned API contract, a protocol, and bind it to one or more real providers through declarative backends. Callers invoke the protocol. Link validates the request, maps it onto the configured backend, dispatches the call, maps the response back and logs the exchange. This cleanly separates the API a consumer codes against from the system that actually serves it. You change what is behind the API without changing the API. Key capabilities: 1. Protocol abstraction: define a versioned, schema-validated API contract once and reuse it across providers. 2. Declarative backends: bind a protocol to any provider through mapping rules, not per-vendor code. 3. Provider switching: re-point the same contract to a different backend, or run several in parallel, without the caller noticing. 4. Operational surface by default: generated OpenAPI, message-level encryption, credential and key rotation, execution audit log. 5. Integration as configuration: migrations become your config instead of your customer's project. 6. Part of the Composable Payment Architecture: works alongside Hellgate Commerce, Guardian and Specter.