Global developer platform: Known issues and workarounds

This page provides a list of known issues on the Clover global developer platform and the workarounds for them. The Clover team is working to resolve these issues as a priority.

Developer account lockout due to incorrect login link (URL)

To access your developer account for the North America region, use the global developer platform link (URL): https://www.clover.com/global-developer-home.

Issue: Global developer account login error.
Workaround: Verify that you are not using the legacy sandbox or production URLs. For more information, see Create global developer account.

Issue: Developer account is locked due to incorrect login attempts on a legacy URL.
Workaround: Send an email to [email protected] with your developer account information and the Subject line: Global developer experience.

Multiple account confirmation emails

Issue: Received multiple developer account confirmation emails while creating your account.
Workaround: Use the link from the most recent email to confirm your developer account. The links in the other confirmation emails give a page not found (404) error.

Two-factor authentication (2FA) for test merchants

You cannot access your global developer account if you set up two-factor authentication (2FA) for your test merchant owner accounts. To avoid being logged out of the Global Developer Dashboard, we recommend not enabling 2FA for test merchant owner accounts.

However, in some cases, such as when setting up an API token for your test merchant, you need to complete the 2FA setup.

Issue: Logging out from the Global Developer Dashboard if 2FA is set up for test merchant accounts.
Workaround: Do not set up 2FA from your test merchant owner account. Instead, on the test Merchant Dashboard, do the following:

1. Create an Employee record for the merchant with the role set as Admin.
2. Use the new Employee credentials to log in to the test Merchant Dashboard.
3. Complete the steps to create your token.

For more information on 2FA, see Set up two-factor authentication (2FA).

Log out issue when using MFA for subsequent logins

Issue: Developers with multiple global developer platform accounts may encounter logout issues when attempting to log in with different developer credentials.

Example: After successfully logging into the Global Developer Dashboard with multi-factor authentication (MFA), a developer logs out and tries to log in with another set of credentials (email and password). During the MFA process using an authenticator app, such as Google Authenticator, the developer is logged out.

Reason: The issue is caused by a specific domain cookie and is observed even in Incognito mode.

Workaround:

1. Open the Global Developer Dashboard Log in page to manage browser cookies.
2. Right-click on the webpage, and from the menu, click Inspect. The Developer Tools panel for the browser appears.
3. Select the Application tab and from the left navigation menu, click Cookies. A list of domains for which cookies are stored in your browser appears.
   Note: The tab name may vary by browser; for example, in Google Chrome and Microsoft Edge, it is Application, while in Mozilla Firefox, it is Storage. In Chrome and Edge, the Cookies section displays in the Application tab left navigation pane, under Storage.
4. Click the domain name—clover.com— for the Global Developer Dashboard. A list of cookies for the domain appears.
5. Do one of the following:
   • Right-click the domain name and click Clear to clear all cookies in the domain.
   • Find the cookie in the right pane, starting with PF, right-click the PF... cookie, and click Delete.
6. Refresh the cookie list and verify that the PF... cookie does not display in the cookies list for the domain.

To learn more, see Set up multi-factor authentication (MFA).