Marketplaces
Collect for merchants and release when conditions are met
Handle customer payment, platform commission, merchant settlement, and delayed release without scattering state across internal services.
Built for African platforms that move real money
Payment collection, escrow control, and payout release in one operational layer.
Zanga is for marketplaces, commerce systems, fintech products, and group-finance flows that need more than a payment button. It gives operators and developers one system for payment intents, asynchronous confirmation, reconciliation, and controlled release of funds.
Intent-firstCapture payer, payee, reference, and gateway context before money moves.
Operator-visibleKeep payment, webhook, escrow, and payout states traceable for support teams.
Partner-readyDesigned for mobile money, platform settlement, and live onboarding controls.
Control surfaceOperational model
Payment intent
Validate internal references, payer identity, payee destination, and idempotency before a collection request leaves your platform.
Asynchronous confirmation
Wait for customer approval and gateway callbacks without losing state or support visibility.
Escrow and release
Hold, split, or release value according to the product flow instead of forcing immediate settlement everywhere.
POST /v1/payments/intent
{
"externalRef": "market_order_2049",
"payerId": "customer_78",
"payeeId": "merchant_12",
"gateway": "mtn_momo",
"amountNgwe": "25000",
"idempotencyKey": "uuid-v5-key"
}How Zanga fits
Where product teams stop guessing and start controlling the money flow.
Your application keeps customer experience and business rules. Zanga keeps the financial state machine coherent from payment intent to webhook confirmation, escrow handling, and payout release.
1
Platform creates the intent
The partner backend sends customer, merchant, amount, gateway, and internal reference context into one request.
2
Zanga records and validates state
Idempotency, split values, escrow assumptions, and payout prerequisites are applied before downstream execution.
3
External rails confirm payment
Mobile-money or partner rails return asynchronous approval outcomes without forcing your product to stitch together partial truths.
4
Operators receive evidence
Webhook notifications and platform-visible states let support, finance, and engineering teams reconcile completion and exceptions.
Who this is for
Use cases that need control, not slogans.
Zanga is useful where a product has to manage how funds enter, wait, split, and leave the system while staying understandable to operations and compliance teams.
Commerce systems
Keep orders, settlements, and support references aligned
Map each financial action back to the order or invoice that produced it so finance and support teams can trace issues quickly.
Fintech operators
Control payout and wallet-adjacent workflows
Use one operational model for incoming collection, exception handling, and money-out orchestration instead of patching separate systems together.
Group finance
Track pooled funds with clearer release and audit posture
Support stokvel, chama, campaign, and collective-contribution products that need visible rules around holding and disbursing value.
Operational posture
Controls that matter once payment traffic is real.
The value of the platform is not a generic security claim. It is the ability to preserve payment state, environment separation, and operator evidence when real transactions and support incidents start happening.
Environment separation
Keep sandbox and live credentials, callbacks, webhook endpoints, and traffic assumptions distinct.
Webhook evidence
Return observable completion and failure events so integrations do not rely on blind polling or customer screenshots.
Escrow-aware state
Model funds that should wait for delivery, approval, or dispute resolution before release.
Payout readiness
Make money-out routing part of the same control surface instead of a disconnected back-office step.
Next step
Start with the developer surface, then move toward live review.
Read the docs, register a platform, configure webhooks, and test payment-intent flows before asking Zanga to carry production traffic.