Why OmiCloud
Five things we'd put in the contract.
Most payment pitches lead with numbers you can't verify. This page leads with commitments you can: what OmiCloud is allowed to do, what it will never do, and why each one is locked into the architecture instead of written into a policy.
We never touch the money.
OmiCloud is a routing layer between your platform and your gateways. Funds settle gateway-to-you; there is no OmiCloud balance in the middle. That's not a compliance posture we maintain. It's a capability we deliberately don't have. A platform that can't hold your funds can't freeze them, pool them, or lose them.
Our margin never routes.
When routing picks a gateway, it scores exactly two things: the fee you pay and the rolling approval rate. What OmiCloud earns on each path is excluded from the formula on purpose. An orchestrator that routes toward its own margin is quietly working against you on every transaction, so we made that mathematically impossible, and we say so in writing.
The routing stays transparent.
You see every route available to you, always. If a route isn't available, it appears locked with the reason (region, currency, or a compliance gap) instead of silently disappearing. The gateway behind each route stays masked; the reason a route is or isn't available never does. Curated shortlists are how platforms steer you toward their best deal. An honest view of what's available, and why, is how you find yours.
Failure is part of the design.
Gateways go down at the worst possible hour, webhooks arrive twice, requests time out mid-flight. None of that is an edge case. It's the operating environment. Cascading retries, health checks that route around degraded gateways, idempotent submissions and verified signatures exist because we assume failure, not because we were surprised by it.
History doesn't get rewritten.
Every state a transaction passes through lands in an append-only event history. Invalid transitions are rejected loudly, never patched over: a record can't quietly skip from declined to settled. When you and a gateway disagree about a payment, the ledger is the referee, and it works for you.
What you won’t find on this site.
A payments company that will shade the truth on its own website will shade it in your settlement report. So we hold the marketing to the same rule as the ledger: if a claim can’t be backed, it doesn’t ship.
- A “99.99% uptime” badge no one audited
- Fabricated volume counters ticking upward
- Logos of companies we don't actually serve
- “Live in 190+ countries” with an asterisk
- Design guarantees you can verify in the docs
- Plain answers about what isn't built yet
One direct PSP
- Their bad night is your outage
- Approval rate is whatever they give you
- Funds often pooled in their balance
- Leaving means re-integrating from zero
DIY multi-gateway
- One integration per gateway, forever
- You build routing, retries and dedupe
- You reconcile every disagreement
- Engineering time that isn't your product
With OmiCloud
- One contract, every gateway behind it
- Approval-scored routing with cascade
- No custody anywhere in the middle
- The ledger referees every dispute
Hold us to all five.
Bring this page to the demo and make us defend every line of it against your traffic.