One QR, Three Handoffs: How Pace Sync Closes the Gate-to-Pad Gap

Abstract

The promise of K-UAM is seamless city-to-skyport travel. The operational reality, at least through the 2027 commercial window, is a chain of three discrete transport operators — taxi, ground shuttle, and vertiport pad controller — each running a separate booking system, a separate identity check, and a separate payment terminal. Every seam in that chain is a potential missed flight and a lost passenger. The UAM Korea Travel app (v2.0, App ID 6769374828) addresses this directly through a Pace Sync architecture: a single signed QR boarding pass that carries identity, payment authorization, and vertiport slot reservation through all three handoffs without re-authentication. This article defines Pace Sync as an operational discipline, maps the three handoff points against real Seoul and Incheon corridor geometry, explains how the QR payload survives each transition under Korea's PIPA data minimization requirements, and describes what happens when an upstream leg slips its window. For vertiport operators, mobility-platform PMs, and K-UAM Roadmap 2030 working-group members preparing for commercial certification, this is the credential architecture that converts a booking into a completed flight.

---

1. Operational Anchor — Gimpo–Yeouido Shuttle Corridor, Seoul Metropolitan Government UAM Pilot

The Site

Gimpo Airport and Yeouido represent the highest-probability early-commercial K-UAM corridor in the Seoul Metropolitan Area. The Seoul Metropolitan Government's UAM pilot designation covers the Han River waterfront axis, and the Yeouido heliport has served as the de facto reference pad for Ministry of Land, Infrastructure and Transport (MOLIT) trial operations since 2024. Ground access to Yeouido heliport depends on a combination of Kakao Taxi dispatch and a dedicated shuttle bus linking Yeouido Station (Line 5/9) to the heliport gate — a shuttle that does not currently share a scheduling API with the pad booking system. That gap is precisely the handoff failure mode Pace Sync is designed to eliminate.

Environmental Read

The Gimpo–Yeouido corridor operates under Seoul's municipal noise ordinance, which caps low-altitude rotorcraft operations below 600 ft AGL over the Han River residential bank during 22:00–07:00 KST. Slot density during morning peak (07:30–09:30) and evening peak (17:30–20:00) is therefore high and non-flexible. A passenger whose taxi leg slips 6 minutes does not simply arrive late — they arrive at a shuttle gate whose next departure may be 8 minutes away, while the reserved pad slot expires in 5. Without a clock-locked credential that propagates delay signals upstream and re-slots downstream automatically, the passenger absorbs the failure manually, at the gate, in real time.

Differential Factor

What distinguishes this Korean case from a generic airport-transfer scenario is the regulatory layering: KAS Part 25 imposes manifest obligations on the eVTOL operator, PIPA constrains how identity data flows between the taxi platform (Kakao Mobility), the shuttle operator (Seoul Metropolitan Facilities Management Corporation), and the vertiport pad controller. Each operator has a different data-processing legal basis. A QR credential that naively embeds full identity data would violate PIPA's purpose-limitation principle at the shuttle gate, which has no legitimate need for passport-grade identity. The Pace Sync architecture solves this through token scoping, not data suppression.

Modern Bridge

For a vertiport operator today, the relevant question is not whether to adopt a QR boarding pass — it is whether the QR issued by a third-party mobility app (including UAM Korea Travel) will carry enough trusted state to satisfy pad-side manifest requirements without requiring a secondary scan or manual re-entry. The 2027 commercial window leaves approximately 18 months to establish that interoperability standard. Operators who participate in defining the token schema now will not be renegotiating it at certification.

---

2. Problem Definition — The Three-Seam Latency Chain

The K-UAM Roadmap 2030 plans 200+ vertiports across Korea, the majority in metropolitan corridors already operating under dense multi-modal ground transport. MOLIT's own connectivity model assumes that vertiport access will be primarily intermodal — passengers arriving by KTX/SRT, metro, taxi, or shuttle rather than private vehicle. That assumption converts every vertiport into a transfer node, and every transfer node into a latency-management problem.

The three handoffs in a standard Gimpo–Yeouido journey each carry measurable latency risk:

Handoff 1 (App dispatch → Taxi arrival): Kakao Mobility's 2025 dispatch reliability data shows a median 2.3-minute delta between estimated and actual pickup in inner-Seoul during peak hours, with a 95th-percentile delta of 6.8 minutes. A slot reservation made at booking time must absorb this variance or trigger re-slot logic.

Handoff 2 (Taxi arrival → Shuttle gate scan): Shuttle dwell time at Yeouido Station averages 4 minutes with a scheduled frequency of 10 minutes. A passenger who misses a shuttle cycle faces a mandatory 10-minute wait, which exceeds the typical pad slot buffer.

Handoff 3 (Shuttle arrival → Pad check-in scan): Pad-side manifest closure for eVTOL operations under current Korean trial procedures requires T-3 minutes confirmation. A passenger arriving at T-2 with an expired QR token must be manually re-accommodated, creating gate congestion for subsequent slot holders.

Without a unified credential that propagates real-time position and delay state across all three operators, each handoff becomes a discrete re-booking event. Current trial data from the Seoul heliport and Incheon Technopark corridors suggests that manual re-accommodation accounts for approximately 12–18% of passenger touchpoints during peak trial windows — a failure rate that would be commercially unacceptable at 200-vertiport scale.

---

3. UAM KoreaTech Solution — Pace Sync QR Architecture in UAM Korea Travel v2.0

The UAM Korea Travel app (v2.0) implements Pace Sync through a three-layer QR payload architecture:

Layer 1 — Identity Token: A PIPA-compliant signed JWT encoding a pseudonymous passenger identifier, age-band flag (for alcohol/safety compliance), and biometric-hash reference linked to the passenger's Apple/Kakao/Toss Pay-verified account. This layer is readable by all three operators but reveals only what each operator's role permits: the taxi dispatcher reads only the dispatch identifier, the shuttle gate reads only the boarding-eligible flag, and the pad controller reads the full manifest-relevant token.

Layer 2 — Payment Authorization Nonce: A single-use payment nonce pre-authorized against the passenger's selected payment method (Apple Pay, Kakao Pay, or Toss Pay) covering the full multi-modal fare bundle. This nonce is consumed at the first scan and replaced by a receipt reference at each subsequent gate, preventing double-charge and eliminating per-leg payment friction.

Layer 3 — Slot Reservation Handle: A pointer to the vertiport's authoritative slot record, not a copy of it. The slot management system retains state; the QR carries only the lookup key. When the Kakao Mobility API reports that the taxi ETA will exceed the Pace Sync buffer threshold (configurable per corridor; default 4 minutes for inner-Seoul, 7 minutes for Incheon gateway routes), the app fires an automated re-slot request against the vertiport slot API and updates the QR payload's slot handle in the background. The passenger sees a silent push notification; no manual intervention is required.

The technical provenance of this architecture — pseudonymous tokens, least-privilege field scoping, and pointer-based slot references — reflects PIPA data minimization obligations and is designed to satisfy the identity audit requirements anticipated under MOLIT's forthcoming vertiport certification framework. The app's Incheon Airport OpenAPI integration provides real-time slot visibility for Incheon gateway routes, while the Korail/SRT interlink surfaces train delay data as an upstream trigger for Pace Sync recalculation when passengers are arriving from KTX/SRT feeder legs.

---

4. Strategic Context — Why Pace Sync Is a Regulatory Inevitability, Not a Feature Choice

The K-UAM Roadmap 2030 is explicit: vertiports must function as intermodal nodes, not standalone pads. MOLIT's working group on vertiport ground access has flagged multi-modal credential interoperability as an open item in every published consultation since 2024. The 2027 commercial certification window will require operators to demonstrate that passenger manifest integrity is maintained across the full journey, not just the final airside leg.

KAS Part 21/23 airworthiness approval for eVTOL operators imposes manifest obligations equivalent in spirit to ICAO Doc 9303 machine-readable travel document standards — the passenger on the manifest must be verifiably the passenger on the pad. In a multi-operator handoff chain, that verification chain is only as strong as its weakest credential link. A QR that degrades in authority between the taxi scan and the pad scan is not a compliant manifest chain.

Korea's Kakao Mobility federation (covering approximately 76% of Seoul taxi dispatch volume as of 2025) makes the app-to-dispatcher API link a practical reality rather than a theoretical integration. The EAAF flyway constraint adds a further dimension for Incheon gateway routes: vertiport slot density is bounded not only by airspace capacity but by bird-strike risk windows tied to migratory calendar, making Pace Sync's ability to absorb delay without generating ad-hoc slot overcrowding directly relevant to wildlife safety compliance as well as schedule integrity.

Municipal noise ordinance compliance in Seoul adds a hard outer boundary: slots that cannot be re-accommodated within the operational window are not simply delayed — they are cancelled. A credential architecture that can propagate delay signals fast enough to trigger re-slot before the window closes is therefore a noise-compliance tool as much as a passenger-experience tool.

---

5. Forward Outlook

The immediate 12-month priority is interoperability testing between the UAM Korea Travel app Pace Sync layer and at least two vertiport slot management systems operating under MOLIT trial authorization. The Incheon Technopark site — where AVIX-AI BirdThreat completed its 19/19 HTTP 200 validation in April 2026 — provides a controlled environment for end-to-end QR handoff testing that includes both ground-transport dispatch and pad-side manifest closure.

By Q1 2027, the target state is a published token schema agreed between the app, Kakao Mobility, and at minimum one eVTOL operator certified under KAS Part 21/23, enabling the QR boarding pass to satisfy pad-side manifest requirements without secondary verification. The KTX/SRT interlink integration, already live in v2.0, will be extended to expose train delay data as a Pace Sync upstream trigger for the Osong–Seoul corridor, the most likely high-volume feeder route for the 2027 commercial window.

The longer-term outlook, aligned to the 200+ vertiport deployment scale in the K-UAM Roadmap, is a national credential interoperability standard that the QR architecture developed in UAM Korea Travel v2.0 can serve as reference implementation for.

---

Conclusion

A QR boarding pass is only as valuable as the trust chain it carries across each scan. By encoding identity, payment, and slot reservation in a single PIPA-compliant, least-privilege payload — and by wiring that payload to real-time Kakao Mobility dispatch and Incheon Airport slot APIs — UAM Korea Travel's Pace Sync architecture converts a multi-operator transfer chain into a single managed journey. When Korea's first commercial vertiport opens under the K-UAM 2027 window, the credential that passengers scan at the pad will have already survived two upstream handoffs; the infrastructure that makes that possible needs to be defined and tested now, not at certification.