Introduction - Moflay Documentation

The Moflay API gives your backend direct access to M-Pesa payment, customer, and transaction workflows over HTTPS.

Base URL

https://api.moflay.com/v1

Authentication

Send your API key in the Authorization header:

Authorization: Bearer mof_test_your_api_key

Use a sandbox key for sandbox data and a production key for live data. The API key determines the business, environment, and permissions for the request.

Core API areas

Area	Purpose
Express payments	Create M-Pesa Express STK push payment requests with `POST /v1/express`
Payments	Read the current status of a payment attempt with `GET /v1/payments/{id}`
Customers	Create, update, list, and delete customer records
Transactions	List transactions and fetch individual transaction records
Webhooks	Receive signed payment and customer events in your backend

Payment status flow

Call POST /v1/express.
Store the returned paymentId and transactionId.
Use GET /v1/payments/{id} for status checks (this reads Moflay’s stored state; see Payment statuses & outcomes).
Use Moflay webhooks for production-grade asynchronous status updates.

Amounts

Send payment amounts as integer minor currency units. For example, amount: 1000 means KES 10.00.

Supporting behavior

Cursor-based pagination for list endpoints
Environment-specific API keys
Permission-based access control
Standardized JSON error responses
Rate limit headers on public API responses

Read next

Authentication
Payment statuses & outcomes (Developer Docs → Payments): Moflay statuses, Daraja codes, and webhooks
Errors
Daraja callbacks
Rate limits
Pagination