Fuel networks do not adopt infrastructure on the strength of a demonstration. They adopt it on the strength of what happens when something goes wrong. This page sets out how LiTr behaves under those conditions.
The most common failure in third-party fuel integrations is duplication: two systems recording the same transaction differently, discovered months later, resolved over years.
LiTr does not maintain a parallel ledger. A redemption is recorded once, and the forecourt, the partner portal and the customer all read the same thing. When your finance team queries a litre, they are looking at what we are looking at.
Connectivity at Zimbabwean forecourts is not guaranteed, so LiTr does not assume it. A redemption can be verified and completed at the forecourt without a live connection, and the record is brought up to date once connectivity returns.
The customer is served. The litre is recorded. The reconciliation is unaffected.
Every redemption is attributable to an identified attendant at an identified station. Volume, fuel type, station, attendant and time are recorded together. Where a question arises about a specific transaction, there is a specific answer.
Partner, forecourt and consumer access are held apart from one another, and each is granted according to the job it serves. Access gained in one place does not carry into another.
LiTr operates under the Cyber and Data Protection Act. We collect what is needed to operate the service, retain it only as long as it is needed, and do not sell it. Our Privacy Policy sets out what we collect and why, and how to exercise your rights over it.
Technical due diligence is a reasonable thing to ask for. This page covers how the platform behaves. Detailed architecture, security and integration documentation is shared with partners under agreement, at the point it becomes useful to them.
Talk to our team about reconciliation, offline resilience, and how LiTr behaves on your own network.
