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 and 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!
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:
Additional Documentation
Mobile Payments SDK
Reader SDK Quickstart
Square Developer Documentation
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.
“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.