# Hyperswitch

Open-source payments switch that routes across 100+ processors, driven by a REST API and SDKs.

A Rust payments orchestrator from Juspay. You connect Stripe, Adyen, PayPal and other processors once, then create payments, refunds, payouts and routing rules through one API. The Community Edition is Apache-2.0 and self-hosted with Docker or Helm; reconciliation, revenue recovery and cost observability are paid add-ons.

Alternative to: Spreedly

- Capabilities: adaptable, operable
- Vertical: invoicing-finance
- Shape: business-app
- Form factor: api
- Execution model: deterministic
- Provenance: human-written (recorded, never ranked)
- Repo: https://github.com/juspay/hyperswitch (Apache-2.0), 43569 stars, last commit 2026-09-03
- Last activity: 2026-09-03
- Page: apps/juspay--hyperswitch.html
- JSON: apps/juspay--hyperswitch.json

## Use it when

- I am outgrowing a single Stripe integration and want routing and retries across processors without rewriting checkout
- I want my agent to create payment links, refunds and payouts through one API regardless of which processor settles them

## Gotchas

- Infrastructure-grade: Postgres, Redis and several services; heavier than an SMB invoicing tool
- Reconciliation, revenue recovery and cost observability are paid add-ons even on self-host
- Card data handling still needs your own PCI scope decisions; the vault is a separate service

## Editions

- Self-Host Community Edition: Free, open source
  - source: https://github.com/juspay/hyperswitch
  - container: git clone --depth 1 --branch latest https://github.com/juspay/hyperswitch && cd hyperswitch && scripts/setup.sh
- Self-Host Enterprise Edition: Free, closed source
  - hosted: https://hyperswitch.io/pricing
- Hyperswitch Cloud: Free, closed source
  - hosted: https://app.hyperswitch.io

## Adaptable: make it yours

Effort: config-only (15 things to edit)

Run scripts/setup.sh for a Docker profile, then edit the TOML config for server, database, Redis, locker and connector settings; docker-compose exposes DATABASE_URL, REDIS_URL and the API keys the Control Center uses. Processor credentials are added per connector in the Control Center or over the API, not in the repo.

- Env vars: DATABASE_URL, REDIS_URL, HYPERSWITCH_SERVER_URL, HYPERSWITCH_CLIENT_URL, HYPERSWITCH_CONTROL_CENTER_URL, HYPERSWITCH_PUBLISHABLE_KEY, HYPERSWITCH_SECRET_KEY, LOG_LEVEL, SCHEDULER_FLOW, SDK_ENV
- Config files: config/development.toml, config/docker_compose.toml, config/config.example.toml, config/dashboard.toml, docker-compose.yml
- Prompt files: none
- Accounts you'll need: At least one payment processor account, such as Stripe, Adyen, or PayPal; Hyperswitch Cloud account (Cloud edition only)

## Operable: what an agent can drive

Operability: official. Interface: api at https://api-reference.hyperswitch.io/ (published by the builder, both).

### Reach (partial coverage)

- Create, confirm and capture payments: reachable. Payments API in api-reference.hyperswitch.io; core of the app server
- Refunds and disputes: reachable. Refunds and Disputes endpoints in API reference
- Connect payment processors: reachable. Merchant Connector Account API; also Control Center UI
- Intelligent routing rules: reachable. Routing API and decision-engine service; listed as included in all plans on hyperswitch.io/pricing
- Store cards and payment methods (vault): reachable. Customers and Payment Methods API; Vault included in all plans
- Payouts: reachable. Payouts API; 'Payout Orchestration' included in all plans
- Webhooks to your systems: reachable. Webhook configuration in business profile API
- Hosted checkout and drop-in widgets: reachable. Payment Links API; hyperswitch-web SDK for embedding
- Reconciliation: not reachable. hyperswitch.io/pricing lists Reconciliation as a paid add-on for Community and Enterprise
- Revenue recovery and cost observability: not reachable. hyperswitch.io/pricing lists both as paid add-ons

## Code stack

- Languages: Rust, ReScript, TypeScript
- Frameworks: actix-web
- Package manager: cargo
- Database: PostgreSQL, Redis
- Hosting target: Docker, Kubernetes (Helm), AWS, GCP, Azure

## Evidence and confidence

- formFactor: Rust app server exposed as REST API; Control Center is a separate repo (README Ecosystem Mapping) (confidence 0.9)
- executionModel: no model at runtime for payments; 'AI-powered cost observability' is a paid add-on outside the open edition (confidence 0.85)
- operability: api-reference.hyperswitch.io published by Juspay; official web and mobile SDKs listed in README (confidence 0.95)
- effort: config/ directory in repo with development.toml, docker_compose.toml, config.example.toml; docker-compose.yml env keys (confidence 0.8)
- editions: hyperswitch.io/pricing: Community free, Enterprise custom, Cloud custom; add-ons listed (confidence 0.85)
- active: GitHub pushedAt 2026-09-03; 2,141 open issues at triage
- reach:  (confidence 0.75)

## Open questions

- Reach lines were taken from the API reference index and pricing page, not walked endpoint by endpoint
- Is there a first-party MCP server on the juspay org (none seen in the README)

## Sources

- https://github.com/juspay/hyperswitch (sourcing:invoicing-finance:curated)
- https://hyperswitch.io/pricing (analysis:invoicing-finance)
- https://api-reference.hyperswitch.io/ (sourcing:invoicing-finance:curated)