# Clarification about Reader SDK deprecation and migration to Mobile Payments SDK

**URL:** <https://developer.squareup.com/forums/t/clarification-about-reader-sdk-deprecation-and-migration-to-mobile-payments-sdk/24489>\
**Category:** Questions\
**Tags:** reader-sdk, square-reader, mobile-payments-sdk\
**Created:** [November 11, 2025, 9:38am UTC](https://developer.squareup.com/forums/t/clarification-about-reader-sdk-deprecation-and-migration-to-mobile-payments-sdk/24489 "2025-11-11T09:38:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dishumskaya](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@dishumskaya](https://developer.squareup.com/forums/u/dishumskaya)\
**Post date:** [November 11, 2025, 9:38am UTC](https://developer.squareup.com/forums/t/clarification-about-reader-sdk-deprecation-and-migration-to-mobile-payments-sdk/24489/1 "2025-11-11T09:38:29Z")

</div>

Hi 👋

The documentation says:

> The Mobile Payments SDK is the successor of the Reader SDK, providing a simple and PCI-compliant payment flow for iOS and Android applications. Developers should migrate their Reader SDK applications to the Mobile Payments SDK to benefit from new features and ensure continued support **before the retirement of the Reader SDK on December 31, 2025**. The following sections cover the major differences between the Reader SDK and the Mobile Payments SDK. When migrating your application, you can also reference the Mobile Payments SDK sample applications for [iOS](https://github.com/square/mobile-payments-sdk-ios) and [Android](https://github.com/square/mobile-payments-sdk-android).

Could you please clarify exactly what **“retirement”** means?

- Will the **Reader SDK stop working completely** after December 31, 2025 (e.g., the APIs will be disabled or rejected)?

- Or will existing apps built with Reader SDK **continue to function** for some time but simply won’t receive support or updates?

Thanks in advance for confirming!

---

<div class="post-metadata">

**Author:** ![Square-Dev-AI](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/square-dev-ai/32/2513_2.png) [@Square-Dev-AI](https://developer.squareup.com/forums/u/Square-Dev-AI)\
**Post date:** [November 11, 2025, 9:38am UTC](https://developer.squareup.com/forums/t/clarification-about-reader-sdk-deprecation-and-migration-to-mobile-payments-sdk/24489/2 "2025-11-11T09:38:36Z")

</div>

👋 I’m Square Dev AI, here to help answer your question!  
Based on the information you’ve provided, the following documentation will help answer your question:

> **[Migrate from the Reader SDK](https://developer.squareup.com/docs/mobile-payments-sdk/migrate)**
>
> Learn how to migrate applications from the Reader SDK to use the Mobile Payments SDK.

> **[Reader SDK](https://developer.squareup.com/docs/reader-sdk/what-it-does)**
>
> Learn more about processing payments with the Square Reader SDK.

> **Additional Documentation**
>
> [Mobile Payments SDK](https://developer.squareup.com/docs/mobile-payments-sdk)  
> [Reader SDK Quickstart](https://developer.squareup.com/docs/reader-sdk/quick-start/start)  
> [Square Developer Documentation](https://developer.squareup.com/docs/reader-sdk/how-it-works)

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.  
Otherwise one of our Developer Advocates will provide additional assistance shortly.

---

<div class="post-metadata">

**Author:** ![Square-Dev-AI](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/square-dev-ai/32/2513_2.png) [@Square-Dev-AI](https://developer.squareup.com/forums/u/Square-Dev-AI)\
**Post date:** [November 11, 2025, 5:59pm UTC](https://developer.squareup.com/forums/t/clarification-about-reader-sdk-deprecation-and-migration-to-mobile-payments-sdk/24489/3 "2025-11-11T17:59:50Z")

</div>

“Retirement” in the context of the Square Reader SDK means that the SDK will no longer be available or supported after December 31, 2025. This implies that the APIs associated with the Reader SDK will be disabled, and any REST calls attempting to use retired functionality will return errors. Therefore, existing apps built with the Reader SDK will not continue to function as they rely on these APIs, which will be unavailable. It’s important to migrate to the Mobile Payments SDK to ensure continued functionality and support.

_This answer was reviewed by @Bryan-Square._