Topic starter
11/11/2026 5:56 pm
TL;DR: Verified wallet identity can populate flight booking forms in one click, according to Hopae. Booking systems then move from error-prone manual entry to controlled credential reuse.
Editorial analysis by NHI Mgmt Group, based on content published by Hopae: “Trip.com turns the phone wallet into the booking form”.
Key questions
Q: How should travel platforms govern digital identity reuse across booking and check-in?
A: Travel platforms should govern digital identity reuse by setting assurance thresholds for each step, such as booking, payment, self-service changes, and check-in.
Q: What is the difference between a digital wallet and a passport credential?
A: A digital wallet is the container or app that stores and presents credentials, while a passport credential is one specific identity document issued by an authority.
Q: How do wallet-based credentials change online identity verification?
A: Wallet-based credentials let a person present verified claims from a digital wallet instead of retyping identity data into a website or app.
Practitioner guidance
- Define accepted wallet credentials for each booking step Specify which eID schemes and wallet types can populate booking fields, and tie each one to a defined assurance level and transaction purpose.
- Separate booking assurance from downstream travel checks Set different policy thresholds for booking, check-in, visa handling and biometric boarding so a single verified credential is not overextended.
- Map identity attributes before autofill goes live Document which wallet attributes populate which booking fields, where normalization happens, and what exceptions require manual review.
Bottom line: Wallet-based identity can reduce booking friction, but it shifts the trust decision from typed data to credential assurance and issuer policy.
Glossary terms: Digital Identity, Identity Wallet, Verifiable Credentials (VCs), Relying Party
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:07 pm
Digital identity is moving the trust decision upstream: Booking systems no longer need to accept identity as typed input when a wallet can present a verified credential instead. That changes the control point from form validation to credential assurance, issuer trust and attribute mapping. The implication is that travel IAM must treat the booking step as part of identity governance, not just customer experience.
A question worth separating out:
Q: What should teams do first before replacing form entry with verified identity?
A: Teams should first map which forms collect identity data, why each field is needed, and what trust level the process actually requires. That lets them decide whether verified identity, selective disclosure, or plain form entry is appropriate, and where fallback steps, exception handling, and fraud checks are needed before automation replaces manual input.
👉 Read our full editorial: Trip.com autofills flight bookings with wallet-based identity