With Zamna technology powering verification requirements for check-in on select flights between Canada and London UK, our guests will enjoy complete assurance that their travel documents are fully compliant in order to fly.
Zamna verifica todos los documentos de viaje (Pasaporte y Green Card) y los compara con reglas de viaje complejas, emparejándolos con la reserva, eliminando tareas para tus Operativos/Agentes. Zamna crea una Inteligencia Digital duradera a partir de datos verificados.
1.2. Zamna WebView When the Zamna Webview (frontend application) is used, additional component is deployed, as well as public-facing API: Zamna ApiServers can be integrated by Zamna with your DCS and other internal/external systems for orchestration, supporting complex workflows and rich use cases.
Zamna API reference description Reference Names matching First, all names in all incoming documents (as well as PNR data coming from the DCS) are always translated to the MRZ format, compatible with the ICAO 9303 standard, allowing only A-Z letters and spaces in names fields. Please, refer to the name translation steps specification. MRZ forms are then compared directly — if no direct match ...
Getting started 1. Zamna Client integration scheme Airline is required to deploy and configure the Zamna Client stack within its own infrastructure (on-prem or Cloud). Zamna Client then provides APIs, callable from within the Airline existing business processes and touch-points. Crucially, no personal data is ever stored or exposed from Airline security premises using Zamna. Through the ...
Note checklist_id is an optional parameter - if not provided, Zamna will create a new checklist and auto generate its id. When checklist_id is provided, Zamna will try to locate existing checklist and return its current state - otherwise, a new checklist will be created with this checklist_id. This is useful when different touch-points and Airline systems interact with checklist of the same ...