Stripe Terminal: Unified In-Person Payments with Stripe

Businesses today need seamless, unified payment solutions that work both online and in person. Stripe Terminal is designed to meet this need by allowing businesses to integrate Stripe payments into their existing in-person checkout flow, unifying all transactions under a single platform. This guide is for businesses and developers looking to unify their in-person and online payments using Stripe Terminal. We cover features, hardware options, integration paths, security, and operational management, ensuring you have a comprehensive understanding of how Stripe Terminal can streamline your payment processes.

Whether you’re a retailer, service provider, or platform operator, Stripe Terminal offers the tools and flexibility to accept secure in-person payments, manage devices, and reconcile sales across all channels. Read on to discover how Stripe Terminal can transform your point-of-sale experience.

Key Takeaways

• Stripe Terminal enables businesses to accept secure in-person card payments using Stripe’s platform, a selection of pre-certified readers that accept various payment methods, including EMV and contactless, and Tap to Pay on compatible mobile devices.
• Terminal unifies online and in-person transactions under a single Stripe account, with shared reporting, payouts, and customer data—eliminating the need to reconcile separate payment processors.
• Developers can integrate Terminal via SDKs for iOS, Android, JavaScript, and React Native, while non-technical teams can leverage low-code or third-party POS solutions.
• Businesses choose between dedicated EMV card readers for high-volume environments and Tap to Pay on iPhone or Android device options for mobile staff, deliveries, and pop-up events.
• Stripe handles encryption, PCI compliance, and centralized device management through the Stripe Dashboard, reducing operational burden and security scope for merchants.

What Is Stripe Terminal?

Stripe Terminal allows businesses to integrate Stripe payments into their existing in-person checkout flow. It’s not just hardware—Terminal combines pre-certified readers, SDKs, APIs, and dashboard tools into a unified commerce experience that bridges your online and offline sales.

The key distinction from standard Stripe Payments is that Terminal extends your existing Stripe account into physical locations. A retail store or café can use Stripe Checkout for online orders and Stripe Terminal at the counter, with all transactions appearing in the same reports and sharing the same customer profiles.

Core components of Stripe Terminal:

• Pre-certified card readers (Stripe Reader S710, BBPOS WisePOS E) that accept various payment methods, including EMV and contactless
• Tap to Pay on compatible iPhone and Android devices, allowing businesses to accept contactless payments without extra hardware
• Client-side SDKs for iOS, Android, JavaScript, and React Native
• Server-side Terminal APIs and SDKs for payment processing
• Stripe Dashboard for device management, reporting, and configuration

Next, let’s explore the core features and capabilities that make Stripe Terminal a powerful solution for unified in-person payments.

Core Features and Capabilities

Payment method support

• EMV chip card acceptance for secure, authenticated transactions (EMV refers to cards with embedded microprocessor chips for enhanced security)
• NFC contactless payments, including contactless cards and digital wallets
• Apple Pay and Google Pay support across all Terminal hardware and Tap to Pay
• Magstripe swipe is regionally supported (availability varies by country)

Tap to Pay options

• Tap to Pay on iPhone works on iPhone XS or later running iOS 16.4+, allowing merchants to accept contactless payments without additional hardware
• Tap to Pay on Android supports NFC-enabled devices like recent Samsung Galaxy or Google Pixel models, turning any compatible phone or tablet into a payment terminal
• Businesses can use Tap to Pay on compatible iPhone and Android devices to accept contactless payments without extra hardware

Unified reporting and reconciliation

• In-person and online transactions share the same payouts and account view
• Customer profiles sync across channels, enabling consistent service and insights
• Dispute handling and refunds are managed from one Dashboard location
• Payment data flows into the same analytics you use for e-commerce

Subscription and recurring billing integration

• Save cards on file during in-person transactions for future charges
• Kick off recurring billing via Stripe Billing from an in-store sign-up
• Handle subscription renewals and payment method updates seamlessly

Multi-location and fleet management

• Manage devices across stores, pop-ups, and field staff from the Stripe Dashboard
• Group readers by location for organized reporting and configuration
• Push firmware updates remotely without manual intervention

Platform and marketplace support

• Connect with Stripe Connect to onboard and manage merchants under one platform
• Provision readers to sub-merchants automatically
• Route transactions to the correct connected account with built-in reporting

Next, let’s look at the hardware and device options available with Stripe Terminal.

Stripe Terminal Hardware and Tap to Pay Options

Stripe Terminal supports both dedicated card readers and device-only Tap to Pay experiences, giving businesses flexibility to mix and match based on their operational needs.

Pre-certified Card Readers

Stripe Terminal offers a selection of pre-certified readers that accept various payment methods, including EMV and contactless. In higher-volume or mobile environments, merchants may also evaluate Android handheld POS terminals with EMV, chip & PIN as part of their broader device strategy.

• Stripe Reader S710:
  • Portable, all-in-one reader with built-in display and PIN pad
  • Supports EMV chip, tap, and swipe (where regionally available)
  • Wi-Fi connectivity with an optional dock for countertop use
  • Ideal for mobile sales staff, table-side ordering, or flexible checkout stations
• BBPOS WisePOS E:
  • Countertop smart reader with a larger touchscreen display
  • Suitable for staffed checkouts, kiosks, and high-volume environments
  • Supports custom splash screens and receipt configurations
  • Built for durability in busy retail or hospitality settings
• Other hardware options:
  • Regional availability varies—check Stripe’s hardware page for current offerings
  • Legacy readers like the BBPOS WisePad 3 may be available in specific markets
  • All Stripe-certified readers support end-to-end encryption by default and are EMV certified, and some merchants may complement these with Android handheld POS systems with integrated printers in retail settings that require on-the-spot receipts.

Tap to Pay

• Tap to Pay on iPhone:
  • Compatible iPhone models (XS or later) with supported Stripe integration
  • Accept contactless cards and digital wallet payments with no reader purchase
  • Perfect for deliveries, field services, and mobile pop-up events
• Tap to Pay on Android:
  • Most recent NFC-enabled Android phones and tablets supported
  • Similar functionality to iPhone—turn any compatible Android device into a terminal
  • Reduces hardware costs for businesses with distributed mobile teams

Businesses can use Tap to Pay on compatible iPhone and Android devices to accept contactless payments without extra hardware.

When to choose dedicated hardware vs. Tap to Pay

Scenario	Recommended Option
High-volume retail counter	BBPOS WisePOS E or S710 with dock
Mobile staff or deliveries	Tap to Pay on iPhone or Android device
Pop-up events or markets	Tap to Pay or portable S710
Customer-facing kiosk	BBPOS WisePOS E with custom display
Field technicians	Tap to Pay on phone or tablet

How Stripe Terminal Works Under the Hood

Stripe Terminal bridges your application, Stripe’s APIs, and payment hardware into a cohesive system. The architecture handles encryption, card network rules, and tokenization so merchants never touch raw card data directly.

Client-side SDK responsibilities

• Discover available readers via Bluetooth, USB, or internet connection
• Collect encrypted card details from the reader
• Handle the tap/insert/swipe user experience
• Send tokenized payment information to Stripe securely

Server-side API role

• Create Payment Intents that authorize and capture charges
• Link transactions to customers, orders, or invoices
• Process refunds and manage disputes
• Serve as the source of truth for all payment records

Data flow and tokenization

• Card data is encrypted at the reader before transmission
• Encrypted data passes through Stripe’s infrastructure to secure HSMs
• Only tokens reach your backend—never raw card numbers
• This approach scopes PCI compliance to Stripe’s validated solutions

Device management

• Firmware updates pushed remotely via Dashboard or API
• Activation codes generated for linking readers to test or live environments
• Reader configurations are managed without physical access to devices, and larger retailers may coordinate this alongside a broader fleet of advanced POS systems and hardware for retail and hospitality.

Example transaction flow

1. Cashier initiates a Payment Intent via the POS app
2. Reader prompts customer to tap, insert, or swipe
3. Terminal SDK collects encrypted payment details
4. Stripe processes the transaction through card networks
5. Success status returns to the app, and reports update in real time

Now that you understand the technical workflow, let’s explore integration paths and developer tooling for Stripe Terminal.

Integration Paths and Developer Tooling

Stripe Terminal provides SDKs built for modern development environments to facilitate integration, allowing for the development of custom POS applications tailored to specific business needs.

SDK options

• iOS SDK (Swift/Objective-C): Native integration for iPhone and iPad POS apps
• Android SDK (Kotlin/Java): Full support for Android device deployments
• React Native SDK: Cross-platform option for teams using React Native
• JavaScript SDK: Browser-based or desktop environments, ideal for web POS

Integration modes

• Server-driven integration: Connect a reader directly to a browser or desktop app with server-managed flows
• Local SDK mode: Mobile devices running native apps handle reader communication directly
• Choose based on your deployment model and whether devices are always connected to a server

Typical integration process

1. Design your POS flow and identify hardware requirements
2. Order readers through the Dashboard and generate registration codes
3. Implement the client SDK for reader discovery and payment collection
4. Build backend API calls for Payment Intents, captures, and refunds
5. Test thoroughly in test mode with simulated readers and test cards
6. Deploy to production and monitor via Dashboard

Platform integration with Connect

• Provision readers for connected merchants automatically
• Associate transactions with the correct connected account
• Ship devices directly to sub-merchants through Dashboard ordering
• Handle multi-merchant reporting from one platform view

Testing recommendations

• Use Stripe’s test mode before going live
• Test cards simulate various scenarios (approvals, declines, specific card types)
• Simulator options available for development without physical hardware
• Validate edge cases like network outages and reader disconnections

With integration options in place, let’s move on to security, compliance, and encryption with Stripe Terminal.

Security, Compliance, and Encryption

Stripe Terminal supports end-to-end encryption for secure transactions by default, ensuring sensitive card data is protected throughout the payment process.

End-to-end encryption (E2EE)

• Card data is encrypted at the reader before transmission
• Data remains encrypted until it reaches Stripe’s secure environment
• Pre-certified hardware ensures encryption is always active
• Merchants never handle or store raw card data

PCI DSS compliance

• Stripe is PCI DSS Level 1 certified (the highest level)
• Using Terminal significantly reduces the merchant PCI scope
• No need for custom certification of payment hardware
• Tokenization keeps sensitive data off merchant systems

Point-to-point encryption (P2PE)

• Optional PCI-audited P2PE solution for high-compliance industries
• Ideal for healthcare, education, government, and similar sectors
• Further minimizes audit burden and compliance costs
• Requires following Stripe’s P2PE Instruction Manual (PIM) for secure handling

P2PE requirements

• Secure installation and storage of card readers
• Documented handling procedures for devices
• Proper decommissioning of retired hardware
• Staff training on secure practices

Ongoing security assurance

• Stripe undergoes regular independent security assessments
• Remote device management prevents unauthorized firmware changes
• Lost or stolen devices can be deactivated from the Dashboard immediately
• All supported readers are pre-certified—no custom certification work required

With security and compliance addressed, let’s see how Stripe Terminal is used across different industries and business models.

Use Cases and Industry Examples

Terminal’s flexibility supports everything from single-store retailers to large platforms serving thousands of merchants. Here are concrete examples across different business types.

Retail operations

• Multi-location boutiques using Terminal at checkout counters and pop-up events
• Inventory and customer data synced across all locations through unified Stripe reporting
• Same payment data available whether the sale happens online or in person, and retailers can complement software integrations with high-quality POS systems for retail and business to optimize in-store operations.

Field services

• Technicians, consultants, and home-visit professionals accepting payment on site
• Tap to Pay on iPhone or Android device eliminates the need for dedicated hardware, though some teams may prefer mobile handheld POS devices for rugged field use and integrated peripherals.
• Process payments immediately after completing service calls

Platform and marketplace deployments

• SaaS providers for gyms, salons, or barbershops embedding Terminal SDK into their POS
• Each business accepts in-person payments with its own connected account
• SQUIRE, for example, enabled barbers to accept contactless payments via smartphones, adapting to the shift toward cards and digital wallets, while fitness businesses can pair Terminal with a dedicated gym POS system with billing, check-ins & memberships to manage member operations.

Subscription and membership sign-ups

• Gyms and clubs are signing up members in person and starting recurring billing
• Card saved on file during in-store transaction, future charges handled automatically
• Stripe Billing integration makes the handoff seamless, and retailers offering memberships or loyalty programs can also enhance self-service experiences with retail price checker kiosks that verify barcodes and pricing on the sales floor.

Non-profit and event scenarios

• On-site donations processed through Terminal with unified reporting
• Event ticket sales in person synced with online sales data, and venues can supplement staffed checkouts with self-service kiosks for touchscreen ordering and payment to reduce queues.
• Single view of all product sales and donations in the Dashboard

Next, let’s review how to manage and scale Stripe Terminal operations across teams and locations.

Operational Management and Scaling with Stripe Terminal

Stripe provides tools for ordering and managing card readers from the Stripe Dashboard, making day-to-day administration, device logistics, and scaling across teams and locations straightforward.

Ordering and setup

• Order readers directly through the Stripe Dashboard
• Track shipments and manage delivery logistics from one place
• Devices arrive ready for activation—no complex setup required

Reader activation

• Generate registration codes in the Dashboard
• Link readers to test or live environments as needed
• Assign devices to specific locations or teams for organized management

Remote management capabilities

• Monitor reader status and connectivity in real time
• Push firmware updates automatically without physical access
• Configure Wi-Fi certificates or connectivity settings remotely
• Deactivate lost or stolen devices immediately

Roles and permissions

• Admins manage hardware, view reports, and configure settings
• Staff roles can handle transactions and refunds without hardware access
• Role-based permissions protect sensitive operations and reporting

Scaling scenarios

• Open new stores and deploy readers through the Dashboard ordering
• Onboard seasonal staff with minimal training on device setup
• Provision devices to franchisees or partner locations via Connect, while leveraging comprehensive POS solutions and services for retail and hospitality for deployment, training, and long-term support.
• Manage multi-store fleets with location-based grouping and reporting

Now, let’s compare Stripe Terminal to alternative in-person payment options to help you evaluate the best fit for your business.

Stripe Terminal vs. Alternative In-Person Payment Options

When evaluating Terminal against other options, consider how it fits your existing infrastructure and growth plans. This comparison focuses on conceptual differences rather than specific competitor products.

Compared to stand-alone terminals

Factor	Stripe Terminal	Traditional Stand-Alone
Payouts	Unified with online	Separate merchant account
Reporting	Single Dashboard	Separate reconciliation
Customer data	Shared profiles	Siloed systems
Integration	API-first	Often closed/proprietary

Compared to legacy POS systems

• Terminal’s APIs and SDKs offer flexibility that closed systems lack
• Build custom workflows in your app rather than adapting to rigid software
• Modern SDK support for iOS, Android, React Native, and JavaScript

Compared to generic mobile readers

• Easy initial setup with basic readers, but limited customization
• Terminal scales with deeper integration options as businesses grow
• Server-driven integration and local SDK modes provide flexibility

Advantages for existing Stripe users

• Extend your existing account to in-person sales without new providers
• Same familiar Dashboard, reporting, and support resources
• No need to juggle multiple payment relationships or reconcile across systems

With these comparisons in mind, let’s address some frequently asked questions about Stripe Terminal.

FAQ

Do I need to be a developer to use Stripe Terminal?

While Terminal is primarily built for developers, non-technical businesses have options. Implementation partners and no-code/low-code tools built on Stripe can handle the technical work. Some prebuilt payment app solutions and third-party POS systems integrate with Terminal out of the box. Setting up hardware and basic settings in the Dashboard is straightforward, but custom workflows and POS logic require development effort.

Which countries currently support Stripe Terminal?

Terminal availability varies by country, and hardware options differ across regions. The US, Canada, UK, and EU nations have strong support, with Australia and additional markets following. Check Stripe’s official Terminal availability page for the current list—coverage changes as Stripe expands. Contact sales for specific regional requirements.

Can I use my existing card readers with Stripe Terminal?

Stripe Terminal works only with pre-certified card readers and compatible Tap to Pay iPhone and Android devices to ensure encryption, compliance, and SDK compatibility. Generic, off-the-shelf terminals usually cannot connect directly to the Terminal. If you have existing hardware, check Stripe’s supported hardware list—otherwise, plan to purchase Stripe-certified devices.

How does pricing work for Stripe Terminal?

Terminal pricing typically includes a per-transaction fee similar to online payments (around 2.9% + 30¢ in the US, varying by region and volume), plus one-time hardware purchase costs if using physical readers. Tap to Pay options avoid hardware costs. Custom pricing is available for companies with large payment volumes or specific integration needs—consult Stripe’s pricing page or contact sales for tailored quotes specific to your sales volume.

What happens if my internet connection goes down?

Most Terminal setups require a stable network to process payments in real time, preventing declined or duplicate transactions. Some POS implementations support limited offline behavior by queuing transactions for later sync, but merchants must weigh the risk of offline approvals. Running a stable internet connection is strongly recommended—check Stripe’s documentation for current offline capabilities and supported configurations.

---

With this guide, you now have a comprehensive overview of Stripe Terminal, including what it is, hardware options, integration paths, security, use cases, and operational management. Stripe Terminal allows you to integrate Stripe payments into your existing in-person checkout flow or build in-person payments into your native mobile or web-based application, providing a unified and secure payment experience for your business.