Payments for voice agents

Payments built for voice.

Today, getting paid over the phone means asking the caller to read out a 16-digit card number. Ringup makes the phone number the payment identity — your agent recognizes the caller and charges a saved card, or texts a one-tap link to pay.

Get accessSee how it works

Private beta · drops into your existing agent

Caller AI agent
Caller
Hey, I'd like the usual — large oat latte.
Agent
Got it — $6.40. I've got your card ending 4242 on file. Charge it?
Caller
Yep.
Agent · Paid
Confirmation RU-7T29Q — ready in 5.

01 — The problem

Your agent does everything — except take the payment smoothly.

Voice AI books the table, takes the order, files the claim, answers the question. Then it hits the one step it can't make smooth: getting paid. So it falls back to a card number read aloud to a bot, a transfer to a human, or "pay when you get here" — and that's where it breaks.

Order in seconds, then wait in line
Without Ringup

The agent takes the order instantly — but the caller still drives over and stands at the register to pay, increasing wait times for diners and creating more work for staff.

With Ringup

Ringup charges their saved card on the call — the order's prepaid before they leave the house.

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
J
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, they're matched to the payment method they saved last time — no link, no re-entry.

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
Got it — $6.40. I've got your card ending 4242 on file. Charge it?
Caller
Yep.
Agent · Paid
Confirmation RU-7T29Q — ready in 5.

03 — Why Ringup

An internet wallet is not built for phone call payments.

Internet wallets make repeat users login on web or app, making them not suitable for payments over a live phone call. Ringup recognizes the repeat user automatically from carrier identity signals and a voiceprint, so they can pay right on the call.

Other solution

Internet wallets

Made for the web, not the call

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

Designed to pay right on the call
Caller is recognized based on phone number
Identity verified using carrier signals and voiceprint — line type, name, SIM swap
Works on any phone — no app or website needed

04 — Settlement

The money goes straight to the merchant.

Every charge settles directly on the merchant's existing processor. Ringup collects it — never a stop in the funds flow, never a home for your card data.

01

The customer pays

Apple Pay, Google Pay, card, or bank account — in one tap on the call.

02

Ringup secures it

Identity check and a PCI Level 1 vault. Card data never touches your agent or servers.

03

The merchant gets paid

Funds settle directly on the POS or processor they already use. No new account to switch to.

The core idea

The phone number is the account number.

No card read aloud, no app to download, no login mid-call. The line is the identity — recognized, verified, and charged in the conversation.

05 — Get started

Three ways to add Ringup.

Run one line, forward your agent's payment step to us, or wire the API in. Same payment identity underneath, same money-to-the-merchant settlement.

Beta · fastest

One line

The fastest way to add Ringup — run a single command and we wire the rest.

$npx ringup init

Detects your stack, wires the identify and charge tools over MCP, and runs a test charge — works with Retell, Vapi, Synthflow, MCP clients, or your own agent. In private beta: request a key to get access.

No code · hosted

Call forward

Point your agent's payment step at a Ringup number. We pick up, take the payment, and hand the call back — no code on your side.

  • No payment code in your agent at all
  • We manage PCI, identity, and the pay-link UX
  • Result posts back via webhook
forward → +1 (415) 000-RING
Full control · API

REST API

Call Ringup as a tool from inside your agent — identify, then charge. You own the conversation; we own the payment.

  • Drop-in tool for Retell, Vapi, Synthflow, your own
  • Card-on-file detection + carrier identity in one call
  • No PCI scope — card data never hits your servers
POST /v1/charge
{ "phone": "+19255550182",
"amount": 2400,
"processor": "merchant" }
→ { "status": "paid",
"confirmation": "RU-7T29Q" }

06 — Safe by construction

Built for moving money over a phone call.

Letting an agent take payment only works if card data never touches you, and every charge has a verified human behind it.

01

PCI offloaded

Wallets and a PCI Level 1 vault hold the card. It never touches your agent or servers.

02

Carrier-verified identity

SIM-swap, port, and line checks confirm the number before a stored card can be used.

03

Consent ledger

Every approval — the wallet tap, the spoken "yes" — recorded, timestamped, auditable.

04

Your processor

Funds settle on the POS or processor you already use. We stay out of the money flow.

07 — FAQ

Questions, answered.

What is Ringup?
Ringup is the payment 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, carrier signals, and a voiceprint, 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, and carrier checks confirm the SIM hasn't been swapped or the line forwarded) and a carrier-verified identity (the name on file, an identity match, and a voiceprint). 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?
The fastest way is one line — npx ringup init (beta) detects your stack and wires the identify and charge tools over MCP. You can also forward your agent's payment step to a Ringup number (no code), or call the REST API directly. It drops into Retell, Vapi, Synthflow, MCP clients, or your own stack.

08 — Get access

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 for the private beta.