Systems and methods for multi-party cardless payment transactions

Abstract

A method of managing a multi-party cardless payment transaction includes receiving, at a service provider, a request for creating a data structure for tracking user expenses associated with an event; generating the data structure, wherein the data structure is stored in association with a database of the service provider; associating two or more user accounts with the data structure; receiving, via an application executing on at least one user device associated with a user account, expense data associated with the event; determining, for each user account, a portion of the expense data to be allocated to each user account; determining, based at least in part on the portion of the expense data to be allocated to each user account, an amount owed by each user; and causing at least one amount to be presented on the application to facilitate payment for at least the portion of the expense data.

What is claimed is: 
     
         1 . A computer-implemented method comprising:
 receiving, at a service provider, a request for creating a data structure for tracking individual user expenses associated with an event;   generating, by the service provider, the data structure, wherein the data structure is stored in association with a database of the service provider;   associating, by the service provider, two or more user accounts with the data structure;   receiving, at the service provider and via an application executing on at least one user device associated with a user account of the two or more user accounts, expense data associated with the event;   determining, by the service provider and for each user account of the two or more user accounts, a portion of the expense data to be allocated to each user account of the two or more user accounts;   determining, by the service provider and based at least in part on the portion of the expense data to be allocated to each user account of the two or more user accounts, an amount owed by each user associated with each user account of the two or more user accounts; and   causing at least one amount to be presented via a user interface of the application on the user device to facilitate payment for at least the portion of the expense data allocated to the user account.   
     
     
         2 . The computer-implemented method of  claim 1 , further comprising:
 presenting a list of cardless payment transactions on the user device for selection, each cardless payment transaction on the list being associated with a respective event, the list including a cardless payment transaction for the event, wherein:   the request for creating the data structure is associated with a selection of the cardless payment transaction from the list; and   the data structure is generated for the cardless payment transaction associated with the event.   
     
     
         3 . The computer-implemented method of  claim 2 , wherein the list is generated based on a relevancy metric associated with a user of the user device. 
     
     
         4 . The computer-implemented method of  claim 3 , wherein the relevancy metric is generated based on prior transactions associated with the user of the user device. 
     
     
         5 . The computer-implemented method of  claim 3 , wherein the relevancy metric includes a geo-location of the user device. 
     
     
         6 . The computer-implemented method of  claim 1 , further comprising:
 updating, in real-time, the portion of the expense data to be allocated to each user account upon receiving new expense data at the service provider, wherein the updating includes sending a push notification to each user device reflecting updated portion of the expense data allocated to each user account of the two or more user accounts.   
     
     
         7 . The computer-implemented method of  claim 1 , wherein the application is executed on each user device associated with the two or more user accounts, and a different subset of the expense data is received from each application executed on each user device. 
     
     
         8 . A system of a service provider comprising:
 one or more memories having computer-readable instructions stored therein; and   one or more processors configured to execute the computer-readable instructions to:   receive a request for creating a data structure for tracking individual user expenses associated with an event;   generate the data structure, wherein the data structure is stored in association with a database of the service provider;   associate at least one user account with the data structure;   receive, via an application executing on at least one user device associated with the at least one user account, expense data associated with the event;   determine, for each user account associated with the event, a portion of the expense data to be allocated to each user account;   determine, based at least in part on the portion of the expense data to be allocated to each user account, an amount owed by each user associated with each user account; and   cause at least one amount to be presented via a user interface of the application on the user device to facilitate payment for at least the portion of the expense data allocated to the user account.   
     
     
         9 . The system of  claim 8 , wherein the one or more processors are further configured to execute the computer-readable instructions to:
 present a list of cardless payment transactions on the user device for selection, each cardless payment transaction on the list being associated with a respective event, the list including a cardless payment transaction for the event, wherein:   the request for creating the data structure is associated with a selection of the cardless payment transaction from the list; and   the data structure is generated for the cardless payment transaction associated with the event.   
     
     
         10 . The system of  claim 9 , wherein the list is generated based on a relevancy metric associated with a user of the at least one user device. 
     
     
         11 . The system of  claim 10 , wherein the relevancy metric is generated based on prior transactions associated with the user of the at least one user device. 
     
     
         12 . The system of  claim 10 , wherein the relevancy metric includes a geo-location of the at least one user device. 
     
     
         13 . The system of  claim 8 , wherein the one or more processors are further configured to execute the computer-readable instructions to:
 update, in real-time, the portion of expense data to be allocated to each user account upon receiving new expense data at the service provider, wherein the updating includes sending a push notification to each user device reflecting updated portion of the expense data allocated to each user account.   
     
     
         14 . The system of  claim 8 , wherein the one or more processors are further configured to execute the computer-readable instructions to:
 send a push notification to at least one second user device for joining the event;   upon receiving an indication of acceptance from the second user device, associate the second user device with the data structure.   
     
     
         15 . One or more non-transitory computer-readable media comprising computer-readable instructions, which when executed by one or more processors of a service provider, cause the service provider to:
 receive a request for creating a data structure for tracking individual user expenses associated with an event;   generate the data structure, wherein the data structure is stored in association with a database of the service provider;   associate at least one user account with the data structure;   receive, via an application executing on at least one user device associated with the at least one user account, expense data associated with the event;   determine, for each user account associated with the event, a portion of the expense data to be allocated to each user account;   determine, based at least in part on the portion of the expense data to be allocated to each user account, an amount owed by each user associated with each user account; and   cause at least one amount to be presented via a user interface of the application on the user device to facilitate payment for at least the portion of the expense data allocated to the user account.   
     
     
         16 . The one or more non-transitory computer-readable media of  claim 15 , wherein the execution of the computer-readable instructions further cause the service provider to:
 present a list of cardless payment transactions on the user device for selection, each cardless payment transaction on the list being associated with a respective event, the list including a cardless payment transaction for the event, wherein:   the request for creating the data structure is associated with a selection of the cardless payment transaction from the list; and   the data structure is generated for the cardless payment transaction associated with the event.   
     
     
         17 . The one or more non-transitory computer-readable media of  claim 16 , wherein the list is generated based on a relevancy metric associated with a user of the at least one user device. 
     
     
         18 . The one or more non-transitory computer-readable media of  claim 17 , wherein the relevancy metric is generated based on prior transactions associated with the user of the at least one user device. 
     
     
         19 . The one or more non-transitory computer-readable media of  claim 17 , wherein the relevancy metric includes a geo-location of the at least one user device. 
     
     
         20 . The one or more non-transitory computer-readable media of  claim 15 , wherein the execution of the computer-readable instructions further cause the service provider to:
 update, in real-time, the portion of expense data to be allocated to each user account upon receiving new expense data at the service provider, wherein the updating includes sending a push notification to each user device reflecting updated portion of the expense data allocated to each user account.