Built by TukiTech · East Africa
Lipachap routes mobile money collections and disbursements through a single Selcom-compatible API. Connect Vikoba, marketplaces, billing systems, or custom backends — with sandbox keys in seconds and production-grade signed webhooks when you go live.
Platform
Lipachap sits between your application and mobile money operators. Your backend signs API requests, Lipachap talks to the right network route, and your webhook endpoint receives the final payment outcome — so you never block user flows polling for status.
Create a unique transid, sign the JSON body, and POST to Lipachap from your server — never from a mobile app or browser.
Validates digest auth, resolves MSISDN to the correct MNO route, queues the transaction, and tracks fees and references.
Customer approves STK push, USSD, or wallet debit depending on operator and transaction type.
Receive HMAC-signed JSON with SUCCESS or FAILED. Update orders, contributions, or ledger entries idempotently.
Payment operations
POST /v1/walletcashin/process
Pull funds from a customer MSISDN into your merchant flow — contributions, checkout payments, wallet top-ups, loan repayments, or invoice settlement.
utilityref for your order or member idreference for support and reconciliationPOST /v1/gateway/cashin
Send funds to a registered mobile money wallet — loan disbursements, vendor payouts, refunds, or withdrawal to customer MSISDN.
providerFee, platformFee, and totalChargedPOST /v1/checkout/status
Look up any transaction by your transid when a webhook is delayed or you need to verify state during support calls.
PENDING, SUCCESS, FAILEDtransid returns existing record (code 101)Coverage
Lipachap detects country and operator from MSISDN prefixes and routes to the configured provider integration. You send a normalized phone number; the gateway handles network label, provider key, and integration endpoint selection.
Sandbox uses mock provider mode for end-to-end testing without live MNO charges.
POST /v1/walletcashin/process
Authorization: GATEWAY <digest>
{
"transid": "TXN-20260531-001",
"amount": 25000,
"msisdn": "255712345678",
"utilityref": "ORDER-8842",
"utilitycode": "VMCASHIN",
"countryCode": "TZ"
}Developers
Lipachap uses Selcom-compatible digest authentication so existing integrations can migrate with minimal changes.
Sign sha256(secret + path + rawBody), send JSON over HTTPS, verify webhooks with HMAC — done.
| Host | Keys |
|---|---|
sandbox.api.lipachap.com | TEST |
api.lipachap.com | LIVE (approval required) |
TEST keys are rejected on the live host and vice versa — no accidental production charges during development.
Every callback includes:
X-Gateway-Timestamp — reject stale requestsX-Gateway-Signature — HMAC-SHA256 over {timestamp}.{body}X-Gateway-Nonce — unique per delivery attemptFailed deliveries retry with backoff. Your handler should return HTTP 200 and treat transid idempotently.
Full integration guides and copy-paste examples in five languages:
View all code samples →Use cases
Member contributions and loan repayments via CASHIN; loan disbursements and group payouts via CASHOUT with fee fields passed through. Webhooks drive ledger updates in your core banking or group management system.
Checkout collection at order placement; vendor settlement batches with unique utilityref per seller.
Status API as fallback when customers close the browser before webhook delivery.
Recurring mobile money pulls keyed to subscription ids. Separate sandbox merchant per environment. Dashboard transaction export for finance reconciliation.
Closed-loop e-money balance with top-up, withdraw, P2P send, and pay-merchant flows on the same gateway infrastructure.
Pricing
Deposits and contributions move at face value. Lipachap platform fees apply on withdrawals and disbursements, alongside the mobile network provider tier.
Face value · zero Lipachap platform fee
When a customer pays 10,000 TZS, your transaction records 10,000 TZS. The mobile network may charge the customer its standard MNO fee directly — Lipachap does not add a platform markup on inbound payments.
Provider fee + platform fee
Outbound transfers include a network provider fee (tiered by MNO) and a Lipachap platform fee.
Your integration sends totalCharged so the customer or your float account covers the full debit.
totalCharged = amount + providerFee + platformFee
Sandbox is free. LIVE keys require merchant approval — start in sandbox and request production access from the dashboard.
Security
Per-merchant API keys with TEST/LIVE mode enforcement at the host level. Secrets never appear in client-side code.
Every payment API call requires digest auth tied to the exact request path and raw JSON body.
Transaction log, webhook delivery log, and profit ledger per merchant for operations and support.
Create a sandbox merchant, copy your TEST keys, and make your first signed API call today.