Company

About

AFRIPEI is payment infrastructure for Tanzania. A merchant integrates once. Mobile money stays behind the API. Status, webhooks, and the ledger are AFRIPEI’s.

What merchants use

• Collections by phone prompt or control number, in TZS.
• Payouts to mobile money and to a bank account, only against available balance.
• Signed webhooks, so the merchant’s system hears the outcome.
• A merchant portal for keys, balances, verification, and support on a transaction.

Amounts are decimal strings. TZS uses two decimal places. A create response means the request was accepted. The customer still confirms a collection on their phone.

One integration

M-Pesa, Airtel Money, Mixx by Yas, and Halopesa are how customers already pay. A merchant sends a phone number. AFRIPEI delivers the prompt. The merchant does not keep a separate integration for each wallet, and does not keep a separate ledger for money in and money out.

Two portals

The merchant portal is where a business signs in, creates keys, reads the balance, and opens support. The owner portal is where verification is reviewed. They do not share a session. A merchant key cannot call owner routes.

What is recorded

Each collection and each payout keeps the amount, the status, and the fee snapshot from the moment it was created. A later change to the account does not rewrite that row. Webhooks are signed. Audit records of money and access are insert-only.

Before money moves

A new account waits for verification. Until it is active, it cannot collect and it cannot pay out. A live key on the production API moves real shillings. There is no sandbox.