Refund
A full or partial return of a completed payment to the customer. In travel, refund state should be reconciled across supplier, seller and PSP systems.
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?
Refund commonly appears across transaction layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
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 →Idempotency and Duplicate Booking Prevention
Design idempotency boundaries and duplicate-booking safeguards across travel booking, payment, cancellation and refund operations.
Explore →Payment Authorized/Captured but Booking Unknown/Failed
Diagnose payment-booking divergence when payment succeeds while booking remains unknown or fails, then choose safe recovery and compensation.
Explore →Refund / Reconciliation Mismatch Troubleshooting
Diagnose divergence between booking cancellation and payment refund state across amount, currency, partial refunds and provider evidence.
Explore →Travel Booking Saga and Compensation Patterns
Design Saga and compensation patterns for travel booking, payment, cancellation and refund workflows where rollback is impossible.
Explore →Travel Servicing Architecture
Model post-booking change, cancellation, refund, exchange, ancillary and schedule-change workflows with a canonical servicing architecture.
Explore →