Clover DevKits are Clover devices with special permissions that can simulate transactions in a sandbox environment. This environment is completely separate from the production environment. Clover has designed this environment to enable you to test apps in preparation for later deployment on the production server.
We highly recommend that you order a Clover Developer Kit (DevKit). Clover DevKits allow you to experience transactions from end-to-end from the merchant and customer perspectives.
Once you’ve placed your order and received your DevKit, you should familiarize yourself with the hardware by reviewing the accompanying guide. The guide is also available on the Clover website.
Then, follow the steps below to set up your device for use with your sandbox development account.
Repeatedly inserting an active EMV credit card into an EMV-enabled development device that is pointed to a blackhole payment gateway may result in the credit card disabling itself. This is due to EMV protections against repeated inserts that do not result in actual payments.
If you encounter issues with your Clover device, please refer to the DevKit Troubleshooting guide.
Create a sandbox account
To create a sandbox account:
- Navigate to https://sandbox.dev.clover.com/developers.
- Enter your email address and click the Create Account button.
- Complete the form that appears.
Because the sandbox environment is separate from the production environment, you must create a new developer account in the sandbox environment. You cannot re-provision your device to point to a different environment. In addition, you cannot migrate your developer and merchant accounts to a different environment.
Associate your device
After creating your account:
- Navigate to the DevKit tab in your sandbox developer account dashboard.
- Under Manage Dev Devices, enter the serial number for your development kit. You can find the serial number on the sticker attached to the outside of the box for your device (e.g., C012UQ12345678).
- Use the drop-down menu to select the test merchant account you want to associate the device with.
- Select Associate Device. An activation code will appear. Clover will also email this code to your development account. You will need this code to activate your device.
Be ready to activate and finish associating your device prior to selecting Associate Device. If the activation process is not completed within 30 minutes, Clover will disable the activation token, and you will need to begin the association process again.
Activate your device
After you’ve associated your device, you will need to complete the following steps to activate it.
Power the device on. A welcome screen with a message for your test merchant name will display.
If the welcome screen has a generic “Welcome to Clover” message, it has not yet been associated, or the activation code has expired.
Click the Continue button. you must set up a Wi-Fi connection on a Wi-Fi Protected Access (WPA) network.
Clover DevKits do not contain functional SIM cards. You may provide your own SIM card to use a 3G connection on a SIM-enabled device.
To connect a Clover device to a Wi-Fi network, the network must be secured with a WPA or better security protocol.
To activate the device, select Next, and then enter the activation code you received after associating your device.
Finally, proceed through the remaining screens of the Setup Wizard. After you’ve confirmed and downloaded all of the default apps, you will arrive at your device’s home screen.
Enable Android Debug Bridge
Sandbox Clover Station will not allow debugging via USB. In order to use ADB with a sandbox Station device, you must connect via Wi-Fi, as described in the next section. Sandbox Clover Station already has the tcpip port set to 5555.
Android Debug Bridge (ADB) can be used to access your developer kit device directly via the included USB cable or via Wi-Fi as described below. To enable your PC to recognize the device you must add
0x28F3 #clover mobile or mini to a new empty line in your
adb_usb.ini file (on a Mac, this file is located at
~/.android/adb_usb.ini). After this change your
adb_usb.ini file should look similar to the following:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x28F3 #clover mobile or mini
Some Windows users have experienced issues with their computers not recognizing their DevKits after following the steps above.
If this occurs, please try this temporary solution, which involves force-installing Samsung ADB Driver.
ADB over Wi-Fi
Once you’ve configured your computer to recognize Clover sandbox devices via ADB, it will be possible to use ADB over Wi-Fi as well as USB. The steps are the same as for a standard Android device.
You must disconnect or disable any ethernet network connection on your Sandbox device in order for the device to fallback to Wi-Fi, allowing wireless ADB.