Skip to content
Techart Ticketing

Techart Ticketing

Ticketing for bus companies, not another booking site

Every operator gets its own website, its own counters, its own fares and its own payment account. Passengers book from the company they already know — and the company keeps the customer, the money and the timetable.

Already with us? Sign in.

A screen from the product

What it does

Everything below is a screen in the product, not a plan.

One seat, sold once

A clerk at the bus park and a passenger on a phone compete for the same seat. The hold is a countdown on the server, not a number in the browser that a reload resets — so a seat is released when it really expires, and never sold twice.

  • Counter and web share one inventory
  • Holds expire server-side
  • Sold-out seats are shown, not hidden

The seat map, mid-booking

A seat plan that matches the bus

Sleepers, berths above seats, a driver, a door, a toilet, two decks — drawn as the floor really is, so a passenger recognises the bus they are about to board and a clerk is looking at the same plan on the same screen.

  • Per-vehicle floor plans
  • Seat types with their own fares
  • The seat sold is the seat printed

A floor plan in the fleet screen

Its own website, on its own domain

Its colours, its logo, its routes, its photographs, its pages. Passengers never see this page, and never see another operator. Changing how it looks is a setting, not a deployment.

  • A hostname per company
  • Theme colours without a rebuild
  • Its own pages, places and offers

An operator’s own home page

The money goes to the company

Each company configures its own eSewa or Khalti merchant account. Nothing passes through us. What each counter owes is worked out from what it sold, with the figures and the rounding shown.

  • Per-company merchant credentials
  • Counter settlement, itemised
  • Refunds against the terms that were sold

The settlement report

Who uses it

The counter screen

The counter

The clerk at the bus park, selling to somebody standing in front of them.

  • Sell a seat and take cash in one screen
  • A receipt on the till roll, a ticket on A4
  • Passenger papers captured where the route needs them
  • What the counter owes, worked out for it

The reports screen

The office

Whoever runs the routes, the fares and the fleet, and answers for the numbers.

  • Routes, stops, schedules and departures
  • Fares by segment, with discounts and policies
  • Cancellations and refunds, with an audit trail
  • Sales and manifests, exportable

What a company gets

Everything below belongs to the company, not to us.

Its own website

Its own website

On its own domain, with its own colours, logo, routes and photographs.

Counters and online, one timetable

Counters and online, one timetable

The clerk and the website compete for the same seat, and it is sold once.

Its own payment account

Its own payment account

Money goes to the company. Each one configures its own eSewa or Khalti account.

Seat plans that match the bus

Seat plans that match the bus

Sleepers, berths over seats, a driver, a door, a toilet — on one deck or two.

Counter settlement

Counter settlement

What each counter owes, worked out from what it sold, with the rounding shown.

Cross-border journeys

Cross-border journeys

A route that leaves the country asks every passenger for papers before departure.

How a company comes on

  1. 1

    We set the company up

    Its network, its agencies, its counters and the first administrator account.

  2. 2

    Its own data comes across

    Routes, buses, seat plans, fares and past bookings, checked against the old system before anything goes live.

  3. 3

    It starts selling

    The company runs itself from then on. We keep the platform up and stay out of its timetable.

Run a bus company?

Tell us about your routes and your counters, and we will show you what it looks like with your own buses in it. No obligation, and nothing to install.

Your team, or a bus