Payment orchestration without the platform lock-in.
GetPaidHQ sits between your application and your payment processors through a single adapter interface. Add the gateways you need and route every charge by region, by customer, or for failover — without re-architecting.
Free and open-source under AGPLv3 — self-host today, or talk to us about cloud.
Route every charge the way your business actually works.
Different regions, customers, and risk profiles call for different processors. Orchestrate them from one place.
- Per region
- Send each region’s charges to the acquirer with the best rates and acceptance there.
- Per customer
- Override routing for specific customers or segments without code changes.
- Failover
- Automatically retry on a backup processor when the primary declines or is down.
Bring your own gateway.
A clean adapter interface abstracts every processor behind one API. Checkout.com and Paystack are supported today, and any processor can be added by implementing the adapter interface — including your own in-house PSP.
Built for money-movement.
- Idempotency keys
- Safely retry requests without double-charging customers.
- Smart retries
- Configurable retry logic across processors recovers transient failures.
- Webhooks
- Signed, retried event delivery keeps your systems in sync.
Orchestration in three steps.
- 01
Add your processors
Configure Checkout.com, Paystack, or your own adapter.
- 02
Define routing
Set rules by region, customer, or failover priority.
- 03
Charge through GetPaidHQ
One API call; GetPaidHQ routes, retries, and reconciles.
What is payment orchestration?
Payment orchestration is a layer that connects a business to multiple payment processors and routes each transaction to the best one — handling retries, failover, and reconciliation through a single integration. GetPaidHQ adds full subscription billing on top, and unlike hosted orchestrators it’s open-source and self-hostable, so you own the routing logic and the data.
Questions, answered.
- Which processors are supported?
- Checkout.com and Paystack today, plus any processor you implement against the adapter interface.
- Do I have to change my application code to switch processors?
- No — routing is configured in GetPaidHQ, so you can change or add processors without touching your app.
- Is the orchestration layer self-hostable?
- Yes. GetPaidHQ is AGPLv3 open-source and runs on your own infrastructure, so routing logic and payment data stay in your perimeter.
Orchestrate payments on infrastructure you own.
Self-host GetPaidHQ for free today, or talk to us about managed Cloud.
Free and open-source under AGPLv3 — self-host today, or talk to us about cloud.