How do payouts work in Omno?
A payout starts from one of two places. In the hosted checkout, the customer opens the payout view in the same session they use for payments, chooses an eligible method and confirms the amount. In Direct Link, your backend calls Omno directly for APM and crypto payouts, such as marketplace seller payouts or cashback, and no Omno UI is shown. Either way the request enters the same API as a payment.
Omno then applies eligibility. Providers that do not pay out in the recipient’s country, do not support the chosen method, or are restricted to other customer groups or customer verification levels (KYC levels in the API) are removed. Routing picks one of the remaining providers and sends the payout. When the provider confirms or rejects it, Omno sends a webhook to your backend with the final status. That webhook, or a call to Get Transaction Info, is what your finance team should use to close the payout.
Payout statuses follow the same pattern as payments. A payout can succeed, be declined by the provider, fail before or at the provider, time out, or stay pending while the receiving bank or wallet processes it. Pending and timed-out payouts can resolve later, so your systems should keep the payout open until a final status arrives instead of retrying blindly and risking a double payment. Using your own reference on every request makes it easy to match the webhook to the payout in your ledger, and the transaction ID Omno returns links the payout to its routing log.
Why are payouts harder than payments?
Payments are pushed by a customer who wants to buy. Payouts are pulled from your balance, under more rules and more scrutiny. Several things make them harder:
- Coverage is thinner. Not every method that accepts payments can send money back. Some providers accept payments in a country but cannot pay out there.
- Identity rules are stricter. Many markets expect payouts to go to an account in the recipient’s own name, and refunds often return through the method used to pay.
- Timing is visible. A slow seller or customer payout is a support ticket and a reason to leave. Customers and sellers notice delays more than they notice fast payments.
- Funding matters. A provider can only pay out what is available in your balance with that provider, so payout routing has to consider where funds sit.
Treating payouts as part of the same orchestration layer addresses most of these. The same rules that keep a payment away from an unsuitable provider keep a payout away from one too.
What changes versus a single PSP?
With one provider, your payout coverage is that provider’s coverage. If it cannot pay to a local wallet in Uzbekistan or a bank account in Mexico, you either build a second integration or ask customers and sellers to choose something else. If its payout rail is down, customer and seller payouts queue up and support volume rises.
With Omno, payouts can use any eligible provider connected to your account. You can route payouts for a country to the provider with the best payout coverage there, even if a different provider handles most payments. Customer groups let you give high-value customers or top sellers a different payout path. Customer verification levels let you hold back payouts through certain providers until a recipient is verified. All payouts report in one format, so reconciliation does not change when the provider does.
How should finance teams reconcile payouts?
Use the webhook as the trigger and the transaction ID as the key. When a payout webhook arrives with a final status, update your ledger and the customer’s or seller’s balance. For payouts that stay pending longer than expected, call Get Transaction Info rather than guessing. Export payout data from the dashboard by provider, method and period to match against provider statements, and use the routing logs to see which provider handled each payout and why. Omno’s reporting and data export cover payments and payouts in the same format, which keeps month-end work in one place.