Category comparison
Zetu vs payment gateways
How to read this page
This compares categories, not products. The names below are recognizable examples of the category, described in terms that are not in dispute. You will not find a feature-by-feature table against a named product here, because such a table is accurate for about a quarter — and a comparison that is quietly out of date is worse than none, particularly on a site arguing that you should not trust numbers you cannot verify. For anything specific about another product, check their documentation.
The category
Who is in this category
Mobile money
M-PESA, MTN MoMo, Airtel Money, GCash and comparable wallets, market by market.
Pesapal
Payment processing across cards and mobile money in East Africa.
IntaSend
Payment collection and disbursement APIs.
Paystack
Payment processing across African markets.
Flutterwave
Payment infrastructure across multiple African countries.
Card networks and banks
The underlying rails that carry card and account-to-account payments.
Credit where due
What payment providers do genuinely well
Moving money reliably, at scale, under regulatory obligations most software companies would struggle to meet. Reach across cards, mobile money, bank rails and wallets. Settlement, fraud controls, security, dispute handling with networks, and APIs that make collection straightforward. This is difficult infrastructure and Zetu depends on it.
The limit
What a provider cannot tell you
A provider's job ends when the money has moved. It can tell you a transaction succeeded, its amount, its time, and whatever the rail carried about the sender. It cannot tell you whose obligation that money was for, whether it settles one obligation or eighteen, what balance it leaves behind, whether it changes an account's standing, whether it is a duplicate of a payment that arrived yesterday under a different receipt number, or what somebody should do about the shortfall. Those questions require a model of what was owed, and a provider has no reason to hold one.
The difference
What Zetu adds
The interpretation layer. Obligations to match against, payer identity built from history, allocation across one or many obligations, suspense for money that cannot be attributed, comparison against independent sources where they exist, standing, entitlements and a collections workflow. Zetu takes the provider's transaction and turns it into a settled obligation, a changed balance and a next action.
When a payment provider is all you need
- You take one-off payments with no ongoing obligation behind them.
- Every payment carries a reference your systems can act on automatically.
- You do not need to know who has not paid, only who has.
- There is no follow-up, no standing, and no consequence to non-payment.
Retail and one-off commerce genuinely fit this. Recurring relationships almost never do — which is the reason this site exists.
When you need to know what the money meant
- You need to know who has not paid, not just who has.
- Payments arrive without references, or with references that identify nobody.
- One payment settles several obligations, or several settle one.
- Somebody pays on behalf of somebody else, routinely.
- You hold money you cannot attribute and it is growing.
- A missing callback means a customer is suspended while holding a confirmation message.
- Payment status has to drive access, privileges or service.
Coexisting
Zetu is not an alternative to your payment provider and never will be. Bring the providers and bank relationships you already have — Zetu sits behind them. Changing provider should be a configuration change, not a migration, and that is only true because Zetu keeps its own financial model rather than inheriting one from a rail.
Questions
Common questions
Does Zetu process payments or hold funds?
No. Money moves through your existing providers into your own accounts and stays there. Zetu records obligations, reconciles the payments that arrive, and maintains the resulting balances and standing. It performs no regulated financial activity.
Our provider gives us a reconciliation report. Isn't that enough?
A provider reconciliation tells you that its records agree with its settlement to you — an important check, and a different one. It cannot reconcile against what you were owed, because it does not know. The gap between 'the provider paid us what it collected' and 'the money we collected settles the obligations we expected' is precisely where unallocated cash accumulates.
Something on this page look wrong or out of date? Tell us — including if you work on one of the products named above. We would rather correct it than defend it.
Other comparisons
- Zetu vs subscription billingWhere plan-and-card billing ends and receivables operations begin.
- Zetu vs accounting softwareRecording financial history versus operating the relationship.
- Zetu vs membership softwareMember databases versus financial control over member money.
- Why ZetuThe full differentiation argument.
- Recurring billing vs recurring receivablesThe distinction underneath all four comparisons.
Still deciding?
Tell us how money is expected and how it actually arrives. If another category fits you better, we will say so.