Ship voice-agent payments on Clover

Building for merchants on Clover? Charges settle on each merchant’s own Clover account, using credentials the merchant mints from their own dashboard, with no app-store approval gate between you and a pilot merchant. Orders land in their Orders view as paid, with line items, customer, and card attached.

Settles on the merchant’s Clover accountOrders in their dashboardSelf-serve merchant connectNo PCI scope for you

Why Ringup

Your merchants’ POS stays the system of record.

Their dashboard

Orders are created first and paid second, so Clover shows your merchant a normal paid order with line items, customer, and card. Their reporting, refunds, and reconciliation work exactly as today, with nothing new for you to support.

Their money

Every charge settles on the merchant’s own Clover account at their existing rates. Ringup is never in the money flow, never holds funds, and your merchant stays the merchant of record. No rate conversation, no re-underwriting.

And the experience you ship is the point: your agent recognizes returning callers by phone number and charges their saved card in one sentence. No card read aloud, no number in any transcript, no PCI scope anywhere in your stack.

The tools

Three tools

identify

The sign-in, not a lookup. Matches the caller’s number to an authenticated session: name, saved card (brand + last four), returning or new, and the merchant’s payment-policy verdict. Treat it as a login event: attach your own order history and preferences to the caller.

charge

Charge the saved card after verbal confirmation. Idempotent: platform retries can never double-charge. Settles on the merchant’s own processor.

send_link

Text a secure pay page to first-time callers. The card is captured once, off the call, and every future call after that is one sentence.

Quick start

What actually happens on a charge

1  POST /v1/orders            →  order created
2  POST /v1/orders/{id}/pay   →  source: the caller's saved card

→  Clover Dashboard: ECOMM ORDER: Paid   (items · customer · card)

Same order id from creation to paid, verified in Clover sandbox with the order visible in the merchant dashboard as a paid ecommerce order with refund support wired.

Best practices

Clover best practices

Self-serve merchant connect	Merchants generate Ecommerce API tokens from their own Clover dashboard (Account & Setup → Ecommerce API Tokens) and drop them into a hosted connect page. No app review between you and going live.
Order-then-pay	Create the order, pay it by id, and the same order transitions to paid in your merchant’s Orders view: line items, customer, and payment attached.
Saved cards, done natively	Clover models the card-network stored-credential framework directly: the consented first charge and merchant-initiated repeat charges are first-class API concepts, exactly what your repeat-caller flow needs.
Refunds	One call against the charge, linked and visible in the merchant dashboard like any other Clover refund.
Capture timing	The success signal is instant: your agent speaks the confirmation on the call. Settlement happens in Clover’s normal batch cycle.
Recognition	Returning callers are matched by phone number in Ringup’s identity layer and confirm their saved card verbally; your agent never re-collects a card after the first save.

Platform reference: Clover docs. Ringup maintains this page against Clover’s current API surface.

FAQ

Questions

Do my merchants have to change anything about their Clover setup?

No. Charges settle on their existing Clover merchant account at their existing rates. Ringup never holds funds, and the merchant stays the merchant of record.

What shows in the merchant’s dashboard?

Paid ecommerce orders with line items, customer, and card payment attached, refundable like any other order. Their reporting doesn’t change.

How do I onboard a merchant?

They mint Ecommerce API tokens from their own Clover dashboard and paste them into a hosted connect page. No hardware, no app install, and their credentials never pass through your stack.

Can a caller’s saved card work across my merchants?

Clover scopes cards per merchant, but Ringup’s identity layer recognizes the caller everywhere. The card re-links per business with one consent, so the experience your agent ships stays one sentence.