Developer account set up FAQs

Whom do I contact in case of a developer account rejection?

You can send all developer account and app inquiries to Clover Developer Relations at: [email protected]. Include your developer account details and any other relevant information.

Why am I getting a billing error when trying to upgrade a test merchant’s service plan in the Clover sandbox environment?

Sandbox test merchants cannot self-upgrade service plans. If you encounter a billing error while attempting to access features like Inventory, you’ll need to request support from Clover. Once approved, the Clover team can manually upgrade your test merchant account to enable the required features. Email your request to [email protected].

Why am I getting an Invalid claim state?

Clover accounts are region-specific, and the same email address cannot be used across multiple regional developer accounts. If your email is already associated with a Clover account in the US region (clover.com), you cannot reuse it for the European region (eu.clover.com). Attempting this results in an Invalid claim state error.

To resolve this:

• Use a different email address that is not linked to any Clover account.
• Log out of all Clover sessions and clear browser cookies.
• Try registering in Incognito mode to avoid session conflicts.
• See the Global Developer Platform guide for region-specific setup instructions.
• If the issue persists, email Clover Developer Relations at [email protected]. Include your current account details and mention the subject: Global developer experience. They can assist with overriding the claim state or generating a new claim link for the EU region.

Why does my Clover sandbox account only show the billing authorization page and not the expected dashboard?

If your Clover sandbox account only displays the Authorize billing page and not the full dashboard, it’s likely that the onboarding process hasn’t been fully completed. You must accept the billing authorization to proceed—this step is required even for sandbox accounts and does not result in any charges. Once accepted, you should be redirected to the sandbox dashboard. Other quick checks are:

• Permissions: Ensure you are logged in as the Owner of the test merchant account; Employee roles may lack the authority to bypass the billing screen.
• App status: If you are a developer, ensure you have created at least one Test Merchant in your Developer Dashboard. You cannot access a dashboard without an associated merchant entity.

How can I add permissions for my app to the Employee app under the permissions section?

This is not currently supported. Clover does not allow third-party apps to appear in the native Employee app’s permissions section. However, you can implement custom permission logic using the Employee SDK. For example, you can check if an employee has admin privileges and conditionally enable or disable features in your app. See the Clover blog: Access Granted…Access Denied: Permissions Based on Employee Role.

Why can’t I verify my developer account or update business info in the sandbox?

The sandbox environment is strictly for development and testing, and the account verification process is reserved exclusively for the production environment. In the sandbox, your account will always remain in an unverified state. This does not limit your ability to create apps, test REST APIs, or use the emulator. While you can edit basic profile details, you cannot submit formal business documentation, such as Tax IDs or Bank information in the sandbox, as no real money is processed there.