> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ringup.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Clover

> 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](/payment-providers/overview)). 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.

## What the merchant does

<Steps>
  <Step title="They open your Connect button and pick Clover">
    It lands on Ringup's hosted connect page, where they choose **Clover**.
  </Step>

  <Step title="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.
  </Step>

  <Step title="They copy their Merchant ID">
    The 13-character code in their Clover dashboard URL (`.../m/XXXXXXXXXXXXX/...`), or under **Settings, then Business information**.
  </Step>

  <Step title="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.

    <Frame caption="Ringup connect page: paste the two tokens and the Merchant ID.">
      <img src="https://mintcdn.com/ringup/6rwpYNEIBAppz8jr/images/merchant/clover-02-connect-form.png?fit=max&auto=format&n=6rwpYNEIBAppz8jr&q=85&s=c9e31a58f8c63bf9961dae01529ecfbb" alt="Ringup Clover connect form" width="930" height="1438" data-path="images/merchant/clover-02-connect-form.png" />
    </Frame>
  </Step>
</Steps>

<Note>
  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.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Square" href="/payment-providers/square">The one-click OAuth path for Square merchants.</Card>
  <Card title="Webhooks" href="/concepts/webhooks">Handle `merchant.connected` and payment events.</Card>
</CardGroup>