| Scavenger Hunt | | | The Great Code Chase | | Think you can catch The Code Runner? We’re thrilled to introduce The Great Code Chase — our latest scavenger hunt! A sneaky thief has stolen a critical piece of code, and we need developers like you to track them down. Follow the clues across Square Developer channels, and if you solve the mystery in time, you could win a limited-edition Square Developer LEGO Minifigure. Get your first clue on the Square Developer YouTube Channel now. Good luck!
Disclaimer: No purchase necessary. Contest open to residents of the U.S. and Canada who have reached the legal age of majority in the participant's jurisdiction of residence at the time of entry. Contest begins on January 23, 2025 at 10 a.m. PST and ends on April 15, 2025 at 5 p.m. PST or until all prizes have been claimed. Winners will be chosen based on specific criteria and contacted via email. Limit one entry per person. Contest T&Cs here. | | Start the hunt → |
|
|
|
|
|
|
| Docs | | Compare Square Payment Hardware Solutions | | Learn about solutions that enable you to connect your app to Square payment hardware, explore use cases for in-person payments, and identify the APIs and SDKs that best suit your development goals and application requirements. | | Learn more → |
|
|
|
|
|
|
| SDK | | Mobile Payments SDK (GA) | | Succeeding the Reader SDK, Mobile Payments SDK allows you to build Android and iOS mobile apps that connect with Square hardware to accept payments. It introduces improved reliability, key features to support more use cases, and deeper integrations with the Square ecosystem. Available only to developers serving sellers in the U.S. If your application currently uses the Reader SDK, please migrate to the Mobile Payments SDK by following the steps in our migration guide, as we plan to deprecate and eventually retire the Reader SDK. | | Learn more → |
|
|
|
|
|
|
Customers API:
• Customer object - The cards field will be retired in Square API version 2025-01-23. This field is replaced by the ListCards and ListGiftCards endpoints with the customer_id query parameter. Note that the retirement date for the deprecated CreateCustomerCard and DeleteCustomerCard endpoints isn't currently scheduled, but you should migrate to the Cards API and Gift Cards API as soon as possible. For more information, see Migration notes. GraphQL:
• Square GraphQL queries now support the Payouts graph (Alpha). See an example query. Payments API:
• CreatePayment endpoint - New buyer_phone_number field.
• ListPayments endpoint - New updated_at_begin_time, updated_at_end_time, and sort_field filters that can be used to filter the results by the payment's updated_at field. Team API:
• New Job object and job management endpoints (Beta):
CreateJob, UpdateJob, ListJobs, RetrieveJob.
• TeamMember object - New wage_setting field (Beta), which provides direct access to a team member's overtime exemption status and job and compensation information using TeamMember endpoints (instead of RetrieveWageSetting or UpdateWageSetting).
• JobAssignment object - New job_id field (Beta), which now serves as the unique job identifier instead of job_title. For more information about using these new Team API features, see Integration Guide. Terminal API:
• CreateTerminalCheckout endpoint - New QR_CODE enum value for payment_type, which allows the Square Terminal to support a single QR code payment that integrates with multiple Japanese digital wallet brands. Documentation Updates: Square SDKs:
• Reorganized the Square SDKs overview page for easy access to each SDK package and GitHub repos, and added information about mobile and frontend SDKs.
• Removed the Stay Current with SDK Version topic for each SDK. This content is now present on each SDK landing page. Point of Sale API:
Offline Mode - Added a Requirements and limitations section to clarify how to maintain a Bluetooth connection and a secure connection to take payments while offline. Web Payments SDK:
• Integrate Digital Wallets with the Web Payments SDK - Removed the note that Apple Pay and Google Pay already comply with SCA. Developers are encouraged to implement SCA for all digital wallet payments. | | See changelog → |
|
|
|
|
|
|
| | Have colleagues who want to receive this newsletter? | | Have them subscribe here. |
|
|
|
|
|
|
