Overview
Stay organized with collections
Save and categorize content based on your preferences.
Page Summary
The Actions Center's Reservations End-to-End integration allows linking out to your booking page for reservations requiring deposits, no-show fees, or prepaid inventory to handle the transaction.
To add payments to specific reservations, you need an existing live E2E Integration, the ability to deep link to a booking page that handles payment processing, and compliance with Payment Redirect Policies.
Implementing Payments Redirect involves setting up your URL template and additional fields, specifying payment types for slots, and enabling conversion tracking.
Partners using Real-Time Updates must update them to include the new payments redirect fields.
As part of the Actions Center's Reservations End-to-End integration, you can enable
any deposits, no-show fees, or prepaid inventory to be linkedout to your booking
page for any transactions that may requirement payments. Enabling payments in
this manner lets you handle the entire booking flow and transaction on the
booking page that you specify.
Eligibility
To add payments to specific reservations, you must have the following
prerequisites:
An existing live E2E Integration.
The ability to deep link directly into a booking page
that can handle payment processing.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-18 UTC."],[],["Payments Redirect, in pilot, allows partners to handle deposits, no-show fees, or prepaid inventory transactions on their own booking pages. To implement, partners need an existing E2E integration and a payment-capable booking page, following specific policies. Implementation involves setting up URL templates, specifying payment types, and enabling conversion tracking. Migrating from legacy payments requires removing the `tokenize_config` field from feeds, as Google no longer processes payments.\n"]]