Authorization
The payment step that approves or reserves a chargeable amount on a payment method. Successful authorization does not imply capture or booking confirmation.
Why it matters
Transaction concepts describe how a metasearch click becomes a downstream booking experience. Without context-preserving links, durable click identity, booking lifecycle events and reconciliation, search performance becomes disconnected from actual commercial outcomes.
What does it look like in practice?
A metasearch click ID travels through the deeplink, returns with booking events and is reconciled through cancellation/stay states. Breaking this lineage creates commercial attribution gaps.
Implementation questions
- Is search context preserved on the landing page?
- Is there a durable ID from click to booking?
- Are booking lifecycle events idempotent?
- Is provider state reconciled with internal state?
Common mistakes
- Treating a generic landing page as successful handoff
- Treating unknown booking state as failed
- Counting replayed conversions twice
Where does it appear in the travel stack?
Authorization commonly appears across transaction, agentic layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Agentic Travel Authorization, Mandates and Human-in-the-Loop
Design user intent, mandates, delegated authority and human-in-the-loop checkpoints for AI-driven travel purchase and servicing side effects.
Explore →Agentic Travel Reference Architecture
Design AI agent → search → offer → reprice → confirmation → payment → booking → servicing with travel-specific authorization, idempotency and audit boundaries.
Explore →Payment + Booking Distributed Transaction
Model payment and supplier booking as a distributed transaction using authorization, capture, compensation, UNKNOWN outcomes and reconciliation.
Explore →Agentic Travel Servicing, Consent and Auditability
Design agent-driven cancellation, refund and servicing with explicit consent, traceability, versioned evidence and post-booking authorization boundaries.
Explore →Agentic Travel Transaction Safety
Prevent duplicate booking and payment caused by agent loops, retries and tool invocation using idempotency, side-effect guards and UNKNOWN-aware recovery.
Explore →Idempotency and Duplicate Booking Prevention
Design idempotency boundaries and duplicate-booking safeguards across travel booking, payment, cancellation and refund operations.
Explore →