Policies Overview for Payments

In addition to the integration policies, you are also required to abide by the following policies.

Supported Countries


  • Non-payments support include any reservation or booking that does not require payment to complete.
  • Accepting payments support indicates that payments may be accepted to reservations for merchants in that country.
Country Country Code Non Payments Accepting Payments
Aland AX Supported Not Supported
Andorra AD Supported Not Supported
Anguilla AI Supported Not Supported
Argentina AR Supported Supported
Aruba AW Supported Not Supported
Australia AU Supported Supported
Austria AT Supported Supported
Bahrain BH Supported Not Supported
Belgium BE Supported Supported
Brazil BR Supported Supported
British Virgin Islands VG Supported Not Supported
Bulgaria BG Supported Supported
Canada CA Supported Supported
Cayman Islands KY Supported Not Supported
Chile CL Supported Supported
Christmas Island CX Supported Not Supported
Colombia CO Supported Supported
Cook CK Supported Not Supported
Croatia HR Supported Supported
Curaçao CW Supported Not Supported
Czech Republic CZ Supported Supported
Denmark DK Supported Supported
Estonia EE Supported Supported
Falkland FK Supported Not Supported
Faroe Islands FO Supported Not Supported
Finland FI Supported Supported
France FR Supported Supported
French Polynesia PF Supported Not Supported
Germany DE Supported Supported
Gibraltar GI Supported Not Supported
Greece GR Supported Supported
Greenland GL Supported Not Supported
Guam GU Supported Not Supported
Hong Kong HK Supported Supported
Hungary HU Supported Supported
India IN Supported Not Supported
Indonesia ID Supported Supported
Ireland IE Supported Supported
Isle of Man IM Supported Not Supported
Israel (EN UI only) IL Supported Not Supported
Italy IT Supported Supported
Japan JP Supported Supported
Latvia LV Supported Supported
Lithuania LT Supported Supported
Luxembourg LU Supported Supported
Malaysia MY Supported Supported
Malta MT Supported Not Supported
Martinique MQ Supported Not Supported
Mexico MX Supported Supported
Montserrat MS Supported Not Supported
Netherlands NL Supported Supported
New Caledonia NC Supported Not Supported
New Zealand NZ Supported Supported
Niue NU Supported Not Supported
Northern Mariana Islands MP Supported Not Supported
Norway NO Supported Supported
Panama PA Supported Not Supported
Peru PE Supported Not Supported
Philippines PH Supported Supported
Poland PL Supported Supported
Portugal PT Supported Supported
Puerto Rico PR Supported Supported
Russia RU Supported Supported
Saint Helena SH Supported Not Supported
Saint Pierre and Miquelon PM Supported Not Supported
Samoa WS Supported Not Supported
San Marino SM Supported Not Supported
Singapore SG Supported Supported
Sint Marteen SX Supported Not Supported
South Africa ZA Supported Supported
South Korea KR Supported Not Supported
Spain ES Supported Supported
Svalbard SJ Supported Not Supported
Sweden SE Supported Supported
Switzerland CH Supported Supported
Taiwan TW Supported Supported
Thailand TH Supported Supported
Tokelau TK Supported Not Supported
Turkey TR Supported Supported
Turks TC Supported Not Supported
United Arab Emirates (EN UI only) AE Supported Supported
United Kingdom GB Supported Supported
United States US Supported Supported
Uruguay UY Supported Not Supported
US Virgin Islands VI Supported Supported
Vatican City VA Supported Supported
Vietnam VN Supported Supported
Wallis WF Supported Not Supported

Notes and exceptions

  1. Accepting payments is subject to the Actions Center's payment policy.
  2. We recommend you check with the Actions Center support team prior to planning to launch payments in a country as there may be country specific requirements.
  3. CDF (Cadastro de Pessoas Físicas) or National Identification payments are not supported in Brazil at this time.
  4. For merchants and services that are operating in Quebec, all text must be localized in both English and French.
  5. For Israel, price must be in local currency (ILS). Item price must be in increments of 0.10 (eg. 50.10, 50.20, 50.30) and not be in other increments (eg. 50.12, 50.22).

Payments Policies

This section specifies the general and feature-specific policies for implementing payment on the Actions Center. To ensure a consistent experience for consumers, merchants, and partners using the Actions Center, inventory requiring payment must adhere to the appropriate guidelines. Failure to adhere to these policies will lead to suspension of your integration.


These policies apply to all payments transactions and inventory on Reserve with Google:

  1. No charges should be made to a user that are not explicitly agreed to at checkout, as articulated via our payments configuration process.
    • Payment terms contained within the linked Terms of Service page do not satisfy this requirement.
  2. For in-person services, all payments must occur at the time of booking or in-person only. Solicitation of payment by any other means is strictly prohibited.
  3. The amount charged to a user must be the same amount specified in the terms of the transaction.
  4. The transaction must be displayed and charged in the currency of the location of the merchant (currency is specified via the payments configuration process). No currency conversions may take place.
  5. Payment tokens cannot be used to support charges for other transactions or purposes.
  6. No instrument other than the token created for this transaction and sent to you by Google can be used for these charges.
  7. If the acquiring bank for your transactions is subject to PSD2, you must implement 3DS1 or 3DS2 for those transactions when supported by Actions Center and your payment processor.
  8. If the service requires pre-payments, no show fees, and/or deposits, service cancellation_policy definition is mandatory.
  9. If you are adding payments to your integration now or in the future, you must provide reliable and complete contact information including name, address, phone number, email address, and registry information as may be required by certain regulations.

No Show Fee

The following policies apply to inventory and transactions using the no show fee feature:

  1. No show fees for late cancellations must only be charged if a user cancels after the no-charge cancellation window specified for that booking.
    • If no cancellation window is specified for a booking, the default cancellation window ends at the start of the reservation.
  2. Google must be informed via a real-time update if a user is charged a no show fee.


The following policies apply to inventory and transactions using the deposit feature:

  1. Deposits should not be used to pay the full price of a service. Prepayment should be used for this function.
  2. If a user cancels before the end of the no-charge cancellation window specified for that deposit, then:
    • Their deposit must be refunded or not charged.
    • If the booking is cancelled outside of the Actions Center, Google must be informed via a real-time update.


The following policies apply to inventory and transactions using the prepayment feature:

  1. A cancellation policy is defined for all prepayment bookings.
    • If no cancellation policy is specified, then bookings default to non-refundable
  2. If a user cancels in a timeframe eligible for a refund (as defined by the cancellation policy for that booking), then:
    • Their prepayment must be refunded as defined by that cancellation policy.
    • If the booking is cancelled outside of Actions Center, Google must be informed if a refund took place or not via a real-time update.

Credit Card Required

The following policies apply to inventory and transactions using the credit-card-required feature:

  1. No charges should be made to the user for any credit-card-required transactions.