Yes, you can use crypto with HyperSwitch. HyperSwitch is designed to be a payment orchestration layer, meaning it connects to various payment processors and allows merchants to choose the best options for their needs, including cryptocurrency payments. Here's how it works, and why it's possible:

Key Ways HyperSwitch Supports Crypto:

1. Integration with Crypto Payment Processors: HyperSwitch doesn't directly handle crypto transactions itself. Instead, it integrates with specialized cryptocurrency payment processors. Think of it like this: you wouldn't expect HyperSwitch to handle every type of credit card directly; it connects to Visa, Mastercard, etc., via payment processors. The same principle applies to crypto. Common examples of crypto payment processors that HyperSwitch can integrate with (or likely will in the future if they haven't already) include:

   • BitPay: One of the largest and best-known crypto payment processors.
   • Coinbase Commerce: Coinbase's offering for businesses to accept cryptocurrency.
   • Binance Pay: Binance's payment solution.
   • BTCPay Server: An open-source, self-hosted crypto payment processor (very important for decentralization).
   • Checkout.com Crypto: Checkout.com has added crypto payment processing to its existing suite.
   • Stripe Crypto: In recent years Stripe has introduced support for crypto in certain jurisdictions. HyperSwitch's ability to integrate with Stripe means it can indirectly facilitate crypto through this.
   • NOWPayments: another crypto processor.
   • TripleA: An example of a processor focused on the Asian market.
   • ...and many others. The key is that HyperSwitch is designed to be extensible—to add new connectors as the payment landscape evolves.

2. Routing and Optimization: Just like with traditional payments, HyperSwitch can intelligently route crypto transactions. This is a core feature of payment orchestration:

   • Cost Optimization: Which crypto processor offers the lowest fees for a particular transaction (considering both the processor's fees and potential network fees)? HyperSwitch can help route to the cheapest option.
   • Success Rate Optimization: If one crypto processor is experiencing downtime or has limitations, HyperSwitch can automatically switch to another. Some processors may have better success rates in certain geographic regions or with specific cryptocurrencies.
   • Compliance: Different processors may have different compliance requirements (KYC/AML). A merchant might use HyperSwitch to choose a processor based on the level of compliance needed for a particular customer or transaction.

3. Unified Reporting and Reconciliation: Even if a merchant uses multiple crypto payment processors (and traditional payment methods), HyperSwitch provides a single dashboard and reporting system. This simplifies accounting and reconciliation significantly.

4. Token Support: The specific cryptocurrencies supported depend on the underlying payment processors HyperSwitch is connected to. If BitPay supports Bitcoin, Litecoin, and Ethereum, and HyperSwitch is connected to BitPay, then the merchant can accept those currencies.

How a Transaction Might Work (Simplified Example):

1. A customer chooses to pay with Bitcoin on a merchant's website that uses HyperSwitch.
2. HyperSwitch identifies the customer's location (e.g., for compliance reasons) and the desired cryptocurrency (Bitcoin).
3. Based on pre-configured rules (set up by the merchant), HyperSwitch routes the transaction to, say, Coinbase Commerce.
4. Coinbase Commerce generates a Bitcoin payment address and QR code.
5. The customer sends Bitcoin to that address.
6. Coinbase Commerce confirms the payment (handling the blockchain confirmation).
7. Coinbase Commerce notifies HyperSwitch that the payment is successful (and potentially converts the crypto to fiat currency if the merchant wants that).
8. HyperSwitch updates the merchant's system and provides reporting data.

Important Considerations:

• Specific Integrations: While HyperSwitch can support crypto, it's crucial to check which specific crypto processors it currently has connectors for. This information is usually available in their documentation.
• Merchant Configuration: The merchant needs to configure their HyperSwitch account to enable crypto payments and set up the rules for routing.
• Volatility: Merchants need to be aware of the volatility of cryptocurrencies if they choose to hold the crypto rather than immediately converting it to fiat currency. HyperSwitch itself doesn't mitigate this risk; the choice of processor and the merchant's risk management strategy do.
• Regulatory Landscape: Crypto regulations vary widely by country. HyperSwitch can help with compliance by connecting to compliant processors, but the merchant ultimately remains responsible for ensuring they are operating legally.
• Open Source: HyperSwitch itself is open source. This is relevant because that allows you to inspect its codebase and contribute to it, including adding integrations to a crypto processor of your liking.

In short, HyperSwitch is designed to handle a wide range of payment methods, and cryptocurrency is absolutely within its capabilities through its integration with specialized payment processors. It offers the advantages of flexibility, optimization, and unified management, making crypto payments easier for merchants to implement and manage. Always refer to the latest HyperSwitch documentation for up-to-date specifics.

1. Introduction
2. Architectural Overview
3. Try Hyperswitch
4. Support, Feature requests & Bugs
5. Our Vision
6. Versioning
7. Copyright and License

Here are the key components of Hyperswitch that deliver the whole solution:

• Hyperswitch Backend: Hyperswitch backend enables seamless payment processing with comprehensive support for various payment flows - authorization, authentication, void and capture workflows along with robust management of post-payment processes like refunds and chargeback handling. Additionally, Hyperswitch supports non-payment use cases by enabling connections with external FRM or authentication providers as part of the payment flow. The backend optimizes payment routing with customizable workflows, including success rate-based routing, rule-based routing, volume distribution, fallback handling, and intelligent retry mechanisms for failed payments based on specific error codes.

• SDK (Frontend): The SDK, available for web, Android, and iOS, unifies the payment experience across various methods such as cards, wallets, BNPL, bank transfers, and more, while supporting the diverse payment flows of underlying PSPs. When paired with the locker, it surfaces the user's saved payment methods.

• Control Center: The Control Center enables users to manage the entire payments stack without any coding. It allows the creation of workflows for routing, payment retries, and defining conditions to invoke 3DS, fraud risk management (FRM), and surcharge modules. The Control Center provides access to transaction, refund, and chargeback operations across all integrated PSPs, transaction-level logs for initial debugging, and detailed analytics and insights into payment performance.

Read more at Hyperswitch docs.

You can run Hyperswitch on your system using Docker compose after cloning this repository.

git clone --depth 1 --branch latest https://github.com/juspay/hyperswitch
cd hyperswitch
docker compose up -d

Check out the local setup guide for a more details on setting up the entire stack or component wise. This takes 15-mins and gives the following output

[+] Running 2/2
✔ hyperswitch-control-center Pulled 2.9s
✔ hyperswitch-server Pulled 3.0s
[+] Running 6/0

✔ Container hyperswitch-pg-1 Created 0.0s
✔ Container hyperswitch-redis-standalone-1 Created 0.0s
✔ Container hyperswitch-migration_runner-1 Created 0.0s
✔ Container hyperswitch-hyperswitch-server-1 Created 0.0s
✔ Container hyperswitch-hyperswitch-web-1 Created 0.0s
✔ Container hyperswitch-hyperswitch-control-center-1 Created 0.0s

Attaching to hyperswitch-control-center-1, hyperswitch-server-1, hyperswitch-web-1, migration_runner-1, pg-1, redis-standalone-1

The fastest and easiest way to try Hyperswitch on AWS is via our CDK scripts

1. Click on the following button for a quick standalone deployment on AWS, suitable for prototyping. No code or setup is required in your system and the deployment is covered within the AWS free-tier setup.

   

2. Sign-in to your AWS console.

3. Follow the instructions provided on the console to successfully deploy Hyperswitch. This takes 30-45mins and gives the following output

We support deployment on GCP and Azure via Helm charts which takes 30-45mins. You can read more at Hyperswitch docs.

You can experience the product by signing up for our hosted sandbox. The signup process accepts any email ID and provides access to the entire Control Center. You can set up connectors, define workflows for routing and retries, and even try payments from the dashboard.

For any support, join the conversation in Slack

For new product features, enhancements, roadmap discussions, or to share queries and ideas, visit our GitHub Discussions

For reporting a bug, please read the issue guidelines and search for existing and closed issues. If your problem or idea is not addressed yet, please open a new issue.

Linux for Payments

Payments are evolving rapidly worldwide, with hundreds of processors, fraud detection systems, authentication modules, and new payment methods and flows emerging. Businesses building or managing their own payment stacks often face similar challenges, struggle with comparable issues, and find it hard to innovate at the desired pace.

Hyperswitch serves as a well-architected designed reference platform, built on best-in-class design principles, empowering businesses to own and customize their payment stack. It provides a reusable core payments stack that can be tailored to specific requirements while relying on the Hyperswitch team for enhancements, support, and continuous innovation.

1. Embrace Payments Diversity: It will drive innovation in the ecosystem in multiple ways.
2. Make it Open Source: Increases trust; Improves the quality and reusability of software.
3. Be community driven: It enables participatory design and development.
4. Build it like Systems Software: This sets a high bar for Reliability, Security and Performance SLAs.
5. Maximise Value Creation: For developers, customers & partners.

This project is being created and maintained by Juspay

Check the CHANGELOG.md file for details.

This product is licensed under the Apache 2.0 License.

The core team of 150+ engineers building Hyperswitch. Keep up the great work! 🥂