Show HN: I built remembered checkout for Voice calls

01 — The problem

Your agent still doesn't know who's calling.

Voice AI books the table, takes the order, files the claim. But every call starts from zero: the regular gets treated like a first-timer, reading out a 16-digit card number every time a payment comes up.

Food pickupReservationsInsurance & billingCollectionsCustomer supportAuto parts

Order in seconds, prepaid before they leave the house

Without Ringup

The agent takes the order instantly, but the caller is a stranger: no name, no saved card. They still drive over and stand at the register to pay, adding lines for diners and work for staff.

With Ringup

The agent greets the regular by name, confirms the usual, and charges their saved card on the call. The order is prepaid, labeled, and ready at pickup.

Bookings that hold, without the card recital

Without Ringup

Deposits and no-show fees mean asking every guest to read a card to a bot, so most agents skip them and no-shows eat the night.

With Ringup

Recognized guests confirm the deposit in one sentence: “your Visa ending 5858?” First-timers tap a texted link. No digits spoken, every booking backed.

The claim is filed. The balance is settled.

Without Ringup

Identity by interrogation: name, date of birth, account number, then a card keyed digit-by-digit into the keypad, on every single call.

With Ringup

The phone number is the identity: carrier-verified, matched to the account, and the balance settled from a saved card in one sentence.

Make paying the easy part

Without Ringup

The hardest call in the book gets harder at the finish: the payer must dig out a card and read 16 digits before a promise-to-pay becomes money.

With Ringup

The moment they agree, it's done. The saved card is charged on the call, or a one-tap link lands by text while they're still on the line.

Know them before hello

Without Ringup

Every ticket opens with an interrogation (“name, email, order number?”) before the actual problem is even on the table.

With Ringup

identify returns who's calling before the first hello. Your agent opens with their history in hand, and if something's owed, it's one sentence to settle.

Hold the part, take the payment

Without Ringup

The counter quotes the part and holds it unpaid. Half the holds never show, and chasing cards by callback burns the counter's day.

With Ringup

Regulars are recognized on the first ring. The part is held and paid in the same breath, charged to the card on file.

02 — How it works

Phone as the payment identity

The first time someone pays, they're saved, keyed to the number they call from. Every call after, they're recognized instantly. Either way, paying takes seconds and never leaves the conversation.

First-time caller

Pay in one tap. Saved for next time.

1

A link arrives by text

While they're still on the call, a secure pay link lands in their messages. No app to download, no portal to log into.

2

They pay, their way

One tap with a digital wallet, or add a card or bank account, saved with their consent, nothing read aloud, nothing typed.

3

Done before they hang up

The payment confirms on the call, and they're recognized instantly the next time they ring.

9:41

Joe's Burgers

Here's your secure link to pay Joe's Burgers 👇

Pay Joe's Burgers$24.00

Pay

Pay

or pay another way

Card

Credit or debit

Bank account

Pay direct from your bank

+

iMessage

Returning caller

Recognized by number. Paid by voice.

1

We already know them

The moment they call, Ringup returns their name, saved card, and any context you've attached. Your agent greets them by name, not a form.

2

They just say yes

"Charge your card on file for $24?" "Yep." That spoken yes is the entire checkout.

3

Paid in seconds

The charge clears mid-conversation and the confirmation is read right back to them.

Caller AI agent

Caller

Hey, I'd like the usual: large oat latte.

Agent

Welcome back, Sam. That’s $6.40, and I've got your card ending 5858 on file. Charge it?

Caller

Yep.

Agent · Paid

Confirmation RU-7T29Q. Ready in 5.

03 — Why Ringup

One integration. Every processor your merchants run.

Your merchants don’t all use the same processor, and you shouldn’t care. The same API charges whichever one each merchant already has.

Other solution

Internet wallets

Made for the web, not the call

Your merchant needs to add a new processor

Locked to the wallet's own processing rails

Built to checkout on a web page or app

Looks you up by email, not the number you're calling from

Caller is asked to login to a website or app to authorize each time

Needs a smartphone, a browser, and a wallet account

Our solution

Ringup

Built for the phone call

Your merchant gets to keep their existing processor

One API across processors

Designed to pay right on the call

Caller is recognized based on phone number

Caller authorizes with a spoken yes or one tap

Works on any phone, with no app or website needed

04 — Payment providers

144+ payment providers, connected.

Every charge settles on the merchant's own account: their rates, their dashboard, their merchant of record. No reconciliation issues, no new processor account creation, no parallel disputes and chargeback flows, no headaches.

See all 144+ payment providers →

05 — Voice platforms

Every voice platform. Or your own stack.

Hosted call transfer drops into the platforms your agents already run on, and the REST API covers everything else: recognize the caller, create the checkout, transfer the call.

VapiRetell AIElevenLabs AgentsOpenAI RealtimeLiveKit AgentsPipecatVoiceflowTwilio ConversationRelayDeepgram Voice AgentAPIYour own stack (REST API)

06 — FAQ

Questions, answered.

What is Ringup?

Ringup is the identity and payments layer for AI voice agents. When someone pays over a phone call, Ringup turns the phone number into the payment identity, so a returning caller is recognized and charged on the spot, or texted a one-tap link the first time. No card read aloud, no app to download.

How is Ringup different from Stripe Link and other wallets?

Wallets like Stripe Link are built for paying on the web, not on a call. By design they make the customer log in on a web page or app, which doesn't work mid-call. Ringup is built for the voice channel: it recognizes the caller from their number and carrier signals, and lets them pay right on the call. There's a full side-by-side in the Why Ringup section above.

How does a customer pay during a call?

A returning caller is recognized by their number and pays by voice: "Charge your card on file?" "Yes." That's the whole checkout. A first-time caller gets a secure one-tap link by text and pays with a wallet, card, or bank; that method is saved to their number, so next time they just say yes. Nothing is typed or read aloud.

Is your solution 2FA-compliant for payments?

Yes, and it's stronger than the SMS codes most two-factor checks rely on. A payment is authorized by two independent factors: possession of the line (the call comes from the number itself) and its carrier-verified integrity (checks that the SIM hasn't been swapped and the line hasn't just been ported or forwarded). The biggest weakness of SMS two-factor is the SIM-swap: moving a number to a new SIM so the codes follow. Ringup detects exactly that, and there's no one-time code to phish. You get every assurance of 2FA, plus a defense against the attack that usually beats it.

Do you store card numbers? Is it PCI-compliant?

Card details live in a PCI Level 1 vault and in the customer's wallet, never on your agent or your servers, and never read aloud on the call. That keeps card data out of your PCI scope.

Where does the money go? Do you hold our funds?

No. Every charge settles directly on the processor you already use. Ringup collects the payment on the call but never sits in the funds flow, and never becomes a new account you have to reconcile.

How do we add Ringup to our agent?

Two ways. From the Ringup dashboard, connect your voice platform, pick the agents that take payments, and Ringup provisions the payment tool: at payment time the call transfers to Ringup's hosted payment line. Or keep the caller in your own stack with the REST API: recognize the caller, create a Checkout Session, and transfer the call. Either way, Ringup recognizes the caller by phone number, charges their saved card on the merchant's own processor, and no card number is read aloud. Full setup is at docs.ringup.dev.

07 — Request a demo

Ready to get started?

Tell us what you're building and we'll get you a key. We're onboarding a handful of voice-AI teams now.