Stripe Terminal: A Founder's Guide to the Hardware Nobody Told You Was Optional (2026)

The Card Reader I Almost Bought for a Product That Lived in a Browser

In 2024, I went down a very stupid rabbit hole. I was sketching out a booking tool — a little SaaS for salons and small studios, the kind of thing where someone books a slot online and pays. Classic software. Lives in a browser. And somewhere in the research, I opened Stripe’s dashboard, saw a product called Stripe Terminal, and thought: ooh, hardware. Card readers. Maybe I should sell those too.

I spent an evening pricing out card readers for a product where nobody would ever stand at a counter. That’s the Broken Engineer disease in one sentence — optimizing for a problem I didn’t have, on a product with zero users.

So let me save you that evening. This is what Stripe Terminal actually is, what the boxes cost in 2026, and the one honest question most guides skip: do you, a software founder, need any of this? (Spoiler that I’ll earn later: probably not.)

---

What Stripe Terminal Actually Is

Here’s the thing everyone gets confused about. Regular Stripe — the Stripe you already know — is for card-not-present payments. Someone types their card into a checkout form on your website. That’s it. That’s 99% of what a SaaS founder ever touches.

Stripe Terminal is the opposite. It’s Stripe’s in-person, card-present product. A physical card reader on a counter, or a phone tapped against a customer’s card, wired back into the same Stripe account you already have. Same dashboard, same payouts, same API keys — but now the money comes from someone physically standing in front of you.

It’s two things bolted together:

1. Hardware — the actual card readers. Little terminals that do tap, chip, and swipe.
2. An SDK — so your own app (a point-of-sale app, a kiosk, a mobile app your staff carries) can drive that hardware and take the payment.

That’s the whole idea. Terminal exists so that a business with both an online store and a physical presence can run everything through one payment processor instead of duct-taping Stripe for the web and some separate clunky terminal for the counter. Omnichannel, if you want the buzzword. One ledger for online and offline.

---

The Readers (and What They Cost in 2026)

Stripe sells the hardware directly from your dashboard, at cost, no markup. Here’s the 2026 US lineup, from cheapest to fanciest:

Reader	Price	What it’s for
Stripe Reader M2	$59	Pocket reader, pairs with your phone/tablet over Bluetooth. Pop-ups, markets, trade shows.
BBPOS WisePad 3	$59	Same mobile-companion idea, PIN pad built in.
BBPOS WisePOS E	$249	Countertop Android touchscreen. Runs your POS app right on the device.
Stripe Reader S700	$349	The flagship. 5.5-inch touchscreen smart reader, WiFi/Ethernet, built to run your own app on it. There’s a cellular sibling, the S710, too.

The pattern’s simple. If you’re mobile and scrappy — a food stall, a photographer taking payment at a shoot — you grab the $59 M2 and pair it with the phone in your pocket. If you’re a real storefront with a counter, you buy the WisePOS E or the S700 and let it be the whole till.

The readers are made by Stripe and a hardware partner (BBPOS on the cheaper units); you don’t need to care about that beyond knowing the WisePad and WisePOS names when you’re ordering.

The Free Reader: Tap to Pay on a Phone

This is the genuinely cool part, and the one worth knowing even if you never buy a box.

Tap to Pay turns a phone into the card reader. No extra hardware, $0 up front. On Apple’s side, Tap to Pay on iPhone works on an iPhone XS or later — the customer taps their contactless card or their Apple Wallet against the back of your phone, and it’s done. There’s an Android version too, running on NFC-capable, Google-certified devices.

For a solopreneur who occasionally sells in person — you do a workshop, a pop-up, a one-off — this is the move. You don’t buy a $349 terminal to take payment four times a year. You install an app, tap, done. The phone you already own is the reader.

---

What It Actually Costs to Run

Hardware is the one-time cost. The ongoing cost is the per-transaction fee, and in-person is cheaper than online because there’s less fraud risk when the card is physically present.

In the US, in-person payments through Terminal run 2.7% + 5¢ per transaction. On a $100 sale that’s $2.75. Compare that to Stripe’s standard online rate (2.9% + 30¢), and card-present is the better deal — that 30¢ fixed fee online really bites on small tickets.

The one asterisk: Tap to Pay adds +10¢ per authorization on top. So tapping a phone is 2.7% + 15¢. Still fine, and you saved $59–$349 on hardware, so for low volume it’s a no-brainer. There’s also an optional point-to-point encryption surcharge (a few cents) that some industries require — most founders can ignore it.

No monthly fee for Terminal itself. You pay for hardware once, then per-transaction. That’s it.

---

When Terminal Actually Fits

I want to be fair to the product, because it’s genuinely good at its job. Terminal makes sense when:

• You run retail. A shop, a café, a store with a counter. You want tap-and-chip and you want it in the same Stripe account as your website.
• You do events or markets. Pop-ups, festivals, fairs. Grab the $59 M2 or just use Tap to Pay and take cards anywhere.
• You’re building omnichannel software. This is the real developer angle. If you’re building a point-of-sale app — the software a restaurant or retailer actually rings sales up on — Terminal’s SDK is how your app talks to the hardware. You’re not the merchant; you’re building the tool the merchant uses. That’s a legit SaaS, and Terminal is a legit backbone for it.
• You sell a physical thing at a physical place and also online, and you’re sick of reconciling two payment systems.

Notice the thread: every one of those involves the real world. A counter, a stall, a customer standing there with a card.

---

The Broken Engineer Take: You Probably Don’t Need This

Now the part I wish someone had said to me in 2024.

If you’re a pure software SaaS founder — your product is a web app, users sign up online, they pay with a card typed into a checkout form — you do not need Stripe Terminal. Not “you might not.” You don’t. Terminal solves a problem you don’t have. Your customers are never in the same room as you. There is no counter. There is no card to tap.

Reaching for Terminal when you’re building software is like me pricing card readers for a booking tool that lived entirely in a browser tab. It’s a category error dressed up as diligence. Regular Stripe checkout — or Stripe Billing if you’re doing subscriptions — is your entire in-person-payments strategy, because you have no in-person payments.

So why write a whole post telling you to skip it? Same reason I wrote the Bunny CDN story — you need to know a tool exists so you can reach for it the one day you actually need it. The day you add a physical component — you start doing paid workshops, you sell merch at a conference, you build the POS app for a client — Terminal is sitting right there inside the Stripe account you already have. No new processor, no new contract. You flip it on. That’s the value of knowing about it: not using it today, knowing exactly where it is tomorrow.

Knowledge is leverage. The founder who knows Terminal exists can say yes to an in-person opportunity in an afternoon. The one who doesn’t goes and signs up for some clunky standalone POS box and splits their money across two dashboards. Don’t be that founder.

If you’re weighing which payment rail to build on in the first place — online, that is — that’s a different (and more important) fight. I laid out the whole thing, including who owns whom after Stripe’s acquisitions, in Paddle vs Lemon Squeezy.

---

The India Asterisk (Because I’m Indian and I Checked)

Here’s where I have to be honest about my own backyard. I opened the Stripe Terminal devices page from India, and every single reader said the same thing: “Not available in your country.” Pricing showed rupee rates for online products, but the hardware? Blocked.

This isn’t a Terminal quirk — it’s the whole Stripe-in-India situation. Stripe itself is invite-only in India thanks to RBI rules, and the in-person hardware side isn’t a thing you can just order here. So if you’re an Indian founder reading this dreaming about a slick S700 on your counter: pump the brakes. You’ll be looking at domestic players for in-person — Razorpay and the local POS ecosystem, or Square if you’re operating in a market where it’s available (it isn’t India either, really). I wrote up the whole online-payments mess for Indian founders in Stripe alternatives for India — the in-person story is even thinner, so plan accordingly.

For the global shops that build in-person retail software, by the way, Stripe isn’t the only game — Square and Shopify POS live in the same neighborhood, and they bundle more of the retail stack out of the box. But if you’re already a Stripe shop online, Terminal being the same account is the reason to stay.

---

The Bottom Line

Stripe Terminal is a well-built, fairly-priced product for a specific person: someone whose business touches the physical world. Readers from $59 to $349, a free tap-to-pay-on-your-phone option, and a clean 2.7% + 5¢ card-present rate, all wired into the Stripe you already use.

But most of us reading a SaaS blog aren’t that person. We build things that live in browser tabs. And the single most useful thing I can tell you about Stripe Terminal is that you should file it away, know its shape, and not buy a card reader for a product nobody can stand in front of. The day the real world knocks — a workshop, a conference table, a client’s shop — you’ll know exactly where it lives. Until then, close the tab and go get some users. (If that’s the part you’re stuck on, distribution is the actual war, not payment hardware.)

This is the Broken Engineer Guide. I over-engineer everything, price out hardware I’ll never use, fail at business, and hand you the scars so you can skip them. Go build something — online.