A Clover merchant connects by pasting three values from their Clover dashboard: the public token, the private token, and their Merchant ID.
Clover is one of the processors on Ringup’s hosted connect page (reached from the generic Connect button, see Merchant integrations). A Clover merchant pastes three values from their Clover dashboard: the public token, the private token, and their Merchant ID. You embed nothing Clover-specific, and no card data passes through your systems.
It lands on Ringup’s hosted connect page, where they choose Clover.
2
They copy the two tokens from Clover
In their Clover dashboard: Settings, then All settings, then Ecommerce, then Ecommerce API tokens. They copy the Public token and the Private token. Clover reveals the private token once, so they grab it right away.
3
They copy their Merchant ID
The 13-character code in their Clover dashboard URL (.../m/XXXXXXXXXXXXX/...), or under Settings, then Business information.
4
They paste and connect
They paste all three into the Ringup connect page and click Connect. Ringup verifies the token against Clover and the merchant is live. Ringup fires merchant.connected (carrying merchant_id) so you can reflect it in your own UI.
Ringup connect page: paste the two tokens and the Merchant ID.
The public token creates one-time card tokens in the browser; the private token settles the charge on the merchant’s Clover account. Both stay server-side at Ringup after connect. The card number never touches your systems or the merchant’s dashboard.
