Where people touch it
Web banking, the merchant dashboard, the mobile app, Olympus Go and your own product are all clients. None of them hold money or keep their own books; they ask the layers below.
What businesses use
Accounts, payments, cards, merchant services and treasury tools are product surfaces over shared capabilities. A new product reuses what already exists.
How value travels
Transfers, bulk payments, payment links, QR, payouts and settlement are one movement layer. It handles approvals, limits, idempotency and status for every route.
The single record
Balances and history come from a set of accounting records. A payment made in the app and one made through the API post to the same records, which is what makes reconciliation possible.
Controls that apply to everything
KYC and KYB, device intelligence, sanctions screening and transaction monitoring sit alongside the platform, not inside one product, so no route around them exists.
How you build on it
The same capabilities are exposed through scoped API keys, sandbox keys and signed webhooks, so a platform can offer to its users what Olympus offers to its own.
The layers of the Olympus platform.