Managed Cloud Infrastructure

Payment orchestration,
engineered for scale.

OpenSwitch is a paid, managed cloud service. We host, configure, and operate the orchestration layer while you retain control of provider accounts and business requirements.

Talk to salesExplore service
routing_preview.logIllustrative
>[req_892b] Validating payload constraints...
>[req_892b] Regional policy matched: EU_Core
>[req_892b] Selecting optimal route: PSP_Europe_Main
>[req_892b] Dispatching securely...
>[req_892b] Response normalized and returned
_
Routing policy
Configured
Service model
Managed
Hosted operations within the agreed scope.
Topology

The managed control layer

OpenSwitch hosts and operates the orchestration layer between your checkout and approved providers. We agree on and operate the supported configuration, built on Hyperswitch.

Managed Cloud Topology
Customer System
Merchant App
Payment request
Managed Core
OpenSwitch
Hosted Hyperswitch
Configured Policies
Operated Service
Configured Accounts
Approved provider
Configured account
Market method
Payment Rails
Card railsBank railsLocal rails
Selected path
Configuration-dependent
Managed operation
Provider bounds
Integration Contract

Verified service boundary

The public reference documents the implemented sandbox contract and an owner-reviewed support inventory. Production coverage remains implementation-specific until confirmed in writing.

  • 5 supported public capabilities, each with a defined scope
  • Provider, payment-method, market, and operation status in one inventory
  • Planned and unsupported capabilities clearly separated
  • Reviewed by OpenSwitch Product & Engineering
Inventory Manifest

Know what is supported before design

Review exact sandbox capabilities and production items that require written confirmation before OpenSwitch configures your managed environment.

Review API reference
Capabilities

What the orchestration layer provides

Configured orchestration

OpenSwitch configures an orchestration layer around your approved providers, payment methods, markets, and operating requirements.

Managed operations

Our team operates the hosted service and reviews eligible routing or recovery behavior against your agreed implementation scope.

Consistent integration

Use the published sandbox contract while OpenSwitch handles the complex managed platform boundary behind it.

Operational visibility

Review the real-time payment activity and reporting fields included in your approved managed-service scope.

Provider strategy

Bring your provider relationships and requirements; OpenSwitch coordinates the approved configuration robustly.

Integration evaluation

Search verified coverage, then confirm provider accounts, credentials, markets, methods, and operations during design.

Positioning

A managed service, not a PSP

OpenSwitch does not replace your payment providers. It is a paid managed cloud service that hosts the orchestration layer, with behavior confirmed per implementation.

Service model

Single provider / PSP
Provider service
OpenSwitch
Managed cloud orchestration

Platform operations

Single provider / PSP
Provider-owned
OpenSwitch
Hosted and operated by OpenSwitch

Provider setup

Single provider / PSP
Customer configures
OpenSwitch
Accounts supplied; Scope configured

Routing behavior

Single provider / PSP
Provider-defined
OpenSwitch
Agreed policies where supported

Commercial model

Single provider / PSP
Provider terms
OpenSwitch
Transaction-fee service
Connectors

Evaluate the integrations

Use the directory to inspect verified scope. Production availability is confirmed during solution design, not implied automatically.

Provider accounts
Payment methods
Markets
Operations
Routing inputs
Sandbox access
Process

Clear responsibilities

OpenSwitch hosts the platform and manages configuration, operations, updates, and support. Customers provide provider relationships, credentials, and requirements.

OpenSwitch is not a customer-operated deployment. There is no free tier. Pricing is transaction-based and scoped during sales.

  1. 01
    Phase 01

    Review fit

    Share volume, providers, methods, and flow requirements.

  2. 02
    Phase 02

    Confirm scope

    We validate integrations and document behavior.

  3. 03
    Phase 03

    Configure

    We set up the hosted environment and provider policies.

  4. 04
    Phase 04

    Operate

    We support the service while your team runs your app.

Move to a managed payment strategy.

Tell us about your payment volume, provider accounts, and integration needs. We’ll confirm fit and scope the managed service.

Talk to salesReview integrations