What does the Omno dashboard show?
The dashboard is built around the questions payment teams ask every day. How many payments and payouts went through? What share was approved, declined or failed? Which providers, methods and countries are doing worse than last week? Every number can be filtered by merchant account, provider, method, country, currency, customer group and period.
Real-time transaction success metrics sit on top. They update as transactions finish, so a provider that starts timing out or declining more than usual is visible within the day, not in next month’s report. Because every provider reports through the same orchestration layer, the definitions are the same for all of them. An approval at one PSP means the same thing as an approval at another.
What does the transaction trail show?
Routing is only useful if you can trust it, and you can only trust what you can inspect. For every transaction Omno records the providers that were eligible after country, method, customer group and verification level filtering, the router that made the choice, the provider selected, every cascade attempt with the provider’s response, every webhook sent to your backend, and the final outcome. Investigations that used to take a ticket per provider take minutes.
Support teams use the log to answer customer questions such as why a card was charged by an unfamiliar descriptor. Payments teams use it to check that a new rule behaves as intended. Finance uses it to match a successful payment to the provider statement that will contain it. Risk teams use it to see whether declined payments moved to another provider, and where.
Approval rate needs a clear definition before anyone acts on it. With cascading, one customer payment can produce several attempts: a rejection at the first provider and an approval at the second. Counted per attempt, the first provider shows a decline and the second an approval. Counted per payment, the customer was approved once. Both views are useful. The per-attempt view tells you how each provider performs. The per-payment view tells you how many customers actually got through. Keep the two apart when you compare routes, and when you compare Omno’s numbers with a provider’s own portal, check which one the provider reports.
What changes versus a single PSP?
A single PSP gives you its own reports in its own format. That is fine until you add a second provider. Then you have two portals, two export formats, two sets of status names and two definitions of approval rate. Comparing them takes a spreadsheet and a lot of trust.
With Omno, every provider feeds the same data model. You can put two providers side by side on the same country, method and period and see which approves more, which declines for which reasons and which pays out faster. You can see the effect of a routing change on the same dashboard where you made it. Multi-merchant management extends the same view across brands and legal entities, while role-based access control keeps each team inside the accounts it should see.
What do customer profiles add?
A payment is one event; a customer is a history. The customer profile brings together every payment a customer made across your providers, the cards and accounts they saved, and the details Omno forms collected when a provider needed them. Support sees the whole picture when a customer writes in, and risk and routing rules can treat a returning customer with a clean history differently from a first-time payer.
How should teams use reporting day to day?
Payments managers usually start with approval rate by provider and country, then drill into decline reasons where a route underperforms. A rise in soft declines on one provider is a signal to change the provider order in your routing rules. A rise in technical failures is a signal to check the provider’s status.
Finance teams use exports for reconciliation: payments and payouts by provider and period, matched to settlement reports. Risk teams watch chargeback-related signals by method and customer group, and use card blocking where a pattern appears. Product teams look at method usage by country to decide which local methods to add next. All of these views come from the same data, which keeps everyone working from the same numbers.