Add the Connect button
Drop this one line wherever your merchants manage their account. It renders a “Connect Pay by Phone” button that opens Ringup’s hosted connect page, where the merchant picks their processor and authorizes it.data-ringup-label (button text), data-ringup-variant (filled default, or outline), data-ringup-return (URL to send the merchant back to). Prefer your own UI? Point any element or link at https://ringup.dev/connect?vendor=YOUR_PUBLIC_KEY.
What the merchant sees
The hosted page lists the processors Ringup supports and lets the merchant connect theirs:Square
Live now. One-click OAuth (details on the Square page).
Stripe, Clover, Toast
Rolling out. Each connects with its own flow as the adapter ships.
How it fits your integration
Connecting is the merchant’s step, and it happens whenever they are ready, asynchronously to your own launch. Until a merchant connects, the payment layer stays inaudible on their calls (create_checkout returns payment_required: "none"), so you can ship Ringup across your whole fleet while merchants onboard at their own pace. The merchant is live the moment they connect, with nothing else for you to do; Ringup fires merchant.connected (carrying merchant_id) so you can reflect it in your own UI if you like.
You never handle card data or the merchant’s processor credentials. For OAuth processors the client secret stays on Ringup’s server; for credential-entry processors the keys go straight into a hosted, encrypted field, never through your dashboard.
Next steps
Square
The one-click OAuth option.
Webhooks
Handle
merchant.connected.