Skip to main content
Moflay is a developer-first payments infrastructure layer for M-Pesa. You integrate with Moflay once, and Moflay handles the Daraja complexity that usually slows teams down: credential management, request validation, transaction state updates, and Safaricom callback handling. These docs focus on the developer workflow for accepting M-Pesa payments through the API and SDK.

​
What you can do with Moflay

  • Accept M-Pesa payments with a clean API or SDK
  • Test in a sandbox before you go live
  • Manage Daraja credentials by environment
  • Track customers and transactions from the dashboard or API
  • Receive real-time payment updates through signed webhooks

​
Why teams use Moflay

  • Ship faster: Get from account creation to first payment in minutes
  • Avoid direct Daraja complexity: No manual token handling or raw callback plumbing
  • Keep settlement simple: Payments go directly to your M-Pesa till or paybill
  • Operate with confidence: Use consistent transaction records, dashboard visibility, and webhook events

​
Start here

Make your first payment

Go from zero to a sandbox STK push with the SDK.

Set up your account

Create your organization, choose an environment, and prepare your dashboard.

Create an API key

Generate a sandbox or production key and assign the right permissions.

Understand the flow

See how Moflay fits between your app, Safaricom, and your backend.

​
Choose the right path

​
What these docs assume

  • You are building a product that needs to collect M-Pesa payments
  • You have or will create a Moflay account
  • You understand the difference between sandbox testing and production payments
Moflay may also support payment links or hosted checkout in the product, but this docs set is centered on API- and SDK-based integration.