One integration, then your team runs providers, routing rules and the checkout from one dashboard. Built for e-commerce: cards, Apple Pay, Google Pay, local methods and crypto.
389.00 SARCard •••• 4417, Saudi Arabia, order 48207
✓Created27 Oct 2026, 14:01:38
•••Pending 3DSCustomer verified
✕Declined, PSP ASoft decline 05, 412 ms
✓CascadedNext eligible route, PSP B
✓Success, PSP B14:01:40, webhook delivered
Your storeYour checkout, your design
Linen overshirtSand, size M, qty 179.90 EUR
Subtotal79.90Delivery10.00Total89.90 EUR
Standard delivery2 to 4 business days, 10.00 EUR
Delivering toKeizersgracht 120, Amsterdam
Contacte****n@gmail.com, order updates by emailEdit
Pay by cardCard number4242 4242 4242 4242OMNO FIELDExpiry08 / 29OMNO FIELDCVV1•••OMNO FIELDEnter the 3-digit codePay 89.90 EUR✓ ApprovedCard data goes straight to Omno. Dashed outlines mark the Omno fields for this example.
Card Fields.Your checkout, your brand. Three secure Omno fields for card number, expiry and CVV, styled to match. Card data never touches your servers.
Checkout.A no-code checkout builder: layout, branding, method categories, minimum and maximum amounts and fields, changed in the dashboard without a release.
Eligibility rules remove providers that cannot take this payment, by country, method, currency, amount, customer group or verification level.
2Route.
1Brazil, PIXPSP B, then A, then DMatch2Amount over 2,000 BRLPSP A onlySkip3Repeat customersPSP D firstSkipRule 1 appliedEdited by your team
Your routing rules pick the provider: by card BIN, country, currency, amount, browser or customer segment. Split traffic by share, cap each provider, and keep returning customers on the provider that worked.
3Cascade.
✕PSP B unavailableNo response, moved on✕PSP A rejected the requestNot accepted, moved on✓Accepted, PSP DNext provider in your ruleCustomer saw one checkoutTries until one accepts
An automatic fallback: if a provider is unavailable or rejects the request, the payment moves to the next provider in your rule, until one accepts.
4Confirm.
payment.status_changed200 OK"status": "approved","amount": 150.00,"currency": "BRL"Delivered in 120 msSigned, retried on failure
The final status reaches your back office by webhook. Your balances follow the webhook, not the redirect.
Cards, wallets and crypto side by side, with the final status sent to your back office by webhook before you deliver.
Several shops, one account
Each brand or country store keeps its own routing rules and checkout design, with one team and one report.
Regulated and high-risk sectors
Licensed merchants in regulated industries use the same routing, risk controls and payouts. How we work with them
Examples. Values are illustrative.
Where your customers pay. Almost anywhere.
Omno serves every country except markets under OFAC sanctions or on the FATF call-for-action list. Pick a payment type to see where its local methods are, then open a country guide.
Cards and wallets
Visa, Mastercard, Apple Pay and Google Pay almost everywhere, plus local wallets and super apps where shoppers prefer them.
Route each payment by card BIN, country, currency, amount, browser or customer segment. No code, no deploy.
Traffic splitting and limits
Share volume across providers by proportion, and cap how much each one gets based on its declines and successes.
Sticky routing
Keep returning customers on the provider that worked for them, or move them off the one that did not.
Cascading
If a provider is unavailable or rejects the request, the payment moves to the next one until it is accepted. Provider downtime stops being your downtime.
Brazil, PIX and cards 6 conditions configuredSave changes
CountriesBrazil
MethodsPIXCard
CustomerVerification level 2+
Provider order1PSP B2PSP A
AmountUp to 5,000 BRL
If rejectedNext provider in order
Recent decisions✓150.00 BRLPIXPSP B✓89.90 BRLCardPSP B✓2,400.00 BRLCardPSP A, after PSP B rejected
Rule 1 of 3Edited by Ana, 14:02
Checkout builderLayout, branding, categories, min and max amountsCustomise
Omno formsAsk the customer for fields a provider needs
Saved cards and accountsReturning customers skip the card form
Payment orchestration is a software layer between your checkout and your payment providers. It connects many providers through one API and applies your routing rules to every payment, then moves the payment to another provider when one is unavailable or rejects it.
Who is Omno for?
Omno is payment orchestration for e-commerce merchants in every market, with cards, Apple Pay, Google Pay, crypto and the local methods each market prefers, such as PIX in Brazil, mada in Saudi Arabia or Kaspi in Kazakhstan. It serves every country except markets under OFAC sanctions or on the FATF call-for-action list, and also works with licensed merchants in regulated and high-risk sectors.
Do we need developers to change providers or routing?
No. After one integration, your payments team adds or switches providers, edits routing rules and changes the checkout in the dashboard. Your developers stay on your product instead of payment plumbing.
What customer data do we have to send?
Very little. A payment can start with the minimum, and when a provider asks for more, such as an address or a national ID number, an Omno form collects it from the customer and Omno stores it for the next payment. You never build those forms or keep that data on your side.
How fast can we go live?
A typical integration goes live in 14 days. Most of that time is your providers' onboarding, not code. Connecting to Omno does not sign you up with payment providers: each provider onboards you separately, with its own checks and contract, and we connect each one as soon as it approves you. On the Omno side, one API and the hosted checkout cover every method, and routing rules are set in the dashboard.
What does Omno cost?
Omno does not publish a price list. We quote Omno's own fee per merchant, based on your monthly volume, your markets and the products you use. Processing fees stay with the payment providers, under your own contracts with them, so you see both separately.
How does cascading work?
Cascading is an automatic fallback. When a provider is unavailable or rejects the request, Omno sends the same payment to the next provider in your rule, and keeps going until one accepts. The customer does not re-enter anything.
Does Omno support recurring payments and refunds?
Not yet. Both are on the roadmap. Today Omno covers one-off payments with cards, wallets, local methods and crypto, with saved cards and accounts for returning customers. If you need recurring payments or refunds, tell us your timeline and we will share ours.
Order2,000.00 KZTKaspi.kzreturning customer
PSP Asoft decline 05
cascadenext eligible route
PSP Bapproved
Will it pass?
it will.
Tell us where your payments fail. We will show you how routing changes the outcome.