Traxease is the layer underneath the sale — the storefront, the checkout, the wallet, the ledger and the payout — so that selling on the internet in Nigeria can mean running a business rather than managing a chat thread.
Where this came from
A seller with good products, real customers and no business underneath any of it. The order lives in a chat. The payment is a screenshot. The record is memory. It works right up until it does not, and then it costs the seller the customer.
Amaka · customer
How the order arrives today
Searchable: no. Countable: no. Provable: no.
Order TRX-4192
The same evening, on Traxease
Searchable: yes. Countable: yes. Provable: yes.
None of that is sophisticated. It is just the ordinary machinery of a shop, and it is exactly what nobody had built for the way people here actually sell.
What we believe
A seller should never have to trust us to know where their money is. Not because we would misuse it, but because a business built on trusting a platform is a business with a single point of failure that its owner cannot inspect. So we made the money legible. Every amount is a whole number of kobo. Every movement writes one permanent row. Every night a job re-adds every row for every wallet on the platform and fails loudly if a single kobo disagrees. You are not asked to believe us. You are shown the arithmetic.
Non-negotiables
Every one of these makes something slower to build. All five are the reason the money side of this platform can be explained line by line instead of asserted.
01 / THE MONEY
Every amount on the platform — a price, a delivery fee, a commission, a payout — is a whole number of kobo. There is no floating-point arithmetic anywhere in the money path, because floats do not add up: a half-kobo of rounding drift is invisible on one order and unexplainable across ten thousand.
One shared Money type. No float ever enters or leaves it.
02 / THE RECORD
Every movement of money appends one row carrying what moved, why, and the balance that followed it. Nothing is edited. Nothing is deleted. A correction is a new row, not a quiet amendment of an old one — so the history of your wallet always reconstructs to the number you are looking at today.
Row-locked, idempotency-keyed, inside a single transaction.
03 / THE BOUNDARY
Isolation is not a filter a developer has to remember to write. It is applied at the database layer to every query the application can make, so a query that forgot to scope itself simply returns nothing. Another vendor cannot reach your products, your orders or your customers — not by accident, and not on purpose.
Enforced structurally, covered by tests that try to break it.
04 / THE PROTECTION
A card sale lands in your wallet immediately as pending — already yours, already counted, simply not spendable until the customer has what they paid for. Mark it delivered and it frees at once. Forget to, and it frees itself after seven days. A forgotten order never sits on your cash.
Seven days, set by the platform, never per-order.
05 / THE DEVICE
Not a desktop app that survives being made narrow. Adding a product, fulfilling an order, checking what sold and moving money to your bank are all designed first for a phone held in one hand on a connection that comes and goes — because that is where this work actually happens.
Designed at 360px, then allowed to grow.
The specifics
Not projections and not averages. These are the constants the platform actually runs on, and every one of them is visible to you inside your own dashboard.
0%
Commission
Taken on withdrawal, after the money is already yours. Nothing is skimmed at checkout, so what a customer pays is what you are owed.
0 days
Escrow window
The longest a delivered-but-unmarked order can hold your money before it releases itself.
₦0
Minimum payout
Low enough that your first week of sales is actually reachable, rather than sitting behind a threshold designed to keep it here.
0
Floats in the money path
Every amount is an integer number of kobo, end to end, from the price you type to the naira that lands in your bank.
How we build
The interesting decisions in a commerce platform are all about what you refuse to make interesting.
Tenant isolation, wallet mutation and payout are covered by tests that actively try to break them — cross-store reads, double-spends, replayed webhooks, failed transfers. The pretty parts of the product can be fixed on a Tuesday. These cannot.
One service that moves money. One library that stores a file. One component that picks an image. A second way to do something is a second thing to keep correct, and the one that is used less is the one that quietly goes wrong.
A payment is confirmed against the processor on our server before an order changes state. A callback that claims success proves nothing on its own, so we never treat one as proof.
Anything non-obvious carries the reason it is that way, in the file where it matters. A team that has to rediscover why a decision was made will eventually undo it.
A nightly job re-checks every wallet against its ledger and exits non-zero on a single kobo of drift. Silent degradation in a money system is worse than an outage — an outage is at least honest.
A half-built feature behind a flag is a promise you have made to yourself. If it is on the site, it works in the app, on a phone, on a bad connection.
Where we are
Naira first, not converted from dollars. Pay-on-delivery as a first-class checkout rather than a compromise, because a lot of the country still buys that way and pretending otherwise loses the sale. Delivery zones a seller defines themselves, because nobody in Lagos should be pricing a drop in Nsukka. Receipts that look like receipts. This is not a global platform with a Nigeria setting — it is a Nigerian platform, and the difference shows in the defaults.
Open a store, add one product and send yourself through checkout. It takes about ten minutes and it will tell you more than this page can.
Free to start · No card required
