Core Architecture & Fare Taxonomy
Foundational fare taxonomy, event topology, smart-card schema mapping, and the security boundaries that keep settlement auditable end-to-end.
Public Transit Fare Collection
& Revenue Reconciliation Automation
A production-focused engineering resource for the people who keep transit revenue accurate. Turn raw taps, scans, and vendor settlement files into auditable financial records with deterministic, type-safe Python pipelines.
Built for transit operations teams, revenue analysts, and mobility-tech developers, the guides here cover the full reconciliation lifecycle: smart-card data parsing, fare-rule validation, agency settlement calculation, fraud-pattern detection, GTFS-RT synchronization, batch reconciliation, and compliance reporting.
Every section pairs architectural guidance with runnable, copy-ready code — so you can move from opaque binary dumps and rate-limited APIs to sub-0.1% variance settlement without manual forensic accounting.
What you’ll find here
Three pillars, organized from architecture down to runnable how-to guides. Follow the links into any cluster to reach detailed, code-first walkthroughs.
Fare Data Ingestion & GTFS-RT Sync
Bring heterogeneous AFC telemetry under control — GTFS-RT sync, CSV batch parsing at scale, vendor API extraction, and schema validation pipelines.
Fare Rule Validation & Calculation Engines
Deterministic fare math — transfer windows, discount eligibility, graceful offline fallback, and peak-pricing threshold tuning.