Frequently asked questions

No. One account gives you access to all of them, but you only pay for what you use. Plenty of customers use HashSMS alone, or payments alone. They work better together — a payment can trigger an SMS receipt without you writing extra code.

Not yet. Those are systems we build around your specific operation rather than self-service products. They run on the same payments, messaging and wallet services as our products, so the hard parts are already built. Talk to us and we will scope it.

For our products, minutes — register, top up, and your API key is available immediately. For a custom system, the discovery call happens within days and you get a scoped proposal before any commitment.

Our messaging and payment services are built for Kenya — M-Pesa, Kenyan mobile networks and local compliance. Custom software projects we take on across East Africa.

Yes. You can start on our shared sender ID immediately and apply for your own alphanumeric sender ID at the same time. Once it is approved and mapped to your account, your messages go out under your own name automatically.

Every message gets a delivery report from the network, shown per recipient in the dashboard and available over the API. You see delivered, failed and the reason for failure — not just "sent".

OTPs, payment receipts, order and delivery updates, and reminders. Open rates are far higher than SMS, though WhatsApp has its own rules about what you may send and when.

Yes. The APIs share the same shape, so switching channel — or falling back to SMS when WhatsApp is not available for a contact — is a small change rather than a second integration.

HashPay is our payment service: M-Pesa collections via STK Push, Till, Paybill and bank, payment links and hosted checkout, plus wallets and payouts. You can receive money without applying for your own Safaricom till.

Yes — that is what B2C payouts and disbursements are for. Upload a payroll or payout file, review it, and run it. Each payout is tracked individually with its own result and receipt, so a failure in one row does not leave you guessing about the rest.

Settlements are processed in real time. Funds collected through HashPay move to your linked account automatically, usually within minutes of a successful transaction.

Failed transactions are logged in real time with the exact reason from Safaricom — cancelled, insufficient balance, wrong PIN, timeout. No funds leave the customer's account and no settlement is triggered. Your system can handle each case differently via webhooks.

A small per-transaction fee, with no setup or monthly charges. See the pricing page for the current rates for your volume.

HashBack decodes the hashed phone numbers that arrive in Safaricom M-Pesa C2B callbacks, turning an unreadable hash into a real phone number you can use to match a payment to a customer.

Pay as you go. Top up credits (KES 100 minimum on Regular) and pay per request. Credits never expire, and no credit is deducted for a failed decode.

Most decode requests return in under 200ms, which makes it usable inside a live payment confirmation flow rather than as a batch job.

No. HashBack supports Kenyan mobile numbers only (Safaricom and Airtel). It is built specifically for Kenya's M-Pesa ecosystem.