What's New in the Mobile Payments SDK Beta
Article Summary
Square just launched the successor to their Reader SDK after 6 years, and KIOS was among the first to build with it. Their integration story reveals what's actually possible when payment SDKs are built for developers, not just transactions.
Square's new Mobile Payments SDK (currently in beta for US developers) replaces the Reader SDK with expanded capabilities based on partner feedback. KIOS, a restaurant kiosk software company serving 300+ customers with a team under 10, tested the SDK during alpha and shares their hands-on integration experience.
Key Takeaways
- Orders integration enables itemized receipts that automatically sync with Square systems
- Reader Management API provides real-time device status for remote troubleshooting
- Offline payments eliminate WiFi dependency for restaurant uptime
- App fees feature delivers same-day funds enabling cash accounting benefits
- Migration from Reader SDK to Mobile Payments SDK now recommended
The Mobile Payments SDK transforms in-person payment integration from basic transaction processing into a full-featured platform with orders, offline mode, device management, and flexible monetization.
About This Article
KIOS couldn't see the status of their Reader devices across different locations. When something broke in a remote city, they had to call customers and make educated guesses instead of diagnosing the problem right away.
The Reader Management API gave them real-time information about each device. They could check connection status, see when the last transaction happened, monitor battery life, and track software versions. This let KIOS spot authorization failures and connectivity issues instantly from their dashboard.
KIOS stopped waiting for problems to happen and started preventing them. Instead of calling customers or hunting for solutions, they could now authorize Readers remotely or send technicians out with exact information about what needed fixing. This worked across their 300+ customer locations.