Payment Radar
Toast Enables Multi-Hotel Payment Routing for Cross-Property Dining
Toast announced on January 27, 2026, that its property management system (PMS) integrations now support multi-hotel payments, allowing guests to charge meals to their room at any participating property.
Payment RadarOriginal source: Toast · linked publisher media; native reuse rights require confirmation 
What changed
Toast updated its property management system (PMS) integrations to support multi-hotel payments. This allows guests to charge meals to their room at any participating property within a hotel group. The update introduces additional mapping between hotels and restaurants to enable seamless cross-property dining and payment experiences. Payments can now be routed to FOSSE, Full Service PMS, Lightspeed PMS, and Infor HMS. The feature is available to all locations that have Toast hotel integrations as of December 1, 2025, and is available in all countries. A property management system (PMS) is software that hotels use to manage bookings, guest information, and billing.
Why a business should care
This update directly changes payment routing and checkout capabilities for hotel and restaurant operators using Toast. It enables cross-property billing, potentially simplifying guest checkout and settlement workflows. Operators can now offer a more integrated dining experience across multiple properties.
Who it affects
Hotel and restaurant operators using Toast with hotel integrations as of December 1, 2025.
What to consider doing
Contact Toast support to enable the multi-hotel payment feature for your locations. Verify that your PMS provider (FOSSE, Full Service PMS, Lightspeed PMS, or Infor HMS) is correctly mapped for cross-property billing to ensure smooth settlement.
Uncertainty and risks
Merchants must contact Toast support to enable the feature. Payments will be routed to specific PMS providers, potentially affecting settlement and reconciliation workflows. Operators should confirm their current setup supports the new routing before enabling the feature to avoid billing discrepancies.
Comments