Square, Inc.

Block, Inc.

Imran Sana Khan

Todor Ristov

Isreal Blagdan

Evan Doyle

Elise Hurwitz

Christine Lin

Sara Sanchez-Llorens

Arnaud Ponchon

Kartik Lamba

Claudia J Ng

James Paul Thome

Jennifer Murse

Max Joseph Guise

Eric Monti

John L Kelley

Tait Svenson

Daniel Jeffrey Post

Mark Funk

Techniques for using a stored balance associated with a payment instrument are described. Transaction data associated with a transaction is received, wherein a payment instrument linked to a stored balance of a user is provided for payment of the transaction. In one example, a computer system determines that the stored balance is insufficient to satisfy the total amount of the purchase. The computer system further determines, based on a policy and without user input, to access funds from a bank account linked to the stored balance. The funds from the bank account are deposited to the stored balance, and the payment is processed for the total amount using the updated stored balance.

Selection of a financial account associated with a proxy object

Techniques are described for securely updating a point-of-sale (POS) system that includes a merchant-facing device and a buyer-facing device. For instance, the merchant-facing device may execute first software that provides first POS functionality and the buyer-facing device may execute second software that provides second POS functionality. To update both devices, the merchant-facing device may receive a software update from a payment service via a network connection, and update the first software using the software update. The merchant-facing device can then cause, via a physical connection, the buyer-facing device to reboot in an update mode and send the software update to the buyer-facing device. In response, the buyer-facing device can update the second software using the software update and then reboot in a payments mode. In some instances, the buyer-facing device can then update a secure enclave on the buyer-facing device using the software update.

Securely updating software on connected electronic devices

A method and apparatus for selecting a financial account associated with a payment object based on fund availability are disclosed. A payment object, such as a proxy card associated with multiple financial accounts, is used by a consumer to make a purchase. In one example, the consumer selects a debit card associated with the proxy card to use for the purchase. A computer system determines that the debit card account has insufficient funds available for the purchase, and determines that an alternate account associated with the proxy card has sufficient funds. The computer system notifies the consumer, via a mobile device of the consumer, that the debit account has insufficient funds, and provides the consumer with the option of using the alternate account. The consumer indicates a desire to use the alternate account, and the computer system processes the payment based on the alternate account.

Techniques for conducting transaction(s) between a merchant and customer(s) via a multi-device point-of-sale (POS) system is described. The multi-device POS system can include a customer-facing device having a first processor for processing first instructions for presenting a customer user interface (UI) on a display of the customer-facing device. The customer-facing device can include a payment reader that is accessible by the one or more customers. Further, the multi-device POS system can include a first merchant-facing device having a second processor for processing second instructions for presenting a first merchant UI, which can enable the merchant to perform a first action associated with a first transaction of the one or more transactions. The first merchant-facing device can be coupled to the customer-facing device. The multi-device POS system can further include an application, which can be stored on the customer-facing device, a second merchant-facing device, or a personal device, for presenting a second merchant UI enabling the merchant to perform a second action.

Multi-device point-of-sale system having multiple merchant-facing devices

Temporarily provisioning functionality to a personal device in a multi-device point-of-sale (POS) system is described. In an example, a presence of a personal device operated by, or on behalf of, a merchant can be determined to be within a range of a POS system of a merchant. The POS system can include a merchant-facing device and a customer-facing device that is coupled to the merchant-facing device. Functionality can be provisioned to the personal device that (i) configures the personal device to present a merchant user interface (UI) via a display of the personal device to enable the merchant to interact with one or more customers and (ii) enables the personal device to interact with at least one of the merchant-facing device or the customer-facing device. Responsive to determining an occurrence of an event, the functionality can be de-provisioned from the personal device.

Temporarily provisioning functionality in a multi-device point-of-sale system

Techniques associated with a dual state merchant-facing device are described herein. A point-of-sale system can comprise multiple devices, such as a customer-facing device and a merchant-facing device that is coupled to the customer-facing device and can operate in a first state or a second state. In at least one example, the merchant-facing device operating in the first state can present a graphical user interface (GUI) on a display. The merchant-facing device can transition from the first state to the second state, the second state enabling the merchant-facing device to perform at least one additional functionality that is not available to the merchant-facing device in the first state, and can update the GUI based at least in part on the at least one additional functionality.

Multi-state merchant-facing device

Temporarily provisioning functionality to a personal device in a multi-device point-of-sale (POS) system is described. In an example, a personal device can be determined to be within a range of a POS system of a merchant. The POS system can include a merchant-facing device and a customer-facing device that is coupled to the merchant-facing device. Functionality can be provisioned to the personal device that (i) configures the personal device to present a customer user interface (UI) via a display of the personal device to enable a customer operating the personal device to interact with the merchant and (ii) enables the personal device to interact with at least one of the merchant-facing device or the customer-facing device. Responsive to determining an occurrence of an event, the functionality can be de-provisioned from the personal device.

Techniques for conducting transaction(s) between a merchant and customer(s) via a. multi-device point-of-sale system are described. The multi-device POS system can include a merchant-facing device having a first processor for processing first instructions for presenting a merchant user interface (UI) on a display of the merchant-facing device. Further, the multi-device POS system can include a first customer-facing device having a second processor for processing second instructions for presenting a first customer UI. The first customer UI can enable a first customer to perform a first action associated with a first transaction. The first customer-facing device can have been coupled to the merchant-facing device at a first time. Further, the multi-device POS system can include an application, which can be stored on the merchant-facing device, a second customer-facing device, or a personal device, for presenting a second customer UI enabling performance of a second action.

Multi-device point-of-sale system having multiple customer-facing devices

Techniques for securely updating a point-of-sale (POS) system that includes a merchant-facing device and a buyer-facing device are described. For instance, the merchant-facing device may execute first software that provides first POS functionality and the buyer-facing device may execute second software that provides second POS functionality. To update both devices, the merchant-facing device may receive a software update from a payment service via a network connection, and update the first software using the software update. The merchant-facing device can then cause, via a physical connection, the buyer-facing device to reboot in an update mode and send the software update to the buyer-facing device. In response, the buyer-facing device can update the second software using the software update and then reboot in a payments mode. In some instances, the buyer-facing device can then update a secure enclave on the buyer-facing device using the software update.

Techniques and arrangements for facilitating synchronization of order ticket functionality utilized by point-of-sale (POS) devices with kitchen display systems. In some example, a POS device and a line buster device collectively receive a plurality of customer orders associated with a transaction between a merchant and plurality of customers. Based on individual customer orders, the POS device determines when to fire off the orders to the kitchen display system irrespective of the sequence in which they are received. In some examples, the kitchen display system then synchronizes with a customer device to provide real-time or near-real time updates on the status of the order.

Order fulfillment and tracking systems and methods

Selecting a financial account associated with a proxy object based on fund availability

Techniques associated with a multi-functionality customer-facing device are described herein. A point-of-sale system can comprise multiple devices, such as a customer-facing device and a merchant-facing device that is coupled to the customer-facing device. The customer-facing device is capable of operating in a first state or a second state. In at least one example, the customer-facing device can present a graphical user interface (GUI) on a display. The customer-facing device can transition from the first state to the second state. The second state can enable the customer-facing device to perform at least one additional functionality that is not available to the customer-facing device in the first state. The customer-facing device can receive, while in the second state, an input via the GUI and can send to the merchant-facing device, an indication of the input.

Multi-functionality customer-facing device

Techniques and arrangements for facilitating synchronization of order ticket functionality utilized by point-of-sale (POS) devices with kitchen display systems. In some example, a POS device and a line buster device collectively receive a plurality of customer orders associated with a transaction between a merchant and plurality of customers. Based on individual customer orders, the POS device determines when to fire off the orders to the kitchen display system irrespective of the sequence in which they are received. In some examples, the kitchen display system then determines whether or not to request payment from the customer before the order is prepared or delivered.

Smart inventory tags are described herein. In an example, a service provider can determine interaction capability(s) for a tag associated with an item in an inventory of a merchant. The tag can be configured to be positioned proximate to the item offered for sale by the merchant at a physical store of the merchant. The service provider can receive an indication associated with a selection of at least one interaction capability of the interaction capability(s) and, based at least in part on the indication, the service provider can generate encoded information associated with the at least one interaction capability. The service provider can generate an instruction for generating the tag including the encoded information to enable a presentation of a user interface associated with the at least one interaction via a device operated by a user at the physical store of the merchant.

Smart inventory tags

A payment card reader for reading integrated circuit (IC) payment cards is disclosed. The payment card reader includes a microcontroller having non-programmable logic, coupled with a data input from the IC payment card, configured to effect a first implementation of a communication standard for communication between the microprocessor and the IC payment card, the non-programmable logic comprising a non-programmable hardware timer. The microcontroller also includes extensible logic, coupled with the data input via a general-purpose input/output (GPIO) pin, the extensible logic configured to include an extensible timer and interrupt logic, the extensible timer and interrupt logic for use with the non-programmable logic and the data input to effect a second implementation of the communication standard for communication between the microprocessor and the IC payment card.

Growing community of inventors

San Anselmo, CA, United States of America

Imran Sana Khan