Paid Before They Hang Up
If the caller has paid you before, you already have their card. Charge it while they are still talking, and the ticket is on the pass before they hang up.
On this page
A caller orders, hangs up, gets a text, taps it, types a card, and the ticket prints somewhere between thirty seconds and thirty minutes later. If they get distracted, it never prints at all.
That was the old trade, and it was worse than it looked. The food waited. The counter had to chase it. And sometimes nobody noticed.
Now, if the person calling has paid you before, you already have their card. Charge it while they are still talking, and the ticket is on the pass before they hang up.
TL;DR:
- A returning customer's card is charged while they are on the phone, and the ticket reaches the kitchen during the call.
- A first-time caller gets a text link, the line stays open, and they hear the payment go through.
- Paying a link keeps the card on file, so the second order is quicker and the third is a one-touch charge.
- No card number is ever read to the agent, recorded, or written down.
- Processing is 2.9% + 30¢ at Stripe, against 15%–30% for a delivery app.
Why the link was never good enough
A payment link is an honest compromise, and it is still worse than being paid.
Three things go wrong with a link:
- The order waits. Nothing prints until the payment clears, so the pickup time you quoted starts after they have finished typing.
- Some people never pay. A cart abandoned on a payment page is a ticket the kitchen has already planned around.
- Someone has to chase it. A staffer notices an unpaid order and has to decide whether to cook it, call back, or bin it.
None of that happens if the card is already on file.
How it works, in plain terms
Four things, and only the last one involves the customer saying anything.
- They call. You know the number, so you know it is the caller who ordered last Friday.
- You have their card. They paid a link once, and Stripe kept the card against their number.
- They confirm the order. It is read back the way it will print.
- It is charged while they are still talking. The ticket goes to the kitchen, and they hear the total they are paying.
The one phrase worth knowing is "on file". That is the whole trick: the first payment saves the card, and every call after that is a charge, not a conversation about digits.
The first-time caller
Every restaurant has them, and the honest answer is different for them.
A caller with no card on file gets a text with a payment link. The line stays open while they pay, and they hear it go through. That is already better than the old flow, because they are not left wondering whether the order landed.
Paying that link keeps the card on file. The next call from that number is a one-touch charge. A pizzeria with a lot of regulars gets to the good version within a month. A shop with mostly new customers spends that month building it.
What the caller hears
The payment is part of the conversation, not a handoff to a page:
"That's a large half-mushroom half-pepperoni, extra crispy, a dozen knots, and a two-liter. $47.80. The card ending 4412 is on file — put it on that?"
If they say yes, it is charged and the order is confirmed. If they want to use a different card, they get the link instead.
What nobody does is read a card number aloud. That is the line that keeps a recording clean and keeps your staff out of it.
Some shops still take it at the counter
Not everyone wants to charge a card before the food is bagged, and that is fine.
With cards off, the order is confirmed on the call and paid when the customer collects. Nothing touches a card in the call, the ticket prints straight away, and the till does what it has always done. For a small counter with regulars who pay cash, that is the simpler setup and it is the one to start with.
The trade is the one you already know: an order that is placed but not paid can still walk. If that happens rarely, keep it. If it happens on a Friday, turn the card path on and let a returning caller pay while they talk. The chat on your website uses the same link, so a customer who would rather type gets the same experience as one who calls.
Where the money lands
The customer, the saved card, and the charge all have to be in the same place: the restaurant's own Stripe account when one is connected, otherwise the platform account.
That is a setup step, not a decision you make mid-service. Connect Stripe before the first paid order, or you end up with customers split across two accounts and a refund that does not match the charge.
The cost of getting paid
Stripe charges 2.9% plus 30 cents on a successful US card charge. On a $40 order that is about $1.46.
Put it next to the alternative. A delivery app takes 15% to 30%, which is $6 to $12 on the same $40, and closer to $12 to $16 all-in with promotions. Processing was never the expensive part of the order. The marketplace is.
What to try before you switch the line
- A first-time caller. Order, take the link, pay, and watch the ticket print only after payment.
- Call back from the same number. The card should be offered, not asked for.
- A different card. The link should still work without wiping the card on file.
- A declined card. Find out exactly what the caller hears and whether the order falls back to a link or stops.
- A refund. Confirm it goes against the same account the order used.
- The ticket. It should print at payment, not before, and show the amount the caller heard.
The Toast walkthrough shows where the ticket lands once it is paid, and the pricing page has the plan arithmetic. If yours is a shop where callers ask for a table as often as a pizza, the reservation book covers the other half of the call.
FAQ
Do I have to read card numbers to the agent?
No. Nobody reads a card number on a call. When a customer pays a link once, the card is kept safely with Stripe against their number. After that, the card can be charged while they are still talking, and no number is ever spoken, recorded, or written down.
What happens the first time someone orders?
They get a text with a payment link. The line stays open while they pay, and they hear it go through. Paying the link keeps the card on file for next time, so the second call is a one-touch charge and the third is even faster.
What if the card is declined?
Ask the demo to show you. The order should not go to the kitchen on a declined charge; the caller should hear the problem and be offered the link or another card. Test it with a real card before you switch the line over, and check how a refund is handled on the same account the order used.
Where does the money go?
To the restaurant's own Stripe account when one is connected, otherwise to the platform account. It has to be one place: the customer, the saved card, and the charge all live on the same account, which is why you connect Stripe before the first paid order rather than after it.
What does card processing cost?
Stripe's standard US rate is 2.9% plus 30 cents per successful charge, so a $40 order costs about $1.46. Compare that with a delivery app taking 15% to 30%, which is $6 to $12 on the same ticket.
Final Thoughts
Getting paid on the call is not really about the card. It is about the gap between "ordered" and "on the pass", and for a regular customer that gap is now nothing.
A returning caller's card is charged while they talk. A new caller pays a link and hears it land, and next time they are a regular too. Take a test call and pay for one order yourself.