A platform needs a baseline
omwio has published a product update on Core, the part of the platform every tenant runs on regardless of billing plan. The company describes Core as the piece that has to exist before any optional module makes sense: a payment platform isn't useful until money can move, be attributed to a merchant, and be seen by everyone who needs to act on it. Core spans the Tenant manager, Merchant panel, Hosted checkout and Processing API.
Merchants, transactions and wallets in one model
Each tenant onboards its own merchants with tariffs, commissions, assigned methods and per-merchant overrides, and the merchant record is the anchor everything else hangs off. Payments, payouts, exchanges, refunds and chargebacks are all modeled as transactions, sharing one status model, a public token and a single collapsed status mapping that merchants see. Wallets are multi-currency per merchant, with balance history and reserve visibility, so a manager can answer where an amount came from and what is currently being held.
Routing, checkout and invoicing
Providers are attached as modules, MIDs are registered against them, and each currency gets its own enabled method set. Route resolution can be previewed for a given merchant and method before any traffic reaches it. Hosted checkout gives merchants a branded payment page on the tenant's own pay host, and the Processing API is one signed API to create and read transactions, with provider quirks normalised into canonical payment instructions. Merchants can also raise invoices and send them through branded mail in the recipient's language, with payers settling on a public page; a tenant-scoped customer directory stores payer details encrypted, with blind-index lookup so search never needs plaintext.
Refunds, chargebacks and disputes
The full post-payment path sits in the baseline, not behind an add-on: refunds, chargeback handling and a structured dispute workflow. A manager can let a merchant open disputes on its own payments and payouts, from the merchant panel or through the Processing API, with a reason and up to five evidence files. The manager resolves disputes, and balances are rolled back and re-posted automatically.
Analytics, currencies and access control
Core includes conversion and provider analytics: success rates, failure reasons and volume over time for payments and payouts, ranked by merchant, provider and MID, and filtered by currency, status and period. Merchants get their own dashboard limited to their own data. Currency pairs come with rate sources and rate locks, merchant-to-merchant exchanges run on live quotes, and rounding rules are enforced server-side so exports and screens agree. Access is governed by RBAC down to individual panel actions, with tenant-scoped two-factor authentication, password resets, session controls and a recorded trail of administrative activity.
Always on, in every plan
Core is present in every billing plan and cannot be switched off. A tenant running only Core can already onboard merchants, take payments, pay out, invoice, exchange currency and resolve disputes — optional modules add reach on top of that, not the ability to trade.
