The OS for Modern Merchants
OrcoPay sits between your checkout and your payment providers - routing every transaction to the gateway most likely to approve it, retrying the ones that fail, and reconciling all of it in one ledger.
- Authorization received₹18,400 · card
- Risk checks passedvelocity, blocklist
- Routed to Gateway A98.2% success rate
- Declined - issuer timeoutattempt 1
- Retried on Gateway Battempt 2
- Authorized1.9s end to end
Connect the gateways you already use
Most teams lose sales to a single gateway.
Adding another PSP was supposed to raise approval rates. Instead it multiplied integrations, settlement files, and the time it takes to find out why a payment failed.
Approvals leak away
A 3–4% drop in authorization rate is often one gateway having a bad hour - but nobody can see which one until the month is already gone.
Every PSP is a new integration
A second gateway for redundancy becomes four APIs, four webhook shapes, and four dashboards your support team has to live in.
Settlement files don't match
Finance closes the month against six different report formats. Refunds and chargebacks never line up with the original payment.
One integration. Every payment rail.
Route, retry, and reconcile across every provider from a single API and a single ledger - without ripping out the gateways you already have.
Platform
Everything between checkout and settlement
Orchestration is more than a router. OrcoPay handles the whole lifecycle of a payment - and gives your operations team somewhere to actually work.
Smart routing
Route each authorization on success rate, cost, currency, or issuer - with rules you can read and change without a deploy.
Retries and failover
A soft decline on one gateway retries instantly on the next. Cascades are capped so you never double-charge a customer.
Unified reconciliation
Settlements, refunds, chargebacks and fees from every provider normalized into one ledger and one export.
Risk controls
Velocity limits, blocklists and per-merchant thresholds applied before an authorization ever reaches a gateway.
Analytics that explain
Conversion and performance broken down by gateway, method and issuer, so you can see which leg of the cascade is leaking.
One webhook contract
A single normalized event schema across every provider, with signed deliveries, retries and a full replay log.
- Platform uptime
- 99.99%Platform uptime
- Added routing latency
- <40msAdded routing latency
- Gateways supported
- 12+Gateways supported
- Continents covered
- 6Continents covered
How it works
Three steps to your first payment
We get the payment companies in place. You keep running your business.
- 01
Get your providers
Need one payment company or several? We help you sign up, finish the paperwork, and get approved - whether you are starting fresh or adding more.
- 02
Set how payments flow
Choose who should take a payment first. If one provider is down or says no, the next one tries - so fewer sales are lost.
- 03
Start taking payments
Connect your website or app once. After that, you can add or change providers without building everything again.
For developers
One API. Every provider behind it.
Create a payment and let OrcoPay pick the gateway. Add a provider next quarter and your integration doesn't change - the routing rules do.
- REST API with idempotency keys on every write
- Signed webhooks with replay and delivery logs
- Sandbox with simulated declines and failover paths
- Server SDKs for Node, Python, PHP and Go
curl https://api.orcopay.com/v1/payments \
-H "Authorization: Bearer $ORCOPAY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"amount": 1840000,
"currency": "INR",
"method": "card",
"routing": "smart",
"reference": "ord_9F42B7"
}'Ready to route your first payment?
Connect a gateway, define a rule, and go live. No replatforming, no rip-and-replace.
No setup fees · Sandbox access on signup