Frequently Asked Questions

Find answers to common questions about the Universal Commerce Protocol (UCP) for Lodging.

General

What is the Universal Commerce Protocol (UCP) for Lodging?

UCP for Lodging is our new open standard designed to unify digital commerce, now expanding to support the travel industry. We built it to enable direct, instant bookings across Google Surfaces. Our goal is to reduce friction in the booking process and help you minimize reservation abandonment.

What are the main benefits of integrating with UCP?

When you integrate with UCP for Lodging, you gain:

  • Expanded reach: Connect with high-intent travelers directly within Google's AI surfaces, including AI Mode in Search.
  • Reduced booking friction: Enable direct bookings within the interaction flow to keep users engaged.
  • Control: You remain the Merchant of Record, maintaining full control over your customer relationships and data.
  • Compatibility across the ecosystem: Benefit from a protocol that is interoperable with major industry standards (AP2, A2A, and MCP) and built to handle the full end-to-end travel journey.

What makes UCP different?

  • Modular and extensible: UCP is designed to support rich commerce experiences using capabilities and extensions tailored for lodging.
  • Fast and straightforward to implement: UCP gives businesses the choice to select the set of capabilities they want to support, whether using APIs, MCP, or A2A.
  • Co-designed with industry leaders: UCP is open source and designed in collaboration with leaders in travel and hospitality.
  • Secure and seamless payments: UCP supports secure payments using tokenization and lets you use existing payment integrations.

Integration & Technical

Is UCP compatible with my existing tech stack?

We built UCP on open standards, making it seamlessly compatible with major existing protocols you might already use, such as AP2, A2A, and MCP. UCP primitives map directly to standard hospitality operations like booking.

How does UCP relate to the Agent Payments Protocol (AP2)?

AP2 is our standard for secure, agent-led payment transactions. We use UCP to orchestrate the broader reservation lifecycle, while AP2 can be used as a specialized payment layer within UCP. This is particularly useful for future scenarios involving autonomous AI agent transactions.

How do we process payments? Do I need to support Google Pay?

You don't need to support checkout with Google Pay API on your website or app, but your Payment Service Provider (PSP) must be able to process our tokens. Most major global PSPs support this payment framework.

If I already have Google Pay, will you respect my existing configuration (e.g., card restrictions)?

Because UCP is a new integration, we require you to provide configuration specifically for this channel. You will need to define your parameters (such as restricting specific card types) specifically for your UCP integration.

How do I distinguish traffic from UCP versus my own channels?

We exchange booking, reservation, and transaction lifecycle events using the API contracts established in our specifications. This lets you clearly differentiate traffic and payments flowing through our AI surfaces versus your own website or app.

How do we handle real-time availability checks?

Before enabling the final "Book" button, we perform a real-time price and availability check against your API.

User Experience

Will integration using UCP for Lodging affect my property ranking?

No. Opting for our booking integration does not influence how we rank your properties or rates in listings. The user experience for listings remains consistent; however, offers integrated with UCP will feature the direct booking option.

Can users provide guest details and preferences during checkout?

Yes. We allow users to review and provide guest details, room preferences, and occupancy information during the flow. We expect your system to dynamically update rates, taxes, and fees based on the specific guest information provided.

Will I lose control of my customer data?

No. You are the Merchant of Record. You retain full ownership of your customer relationships, booking data, and the post-stay experience.

How do we handle customer privacy?

Our standard security and privacy practices apply to the interaction, but you own the transaction data. We are also building features like account linking that are designed to keep the traveler in control of their data and loyalty status.

What Terms & Conditions apply to a UCP reservation?

Your Terms & Conditions cover the booking, just as if the customer reserved directly on your own website. We display these terms to the customer, and they must accept them during the booking flow.

Are there limitations on re-marketing to customers acquired through UCP?

Since you are the Merchant of Record, you possess the customer's information just as you would for a direct booking. Standard privacy regulations and consent practices apply. We are planning a feature that will allow users to explicitly opt-in to marketing communications during the booking flow in a future update.