One platform. Four subdomains.
Every user group enters through its own subdomain — the data is the same, in real time.
In short
TIS has four access points on one platform: app.tis.md — the passenger app (QR scan, instant payment, history, MEV receipts); station.tis.md — the station ticket desk (sales, cash/card, cancellations, shift report); admin.tis.md — the operator panel (routes and tariffs, vehicles, reports, audit); api.tis.md — the integration platform (REST API, webhooks, OAuth2, sandbox). Modules talk over an internal API, and fiscalisation applies automatically regardless of the sales channel.
Four actors. One ecosystem.
Passengers, cashiers, carriers and integrators — each with their own access point and the same real-time data.
Passengers
Scan transport QR, pay by card or MIA, get your ticket instantly. No more lines at the counter.
Stations & cashiers
Sell tickets, take cash or card, issue MEV receipts, handle voids and shift reports — all in one panel.
Carriers
Manage vehicles, routes, fares, schedules, drivers and reports. See revenue and occupancy in real time.
Integrators
REST API for ERP, accounting systems and external apps. Webhooks, OAuth2 and a demo sandbox for technical partners.
One platform. Four subdomains.
Each user group signs in through its own subdomain. The data is the same, in real time, no matter where you connect from.
Modules talk through an internal API. Fiscalization is applied automatically, on any sales channel.
Four access points.
Each user group enters TIS through its own subdomain, with a dedicated interface and permissions.
Passenger app
QR scanning, ticket payment, trip history, MEV receipts, departure notifications. One app for every route in the network.
Station counter
The cashier panel — fast ticket sales, route selection, cash or card collection, voids, automatic MEV receipt on every transaction.
Carrier dashboard
The control center: vehicles, routes, fares, scheduled trips, QR generation, user management, financial and audit reports.
Integration platform
Public docs, endpoints for carriers, ERPs and external apps. Webhooks, OAuth2 authentication, demo sandbox.
The main flow: from QR to the electronic receipt
One thread: vehicle QR → vehicle identification → active ride → payment → ticket issued → MEV receipt → validation. Every step feeds the same data, visible to every role in real time.
Interface and permissions per role
Each subdomain has its own interface and permissions: the passenger sees their tickets, the cashier the sales panel, the operator the control centre, the integrator the docs and endpoints.
TIS, at a glance
- app.tis.md
- Passengers — QR scan, instant payment, history, MEV receipts (iOS · Android · Web)
- station.tis.md
- Station desk — sales, cash/card, cancellations, shift report (Web · POS)
- admin.tis.md
- Operator panel — routes and tariffs, vehicles, reports, audit (Web)
- api.tis.md
- Integration — REST API, webhooks, sandbox, docs (REST · OAuth2)
- Data
- The same, in real time, across all subdomains
Frequently asked questions
Why separate subdomains?
Each user group gets its own interface and permissions, but the data is the same, in real time, from any access point.
How do the modules communicate?
Over an internal API; fiscalisation applies automatically, regardless of the sales channel.
Transport digitalization starts here.
Schedule a 30-minute demo. We walk through the full flow on your data, no obligations.