Work / Commerce & money

Tradia

Commerce, payments and WhatsApp in one system — built for Nigerian payment rails, where the constraint is reconciliation rather than features.

State
In build
Domain
Commerce & money
Our role
Built & run
Still ours
On call
The problem
A merchant runs a storefront on one tool, payments on another, logistics on a third and inventory in a spreadsheet. Meanwhile the buyer starts a new account and re-enters a card at every shop they visit — so nobody accumulates any advantage from having shopped before.
What we built
Storefront, payments, logistics, inventory and live shopping in one system, with a consumer network on top that gives a buyer one identity and one saved payment vault across every merchant on it.
The hard part
Reconciliation, not the feature set. Nigerian payment rails fail differently from one another — a card that times out is not a transfer that silently succeeds, and neither is a wallet debit that reverses hours later. We built settlement assuming a payment either worked or did not, and had to rebuild it around a payment whose state is unknown for a while and then changes.
Where it runs now
In build.
What this means for your project
It is the evidence behind conversational commerce on WhatsApp, payments and fintech integration, and marketplace and MVP builds. If you are selling into a market where the rails are the hard part, we have already met them.

The features were never the hard part. Reconciliation was.

Build something like this?

[email protected]