Clover Developer Kits can be ordered at http://cloverdevkit.com/
Repeatedly Inserting an active EMV credit card into an EMV enabled development device that is pointed to a ‘black hole’ 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.
Clover Developer Kits are specially-permissioned Clover devices that can simulate transactions in a sandbox environment. This environment is completely separate from the production environment has been designed to enable testing apps in preparation for later deployment on the production server.
Once you have placed your order and received your developer kit, familiarize yourself with the hardware using the included guide, also available here: https://www.clover.com/setup
Then, follow the steps below to set up your device for use with your sandbox development account.
If you’re running into issues with your Clover device, please refer to our Devkit Troubleshooting guide.
Create a sandbox account
Navigate to https://sandbox.dev.clover.com/developers and create a new developer account by entering your email and selecting Create Account. Then fill in your account details as directed.
Because the sandbox environment is separate from the production environment you must create a new developer account in the sandbox environment. Devices cannot be re-provisioned to point at a different environment, and developer and merchant accounts also cannot be migrated to a different environment.
Associate your device
After creating your account, navigate to the Dev Kit tab in your sandbox developer account dashboard. Under Manage Dev Devices enter the serial number of your development kit, which may be found on the sticker attached to the outside of your device’s box (e.g. “C012UQ12345678”). Then use the drop-down to select which of your test merchant accounts you wish to associate the device with. Finally, select Associate Device. An activation code will be displayed, and the same code will be emailed to your development account. Take note of this code for the next step – activating 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, the activation token will be disabled, and you will need to begin the association process again.
Activate your device
After associating your device from the developer dashboard, power on the device and you will see a welcome screen with a message for your test merchant name.
If the welcome screen has a generic “Welcome to Clover” message, it has not yet been associated, or the activation code has expired.
After selecting Continue you must set up a Wi-Fi connection on a Wi-Fi Protected Access (WPA) network.
Clover Dev Kits 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 with the remainder of the Setup Wizard, and once all of the default apps have been confirmed and downloaded 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 WiFi, 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 WiFi 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 can be found 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 computer not recognizing their Dev Kit after following the above steps.
Please try this temporary solution via force installing Samsung ADB Driver: http://developer.samsung.com/technical-doc/view.do?v=T000000117
For information on how to force install a driver, please see: http://revryl.com/2013/08/06/install-unsigned-drivers/
ADB over WiFi
Once your computer has been configured to recognize Clover sandbox devices via ADB, it is possible to use ADB over WiFi as well as USB. The steps are the same as a standard Android device, as described here: https://developer.android.com/studio/command-line/adb.html#wireless
You must disconnect, or disable any ethernet network connection on your Sandbox device in order for the device to ‘fallback’ to WiFi, allowing wireless ADB.