Chiron registration step by step

Step 1 — Open the official Chiron page

Start with the official Flemish government page about Chiron:

Rittendatabank Chiron — vlaanderen.be

This page explains that a taxi service operator must send trip information to Chiron. It also provides links to the test environment, production, the startersgids, technical documentation and error codes.

Step 2 — Register on the test environment

On the official page, click the test environment link, or open directly:

Chiron test / acceptance portal — chiron-acc.vlaanderen.be

That is where you start. The Flemish government states that before sending real trips, you must first register on the test environment, copy the access credentials shown after registration, then pass them to your IT provider or to the publisher of your Chiron-connected software.

Step 3 — Sign in with itsme or eID

On the Chiron test portal, click Aanmelden. You can normally sign in with a Belgian digital key:

• itsme (often the simplest);
• eID with card reader;
• another method offered by the portal.

To understand or activate itsme: official help — sign in via itsme. The Flemish government explains that itsme is a Belgian application for secure online identification, with a smartphone, the itsme app, and either a Belgian eID or a compatible bank account.

If you use itsme, keep your phone nearby: you will receive a validation request in the app to confirm before continuing.

The official Startersgids guide states that access can only be requested by a person legally linked to the company in the KBO/BCE, via eID or itsme.

Step 4 — Select your company

After signing in, choose the taxi company concerned. You must be legal representative or have the necessary rights to act on behalf of that company.

If your company does not appear, or access is denied, the problem often comes from rights linked to your company in the BCE/KBO — not from the taxi software. In that case, check your administrative data with your accountant before forcing registration.

Also check the official company name, BCE/KBO number, email and contact phone. Use a company email address — not a driver's personal address who might leave the company.

Step 5 — Choose the authentication method

Chiron offers several technical methods so the publisher of your Chiron-connected software can establish the connection:

Method 1 — Client ID and Secret

This is the easiest method to understand. Chiron provides a Client ID and a Secret. These two values then allow requesting an access token and sending trips to Chiron from your connected software.

Method 2 — Public key / JWT (JWKS)

A more technical method, based on a key pair (public key passed to Chiron, private key kept by the operator or software publisher). More secure, but requires advanced configuration — to be handled with your IT provider or the publisher of your Chiron-connected software.

For an operator who wants to connect specialised software, the key point is not to attempt this part alone if you are not technical: ask for support from your provider.

Step 6 — Copy Chiron test credentials

After registration is validated, Chiron displays technical access credentials. Copy them immediately — depending on the method chosen: Client ID, Secret, JWKS data or public key.

The Flemish government states that these credentials must be passed to your IT provider or to the publisher of your Chiron-connected software to link your test environment to the official platform.

Important: do not publish these credentials, share them in a WhatsApp group or send them to just anyone. They grant access to the technical connection between your company and Chiron.

Hello,

Here are the Chiron test credentials for our company.

Company: [name]
BCE/KBO: [number]
Environment: test / acceptance
Client ID: [value]
Secret: [value]
Chiron email: [address]
Phone: [number]

Please connect our account to Chiron.

Step 7 — Configure the Chiron connection in test

Once credentials are received, your Chiron-connected software — or your IT provider — configures the link between your space and the test environment. At this stage, real trips do not yet go to production: first the connection is verified and messages sent are accepted by Chiron.

The official technical documentation details the OAuth API, mandatory fields, trip statuses (departure, arrival), vehicle, driver, price, distance and GPS data.

Step 8 — Send the 10 test messages

The Flemish government then asks you to send 10 test messages via the Chiron test environment: 5 departures and 5 arrivals. The official page explicitly states: « Verstuur 10 testberichten via de Chiron-testomgeving: 5 vertrekken (start) en 5 aankomsten (stop). »

In Chiron-connected software, this corresponds to several test trips where the driver starts the trip, ends it, and the application transmits information to the official platform.

Before launching tests, check that each driver has a driver card number, each vehicle a correct licence plate, the right driver uses the right vehicle, and price, distance and GPS are recorded correctly.

Important information sent to Chiron includes: trip number, BCE/KBO, company name, licence plate, driver card, departure and arrival times and GPS points, distance and price.

Step 9 — Fix any errors

If Chiron rejects a message, it is not necessarily serious: information is missing or a format is incorrect. Common examples:

• missing licence plate or driver card;
• missing departure time;
• arrival sent before departure;
• missing distance or price;
• incorrect GPS coordinates;
• same trip sent twice with different data.

Consult the official Foutenlijst (error codes). The publisher of your Chiron-connected software or your IT contact analyses the error, corrects the data, then resends the message.

Step 10 — Move to production

When tests are validated, return to the official Chiron page, then open the production portal:

Chiron production portal — chiron.vlaanderen.be

The Flemish government states that after testing, the operator must register on Chiron production, copy the new access credentials, then pass them to their IT provider or to the publisher of their Chiron-connected software to link the real environment.

Note: test and production credentials are not the same. You must pass the new production credentials the same way as in test.

Step 11 — Activate Chiron in production

When your IT provider or the publisher of your Chiron-connected software receives production credentials, real transmission can be activated. From that point:

1. the driver works normally in their trip management application;
2. Chiron-connected software prepares and sends the required messages;
3. if an error returns, it is handled technically or administratively.

The driver must not log in to the Chiron portal during the day. Their role: use their own account, the right vehicle, start and end the trip at the right time, check the final price, and report any error to the operator.

FAQ

Official sources

• Flemish government — Rittendatabank Chiron
• Chiron Startersgids r3.0.3
• Chiron Technische handleiding r3.0
• Chiron Foutenlijst r3.0.1 — error codes
• Flemish government — Sign in via itsme