Apply passenger name record rules for exact ticket name matching

Steps

1. Collect the passenger's name exactly as it appears on the travel document (passport or national ID) they will use — do not infer from a user profile or email address without explicit confirmation.
2. Most airlines accept Latin characters only on tickets; for passengers whose documents use non-Latin scripts (Arabic, Chinese, Cyrillic), use the romanized name from the machine-readable zone (MRZ) of the passport.
3. Remove or transliterate special characters that airline reservation systems cannot process: accented characters (é→E, ü→UE per ICAO), hyphens in given names (Anne-Marie → ANNEMARIE or ANNE MARIE depending on carrier), and apostrophes (O'Brien → OBRIEN).
4. Split name into surname and given name(s) as separate fields — do not concatenate into a single string; middle names are typically included in the given name field and must not be omitted if on the travel document.
5. Titles (Mr, Mrs, Dr) are stored in a separate title field in booking APIs — do not prepend them to the name string, as this causes name mismatch at check-in.
6. After creating the booking, display the ticketed name back to the user for confirmation before payment is captured; name changes after ticketing are expensive or impossible on most carriers.