Abstract: Product catalogs are received at a first point-of-sale (POS) device of a first business entity from POS devices of a second business entity and a third business entity. At least one product specification is selected from the product catalog of the second business entity and at least one product specification is selected from the third product catalog of the third business entity. A product catalog for the first business entity is then generated at the first POS device that includes a product specification that is different from, but informed by, the received product specifications. The generated catalog is transmitted by the first POS device to a fourth POS device of a fourth business entity.

Abstract: The disclosed technique enables a payer who uses a payment object to pay for goods or services to specify, by using a mobile device, how the payment amount should be apportioned the payer and additional payers. In certain embodiments, the technique involves communication between a mobile payment application installed on the payer's mobile device and a remote payment service system (PSS). The payment amount is transferred from the payer to the payee. The mobile payment application enables the payer to identify additional payers and specify how the payment amount should be apportioned between the payers. The mobile payment application communicates this information to the PSS, which then executes or triggers reimbursement to the payer to carry out the specified apportionment.

Abstract: In an example, a method can include receiving, at a merchant-facing portion of a payment system, data from a customer-facing portion of the payment system indicating a payment transaction between a merchant and a customer, wherein there is a physical connection between the portions; determining that the payment system is unable to access a remote payment service system via an external network; determining that the payment transaction is not preapproved for payment by the remote payment service system; storing the payment transaction on the merchant-facing portion even though the payment transaction is not preapproved; determining that the payment system is able to access the remote payment service system via the external network; and transmitting transaction information including the stored payment transaction to the remote payment service system, via the external network, for processing the stored payment transaction.

Abstract: Product catalogs are received at a first point-of-sale (POS) device of a first business entity from POS devices of a second business entity and a third business entity. At least one product specification is selected from the product catalog of the second business entity and at least one product specification is selected from the third product catalog of the third business entity. A product catalog for the first business entity is then generated at the first POS device that includes a product specification that is different from, but informed by, the received product specifications. The generated catalog is transmitted by the first POS device to a fourth POS device of a fourth business entity.

Abstract: Application Programming Interfaces (APIs) are exposed by a service provider to point-of-sale (POS) devices of a plurality of merchants. Product catalogs including product specifications are received from merchants via a merchant support application executing on the POS devices. Pricing records are received from the POS devices of the merchants that indicate prices, locations, and time periods for the prices. Sales data including quantity, time, and location of historical sales is obtained. A price recommendation is provided to a merchant based at least in part on correlations between the historical sales data and pricing.

Abstract: Techniques associated with a customer-facing device and a merchant-facing device are described herein. In an example, a system can include a customer-facing device configured with a customer application that is executable on an operating system of the customer-facing device to (i) display information to a customer and (ii) receive input from the customer, wherein the customer-facing device includes a payment reader to read payment data from a payment instrument in association with a payment transaction between the customer and a merchant, and a merchant-facing device configured with a merchant application that is executable on an operating system of the merchant-facing device to (i) display information to the merchant and (ii) receive input from the merchant. In at least one example, the customer-facing device and the merchant-facing device can communicate to process, at least in part, the payment transaction associated with the payment instrument via a remote payment service system.

Abstract: Techniques associated with a customer-facing device and a merchant-facing device are described herein. In an example, a system can include a customer-facing device configured with a customer application that is executable on an operating system of the customer-facing device to (i) display information to a customer and (ii) receive input from the customer, wherein the customer-facing device includes a payment reader to read payment data from a payment instrument in association with a payment transaction between the customer and a merchant, and a merchant-facing device configured with a merchant application that is executable on an operating system of the merchant-facing device to (i) display information to the merchant and (ii) receive input from the merchant. In at least one example, the customer-facing device and the merchant-facing device can communicate to process, at least in part, the payment transaction associated with the payment instrument via a remote payment service system.

Abstract: A product catalog service allows merchants to create and store product catalogs indicating products that are available from the merchants. Transaction data from point-of-sale (POS) devices of a plurality of merchants can be received. A first catalog of a first merchant can be obtained from a first POS device of a first merchant. The first catalog contains items to be sold by the first merchant. Using the transaction data and the catalog, a second catalog of items to be sold by a second merchant can be generated or updated and transmitted to the second merchant. Items can be compared using item attributes. Item descriptions in the second catalog can be based on item descriptions in the first catalog.

Abstract: Techniques associated with a customer-facing device and a merchant-facing device are described herein. In an example, a system can include a customer-facing device configured with a customer application that is executable on an operating system of the customer-facing device to (i) display information to a customer and (ii) receive input from the customer, wherein the customer-facing device includes a payment reader to read payment data from a payment instrument in association with a payment transaction between the customer and a merchant, and a merchant-facing device configured with a merchant application that is executable on an operating system of the merchant-facing device to (i) display information to the merchant and (ii) receive input from the merchant. In at least one example, the customer-facing device and the merchant-facing device can communicate to process, at least in part, the payment transaction associated with the payment instrument via a remote payment service system.

Abstract: The disclosed technique enables a payer who uses a payment object to pay for goods or services to specify, by using a mobile device, how the payment amount should be apportioned the payer and additional payers. In certain embodiments, the technique involves communication between a mobile payment application installed on the payer's mobile device and a remote payment service system (PSS). The payment amount is transferred from the payer to the payee. The mobile payment application enables the payer to identify additional payers and specify how the payment amount should be apportioned between the payers. The mobile payment application communicates this information to the PSS, which then executes or triggers reimbursement to the payer to carry out the specified apportionment.

Abstract: The disclosed technique enables a consumer who uses a payment object to pay for goods or services to specify, by using a mobile device, how the transaction amount should be apportioned among multiple payers. In certain embodiments, the technique involves communication between a mobile payment application installed on the consumer's mobile device and a remote payment service system (PSS). The mobile payment application enables the user to specify how many payers there are, who the payers are, and exactly how the transaction amount should be apportioned among the payers. The mobile payment application communicates this information to the PSS, which then executes or triggers reimbursement to carry out the specified apportionment.

Abstract: A product catalog service allows merchants to create and store product catalogs indicating products that are available from the merchants. Transaction data from point-of-sale (POS) devices of a plurality of merchants can be received. A first catalog of a first merchant can be obtained from a first POS device of a first merchant. The first catalog contains items to be sold by the first merchant. Using the transaction data and the catalog, a second catalog of items to be sold by a second merchant can be generated or updated and transmitted to the second merchant. Items can be compared using item attributes. Item descriptions in the second catalog can be based on item descriptions in the first catalog.

Abstract: A method for a transaction with a taxi includes establishing secure communication between a first computing device in a driver section of a vehicle and a second computing device in a passenger section of a vehicle, receiving in the second computing device a card number from a card reader coupled to the second computing device before receiving a signal from a meter indicating an end of a trip for the passenger, after receiving the card number submitting the transaction for authorization from at least one of the first device or the second device, after receiving a signal from the meter indicating the end of the trip for the passenger, displaying an amount of a fare for the trip on a display, and receiving an indication that the transaction is authorized.

Abstract: Techniques for facilitating a secure transaction between a first mobile computing device associated with a driver and a second mobile computing device associated with a passenger are discussed herein. The techniques may include registering an association between a first application executing on the first mobile computing device and a second application executing on the second mobile computing device. The second application may display information indicating an amount of fare for a ride offered by the driver to the passenger. Upon receiving input from the passenger to authorize processing of a payment transaction, the second application may send a request to process the payment transaction using card information. In some examples, the payment transaction is authorized without providing the first application with access to card information.

Abstract: A product catalog service allows business entities to create and store product catalogs indicating products that are available from the business entities. A product catalog includes multiple product family definitions. Each product family definition specifies attribute names of a product family and, for each attribute name, a set of allowed attribute values. In order to specify a particular product variant, an entity may supply one of the allowed attribute values for each specified attribute name of the product. The product catalogs may be received from multiple business entities. Each product catalog may also be shared with multiple business entities. A merchant, for example, may select products from a product catalog to purchase from another merchant. When creating a product catalog, a business entity may reference product family definitions of other product catalogs.

Abstract: In some examples, a computer system may receive transaction information for transactions between card users and a payee that may include transaction card information from a plurality of read events of a plurality of transaction cards at the payee's card reader. In association with the plurality of read events, the system may receive location information of a plurality of mobile devices, each mobile device being associated respectively with one of the plurality of transaction cards in a data structure maintained by the computer system. For instance, the location information for each mobile device may be indicative of a location of the mobile device at a time of a corresponding read event of an associated transaction card. The system may determine an approximate location of the card reader based on the location information of the plurality of mobile devices.

Abstract: A product catalog service allows business entities to create and store product catalogs indicating products that are available from the business entities. A product catalog includes multiple product family definitions. Each product family definition specifies attribute names of a product family and, for each attribute name, a set of allowed attribute values. In order to specify a particular product variant, an entity may supply one of the allowed attribute values for each specified attribute name of the product. The product catalogs may be received from multiple business entities. Each product catalog may also be shared with multiple business entities. A merchant, for example, may select products from a product catalog to purchase from another merchant. When creating a product catalog, a business entity may reference product family definitions of other product catalogs.

Abstract: The disclosed technique enables a consumer who uses a payment object to pay for goods or services to specify, by using a mobile device, how the transaction amount should be apportioned among multiple payers. In certain embodiments, the technique involves communication between a mobile payment application installed on the consumer's mobile device and a remote payment service system (PSS). The mobile payment application enables the user to specify how many payers there are, who the payers are, and exactly how the transaction amount should be apportioned among the payers. The mobile payment application communicates this information to the PSS, which then executes or triggers reimbursement to carry out the specified apportionment.

Abstract: Techniques associated with a customer-facing device and a merchant-facing device are described herein. In an example, a system can include a customer-facing device configured with a customer application that is executable on an operating system of the customer-facing device to (i) display information to a customer and (ii) receive input from the customer, wherein the customer-facing device includes a payment reader to read payment data from a payment instrument in association with a payment transaction between the customer and a merchant, and a merchant-facing device configured with a merchant application that is executable on an operating system of the merchant-facing device to (i) display information to the merchant and (ii) receive input from the merchant. In at least one example, the customer-facing device and the merchant-facing device can communicate to process, at least in part, the payment transaction associated with the payment instrument via a remote payment service system.

Abstract: Method, systems, and apparatus for a method of processing a payment transaction using a mobile device of a merchant. In one aspect, determining the mobile device does not have a connection to an external network; receiving data indicating a payment transaction between a customer and the merchant; determining whether the payment transaction should be stored, where the determining is based on a risk heuristic model that considers one or more of the following: a number of already stored transactions, a value of the payment transaction, a total value, where the total value is a sum of the value of the payment transaction and values of one or more already stored transactions, and risk factors associated with the customer; and based at least on the determination, storing the payment transaction on the mobile device for future processing.