We have released the following improvements in the Clover Sandbox and Production environments:

New driver for saving print receipts as images

We are introducing a new printer driver that enables you to test receipts using your emulator. For more information, see our documentation on Testing with printer receipt images.

Target SDK version for uploading Android APKs

Clover supports Android apps with the targetSDKVersion value in the AndroidManifest.xml file set to 25 or lower. SDK level 26 onwards, Android has introduced the account access and discoverability policy, which explicitly requests access to Clover merchant accounts and disrupts the expected merchant flow.

Both in the sandbox and production environments, you will now be notified with an error message if you upload an APK with the targetSDKVersion value set to 26 or above.

New Ideas & Feedback space on Community

We are introducing a new space on community.clover.com called Ideas & Feedback. In this space, you can freely post ideas and suggestions about improvements to the Clover SDKs, REST API, and Clover App Market.

To post an idea:

1. In the Ideas & Feedback space, select Post an idea. Log on with your account credentials.
2. On the Suggest an idea page, enter the information you want to share.
3. Once you are done, select Post Your Idea.

2FA for your accounts

We are recommending all 3rd party developers and Clover merchants to enable two-factor authentication (2FA) for their accounts.

To enable 2FA:

1. On the sandbox Developer Dashboard, select Account name > Account Settings from the header.
2. Under Two-Factor Authentication, select Set Up Authentication App or Set Up SMS Authentication.
3. Follow the mentioned steps and complete your setup.

📘

NOTE

Repeat these steps to enable 2FA for your production account.

You can keep track of all merchant-facing changes on Clover Help. For questions and feedback, use community.clover.com.

To receive more third-party developers communication from Clover, sign up here.