Mobile money collection
Trigger USSD push payments to customers' phones and track each one from pending to completed.
Collect mobile money, run subscriptions, notify your apps with signed webhooks and reconcile every shilling — without rebuilding payment operations for each app.
Built for teams running several apps on one payments backbone.
Trigger USSD push payments to customers' phones and track each one from pending to completed.
Define packages with daily, weekly, monthly or yearly plans. Completed payments provision access automatically.
Each app gets its own project, API keys, packages and webhook endpoint — all managed from one place.
Your backend is notified the moment a payment settles, signed with HMAC-SHA256 so you can trust every call.
Missed provider callback? Scheduled status polling catches up and updates the transaction for you.
Volume, success rate, webhook health and subscriptions — filter by project or see everything at once.
Store provider credentials once and route each project and package to the right account.
Publish step-by-step "how to pay" guides in English and Swahili that your apps load via the API.
Your app lists packages and instructions from the API and the customer enters their phone number.
PaymentSystem routes the request to the right provider account for that project.
A USSD prompt appears on their phone. They approve the amount with their mobile money PIN.
The payment settles, the subscription activates and your backend receives a signed webhook.
Connected to leading Tanzanian aggregators so one integration reaches every major network.
Authenticate with your project's API key and secret, then collect payments, check status and verify subscription access.
GET /api/v1/packagesPOST /api/v1/payments/payGET /api/v1/payments/{reference}GET /api/v1/subscriptions/statusGET /api/v1/payment-instructionscurl -X POST "https://your-host/api/v1/payments/pay" \
-H "Content-Type: application/json" \
-d '{
"apiKey": "<API_KEY>",
"apiSecret": "<API_SECRET>",
"package_code": "BASIC",
"customer_id": "CUST-1001",
"phone_number": "2557XXXXXXXX"
}'
# → { "status": "pending", "reference": "PAY-XXXXXXXX" }
Staff sign in through IdentityFBC. No separate passwords to leak.
Every project has its own key and secret, so one app can never act for another.
Inbound and outbound webhooks are verified with HMAC signatures and timestamps.
Every transaction, webhook delivery and status poll is logged and searchable.
Sign in with your FBC account to open your workspace.
Loading…