Core components of the platform
Following are a the core components of the platform.
Business logic, persistence & routing layer
These are the core services that interpret each API call:
-
maintain user/app sessions
-
load and save tickets
-
journeys, baggage, and devices
-
apply EBT security rules
-
handle tag transaction approvals
-
decide which downstream airline integration to call.
Persistence keeps the authoritative link between journey, baggage, device, and passengers' travel plans.
Airline targeted services
There are server modules that speak to each airline’s systems. These modules know how to interact with specific airlines, giving the ability to connect and plugging them into the system.
Multi-tenant handler gives us the ability to connect to similar systems employed by different airlines by only adding new configurations. For e.g.: Any airline using Amadeus Navitaire can be connected through a multi-tenant handler for Amadeus Navitaire.
Validation engine
These are rules that run on loaded journeys and tag operations: check-in window, whether a bag tag is allowed, data consistency, and airline-specific checks. Results surface as clear messages or errors, so the app can explain why the user cannot continue instead of failing silently later.
Webhook handler layer
Optional outbound notifications to partner systems when important events occur (for example after a successful device attachment), using each onboarded client’s endpoints and security model. Exact event catalogs are agreed per partner.