Collections and payouts, in seconds.

One REST API to collect from and pay out to mobile money wallets. Asynchronous by design, idempotent by default, webhook-driven, with a ledger you can reconcile against.

Get credentials Read the API docs

Collect

Pull funds from a customer's wallet. The customer approves on their handset and the payment settles to a final state of success, failed or expired. Deposits, top-ups, checkout and subscriptions, with line items and tax recorded.

Disburse

Push funds to a customer's wallet with no approval step. Balance is reserved at submission and the payout settles to success or failed. Refunds, winnings, payroll and marketplace payouts.

Built for networks that are not reliable

Mobile money is slow and occasionally lies. The API assumes it.

Asynchronous

Every submission returns 202 Accepted immediately. Nothing in your stack blocks on a network that can take minutes.

Idempotent

An idempotency key on every request means a retry after a timeout never charges a customer twice.

Signed webhooks

HMAC-SHA256 signatures with a five minute replay window, so you can trust the callback that moves your ledger.

Reconcilable

A full transaction ledger with balance tracking, so month end is a query rather than an investigation.

Integration

Six steps to live.

Get credentials
A base URL and an API key for the sandbox, then production.
Submit the payment
POST to /v1/payments to collect, or /v1/payouts to disburse.
Take the 202
Accepted immediately. Store the reference and move on.
Customer approves
On collections only. The prompt reaches the handset.
Handle the webhook
Verify the signature, act on the final state, respond fast.
Reconcile
Query the ledger and the wallet balance for the settled position.

Who it is for

Platforms operating at volume that need collections and payouts in a mobile money market: marketplaces, gaming and digital platforms, billers, lenders collecting instalments, and licensed institutions that want the traffic to settle onto their own book.

The regulatory position

Maly Tech does not hold, own or take custody of funds and does not carry out regulated payment activity. A licensed institution safeguards and settles the money. Where a partner institution holds the settlement account, every merchant collection converts a payments relationship into a deposit relationship.

Documentation

Full API reference, webhook specification, idempotency rules, error taxonomy and a go-live checklist.

malypay.com/docs

Operational questions

The things that break in production.

Nothing bad. Requests carry an idempotency key. A retry with the same key returns the original result rather than creating a second payment, which is the single most common way platforms double-charge customers on unreliable networks.

Every webhook is signed with HMAC-SHA256 and carries a timestamp with a five minute replay window. Verify the signature before you act on it, and reject anything outside the window.

A collection settles to success, failed or expired. Expired means the customer never approved the prompt. A payout settles to success or failed, with the balance reserved at submission so a payout cannot be authorised against money that is not there.

The gateway is live in the Republic of Congo, integrated and deployed, with the operating rules set. Additional markets follow the same integration pattern on rails Maly already runs.

Yes, and that is usually the point. Merchants settle into your account, so payment traffic becomes deposits, float and structured transaction history you can underwrite against.

Start the conversation

Start in the sandbox.

Tell us the market and the volume. We issue credentials, share the integration guide and walk your engineers through the go-live checklist.

Request credentials API documentation