[Action Required] Reader SDK Deprecation and Retirement🚨

Announcements
,
1

Hi everyone,

We are officially deprecating the Reader SDK and retiring the product on December 31, 2025.

Effective immediately, the Reader SDK will no longer receive new releases, and support for new operating system versions is not guaranteed. If you are currently using the Reader SDK, please migrate to the Mobile Payments SDK before the retirement date. We encourage you to migrate as soon as possible to avoid compatibility issues with future iOS and Android updates. After December 31, 2025, the Reader SDK will be discontinued, and applications will no longer be able to use the Reader SDK to process payments.

Why is this happening?

The Mobile Payments SDK was designed to address critical pain points of the Reader SDK. It provides improved reliability with offline payment support and a built-in reader manager; added features, like Sandbox testing; and a deeper integration with the Square ecosystem, including the Payments API and Orders API. To ensure the best experience for you and your sellers, we have decided to phase out the Reader SDK.

What do I need to do?

  1. Migrate from the Reader SDK to the Mobile Payments SDK by following the steps in our migration guide.

  2. Once the migration is complete, notify your sellers to update to the latest version of your app, ensuring compatibility with the Mobile Payments SDK. Please migrate as soon as possible to give your sellers ample time to upgrade, to avoid compatibility issues with iOS and Android, and to take advantage of the latest features.

For more details on the Mobile Payments SDK, check out the docs.

Note: Flutter and React Native plug-ins are not yet available for the Mobile Payments SDK, but they will be shortly. If you require these plug-ins to migrate, please review the migration guide in the meantime. If you built your own plug-ins, you will need to update your code to be compatible with the Mobile Payments SDK.

Is the Mobile Payments SDK at feature parity with the Reader SDK?

Some features of the Reader SDK are not directly available on the Mobile Payments SDK. They either have been removed or require custom implementation, such as building your own UI. For details on these differences and how to address them, please refer to the migration guide.

Please migrate to the Mobile Payments SDK as soon as possible to ensure a seamless transition. Our team is here to help, and we recommend you reach out to your dedicated Square account manager. If you do not have one, please please feel free to ask any questions here or contact our developer support team.