Mobile Payments SDK General Availability and Terminal API Features
Article Summary
Square just launched their Mobile Payments SDK to GA with a twist: your phone becomes the card reader. No external hardware required for contactless payments.
Square announces the general availability of their Mobile Payments SDK (successor to Reader SDK) and expanded Terminal API features. The release brings offline payments, tap-to-pay capabilities, and cross-platform support to developers building custom in-person payment solutions across US, Canada, and Australia.
Key Takeaways
- Tap to Pay on iPhone and Android eliminates need for external hardware
- Flutter and React Native plugins enable single codebase deployment
- Offline payments ensure transactions continue during network outages
- Terminal API now supports Orders integration in Canada, UK, and Australia
- Multi-brand QR codes accept 7 payment methods in Japan simultaneously
Square's Mobile Payments SDK reaches GA with tap-to-pay support and cross-platform plugins, while Terminal API expands Orders integration to three new countries and simplifies QR payments in Japan.
About This Article
Developers had to move away from the deprecated Reader SDK by December 31, 2025. After that date, Square couldn't guarantee support for new operating systems.
Square built the Reader Management API to help developers keep tabs on their connected Square Readers. The API tracks battery levels, software versions, and serial numbers so developers can spot and fix problems before they cause downtime.
Hundreds of developers created integrations that let thousands of sellers use Square Reader, Square Stand, and Square Terminal with third-party apps. DH Pace, for example, runs 50 locations across the country and uses the Mobile Payments SDK to process field service payments.