Abstract: A method of processing a transaction between a customer and a merchant includes receiving from a mobile device of the customer or from another device of the customer an indication of consent to perform a cardless payment transaction with the merchant, receiving from the mobile device an indication that the customer is within a predetermined distance of the merchant, after receiving both the indication of consent and the indication that the customer is within the predetermined distance, sending to a computer system of the merchant an indication of the presence of the customer and personal identifying information for the customer, receiving data indicating a transaction between the customer and the merchant, and submitting the transaction to a financial service for authorization.

Abstract: A method of processing a transaction between a customer and a merchant includes receiving from a mobile device of the customer or from another device of the customer an indication of consent to perform a cardless payment transaction with the merchant, receiving from the mobile device an indication that the customer is within a predetermined distance of the merchant, after receiving both the indication of consent and the indication that the customer is within the predetermined distance, sending to a computer system of the merchant an indication of the presence of the customer and personal identifying information for the customer, receiving data indicating a transaction between the customer and the merchant, and submitting the transaction to a financial service for authorization.

Abstract: 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.

Abstract: In some examples, a system may receive a notification of a transaction using a first device, wherein the notification includes an identifier that identifies at least one of: a user, or a second device associated with the user. The system may send, to the second device, based on the identifier included in the notification, a communication to cause the second device to present a user interface that displays information about the transaction. Further, the system may receive, from the second device, prior to completion of processing the transaction, an indication of a user input received via the user interface indicating a confirmation of the information about the transaction. Based at least on receiving the confirmation from the second device, the system may submit, to a payment processor, information related to the transaction to enable the payment processor to determine whether to approve the transaction.

Abstract: Introduced here is a technology for automatic notification of an invoice based on identification of a customer identifier included in transaction data received from a point-of-sale (POS) device of a particular merchant. Transaction data for a transaction occurring at the merchant POS device between a customer and the first merchant can be transmitted from the POS device to server(s) of a payment processing service. The transaction data can include a customer identifier. The POS device can receive invoice data from the server(s) associated with an unpaid invoice that is associated with the customer identifier and a historical transaction with the first merchant or a second merchant. The POS device can cause presentation, on a display of the POS device, an invoice payment invitation for the customer to make a payment on the unpaid invoice.

Abstract: Introduced here is a technology for automatic notification of an invoice for a customer based on identification of a customer identifier included in transaction data received from a point-of-sale (POS) system of a particular merchant (“the invoice technology”). The notification can include a promotion to provide an incentive to the customer to pay the invoice. The notification can be presented on a display of the POS system. Alternatively, the notification can be presented in a receipt for the transaction conducted at the POS system, where that receipt can be transmitted for display at a user device of the customer. For example, the receipt can be in the form of an email message or a text message. Upon notification of the invoice, the customer can submit a payment for that invoice (“invoice payment”) in exchange for the promotion.

Abstract: In one embodiment, systems and techniques include receiving, by a transaction server and from an electronic device of a first user, a transaction request for a transaction between the first user and a second user. The transaction request includes an amount to be withdrawn from or deposited into a financial account of the second user and identifying information for the second user. The identifying information includes information from a form of identification provided at the electronic device. The techniques include identifying, via a mapping database associated with the transaction server, the financial account of the second user and a financial account of the first user. The techniques include adjusting, via the mapping database, respective monetary balances of the financial accounts based at least in part on the amount of the transaction. The techniques include transmitting, to at least one electronic device associated with the transaction, a confirmation message.

Abstract: Techniques and arrangements for analyzing previous tickets of a customer at different merchants—specifying interactions of the customer at the different merchants—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.

Abstract: In one embodiment, a method includes receiving, by a payment server, an identity of a customer based on data obtained from a mobile application executing on a device associated with the customer. The method includes creating a financial account for the customer. The method includes, upon receiving a request for a cash deposit or cash withdrawal via the mobile application, facilitating, by the payment server, generation of an electronic code to be used at a point-of-sale (POS) device of a merchant. The method includes receiving transaction information associated with a transaction involving the customer and the POS device of the merchant. The transaction information includes the electronic code. The method includes identifying, based on the transaction information, the financial account of the customer. The method includes causing an adjustment of a monetary balance of the financial account of the customer in a mapping database.

Abstract: Various embodiments are related to apparatuses and methods for enabling a merchant to perform banking-type transactions for a customer. A merchant can use, for example, a sales system configured to be used by the merchant to sell goods to perform a banking-type transaction for a customer. The sales system can send information related to the banking-type transaction to, for example, a buyer/seller platform. When the banking-type transaction is a deposit, the merchant can receive funds for the deposit from the customer. The platform can credit the customer's financial account for the deposit amount by diverting payment card funds, received by the merchant for the sale of goods and processed by the platform, to the customer's financial account. When the banking-type transaction is a withdrawal, the platform can debit the customer's financial account and credit the debited funds to the merchant's financial account.

Abstract: Techniques and arrangements for integrating predefined templates with open ticket functionality. For instance, a merchant device can identify a type of transaction between a merchant and a customer, select a ticket type for the transaction based on the type of transaction, and select a transaction flow based on the ticket type. The merchant device can then generate an open ticket for the transaction based on the ticket type, and associated transaction flow with the open ticket. Additionally, the merchant device can generate a visual representation of data associated with the open ticket, where a layout of the data within the visual representation is based on the type of transaction and the transaction flow, and present the visual representation to the merchant. In some examples, the type of transaction is identified using received input. In some examples, the type of transaction is identified based on a group associated with the customer.

Abstract: Method, systems, and apparatus for generating a storefront for a merchant, comprising: receiving transaction data associated with a brick and mortar (BOM) transaction, processing a payment for the BOM transaction, updating inventory data based on the transaction data, receiving a request to generate an online storefront for a point of sale system of the merchant, where the point of sale system includes inventory data of a plurality of items for sale, identifying the plurality of items for sale from the inventory data from point of sale system; generating one or more resources for each item of the plurality of items for sale; causing display of the graphical user interface comprising the one or more resources to be presented to enable purchase of an item, and updating the inventory data based on a purchase of the item by the ecommerce customer.

Abstract: A method of processing a transaction between a customer and a merchant includes receiving from a mobile device of the customer or from another device of the customer an indication of consent to perform a cardless payment transaction with the merchant, receiving from the mobile device an indication that the customer is within a predetermined distance of the merchant, after receiving both the indication of consent and the indication that the customer is within the predetermined distance, sending to a computer system of the merchant an indication of the presence of the customer and personal identifying information for the customer, receiving data indicating a transaction between the customer and the merchant, and submitting the transaction to a financial service for authorization.

Abstract: Techniques and arrangements for integrating predefined templates with open ticket functionality. For instance, a merchant device can identify a type of transaction between a merchant and a customer, select a ticket type for the transaction based on the type of transaction, and select a transaction flow based on the ticket type. The merchant device can then generate an open ticket for the transaction based on the ticket type, and associated transaction flow with the open ticket. Additionally, the merchant device can generate a visual representation of data associated with the open ticket, where a layout of the data within the visual representation is based on the type of transaction and the transaction flow, and present the visual representation to the merchant. In some examples, the type of transaction is identified using received input. In some examples, the type of transaction is identified based on a group associated with the customer.

Abstract: Method, systems, and apparatus for generating a storefront for a merchant, comprising: receiving transaction data associated with a brick and mortar (BOM) transaction, processing a payment for the BOM transaction, updating inventory data based on the transaction data, receiving a request to generate an online storefront for a point of sale system of the merchant, where the point of sale system includes inventory data of a plurality of items for sale, identifying the plurality of items for sale from the inventory data from point of sale system; generating one or more resources for each item of the plurality of items for sale; causing display of the graphical user interface comprising the one or more resources to be presented to enable purchase of an item, and updating the inventory data based on a purchase of the item by the ecommerce customer.

Abstract: A method of processing a transaction between a customer and a merchant includes receiving from a mobile device of the customer or from another device of the customer an indication of consent to perform a cardless payment transaction with the merchant, receiving from the mobile device an indication that the customer is within a predetermined distance of the merchant, after receiving both the indication of consent and the indication that the customer is within the predetermined distance, sending to a computer system of the merchant an indication of the presence of the customer and personal identifying information for the customer, receiving data indicating a transaction between the customer and the merchant, and submitting the transaction to a financial service for authorization.

Abstract: Techniques and arrangements for facilitating synchronization of open ticket functionality utilized by point-of-sale (POS) devices with kitchen display systems. In some example, a POS device associated with a merchant receives customer orders associated with transaction between the merchant and customer(s). The customer orders originate both from user input to the POS device and from an application(s) executing on a separate device. The POS sends the customer orders to a kitchen display system (KDS) associated with the merchant. The KDS aggregates the orders and, responsive to the aggregating, causes presentation of the orders.

Abstract: 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.

Abstract: 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.

Abstract: 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.