Select a reader

Learn about Stripe's pre-certified card readers and Tap to Pay.

Stripe Terminal readers offer end-to-end encryption and remote management tools. Use this page to find the right reader for your integration.

Stripe Reader the related setting/the related setting

the related setting WisePOS E

Stripe Reader M2

the related setting WisePad 3

Tap to Pay

Verifone Public preview

Choose by use case

To narrow your options, start with your physical environment and integration needs.

Key decision factors

If your use case isn’t listed, use these dimensions to narrow your choice:

Device category

• Smart readers (sPOS): Internet-connected touchscreen devices that support Terminal SDK, JavaScript SDK, and server-driven integrations. The options include Stripe Reader the related setting and the related setting, the related setting 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 the related setting WisePad 3 outside the United States.
• Tap to Pay: Accepts contactless payments on a compatible iPhone or Android device without a separate reader.

Connection type

• 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 the related setting supports 4G LTE connectivity in locations without reliable WiFi.

Integration platform

• 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 doesn’t 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 the related setting/the related setting and Verifone V660p. See Apps on Devices.
• Standalone mode: Uses a no-code Stripe app pre-installed on compatible smart readers, including Stripe Reader the related setting/the related setting and Verifone V660p. Availability varies by reader. See Standalone mode.

Compare reader capabilities

This table compares the key capabilities across all readers.

1 Offline mode requires the Terminal mobile SDK.

Global availability

Reader availability varies by country. Not all Verifone models (V660p, the related setting, the related setting, and the related setting) are available in every country.

Order readers

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.

• Browse readers and accessories .
• For Tap to Pay, see compatible iPhones and Android devices .
• Use the Terminal Hardware Ordering API to automate ordering at scale.

If you don’t have a physical reader yet, you can use the simulated reader to build and test your Terminal integration.

Warning

Stripe readers aren’t 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 doesn’t properly operate or charge properly after drying, you need to replace it.

Integration platform comparison

Choose an integration platform based on your preferred reader, desired features, and technology stack.

Device specifications

For detailed hardware specifications (dimensions, weight, battery, memory, connectivity, and accessories), see the individual reader pages:

• Stripe Reader the related setting/the related setting
• the related setting WisePOS E
• Stripe Reader M2
• the related setting WisePad 3
• Tap to Pay
• Verifone V660p , the related setting , the related setting , and the related setting

Connect a reader

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 don’t 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.

Pre-certification

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.

Reader software updates

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.

• Smart readers update automatically when powered on, sufficiently charged, and not in use.
• Mobile reader updates are handled by the Terminal SDK when connected to your point of sale. Required updates install automatically during connection. Optional updates, however, must be triggered by your application.

Next steps

• Design your integration
• Set up your integration
• Order readers