What's the difference between Stripe Terminal and traditional POS systems?

Stripe Terminal integrates directly with your existing Stripe online payment processing, creating a unified view of both digital and in-person transactions. Traditional POS systems operate independently, requiring separate reporting, reconciliation, and customer data management. Terminal shares customer profiles, payment methods, and transaction history across channels, enabling features like in-store pickup for online orders and unified customer support.

Do I need different hardware for different business types?

Hardware selection depends on your operational requirements rather than business type. The [$59 Stripe Reader M2](https://stripe.com/terminal/m2) works well for mobile or low-volume businesses, connecting via Bluetooth to smartphones or tablets. The [$349 Stripe Reader S710](https://stripe.com/terminal/devices) with cellular connectivity suits businesses needing mobility without Wi-Fi dependence. Fixed-location retailers typically choose the [$299 S700](https://stripe.com/terminal/s700) for its large display and custom app capabilities.

Can Terminal work offline without internet connectivity?

Yes, Terminal supports offline payment processing for scenarios with intermittent connectivity. Smart readers store transaction data locally and sync with Stripe's servers when connectivity returns. However, certain features like real-time fraud detection, dynamic currency conversion, and payment method validation require active internet connections during transactions as detailed in the [network requirements guide](https://docs.stripe.com/terminal/network-requirements).

What programming languages and frameworks does Terminal support?

Terminal provides [native SDKs for iOS (Swift/Objective-C), Android (Java/Kotlin), JavaScript, and React Native](https://docs.stripe.com/terminal/references/api). The platform also offers a [server-driven API integration](https://docs.stripe.com/terminal/payments/connect-reader) for businesses preferring backend-heavy implementations. For non-developers, Terminal integrates with [third-party POS systems](https://docs.stripe.com/terminal/features/connect) including Oracle, Lightspeed, and Shopify without code requirements.

How does Terminal pricing compare to other payment processors?

Terminal charges [2.7% + 5¢ per successful transaction](https://stripe.com/terminal) with no monthly fees, setup costs, or per-device charges. This includes EMV processing, device management, security updates, and developer tools. Competitors like Square Terminal charge similar per-transaction rates but often exclude hardware management and API access. Traditional processors typically charge 2.4-3.5% plus monthly fees ranging from $30-200+ for comparable functionality.

Can I customize the checkout experience on Terminal devices?

Smart readers like the [Stripe Reader S700](https://stripe.com/terminal/s700) support extensive customization including itemized cart displays, [custom splash screens](https://docs.stripe.com/terminal/fleet/configurations-overview), and [customer input collection](https://docs.stripe.com/terminal/features/collect-inputs) for signatures or survey responses. The [S700 setup guide](https://docs.stripe.com/terminal/payments/setup-reader/stripe-reader-s700) details how to deploy custom Android applications directly onto smart readers for completely custom experiences.

What happens if my Terminal device breaks or needs replacement?

Terminal includes device management and replacement services through Stripe's hardware support program. Businesses can order replacement devices through the Dashboard or API, with Stripe handling warehousing and shipping. Device configurations and settings sync automatically when replacement readers connect to your account, as detailed in the [configuration overview](https://docs.stripe.com/terminal/fleet/configurations-overview).

Does Terminal support international payments and currencies?

Terminal operates in [50+ countries](https://docs.stripe.com/terminal/overview) and processes payments in [135+ currencies](https://stripe.com/newsroom/information). The platform supports region-specific payment methods including contactless cards, mobile wallets, and local card schemes. Dynamic currency conversion allows international customers to see prices in their home currency, though this feature requires active internet connectivity during transactions.

How secure is Terminal for payment processing?

All Terminal readers maintain [EMV Level 1 and Level 2 certifications](https://support.stripe.com/questions/stripe-terminal-encryption-e2ee-vs-p2pe) with end-to-end or point-to-point encryption for cardholder data. Stripe handles PCI DSS compliance, security updates, and fraud monitoring through its global infrastructure. Point-to-point encryption validation adds [5¢ per authorization](https://stripe.com/terminal) for industries requiring enhanced compliance like healthcare or financial services.

Can Terminal integrate with my existing business software?

Terminal integrates with business applications including inventory management, accounting software, and customer relationship tools through its [Connect platform capabilities](https://docs.stripe.com/terminal/features/connect). Popular integrations include QuickBooks, Xero, Salesforce, and various ecommerce platforms. For custom integrations, Terminal's [comprehensive API](https://docs.stripe.com/terminal/references/api) enables connection to virtually any business system that supports webhook notifications or REST API communication.

Currently viewing the AI version

Switch to human version

Stripe Terminal: AI-Optimized Technical Reference

Platform Overview

Core Function: Unified in-person payment platform extending Stripe's digital infrastructure to physical environments
Scale: Processes $1.4 trillion annually across 50+ countries, 135+ currencies
Architecture: Server-driven with pre-certified card readers, mobile SDKs, cloud device management

Hardware Options and Selection Criteria

Device	Price	Connectivity	Critical Use Cases	Failure Scenarios
M2 Reader	$59	Bluetooth only	Mobile/low-volume (small businesses, pop-ups)	Requires paired device; fails if phone/tablet dies
S700 Wi-Fi	$299	Wi-Fi only	Fixed locations with reliable internet	Unusable during Wi-Fi outages; no cellular backup
S710 Cellular	$349	Wi-Fi + Cellular	Mobile businesses, unreliable Wi-Fi areas	Higher cost for cellular data usage
BBPOS WisePOS E	$249	Wi-Fi + Bluetooth	Traditional retail countertop	Limited customization vs smart readers
Tap to Pay	$0 hardware	Device native	Service businesses, minimal setup	Contactless only; +10¢ per transaction premium

Implementation Requirements

Technical Prerequisites

SDK Options: React Native (community-maintained), iOS/Android native, JavaScript
Integration Flow: Backend connection token → Reader discovery → Payment intent creation
Security: PCI DSS compliant, EMV L1/L2 certified, E2EE/P2PE encryption
P2PE Validation Cost: +5¢ per authorization for enhanced compliance industries

Critical Development Decisions

Architecture Choice Impact:

Server-driven architecture ensures payment data never touches client apps
Real-time processing requires active internet for fraud detection, currency conversion
Offline capability stores transactions locally, syncs when connectivity returns

SDK Selection Consequences:

React Native: Cross-platform but community-supported (potential maintenance risks)
Native iOS/Android: Platform-specific optimizations, first-party support
JavaScript: Web-based POS systems, browser dependency limitations

Pricing Structure and Hidden Costs

Transaction Fees

Standard Rate: 2.7% + 5¢ per successful transaction
Included: Device management, EMV certification, network costs, developer tools
No Monthly Fees: Unlike traditional POS providers charging $30-200+ monthly
Volume Pricing: Custom rates available for large processors

Additional Costs

P2PE Validation: +5¢ per authorization for healthcare/financial compliance
Tap to Pay Premium: +10¢ per contactless transaction on mobile devices
Cellular Data: Variable costs for S710 cellular connectivity
Replacement Hardware: Covered under device management program

Critical Warnings and Failure Modes

Connectivity Dependencies

Wi-Fi Only Devices: S700 becomes unusable during internet outages
Real-time Features: Fraud detection, dynamic currency conversion require active connection
Offline Limitations: Local storage has capacity limits, sync delays affect reporting

Integration Complexity

Custom Development: Requires backend integration for connection tokens
Third-party POS: Limited to partner capabilities (Oracle, Lightspeed, Shopify)
SDK Maintenance: React Native community support creates long-term risk

Operational Constraints

EMV Certification: Breaking changes require recertification cycles
Device Management: Fleet configuration errors affect all readers simultaneously
Payment Method Limitations: Some regional payment methods require specific hardware

Performance Thresholds

Reliability Metrics

Stripe Infrastructure: 99.99% uptime SLA
Transaction Processing: Real-time authorization, delayed capture model
Security Updates: Automatic, no manual intervention required

Scale Limitations

Device Fleet: No documented upper limits for enterprise deployments
Transaction Volume: Custom pricing triggers at undisclosed thresholds
Geographic Coverage: 50+ countries but regional payment method variations

Competitive Advantages

Unified Platform Benefits

Single Dashboard: Online and in-person transactions consolidated
Shared Customer Data: Profiles and payment methods across channels
Simplified Reconciliation: Eliminates separate POS system data silos

Developer Experience

Comprehensive APIs: Full integration control vs limited POS configurations
Custom Applications: Smart readers support Android app deployment
Testing Environment: Sandbox mode for development without live transactions

Migration and Integration Considerations

Existing POS Replacement

Data Migration: Customer and transaction history requires manual export/import
Staff Training: New interfaces and workflows need accommodation time
Hardware Transition: Existing terminals become incompatible, full replacement needed

Development Timeline Factors

SDK Learning Curve: 2-4 weeks for experienced mobile developers
Custom POS Development: 3-6 months for full-featured applications
Third-party Integration: 1-2 weeks configuration for supported partners

Support and Maintenance

Included Services

Hardware Replacement: Covered under standard program
Security Updates: Automatic deployment
EMV Compliance: Stripe maintains certifications
Device Configuration: Remote management through dashboard

Support Quality Indicators

Documentation: Comprehensive with code examples
Community: Active developer resources and forums
Enterprise Support: Dedicated support teams for large deployments
Response Times: Standard support SLAs, enterprise escalation paths

Decision Framework

Choose Terminal When:

Existing Stripe integration for online payments
Need unified reporting across sales channels
Require custom checkout experiences
Want transparent pricing without monthly fees
Need extensive API access for integrations

Avoid Terminal When:

Purely offline business model (no internet dependency tolerance)
Complex legacy POS integrations outweigh benefits
Basic transaction processing is sufficient
Higher per-transaction costs are prohibitive vs flat monthly fees
No technical development resources available for integration

Technical Readiness Assessment:

High: Existing mobile/web development team, current Stripe integration
Medium: Technical staff available, willing to learn new SDKs
Low: No development resources, prefer turnkey solutions with minimal customization

42%

Recommendations combine user behavior, content similarity, research intelligence, and SEO optimization