Text-to-pay vs counter payments: when each one wins

Five years ago, every shop took payment one way: card or cash at the counter when the customer came to pick up. The card reader sat by the receipt printer. The pickup conversation, the warranty handoff, and the payment all happened in the same 90 seconds.

That works when 100% of pickups happen during business hours. It doesn't work when 30% of your pickups now happen after-hours via a key drop, when commercial customers want to pay over Net 30, or when grandpa's mower is being picked up by his daughter who lives three states away.

Text-to-pay solves a real problem — but only sometimes. Here's how to think about when to use it.

Counter payments win when:

• The customer is standing in front of you. Friction is zero, processing fees are slightly lower (Stripe Terminal vs. Payment Links), and the warranty handoff plus payment plus key transfer all happen in one conversation.
• It's a commercial account paying COD. They expect to swipe at the counter, sign a paper receipt, and walk out with a printed invoice for their bookkeeper.
• The job is under $50. The 30 seconds saved by skipping the card reader doesn't outweigh the 2 minutes of "did you get my text?" you'll spend later.

Text-to-pay wins when:

• After-hours pickup. Customer wants to grab the unit on Saturday morning before the shop opens. Send the link Friday night, they pay before they show up, key is in the lockbox.
• Out-of-town drop-off. Snowblower came in via a delivery service and is going back via the same. The customer has never set foot in your shop and shouldn't have to.
• Commercial customer paying weekly. Generate a payment link for the week's tickets. They pay it Friday, your books reconcile Monday, no awkward "you still owe us" call.
• Approving and paying for the estimate together. Send the estimate as a text. If they want to approve and pay the deposit, the same text has the link.

The trap: don't text-to-pay in person

The single biggest mistake we see: shops that have a card reader on the counter but text the link "for convenience" while the customer is standing right there. The customer feels like they're being held up, processing fees are slightly higher on Payment Links, and you've turned a 30-second card swipe into a 4-minute "let me find my reading glasses" moment.

If they're at the counter, run the card.

Processing fees, plainly

You'll see roughly the same rate either way — somewhere around 2.6% + $0.10 per transaction on Stripe Terminal or Payment Links. The fee differential between in-person and online card-not-present is real but small (often the difference between a 0.05% incentive on swipe vs. tap). Don't optimize processing fees. Optimize for whether the customer feels respected.

How a small shop should set this up

You only need three things:

1. A card reader at the counter. Stripe Terminal is the standard. Tap-to-pay on a recent iPhone works as a backup.
2. The ability to generate and send a payment link from a ticket — the link should know the ticket number, the customer's phone, and the amount.
3. A clear expectation set at intake. Tell the customer at drop-off: "When it's done I'll text you with what you owe — you can pay the link or pay when you pick up. Whatever's easier." Most will pay the link. The good ones will tip you.

That's it. Same software handles both flows, customer picks the one that fits their day, you stop chasing money on Saturday afternoon.