What breaks in cross-border e-commerce payments?
Cross-border e-commerce loses money in three places: at the issuer, at the checkout and after the sale.
At the issuer, a foreign transaction is treated with suspicion. A card from Saudi Arabia, Turkey or Brazil that is charged by an acquirer in another country is more likely to be declined than the same purchase processed locally. The customer sees an error, tries again or leaves, and the merchant never learns that the same card would have been approved through a domestic route.
At the checkout, the problem is choice. In many of the fastest-growing online markets, cards are not the default. Brazilian shoppers reach for PIX. Saudi shoppers use mada debit cards and wallets such as STC Pay. Mexican shoppers pay with SPEI or cash at OXXO. Colombians use PSE. Kazakh shoppers use Kaspi. A checkout that offers only international cards loses a share of every basket in these markets before a single payment is attempted.
After the sale, the problem is disputes and reconciliation. Chargebacks grow with volume and with new markets. Each provider reports in its own format, so finance cannot easily see which route is cheaper, which approves more or which causes more disputes.
How does Omno improve checkout conversion?
Conversion improves when more shoppers find a method they trust and more of their payments are approved. Omno works on both.
The hosted checkout shows each shopper the methods that are eligible for them, from every provider you have connected. A shopper in Brazil sees PIX and cards. A shopper in Saudi Arabia sees mada and the wallets available there. You integrate once, through the Web SDK or an iFrame, and adding a method in a new market changes what shoppers can select without changing your frontend.
Behind the checkout, routing chooses the provider for each payment. Eligibility rules filter providers by country, method and customer group, and your routing rule picks from those that remain, for example a provider with local acquiring in the shopper’s country. If the provider is unavailable or rejects the request, cascading moves the payment to the next provider in the rule without the shopper typing anything again.
Saved cards shorten repeat purchases. Card details are stored as tokens in Omno’s PCI DSS compliant environment, so returning shoppers pay in fewer steps and raw card data never reaches your servers. Because the token lives in the orchestration layer rather than in one provider’s vault, a saved card can be routed to whichever provider your rules choose.
Why do local payment methods matter so much?
Local methods are not a nice extra in these markets. They are how people pay. Instant payment systems such as PIX and SPEI move money between bank accounts in seconds. Domestic card schemes such as mada in Saudi Arabia, Troy in Turkey and the Humo and Uzcard schemes in Uzbekistan are issued to most of the population. Wallets and super-apps such as STC Pay, Kaspi, Payme and Vodafone Cash are used daily. Voucher and cash networks such as OXXO Pay and Fawry serve shoppers without cards. BNPL providers such as Tabby let shoppers split larger purchases.
Each method has its own behaviour. Some confirm instantly, others hours or days later. Some support refunds and payouts, others do not. Some have no chargebacks at all. Omno’s payment method pages describe each one, and the checkout handles the differences, reporting every outcome to your backend in the same webhook format.
How does Omno help control chargebacks and fraud?
Chargebacks are a cost and a risk. Each one carries a fee and a lost sale, and a high ratio puts the merchant under acquirer and scheme monitoring. Omno gives e-commerce merchants several controls:
- Fraud scoring gives every transaction a risk score before it is processed.
- Customer rules and blocking allow or restrict providers and methods by customer tag and volume, and block a risky customer fully or from specific methods.
- Limits cap amounts and volumes per provider and per method.
- Card blocking stops a card linked to fraud or a chargeback from being used again.
- Customer groups let you route new or higher-risk customers to providers with stronger checks, and trusted repeat customers to providers that approve more.
- Method mix matters. Many bank transfer and instant payment methods have no card-style chargeback process, so offering them shifts part of your volume away from dispute exposure.
- The transaction trail and exports show which providers, methods and customer segments decline or fail, so you can change routing with evidence.
Merchants that also run a dedicated fraud screening tool can pass its results to Omno through customer groups, so routing and risk decisions stay in one place.
What about refunds and payouts?
Refunds are part of conversion. Shoppers buy more readily from a store that refunds quickly through the method they paid with. For cards, a refund usually returns to the same card. For local methods the rules differ: some instant payment and wallet methods support refunds directly, some voucher methods do not, and the merchant has to pay the shopper back another way. Omno’s method pages state refund support for each method so you can plan this before launch. Refunds through Omno itself are on the roadmap and not available yet.
Marketplaces and platforms also send money out, to sellers, creators or partners. Omno Pay-Out uses the same API, eligibility rules and webhook format as pay-ins, so a payout to a local wallet or bank account is handled by the same integration that took the original payment. Finance teams reconcile payouts and sales from the same exports, keyed by the same transaction IDs.
Which markets does Omno cover for e-commerce?
Omno serves e-commerce merchants in every country except markets under OFAC sanctions or on the FATF call-for-action list. The countries on this page show the local depth behind that, including markets such as Brazil, Mexico and Colombia, Saudi Arabia, the United Arab Emirates, Egypt and Turkey, Kazakhstan and Uzbekistan, and Nigeria. The coverage index lists each country with its main local methods, and current counts of connected providers, methods and currencies appear in the facts on this page.
What changes versus a single PSP?
With one provider, your approval rate in each country is that provider’s approval rate there, your local method coverage is its coverage, and its outage is yours. Expanding into a new region usually means adding a second provider anyway, with a second integration and a second report.
With Omno, every provider sits behind one checkout, one API and one webhook format. Payments follow the routing rules you set, a rejected payment moves to the next provider, and payouts use the same integration. Approval rates and decline reasons for every provider sit on one dashboard, which makes it practical to compare routes and negotiate with providers using your own data.