Advance passenger information capture
How do we collect the passport and Secure Flight data once on a secure screen after booking and write it to the reservation before the carrier's deadline?
Ask once, read the passport, and write the data to the reservation on the clock. After booking, Callvu prefills the Secure Flight and advance passenger information fields from the traveler's profile (the name as on the ID, the date of birth, the gender, the known traveler and redress numbers, the passport number, nationality, expiry and issuing country, the country of residence and the destination address where required), asks the traveler on a secure screen only for what is missing or stale, reads a passport image where one is provided and checks the fields against the booking name, chases the data on a schedule counted back from the carrier's deadline, routes a name mismatch to the travel desk in the Decision Desk, and writes the data to the reservation in the booking system in the carrier's format before the deadline with the confirmation recorded.
In scopeSimpleCallvu moves: prefill, chase and verify, write back
Last updated November 7, 2026.
The problem today
The reservation had the nickname, the passport had the full name, and the boarding pass could not be issued at the kiosk.
Carriers must send passenger data to the authorities before departure: Secure Flight data for US flights and advance passenger information for international ones. The agency enters what it has; the traveler is asked at online check-in for the rest; the name on the reservation is a nickname; the passport number has a typo. The traveler ends up at the counter, and a reservation without the data in time is cancelled by some carriers.
The data is a fixed set of fields with a source (the profile and the passport) and a deadline (the carrier's, driven by the authorities' rules: Secure Flight data 72 hours before departure where possible, API before departure). Captured once on a secure screen, read from the passport and checked against the booking, it can be written to the reservation in the carrier's format and confirmed.
One secure capture after booking is the whole fix.
How it runs
From the requestto the system of record.
A flight is booked (through the booking tool or an agent). Callvu opens the data capture with the carrier's deadline.
- Traveler
- Confirms the prefilled data and provides what is missing on a secure screen, with a passport image where needed.
- Travel desk
- Decides name mismatches in the Decision Desk.
- Carrier
- Receives the data in the reservation and transmits it to the authorities.
- Callvu
- Prefills, captures, reads, checks, chases, routes and writes.
Prefill
The Secure Flight fields (the full name as on the government ID, the date of birth, the gender, the redress and known traveler numbers) and the advance passenger information fields (the passport number, nationality, expiry and issuing country, the country of residence, the destination address for US arrivals) are prefilled from the traveler's profile and compared with the booking name.
Chase and verify
The traveler is asked on a secure screen only for what is missing or stale (a new passport, a missing known traveler number), with a passport image read for the fields where provided; each field is checked (the name against the booking name with the carrier's matching tolerance, the passport expiry against the trip, the number's format and check digit, the date of birth against the profile); the data is chased on a schedule counted back from the carrier's deadline.
Decide
Data that passes writes by rule; a name mismatch between the profile, the passport and the booking (beyond the carrier's tolerance), or a passport that fails the check, goes to the travel desk in the Decision Desk with the data and only the allowed outcomes (correct the reservation name through the name correction process, accept within tolerance, or request a corrected document).
Write back
The data is written to the reservation in the booking system, the system of record, in the carrier's format (the SSR and the DOCS, DOCA and DOCO elements), the carrier's acceptance is confirmed and recorded with the time against the deadline, and the traveler is told the check-in can proceed.
Where it ends: The passenger data was captured once from the profile and the passport, checked against the booking, and written to the reservation before the carrier's deadline with the acceptance recorded. The Decision Trace shows the checks and any decision; the Audit Trace shows the capture, the write and the confirmation with time.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
A link after booking; the traveler confirms on a secure screen on their phone.
The back office
The travel desk decides only name mismatches; the carrier receives the data in the reservation.
The Decision Desk
- A name mismatch beyond the carrier's tolerance or a passport that fails the check goes to the travel desk in the Decision Desk with the data and only correct the reservation name, accept within tolerance, or request a corrected document.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
Questions
What buyers ask next,answered plainly.
What data is collected?
The Secure Flight fields (full name as on the ID, date of birth, gender, redress and known traveler numbers) and the advance passenger information fields (passport number, nationality, expiry, issuing country, residence and the destination address where required), once, on a secure screen.
When must it be in the reservation?
Secure Flight data about 72 hours before departure where the booking is made earlier; advance passenger information before departure as the carrier's rules set; the chase runs back from the carrier's deadline.
What if the names do not match?
The travel desk decides with the data: correct the reservation through the name correction process, accept within the carrier's tolerance, or request a corrected document.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.