Prepare Clover configuration
Compatibility with Clover’s current authentication remains unvalidated. Contact support before preparing a new installation.
This page documents the fields of the existing Clover connector in ImaCash. Before a new setup goes live, confirm a compatible authentication and renewal procedure and the required permissions with support and the provider. Appearing in the selector does not validate an operational installation.
Clover distinguishes sandbox test credentials from the expiring tokens and renewal used in production. Keep the environments separate and obtain the appropriate private details from the responsible person. Entering a Token here does not itself establish that access will remain valid.
Preparation steps
- Confirm the environment, region, merchant, authorisation and connector permissions with the provider. Complete this review before connecting a real account; preserve a working configuration until any change has been agreed.
- Open Configuration > Integration > POS and select Clover. Configure the cash device separately under Machine.
- URL: enter the confirmed HTTPS API base for that environment, ending with a slash. Clover publishes these production bases:
- https://api.clover.com/
- https://api.eu.clover.com/
- https://api.la.clover.com/
- In the Token field, use only the private credential authorised for the relevant environment and merchant. Obtain the renewal procedure too; do not copy a test token into production.
- Merchant ID: enter the private merchant identifier confirmed by the responsible person. It is not a terminal number or website address.
- Close the changed configuration and choose to save. Check any messages; saving or displaying payment methods does not validate the complete workflow.
- In the payment-method dialogs, select the actual, distinct cash and card methods. Review Accept cards and the general capture and pending-transaction filters with the provider.
- With the provider, check references, dates, amounts, signs, payment methods and filters in an authorised environment before using the connector. Review both programs and actual cash separately. If a restart is proposed, explicitly complete it only when appropriate and recheck the selected payment methods.
Scope and limits
The documented workflow queries payments that Clover already reports as SUCCESS. It is not a list of orders awaiting payment. A recorded payment reference and amount do not themselves prove a cash movement in the device.
Check cash and card classification against the merchant’s methods. Mixed payments, refunds and other methods need specific validation; universal breakdowns and a bank card total are not advertised.
Queries devices and employees for the available filters. Check each capture and pending-transaction filter against actual values. Changing the synchronisation date does not guarantee complete history or prevent duplicates.
A local confirmation or cancellation does not prove a payment, cancellation or refund was written to Clover. If the result is uncertain, review both systems and actual cash before repeating, resynchronising or restarting.
Does not import products or shifts. The provider must review the connector’s necessary permissions and effects; this page does not validate globally read-only access, production authentication, universal compatibility or physical operation.
Official Clover environment documentation
The historical Spanish-language screenshot shows Hospitality and a Save button. The current selection is POS > Clover and saving is requested on closing. The screenshot’s URL is incomplete and must not be copied; it contains no usable access details.
