Developers can use the Development APKs to run the Clover Launcher from an emulator or personal Android device. See our Video Tutorial for a detailed walk through of setting up an emulated Clover Station
A test card is included in every Developer Kit purchase. You can purchase Developer Kits at cloverdevkit.com.
No, Clover does not have a PA-DSS implementation guide. Since Clover does not permit 3rd party application to access consumer payment account data, any 3rd party application is not a Payment Application as the term is defined by PCI PA-DSS. As such, there is no need for a PA-DSS implementation guide for 3rd party applications. […]
You’ll likely be alerted to this problem when you attempt to take a payment and receive an error message repeatedly (e.g. “Transaction Failed: Not Connected” or “Transaction Declined: Failed To Connect To Server”). To verify that the problem is the Internet connection, look at the Wi-Fi icon at the top right. If it’s showing a […]
All Clover devices and servers follow industry best practices for SSL/TLS configuration. To ensure interoperability, you must ensure that your servers use a compatible SSL/TLS configuration. SSL/TLS Versions Clover devices and servers are only guaranteed to support TLS 1.2. Some devices and servers may support TLS 1.1 and TLS 1.0. For security reasons, SSL 3.0 is not supported. […]
The externalPaymentId is an ID that the POS provides for two functions. For payments, it is an attribute that is added to the payment. For payments and manual refunds (Credit) it is also used to prevent duplicate requests from processing. If the device receives a request (Payment or Credit) with the same externalId, it will […]
Please refer to our guide on creating merchant generated API Tokens. Note that these API tokens should only be used for testing and development purposes. Production apps must programmatically generate API tokens through OAuth or the Android SDK.
You can find answers to more questions on the Clover Developer Community.