Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

hyperswitch

hyperswitch: Composable open-source payments infrastructure for flexible and modular payment processing.

What problem it solves

Businesses often need to connect multiple payment providers and add capabilities such as routing, retries, vaulting, observability, and reconciliation without rebuilding their payment stack. Hyperswitch addresses this by allowing teams to select and integrate the modules they need without unnecessary complexity or vendor lock-in.

Key features

  • Intelligent payment routing — Routes transactions across numerous payment service providers to support multi-processor payment stacks and intelligent gateway selection.

    Source: README

  • Revenue recovery and retries — Provides configurable retry strategies with controls for card bin, region, payment method, penalty budgets, and recovery transparency.

    Source: README

  • Vault and tokenization — Stores cards, tokens, wallets, and bank credentials in a PCI-compliant vault, while supporting connections to existing vault providers without retokenization or migration.

    Source: README

  • Payment cost observability — Helps teams audit, monitor, and optimize payment costs through self-serve dashboards and actionable information about fees, downgrades, and penalties.

    Source: README

  • Automated reconciliation — Supports two-way and three-way reconciliation with backdated processing, staggered scheduling, and customizable outputs to reduce manual operations and improve audit confidence.

    Source: README

Quick start

Copied verbatim from the project's README.

# One-click local setup

git clone --depth 1 --branch latest https://github.com/juspay/hyperswitch

cd hyperswitch

scripts/setup.sh

Who it may suit

This may suit payment platform teams, merchants, and developers who want multi-provider routing or need to add a focused payments module to an existing stack.

Topics to discuss

  • Which payment modules should form the minimal production-ready deployment?

  • How should intelligent routing balance authorization outcomes, processing costs, and provider resilience?

  • What contribution would be most useful for connector maintainers and open-source adopters?


Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.

Read the original README https://github.com/juspay/hyperswitch#readme

ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.

github.comhttps://github.com/juspay/hyperswitch

Comments

…