Get paid by M-Pesa, Airtel Money, T-Kash, bank transfer or card.
Pay out the same way. Cloudpay gives businesses in Kenya one wallet for collections, payouts and transfers, with a portal your team can work from and an API for your developers.
Prefer to talk first? Call 
+254 795 703 703 or email hello@cloudpay365.com.
Accept and send money the way Kenya already pays
- M-Pesa
- Airtel Money
- T-Kash
- Visa
- Mastercard
- Bank transfer
Everything your money needs to do, in one account.
Take payments from customers, pay staff and suppliers, and keep a clean record of all of it. Use the merchant portal, the API, or both.
Collect payments
Send a payment request straight to your customer's phone, or accept bank transfers and cards. Money lands in your Cloudpay wallet and you are notified the moment it does.
Pay out in bulk
Pay hundreds of people in one run, to mobile wallets or bank accounts. Follow each payment to its final state, and see exactly which ones need attention.
Scheduled payments
Set up rent, salaries or supplier payments once. Cloudpay sends them on the dates you choose.
Approvals
Decide who can prepare a payment and who must approve it before any money leaves your account.
Wallet and statements
See your balance and every transaction, filtered by date, reference or status. Reconciling takes minutes.
Ways to pay
M-Pesa, Airtel Money, T-Kash, bank and card
Transaction types
Collections, payouts and business transfers
Wallet
Every shilling in and out, in one balance
Sandbox outcomes
Test success, failure and late results before going live
From sign up to live payments.
Only one step involves waiting on anyone, and you can build your whole integration while it happens.
Step 1 of 4
Open an account
Sign up with your personal and business details and confirm your email. Your wallet is ready immediately and you can start collecting from day one.
- Personal and business details
- Email confirmed with a one time code
- Wallet created straight away
Four calls to a working integration.
A REST API with the same requests in sandbox and production. Only your keys change when you go live.
- Get a token. Exchange your client ID and secret for an access token.
- Initiate a payment. Collect, pay out or transfer with a single endpoint.
- Receive the result. We call your webhook when the payment reaches its final state.
- Reconcile. Query any payment, or pull a statement for a date range.
curl -X POST https://api.cloudpay365.com/api/v1/payments/initiate/ \ -H "Authorization: Bearer $ACCESS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "merchant_id": "CP00012345", "transaction_type": "C2B", "payment_method": "mpesa", "currency_code": "KES", "amount": 2500, "account_number": "254712345678", "reference": "ORDER4821", "result_url": "https://shop.example.com/hooks/cloudpay" }'
{
"success": true,
"message": "Request accepted for processing",
"data": {
"charges": 0,
"payment_method": "mpesa",
"transaction_id": "TXN8F3K2Q9",
"merchant_reference": "ORDER4821"
}
}Protection built into every account.
Safeguards that are on by default, not extras you have to remember to switch on.
Verified businesses only
Every merchant is reviewed before money can leave an account, which keeps the whole network safer.
IP whitelisting
Production API calls are accepted only from the server addresses you register. Anything else is refused.
Short lived tokens
API access tokens expire after an hour, so a leaked token is only useful for a very short window.
Code on every sign in
Portal sign in is confirmed with a one time code sent to you, on top of your password.
Approvals before payouts
Ask for a second person to approve a payment before it is sent, so no single login can move funds alone.
Sandbox kept apart
Sandbox credentials only ever charge the sandbox wallet. Testing can never move a real shilling.
Start in sandbox today. Go live when you are ready.
Open an account in a few minutes, or sign in to the merchant portal to pick up where you left off.