Hyperswitch Unified Checkout

Quick Start Guide • Local Setup Instructions • Backend Server • FAQs
Join us in building HyperSwitch • Community • Bugs and feature requests • Copyright and License

While the Unified Checkout is pre-optimized for maximum conversions, it does not restrict you to stick to a one-size-fits-all approach. Using the SDK APIs, you get complete control over modifying the payment experience by,

• 📝 Including new fields to the payment form on a single processor like Stripe or Braintree
• 💳 Prioritizing payment methods by 90% to add & maintain integrations
• 🎨 Switching themes and layouts of checkout page with full visibility and control

⚡️ Quick Start Guide

Ways to get started with Hyperswitch:

Try it in our Sandbox Environment: Fast and easy to start.

    To integrate Hyperswitch into your project, follow these steps:

• Register: Begin by registering at Hyperswitch to gain access to your dashboard.

• Access Your Dashboard: Once logged in, navigate to your dashboard's home page.

• Find Your Keys: In the sidebar, you can find your API Keys. Here, you can also generate your API Key. Additionally, your Publishable Key is available within the same section.

• Integration: After obtaining your Keys add them to your project's environment variables or configuration file for seamless integration.

🛠️ Try it in Local

    You will need to understand and configure a few configurations before starting the local setup. -

• #### Env Configs for Demo App

• HYPERSWITCH_PUBLISHABLE_KEY: The publishable key of your Hyperswitch account. This key will start with pk_dev_ for local development, pk_snd_ for sandbox, and pk_prd_ for production.

• HYPERSWITCH_SECRET_KEY: The API key of your Hyperswitch account that is used to authenticate API requests from your merchant server.

• HYPERSWITCH_SERVER_URL: The URL of the Hyperswitch backend server. You may use our Sandbox URL (https://sandbox.hyperswitch.io). To do this, go to the Hyperswitch Dashboard, find the "Developers" section, then click on API Keys. Here you can generate an API key (HYPERSWITCH_SECRET_KEY) and copy your publishable key (HYPERSWITCH_PUBLISHABLE_KEY).
  

Alternatively, you can specify that your backend is running locally (e.g. http://localhost:8080). In this case, you will need to create the API key and publishable key locally. Read this hyperswitch docs on how to do this.

• HYPERSWITCH_CLIENT_URL: The URL of your hosted Hyperswitch SDK (e.g. http://localhost:9050). You may also use our Sandbox URL (https://beta.hyperswitch.io/v1).

• SELF_SERVER_URL: The URL of the hosted server file for generating client-secret and for fetching urls & configs (eg: http://localhost:5252).

• #### Env Configs for SDK

• ENV_BACKEND_URL: Sets the endpoint for all the APIs used within the SDK to interact with the backend service. If you are running your own backend service, you can configure and specify its endpoint here for local setups.

• ENV_LOGGING_URL: Specifies a custom logging endpoint where logs generated by the SDK can be sent. This allows you to view and manage logs according to your requirements.

### Setup Node

Check if your machine has node already installed by running the below command on your local machine.

node -v

If your machine does not have node installed in it, you can install it from here

Clone the repo

Clone the repository from Bitbucket and save in your folder.

git clone https://github.com/juspay/hyperswitch-web.git
  cd hyperswitch-web

### Setup the repo

• First install all the node modules by running the following command.

npm install

• Once the installation is successful, you can open two terminals.
  

• On the first terminal run the following command for generating the build:

npm run re:start

• On the second terminal, run the following command for starting the SDK server (by default on http://localhost:9050).

npm run start

Upon success, you should see a message Compiled successfully message on both of your terminals.

• Now that the build is generated successfully, on a third terminal, launch the playground.

cd Hyperswitch-React-Demo-App
     npm install
     npm run start

Now you can launch the demo app on http://localhost:5252/ where you can test your payments.
If you encounter any problems, please refer to the troubleshooting section of the Hyperswitch-React-Demo-App Readme.

> 💡 Alternatively, you can update .env file and use the commands > above

⛁ Backend Server

There are two ways to set up the backend:

• ### Local Setup

• Install in your local system: Configurations and setup required in your system. Suitable if you like to customise the core offering, learn more

• If you are running our backend locally, you can use our Postman Collection for generating the API Key and Publishable Key.

• ### Custom Backend

For configuring customBackendUrl, when calling Hyper function you can pass the customBackendUrl in props

In Payment.js file -

window.Hyper(publishableKey, {
    customBackendUrl: `CUSTOM_BACKEND_URL`,
  });

Warning: Please maintain API compatibility of your server and web app. If any API contracts are manually changed without the corresponding handling in the SDK, there is a possibility of the application not working as expected. Please ensure that you use the compatible versions. The latest releases will have the additional details of the compatible versions of the app server, web app, and the control center.

📊 Custom Logging

Logging from the payment checkout web client is crucial for tracking and monitoring the flow of payments. It provides a transparent record of events, errors, and user interactions, aiding developers and support teams in identifying issues, debugging, and ensuring the security and reliability of payment processes. Well-implemented logging enhances traceability and facilitates a more efficient resolution of potential problems in the payment checkout experience.

Logs are sent to the server via non-blocking Beacon API requests. This means that even if the logging endpoint configured is incorrect, it would not affect the core payment functionalities. You can find more about the structure of logging request payload in the beaconApiCall function in the OrcaLogger.res file.

If you want to collect logs, you can do so by setting up an endpoint on your server to receive, process and persist logs.

In the webpack.common.js file, you would have to enable the logging flag, and configure the logging endpoint and log level.

let logEndpoint =
  sdkEnv === "prod"
    ? "<YOUR_PRODUCTION_LOGGING_ENDPOINT>"
    : "<YOUR_SANDBOX_LOGGING_ENDPOINT>";

// Set this to true to enable logging
let ENABLE_LOGGING = true;

// Choose from DEBUG, INFO, WARNING, ERROR, SILENT
let loggingLevel = "DEBUG";

Now let's test the integration by making a payment from your web client!

🔌 Integrate Hyperswitch on your App

Now that the project is up and running, integrating Hyperswitch on your web-app is fast & easy.

Follow the instructions detailed on our documentation page.

🤔 FAQs

Got more questions? Please refer to our FAQs page.

External Services

• Braintree
• Trustpay
• Sentry
• ApplePay
• GooglePay
• Klarna

Security Documentation

For security compliance, we maintain an inventory of all third-party scripts used in this project with justifications for their necessity. You can view this documentation in our Script Inventory file.

💪 Join us in building Hyperswitch

🤝 Our Belief

Payments should be open, fast, reliable and affordable to serve
the billions of people at scale.

Globally payment diversity has been growing at a rapid pace. There are hundreds of payment processors and new payment methods like BNPL, RTP etc. Businesses need to embrace this diversity to increase conversion, reduce cost and improve control. But integrating and maintaining multiple processors needs a lot of dev effort. Why should devs across companies repeat the same work? Why can't it be unified and reused? Hence, Hyperswitch was born to create that reusable core and let companies build and customise it as per their specific requirements.

✨ Our Values

• Embrace Payments Diversity: It will drive innovation in the ecosystem in

multiple ways.

• Make it Open Source: Increases trust; Improves the quality and reusability of

software.

• Be community driven: It enables participatory design and development.
• Build it like Systems Software: This sets a high bar for Reliability,

Security and Performance SLAs.

• Maximise Value Creation: For developers, customers & partners.

🤍 Contributing

This project is being created and maintained by Juspay, South Asia's largest payments orchestrator/switch, processing more than 50 Million transactions per day. The solution has 1Mn+ lines of Haskell code built over ten years. Hyperswitch Web leverages our experience in building large-scale, enterprise-grade & frictionless payment solutions. It is built afresh for the global markets as an open-source product in Rescript. We are long-term committed to building and making it useful for the community.

The product roadmap is open for the community's feedback. We shall evolve a prioritisation process that is open and community-driven. We welcome contributions from the community.

Community

Get updates on Hyperswitch development and chat with the community:

• Read and subscribe to the official Hyperswitch blog.
• Join our Discord server.
• Join our Slack workspace.

Bugs and feature requests

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].

© Copyright and License

This product is licensed under the Apache 2.0 License.

Thanks to all contributors

Thank you for your support in hyperswitch's growth. Keep up the great work! 🥂