programcode

Review · Payment APIs

Stripe Terminal review

A fit for teams already using Stripe, but confirm device support, integration needs and per-transaction costs before rollout.

6.2/10ProgramCode score

We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money

The bottom line

A way to bring in-person payments into Stripe, with transaction and reader costs to model.

Stripe Terminal is Stripe’s in-person payments offering, alongside its online payment products. Stripe says businesses can take in-person payments from the Dashboard without coding, or use APIs for third-party connections and custom workflows.

The listed pricing is pay-as-you-go: card processing fees apply per successful charge, with separate costs for reader hardware, Tap to Pay and optional P2PE. Terminal makes most sense for businesses already building around Stripe; the available information does not establish the SDK, device or rate-limit details a production integration needs.

Good fit if

  • Businesses already using Stripe
  • Teams unifying online and in-store payments
  • Merchants wanting Dashboard-based payment options

Skip it if

  • Teams needing self-hosted payment infrastructure
  • Buyers requiring published rate limits
  • Merchants choosing solely on lowest fees
Stripe Terminal homepage
Stripe Terminal homepage, captured Nov 6, 2026

ScoresHow it rates

  • Features6
  • Ease of use7
  • Value for money6
  • Support6
  • User sentiment5

What works

  • Supports in-person payments alongside online payments
  • Dashboard option for taking in-person payments without coding
  • APIs can support third-party connections and custom workflows
  • Stripe lists support for 135+ currencies and payment methods
  • Connect is described by a customer as an integrated solution

What doesn't

  • Terminal-specific SDK and language details are not established here
  • Processing fees vary by card category
  • Reader hardware and enabled-reader data cost extra
  • No self-hosting, licence or data-export terms are published on the homepage
  • Confirm device compatibility and API limits before production

01What Stripe Terminal is, technically

Stripe Terminal is Stripe’s offering for accepting payments in person. Architecturally, it sits in Stripe’s hosted payments stack: a business accepts an in-person payment through Stripe, alongside the company’s online payments. It is not presented on Stripe’s homepage as a self-hosted server, standalone point-of-sale system or local payment processor.

The integration can be no-code or API-connected. Stripe says businesses can take in-person payments from the Dashboard without coding, while its APIs can connect third parties and support custom workflows. That gives merchants a Dashboard route and developers a way to connect Terminal to their own systems. A customer quote describes Terminal and Connect as an integrated solution, but the homepage does not establish a required Connect dependency. For an existing Stripe business, the architectural appeal is keeping online and in-person payments within one provider; the precise reader-to-application setup depends on the integration and device.

02Stripe Terminal API, SDKs and docs

Stripe describes APIs as a way to connect third parties and support custom workflows, but its homepage does not name a Terminal API style, SDK, programming language, CLI or plugin. It also promotes taking in-person payments from the Dashboard without coding. Developers should confirm current Terminal SDK support, supported languages, reader connections and integration steps in Stripe’s Terminal documentation before choosing an architecture.

The available integration surface is therefore API-based custom work or the Dashboard’s no-code option. A customer quote names Terminal and Connect together, but that does not make Connect a documented requirement for every integration. If the project depends on a particular client framework, mobile platform or backend language, verify support with Stripe before committing. Ask which integration path handles reader discovery, payment creation and device management for the hardware you plan to deploy; the homepage does not provide those implementation details.

03Stripe Terminal pricing for developers

Stripe lists one Terminal plan: Standard (pay-as-you-go), charged per successful charge. EEA and UK cards cost 1.4% + €0.10; other cards cost 2.9% + €0.10. Those rates make card mix relevant to your transaction-cost model. There is no monthly or annual Terminal plan listed, and no free Terminal plan is listed.

Add-ons increase the bill. Tap to Pay adds €0.10 per authorisation, and optional P2PE adds €0.05 per authorisation. Reader prices are €59 for BBPOS WisePad 3, €199 for BBPOS WisePOS E, and €259 each for Stripe Reader S710 and S700; prices exclude VAT. Enabled-reader data costs €9 per reader per month, and Apps on Device is limited to 10 GB per reader per month. Model processing, hardware, data and any enabled add-ons separately. The listed rates are in euros; confirm applicable pricing for your market and setup with Stripe.

Full Stripe Terminal pricing breakdown →

04Stripe Terminal: open source, self-hosting and lock-in

Stripe’s homepage presents Terminal as a Stripe product and does not publish a Terminal source-code licence, a self-hosting option or data-export terms. Treat it as a hosted Stripe service unless Stripe confirms otherwise for your integration; the homepage does not establish that Terminal’s server components can be deployed in your own infrastructure.

That architecture ties payment processing to Stripe. If you migrate to another processor, expect to replace the Stripe-specific payment flow and review how payment records, customer data and reconciliation move to the new system. Stripe lists APIs for connecting third parties and custom workflows, but that is not a stated guarantee of portable data or a processor-independent integration. Ask Stripe about exports, retention and migration support before relying on Terminal as the only source for payment operations.

05Stripe Terminal in production

Before rollout, verify supported readers, connection modes, API limits, availability terms and the compliance responsibilities for your specific integration. The listed Terminal pricing does not state API rate limits. Stripe’s homepage reports 99.999% historical uptime for Stripe services overall, but that figure is not a Terminal-specific availability commitment. Confirm whether the service-level terms you need apply to your account and deployment.

Reader connectivity can affect architecture. In one Reddit thread, a commenter says WisePOS E and S700 support Stripe’s server-driven API, while other models use Bluetooth or local network connections. Treat that as a prompt to verify the current supported setup with Stripe, not as a substitute for device documentation. Reddit discussions also surface implementation friction: a Capacitor developer described errors initializing and connecting the NFC reader, and another thread includes a report of Android build issues. These are individual reports, not evidence of a general failure rate, but they make device-specific testing and a fallback payment path important.

From the threadsWhat users say

Reddit comments describe Terminal’s value as keeping in-person payments in the Stripe stack, but discussions also show uncertainty around device setup and integration details. The small number of comments includes individual implementation problems, so sentiment is mixed rather than conclusive.

Unified payment operations
reporting, payouts, and reconciliation all live in one place
r/stripe · view thread
Integration friction
I get errors trying to Initialize and connect the NFC reader
r/capacitor · view thread
Remote reader questions
From the docs it really does look like Stripe terminals can't support remote connections
r/stripe · view thread

Questions people ask

Can I use Stripe Terminal without building a POS?

Stripe says businesses can take in-person payments from the Dashboard without coding, so a custom POS is not the only route. Confirm that the Dashboard option supports your intended devices and payment flow before buying hardware.

Does Stripe Terminal work with online Stripe payments?

Stripe presents Terminal as its in-person payments offering and describes its products as supporting payments online and in person. A customer quote describes Terminal and Connect as an integrated solution. Confirm the specific data and workflow sharing you need with Stripe.

What does Stripe Terminal cost per transaction?

The listed Standard (pay-as-you-go) rates are 1.4% + €0.10 per successful charge for EEA and UK cards, and 2.9% + €0.10 for other cards. Tap to Pay and optional P2PE have additional per-authorisation fees.

Can I control a Stripe Terminal reader remotely?

A Reddit commenter says WisePOS E and S700 support Stripe’s server-driven API, while other models use Bluetooth or local network connections. Verify the current supported devices and connection requirements in Stripe’s documentation before selecting a reader.

Which Stripe Terminal reader should I buy?

The listed hardware prices are €59 for BBPOS WisePad 3, €199 for BBPOS WisePOS E, and €259 for Stripe Reader S710 and S700, excluding VAT. Choose only after confirming the device supports your integration and required connection mode.

Sources

  1. Stripe Terminal homepage
  2. Stripe Terminal pricing page
  3. Reddit: Getting a Stripe Terminal - What do I need to know?
  4. Reddit: Anyone have experience with Stripe Terminal?
  5. Reddit: Stripe Terminal tap to pay
  6. Reddit: Does Stripe really not support remote connections to terminals?