Traffic e-Ticketing & Enforcement Software for Nigerian States

Offence capture from officers and cameras, a ticket ledger that stands up to challenge, online fine payment, dispute and adjudication, court integration — and the lawful-basis and data-minimisation design that keeps an enforcement programme defensible.

Chat With Us on WhatsApp Get a Quote
By Musskart Technology Editorial Team Published: Updated: Reviewed by Musskart Senior Engineers

250+

Projects Delivered Since 2020

Nigerian

Company, RC-Registered

NDPA

Lawful-Basis Design

B2G

Built For State Agencies

Government enquiries: call +234 813 168 6721 or message us to arrange a demo.

Message Us Now

The Scale Nigerian States Are Now Operating At

Automated traffic enforcement in Nigeria stopped being a pilot. In May 2026 the Lagos State Commissioner for Transportation, Oluwaseun Osiyemi, was reported as saying the state had recorded 737,340 traffic violations in 2025 through its Automated Number Plate Recognition camera system. Published fine levels give a sense of what sits behind that number — ₦20,000 for running a red light and ₦50,000 for speeding.

Other states are moving the same way. Lagos expanded its intelligent transport and e-police camera sites through 2025. The FCT's Directorate of Road Traffic Services began e-ticketing with central booking in February 2025. Gombe established GOSTEC in law in 2025. The direction of travel is settled; what differs between states is whether the software behind it can survive scrutiny.

The uncomfortable part, stated up front. At that volume, two things break systems: tickets that cannot be proved when challenged, and a public that experiences enforcement as surveillance rather than road safety. Both are software and governance problems before they are political ones. A platform that cannot produce the evidence behind ticket number 412,338 from eighteen months ago, or that retains every plate read of every uninvolved vehicle indefinitely, is a liability waiting for a court date. We build for the opposite outcome.

The Offence Ledger Is the Whole System

Everything else is an interface onto one thing: an immutable record of what allegedly happened, when, where, to which vehicle, on what authority, and with what evidence attached. Get the ledger right and disputes resolve themselves. Get it wrong and every contested ticket becomes a manual investigation.

Designing for Lawful Basis, Not Just for Collection

ANPR draws sustained and legitimate criticism in Nigeria and everywhere else it is deployed, because a camera network that reads every plate is reading mostly innocent people. Under the Nigeria Data Protection Act, a state agency running one is a data controller of major importance processing personal data at scale, and it needs to be able to answer for it. We build the answers into the product.

  • Documented lawful basis per processing activity, tied to the specific statutory function the agency is exercising — not a blanket "public interest" assertion applied to everything.
  • Data minimisation on non-offence reads. Plate reads that do not correspond to a detected offence are retained only for the short window needed for system integrity and then purged automatically, with the purge job itself logged and auditable. This is the single most important control, and the one most systems skip.
  • Purpose limitation enforced in code. Enforcement data is not browsable for general intelligence. Every lookup requires a stated purpose and a case reference, and every lookup is logged against the officer who made it.
  • Evidence retention tied to the case lifecycle, with disposal once the appeal window closes and the matter is settled, rather than indefinite accumulation.
  • A DPIA delivered as part of the project, because a Data Protection Impact Assessment is expected for high-risk processing of this kind and should exist before the first camera goes live, not after the first complaint.
  • Published transparency — signage standards, a public privacy notice, and periodic statistics on tickets issued, disputed and upheld.

This is not decoration. It is the difference between an enforcement programme that survives a legal challenge and one that gets suspended. Our NDPA compliance work is a standing part of the firm, and for this class of system we treat it as core scope rather than an add-on.

Command, Control and the Numbers Leadership Asks For

Live operations view

Tickets issued today by corridor, camera and officer; camera health and uptime; verification queue depth; the choke points forming right now.

Revenue and collection

Issued against paid against written off, ageing of unpaid tickets, collection rate by offence type and by corridor, and reconciliation against the state's receipts. Collection rate is the number that exposes whether an enforcement programme is working or just generating paper.

Integrity monitoring

Cancellation and downgrade rates by officer and supervisor, unusual patterns in lookups, tickets voided after payment, evidence uploaded late. Enforcement systems attract internal abuse; the controls have to watch the operators too.

Road safety outcomes

Offence density by location over time, repeat-offender distribution, and whether violations at an enforced junction are actually falling. If they are not, the programme is a revenue exercise, and leadership should be able to see that from the dashboard rather than from a newspaper.

Delivery, Commercials and What We Do Not Do

We build and operate the software layer. We do not supply cameras, gantries or roadside hardware, and we do not take a position on where they should be sited — that is the agency's policy decision and its procurement. We integrate with whatever estate you run, which keeps the hardware market competitive and stops you being tied to one supplier's ecosystem.

Phase 1 — Core ledger and officer app (10–14 weeks)

Offence schedule configured to your state's regulations, field application, ticket issuance, notice delivery, payment and reconciliation. Deployable with no cameras at all, which is how most agencies should start.

Phase 2 — Public portal and adjudication (8–12 weeks)

Ticket lookup and payment, dispute submission, adjudication workflow, decisions with reasons, and the court bundle export.

Phase 3 — Camera integration (12–20 weeks)

ANPR ingestion, human verification workflow, evidence handling, the DPIA and the retention automation. Only after the ledger and the dispute path are proven in production.

On commercials, states typically use a capital build with annual support, a managed service, or a revenue-share model. We will work with any of them, with one caveat we state openly: a pure revenue-share arrangement creates a direct financial incentive to issue more tickets, which is exactly the criticism these programmes attract. If your state prefers that model, we recommend pairing it with a fixed cap, published statistics and independent audit of the cancellation and dispute rates. We are comfortable saying that before the contract rather than after the newspaper story.

Musskart Technology Limited is a registered Nigerian software company in Asaba with an Abuja office and 250+ projects delivered since 2020. We have not previously delivered a statewide traffic enforcement platform and will not claim otherwise; what we bring is the payment, reconciliation, mobile field-application and data-protection engineering these systems are made of, priced in naira and maintained in the same time zone as the people using it. We respond to tenders and expressions of interest.

Related Musskart Pages

Part of a wider GovTech programme?

Enforcement shares its identity, payment and reporting layers with the rest of state government. See revenue collection and IGR software, citizen services and e-governance portals, and land administration and GIS.

Frequently Asked Questions

No. We build and operate the software layer and integrate with whatever camera estate your agency already runs or separately procures. We deliberately stay out of hardware supply for two reasons. First, it keeps your camera procurement competitive instead of tying you to one supplier's closed ecosystem. Second, software and hardware fail differently and should be accountable separately. The platform ingests automatic number plate recognition events over standard interfaces, applies confidence thresholds, and routes low-confidence reads to human verification. If you are starting out, our recommendation is usually to deploy the officer-issued ticketing layer first with no cameras at all, prove the ledger and the dispute process in production, and add camera intake as a later phase.

Several controls stacked together. No ticket is created from an unverified machine read: any automatic number plate recognition event below the confidence threshold goes to a human who confirms the plate against the image first. Plate to registered keeper lookups run against the vehicle registration data your agency is authorised to access, and where the lookup fails or returns stale details the ticket holds in a pending state rather than being served on the wrong person. Every ticket carries its evidence with integrity hashes recorded at capture. Tickets are immutable once written, so amendments and cancellations are separate linked entries with a named officer and a stated reason, which means the pattern of cancellations is itself visible to supervisors and auditors.

Design choices made in code rather than promises made in a policy document. The most important is data minimisation on non-offence reads: plate reads that do not correspond to a detected offence are retained only for the short window needed for system integrity and then purged automatically, with the purge job logged and auditable. Beyond that, purpose limitation is enforced rather than stated, so enforcement data is not browsable for general intelligence and every lookup requires a stated purpose and case reference and is logged against the officer. Evidence retention is tied to the case lifecycle with disposal once appeals close. We also deliver a Data Protection Impact Assessment as part of the project, before cameras go live rather than after the first complaint.

Yes, and a credible dispute route is not optional. A system without one is one bad case away from an injunction. Citizens can look up a ticket by plate or reference on a public page, see the offence, the location and time, and a summary of the evidence, then submit a challenge online with their grounds and any supporting documents. Challenges go to an adjudication queue handled by officers who did not issue the ticket, and every decision carries written reasons. Unresolved matters escalate to the mobile court with the case bundle exported automatically, and the court outcome feeds back into the ledger. Dispute and upheld rates appear on the leadership dashboard, because they are the clearest early signal that something in the enforcement chain is wrong.

Payment runs through the state's own approved collection channels, not through us. We never hold public funds. The platform issues notices by SMS and email with a reference, exposes a public lookup and payment page, and reconciles every receipt against the originating ticket so that each naira collected maps to a specific offence record and each ticket shows its current payment state. Early-payment discounts, instalment arrangements and escalation rules for non-payment are configuration your agency controls rather than code we rewrite. The collection dashboard reports issued against paid against written off, with ageing on unpaid tickets and collection rate broken down by offence type and corridor.

The core ledger and officer field application phase takes ten to fourteen weeks, the public portal and adjudication phase eight to twelve weeks, and camera integration a further twelve to twenty weeks once the earlier phases are proven. States typically procure through a capital build with annual support, a managed service agreement, or a revenue-share model. We work with all three, with one caveat we raise before the contract rather than after: a pure revenue-share arrangement creates a direct financial incentive to issue more tickets, which is precisely the criticism these programmes attract. If your state prefers that model, pair it with a fixed cap, published enforcement statistics and independent audit of cancellation and dispute rates. We respond to formal tenders and expressions of interest with a priced breakdown.

Arrange a Government Demo

We work with state transport ministries, traffic management authorities and road traffic agencies. Tell us your offence schedule, your current process and whether cameras are already in place, and we will arrange a demo and a phased proposal.

Chat on WhatsApp Get a Quote Call +234 813 168 6721 See Our Full Pricing
WhatsApp