Merchant Interaction

Web apps on Clover are built using the Clover REST API and are hosted by the developer. Merchants install approved Web Apps from the Clover App Market. Once an app is installed by a merchant, they can access it from any web browser, including the web browsers installed on Clover devices, via the Clover Home App (also known as the Web Dashboard):

clover-home-app

When a merchant installs or launches an app

When a merchant installs a web app from the Clover App Market, they are redirected to the Site URL specified in the app’s settings of the Developer Dashboard. When a merchant launches the web app from the Clover Home App or the Clover App Market they are redirected to the same Site URL.

When Clover redirects the user to your Site URL, it will append certain URL parameters. These include the merchant_id of the business and employee_id of the current user. To view a full list of query parameters included by Clover see the OAuth Response.

You should use the merchant_id and employee_id to determine if the merchant has ever used your app before and provide a friendly setup experience. Remember that themerchant_id refers to the merchant business account. The individual user (e.g. the merchant, manager, or employee) is identified by the employee_id parameter. See the FAQ for more information on the merchant_id.

Authenticating merchants and users

If users go directly to your web app (instead of launching it from the Clover Home App), you will need to redirect them to Clover in order to authenticate them. See the OAuth Docs for more information.