Merchant of Record
The entity accepting customer payment through its merchant account and carrying primary payment-record, chargeback and refund responsibility.
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?
Merchant of Record commonly appears across transaction layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Travel Payment Ownership: Merchant of Record, Seller of Record and Collect Models
Separate Merchant of Record, Seller of Record, agency collect, hotel collect and pay-at-property models across booking and reconciliation.
Explore →Canonical Hotel Entity Model
Design a canonical hotel identity layer that maps multiple supplier property records into one traceable entity with provenance and merge history.
Explore →Duplicate Property Detection Playbook
Detect the same hotel living under multiple canonical records using name, geo, address and supplier-mapping evidence.
Explore →Travel PII and Passenger Data Boundaries
Design safe boundaries for passenger identity, contact, payment and travel-document data across search, booking, logging and provider integrations.
Explore →Cloudbeds API Integration Guide
Build Cloudbeds PMS integrations with scoped credentials, property identity, reservation synchronization, rate-limit controls and reconciliation.
Explore →GIATA MultiCodes: Hotel Mapping and Master Data Profile
A technical profile of GIATA MultiCodes for hotel identity, supplier-code mapping, deduplication and incremental master-data synchronization.
Explore →