How a payment moves.
Six stages, the same for a payment link, a payout and a transfer.
From an app or API call, with an idempotency key.
Limits, approvals, verification status, sanctions checks.
Method and settlement route chosen from country capability data.
Sent to the processor or bank partner.
Partner webhook confirms or fails the payment.
Records written; your webhook fires.
Routing.
Which methods a merchant can use, which tax logic applies and where proceeds settle are read per country. A new market needs configuration and an integration, not a rebuild. A route that has not been tested end to end stays disabled behind a flag until it has been.
- Per-country capability data
- Settlement to an Olympus account or an external bank
- Unverified routes fail closed
Looked up in capability data.
Chosen from what that country allows.
Olympus account or external bank.
Partner integrations.
Olympus does not move money on its own rails alone: it connects to processors, settlement services and banking partners, and reflects each one’s status.
Card and mobile-money processing
Through a payments aggregator for card, mobile money and bank transfer.
Cross-border and FX
Through a settlement integration for international transfers and foreign-currency account details.
Records and bank sync
Through an accounting and bank-connection integration.
When something fails.
A request is retried
The idempotency key returns the original result.
A partner is slow
The payment stays in processing until a confirming webhook arrives.
A payment fails
Marked failed, nothing recorded, and a payment.failed event fires.
A large refund is requested
It waits for a second reviewer instead of executing.