Deploy and Host self hosted Hyperswitch Adyen (Open-Source Payment Switch for Adyen) on Railway

This template runs a self-hosted Hyperswitch router and Control Center on Postgres and Redis, so you can send card payments to Adyen through an API you control.

About Hosting Hyperswitch Adyen open-source software on Railway (self hosted Hyperswitch with the Adyen connector template)

Hyperswitch is an Apache-2.0 payment switch written in Rust, and this template runs it in your own Railway project so your data and routing logic stay with you.

Railway runs the containers and handles TLS. Check your PCI DSS scope before taking live cards.

Why Deploy Hyperswitch Adyen, the Adyen direct integration alternative on Railway (Railway Free Trial)

Going direct to Adyen ties checkout, webhooks and refunds to one processor's API, so adding another later means a rewrite.

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Hyperswitch Adyen on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.

Railway vs Other Hosting Providers and VPS for Hyperswitch Adyen self hosting

Railway wires the four Hyperswitch services together from one template, while a VPS leaves setup and upkeep to you.

Provider	What You Get with Railway	What You Get with the Other Provider
DigitalOcean	One template deploy with the router on port 8080 and the control center on port 9000, with Postgres and Redis wired in.	A Droplet you size and secure yourself, with Docker Compose from the Hyperswitch repo.
AWS	No VPC, load balancer or IAM setup, with public domains handled for you.	Fine-grained networking and compliance tooling, with a steeper setup for a small stack.
Hetzner	Managed services and domains without patching the OS or tuning Postgres.	Low-cost servers that run the full stack cheaply, if you manage updates and backups.

Either way, back up MASTER_ENC_KEY, because losing it makes stored data unreadable.

Common Use Cases for hosted Hyperswitch Adyen

Adyen behind a processor-neutral API: Your checkout calls the Hyperswitch router instead of Adyen directly, so Adyen-specific code lives in one connector config.
Adding a backup processor for failover: After Adyen is connected, add a second processor later and use routing rules to send traffic there or fail over on declines or timeouts.
Local payment methods through Adyen: Enable methods like Klarna in Adyen's dashboard first, then select the matching methods in the Hyperswitch connector.
One webhook format for your app: Hyperswitch translates Adyen's notifications into a single webhook shape, which keeps your order logic simple.
Testing in Adyen test mode before going live: Run payments, refunds, and webhooks end to end with test credentials, then swap in live keys.

Dependencies for Hyperswitch Adyen Docker hosted on Railway

You need an Adyen account, a working Hyperswitch Control Center, and Postgres and Redis for state.

Deployment Dependencies for Managed Hyperswitch Adyen Service (Payment Orchestration)

The stack has four services. Postgres 18 and Redis 8.2 complete the stack. Expect roughly $15-30 per month on Railway at light traffic.

Implementation Details for Hyperswitch Adyen (Using Hyperswitch official docker image)

ROUTER__SECRETS__ADMIN_API_KEY is for admin endpoints only, so keep it server side. JWT_SECRET is generated at 48 characters.

How does Hyperswitch Adyen compare against other ways to integrate Adyen

Hyperswitch vs Adyen direct integration (Adyen Direct Alternative)

Abstraction layer: Your app talks to one Hyperswitch API, and Adyen sits behind it as a connector. Adding a processor later means adding a connector, not rewriting checkout.
Feature access: Going direct gives you Adyen's full feature set and SDKs with no translation layer. Newer Adyen-specific options may reach Hyperswitch later.
Operational load: Direct integration is simpler to run. Here you own the switch, its database, and its uptime.

Hyperswitch vs Stripe (Stripe Alternative)

Ownership: Stripe is a hosted processor with its own API. Hyperswitch is Apache-2.0 software you run yourself.
Processor choice: Stripe settles through Stripe. Hyperswitch routes across Adyen, Stripe, and many other processors from one API.
Convenience: Stripe wins on setup speed, documentation, and built-in products like Radar and Billing.

Hyperswitch vs Spreedly (Spreedly Alternative)

Deployment: Spreedly is commercial SaaS for orchestration and vaulting. Hyperswitch runs on your infrastructure, so card data stays in your environment.
Maturity: Spreedly has a longer track record and a larger support team. Hyperswitch is newer and moves fast.
Control: Hyperswitch gives you direct access to routing rules, retries, and connector config, in exchange for running it yourself.

Hyperswitch vs Primer (Primer Alternative)

Workflows: Primer offers no-code workflow building. Hyperswitch is configured through its Control Center and API.
Hosting: Primer is hosted. You back up Hyperswitch's Postgres and Redis services and its MASTER_ENC_KEY yourself.
Where Primer wins: If your team wants a managed, low-code payments front end and no infrastructure, Primer is the easier path.

How to use Hyperswitch Adyen (the OSS payment switch)?

Log into the Control Center on your Railway control-center domain and create a merchant and profile.
Open Connectors and choose Adyen.
In Adyen, go to Developers, then API credentials. Paste the API key and merchant account ID into the connector form.
Pick the payment methods enabled in your Adyen account.
Save in test mode first.
In Adyen, go to Developers, then Webhooks, and create a standard webhook pointing at the Hyperswitch webhook URL shown for the connector.
Create a test payment with your Hyperswitch API key:

curl -X POST https://YOUR_ROUTER_DOMAIN/payments \
  -H "api-key: YOUR_HYPERSWITCH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"amount": 1000, "currency": "USD", "confirm": true, "payment_method": "card", "payment_method_data": {"card": {"card_number": "4111111111111111", "card_exp_month": "03", "card_exp_year": "30", "card_holder_name": "Test User", "card_cvc": "737"}}}'

If the payment succeeds and the event shows up in Adyen's webhook log, your first-day setup works.

How to self host Hyperswitch Adyen on other VPS Services (Hyperswitch self hosting guide)

Running this stack on a VPS mirrors what the Railway template does for you.

Clone the Repository

Pull the official Hyperswitch source for the compose file and setup helper.

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

Install Dependencies

Make sure Docker, Docker Compose, and git are installed. The repo's setup script checks for them and prepares the environment.

./scripts/setup.sh

Configure Environment Variables

Set the admin API key, JWT secret, and the three 64-character hex keys (MASTER_ENC_KEY, HASH_KEY, ENCRYPTION_KEY).

Start the Hyperswitch Adyen Application

Bring up the stack, then open the control center at your-domain:9000 and add Adyen under Connectors using the API key and merchant account ID from Adyen Developers, API credentials.

docker compose up -d
curl https://your-domain:8080/health

Railway handles Postgres, Redis, TLS, and service networking for you, which you'd otherwise wire up yourself on a VPS.

Official Pricing of Hyperswitch Adyen (Hyperswitch pricing)

Hyperswitch is open source under Apache-2.0, so the software itself is free to self host. You pay only for the infrastructure it runs on, which on Railway is usage-based.

Adyen charges its own processing fees on every transaction, and those stay the same whether you call Adyen directly or through this switch.

Hyperswitch Adyen cloud vs self hosted comparison (Pricing, features, costs, and more)

Self hosting Hyperswitch is free software-wise, while a managed service bills you for the platform.

Monthly cost of self hosting Hyperswitch Adyen on Railway

On Railway, the router, control center, Postgres 18, and Redis 8.2 typically run about $15-30 per month at light use. Railway's $5 trial covers early testing.

System Requirements for Hosting Hyperswitch Adyen on a VPS

On a VPS, plan for Docker and Docker Compose, enough RAM for the Rust router plus Postgres and Redis, and a public domain with TLS in front of ports 8080 and 9000.

Frequently Asked Questions (FAQs)

Do I need PCI scope if I run Hyperswitch with Adyen?

Probably, at least in part. Handling raw card data puts PCI DSS obligations on whoever runs the switch, so check your scope before taking live cards.

How do I get raw card data permission from Adyen?

Email support@adyen.com and ask them to enable raw card data handling for your account, since Hyperswitch needs it to pass card details server side.

Which payment methods work through this setup?

Only the methods you enable in Adyen under Settings, Payment methods, so match them in the Control Center.

How do I set up the Adyen webhook?

In Adyen, go to Developers, Webhooks, and create a standard webhook pointing at the Hyperswitch webhook URL shown for your connector.

Should I test in Adyen test mode before going live?

Yes. Save the connector with your test credentials, run a few payments end to end, and switch to live credentials only once webhooks and payment states look right.

Can I route between Adyen and another processor?

Yes.