Square, Inc.

Block, Inc.

Other

Ryder Moody

Mathew Wilson

Jonathan Andrew Wolter

Derrick Huhn

Dan Simms

Marc David Perry

Adam Edwards

Christopher Heisel

Morgan Engel

Eric Zundel Ayers

Stephen Brewer

Edward Gonzales

Vibhor Chhabra

Christian De Angelis

Michael Higgins

A merchant uses a merchant point of sale (POS) device to identify items or services for purchase by a customer, and costs for each. One or more payment amounts are sent from the merchant POS device to a checkout server using an application programming interface (API), which the checkout server sends on to an authorized payment terminal device that then reads payment information from a payment object and sends the payment information back to the checkout server. The checkout server processes the transaction and confirms transaction completion to the merchant POS device and payment terminal device.

Area-based identification of devices for pairing

Multi-device authorization

Techniques and arrangements for analyzing previous tickets of a customer at different merchants&#x2014;specifying interactions of the customer at the different merchants&#x2014;to determine subsequent recommendations to send to a particular merchant in real-time when the customer is located at the particular merchant. Other techniques and arrangements facilitate annotation of merchant tickets by the merchants to enrich the data maintained by the tickets and, in some instances, to enhance the described real-time recommendations. Still other techniques and arrangements create a merchant ticket for recording interactions between a merchant and customer upon the customer creating a reservation at the merchant for a specified future time, or being added to a waitlist of the merchant. Upon the customer arriving at the merchant proximate to the specified future time, the merchant may use the created ticket to track items ordered by the merchants, track tenders used to pay for items, and the like.

Data structure analytics for real-time recommendations

Merchant point of sale collaborating with payment reader terminal via server application programming interface

Pairing merchant point of sale with payment reader terminal via server application programming interface

Techniques for leveraging a likelihood that a transaction (or a portion thereof) will be associated with a refund request to determine whether and/or how long to delay sending, to a payment service, a request for processing the transaction (or portion thereof) are described herein. In an example, a payment processing service may receive, from a point of sale device operated by a merchant, transaction data associated with a transaction between the merchant and a customer. The payment processing service may determine a likelihood that the customer will request a refund for a cost of an item of the transaction at a time after the transaction. Based at least partly on the likelihood, the payment processing service may determine whether to wait until at least the time before sending, to a payment service, a request to process the transaction data for at least the cost of the item.

Interchange action delay based on refund prediction

Techniques and arrangements for creating a data structure for recording interactions between a first user and a second user for interactions to occur at a specified future time. The techniques and arrangements include facilitating annotation of the data structure. At the specified future time, the created data structure may be used to track items ordered, track tenders used to pay for items, and the like.

Anticipatory creation of point-of-sale data structures

Growing community of inventors

San Francisco, CA, United States of America

Ryder Moody