LogoLogo
Explore with DeepWikiJoin Slack CommunityContact Us
  • About Hyperswitch
    • Exploration Guide
    • Overview
    • Payments Suite
    • Payments Modules
      • Cost Observability
      • Revenue Recovery
      • Vault
        • Server to Server Vault tokenization
        • Vault SDK Integration
        • Hyperswitch Vault: Pass Through Proxy Payments
      • Intelligent Routing
      • Reconciliation
        • Getting Started with Recon
      • Alternate Payment Method Widgets
        • Hyperwidget Integration Guide
    • Roadmap - Q2 2025
      • Previous Roadmap - Q1 2025
      • Previous Roadmap - Q4 2024
      • Previous Roadmap - Q3 2024
      • Previous Roadmap - Q2 2024
      • Previous roadmap - Q1 2024
      • Previous roadmap - Q4 2023
  • Use-Cases
    • For SaaS Businesses
    • For B2B SaaS Businesses
    • For E-Commerce Businesses
    • For Marketplace/Platforms
  • Explore Hyperswitch
    • Payment Orchestration
      • Accept Payments
        • Connectors
          • Activate Connector on Hyperswitch
          • Try a Payment
          • Available Connectors
            • ACI
            • Adyen
            • Airwallex
            • Authorizedotnet
            • Bambora
            • Bank of America
            • Billwerk
            • Bluesnap
            • Braintree
            • Checkout
            • Coinbase
            • Cybersource
              • Apple Pay
              • Google Pay
            • dLocal
            • Fiserv
            • GlobalPayments
            • GoCardless
            • Klarna
            • Mollie
            • MultiSafepay
            • Nuvei
            • OpenNode
            • Paypal
            • PayU
            • Prophetpay
            • Rapyd
            • Shift4
            • Stripe
            • TrustPay
            • Volt
            • Worldline
            • Worldpay
            • Zen
            • Netcetera
              • Authenticating Payments via Netcetera Through HyperSwitch SDK
        • Setup Payment Methods
          • Cards
          • Wallets
            • Apple Pay
              • Web Domain
              • iOS Application
            • Google Pay
            • PayPal
          • Pay Later
          • Banks
            • Bank Debits
            • Bank Redirects
            • Bank Transfers
            • Open Banking
          • Crypto
          • Test Credentials
        • Payment Links
          • Configurations
          • Create Payment Links
          • Secure Payment Links
          • Setup Custom Domain
        • Save a Payment Method
        • Manual Capture
        • Incremental Authorization
        • Tokenization & Card Vault
          • Network Tokenisation
        • Supported Payment Workflows
        • Co-badged Cards
        • Webhooks
      • Process Payouts
        • Getting Started with Payouts
        • Using Saved Payment Methods
        • Smart Router for Payouts
        • Smart Retries in Payout
        • Payout Links
      • Smart Routing
        • Rule Based Routing
        • Volume Based Routing
        • Default Fallback Routing
      • Smart Retries
        • 3DS Step-up Retries
      • 3DS / Strong Customer Authentication
        • Setting up 3DS Decision Manager
        • Native 3DS Authentication
        • External Authentication for 3DS
      • Fraud & Risk Management
        • Activating FRM in Hyperswitch
        • Fraud Blocklist
      • Subscriptions
        • PG Agnostic Card Forwarding
        • Zero Amount Authorization
      • Split Payments
        • Stripe Split Payments
        • Adyen Split Payments
        • Xendit Split Payments
    • Checkout Experience
      • Customizable and Native Integrations
        • Web
          • Node And React
          • Customization
          • Error Codes
          • Node and HTML
          • Vanilla JS and REST API Integration
        • Android
          • Kotlin with Node Backend
          • Customization
          • Features
        • iOS
          • Swift with Node Backend
          • Customization
          • Features
        • React Native
          • React Native with Node Backend
          • Card Widget
          • Customization
        • Flutter
          • Flutter with Node Backend
          • Customization
        • Headless SDK
        • Server Setup
      • Click To Pay
        • Visa Click to Pay: V1 to V2 Migration
      • Payment Methods Management
    • Payment Operations
      • Managing Accounts and Profiles
        • ⚙️Control Centre Account setup
        • Hyperswitch Account Structure
      • Manage Your Team
      • Analytics & operations
        • Exporting payments data
      • Disputes / Chargebacks
      • Surcharge
        • Surcharge Setup guide
      • Multi-Tenancy
      • Data migration
        • Import data to Hyperswitch
        • Export data from Hyperswitch
    • Security and Compliance
      • PCI Compliance
      • Data Security
      • GDPR compliance
      • Identity and Access Management
    • E-commerce Platform Plugins by Hyperswitch
      • 🔌WooCommerce Plugin
        • Setup
        • Roadmap
        • Compatibility
        • FAQs
      • Saleor App
        • Setup
      • Automatic Tax calculation for Express Checkout wallets
  • Hyperswitch open source
    • Overview
      • Run Hyperswitch Locally Using Docker
        • Run Additional Services
      • Development Environment Setup
        • Backend
          • Configure and Run the Application
          • Try out APIs
        • SDK (Frontend)
        • Control Center
    • Deploy on AWS
      • Deploy on AWS using CloudFormation
      • Component-wise Deployment
        • Deploy app server
        • Deploy Control Center
        • Deploy web client
          • Production ready deployment
          • Integrate web client on your web app
          • Playground deployment for prototyping (optional)
        • Deploy Card Vault
          • Production ready deployment on AWS
          • Cloud setup guide
    • Deploy on Kubernetes
      • Deploy on GCP Using Helm Charts
      • Deploy on Azure Using Helm Charts
    • Account setup
      • Using Hyperswitch Control Center
      • Test a payment
      • Using postman
    • Troubleshooting
  • Testing Payments
  • Check list for Production
    • Going live
      • For SaaS Setup
      • For On-Prem Setup
        • Monitoring
        • PCI compliance
          • Get started
          • Completing the SAQ
        • Data Security
        • Updates
  • Learn more
    • API Reference
    • Connectors Supported
    • SDK Reference
      • React
      • JS
      • Custom Events
    • Hyperswitch architecture
      • Router
      • Storage
      • A Payments Switch with virtually zero overhead
    • Payment flows
    • Blog
  • Community Guidelines
Powered by GitBook
On this page
  • Part 2: Deploy Hyperswitch on Kubernetes Using Helm
  • Expose Hyperswitch Services Locally
  • Test a payment
  • Troubleshooting
  • Customization & Configuration
  • Uninstall Hyperswitch & Delete GKE Cluster
  • Explore Further

Was this helpful?

  1. Hyperswitch open source
  2. Deploy on Kubernetes

Deploy on GCP Using Helm Charts

Last updated 5 days ago

Was this helpful?

Compliance

  • Vulnerability Disclosure
  • PCI DSS 4.0
  • ISO 27001:2022

Community

  • Slack
  • Discord
  • GitHub Discussion

Part 1: Setting Up a Kubernetes Cluster on GCP

Step 1: Set Up GCP Account and Enable Kubernetes Engine API

  1. Sign In to Google Cloud Console:

  • Navigate to the , and click on Go to my console.

  1. Create a Project:

  • Open your project picker:

  • Click New Project:

  • Provide a project name, and click Create:

If you are using an existing project, note the project ID for later use.

  1. Enable Kubernetes Engine API:

  • Navigate to APIs & Services > Library or search for it:

  • Search for Kubernetes Engine API and click Enable:

You'll need to provide billing information in order to proceed further. Follow the necessary steps and ensure the Kubernetes Engine API is enabled.

Step 2: Install Required Tools

  1. Google Cloud CLI (gcloud)

  1. kubectl

Ensure you only have 1 version of kubectl installed to avoid enviornmental conflict.

  1. Helm

Step 3: Create a Kubernetes Cluster

  1. Create the Cluster:

  • Run the following command to create a Kubernetes cluster:

gcloud container clusters create <CLUSTER_NAME> \
    --zone <ZONE> \
    --num-nodes <NUMBER_OF_NODES> \
    --machine-type e2-standard-4

Replace:

  • <CLUSTER_NAME>: A unique name for your cluster.

  • <ZONE>: The GCP zone (e.g., us-central1-a).

  • <NUMBER_OF_NODES>: Number of nodes in your cluster.

  • e2-standard-4: Machine type with 4 CPUs and 16GB RAM per node.

Example:

gcloud container clusters create hypers-cluster \
    --zone us-central1-a \
    --num-nodes 1 \
    --machine-type e2-standard-4    

Choose a --zone that's near you

  1. Verify the Cluster:

  • Fetch cluster credentials to allow kubectl to interact with it:

    gcloud container clusters get-credentials <CLUSTER_NAME> --zone <ZONE>
  • Confirm the nodes are ready:

    kubectl get nodes

Part 2: Deploy Hyperswitch on Kubernetes Using Helm

Step 1: Add and Update the Hyperswitch Helm Repository

  1. Add the Hyperswitch Helm repository:

helm repo add hyperswitch https://juspay.github.io/hyperswitch-helm
  1. Update Helm repository to fetch the latest charts:

helm repo update

Step 2: Prepare the Kubernetes Cluster

  1. Label Kubernetes Nodes: Ensure nodes meet the minimum requirements: 4 CPUs and 6GB memory.

  • Label your nodes:

kubectl label nodes <your-node-name> node-type=generic-compute
  • List nodes to confirm labels:

kubectl get nodes --show-labels
  1. Create a Namespace:

  • Create a dedicated namespace for Hyperswitch:

kubectl create namespace hyperswitch

Step 3: Install Hyperswitch

  1. Deploy Hyperswitch using Helm. Replace <release-name> with your desired release name and <namespace> with the namespace you created:

helm install hypers-v1 hyperswitch/hyperswitch-stack -n hyperswitch
  1. Verify the Deployment:

  • Check the status of all deployed pods:

kubectl get pods -n hyperswitch
  • Ensure all pods are in the Running state.

That's it! Hyperswitch should be up and running on your GCP account 🎉 🎉

Expose Hyperswitch Services Locally

Use the following command for port-forwarding to access the services. Replace <namespace> with your namespace:

kubectl port-forward service/hyperswitch-server 8080:80 -n hyperswitch > /dev/null 2>&1 & \
kubectl port-forward service/hyperswitch-control-center 9000:80 -n hyperswitch > /dev/null 2>&1 & \
kubectl port-forward service/hyperswitch-web 9050:9050 -n hyperswitch > /dev/null 2>&1 & \
kubectl port-forward service/hypers-v1-grafana 3000:80 -n hyperswitch > /dev/null 2>&1 & \
kubectl port-forward service/hypers-v1-vector 3103:3103 -n hyperswitch > /dev/null 2>&1 & \
kubectl port-forward service/mailhog 8025:8025 -n hyperswitch > /dev/null 2>&1 &

Access the services at:

Afterwards, you’ll be taken straight to the Control Center. If you're just taking things for a spin, feel free to skip authentication and start exploring right away.

Test a payment

Troubleshooting

  • View Pod Logs: To check logs for a specific pod in Google Kubernetes Engine (GKE):

kubectl logs <pod-name> -n hyperswitch
  • View Events: To list events in the namespace sorted by creation time:

kubectl get events -n hyperswitch --sort-by='.metadata.creationTimestamp'
  • Deploy Hyperswitch Helm Chart on GKE: If deploying for the first time or reinstalling, run:

helm uninstall hypers-v1 -n hyperswitch
helm install hypers-v1 hyperswitch/hyperswitch-stack -n hyperswitch

Customization & Configuration

To customize Hyperswitch, clone the Helm chart repository and modify values.yaml:

git clone https://github.com/juspay/hyperswitch-helm.git

Update the values.yaml file inside hyperswitch-stack/ and apply changes with:

helm upgrade --install hypers-v1 hyperswitch/hyperswitch-stack -n hyperswitch

Uninstall Hyperswitch & Delete GKE Cluster

  • To uninstall Hyperswitch:

helm uninstall hypers-v1 -n hyperswitch
  • To delete the GKE cluster completely:

gcloud container clusters delete <cluster-name> --region <region> --project <project-id> --quiet

Explore Further

Once you are done with the test payment, you can explore more about these:

The Google Cloud Command-Line Interface (CLI) is a cross-platform tool that allows you to manage GCP resources. To install gcloud, please refer to the official Google.

kubectl is the command-line tool for interacting with Kubernetes clusters. To install kubectl, please refer to the .

Helm is a package manager for Kubernetes applications. To install Helm, please refer to the .

App server:

Control center:

Hyperswitch Web:

Grafana:

Vector:

Mailhog:

The quickest way to explore Hyperswitch is via the . You can create an account or sign in with your email:

A magic link will be sent to . Click on the link in white:

Use can now use the Hyperswitch Control Center and .

Refer our to try out REST APIs.

Cloud SDK installation guide
Kubernetes documentation
official Helm documentation
http://localhost:8080
http://localhost:9000
http://localhost:9050/HyperLoader.js
http://localhost:3000
http://localhost:3103
http://localhost:8025
Control Center
Mailhog
make a payment with dummy card
postman collection

How to set up routing rules

How to integrate Hyperswitch with your app

List of supported payment processors and payment methods

AI Powered observability to reduce cost

Google Cloud Console