Skip to main content
Ringup is a remembered checkout for phone calls. A caller who has paid once is recognized by phone number on every call after and pays again in one sentence: no card read aloud, no app, nothing to repeat. For you it is a payment orchestration engine. You integrate Ringup once, never each payment processor: the same API charges whichever processor a merchant runs. Your agent keeps the conversation; Ringup runs the money. No payment prompt to write, nothing to configure: the payment step inherits everything from your agent. Your merchants keep the payment setup they already have. Charges settle on each merchant’s own processor, at their rates, in their dashboard, and refunds, disputes, chargebacks, and reporting all run exactly where they run today.

​
The call, before and after

Without Ringup

“To pay by card, please say or enter your sixteen-digit card number, followed by the expiration date and security code.” “4 0 2 3… sorry, 4 0 3 2…” “I didn’t get that. Please say or enter your sixteen-digit card number.”

With Ringup

“That’s one large pepperoni, nineteen dollars. I can put that on your Visa ending 1111. Sound good?” “Yep.” “Done. Your confirmation number is 2PJJZY.”
First-time callers get a texted link instead, pay on their phone, and are recognized on every call after that.

​
Where to start

Start by seeing it work, then pick how you integrate: let Ringup run the payment for you, or add Ringup’s tools to your own agent.

See it work

About a minute. Recognize a caller and charge a saved card in test mode, then hear a wired demo call.

Hosted call transfer

About 10 minutes. Your agent transfers the live call to Ringup’s payment line. Set up in the dashboard, write no payment logic. The easiest path, and the one we recommend.

In your agent, with the API

Keep the caller in your own agent and add Ringup’s tools: recognize the caller, charge the saved card, no transfer. The flexible path.

API reference

Every tool, with a live playground and a full error catalog.

Changelog

What has shipped, and the versioning you can build against.

​
What Ringup never does

  • Never reads or stores card numbers. Card entry happens once, on a Ringup-hosted page. The number never appears in audio, transcripts, or your servers, so no PCI scope lands on you.
  • Never creates a new processor account. Charges settle on the merchant’s existing payment processor.
  • Never hard-codes payment behavior into your agent. How payment works is a merchant setting served by Ringup at call time; merchants change it with zero redeploys.