About SMPLY PAY
Money movement shouldn't require five different providers.
We built SMPLY PAY because moving money between Kenyan shillings and crypto, or holding funds in escrow until both sides of a deal are ready, meant stitching together tools that were never designed to talk to each other. We wanted one platform that treats all of it — deposits, withdrawals, conversions, escrow — as one system.
What we stand for
Reliability first
Every feature ships only once it's genuinely reliable — a payments platform that's fast but occasionally wrong isn't actually useful.
Transparent by default
Fees shown before confirmation, an auditable ledger, a real security page instead of marketing filler — nothing about how this platform works should require trusting a black box.
Built for real use, not demos
Every feature here exists because a real transaction shape needed it — KES and crypto side by side, escrow for deals that need a trust layer, an API for systems that need to move automatically.
Correctness over speed-to-ship
A double-entry ledger, OTP confirmation on every withdrawal, and confirmation thresholds on crypto deposits all cost engineering time that a faster, looser implementation wouldn't have spent.
Our story
SMPLY PAY started as an internal tool for reconciling M-Pesa and crypto balances across a handful of accounts, and grew into the platform it is today once it became clear the same problem — money that needs to move reliably across currencies, with a real audit trail — was one a lot more people had. We're still building on that same foundation: correctness and auditability first, new surface area second.