Skip to content

Latest commit

 

History

History
1842 lines (1784 loc) · 101 KB

README.md

File metadata and controls

1842 lines (1784 loc) · 101 KB

Hyperswitch-Logo Hyperswitch-Logo

The open-source payments switch

The single API to access payment ecosystems across 130+ countries

💳 Try a Payment • Setup in k8s • API Docs
Community and Contributions • Copyright and License

Hyperswitch is a community-led, open payments switch designed to empower digital businesses by providing fast, reliable, and affordable access to the best payments infrastructure.

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

Jump in and contribute to these repositories to help improve and expand Hyperswitch!

💳 Try a Payment

To quickly experience the ease of Hyperswitch, sign up on the Hyperswitch Control Center and try a payment. Once you've completed your first transaction, you’ve successfully made your first payment with Hyperswitch!

⚡️ Quick Setup

Deploy on Kubernetes using Helm

This section outlines cloud-provider agnostic deployment steps for easy installation of the Hyperswitch stack on your K8s cluster

Installation

Step 1 - Clone repo and Update Configurations

Clone the hyperswitch-stack repo and start updating the configs

helm repo add hyperswitch https://juspay.github.io/hyperswitch-helm
helm repo update

Step 2 - Install Hyperswitch

Before installing the service make sure you labels your kubernetes nodes and create a namespace hyperswitch Note: minimum --memory 6000 --cpus 4 needed

kubectl create namespace hyperswitch

Use below command to install hyperswitch services with above configs

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

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

Post-Deployment Checklist

After deploying the Helm chart, you should verify that everything is working correctly

App Server

  • Check that hyperswitch_server/health returns health is good

Control Center

💳 Test a payment

Hyperswitch Control center will mimic the behavior of your checkout page. Please follow below steps to test a payment with the deployed app

🔐 Step 1 - Deploy card vault

By default card vault and its dependencies are installed, however you need to create master key, custodian keys and unlock the locker to start saving cards.

Step 1: Generating the keys

To generate the master key and the custodian keys use the following command after cloning the repository. 

# Generate master key
git clone https://github.com/juspay/hyperswitch-card-vault.git
cd hyperswitch-card-vault
cargo run --bin utils -- master-key
To generate the JWE and JWS keys run the following commands

# Generating the private keys
openssl genrsa -out locker-private-key.pem 2048
openssl genrsa -out tenant-private-key.pem 2048

# Generating the public keys
openssl rsa -in locker-private-key.pem -pubout -out locker-public-key.pem
openssl rsa -in tenant-private-key.pem -pubout -out tenant-public-key.pem

Step 2: Update the keys in deployment 

# Update below values in hyperswitch-stack/values.yaml
# The public key for the locker from locker-public-key.pem
hyperswitch-app.server.secrets.kms_jwekey_vault_encryption_key: |
  -----BEGIN PUBLIC KEY-----
  ...
  -----END PUBLIC KEY-----
# The private key for the tenant from tenant-private-key.pem
hyperswitch-app.server.secrets.kms_jwekey_vault_private_key: |
  -----BEGIN RSA PRIVATE KEY-----
  ...
  -----END RSA PRIVATE KEY-----
# The private key for the locker from locker-private-key.pem
hyperswitch-card-vault.server.secrets.locker_private_key: |
  -----BEGIN RSA PRIVATE KEY-----
  ...
  -----END RSA PRIVATE KEY-----
# The public key for the tenant from tenant-public-key.pem
hyperswitch-card-vault.server.secrets.tenant_public_key: |
  -----BEGIN PUBLIC KEY-----
  ...
  -----END PUBLIC KEY-----

Step 3: Unlock the locker

Once the locker is up and running, use the 2 key custodian keys generated earlier securely to unlock the locker for use. Go to the respective locker Pod, open its shell and run below cURLs

The following cURLs are to be used to provide keys

# temporary turn of saving to history to run the following commands
unset HISTFILE

# Add key1, key2 and then decrypt
curl -X POST -H "Content-Type: application/json" -d '{"key": "<key 1>"}' http://localhost:8080/custodian/key1
curl -X POST -H "Content-Type: application/json" -d '{"key": "<key 2>"}' http://localhost:8080/custodian/key2
curl -X POST http://localhost:8080/custodian/decrypt

If the last cURL replies with Decrypted Successfully, we are ready to use the locker.

Step 2 - Make a payment using our Control Center

Use the Hyperswitch Control Center and make a payment with test card.

Refer our postman collection to try out REST APIs

✅ Community & Contributions

The community and core team are available in GitHub Discussions, where you can ask for support, discuss roadmap, and share ideas.

Join our Conversation in Slack, Discord, Twitter

When you want others to use the changes you have added you need to package it and then index it

# To package and index the new changes
task pihh
# To update readme file
task ur

Requirements

Repository Name Version
file://../hyperswitch-app hyperswitch-app 0.2.1
file://../hyperswitch-web hyperswitch-web 0.2.1

Values

Dependencies configuration

Key Default Description
""
 Clickhouse password
"default"
 Clickhouse username
"Asia/Kolkata"
 Clickhouse timezone
true
 Enable Bitnami Clickhouse sub-chart helm installation
"clickhouse"
 Name of the Clickhouse sub-chart
"error"
 Clickhouse log level
1
 Clickhouse replica count
1
 Clickhouse shard count
1
 Zookerper replica count
false
 Link this service to an external Postgres server
"hyperswitch"
 master DB name
"hyperswitch"
 master DB password
null
 master DB plainpassword
"hyperswitch"
 master DB username
"postgresql-ext"
 External postgres host
"hyperswitch"
 replica DB name
"hyperswitch"
 replica DB password
null
 replica DB plainpassword
"hyperswitch"
 replica DB username
false
 External postgres read only host enabled or disabled
"postgres-service"
 External postgres read only host
true
 auth enabled or disabled
""
 redis password
""
 redis username
false
 Link this service to an external Redis server
"redis-ext-master"
 External redis host
1
 Number of replicas to be used for broker
1
 Number of replicas to be used for controller
true
 Enable Bitnami Kafka sub-chart helm installation
"kafka0"
 Name of the Kafka sub-chart
"PLAINTEXT"
 Listener client protocol
"PLAINTEXT"
 Listener controller protocol
"PLAINTEXT"
 Listener external protocol
"PLAINTEXT"
 Listener interbroker protocol
1
 kafka provisioning replicationFactor
29092
 Client port for Kafka
1
 Number of replicas to be used for zookeeper
"admin"
 Name of the Grafana sub-chart
true
 Enable Bitnami Grafana sub-chart helm installation
"10.0.1"
 Grafana image tag
true
 Enable Bitnami Loki sub-chart helm installation
"loki"
 Name of the Loki sub-chart
true
 Enable Bitnami Promtail sub-chart helm installation
true
 Enable Bitnami Mailhog sub-chart helm installation for email testing
"mailhog"
 Name of the Mailhog sub-chart
"replication"
 Postgresql architecture: replication or standalone
true
 enable Bitnami postgresql sub-chart helm installation
"hyperswitch"
 Postgresql database
"ZGJwYXNzd29yZDEx"
 Postgresql password
"hyperswitch"
 Postgresql username
""
 postgres primary name
"150m"
 CPU resource requests
0
 Number of read replicas
"100m"
 CPU resource requests
1
 Number of synchronous replicas
"off"
 synchronous_commit parameter
false
 enable or disable redis auth
false
 enable or disable sentinel
true
 - enable Bitnami redis sub-chart helm installation
1
 Number of replicas to be used for master
0
 Number of replicas to be used for replica
true
 Enable Bitnami Vector sub-chart helm installation
{ "name": "KAFKA_HOST", "value": "kafka0:29092" }
 Vector environment variables

Control Center configs

Key Default Description
"https://app.hyperswitch.io/agreement/tc-hyperswitch-aug-23.pdf"
 Hyperswitch terms and conditions url
"1.0.0"
 Agreement version
"https://app.hyperswitch.io/certificates/PCI_DSS_v4-0_AOC_Juspay_2024.pdf"
 PCI DSS certificate url
""
 Endpoints favicon url
""
 Endpoints logo url
"dd4da7f62941557e716fbc0a19f9cc7e"
 Mixpanel token
"false"
 Enables customization of branding elements like logos, colors.
"false"
 Enables user sign-in and sign-up using magic links instead of passwords. When enabled, users can request a magic link via email that logs them into their account or creates a new account if they are signing up.
"false"
 Enables the ability for users to provide direct product feedback from within the dashboard. When enabled, a feedback modal will be available in the UI that allows users to rate features, report bugs, and suggest improvements. Disabling this flag will remove the feedback modal and prevent collection of any user data.
"false"
 Enables the Fraud and Risk Management (FRM) module within the dashboard. When enabled, this unlocks integrations with FRM players like Riskified and Signified. https://docs.hyperswitch.io/explore-hyperswitch/payment-flows-and-management/fraud-and-risk-management
"false"
 Controls the ability to generate detailed reports on payments, refunds, and disputes. When enabled, this allows users to pull reports covering the previous 6 months of transaction data. The reports can provide insights into trends, identify issues, and inform business decisions.
"false"
 Enables the live mode - that the user is accessing. When enabled, it will show a visual indicator within the dashboard signaling whether the user is currently in a test environment or live production environment. In Live mode, current users are not allowed to sign up. Users must be created manually.
"false"
 Controls the collection and transmission of anonymous usage data to Mixpanel for analytics. When enabled, the dashboard will automatically send information about user actions and events to Mixpanel without collecting any personally identifiable information via REST API.
"false"
 Enables the payout functionality in the dashboard. When enabled, this allows users to configure payout profiles, manage recipient details, schedule disbursements, and process payout batches to pay out funds to third parties.
"false"
 Enables the simplified onboarding flow for new users, where they connect to processors, configure payment routing and test a payment, all in one flow.
"false"
 Enables access to reconciliation capabilities in the Hyperswitch dashboard. When turned on, this unlocks the Reconciliation module that allows users to match payment transactions with bank/ledger entries for accounting purposes.
"false"
 Enables the ability to load simulated sample data into the dashboard for preview purposes. When enabled, dummy transactions, analytics, and reporting data can be generated.
"false"
 Enables the ability to apply surcharges to payments. When enabled, you can create advanced rules based on payment parameters like amount, currency, and payment method to enforce surcharges as needed.
"false"
 Unlocks access to system monitoring and metrics pages within the dashboard. When enabled, users can view technical performance data like payment latency, uptime, API response times, error rates, and more.
"false"
 Enables users to toggle between test and live modes when signing in. When enabled, users will see an option during sign-in to actively switch between test and live environments.
"false"
 Allows enabling sandbox/test payment processors for testing purposes. When enabled, developers and testers can add test payment processors like Stripe Test or PayPal Test to trial payment flows without touching live transactions or making processor API calls.
"false"
 Enables totp will mandate 2fa for all users
"false"
 Grants access to the user journey module within the analytics section of the dashboard. This feature provides comprehensive graphical representations of payment analytics, facilitating a deeper understanding of user behavior and usage patterns.
"#006DF9"
 Primary color for the theme
"#005ED6"
 Primary hover color for the theme
"#242F48"
 Secondary color for the theme
"dd4da7f62941557e716fbc0a19f9cc7e"
 Mix panel token

App Server Secrets

Key Default Description
"default"
 Clickhouse database name
"http://clickhouse:8123"
 Clickhouse host in http(s)://: format
""
 Clickhouse password (optional)
"default"
 Clickhouse username
"us-east-1"
 AWS region used by AWS SES
"arn:aws:iam::123456789012:role/SendEmailRole"
 The amazon resource name ( arn ) of the role which has permission to send emails
"SendEmailRole"
 An identifier for the assumed role session, used to uniquely identify a session.
Recipient email for prod intent email
Recipient email for recon request email
Sender email
"mailhog"
 Host of the smtp server
""
 Password for the smtp server
"PAZE_PRIVATE_KEY"
 Base 64 Encoded Private Key File cakey.pem generated for Paze -> Command to create private key: openssl req -newkey rsa:2048 -x509 -keyout cakey.pem -out cacert.pem -days 365
"PAZE_PRIVATE_KEY_PASSPHRASE"
 PEM Passphrase used for generating Private Key File cakey.pem
"test_admin"
 admin API key for admin authentication.
"0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef"
 API key hashing key.
"dummy_val"
 Merchant Certificate provided by Apple Pay (https://developer.apple.com/) Certificates, Identifiers & Profiles > Apple Pay Merchant Identity Certificate
"dummy_val"
 Private key generated by RSA:2048 algorithm. Refer Hyperswitch Docs (https://docs.hyperswitch.io/hyperswitch-cloud/payment-methods-setup/wallets/apple-pay/ios-application/) to generate the private key
"dummy_val"
 Merchant Certificate provided by Apple Pay (https://developer.apple.com/) Certificates, Identifiers & Profiles > Apple Pay Merchant Identity Certificate
"dummy_val"
 Private key generate by RSA:2048 algorithm. Refer Hyperswitch Docs (https://docs.hyperswitch.io/hyperswitch-cloud/payment-methods-setup/wallets/apple-pay/ios-application/) to generate the private key
"dummy_val"
 Refer to config.example.toml to learn how you can generate this value
"dummy_val"
 Payment Processing Certificate provided by Apple Pay (https://developer.apple.com/) Certificates, Identifiers & Profiles > Apple Pay Payment Processing Certificate
"dummy_val"
 Private key generated by Elliptic-curve prime256v1 curve. You can use `openssl ecparam -out private.key -name prime256v1 -genkey` to generate the private key
"dummy_val"
 Api key for making request to foreign exchange Api, Follow https://github.com/juspay/hyperswitch/tree/main/crates/analytics#setting-up-forex-apis to get the forex api key
"dummy_val"
 Forex Api key for the fallback service
"test_admin"
 JWT secret used for user authentication.
"-----BEGIN PUBLIC KEY-----...-----END PUBLIC KEY-----"
 The public key for the locker from locker-public-key.pub, these are only test keys, please change it when deploying to production or other environments
"-----BEGIN RSA PRIVATE KEY-----...-----END RSA PRIVATE KEY-----"
 The private key for the tenant from tenant-private-key.pem, these are only test keys, please change it when deploying to production or other environments
"kms_key_id"
 KMS key id for encryption and decryption
"us-east-1"
 AWS KMS region
"471f22516724347bcca9c20c5fa88d9821c4604e63a6aceffd24605809c9237c"
 Master Encryption key used to encrypt merchant wise encryption key. Should be 32-byte long.
"dummy_val"
 # Payment method auth key used for authorization
"test_admin"
 Recon Admin API key for recon admin authentication.
"dummy_val"
 Encryption key for redis temp locker
"dummy_val"
 Encryption key used for encrypting data in user_authentication_methods table

Services

Key Default Description
"juspaydotin/hyperswitch-consumer:v1.112.0"
 Consumer image
"juspaydotin/hyperswitch-control-center:v1.34.2"
 Control Center image
"juspaydotin/hyperswitch-producer:v1.112.0"
 Producer image
"http://localhost:8080"
 Router host
"juspaydotin/hyperswitch-router:v1.112.0"
 Router image
"v1.112.0"
 Router version
"http://localhost:9050"
 SDK host
"v0"
 SDK subversion
"0.103.1"
 SDK version

Other Values

Key Default Description
{}
{}
[]
true
10
1
80
24.3
"none"
"dashboard"
"false"
"false"
"false"
"false"
"false"
"false"
"false"
"false"
"false"
"false"
"false"
"false"
"hyperswitch-control-center"
1
 Number of replicas to be used for the application
true
"docker.io/bitnami/postgresql:16.1.0-debian-11-r18"
"docker.io/bitnami/postgresql:16.1.0-debian-11-r18"
60
true
"christophwurst/diesel-cli:latest"
"tags"
"none"
"none"
"offsets.topic.replication.factor=1\ntransaction.state.log.replication.factor=1\n"
"loadBalancer-sg"
"16.1.0-debian-11-r18"
"7.2.3-debian-11-r2"
true
"docker.io/bitnami/redis:7.2.3-debian-11-r2"
60
"clickhouse"
 The Analytics source/strategy to be used
10
 Timeout for database connection in seconds
5
 Number of connections to keep open
"Fifo"
 Add the queue strategy used by the database bb8 client
{ "deployment.kubernetes.io/revision": "1" }
 Annotations that are to be added the the deployments (extends global configuration)
"https://apple-pay-gateway.apple.com/paymentservices/registerMerchant"
 Apple pay gateway merchant endpoint
"12345"
 Default CellID for Global Cell Information
true
"['merchant_id_1','merchant_id_2']"
 List of merchant ids for which the payment id should be sent as connector request id
"GET,POST,PUT,DELETE"
 List of methods that are allowed
30
 Maximum time (in seconds) for which this CORS request may be cached.
true
 If true, allows any origin to make requests
"SES"
 The currently active email client
1
 Number of days the api calls ( with jwt token ) can be made without verifying the email
"plaintext"
 connection type to be used for the smtp server
"1025"
 Port of the smtp server
10
 timeout for the smtp server connection
""
 Username for the smtp server
"no_encryption"
 Encryption manager client to be used
"hyperswitch-api-log-events"
 Kafka topic to be used for incoming api events
"hyperswitch-payment-attempt-events"
 Kafka topic to be used for PaymentAttempt events
"hyperswitch-audit-events"
 Kafka topic to be used for Payment Audit events
"hyperswitch-authentication-events"
 Kafka topic to be used for Authentication events
"['kafka0:29092']"
"hyperswitch-outgoing-connector-events"
 Kafka topic to be used for connector api events
"hyperswitch-consolidated-events"
 Kafka topic to be used for Consolidated events
"hyperswitch-dispute-events"
 Kafka topic to be used for Dispute events
"hyperswitch-fraud-check-events"
 Kafka topic to be used for Fraud Check events
"hyperswitch-payment-intent-events"
 Kafka topic to be used for PaymentIntent events
"hyperswitch-outgoing-webhook-events"
 Kafka topic to be used for outgoing webhook events
"hyperswitch-payout-events"
 Kafka topic to be used for Payouts and PayoutAttempt events
"hyperswitch-refund-events"
 Kafka topic to be used for Refund events
"kafka"
 The event sink to push events supports kafka or logs (stdout)
20001
 Api timeouts once it crosses 20000 ms
21601
 Api calls are made after every 6 hrs
5
 Fetch from Local cache has retry count as 5
1010
 Retry delay for checking write condition
260001
 Redis remains write locked for 26000 ms once the acquire_redis_lock is called
"ach,bacs,sepa"
"credit,debit"
"paypal,pix,venmo"
"https://app.hyperswitch.io/HyperswitchFavicon.png"
"HyperSwitch"
"#4285F4"
"credit,debit"
"https://app.hyperswitch.io/HyperswitchFavicon.png"
"HyperSwitch"
"#4285F4"
"localhost"
 Client Host
7000
 Client Port
"dynamo"
 Client Service Name
{ "app": "hyperswitch-server" }
 Labels to be added to the deployment's (match labels) and their pods (extends global configuration)
500
 Delay between retries in milliseconds
180
 Seconds before the redis lock expires
"http://hyperswitch-vault"
 Locker host
null
 Rust Locker host
true
 Boolean to enable or disable saving cards in locker
"1"
 Key_id to sign basilisk hs locker
false
 Emulate a locker locally using Postgres
220752000
 Time to live for storage entries in locker
true
"DEBUG"
 Log level for console logs, ERROR, WARN, INFO, DEBUG
"json"
false
"DEBUG"
"json"
15
 Interval for collecting the metrics in background thread
false
 boolean [true or false], whether to ignore errors during traces or metrics pipeline setup
false
 boolean [true or false], whether metrics are enabled
"http://localhost:4317"
 endpoint to send metrics and traces to, can include port number
5000
 timeout (in milliseconds) for sending metrics and traces
"['*/confirm']"
0.1
false
 boolean [true or false], whether traces are enabled
false
 Set this to true for AWS X-ray compatible traces
10
 Timeout for database connection in seconds
"20"
 Number of connections to keep open
"Fifo"
 Add the queue strategy used by the database bb8 client
false
"default"
""
"public"
"http://localhost:8080"
"default"
""
"public"
"basic"
"admin"
"eu-central-1"
"admin"
"https://localhost:9200"
"hyperswitch-dispute-events"
"hyperswitch-payment-attempt-events"
"hyperswitch-payment-intent-events"
"hyperswitch-refund-events"
"sessionizer-dispute-events"
"sessionizer-payment-attempt-events"
"sessionizer-payment-intent-events"
"sessionizer-refund-events"
900
 Redis expiry time in milliseconds
{ "traffic_sidecar_istio_io_excludeOutboundIPRanges": "10.23.6.12/32" }
 Annotations that are to be added to the pods (extends global configuration)
600
[]
 A list of URLs that should bypass the proxy
false
"http://proxy_http_url"
 Outgoing proxy http URL to proxy the HTTP traffic
"https://proxy_https_url"
 Outgoing proxy https URL to proxy the HTTPS traffic
true
 Whether or not the client should automatically pipeline commands across tasks when possible.
false
 boolean
"['redis.cluster.uri-1:8080', 'redis.cluster.uri-2:4115']"
 List of redis cluster urls
30
 An optional timeout to apply to all commands. In seconds
900
 Default TTL for hashes entries, in seconds
300
 Default TTL for entries, in seconds
false
 Whether or not to disable the automatic backpressure features when pipelining is enabled.
"127.0.0.1"
200
 The maximum number of frames that will be fed to a socket before flushing.
5000
 The maximum number of in-flight commands (per connection) before backpressure will be applied.
5
 Number of connections to keep open
6379
5
 Delay between reconnection attempts, in milliseconds
5
 Maximum number of reconnection attempts to make before failing. Set to 0 to retry forever.
1
 Default number of entries to read from stream if not provided in stream read options
10
 An optional timeout for Unresponsive commands in seconds. This should be less than default_command_timeout.
false
 RESP protocol for fred crate (set this to true if using RESPv2 or redis version < 6)
10
 Timeout for database connection in seconds
"20"
 Number of connections to keep open
"Fifo"
 Add the queue strategy used by the database bb8 client
1
 Number of replicas to be used for the application
"report_download_config_dispute_function"
 Config to download dispute report
"report_download_config_payment_function"
 Config to download payment report
"report_download_config_refund_function"
 Config to download refund report
"report_download_config_region"
 Region of the bucket
"sandbox"
 Processor URLs will be decided based on this config, Eg: sandbox or production
"dummy_val"
"dummy_val"
"dummy_val"
"dummy_val"
"dummy_val"
"vault_token"
"http://vault:8200"
"no_encryption"
 Secrets manager client to be used
"0.0.0.0"
8080
32768
 HTTP Request body limit. Defaults to 32kB
30
 For more details: https://actix.rs/docs/server/#graceful-shutdown
8
{ "eks.amazonaws.com/role-arn": "my-role-arn" }
 service account annotations to be used
1
0
"RollingUpdate"
30
 The time kubernetes will wait after sending the termination signal to the pods
"http://localhost:9000"
false
false
"90"
"Hyperswitch Sandbox"
"300"
null
null
null
null
null
false
"postgres:16-alpine3.19"
30
true
"christophwurst/diesel-cli:latest"
true
"standalone"
"locker-db"
"V2tkS1ptTkhSbnBqZDI4OUNnPT0K"
"db_user"
"locker-db"
""
"100m"
[]
{}
{}
{}
"juspaydotin/hyperswitch-card-vault:v0.4.0"
{}
"-----BEGIN RSA PRIVATE KEY-----...-----END RSA PRIVATE KEY-----"
 To create this key pairs, follow the instructions provided here:
# Generating the private keys 
openssl genrsa -out locker-private-key.pem 2048
openssl genrsa -out tenant-private-key.pem 2048
# Generating the public keys 
openssl rsa -in locker-private-key.pem -pubout -out locker-public-key.pem
openssl rsa -in tenant-private-key.pem -pubout -out tenant-public-key.pem
The private key for the locker from locker-private-key.pem
"master_key"
 Optionally, you can run 
cargo install --git https://github.com/juspay/hyperswitch-card-vault --root . && ./bin/utils master-key && rm ./bin/utils && rmdir ./bin
"-----BEGIN PUBLIC KEY-----...-----END PUBLIC KEY-----"
 The public key for the tenant from tenant-public-key.pem
"juspaydotin/hyperswitch-web"
 docker image to use for the build
"https://hyperswitch"
 node build parameter, hyperswitch server host
"https://hyperswitch-sdk-logs"
 node build parameter, hyperswitch SDK logs host
"https://hyperswitch-sdk"
 node build parameter, hyperswitch-web sdk host (same as ingress host)
true
 enable npm auto build
false
 force rebuild assets even these files exist
"https://github.com/juspay/hyperswitch-web"
 hyperswitch-web repository
"0.71.11"
 hyperswitch-web repository tag
"v0"
 nginx static server extra path ( like https:///0.15.8/v0 )
"nginx"
 nginx static server image
"1.25.3"
 nginx static server tag
"hyperswitch-web-nginx"
"v0"
 nginx extra path used to set liveness and readiness probe /0.80.0/v0
"IfNotPresent"
 prebuild image pull policy
"nginx"
 prebuild SDK image
"0.35.4"
 prebuild image tag, the image tag whose default is the chart appVersion.
{}
 ingress annotations
"nginx"
 ingress class name
true
 enable/disable ingress
[ { "host": "chart-example.local", "paths": [ { "path": "/", "pathType": "ImplementationSpecific" } ] } ]
 ingress hosts list
[]
 tls configurations list
{}
 pod annotations
{}
 pod labels
{}
 pod security context
1
 deployment/statefulset replicas
{}
 security context
9050
 service port
"ClusterIP"
 service type
"http://localhost:8080"
"pub_key"
"secret_key"
"juspaydotin/hyperswitch-web:v1.0.10"