Your website and embedded booking widget aren't bolted onto your reservation system — they're part of it. Here's the architecture, the data flow, and the security that carries a booking into the backend your team runs on.
Your website and booking widget sit on top, the API layer sits in the middle, and the reservation backend your team logs into — with its isolated database — sits underneath. Bookings flow down from the widget into dispatch; live status flows back up to your team.
The public frontend — what riders see
Hosted on your domain. The booking widget is a drop-in script that calls the API directly over HTTPS — it never touches your database.
WIDGET CALLS THE API OVER HTTPSThe bridge between site and backend
Every request is authenticated, role-checked, and validated here. Roles cover Rider, Driver, and Admin (with Admin sub-roles: Owner, Dispatcher, Accountant). The website never reaches the database directly.
VALIDATED · AUTHENTICATED · RATE-LIMITEDYour back office — what your team logs into
Your team logs in at yourcompany.karfisllc.com. The dispatch board updates in real time over a server-sent-events stream — no manual refresh.
One source of truth — never shared with another company
The backend reads and writes to it; the website only ever reads back what the API allows.
Follow a single reservation from quote request through pricing, dispatch, status updates, and into your reports.
A visitor enters pickup, drop-off, date, and vehicle class in the booking widget and requests a quote.
The API validates the request, the rates engine computes real driving distance, and your rates, zones, and vehicle multipliers are applied.
On confirm, the reservation is saved, a branded confirmation email goes out, and the ride appears on your dispatch board in real time.
Your dispatcher assigns the ride. The driver updates status — assigned, en route, arrived, in progress, completed — live on the board.
The trip flows into revenue summary, revenue over time, ride status breakdown, and driver performance reports.
The website never touches the database directly. Every request is encrypted, authenticated, role-checked, validated, and rate-limited before it reaches your data.
Every request carries a signed token scoped to the user's role. The website never touches the database directly.
Rider, Driver, and Admin (with Admin sub-roles: Owner, Dispatcher, Accountant) see only what their role permits — enforced server-side.
Every write is validated at the API layer before it reaches your data — no client can write something the backend does not allow.
Abusive traffic is throttled at the API before it ever reaches the core, keeping your backend responsive.
Staff accounts can enable TOTP with backup codes. Account setup is email-verified, with self-service password reset.
Your data lives in a single isolated database — never shared with another company, one source of truth.
Everyday moments where the connected website and backend do work that separate tools simply can't.
A traveler books an airport ride outside business hours. The quote is instant, the reservation is captured, and your team sees it on the board the moment they log in — no missed leads.
A corporate client books through your site under their standing account. The ride attaches to the right corporate profile and a net-terms invoice is generated for it.
A new ride lands on the live dispatch board the moment it is booked — no refresh needed. The dispatcher assigns it to a driver and watches the status update in real time.
The driver uses their authenticated API access to move a ride through each status as the trip happens, and the board reflects it instantly for the whole team.
A booking typed once, a ride dispatched automatically, a receipt generated on drop-off. When your website and backend are one system, the manual work simply disappears.
"Where is my car?" is the most expensive phone call a chauffeur operator takes. Driver GPS streamed to the rider’s tracking link makes it the last one you’ll ever need.
Tell us about your fleet and current setup. We will walk you through exactly how this connects your website, drivers, customers, dispatch, and billing.
