Stay organized with collections
Save and categorize content based on your preferences.
How to add merchant specific terms
Merchant specific terms allow you to specify text and/or a url for the
merchant’s specific terms. The text will be shown in the merchant's overview
tab as well as in the booking modal. An example of the booking modal can be
seen here:
The url will be linked to from the bottom of the create booking modal and
will always use the text Terms of Service (this text can not be changed).
[[["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 2024-04-09 UTC."],[[["The legacy Firebase Cloud Messaging (FCM) APIs for HTTP and XMPP are being discontinued, requiring developers to migrate to the HTTP v1 API for enhanced security and features."],["The HTTP v1 API utilizes short-lived OAuth2 access tokens for improved security, offers cross-platform customization through common and platform-specific keys, and is extensible to support future platforms."],["Migration to the HTTP v1 API involves updating the server endpoint to include the version and project ID, replacing the legacy server key with an OAuth 2.0 access token, and modifying the message payload structure to accommodate platform-specific customizations."],["For security reasons, sending messages directly from client apps is not recommended; instead, utilize a trusted environment like an app server or Cloud Functions with HTTPS or the Admin SDK."]]],[]]