Transparency
What runs today, what uses simulated data, and what waits on partners or regulators.
Authentication, roles & tenant isolation
Row-level security per tenant; demo users receive demo-tenant roles only.
Operator & vehicle onboarding with approvals
Self-entered data is labelled self-reported, never government verified.
Fleet assignment to routes
Only approved vehicles may be assigned; every change is audited.
Idempotent fare ingestion & exception queue
Engine is live; incoming events come from a simulated provider.
Double-entry subledger & daily close
Journals must balance; ledger rows are immutable.
Settlement instructions & four-eyes approval
Approved batches wait for a payout provider — no money moves.
GPS tracking
Positions generated by a labelled simulator until a tracker provider is authorised.
PayFine compliance view
Mock adapter. Real citations require PayFine API access and legal authority.
VECTRA Intelligence assistant
Answers from demo-tenant data only; never takes binding actions.
Passenger route browsing
Demonstration routes; arrival estimates only shown when data exists.
Fare provider (TransPay / O-CITY)
No agreement or API access.
Payment gateways (BlueGate, PowerTranz, BiMPay partners)
Requires merchant/partner agreements and credentials.
Electronic Vehicle Registration lookups
Requires government authorisation.
Legally authorised fine deductions
Not built to execute. Requires legal authority, consent and human approval.
Partner portals, government exports, commercial billing
Next build phase.
Every provider must clear each step before moving from NOT CONNECTED.