Stay organized with collections
Save and categorize content based on your preferences.
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.
[null,null,["Last updated 2025-06-09 UTC."],[[["\u003cp\u003ePayments Redirect is a pilot program within Actions Center's Reservations that allows businesses to handle booking transactions directly on their booking pages.\u003c/p\u003e\n"],["\u003cp\u003eTo be eligible, businesses must have a live E2E Integration, a booking page with payment processing capabilities, and adhere to Payment Redirect Policies.\u003c/p\u003e\n"],["\u003cp\u003eBusinesses migrating from the legacy Payments system to Payments Redirect should primarily remove the \u003ccode\u003etokenize_config\u003c/code\u003e field from their Merchant Feed, as Google no longer handles payment processing.\u003c/p\u003e\n"],["\u003cp\u003ePayments Redirect requires setup including URL templates, payment type specifications, and conversion tracking.\u003c/p\u003e\n"]]],["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"],null,["# Overview\n\n| **Note:** [Create a new support case in the Partner Portal](https://partnerdash.google.com/apps/reservewithgoogle/support/cases/create) if you are interested in enabling Payments Redirect.\n\nAs part of the Actions Center's Reservations End-to-End integration, you can enable\nany deposits, no-show fees, or prepaid inventory to be linkedout to your booking\npage for any transactions that may requirement payments. Enabling payments in\nthis manner lets you handle the entire booking flow and transaction on the\nbooking page that you specify.\n\nEligibility\n-----------\n\nTo add payments to specific reservations, you must have the following\nprerequisites:\n\n1. An existing live E2E Integration.\n2. The ability to deep link directly into a [booking page](/actions-center/verticals/reservations/e2e/policies/integration-policies#landing_page_requirements) that can handle payment processing.\n3. Ensure compliance of our [Payment Redirect Policies](/actions-center/verticals/reservations/e2e/policies/integration-policies#payments_redirect_policies)\n\nPayments Redirect Implementation Steps\n--------------------------------------\n\n1. [Setting up your Url Template and additional fields.](/actions-center/verticals/reservations/e2e/add-ons/add-payments-redirect/url-templates)\n2. [Specifying the payment types for your slots.](/actions-center/verticals/reservations/e2e/add-ons/add-payments-redirect/specifying-payment-types)\n3. [Enabling conversion tracking for your integration.](/actions-center/verticals/reservations/e2e/add-ons/add-payments-redirect/conversion-tracking)\n\n| **Important:** Partners using Real-Time Updates (RTU) must update them to include the new payments redirect fields. See [Real-Time API updates](/actions-center/verticals/reservations/e2e/e2e/integration-steps/real-time-api-updates) for more information."]]
