Use Cases
Built for how different people actually use it.
Three real angles on the same platform — pick the one that's you.
- Keep KES and crypto savings in one place instead of juggling M-Pesa, an exchange, and a separate wallet app
- Send and receive across five blockchain networks without a new address to manage per network
- Convert between currencies at a locked quote instead of guessing what a rate will be by the time a transfer clears
Businesses
Accept KES and crypto payments, and use escrow for anything that needs a trust layer.
See how escrow works- Accept M-Pesa payments via Paybill alongside crypto payments, reconciled in one transaction history
- Use escrow for marketplace-style transactions — funds held until both a buyer and seller confirm, with an optional neutral third-party manager
- Programmatic access via the developer API for anything that needs to happen automatically rather than by hand
Developers
Integrate deposits, withdrawals, and escrow directly into your own systems.
See the Developer API- HMAC-signed REST endpoints for deposits, withdrawals, and escrow — no session cookies, built for server-to-server calls
- Signed webhook delivery for status changes, so your systems react to events instead of polling for them
- The same underlying engine (fee calculation, confirmation thresholds, ledger accounting) the dashboard itself uses — no second, less-tested code path