Abstract: This disclosure describes, in part, a payment service that associates customer profiles with an identifier of a payment instrument, and then uses the customer profiles to identify a customer that is using the payment instrument during a transaction with a merchant. For instance, in some examples, the payment service can identify preferences of customers using transaction information that includes an identifier for a payment instrument, and associate the preferences with respective customer profiles. The payment service can then receive transaction information associated with a transaction between a customer and a merchant, identify preferences of the customer using the transaction information, compare the preferences of the customer with preferences stored in the customer profiles, and identify the customer based on the comparing. The payment service can further generate a receipt for the transaction and send the receipt to contact information of the customer.

Abstract: This disclosure describes, in part, a payment service that associates customer profiles with an identifier of a payment instrument, and then uses the customer profiles to identify a customer that is using the payment instrument during a transaction with a merchant. For instance, in some examples, the payment service can identify preferences of customers using transaction information that includes an identifier for a payment instrument, and associate the preferences with respective customer profiles. The payment service can then receive transaction information associated with a transaction between a customer and a merchant, identify preferences of the customer using the transaction information, compare the preferences of the customer with preferences stored in the customer profiles, and identify the customer based on the comparing. The payment service can further generate a receipt for the transaction and send the receipt to contact information of the customer.

Abstract: In some examples, a service provider may coordinate the placement of inventory orders for multiple merchants. The service provider may determine that multiple merchants utilize a same supplier for an item. The service provider may additionally, or alternatively, estimate that inventories of the item for the merchants will reach a threshold lower limit within a particular amount of time of each other. The service provider may designate different times for the merchants to order additional inventory of the item from the supplier.

Abstract: In some examples, a service provider may cause inventory of one merchant to be supplied to another merchant. The service provider may monitor inventory of merchants to determine that a merchant has extra inventory and that another merchant lacks inventory. The service provider may cause the extra inventory of the merchant to be transported to the other merchant that lacks inventory. The service provider may select a courier and request that the courier delivery the extra inventory.

Abstract: This disclosure describes, in part, a payment service that associates customer profiles with an identifier of a payment instrument, and then uses the customer profiles to identify a customer that is using the payment instrument during a transaction with a merchant. For instance, in some examples, the payment service can identify preferences of customers using transaction information that includes an identifier for a payment instrument, and associate the preferences with respective customer profiles. The payment service can then receive transaction information associated with a transaction between a customer and a merchant, identify preferences of the customer using the transaction information, compare the preferences of the customer with preferences stored in the customer profiles, and identify the customer based on the comparing. The payment service can further generate a receipt for the transaction and send the receipt to contact information of the customer.

Abstract: This disclosure describes, in part, a payment service that associates customer profiles with an identifier of a payment instrument, and then uses the customer profiles to identify a customer that is using the payment instrument during a transaction with a merchant. For instance, in some examples, the payment service can identify preferences of customers using transaction information that includes an identifier for a payment instrument, and associate the preferences with respective customer profiles. The payment service can then receive transaction information associated with a transaction between a customer and a merchant, identify preferences of the customer using the transaction information, compare the preferences of the customer with preferences stored in the customer profiles, and identify the customer based on the comparing. The payment service can further generate a receipt for the transaction and send the receipt to contact information of the customer.

Abstract: This disclosure describes, in part, cloud-based generation of receipts using transaction information. In some examples, a payment service can send receipt templates to a point-of-sale (POS) device of a merchant, receive an indication of a selected receipt template from the POS device, and associated the selected receipt template in a merchant profile of the merchant. The payment system can then receive transaction information from the POS device of the merchant, generate a receipt for the transaction using the selected receipt template associated with the merchant profile, and send data representing the receipt to the POS device. In some examples, the receipt template defines a layout of the receipt, text to include in the receipt, and one or more graphics to include in the receipt.

Abstract: Techniques for generating serialized view models that are used for both debugging an application and application support. The techniques include executing an application, creating a view model associated with the application, the view model including information associated with a service provided by the application, and presenting a user interface associated with the view model. The techniques can further include identifying, while presenting the user interface, an error occurring with the application, capturing a stack trace corresponding to the error, capturing a process image of the view model, serializing the process image of the view model to generate a serialized view model, and sending the stack trace and the serialized view model to a service. The service can then use the stack trace and the serialized view model to debug the application.

Abstract: This disclosure describes, in part, techniques for collecting customer information of users at a centralized location and utilizing the information in an intelligent manner to assist customers in improving spending habits and in meeting budgetary goals. In some instances, the centralized location is a payment service that functions to both authorize payment instruments of users for costs of transactions conducted at the merchant, and to collect, generate and propagate budgetary profiles, to make budgetary suggestions and perform budgetary operations with regard to interactions of the merchants and the users.

Abstract: This disclosure describes, in part, cloud-based generation of receipts using transaction information. In some examples, a payment service can send receipt templates to a point-of-sale (POS) device of a merchant, receive an indication of a selected receipt template from the POS device, and associated the selected receipt template in a merchant profile of the merchant The payment system can then receive transaction information from the POS device of the merchant, generate a receipt for the transaction using the selected receipt template associated with the merchant profile, and send data representing the receipt to the POS device. In some examples, the receipt template defines a layout of the receipt, text to include in the receipt, and one or more graphics to include in the receipt.

Abstract: This disclosure describes, in part, a payment service that associates customer profiles with an identifier of a payment instrument, and then uses the customer profiles to identify a customer that is using the payment instrument during a transaction with a merchant. For instance, in some examples, the payment service can identify preferences of customers using transaction information that includes an identifier for a payment instrument, and associate the preferences with respective customer profiles. The payment service can then receive transaction information associated with a transaction between a customer and a merchant, identify preferences of the customer using the transaction information, compare the preferences of the customer with preferences stored in the customer profiles, and identify the customer based on the comparing. The payment service can further generate a receipt for the transaction and send the receipt to contact information of the customer.