Merchant of record (MoR)_

Travel businesses operating across borders sometimes use a third-party MoR to simplify tax and compliance in markets where direct registration is impractical. The trade-off is reduced control over settlement timing, dispute handling and customer-facing descriptors.

The MoR question is where international travel businesses really feel the cost of global commerce. Direct registration in every market is operationally expensive; using a third-party MoR is faster but means giving up control over settlement, descriptor and dispute flow. The right answer depends on volume, regulatory exposure and how much the brand cares about the customer-facing experience.

The travel businesses that use a third-party MoR well negotiate booking-level data access as part of the deal, so finance and operations still see the picture even when the legal entity is different. The businesses that take the simpler MoR option lose visibility into their own revenue and rebuild it through manual exports months later.

felloh keeps booking-level evidence intact whether the travel business is its own MoR or working with one, so the picture for finance, support and compliance does not fragment.

The dashboard’s Bookings and Settlement views surface the underlying booking-level picture regardless of MoR arrangement, with the legal-entity context recorded in the Audit and Suppliers views. Where a third-party MoR handles settlement and dispute correspondence, the booking trail still flows through to the operating teams that need it.

For travel businesses using a third-party MoR for international expansion, the trade-off in operational visibility is mitigated. The customer-facing experience remains compliant in each market, and the finance team still gets the booking-level evidence they need.