One QR, Three Handoffs: How Pace Sync Boards the K-UAM Passenger

Abstract

K-UAM's 2027 commercial window is not primarily a certification problem. It is a passenger-experience engineering problem. An eVTOL departure slot at a high-frequency vertiport is a constrained resource measured in seconds, not minutes. Passengers arriving via taxi, shuttle, and pad gate face three distinct operator boundaries — each with its own authentication, payment, and scheduling system. Without a unifying data artefact, every boundary becomes a friction point capable of collapsing the connection window.

Pace Sync is UAM KoreaTech's operational framework for solving this. At its centre sits a single QR boarding pass generated by the UAM Korea Travel app (App ID 6769374828) that carries a signed identity claim, a settled payment token, and a time-locked vertiport slot reservation through all three handoffs without re-authentication. This article defines the handoff architecture, quantifies the timing constraints, and explains why claim-scoped identity federation — rather than a centralised passenger-data silo — is the correct engineering posture for the K-UAM era. The analysis is grounded in the Kakao Mobility API integration, Incheon Airport OpenAPI infrastructure, and the MOLIT K-UAM Roadmap 2030 target of 200+ vertiports by 2030.

---

1. Operational Anchor — Gimpo Airport North Apron Shuttle Corridor

The Site

Gimpo International Airport operates one of Korea's most constrained multi-modal surface environments. Its north apron interfaces with a dedicated bus-shuttle corridor that connects the airport's domestic terminal to three prospective vertiport pads identified in the K-UAM Roadmap 2030 planning documents. Daily passenger throughput at Gimpo exceeds 40,000 domestic travellers, a significant fraction of whom already use Kakao Mobility's airport-pickup API for last-mile ground transit. This makes Gimpo the highest-density test case for multi-modal boarding handoffs in the Korean UAM planning horizon.

Environmental Read

The Gimpo shuttle corridor runs on a fixed 12-minute headway during peak hours. Vertiport slot windows in early K-UAM commercial operations are expected to be 3–5 minutes wide, based on MOLIT's published capacity modelling. The arithmetic is immediate: a passenger whose taxi leg runs four minutes late consumes the entire shuttle headway buffer before the shuttle even departs. Without real-time pace monitoring and automated slot adjustment, the miss rate at Gimpo's prospective vertiport pads would structurally exceed 20% during morning peaks — rendering the service commercially unviable before it launches.

Differential Factor

What distinguishes Gimpo from generic K-UAM planning scenarios is the maturity of its existing digital infrastructure. Gimpo already exposes real-time gate and shuttle data through the Incheon Airport OpenAPI framework (shared infrastructure across Korean major airports). This means Pace Sync does not need to build a proprietary data feed — it can subscribe to certified, latency-audited API endpoints that already carry the timing signals needed to drive slot-extension logic. The integration surface exists; the orchestration layer does not. That is precisely the gap the UAM Korea Travel app v2.0 is designed to fill.

Modern Bridge

For a vertiport operator commissioning a new pad at Gimpo, the Pace Sync framework translates directly into an SLA conversation: what percentage of booked passengers arrive at the pad gate within their slot window? Without Pace Sync, that figure is a function of Seoul traffic variance — essentially unmanaged. With Pace Sync, it becomes a managed metric backed by Kakao Mobility navigation telemetry, automated slot-extension requests, and a QR boarding pass that propagates updated state to every downstream scanner without requiring the passenger to re-enter any information.

---

2. Problem Definition — The Three-Boundary Latency Gap

The K-UAM boarding chain involves at minimum three commercial-operator boundaries: the taxi or ride-hail provider (Kakao Mobility), the ground-shuttle operator (airport or vertiport concessionaire), and the vertiport operator managing pad allocation. Each boundary historically requires a separate authentication event — app login, ticket scan, gate validation — adding an average of 45–90 seconds per crossing based on analogous multi-modal transit data from Seoul Metro's integrated ticketing studies.

At three boundaries, cumulative authentication overhead runs 135–270 seconds — more than the entire slot window in a high-frequency K-UAM operation. The MOLIT K-UAM Roadmap 2030 targets a 15-minute city-centre-to-vertiport connection time in its 2027 commercial phase. If 270 seconds of that budget is consumed by re-authentication alone, the transport mode cannot compete with premium ground alternatives on journey-time grounds.

The structural fix is identity federation: one credential, issued once at booking, readable by all three operators within their authorised claim scope. ICAO Doc 9332 surface-operations doctrine establishes the principle that passenger identity verification should be completed at the earliest possible point and propagated forward — not re-verified at each boundary. The K-UAM context makes this principle operationally urgent rather than merely aspirational. The UAM Korea Travel app v2.0 implements it via a signed JWT embedded in a QR boarding pass, with claim-scoped disclosure at each gate.

---

3. UAM KoreaTech Solution — The QR Boarding Pass Architecture

The UAM Korea Travel app generates the QR boarding pass at booking confirmation. The QR encodes three distinct signed claims in a single JWT payload:

1. Identity claim — a tokenised wallet reference from Apple Pay, Kakao Pay, or Toss Pay, confirming the passenger's verified identity without transmitting raw financial data.
2. Payment claim — a settled-transaction reference from the Kakao Mobility API (ground leg) and the Incheon Airport OpenAPI (airside slot reservation), confirming that all legs are pre-paid and non-refundable unless a Pace Sync recovery event is triggered.
3. Slot reservation claim — a time-locked hash encoding the target pad, departure window, and a 90-second grace buffer. The hash is server-side refreshable: if Pace Sync triggers a slot extension, the QR's visual code does not change, but the backend state the scanner validates against is updated within 5 seconds of extension approval.

At each of the three handoffs — taxi confirmation, shuttle manifest close, pad gate — the relevant operator's scanner reads only the claim it is authorised to verify. The taxi system reads the payment claim. The shuttle manifest system reads the trip token from the Kakao Mobility federation. The pad gate reads the slot reservation hash. No operator receives the full JWT. This claim-scoped disclosure model is consistent with Korea's Personal Information Protection Act (PIPA) obligations and avoids creating a centralised passenger-data liability.

Pace Sync runs as a background watchdog within the app. It polls Kakao Mobility's real-time navigation API every 30 seconds during active transit legs, computes projected arrival at the next handoff point, and compares it against the slot reservation window. If the projected arrival exceeds the window by more than 60 seconds, the app automatically submits a slot-extension request via the Incheon Airport OpenAPI before the passenger is aware a problem exists. The Korail/SRT interlink within v2.0 extends the same logic to passengers arriving by KTX or SRT, where train-delay telemetry feeds the same Pace Sync watchdog.

---

4. Strategic Context — Why Federation Beats Centralisation in the 2027 Window

MOLIT's K-UAM Roadmap 2030 envisions 200+ vertiports along the EAAF flyway corridor and Seoul metropolitan demand bands. At that density, no single operator can own the passenger identity layer. Kakao Mobility, airport concessionaires, and independent vertiport operators will each maintain their own customer relationship and compliance posture. A centralised passenger-data silo would require every operator to surrender data sovereignty — a non-starter in Korean commercial practice.

Claim-scoped identity federation solves this without requiring regulatory compulsion. Each operator participates by reading a standard claim from the QR; none is required to share data with the others. The UAM Korea Travel app acts as the trust anchor — the entity that issues and signs the JWT — while each operator retains full autonomy over its own gate system. This architecture is extensible: as new vertiport operators come online through 2027 and beyond, they integrate by implementing the claim reader, not by joining a data-sharing consortium.

For dual-use VCs scoping the 2027 commercial window, the federation model has a clear valuation implication. UAM KoreaTech's trust-anchor position in the QR issuance chain is a network-effect asset that grows with every new vertiport operator integration. The UAM Korea Travel app's transactional layer — already connected to Kakao Mobility, Incheon Airport OpenAPI, Korail, SRT, Apple Pay, Kakao Pay, and Toss Pay — represents a multi-rail settlement infrastructure that would cost a new entrant 18–24 months to replicate from scratch.

---

5. Forward Outlook

The immediate milestone is pad-gate scanner certification at the first K-UAM commercial vertiport sites targeted by MOLIT for the 2027 commercial launch. UAM KoreaTech is engineering the QR boarding pass architecture to be scanner-agnostic — the JWT claim structure maps to standard QR ISO/IEC 18004 encoding, readable by any certified gate reader without proprietary hardware.

Through the remainder of 2026, Pace Sync's slot-extension API will be validated against Incheon Airport OpenAPI's published latency SLA. The target is a sub-5-second round-trip from extension request to confirmed slot-hash refresh — consistent with the 90-second grace buffer built into the slot reservation claim. Integration testing with Kakao Mobility's production navigation API for real-time pace estimation is scheduled for Q3 2026.

By Q1 2027, the app's Korail/SRT interlink will expand to include delay-notification webhooks from Korail's operational API, enabling Pace Sync to initiate slot-extension logic as early as the rail leg rather than waiting for shuttle-departure confirmation. This upstream integration compresses the recovery window and increases the proportion of passengers who arrive within their original slot without requiring re-booking.

---

Conclusion

K-UAM's commercial viability in 2027 depends on the passenger experience being as frictionless at the boundary between modes as it is within each mode. A single QR boarding pass — carrying identity, payment, and a time-locked slot reservation through every handoff — is not a product feature; it is an operational prerequisite. Pace Sync gives vertiport operators a managed arrival-rate metric where today there is only traffic variance, and it gives K-UAM working-group members a deployable federation architecture that scales to 200+ vertiports without demanding data-sovereignty concessions from any participant. The 2027 window is not waiting.