| [ Web Proxy ] |
| Viewing: https://stripe.com/jp/docs/terminal/payments/setup-reader | [Back] [Original] |
Stripe Terminal readers offer end-to-end encryption and remote management tools. Use this page to find the right reader for your integration.
To narrow your options, start with your physical environment and integration needs.
| Use case | Recommended reader | Why |
|---|---|---|
| Countertop checkout | Stripe Reader S700/S710 or Verifone | Smart readers with touchscreen, tipping, on-screen inputs, and server-driven or SDK integration. The S710 adds cellular connectivity, and is commonly used in retail, restaurants, and hospitality. |
| Mobile or field payments | Stripe Reader M2 (US) or BBPOS WisePad 3 (outside US) | Compact mobile readers that pair with a phone or tablet running your app. Commonly used for delivery, curbside, and event payments. For an all-in-one device without a separate phone or tablet, consider Stripe Reader S700/S710 with Apps on Devices. |
| No additional hardware | Tap to Pay | Accept contactless payments directly on a compatible iPhone or Android device. |
| Self-service kiosk or unattended terminal | Stripe Reader S700/S710 or Verifone UX700 | All-in-one smart readers run standalone mode or custom apps on-device, so the reader is the interface. For an embedded kiosk where your own hardware owns the interface, use a mobile reader (Stripe Reader M2 or BBPOS WisePad 3). For outdoor kiosks, consider the Verifone UX700. |
If your use case isnt listed, use these dimensions to narrow your choice:
Smart readers (sPOS): Internet-connected touchscreen devices that support Terminal SDK, JavaScript SDK, and server-driven integrations. The options include Stripe Reader S700 and S710, BBPOS WisePOS E, and supported Verifone readers.
Mobile readers (mPOS): Connect to a phone or tablet running a Terminal mobile SDK through Bluetooth or USB on Android. The options include Stripe Reader M2 in the United States and BBPOS WisePad 3 outside the United States.
Tap to Pay: Accepts contactless payments on a compatible iPhone or Android device without a separate reader.
Internet (WiFi or Ethernet): Smart readers connect to Stripe over the internet. Your point-of-sale communicates with the reader through the Stripe API (server-driven integration) or over the local network using a Terminal SDK.
Bluetooth or USB: Mobile readers connect to your tablet or mobile device that runs the Terminal iOS, Android, or React Native SDK. USB connections are supported on Android.
Cellular: Stripe Reader S710 supports 4G LTE connectivity in locations without reliable WiFi.
Mobile SDKs (iOS, Android, and React Native): Support smart readers, mobile readers, and Tap to Pay. Mobile readers require one of these SDKs. Apps on Devices also run on the Android and React Native SDKs where your custom app runs directly on a compatible smart reader.
Server-driven integration (Stripe API): Supports Terminal smart readers only and doesnt require a Terminal client SDK.
JavaScript SDK: Supports Terminal smart readers only and runs in a web-based point-of-sale application.
Apps on Devices: Run your custom app directly on a compatible smart reader using the Android or React Native SDK. Available on Stripe Reader S700/S710 and Verifone V660p. See Apps on Devices.
Standalone mode: Uses a no-code Stripe app pre-installed on compatible smart readers, including Stripe Reader S700/S710 and Verifone V660p. Availability varies by reader. See Standalone mode.
This table compares the key capabilities across all readers.
| Stripe Reader S700/S710 | BBPOS WisePOS E | Stripe Reader M2 | BBPOS WisePad 3 | Tap to Pay | Verifone | |
|---|---|---|---|---|---|---|
| Device category | sPOS | sPOS | mPOS | mPOS | Phone/tablet | sPOS |
| Connection | Internet | Internet | Bluetooth, USB | Bluetooth, USB | N/A | Internet |
| Country availability | Multiple | Multiple | US only | Multiple | Multiple | Multiple |
| Contactless and digital wallets | ||||||
| EMV chip cards | ||||||
| Magstripe cards | ||||||
| Server-driven integration | ||||||
| JavaScript SDK | ||||||
| Mobile SDKs (iOS, Android, React Native) | ||||||
| Standalone mode | V660p only | |||||
| Offline payments1 | iPhone only Private preview | |||||
| On-reader tipping | Receipt tipping only | In-app | ||||
| On-screen input collection | In-app | |||||
| Custom splash screen | ||||||
| Custom apps on-device (paid) | In-app | |||||
| Cellular connectivity | S710 only |
1 Offline mode requires the Terminal mobile SDK.
Reader availability varies by country. Not all Verifone models (V660p, UX700, P630, and M425) are available in every country.
| Country | Smart readers | Mobile readers | Tap to Pay |
|---|---|---|---|
United States |
|
|
|
Australia |
|
|
|
|
|
|
|
New Zealand |
|
|
|
Canada |
|
|
|
|
|
|
|
Singapore |
|
|
|
|
|
|
|
Poland |
|
|
|
France |
|
|
|
Germany |
|
|
|
Japan |
|
|
|
Malaysia |
|
|
|
Mexico |
| ||
|
|
|
|
|
|
You can order readers from the Dashboard and have them shipped to a location of your choice. As a Connect platform, you can order readers centrally and assign them to your connected accounts, or enable your connected accounts to order their own readers directly.
If you dont have a physical reader yet, you can use the simulated reader to build and test your Terminal integration.
Stripe readers arent liquid-proof so make sure your devices remain dry. If your device has experienced liquid ingress, stop using the device and let it dry thoroughly before attempting to reuse or charge the device. If your device doesnt properly operate or charge properly after drying, you need to replace it.
Choose an integration platform based on your preferred reader, desired features, and technology stack.
| Platform | Works with | Best for |
|---|---|---|
| iOS SDK | All readers | Native iOS apps with mobile readers, smart readers or Tap-to-pay on iPhone readers. |
| Android SDK | All readers | Native Android apps with mobile readers, smart readers, Tap-to-pay on Android readers, or Apps on Devices. |
| React Native SDK Public preview | All readers | Cross-platform mobile apps with a single codebase supporting both iOS and Android Terminal integrations. |
| Server-driven integration | Smart readers only | Existing server infrastructure without a client-side SDK. Manage readers entirely through the Stripe API. |
| JavaScript SDK | Smart readers only | Browser-based POS systems. |
| Standalone mode Public preview | S700/S710, Verifone V660p | Accepting payments without a connected POS. A prebuilt Stripe payment app runs on the reader and doesnt require code or a separate POS. |
For detailed hardware specifications (dimensions, weight, battery, memory, connectivity, and accessories), see the individual reader pages:
Before processing payments, you must connect a Terminal reader to your point-of-sale application using a Terminal SDK. With a server-driven integration, you manage readers through the Stripe API and dont need an SDK connection.
A reader connects to one SDK instance at a time. To use a reader with a different device, disconnect it before connecting to the new one.
Terminal readers are pre-certified for PCI and EMV compliance. They accept payment details (EMV, contactless, and swiped) and encrypt sensitive card information, so your application never handles raw card data.
Stripe periodically releases reader software updates that include improvements and required security patches. Your application must support automatic updates. Failing to install a required update can prevent a reader from accepting payments.
| Web Proxy Viewer | New URL | Original Page |