Step 3: Development
During the development phase, you integrate your POS app with Clover using the SDK and Pay Display app. To start developing your integration, do the following:
1. Set up your sandbox and production developer accounts
Before you get started with developing your application, you must create a Clover developer account for both the sandbox and production environments using the Developer Dashboard:
- Clover sandbox developer account—Allows you to create a test merchant while developing your application. All development and testing for your semi-integration solution must be done in this sandbox environment.
- Region-based production environment; See Production developer accounts for more information:
- US Clover production developer account—Allows you to manage your published app in the live environment in the US region.
- Europe Clover production developer account—Allows you to manage your published app in the live environment in the European region.
2. Create a Remote App ID (RAID)
When your integration connects to a Clover device, your semi-integrated application must pass a Remote App ID (remoteApplicationID
or RAID) generated for your Clover app. This differs from your Clover App ID; both IDs are needed to launch your integration with Clover. The format of the RAID is {developerId}.{appId}.
The Remote App ID allows Clover to expedite support requests for your semi-integrated solutions, enabling the logging of payments made through your app. Your point of sale (POS) uses this ID when creating an ICloverConnector
; see Use Clover Connector. Clover checks and verifies the Remote App ID for each call and then uses it to log certain operations. You can create or view your Remote App ID on the Developer Dashboard. See Create your Remote App ID.
NOTE
If you are creating integrations for more than one platform or connection protocol, a separate app and unique RAID is required for each so Clover can provide reliable support. For example:
- To create POS apps for web and iOS clients use the Remote Pay Cloud and Remote Pay iOS SDKs. Do not use the same RAID for both apps.
- To connect your app to the device using a USB or Network Pay Display, create a separate RAID for each connection type.
- To integrate POS systems for more than one platform, make sure you are using the correct RAID for each app.
3. Order a Developer Kit
A positive overall merchant and customer experience is the goal of all integrations. Clover recommends that you order a Developer Kit (Dev Kit) for the Clover device you want to use with your integration. See Clover Developer Kits.
The Dev Kit you select also depends on the region your merchants operate in.
Region | Clover Flex | Clover Go | Clover Mini |
---|---|---|---|
US | ✅ | ✅ | ✅ |
Canada | ✅ | ||
UK/Ireland | ✅ | ✅ | |
Argentina | ✅ | ✅ |
4. Develop your integration
Once your Dev Kit is configured, you can start using the CloverConnector
interface to connect to and interact with the Clover device.
- Connect your POS to the Clover Dev Kit.
- Use the Clover Connector SDK to enable interactions between your POS and the Clover device. See Use Clover Connector.
5. Receive developer support
Clover provides support to all integration projects to run as smoothly as possible. If you encounter an issue with an SDK or have a question about your integration, email us at [email protected]. Your email is added to a ticketed queue; a Clover engineer reviews it and then assists with your question.
Updated 7 months ago