Charge splitting across multiple payment systems

Abstract

A system and a method for splitting a transaction across multiple systems is disclosed. In some examples, a system is configured to receive a notification of a transaction that has occurred with a merchant for a transaction account. The system is configured to initiate a split of the transaction based at least in part on a selection of a user interface element and display a user interface for identifying a selection of a peer-to-peer system for a selected contact of the transaction. A funds request is transmitted and includes an identifier for the selected contact at the peer-to-peer system.

Therefore, the following is claimed: 
     
         1 . A system, comprising:
 a first computing device comprising a processor, a memory, and a display; and   machine-readable instructions stored in the memory that, when executed by the processor, cause the first computing device to at least:
 receive a notification of a charge for a transaction account that has occurred with a merchant; 
 display a first user interface that includes a list of transactions for the transaction account, the list of transactions comprising the charge; 
 initiate a split of the charge based at least in part on a selection of the charge from the list of transactions in the first user interface; 
 display a second user interface that includes a list of requestees from a plurality of contacts stored in the memory, the second user interface being configured to display an indicator for a peer-to-peer system to indicate a respective requestee has an account with the peer-to-peer system, wherein displaying the second user interface comprises relocating text information in the first user interface to create a viewable area for the list of requestees displayed in the second user interface; 
 determine a unique identifier of a requestee based at least in part on a selection of the indicator for the peer-to-peer system from the second user interface; and 
 transmit a funds request to a second computing device, wherein the funds request includes the unique identifier and a requested amount. 
   
     
     
         2 . The system of  claim 1 , wherein the notification is a push notification or a short message service (SMS) notification. 
     
     
         3 . The system of  claim 1 , wherein the machine-readable instructions stored in the memory that, when executed by the processor, cause the first computing device to at least:
 generate the list of requestees based at least in part on filtering the plurality of contacts using a contact attribute.   
     
     
         4 . The system of  claim 3 , wherein the contact attribute comprising at least one of a geographic location of a contact, a calendar entry of the contact, profile information for the contact, or social networking information for the contact. 
     
     
         5 . The system of  claim 1 , wherein the machine-readable instructions, when executed by the processor, cause the first computing device to at least:
 determine the requested amount for the funds request for the unique identifier based at least in part on a quantity of selected requestees for the funds request.   
     
     
         6 . The system of  claim 1 , wherein the unique identifier of the requestee is a peer-to-peer payment system username and transmitting the funds request to the second computing device causes the second computing device to initiate a payment request to the requestee using the peer-to-peer payment system username. 
     
     
         7 . The system of  claim 1 , wherein the unique identifier is a mobile phone number or an email address associated with the requestee to which the second computing device can send a payment request. 
     
     
         8 . A method, comprising:
 displaying, by a client device, a first user interface that includes a notification of a charge for a transaction that has occurred with a merchant, the first user interface includes a user interface element for initiating a split of the charge, the notification being received from a remote computing device;   generating, by the client device, a list of requestees from a plurality of contacts stored in a memory of the client device in response to a selection of the user interface element;   displaying, by the client device, a second user interface that includes the list of requestees, the second user interface being configured to display an indicator for a peer-to-peer system to indicate a respective requestee has an account with the peer-to-peer system, wherein displaying the second user interface comprises relocating text information in the first user interface to create a viewable area for the list of requestees displayed in the second user interface;   determining, by the client device, a unique identifier of a requestee based at least in part on a selection of the indicator for the peer-to-peer system from the second user interface; and   transmitting, by the client device, a funds request to the remote computing device, wherein the funds request includes the unique identifier and a requested amount.   
     
     
         9 . The method of  claim 8 , wherein the first user interface is automatically displayed in response to receiving the notification from the remote computing device. 
     
     
         10 . The method of  claim 8 , wherein the list of requestees is generated based at least in part on filtering the plurality of contacts using a contact attribute. 
     
     
         11 . The method of  claim 10 , wherein the contact attribute comprising at least one of a geographic location of a contact, a calendar entry of the contact, profile information for the contact, or social networking information for the contact. 
     
     
         12 . The method of  claim 8 , further comprising
 determining, by the client device, the requested amount for the funds request for the unique identifier based at least in part on a quantity of selected requestees for the funds request.   
     
     
         13 . The method of  claim 8 , wherein the unique identifier of the requestee is a peer-to-peer payment system username and transmitting the funds request to the remote computing device causes the remote computing device to initiate a payment request to the requestee using the peer-to-peer payment system username. 
     
     
         14 . The method of  claim 8 , wherein the unique identifier is a mobile phone number or an email address associated with the requestee to which the remote computing device can send a payment request. 
     
     
         15 . A non-transitory, computer-readable medium comprising machine-readable instructions that, when executed by a processor of a first computing device, cause the first computing device to at least:
 receive a notification of a charge for a transaction account that has occurred with a merchant, the notification of the charge being received from a remote computing device;   display a first user interface that includes the notification of the charge, the first user interface including a user interface element for initiating a split of the charge;   initiate the split of the charge based at least in part on a selection of the charge from a list of transactions in the first user interface;   generate a list of requestees from a plurality of contacts stored in a memory of the first computing device in response to the initiation of the split of the charge;   display a second user interface that includes the list of requestees, the second user interface being configured to display an indicator for a peer-to-peer system to indicate a respective requestee has an account with the peer-to-peer system;   determine a unique identifier of a requestee based at least in part on a selection of the indicator for the peer-to-peer system; and   transmit a funds request to a second computing device, wherein the funds request includes the unique identifier and a requested amount.   
     
     
         16 . The non-transitory, computer-readable medium of  claim 15 , wherein the first user interface is displayed automatically in response to receiving the notification of the charge from the remote computing device. 
     
     
         17 . The non-transitory, computer-readable medium of  claim 15 , wherein the machine-readable instructions cause the first computing device to at least:
 determine the requested amount for the funds request for the unique identifier based at least in part on a quantity of selected requestees for the funds request.   
     
     
         18 . The non-transitory, computer-readable medium of  claim 15 , the unique identifier of the requestee is a peer-to-peer payment system username and transmitting the funds request to the second computing device causes the second computing device to initiate a payment request to the requestee using the peer-to-peer payment system username. 
     
     
         19 . The non-transitory, computer-readable medium of  claim 15 , wherein the machine-readable instructions, when executed by the processor, cause the first computing device to least:
 generate the list of requestees based at least in part on filtering the plurality of contacts using a contact attribute.   
     
     
         20 . The non-transitory, computer-readable medium of  claim 19 , wherein the contact attribute comprising at least one of a geographic location of a contact, a calendar entry of the contact, profile information for the contact, or social networking information for the contact.