Build Basics

Language Preferences for Applications to Communicate

People communicate with software through natural languages, such as English, French, and Spanish. Because each person has a different preferred language, it is important for applications to track and accommodate individual language preferences.

The following describes how applications that integrate the Square API might accommodate these language preferences in communications. When communicating through a web browser or mobile application, applications can use the language preferences that those devices already provide. For other types of communication, you must have a language preference on file. Example communications include:

  • Sending a daily status email to a Square seller about how the application's functionality was used that day.

  • Printing receipts for a buyer when using hardware that is associated with your application.

  • Sending a text message to a buyer after the buyer interacts with your application.

Square maintains language preferences for each seller that applications can use in communications. By using Square's language preferences, sellers get a consistent language experience when they access your application (also referred to as third-party applications) and when they access Square software.

The Square-maintained language preferences for each seller are:

  • Location specific. Each location that a seller creates in their Square account has its own language preference. Applications can use the Locations API to retrieve or update these preferences. You can also manage these preferences in the Seller Dashboard (see Manage Multiple Locations with Square).

    Applications can use this language preference for communications at a location when there is neither a personal nor device language. For example:

    • Printing receipts. When Square Point of Sale (POS) prints a receipt, the buyer generally does not have a Square account or a device to select the language preference. So the receipt should be printed in the location's language.

    • Sending emails and other communications. Applications can use the location language when emailing receipts, invoices, or any other communications for a location.

  • In the merchant/seller language. Square also maintains a seller-level language preference, available through the Merchants API. The merchant language is the ultimate fallback language if none of the preceding apply. For example, consider a daily status report to the seller. If the status report covers all locations of the seller, then it is best to use the language of the overall merchant for the communication.