Square, Inc.

Block, Inc.

Christopher Philip Renke

Mathew Wilson

Eric Dickeson Muller

Michael Wells White

Justin Brunet

William Rocklin

A payment handling system may operate to handle payments for the cost of a transaction in which one or more devices operate in an offline mode. The payment handling system may allow for merchant devices to make modifications to local versions of an open ticket while in an off-line mode. When a merchant device subsequently enters an online mode, the systems and techniques may operate to reconcile differences between the local versions of the open ticket.

Open ticket payment handling with offline mode

This disclosure describes techniques and arrangements for splitting one or more items from a ticket to another ticket. Some techniques and arrangements facilitate the splitting of one or more items from an open ticket to one or more split tickets. In some implementations, a foster ticket is utilized to account for items associated with split tickets. Other techniques and arrangements include providing split ticket suggestions. In some implementations, split ticket suggestions are provided based on historical ticket information and/or customer information.

Customer-based suggesting for ticket splitting

Techniques and arrangements for facilitating synchronizing data structures between devices using application programming interfaces (APIs) are described. In some examples, two devices may try to synchronize a data structure between one another by sending and receiving data for the data structure. However, each device may include hardware and/or software that is different than, and not compatible with, the other device. As such, the application describes a service that provides a first device an API for sending the service information for a transaction. The service uses the information to create a data structure for the transaction, and then sends the data structure to a second device. The second device can receive data structure from the service. After receiving the data structure, the service can process the transaction.

Utilizing APIs to facilitate open ticket synchronization

A payment handling system may operate to handle payments for the cost of an open ticket transaction in which incremental authorization operations are performed. The payment handling system may receive items to add to the open ticket, payment instruments for paying the cost of the open ticket or adjustments to any bill splitting arrangement throughout the life of the open ticket. As items are added, payment instruments are received, and/or adjustments are input, the amount allocated to the one or more payments instruments may be updated. Incremental authorization values may be determined for some or all of the payment instruments. When the amount allocated to a payment instrument exceeds the incremental authorization value, an authorization of the instrument is attempted and a new authorization value is determined. At the end of the interaction, the open ticket is closed and payment is executed.

Open ticket payment handling with bill splitting

A payment handling system operates to handle payments for the cost of an open ticket transaction in which incremental authorization operations are performed. The payment handling system receives items to add to the open ticket, payment instruments for paying the cost of the open ticket or adjustments to any bill splitting arrangement throughout the life of the open ticket. As items are added, payment instruments are received, and/or adjustments are input, the amount allocated to the one or more payments instruments may be updated. Incremental authorization values are determined for some or all of the payment instruments. When the amount allocated to a payment instrument exceeds the incremental authorization value, an authorization of the instrument is attempted and a new authorization value is determined. At the end of the interaction, the open ticket is closed and payment is executed.

Open ticket payment handling with incremental authorization

Techniques and arrangements for managing animations (e.g., chrome) on an application of a computing device are described. The application may dynamically adjust the number of animations to process information at a faster and/or slower rate. The application may adjust the number of animations based on various factors, such as a rate of input events, a rate of outbound signals, a type of user, an experience level of a user, a time of day, a time of year, and/or other factors.

Animation management in applications

Techniques for processing a transaction using one or more service computing devices of a payment service that processes transactions for multiple merchants including a merchant are described. A first point-of-sale device operable by the merchant is configured to (i) receive, from a first point-of-sale (POS) device operable by the merchant, transaction data indicating an amount to charge a customer for at least one item ordered by the customer from the merchant in a transaction, and (ii) send the transaction data to a second POS device operable by the merchant, and the second POS device is configured to (i) receive the transaction data, (ii) generate payment data via a card reader associated with the second POS device, and (iii) transmit the payment data to a payment gateway for processing payment for the transaction.

Cloud-based point-of-sale transaction processing

Techniques and arrangements for synchronizing kitchen display system functionality with point-of-sale (POS) waitlist generation. In some examples, a POS device generates a waitlist using both front of the house data (e.g., data associated the POS device) and back of the house data (e.g., data associated with the kitchen display system). For instance, the POS device can receive input associated with transactions between a merchant and customers. The POS device can then generate a waitlist based on the input. Additionally, the POS device can receive data associated with order tickets from the kitchen display system. Based on receiving the data, the POS device can update the waitlist using the data. In some examples, the POS device updates the waitlist by determining a state associated with each of the transactions, and the updating wait times for the transactions based on the states.

Synchronizing KDS functionality with POS waitlist generation

Techniques and arrangements for facilitating synchronization of open tickets between electronic devices using application programming interfaces. In some examples, a system may provide an application programming interface (API) for generating open tickets to a first electronic device and receive, from the first electronic device using the API, cart information indicating one or more items. The server can then generate an open ticket based at least in part on the cart information and send data associated with the open ticket to a second electronic device. In some examples, the data includes the one or more items. In some examples, the first electronic device can add additional items to the open ticket via the API and/or the second electronic device add additional items to the open ticket by sending data associated with the additional items to the server.

Growing community of inventors

San Francisco, CA, United States of America

Christopher Philip Renke