Patent Grant
11989718
This disclosure generally relates to databases, data management, and discovery within network environments, and in particular relates to hardware and software for transfer systems.
Peer-to-peer transfers using transfer systems enable transfers of items between user accounts, thereby facilitating the transfer of ownership of such items between users. In conventional transfer systems for transferring items from one user to another user (i.e., “peers”), the transferring user enters a user identifier for the receiving user such as a username, phone number, or email address into a user interface of the transfer system. To initiate the transfer of the item from the transferring user to the correct receiving user, the transferring user first obtains the correct user identifier of the receiving user and then carefully enters the user identifier to the user interface. The transfer system can disassociate the item from the transferring user and associate the item with the receiving user, based on the provided user identifier. This process can be time consuming, prone to user error, and require significant computational resources in presenting appropriate user interfaces to share relevant user identifiers and receive input from transferring users. A transferring user who enters an incorrect user identifier may request the item back from the incorrect recipient, further using computational resources and taking further time, but return is not guaranteed.
Application programming interface (API) based technologies for integrating merchant applications and/or systems with a payment service system to enable split bill payment and purchase transfer introduced here may be better understood by referring to the following Detailed Description in conjunction with the accompanying drawings, in which like reference numerals indicate identical or functionally similar elements.
An application programming interface (API) is described for integrating merchant applications and/or systems with a payment service system to enable split bill payment and purchase transfer. In some embodiments, merchant applications and/or systems can integrate API modules provided by a payment service system to request payment of a bill that is split or shared among multiple bill payers (“split bill payment technology”). In other embodiments, merchant applications and/or systems can integrate the API modules to facilitate transfers of purchased “units” to other users (“purchase transfer technology”).
In some embodiments, integrating the API with a point-of-sale (PoS) system enables merchants to split a bill among any number of users or bill payers and receive payments collected from the payers, without having to handle, e.g., swipe multiple payment cards or indeed, any payment card. Consider, for example, a party of five that receives a $200 bill (before or after tax (if applicable) and tip) at a restaurant. Suppose the party decides to divide the bill evenly among themselves, with each bill payer being responsible for $40. The restaurant can have a merchant application executing on a merchant system (e.g., PoS terminal). A bill splitting API provided by the payment service system can be integrated into the merchant application to enable the merchant application to send requests and/or data to the payment service system using various methods defined by the bill splitting API. A worker at the restaurant (“merchant”) can input information (e.g., a username, an email address, a phone number, an alias, etc.) about each bill payer into the merchant application. Alternatively, if the merchant system and mobile computing devices (“mobile devices”) of the bill payers have a Bluetooth Low Energy (BLE) radio turned on, the merchant system can establish a connection with each of the mobile devices using a BLE connection, and exchange information that can be used by the merchant application and the payment service system to automatically identify each bill payer in the party of five. In some embodiments, the merchant system can identify the bill payers using geo-fencing technology. Geo-fencing technology uses information from a Global Positioning System (GPS), cellular towers and/or Wi-Fi routers to compare a location of the bill payer's device to a location of the merchant system to determine that the bill payer is at the merchant location. The merchant can also assign each bill payer a portion of the bill. In this example, each person is assigned $40. However, the merchant application can also be used to assign items in the bill to respective bill payers and determine each bill payer's share of the bill based on the assignment. The merchant application can then generate and send a split bill payment request that includes information identifying each bill payer in the party of five and a corresponding portion of the bill that the bill payer is responsible for via the bill splitting API. The split bill payment request is a request for payment of a bill that is split or shared among multiple bill payers. The payment service system sends a payment request in the amount of $40 to each bill payer (e.g., via a payment application on a mobile device, text message, email message). Each bill payer receiving the payment request approves the requested $40 or a different amount to pay for the bill payer's share of the bill, which would then be transferred from the bill payer's financial account to the merchant's financial account. In some embodiments, a bill payer can approve an amount different from the requested amount, but generally greater than the requested amount to pay for unaccounted costs, such as tax, tip, etc. For example, a bill payer in the party of the five can approve $47, the additional $7 being added for tip.
In this manner, the bill splitting API enables the merchant to use the merchant application to send a single split bill payment request to charge multiple bill payers' respective portions of a bill. Consequently, the split bill payment technology significantly reduces the burden on the merchant and speeds up the time to clear a bill, as the merchant need not swipe multiple payment cards one by one to process multiple bills for multiple bill payers.
Various embodiments of the split bill payment technology are described. In some embodiments, a payment service system receives a request to split payment of a bill for a transaction associated with a merchant among multiple bill payers who have shared the transaction with the merchant. The request can include information identifying the merchant, multiple bill payers and a bill payer's portion of the bill, and the request can be received from a merchant application executing on a point-of-sale system operated by the merchant via a bill splitting application programming interface (API) provided by the payment service system. The merchant application is a third-party application that is not associated with the payment service system and the merchant has a financial account pre-registered with the payment service system. The payment service system can send a payment request to mobile devices of the bill payers for payment of the respective portion of the bill. The payment request can cause a payment application executing on a bill payer's mobile device to prompt the bill payer to approve the payment request. The payment service system can receive a response from the mobile devices of the bill payers, indicating an approval of a specified amount for payment of the bill payer's portion of the bill which can cause the payment service system to a transfer of the specified amount approved by the bill payers from the bill payers' financial accounts to the merchant's financial account and transmit, using the bill splitting API, a confirmation to the merchant application executing on the point-of-sale system indicating the payment of the bill by the multiple bill payers.
In some embodiments, a payment service system comprises a server that receives a request for split bill payment from a merchant system and analyzes the request to identify, for example, a merchant associated with the merchant system, multiple users, and the users' portion of the bill. The payment service system can then send a payment request to a mobile device of the users to obtain an approval to withdraw funds to pay for the users' portion of the bill from the users' financial account. When the payment service system receives a response from the users approving a withdrawal of a specified amount of funds from the users' financial account to pay for the users' portion of the bill, the payment service system initiates a transfer of the specified amount of funds approved by the users from the users' financial account to a financial account associated with the merchant.
In some embodiments, a merchant application executing on a merchant system receives an indication to split a bill among multiple bill payers and in response determines the bill payers' share of the bill. The merchant application then sends a split bill payment request to a payment service system. The split bill payment request can be sent using an application programming interface (API) provided by the payment service system and can include information identifying the bill payers, the bill payers' share of the bill, and the merchant. The split bill payment request causes the payment service system to collect payments corresponding to the bill payers' share of the bill and deposit the collected payments to a financial account associated with the merchant. The merchant application then receives a confirmation via the API of the deposit of the payments corresponding to the bill payers' share of the bill into the financial account associated with the merchant.
In some embodiments, integrating the API with the merchant application and/or system enables a user to transfer purchases. Consider for example, a user who purchases three tickets to an event using a merchant application of an event organizer (“merchant”). The merchant application can be integrated against a purchase transfer API provided by the payment service system that enables the merchant application to send the tickets, electronically, to a payment application (directly or through the payment service system) that the user can access. The user can assign one of the tickets worth $50 to a contact John and another one worth $75 to a contact Jane and request a transfer. The payment service system can then send the ticket worth $50 to John and the ticket worth $75 to Jane. When John and Jane accept or “claim” the respective tickets, each acceptance automatically triggers a transfer of a value of the accepted ticket from a financial account associated with the receiver of the ticket to a financial account associated with the user. In some cases, information about the new ticket holders can be transmitted to the merchant via the purchase transfer API to enable the merchant to reissue the tickets in the names of the new ticket holders. The merchant can then send the reissued tickets to the new ticket holders.
In this manner, a merchant application can use the purchase transfer API to send purchase units or information about purchase units, which enables not only the transfer of the purchase units to others, but also collection of the monetary value of the transferred units. As used herein, a “purchase unit” or simply a “unit” is a unit of an item that was purchased and that has a monetary value or price associated with it. For example, a purchase unit can be one ticket having a value of $10 or one television set having a value of $500. Similarly, two purchase units can be two tickets, but both tickets need not have the same value. For example, one ticket can be worth $10, while another one worth $15. The purchase transfer technology disclosed herein is advantageous as a user can receive payments for the transferred units and is not forced to give away the units for free. The burden on the user is also significantly reduced as the information relating to a purchase unit is transferred directly from the merchant application or system to the payment application or the payment service system. The user need only assign a purchase unit to a person (e.g., by selecting a contact from a contact list, inputting an email address or a phone number, by selecting a person who is detected to be nearby the user's device) to initiate a transfer of the purchase unit to that person. The payment service system can collect the payment from that person and deposit the payment into the user's financial account. Moreover, the technology enables a purchase unit to be transferred multiple times, while keeping the monetary value of the purchase unit fixed. Taking the example above, John can transfer his ticket to Jill and receive payment of $50 once Jill accepts or claims the ticket. Since the value of the ticket remains fixed with each transfer, the technology enables merchants to control the prices of purchase units regardless of the number of times the purchase units are transferred or resold. This prevents the practice of ticket scalping, which can artificially inflate prices of items.
Various embodiments of the purchase transfer technology are described. In some embodiments, the payment service system can receive information from a merchant system indicating that the merchant system completed a sale of a transferable ticket to a user. In other embodiments, the sale may be related to other items such as magazine subscription, phone, water bottles, etc., that the user may purchase from the merchant. The received information can identify, for example, a monetary value of the transferable ticket and the user who purchased the transferable ticket. The payment service system can determine that the user has a financial account registered with the payment service system. The payment service system can transmit information about the transferable ticket to a payment application executing on a user mobile device of the user who purchased the transferable ticket. The payment application is associated with the payment service system. The payment service system can receive a request from the payment application executing on the user mobile device to transfer the transferable ticket from the user to a receiver having a receiver mobile device. The receiver can be identified based on at least one of the receiver mobile device being within a pre-defined range of the user mobile device to enable the user and receiver mobile devices to exchange information over a Bluetooth Low Energy (BLE) wireless link or a list of contacts of the user accessible to the payment application on the user mobile device. The payment service system can send a transfer of the transferable ticket to the receiver and receive from the receiver a response accepting the transfer of the transferable ticket. Upon receiving the acceptance response, the payment service system can cause a transfer of an amount corresponding to the specific monetary value of the transferable ticket from a financial account associated with the receiver to the financial account associated with the user and transmitting a confirmation of the transfer of the transferable ticket to the user. In some embodiments, even if the user has no financial account registered with the payment service system, the payment service system can receive the transfer request but hold off processing the transfer request until the user registers a financial account by providing information about a payment card (e.g., credit/debit/pre-paid card number, expiration date, card verification value, expiration date, etc.) to the payment service system. Similarly, in some embodiments, the receiver may not have a financial account registered with the payment service system. The payment service system can, prior to sending the transfer of the transferable ticket to the receiver, access a datastore that stores user information associated with a plurality of users using at least one of a receiver email address or receiver phone number included in the request to determine that the receiver has no financial account registered with the payment service system. In such a case, the payment service system can send a notification to the receiver using the receiver email address or receiver phone number to register a financial account with the payment service system to cause the transfer of the amount corresponding to the specific monetary value of the transferable ticket from the financial account associated with the receiver to the financial account associated with the user and complete the transfer of the transferable ticket from the user to the receiver.
In some embodiments, the payment service system comprises a server and the server can receive purchase information from a merchant system. The purchase information can include, for example, information that identifies a unit purchased by a first user at the merchant system, a price of the unit and the first user. When the server receives a request from a client device of the first user to transfer the unit to a second user, the server can send a request to a client device of the second user to accept the transfer of the unit. The server can receive a response from the client device of the second user accepting the transfer of the unit and in response, withdraw an amount corresponding to the price of the unit from a financial account associated with the second user and deposit the withdrawn amount to a financial account associated with the first user. The server can also notify the first user of the transfer of the unit to the second user.
In some embodiments, a payment application executing on a computing system of a first user can receive and display on a user interface of the computing system, information identifying a first unit purchased by the first user and a price of the first unit paid by the first user. In some embodiments, the information identifying the first unit purchased by the first user and the price of the first unit paid by the first user can be received from a merchant system remote from the computing system. In other embodiments, the information identifying the first unit purchased by the first user and the price of the first unit paid by the first user can be received by the payment application executing on the computing system from a merchant application executing on the same computing system. In yet other embodiments, the information identifying the first unit purchased by the first user and the price of the first unit paid by the first user may be received from a payment service system. In such embodiments, the first user may have purchased the first unit from a second user, instead of the merchant system.
The payment application can also identify potential recipients for user selection. In some embodiments, the potential recipients for user selection can be identified based on a connection established between the computing system and client devices of the potential recipients using a near-field communication technology, for example, a Bluetooth Low Energy wireless technology. The payment application can further receive a selection of a second user from the potential recipients as a recipient of a transfer of the first unit and receive a request to transfer the first unit to the second user. In response, the payment application can cause a transfer of an amount corresponding to the price of the first unit from a financial account of the second user to a financial account of the first user.
Various embodiments of the disclosed technologies will now be described. The following description provides specific details for a thorough understanding and an enabling description of these embodiments. One skilled in the art will understand, however, that the disclosed systems and methods may be practiced without many of these details. Additionally, some well-known structures or functions may not be shown or described in detail, so as to avoid unnecessarily obscuring the relevant description of the various embodiments. The terminology used in the description presented below is intended to be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific embodiments of the disclosed technologies.
The client devices 102-1, . . . , 102-N (hereinafter “client devices 102”) are associated with end-users. In some embodiments, client devices 102 have payment applications 120 associated with the payment service system 108 installed thereon. The payment application 120 can be used by a user to send payments or payment requests to other users. The payment application 120 can also be used by the user to receive payment requests from other users and receive notifications of payments made by other users. The client device 102 can be a desktop computer, a laptop computer, a mobile device, a tablet, or any other processing device. The mobile device can be, for example, a smart phone, a tablet computer, a phablet, a notebook computer, a wearable device, or any other form of mobile processing device. In some embodiments, the client device 102 can include a network interface based on Bluetooth technology (e.g., Bluetooth Low Energy or BLE) to enable the client device 102 to detect and establish a connection with another client device 102 having a similar network interface that is nearby, and exchange information over the established connection.
In some embodiments, the payment application 120 executing on the client device 102 can interface with the network interface and provides user identifying information for exchange with other nearby client devices 102. Such user identifying information that can be exchanged between client devices that have established a connection between each other can include, but is not limited to: a user identifier (e.g., username or UID), an application identifier, a device identifier, a phone number, an email address, an alias, or any other information that enables a payment application 120 of one client device, e.g., client device 102-1 to, directly or by querying a remote server (e.g., payment service system 108), identify a user of a connected client device, e.g., client device 102-2.
The environment 100 can include computer systems of financial institutions or banks 118. The financial institutions 118 include banks associated with users and merchants. For example, some financial institutions issue payment cards (e.g., debit cards, credit cards, prepaid cards, gift cards, and so on) to users. Each user has a financial account with a financial institution 118 and can use a payment card issued by the financial institution 118 to access the user's financial account to deposit or withdraw funds.
The environment 100 also includes a computer system of a card payment network (hereinafter “card payment network 116”) which can be a credit and/or debit card processing network that handles authorization and settlement of transactions made using debit and/or credit cards.
The environment 100 also includes a computer system of a payment service (hereinafter “payment service system 108”) associated with the payment application 120. The payment service system 108 facilitates electronic transfer of money from a financial account of one user to a financial account of another user. In order for the transfer of money to occur, the user sending the money and the user receiving the money each have a user account with the payment service system 108. The user account is associated with or linked to a payment card such as a debit card, a credit card, a prepaid card, or the like. In this manner, the financial accounts of the users are pre-registered with the payment service system 108.
Generally, a user can send a payment or request for payment of a specified amount using the payment application 120. The payment application 120 automatically generates an email message, text message, instant message, or the like, populated with the necessary information for sending by the sender. For example, the “To” field of the email message can be populated with the email addresses of the recipients identified by the payment application 120 (e.g., based on BLE connection) or input by the sender, the “cc” field can be populated with an email address associated with the payment service system 108 and the amount of the payment or the request for payment can be included in the body of the message. In other embodiments, the payment application 120 can generate a text message or an HTTP request including the recipient information, the amount of the request, and a type of the request (e.g., payment or payment request).
The payment service system 108 receives the email message (or text message or HTTP request) sent by the sender and parses the email message to extract a sender email address of the sender, receiver email addresses of the receivers and the amount to be requested or sent. If the email message is for sending a payment request, the payment service system 108 can send an email message or a push notification to each of the receiver email addresses to notify the receivers regarding the sender's payment request. A receiver can then approve the request (e.g., via the email message, the push notification) to trigger the transfer of the approved payment amount from the receiver's financial account at a financial institution 118 to the sender's financial account at a financial institution.
If the email message is for sending a payment, the payment service system 108 generates and sends a payment request including the necessary information (e.g., a payment amount, the sender's payment card information, the receiver's payment card information) to the card payment network 116 (e.g., Star, NYCE or Pulse for debit card processing and Visa, MasterCard, etc., for debit/credit card processing) for authorization and settlement. The card payment network 116 communicates with the financial institutions 118 of the sender and the receiver to facilitate the transfer of the payment amount. After the payment request is approved, the financial institution of the sender debits the sender's financial account in real time. As a part of the settlement process, the payment amount debited from the sender's financial account is sent to the receiver's financial account and the receiver's financial account is credited, thereby completing the transaction. Once the transaction is completed, a notification regarding the crediting or deposit of the payment amount can be sent to the receivers (e.g., via an email message, a text message, a push notification).
The environment 100 also includes merchant systems 105 associated with merchants. A merchant system 105 can be a point of sale (PoS) at which a user can make a payment to the merchant in exchange for goods provided or services rendered. The merchant system 105 can include, but is not limited to: a PoS terminal, an electronic cash register, a tablet or other mobile device based PoS, and/or any processing device that can execute a merchant application 110 to enable transactions. In some embodiments, the merchant system 105 can also be a server hosting a merchant website providing checkout functionality. The merchant application 110 can be integrated against an API or APIs provided by the payment service system 108. The API integration enables the merchant application 110 to send requests and/or other data to the payment service system 108 using specific methods defined by the API and receive responses from the payment service system 108.
Each of the aforementioned computer systems can include one or more distinct physical computers and/or other processing devices which, in the case of multiple devices, can be connected to each other through one or more wired and/or wireless networks. All of the aforementioned devices are coupled to each other through an internetwork 106, which can be, or include, the Internet and one or more wired or wireless networks (e.g., a Wi-Fi network and/or a cellular telecommunications network).
It should be noted that the environment 100 can accommodate transactions involving payment cards such as debit cards, credit cards, pre-paid cards, bank accounts, mobile payment applications and the like. The payment application 120 can include an electronic wallet application, money transfer application (e.g., application for sending and requesting payments via email or text message), or any other application having an account that is linked to one or more payment cards and/or financial accounts and can be used by the owner of the client device to initiate transactions.
The example checkout interface is applicable to a restaurant type merchant. The checkout interface of a merchant application 110, executing on a merchant system 105, depicts an itemized bill 205. The itemized bill 205 lists items of order, quantities, prices and a total. In some embodiments, the checkout interface can include a cancel button 210 to cancel and go back to a previous screen, an add tip button 215 to add a tip to the total amount, and a charge button 225 to charge the bill 205 to a payment card or conduct a cash transaction. In some embodiments, the checkout interface can also include a “split the bill” button 220 which when selected causes the merchant application 110 to identify bill payers among whom the bill is to be split, and generate and send a split bill payment request to the payment service system 108.
In some embodiments, when the “split the bill” button 220 in
In some embodiments, the user interface of the merchant application 110 can include an “add tip” button 325 to add tip to each bill payer's portion of the bill. A similar option for tax or other surcharges can also be included in some embodiments. Once each bill payer's share of the bill has been determined, the “charge” button 330 can be activated, which causes the merchant application 110 to generate a split bill payment request based the information about the bill payers and their respective shares of the bill, and send the request to the payment service system 108. The request can be sent using the bill splitting API, over HTTP/S for example, and can include, but is not limited to: identifiers corresponding to the bill payers, each bill payer's share of the bill, and a merchant identifier.
As illustrated, the merchant system 105, multiple client devices (e.g., 102-1, 102-2, and 102-3) and the payment service system 108 are each coupled to a network 106 for transmission of requests and responses. The merchant system 105 establishes a connection with nearby client devices 102-1, 102-2 and 102-3 over a BLE connection 410 supported by the BLE interface (or radio) 305 on the merchant system 105 and the BLE interface (or radio) 205 on the client devices 102-1, 102-2 and 102-3. In some embodiments, other low energy wireless technologies may be used by the merchant system 105 to establish a connection with the client devices. The merchant system 105 and the client devices can also include other network interfaces, e.g., Wi-Fi/3G/4G/LTE 405 to facilitate communication (e.g., data transfer) between the client devices and the merchant system 105 over network 106. In some embodiments, communication between the merchant system 105 and the client devices facilitated by network 106 can occur when the client devices are within a predefined range of the merchant system 105. The payment application 120 on a client device, enabled by GPS, cell tower and/or Wi-Fi data, can detect when the client device is within, for example, a range of 100 meters, from the merchant location (i.e., where the merchant system 105 is located), and can provide user identifying information to the merchant system 105 over network 106.
In some embodiments, the merchant application 110 executing on the merchant system 105 can use the established connection 410 to exchange information with the payment applications 120 executing on the nearby client devices to identify users of the client devices 102-1, 102-2 and 102-3. The information that is exchanged can include, but is not limited to: a username, a user identifier, an email address, a phone number, a device identifier, an application identifier, an alias, or the like. The merchant can select all or some of the nearby users to be the bill payers and assign to each bill payer a portion of the bill. The merchant can then use the merchant application 110 to submit a split bill payment request 420 to the payment service system 108. The split bill payment request can include information such as, but not limited to: a merchant identifier, identifiers associated with the bill payers, and each bill payer's portion or share of the bill. The request is submitted to the payment service system using a bill splitting API provided by the payment service system 108.
The payment service system 108 receives the split bill payment request 420 from the merchant application 110 and analyzes the request to identify the merchant, the bill payers and each bill payer's share of the bill. In some embodiments, the payment service system 108 can determine whether the bill payers have a financial account registered with the payment service system. For example, the payment service system 108 can determine that one of the bill payers does not have a financial account registered with the payment service system, and in response, can send a request to the bill payer (e.g., using the bill payer's email address or phone number included in the split bill payment request) to request the bill payer to register a financial account with the payment service system by providing details of a payment card, e.g., payment card number, security code, expiration date, address, and/or the like, or a bank account from which funds can be withdrawn for bill payment. The payment service system 108 generates and sends payment requests 425a, 425b and 425c to the bill payers' client devices 102-1, 102-2 and 102-3 respectively. The payment requests can be sent via an email, a text message, instant message, an HTTP/S request, or the like. The payment applications 120 on the client devices can receive the payment requests and prompt the bill payers to confirm the payment requests from the merchant. For example, the payment application 120 executing on the client device 102-3 can display a notification (e.g., 445) based on the payment request 425c and obtain a response from the bill payer. The notification 445, as shown, can identify the merchant (“PDX Bistro”) and a bill amount (“$14.50”) that is being requested. The bill payer can select a “pay” button 450a to approve an amount corresponding to the payment request (e.g., the bill payer's share of the bill). The bill payer can select the “add tip” button 450b to add tip (e.g., $3.00) to the requested amount (“$14.50”) and approve an amount different from the requested amount (e.g., approve $14.50+$3.00 or $17.50 instead of $14.50). The “decline” button 450c can be selected by the bill payer to decline the payment request. The bill payers' responses 430a-c to the payment requests 425a-c are transmitted by the payment applications 120 to the payment service system 108. In some embodiments, if a bill payer does not have a payment application 120 on his or her client device, a payment request can still be sent to the bill payer's client device as an email message or a text (e.g., SMS, MMS message). The bill payer can then respond to the email message or text message to approve an amount for bill payment. In some embodiments, the message can include a link, which when selected redirects the bill payer to a webpage from where the user can approve an amount.
After receiving responses approving the payment requests, the payment service system 108 identifies each bill payer' financial account and a financial account associated with the merchant. The payment service system 108 can then exchange transaction authorization messages 435 with the card payment network 116 to cause an amount approved by each bill payer to be transferred from the bill payer's financial account to the financial account of the merchant. The payment service system 108 can then use the bill splitting API to send a split bill payment confirmation 440 to the merchant application 110 as a response to the split bill payment request 420.
Similar to the first embodiment described in relation to
As described in relation to
The payment applications 120 on the client devices receive the split bill payment requests from the merchant system 105. As described in relation to
In some embodiments, the merchant system 105 can be a merchant server, and the merchant application 110 can be a web-based application or website hosted on the merchant server or a mobile application supported by the merchant server. In relation to
In some embodiments, the transfer of the purchase unit information can occur automatically, without the user having to initiate the transfer by selecting the “transfer ticket” button 520, for example. The payment service system 108 receiving the purchase unit information can then request the user to confirm whether the user would like to transfer any of the purchase units to another. In other embodiments, the payment service system 108 can prompt the user for transfer if the purchase unit meets one or more criteria. Examples of such purchase transfer eligibility criteria can include, but are not limited to: at least two purchase units (e.g., two or more television sets, or two or more concert tickets), transfer requested within a certain period from the purchase date, the number of times a purchase unit has been transferred, and/or the like.
The user interface 530 of the payment application 120 depicts purchase units 540a-d and their monetary values (e.g., 545a) determined from the purchase unit information received from the merchant (e.g.,
As illustrated, the merchant system 105, multiple client devices (e.g., 102-1, 102-2, 102-3) and the payment service system 108 are each coupled to a network 106 for transmission of requests and responses. A user of the client device 102-1 uses a merchant application or a merchant website to place a purchase order 605 of multiple units with the merchant system 105. In some embodiments, the user of the client device 102-1 can also provide an indication 610 to transfer the purchase units to the merchant system 105. In some embodiments, the merchant system 105 can transmit the purchase unit data 615a to the payment service system 108, which in turn can forward the purchase unit data 615b to the payment application 120 on the client device 102-1. In other embodiments, the merchant system 105 can transmit the purchase unit data 615c directly to the client device 102-1.
In some embodiments, the client device 102-1 can establish a BLE connection with multiple nearby client devices, for example, client devices 102-2 and 102-3 and exchange information (e.g., 620a, 620b) using the BLE interface 205 on the client devices. The client devices can also include other network interfaces, e.g., Wi-Fi/3G/4G/LTE interfaces to connect to the network 106, and in some instance to each other (e.g., using local Wi-Fi). The BLE connection enables the client device 102-1 to identify the users of the client devices 102-2 and 102-3. The payment application 120 can use the user's contacts and/or the nearby users to build a list. The user can then assign a purchase unit to a receiver selected from the list. The purchase unit assignment data 625 can then be transmitted to the payment service system 108. Taking the example of
Each receiver can accept or claim the transfer of the purchase unit or units. Alternatively, the receiver can decline the transfer of the purchase unit or units. In some embodiments, the receiver can also partially accept the transfer of purchase units. For example, if a receiver receives a transfer of two tickets, but needs only one, the receiver can accept one ticket and decline the other one. The receivers' responses can then be transmitted by the payment applications 120 to the payment service system 108. When the payment service system 108 receives responses from the receivers accepting the transfers of the purchase units, it can exchange transaction authorization messages 635 with the card payment network 116 to cause an amount corresponding to the total monetary value of a transfer accepted by a receiver to be transferred from the receiver's financial account to a financial account of the user who initiated the transfer. For example, if receiver Ed accepts the transfer of the two tickets, the payment service system 108 initiates a transfer of $298 corresponding to the total monetary value of the transfer from receiver Ed's financial account to the financial account of the user. By way of another example, if receiver Ed accepts the transfer of only one of the two tickets, then a monetary value of the one ticket accepted by receiver Ed is transferred from his financial account to the financial account of the user.
In some instances, information about the transfer of the purchase units may be needed by the merchant for various reasons. For example, in the case of tickets, new tickets may need to be issued to the current ticket holders. Similarly, the merchant may need to know who the end owner of a purchase unit is in case of product recalls, for physical or digital delivery of the unit, for receipt delivery, or the like. Thus, in some embodiments, the payment service system 108 can send purchase unit transfer data 640 to the merchant system 105. In some embodiments, the merchant system 105 can then provide receipts 645a, 645b to the receivers of the transfer. For example, receiver Ed can receive two tickets reissued in his name and receiver Jack can receive one ticket reissued in his name.
In some embodiments, the merchant system 105 includes memory 702 for storing instructions associated with multiple modules of the merchant application 110, and network interfaces 760, among components. The merchant application 110 can include various modules including a bill splitting module 705 having a bill payer identification module 710 and bill splitting API module 715, a purchase transfer module 735 having a purchase transfer API module 745 and a purchase transfer receipt generator 750, a user interface module 756 and a notification module 755, among others. It should be noted some embodiments of the merchant application may exclude the purchase transfer module 735, while other embodiments may exclude the bill splitting module 705.
In some embodiments, the bill splitting module 705 can be triggered by an indication from a merchant to split a bill among multiple bill payers. The bill payer identification module 710 can identify multiple users having mobile devices that are connected to the merchant system 105 over a low energy wireless connection or are otherwise in proximity to the merchant system 105. The bill payer identification module 710 can then identify at least some of the nearby users as bill payers among whom the bill is to be split. The identification can be based on a selection or confirmation from the merchant. The bill splitting module 705 can also determine each bill payer's share of the bill. The determination can be based on indications from the merchant. For example, by default, the bill splitting module 705 can split a bill equally among the bill payers. In some embodiments, the module 705 can receive assignment of items on the bill to the respective bill payers and determine each bill payer's share of the bill based on the received assignment of items and associated prices.
In some embodiments, the bill splitting API module 715 uses information identifying the bill payers and each bill payer's share of the bill and information identifying the merchant to generate and send a split bill payment request to the payment service system 108. Sending the split bill payment request can cause the payment service system 108 to collect payments corresponding to each bill payer's share of the bill and deposit the collected payments to a financial account associated with the merchant identifier. The bill splitting API module 715 can also receive from the payment service system a confirmation of the deposit of the payments corresponding to each bill payer's share of the bill to the financial account associated with the merchant identifier. In some embodiments, the notification module 755 can generate a receipt or notification for each bill payer for the payment of the bill payer's share of the bill.
The purchase transfer module 735 facilitates transfer of purchase units. In some embodiments, the purchase transfer API module 745 receives and sends purchase unit information to the payment service system 108 via the purchase transfer API. In other embodiments, the purchase transfer API module 745 can also send purchase unit information directly to a payment application of the user associated with the purchase of the units. In some embodiments, the sending can occur automatically, while in others, the sending can occur in response to a user input. In some embodiments, the purchase transfer API module 745 can also receive purchase unit transfer data from the payment service system 108 via the purchase transfer API. The purchase unit transfer data can be used by the receipt generator 750 to generate receipts (e.g., reissue tickets) for the receivers of the transfers.
In some embodiments, the merchant application includes a notification module 755 that can generally handle generation and display of any incoming and/or outgoing notifications such as push notifications, email, text messages, and/or the like. The user interface module 756 provides various components for building graphical user interfaces of the merchant application 110. The network interface 760 can be a networking module that enables the merchant application 110 to transmit and/or receive data in a network with an entity that is external to the client device 102 (e.g., other client devices, the payment service system 108), through any known and/or convenient communications protocol supported merchant system 105 and the external entity. The network interface 760 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, Wi-Fi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth (e.g., BLE), a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
The client device 102 includes a memory 805 for storing instructions associated with multiple modules of the payment application 120 and network interfaces 840, among other components. In some embodiments, the payment application 120 can include a nearby user identification module 810 having a filter 815, a purchase unit assignment module 825, a transaction processor 820, a user interface module 830, and/or a notification module 835. One or more of these components or modules may be optional in some embodiments.
The payment application 120 enables a user to send a payment to or request a payment from another user. The transaction processor 820 receives an amount, an indication of a type of request, and identification of one or more recipients from a user, and based on the type of request specified, generates a message (e.g., an email, a text message, an instant message) based on the received information for the user to send to the payment service system 108 for processing. The nearby user identification module 810, in some embodiments, identifies multiple devices (and thereby individuals or users associated with the devices) that are nearby or in proximity to the client device 102. In some embodiments, the client device 102 can be considered to be nearby or in proximity of another device when the client device 102 has established a connection with the other device using a network interface such as a BLE network interface. A BLE connection can be established when two devices are within a pre-configured range. A typical BLE connection range is 20 meters, but it is possible to extend this range to over 100 meters. In some embodiments, the maximum range for the BLE connection can be set by the payment application 120. Alternatively, the maximum range can be configured by a user (e.g., via the payment application 120 or via the device settings). In some embodiments, the nearby user identification module 810 can consider another device as being near the client device 102 when the two devices are connected to the same wireless (e.g., Wi-Fi) network (e.g., same wireless access point) or the same cellular network. Once a connection with a nearby device has been established, the nearby user identification module 810 can exchange information (e.g., user identifying information) with the nearby device over the established connection. In some embodiments, the nearby user identification module 810 can apply a contact filter 815 to identify a subset of nearby users that are contacts of the user.
The purchase unit assignment module 825 can receive purchase unit information provided by a merchant, and can provide the purchase unit information to the user to enable the user to assign a purchase unit to a receiver selected from a list of users identified by the nearby user identification module or from a list of contacts. In some embodiments, the user can also enter receiver information. When the user submits the assignment data for transfer, the purchase unit assignment module 825 can provide the assignment data from the user to the transaction processor 820 to cause the payment service system 108 to use the assignment data to send a transfer of the purchase unit to the receiver.
The notification module 835 can generally handle generation and display of any incoming and/or outgoing notifications such as push notifications, email, text messages, and/or the like. The user interface module 830 provides various components for building graphical user interfaces of the payment application 120. The network interface 840 can be a networking module that enables the payment application 120 to transmit and/or receive data in a network with an entity that is external to the client device 102 (e.g., other client devices, the payment service system 108), through any known and/or convenient communications protocol supported client device 102 and the external entity. The network interface 840 can include one or more of a network adaptor card, a wireless network interface card (e.g., SMS interface, Wi-Fi interface, interfaces for various generations of mobile communication standards including but not limited to 1G, 2G, 3G, 3.5G, 4G, LTE, etc.,), Bluetooth (e.g., BLE), a router, an access point, a wireless router, a switch, a multilayer switch, a protocol converter, a gateway, a bridge, bridge router, a hub, a digital media receiver, and/or a repeater.
In some embodiments, the payment service system 108 can include a request processor 910, a bill splitting API module 915, and a purchase transfer API module 920, among other components. One or more of these components can access one or more database tables including a transaction history database table 950, a payment card database table 955, a user account database table 960, a purchase transfer database table 965, and/or a merchant account database table 970 to retrieve data and/or store data.
The bill splitting API module 915 receives a split bill payment request from a merchant application executing on a merchant system. The split bill payment request can include information identifying a merchant associated with merchant system (e.g., merchant identifier), multiple bill payers and each bill payer's portion of the bill. The bill splitting API module 915 provides the information in the request to the request processor 910. The request processor 910, via the notification module 930, sends to a client device of each bill payer, a request or message for payment a respective portion of the bill. The message can be in the form of a push notification, an email, a text message, an instant message or other communication means. The request processor 910 receives a response from each bill payer approving a specified amount for payment of the bill payer's portion of the bill. The request processor 910 then identifies a financial account associated with each bill payer, and a financial account associated with the merchant and communicates with a payment card network (e.g., the payment card network 116 of
The purchase transfer API module 920 receives purchase unit information from a merchant system associated with a merchant. The purchase unit information is associated with a purchase of multiple units by a user via the merchant system. Each purchase unit has a monetary value associated with it. The purchase transfer API module 920, in some embodiments, can analyze the purchase transfer request to identify the user and transmit the purchase unit information to a payment application on a client device of the identified user. In some embodiments, the purchase transfer API module 920 can also receive purchase unit assignment data from the payment application on the client device. The purchase unit assignment data assigns at least one purchase unit to a receiver for transfer to the receiver. The purchase transfer API module 920 can provide information about the receiver, and the purchase unit to the request processor 910. The request processor 910 then sends a transfer of the purchase unit having a specific monetary value to the receiver and requests a response. The request processor 910 can receive a response from the receiver that can indicate that the receiver accepted the transfer or declined the transfer of the purchase unit. If the receiver accepted the transfer of the purchase unit, the request processor 910 causes an amount corresponding to the monetary value of the purchase unit to be transferred from a financial account of the receiver to a financial account of the user. In some embodiments, the purchase transfer API module 920 can transmit information about the transfer of the purchase unit to the receiver to the merchant system.
One or more of these components can access one or more database tables including a transaction history database table 950, a payment card database table 955, a user account database table 960, a purchase transfer database table 965, and/or a merchant account database table 970 to retrieve data and/or store data. The transaction history database table 950 can store data relating to all transactions in association with a user identifier or merchant identifier. The payment card database table 955 can store payment card details such as payment card type, payment card number or hash thereof, security code, expiration date, and/or the like in association with a user identifier. The user account database table 960 can store data relating to users of the payment service system and can include data fields such as, but not limited to: user identifier, username, first name, last name, email address, phone number, alias, device identifier, application identifier, and/or the like. The purchase transfer database table 965 can store data relating to purchase transfer transactions, and can include data fields such as, but not limited to: merchant identifier, purchase unit identifier, purchase unit value, first buyer identifier, second buyer identifier, third buyer identifier, and/or the like. The merchant account database table 970 can store data relating to merchant accounts, and can include data fields such as, but not limited to: merchant identifier, name, address, store identifier, bank account number, bank name, routing number, and/or the like.
In some embodiments, at block 1005, a merchant application (e.g., merchant application 110) executing on a merchant system 105 receives an indication to split a bill from a merchant via a user interface of the merchant application 110. At block 1010, the merchant application 110 identifies or receives information identifying bill payers among whom the bill is to be split. In some embodiments, the merchant system 105 can connect to the client devices that are nearby and exchange information with those client devices to identify their users. The connection between the merchant system 105 and the client devices can be over a low energy wireless connection (e.g., BLE connection), over a local Wi-Fi network, over a network 106 using geo-fencing technology, and/or the like. Some or all of the nearby users can be selected as the bill payers. In some embodiments, the merchant can input information about the payers into the merchant application 110. At block 1015, the merchant application 110 receives assignment data that divides the bill among the bill payers such that each bill payer is assigned a portion of the bill. At block 1020, the merchant system 105 receives an instruction to send a split bill payment request, and in response, transmits the request to the payment service system 108 via the bill splitting API. The request can include, but is not limited to: information identifying the merchant and the bill payers, along with each bill payer's portion of the bill.
At block 1025, the payment service system 108 receives the split bill payment request. The payment service system 108 analyzes the request to identify the bill payers and each bill payer's share of the bill at block 1030. The payment service system 108 then transmits to each bill payer a request for payment of the bill payer's share of the bill at block 1035. At block 1040, the payment service system receives a response from each bill payer approving a specific amount for payment of the bill payer's share of the bill. In some embodiments, the specific amount approved by the bill payer can include an additional amount for tax, tips, and/or other surcharges, and can thus be greater than the bill payer's portion of the bill amount that was requested.
At block 1045, the payment service system 108 can initiate a transfer of the amount approved by each bill payer from a financial account associated with the bill payer to a financial account associated with the merchant. At block 1050, the payment service system 108 sends a confirmation of collection of the payment from the bill payers to the merchant system 105. The merchant system 105, at block 1055, receives the confirmation. In some embodiments, at block 1060, the merchant system 105 can generate and provide to each bill payer a digital or printed copy of the bill.
In some embodiments, the merchant system 105 receives an indication from a user to transfer a purchase unit purchased by the user to a receiver at block 1105. In response, at block 1110, the merchant system 105 transmits purchase unit information including information about at least one purchase unit to the payment service system 108. In some embodiments, the transmission of the purchase unit information can occur without receiving any indication from the user. For example, the transmission can be triggered upon submission of the purchase order. In some embodiments, the purchase unit information can be transmitted by the merchant system 105 using a purchase transfer API provided by the payment service system 108. At block 1115, the payment service system 108 receives the purchase unit information. At block 1120, the payment service system 108 identifies the user associated with the purchase transfer from the purchase unit information. At block 1125, the payment service system 108 transmits the purchase unit information to a payment application (e.g., payment application 120) executing on a mobile device of the identified user. The payment application can display the purchase unit information, which enables the user to assign or associate the purchase unit to a receiver selected from a list that can include contacts, and/or nearby users (e.g., users having mobile devices that are connected to the user's mobile device over a BLE connection). At block 1130, the payment service system 108 receives purchase unit assignment data that identifies purchased unit and the assigned receiver.
At block 1135, the payment service system 108 sends a transfer of the purchase unit to the receiver identified in the purchase unit assignment data. The receiver can either accept the transfer or decline the transfer. At block 1140, the payment service system 108 receives a response from the receiver accepting the transfer of the purchase unit. At block 1145, the payment service system 108 initiates a transfer of an amount corresponding to the monetary value of the purchase unit from a financial account associated with the receiver to a financial account associated with the user. At block 1150, the payment service system 108 transmits a notification or confirmation on transfer of the purchase unit from the user to the receiver. At block 1155, the merchant system 105 can receive the confirmation. At block 1160, the merchant system 105 can generate a receipt (e.g., a ticket stub) for the receiver and send the receipt to the receiver at block 1165.
In the illustrated embodiment, the processing system 1200 includes one or more processors 1210, memory 1211, a communication device 1212, and one or more input/output (I/O) devices 1213, all coupled to each other through an interconnect 1214. The interconnect 1214 may be or include one or more conductive traces, buses, point-to-point connections, controllers, adapters and/or other conventional connection devices.
The processor(s) 1210 may be or include, for example, one or more general-purpose programmable microprocessors, microcontrollers, application specific integrated circuits (ASICs), programmable gate arrays, or the like, or a combination of such devices. The processor(s) 1210 control the overall operation of the processing device 1200.
Memory 1211 may be or include one or more physical storage devices, which may be in the form of random access memory (RAM), read-only memory (ROM) (which may be erasable and programmable), flash memory, miniature hard disk drive, or other suitable type of storage device, or a combination of such devices. Memory 1211 may store data and instructions that configure the processor(s) 1210 to execute operations in accordance with the embodiments of the technology described above. For example, instructions corresponding to the components of the client device 102 illustrated in
The communication device 1212 may be or include, for example, an Ethernet adapter, cable modem, Wi-Fi adapter, cellular transceiver, Bluetooth radio/transceiver (e.g., Bluetooth 4.0 or BLE), or the like, or a combination thereof. Depending on the specific nature and purpose of the processing device 1200, the I/O devices 1213 can include devices such as a display (which may be a touch screen display), audio speaker, keyboard, mouse or other pointing device, microphone, camera, etc.
Unless contrary to physical possibility, it is envisioned that (i) the methods/steps described above may be performed in any sequence and/or in any combination, and that (ii) the components of respective embodiments may be combined in any manner.
The disclosed technology introduced above can be implemented by programmable circuitry programmed/configured by software and/or firmware, or entirely by special-purpose circuitry, or by a combination of such forms. Such special-purpose circuitry (if any) can be in the form of, for example, one or more application-specific integrated circuits (ASICs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), etc.
Software or firmware to implement the technology introduced here may be stored on a machine-readable storage medium and may be executed by one or more general-purpose or special-purpose programmable microprocessors. A “machine-readable medium”, as the term is used herein, includes any mechanism that can store information in a form accessible by a machine (a machine may be, for example, a computer, network device, cellular phone, personal digital assistant (PDA), manufacturing tool, any device with one or more processors, etc.). For example, a machine-accessible medium includes recordable/non-recordable media (e.g., read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; etc.).
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the disclosed technology. For example, the depicted flow charts may be altered in a variety of ways. The order of the steps may be rearranged, steps may be performed in parallel, steps may be omitted, or other steps may be included. As another example, the actual implementation of the database table may take a variety of forms, and the term “database table” is used herein in the generic sense to refer to any area that allows data to be stored in a structured and accessible fashion using such applications or constructs as databases, tables, linked lists, arrays, and so on. Similarly, any and all of the embodiments described above can be combined with each other, except to the extent that it may be stated otherwise above or to the extent that any such embodiments might be mutually exclusive in function and/or structure. Thus, it is intended that the embodiments of the disclosed technology cover the modifications and variations of the disclosed technology provided they come within the scope of the appended claims and their equivalents.
This application is a continuation under 35 U.S.C. § 120 of U.S. patent application Ser. No. 17/512,618, filed 27 Oct. 2021, which is a continuation-in-part under 35 U.S.C. § 120 of U.S. patent application Ser. No. 14/664,781, filed 20 Mar. 2015, each of which is incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5093787 | Simmons | Mar 1992 | A |
| 5687968 | Tarantino | Nov 1997 | A |
| 5878337 | Joao et al. | Mar 1999 | A |
| 5918216 | Miksovsky et al. | Jun 1999 | A |
| 6098051 | Lupien | Aug 2000 | A |
| 6260027 | Takahashi et al. | Jul 2001 | B1 |
| 6272474 | Garcia | Aug 2001 | B1 |
| 6278982 | Korhammer | Aug 2001 | B1 |
| 6356911 | Shibuya | Mar 2002 | B1 |
| 6398646 | Wei et al. | Jun 2002 | B1 |
| 6721715 | Nemzow | Apr 2004 | B2 |
| 7062361 | Lane | Jun 2006 | B1 |
| 7099850 | Mann, II et al. | Aug 2006 | B1 |
| 7130789 | Glodjo | Oct 2006 | B2 |
| 7182253 | Long | Feb 2007 | B1 |
| 7315840 | Keith | Jan 2008 | B1 |
| 7392213 | Merkoulovitch | Jun 2008 | B2 |
| 7644019 | Woda et al. | Jan 2010 | B2 |
| 7668766 | Goodwin, III et al. | Feb 2010 | B1 |
| 7693771 | Zimmerman et al. | Apr 2010 | B1 |
| 7693784 | Rivest et al. | Apr 2010 | B2 |
| 7792717 | Hankins et al. | Sep 2010 | B1 |
| 7822655 | LaQuinta | Oct 2010 | B1 |
| 7831494 | Sloan | Nov 2010 | B2 |
| 7865435 | Medina, III | Jan 2011 | B1 |
| 7958050 | Finch | Jun 2011 | B2 |
| 8073763 | Merrin | Dec 2011 | B1 |
| 8126794 | Lange | Feb 2012 | B2 |
| 8359260 | Merrin | Jan 2013 | B2 |
| 8417618 | Milne | Apr 2013 | B2 |
| 8452654 | Wooters et al. | May 2013 | B1 |
| 8583549 | Mohsenzadeh | Nov 2013 | B1 |
| 8606640 | Brody et al. | Dec 2013 | B2 |
| 8755943 | Wenzel | Jun 2014 | B2 |
| 8880540 | Sampson et al. | Nov 2014 | B1 |
| 8965791 | Bell et al. | Feb 2015 | B1 |
| 9665858 | Kumar | May 2017 | B1 |
| 9715689 | Ellis et al. | Jul 2017 | B1 |
| 9767467 | Gebb et al. | Sep 2017 | B2 |
| 9934494 | Nolte et al. | Apr 2018 | B1 |
| 9990621 | Ng et al. | Jun 2018 | B1 |
| 10127532 | Grassadonia | Nov 2018 | B1 |
| 10410194 | Grassadonia | Sep 2019 | B1 |
| 10686781 | kaditz et al. | Jun 2020 | B1 |
| 20010051902 | Messner | Dec 2001 | A1 |
| 20020010666 | Wright | Jan 2002 | A1 |
| 20020120568 | Leblang et al. | Aug 2002 | A1 |
| 20020120582 | Elston et al. | Aug 2002 | A1 |
| 20020147671 | Sloan | Oct 2002 | A1 |
| 20020147675 | Das | Oct 2002 | A1 |
| 20020194099 | Weiss | Dec 2002 | A1 |
| 20030182224 | Horrigan | Sep 2003 | A1 |
| 20040024692 | Turbeville | Feb 2004 | A1 |
| 20040122685 | Bunce | Jun 2004 | A1 |
| 20040248548 | Niwa et al. | Dec 2004 | A1 |
| 20050021447 | Lawrence | Jan 2005 | A1 |
| 20050080703 | Chiesa | Apr 2005 | A1 |
| 20050124408 | Vlazny | Jun 2005 | A1 |
| 20050250538 | Narasimhan et al. | Nov 2005 | A1 |
| 20060006226 | Fitzgerald et al. | Jan 2006 | A1 |
| 20060085321 | Staib | Apr 2006 | A1 |
| 20060173908 | Browning et al. | Aug 2006 | A1 |
| 20060178986 | Giordano et al. | Aug 2006 | A1 |
| 20060208065 | Mendelovich et al. | Sep 2006 | A1 |
| 20060293983 | Rosenblatt et al. | Dec 2006 | A1 |
| 20070106558 | Mitchell et al. | May 2007 | A1 |
| 20070198403 | Aloni et al. | Aug 2007 | A1 |
| 20070233615 | Tumminaro | Oct 2007 | A1 |
| 20070244811 | Tumminaro | Oct 2007 | A1 |
| 20070255564 | Yee et al. | Nov 2007 | A1 |
| 20070255652 | Tumminaro et al. | Nov 2007 | A1 |
| 20070255662 | Tumminaro | Nov 2007 | A1 |
| 20070267479 | Nix et al. | Nov 2007 | A1 |
| 20080015871 | Eder | Jan 2008 | A1 |
| 20080040261 | Nix et al. | Feb 2008 | A1 |
| 20080114699 | Yuan et al. | May 2008 | A1 |
| 20080215472 | Brown | Sep 2008 | A1 |
| 20090094123 | Killian et al. | Apr 2009 | A1 |
| 20090106140 | De La Motte | Apr 2009 | A1 |
| 20090157555 | Biffle et al. | Jun 2009 | A1 |
| 20090198528 | Kahn | Aug 2009 | A1 |
| 20090240626 | Hasson et al. | Sep 2009 | A1 |
| 20090307149 | Markov | Dec 2009 | A1 |
| 20090327123 | Wolfson | Dec 2009 | A1 |
| 20100010906 | Grecia | Jan 2010 | A1 |
| 20100088210 | Gardner | Apr 2010 | A1 |
| 20100121745 | Teckchandani et al. | May 2010 | A1 |
| 20100161457 | Katz et al. | Jun 2010 | A1 |
| 20100161484 | Leggatt et al. | Jun 2010 | A1 |
| 20100191570 | Michaud et al. | Jul 2010 | A1 |
| 20100205091 | Graziano et al. | Aug 2010 | A1 |
| 20100257081 | Ritchie | Oct 2010 | A1 |
| 20100306029 | Jolley | Dec 2010 | A1 |
| 20100306094 | Homer et al. | Dec 2010 | A1 |
| 20100306103 | Hankins et al. | Dec 2010 | A1 |
| 20110016536 | O'Brien et al. | Jan 2011 | A1 |
| 20110106668 | Korosec et al. | May 2011 | A1 |
| 20110119166 | Steinberg | May 2011 | A1 |
| 20110125652 | Sato | May 2011 | A1 |
| 20110145049 | Hertel et al. | Jun 2011 | A1 |
| 20110191241 | Blain et al. | Aug 2011 | A1 |
| 20110201306 | Ali Al-Harbi | Aug 2011 | A1 |
| 20110238473 | Sankolli et al. | Sep 2011 | A1 |
| 20110246306 | Blackhurst et al. | Oct 2011 | A1 |
| 20110251910 | Dimmick | Oct 2011 | A1 |
| 20110276418 | Velani | Nov 2011 | A1 |
| 20110288922 | Thomas et al. | Nov 2011 | A1 |
| 20110313871 | Greenwood | Dec 2011 | A1 |
| 20120016799 | Killian et al. | Jan 2012 | A1 |
| 20120041875 | Sorbe et al. | Feb 2012 | A1 |
| 20120078784 | Anthony et al. | Mar 2012 | A1 |
| 20120130903 | Dorsey et al. | May 2012 | A1 |
| 20120143761 | Doran et al. | Jun 2012 | A1 |
| 20120158443 | Kim | Jun 2012 | A1 |
| 20120166332 | Naaman | Jun 2012 | A1 |
| 20120191607 | Lord et al. | Jul 2012 | A1 |
| 20120226545 | Gebb et al. | Sep 2012 | A1 |
| 20120239453 | Osogami | Sep 2012 | A1 |
| 20120239483 | Yankovich et al. | Sep 2012 | A1 |
| 20120253906 | Lapica | Oct 2012 | A1 |
| 20120271712 | Katzin et al. | Oct 2012 | A1 |
| 20120323753 | Norman | Dec 2012 | A1 |
| 20130024289 | Cueli et al. | Jan 2013 | A1 |
| 20130030934 | Bakshi et al. | Jan 2013 | A1 |
| 20130080351 | Schneider | Mar 2013 | A1 |
| 20130132274 | Henderson et al. | May 2013 | A1 |
| 20130179346 | Kumnick et al. | Jul 2013 | A1 |
| 20130185187 | Vasinkevich | Jul 2013 | A1 |
| 20130275334 | Andersen | Oct 2013 | A1 |
| 20130304576 | Berland et al. | Nov 2013 | A1 |
| 20130317893 | Nelson et al. | Nov 2013 | A1 |
| 20140012689 | Henderson et al. | Jan 2014 | A1 |
| 20140012701 | Wall et al. | Jan 2014 | A1 |
| 20140012743 | Hanson et al. | Jan 2014 | A1 |
| 20140095385 | Ainslie et al. | Apr 2014 | A1 |
| 20140100931 | Sanchez et al. | Apr 2014 | A1 |
| 20140156517 | Argue | Jun 2014 | A1 |
| 20140164082 | Sun et al. | Jun 2014 | A1 |
| 20140201110 | Sato | Jul 2014 | A1 |
| 20140249999 | Johnson et al. | Sep 2014 | A1 |
| 20140279098 | Ham | Sep 2014 | A1 |
| 20140297533 | Mittal | Oct 2014 | A1 |
| 20140351118 | Zhao | Nov 2014 | A1 |
| 20140358769 | Howe et al. | Dec 2014 | A1 |
| 20140365304 | Showers et al. | Dec 2014 | A1 |
| 20150012388 | Kim et al. | Jan 2015 | A1 |
| 20150046271 | Scholl et al. | Feb 2015 | A1 |
| 20150058261 | Parikh | Feb 2015 | A1 |
| 20150081534 | Zamer | Mar 2015 | A1 |
| 20150100442 | Van Heerden et al. | Apr 2015 | A1 |
| 20150100443 | Van Heerden et al. | Apr 2015 | A1 |
| 20150112870 | Nagasundaram et al. | Apr 2015 | A1 |
| 20150127392 | Shivakumar et al. | May 2015 | A1 |
| 20150161741 | Unser et al. | Jun 2015 | A1 |
| 20150170132 | Patel | Jun 2015 | A1 |
| 20150186863 | Schwalb et al. | Jul 2015 | A1 |
| 20150186871 | Laracey | Jul 2015 | A1 |
| 20150220914 | Purves et al. | Aug 2015 | A1 |
| 20150220924 | Bakker | Aug 2015 | A1 |
| 20150287006 | Hunter et al. | Oct 2015 | A1 |
| 20150287021 | Itwaru | Oct 2015 | A1 |
| 20150287067 | Robeen | Oct 2015 | A1 |
| 20150294339 | Vargas et al. | Oct 2015 | A1 |
| 20150310461 | Lee | Oct 2015 | A1 |
| 20150348003 | Reader | Dec 2015 | A1 |
| 20150363866 | Depew | Dec 2015 | A1 |
| 20160012428 | Haldenby et al. | Jan 2016 | A1 |
| 20160034906 | Stopic et al. | Feb 2016 | A1 |
| 20160055474 | Syed | Feb 2016 | A1 |
| 20160104237 | Kanjlia et al. | Apr 2016 | A1 |
| 20160117784 | Hwang | Apr 2016 | A1 |
| 20160117910 | Rajala | Apr 2016 | A1 |
| 20160148164 | Luk | May 2016 | A1 |
| 20160196521 | Wada | Jul 2016 | A1 |
| 20160224972 | Li | Aug 2016 | A1 |
| 20160364724 | Wang et al. | Dec 2016 | A1 |
| 20170161698 | Caldwell | Jun 2017 | A1 |
| 20180074523 | Cantrell | Mar 2018 | A1 |
| 20180285970 | Snow | Oct 2018 | A1 |
| 20190132350 | Smith | May 2019 | A1 |
| 20190311443 | Blades | Oct 2019 | A1 |
| 20190340689 | Gordon, III | Nov 2019 | A1 |
| 20200097934 | Brian | Mar 2020 | A1 |
| 20200118068 | Turetsky | Apr 2020 | A1 |
| 20200151709 | Bryan | May 2020 | A1 |
| 20200193752 | Burris | Jun 2020 | A1 |
| 20200302468 | Karuppan | Sep 2020 | A1 |
| 20210142302 | Anderson | May 2021 | A1 |
| 20220051222 | Ng et al. | Feb 2022 | A1 |
| 20220215363 | Grassadonia | Jul 2022 | A1 |
| 20220261925 | Kurczodyna | Aug 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 2005-182338 | Jul 2005 | JP |
| 10-2008-0053056 | Jun 2008 | KR |
| 2011153281 | Dec 2011 | WO |
| Entry |
|---|
| “Billr: Bill Splitting at the Table,” Billr, iTunes Preview, Retrieved from the internet URL: https://itunes.apple.com/us/app/billr-bill-splitting-attable/id501889312?Is=I&mt=8, on Nov. 4, 2014, pp. 1-2. |
| “Divvy on the App Store on iTunes,” iTunes, Helix Interactive, Retrieved from the internet URL: https://itunes.apple.com/us/app/divvy/id560503890?1s= 1 &mt=8, on Nov. 4, 2014, pp. 1-2. |
| “Sharing bills & expenses?,” WeSplit.It., Retrieved from the internet URL : https://wesplit.it/, on Nov. 4, 2014, pp. 1-2. |
| “Split bills, share rent & expenses for your sharehouse or holiday, The best way to split bills,” dapShare, Retrieved from the internet: URL<http://dapshare.com/, on Nov. 4, 2014, pp. 1-2. |
| “Split expenses with friends,” Splitwise, Retrieved from the internet URL: https://www.splitwise.com/, on Nov. 4, 2014, pp. 1-2. |
| “Splitabill,” Funkbit AS, iTunes Preview, dated Oct. 15, 2012, Retrieved from the internet URL: https://itunes.apple.com/us/app/splitabill/id485048203, on Nov. 4, 2014, pp. 1-2. |
| “splitabill.com: Take a tour,” Splitabill, Retrieved from the internet URL: https://splitabill.com/tour/, on Nov. 4, 2014, pp. 1-2. |
| “Splitwise,” Google Play, dated Oct. 15, 2014, Retrieved from the internet URL: ttps://play.google.com/store/aoos/details?id=com.Splitwise.SplitwiseMobile, on Nov. 4, 2014, pp. 1-2. |
| “The quickest way to split a bill and calculate the tip at restaurants and bars,” Billr.me, Retrieved from the Internet URL: http://billr.me/, on Oct. 29, 2015, pp. 1-4. |
| “What is Divvy?,” Divvy That Up, dated Sep. 17, 2013, Retrieved from the internet URL: http://www.divvythatup.com/, on Nov. 4, 2014, pp. 1-5. |
| Dodd, A., “dapShare Mobile—Andriod Apps on Google Play,” dated Nov. 23, 2011, Retrieved from the internet URL: https://play.google.com/store/apps/details?id=com.dapshare&h1=en, on Nov. 4, 2014, pp. 1-2. |
| Goode, L., “Paying With Square's New Mobile-Payments App,” All Things D, dated Apr. 30, 2012, Retrieved from the Internet URL: http://allthingsd.com/20120430/paying-with-squares-new-mobile-payments-app/, on Nov. 7, 2014, pp. 1-3. |
| “Adyen Announces European Availability of Chip & PIN Mobile Point-of-Sale Solution,” Business Wire, dated Dec. 3, 2012, Retrieved from the Internet URL: https://www.businesswire.com/news/home/20121203005476/en/Adyen-Announces-European-Availability-Chip-PIN-Mobile, pp. 1-4. |
| “MeDeploy Launches a New Approach to Digital Pay-Media Distribution at DEMOfall 08,” Science Letter, published Sep. 23, 2008, pp. 1-2. |
| Number | Date | Country | |
|---|---|---|---|
| 20230237462 A1 | Jul 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17512618 | Oct 2021 | US |
| Child | 18190020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14664781 | Mar 2015 | US |
| Child | 17512618 | US |
