The Olympus infrastructure.
A small set of layers, each with a clear job, shared by every Olympus product.
The layers behind every Olympus product.
The layers.
Banking
Accounts, balances and the account model. Business accounts by currency, subaccounts and virtual accounts sit on a set of accounting records.
Payments
The movement layer: transfers, payment links, QR, payouts and settlement, each with limits, approvals and idempotency.
Accounts
The record of who holds what. Balances are derived from account records, so history and balance cannot disagree.
Cards
Card issuing is through issuing partners. Olympus holds the card record, the per-card controls and the spend posting.
Merchant
Acceptance channels, settlement, disputes, approvals and reporting for merchants.
APIs
Scoped keys, sandbox and live environments, idempotency and signed webhooks over the same capabilities.
Identity
Verification of people and businesses, including biometric identity checks and beneficial-owner declarations, before accounts open.
Risk
Device intelligence at sign-in and payment, rate limits, and holds where fraud or financial crime is suspected.
Compliance
Sanctions screening, transaction monitoring against reporting thresholds and retention aligned to the regulator.
Operations
Statements, bulk and scheduled payments, audit logs and reconciliation: the back-office layer.
Design principles.
One platform
Every product posts to the same set of accounting records. There is no side system to reconcile against.
Data-driven country rules
Tax engines, payment methods and settlement rails are configured per country.
Controls alongside the platform
Identity, risk and compliance are shared layers, so a new product cannot skip them.
Fail-safe routing
A route stays switched off until it has been verified end to end.