A privacy-first biometric identity platform that lets a passenger move through the airport on one verified identity — created once at enrollment and reused at security and boarding — without storing raw face images.
It coordinates with the systems an airport already runs (airline, AODB, document checks, staff SSO) without leaking personal data or losing control of it. This document describes the integration blueprint; biometrics are simulated and partner systems are mocked to contracts in this phase.
AURA hands partners a meaningless claim-ticket (a token) — never a passenger's real identity or biometrics. Partners coordinate about a passenger using that token; only AURA's on-prem vault at KSIA can resolve a token back to a person.
| Integration | Why it's in the minimum set | Owner |
|---|---|---|
| INT-1 Airline DCS | Validate the journey against a real booking | Airline |
| INT-2 Airport AODB | Correct flight & gate context at the gate | Airport |
| INT-3 Document Auth | Anchor identity to a genuine document at enrollment | Provider |
| INT-5 Staff SSO | Trustworthy staff identities to drive RBAC | Airport |
| INT-6 Matching simulated | The deterministic gate decision — on-prem only | KSIA (internal) |
| INT-7 Notification | Mobile-first passenger guidance (recommended) | Provider |
Gov/Border (INT-4) and Analytics (INT-8) are designed but not built this phase; INT-4 only enters the pilot if KSIA / the regulator mandates it.
template_data, raw_image,
selfie, given_name, family_name, document_number.
REAL Integration contracts & flows (INT-1,2,3,5,6,7) as contract-shaped mocks · token issuance/resolution · server-enforced RBAC · tamper-evident audit · fail-safe fallback logic.
SIMULATED Biometric capture & matching (INT-6) — deterministic decision, no real biometrics, same contract a real engine will use later.
NOT USED Live passenger / production data — synthetic, non-personal test data only. NOT BUILT INT-4 gov/border & INT-8 analytics (designed only).