Payment transaction audit logs for a Johannesburg store in 2026

The verdict in three sentences

Without an immutable log, you cannot arbitrate a dispute: a customer swears they paid, your database says no, and with no trace you lose either the money or the customer. An append-only log cuts resolution time from 2h to 8 min and satisfies the OHADA requirement of 10-year retention. The decision: a convenient but falsifiable mutable table, or an append-only, timestamped, non-editable log — the latter wins every dispute.

Append-only vs mutable table

A classic table where you update a transaction's status is convenient but erases history: you cannot prove the order of events. An append-only log records each change as a new row, never an UPDATE. You reconstruct state by replay.

Each entry must contain: the provider's transaction id, a traceable financial reference (MTN MoMo Cameroon requires it), gross amount, fees, status, server timestamp, and the raw payload received. That financial reference is what lets you reopen a case with the operator.

Retention and storage cost

Many hesitate between keeping 12 or 24 months. The legal reality decides: OHADA mandates 10 years for accounting records. Good news, the cost is negligible.

At ~3,000 FCFA/year for 100,000 transactions, there is no economic reason to truncate retention below the legal requirement. Archive old logs in cold storage (object, compressed) to cut the cost further.

Mini case study

Marguerite runs a fashion store in Johannesburg, ~300 mobile money tx/month. Without a log, each dispute ("I paid, never got my order") took her 2h of searching emails and screenshots, at ~4 disputes/month, i.e. 8h/month. At 3,000 FCFA/h loaded: 24,000 FCFA/month of wasted time, and sometimes a wrongful refund for lack of evidence.

After setting up an append-only log with financial reference and raw payload, each dispute is settled in 8 min by pulling the exact row. Monthly time: from 8h to ~0.5h, saving ~22,500 FCFA/month, plus the end of unjustified refunds. Annual storage cost: ~3,000 FCFA. The benefit/cost ratio exceeds 90 to 1.

FAQ

Does an append-only log replace my orders database? No, it complements it. Your operational database serves the day-to-day (current status, fast queries); the log is the immutable source of truth for audit, disputes and compliance. The two coexist.

How do I guarantee immutability if it is just a SQL table? Remove UPDATE/DELETE rights from the app account, allow only INSERT, and add a chained hash (each row embeds the previous row's hash) to detect any tampering. On object storage, enable object-lock/WORM.

What exactly should I log for a dispute? At minimum: the provider's financial reference, gross amount and fees, status at each transition, server timestamp, and the raw webhook payload. MTN MoMo Cameroon requires a traceable financial reference — it is your key piece against the operator.

Isn't 10 years of retention too expensive? No: at ~1.2 KB per log, 100,000 tx/year cost ~3,000 FCFA/year of storage, i.e. ~30,000 FCFA over 10 years. That is marginal against a single mis-arbitrated dispute at 25,000 FCFA.

How do I become a Kolonell referral partner? Introduce us to a merchant who needs an auditable payment system: on signature you earn 12% e-commerce, 10% marketplace, 8% institutional and 15% + 5% recurring on a showcase site. An 8,000,000 FCFA institutional project earns you 640,000 FCFA.

Let's talk about your project. We design your immutable audit log, OHADA-compliant and dispute-ready. WhatsApp +221 77 596 93 33.