The operator (legal representative) first registers on the Chiron test environment, shares the credentials with their software, sends 10 test messages, then registers in production. The driver works normally in the app — without logging into Chiron.
Chiron is not a driver app
In Flanders, the operator must send trip data to the central database. Connected software does that for you. The driver does not open the portal during the day — they mainly need to encode vehicle, driver card, start, stop, price and distance correctly.
Who must make the connection?
The legal representative of the taxi company. If you are an employed or freelance driver for a company, you usually do not create that company's Chiron access yourself.
What to prepare
- itsme or Belgian eID
- Access as legal representative of the company
- KBO/BCE number and official company name
- Professional company email and phone number
- Name of your Chiron-connected software (or IT partner)
The 3 official steps
The Flemish procedure always follows this order — test first, then production.
- 1Register on the test environment, copy the credentials, share them with your software or IT partner.
- 2Send 10 test messages: 5 departures (start) and 5 arrivals (stop) — in practice, trips started and closed in the software.
- 3Register in production, copy the new credentials (different from test) and share them to activate real trip sending.
With TaxiGer
TaxiGer simplifies this connection
For the operator: onboarding and Chiron setup without technical complexity. For drivers: day-to-day use in the app — trips go to Chiron automatically.
Who does what?
Legal representative
Registration on test and production portals, retrieval of technical credentials.
Taxi software / IT partner
Technical setup, sending test messages and real trips to Chiron.
Driver
Use the software correctly: right account, right vehicle, start and stop at the right time. No login to the Chiron portal.
Chiron ≠ licence models
Connecting Chiron is not the same as attaching model route sheets and transport documents to the Centaurus file. Those are two separate tracks. Official info is on Vlaanderen.be.
Frequently asked questions
- Who must create the company's Chiron access?
- The operator's legal representative. An employed or freelance driver for a company usually does not.
- Must you start with the test environment?
- Yes. Registration starts on the test (acceptance) environment, before real trips in production.
- How many test messages must you send?
- 10 messages: 5 departures (start) and 5 arrivals (stop).
- Are test and production credentials the same?
- No. After tests you must register in production and share new credentials.
- Must the driver log into Chiron during the shift?
- No. Their role is to use the software correctly; transmission happens in the background.
- Can you set up Chiron alone without being technical?
- Portal registration is done with itsme or eID. Technical setup (OAuth, messages) is usually handled by the software or IT partner.
Ready to connect to Chiron?
Use TaxiGer to make this connection easier: guided onboarding, then setup with our team.