Keep Clover. Add a separate Bitcoin payment rail.
Clover’s current public payment materials emphasize cards, contactless wallets, PayPal, Venmo, Klarna and Pay by Bank; they do not advertise native Bitcoin acceptance. Merchants can evaluate a separate Lightning terminal beside Clover instead of replacing the POS.
The simplest model
Clover keeps the order
Continue using Clover for products, orders, staff operations and the payment methods Clover already supports.
Bitcoin runs beside it
Open a browser-based Bitcoin terminal on an existing phone, tablet, laptop or desktop and generate the customer’s Lightning QR.
Match the records
Use an order number or other reference in the Bitcoin processor so staff and accounting can tie the external payment back to the Clover sale.
What is verified—and what is not
We have not found a current Clover source advertising native Bitcoin acceptance. That is different from saying no Clover app or custom integration can ever support Bitcoin. For a merchant seeking a low-change implementation today, the defensible approach is to treat Bitcoin as an external payment rail unless a specific Clover integration is verified.
Why the browser-terminal model works
Speed says its Terminal product requires no dedicated POS equipment and supports custom order fields and multiple terminals. That lets a merchant test Bitcoin at one register or location before considering a deeper integration.
Primary sources: Clover accepted payments and Speed Terminal.