Devices and Dev Kits FAQs
Dev Kit
How can I add a device for testing purposes in the Clover dashboard?
To associate a test device with your Clover sandbox developer account, follow the steps in Associate your Dev Kit with a test merchant account. This setup allows you to simulate device interactions and retrieve device details after login using OAuth in your Node.js application.
Why won't my Clover Dev Kit connect through Ethernet?
If your Clover device connects to Wi-Fi but not Ethernet, and shows the error adapter not found try the following: Under Settings > Network > Ethernet:
- Check the physical connection: Ensure the Ethernet cable is securely plugged in and the hub or adapter you're using has power. Some Clover devices require a powered USB hub or a specific Ethernet adapter.
- Device limitations: Clover devices may not support Ethernet natively or may require specific hardware. If other devices connect fine using the same cable, the issue is likely with the Clover hardware or compatibility.
Note: Clover network settings may only show toggles for Wi-Fi or Mobile, not Ethernet, if the adapter isn't recognized.
Can I disassociate a used Clover Mini 2 Dev Kit from a previous merchant account and reassign it to a new one?
You can disassociate a Dev Kit from a test merchant account directly through the Clover Developer Dashboard. This action removes the Dev Kit's link to the test account but does not affect its functionality. Once disassociated, the Dev Kit can be linked to another test merchant account.
If you no longer have access to the original merchant account, contact Clover Developer Relations at [email protected]. Provide the device’s serial number and any known Clover ID associations. They will verify the account and assist with unlinking the Dev Kit.
Why am I getting a 403 Forbidden error when associating a Dev Kit with a sandbox device associated with a test merchant?
This error may occur if your device lacks a serial number or if your app hasn’t been properly deployed. To resolve this, send your device serial number, developer UUID, and test merchant UUID to Clover Developer Relations at [email protected].
Why does the emulator crash when submitting a payment using Cloud Pay Display?
The Cloud Pay Display app cannot be tested using an emulator. This app is designed to work only with physical Clover devices, such as Clover Mini or Flex, or Mobile, because it relies on secure WebSocket connections and hardware-level interactions that emulators do not support.
To test Cloud Pay Display functionality:
- Use a Clover Dev Kit with a physical device.
- Follow the Remote Pay Cloud SDK tutorial for proper setup and integration.
- If you're using the emulator for other Clover apps, ensure you’re not attempting to run Cloud Pay Display, as it will crash due to unsupported dependencies.
How can I connect my website to a Clover device using a sandbox account?
You cannot connect a physical Clover device to a sandbox account. The Clover sandbox environment is designed strictly for testing APIs and app development using Dev Kits or simulated environments. Clover devices require a production merchant account for activation and integration.
To simulate device interactions during development, use the Clover REST Pay Display API and Remote Pay Cloud SDK. These tools allow you to test semi-integrated POS flows without needing a physical device. You can follow the Cloud Connection guide and Remote Pay Cloud SDK tutorial for setup instructions. For production deployment, use your client’s Merchant ID and Device Serial Number with the production endpoint: https://api.clover.com/connect/v1/device/{device_id}
Device
Is any setup needed for the Clover device in a production developer account, similar to the sandbox Dev Kit
You cannot associate a Dev Kit with a Production account. Simply install your app on the merchant’s Clover device through the App Market and generate the OAuth access token on the Production Developer Dashboard.
I want to use one production developer account with different Clover devices and the same merchant. Is this possible?
Yes, if the merchant downloads your app and it is compatible with all of their devices, it will automatically be installed on each of those devices.
Why can't I download my app on my Clover device?
If the app appears in the Clover App Market but the download button is grayed out with the message—This app is not available on this device. Please download on a supported device—you need to update App Settings in the Developer Dashboard. This setting controls which devices can install your app. If it's not enabled for your Dev Kit, the app will appear but remain unavailable for download.
- Log in to the Developer Dashboard.
- Go to App Settings > App Type.
- Ensure your app is marked as available for Clover Dev Kit or the specific device type you're testing on.
Can I use one access token across multiple Clover devices, and is there a device limit?
Yes, you can use a single access token across multiple Clover devices. The access token is tied to the merchant account, not individual devices. There is no specific limit on the number of devices that can use the same token, as long as they are associated with the same merchant account.
Clover Go
How can I get the goApiKey and goSecret for the Clover Go Remote Pay SDK in the production environment for the United States?
goApiKey and goSecret for the Clover Go Remote Pay SDK in the production environment for the United States?Contact Developer Relations. Email your request to [email protected] with details about your developer account and intended use for the goApiKeyandgoSecret for the Clover Go Remote Pay SDK in the production environment for the United States.
Can I use Clover Go with a Windows-based vending machine app to take payments?
No, Clover Go readers only work with smartphones or tablets, not computers. If you're using a Windows app, Clover Go is not compatible. Instead, consider using Hosted Checkout or Ecommerce APIs, which allow you to launch a secure payment flow from your app and accept payments online. These options offer more flexibility and automation for vending or kiosk-style setups.
Kiosk
Why does the Clover payment screen time out in Kiosk Mode if left idle overnight?
The payment screen automatically times out if no card is presented within approximately 60 seconds. This behavior applies even when using CustomerMode.enable(this) in Kiosk Mode. To avoid interruptions, ensure that payment interactions are completed promptly or implement logic to reset or reinitiate the payment flow after a timeout.
Mini
Can I change the background and font color on the Clover Mini?
No, Clover does not currently support changing the background or font color on the Clover Mini. However, you can explore the device’s Accessibility settings to enable features like High Contrast Text, which may improve visibility for some users.
Flex
Why does CloverExamplePOS.exe show a USB error when connecting Clover Flex 3 to a Windows PC?
This error usually means the device is detected but not fully initialized. Make sure you’ve completed these steps:
- Install Clover USB drivers (included in the Remote Pay Windows SDK).
- Enable USB Pay Display on the Flex 3 after connecting it to the PC.
- Use a known-good USB cable and port (preferably USB 2.0 or 3.0).
- Run CloverExamplePOS.exe as Administrator to ensure proper permissions.
For additional information, see Connecting your POS to Clover.
Updated 1 day ago
