Tracking repayment status across multiple payment systems

Abstract

A system and a method for tracking repayment status of a transaction split 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. A user interface is displayed provides a repayment status for the fund request transmitted for the identifier.

Therefore, the following is claimed: 
     
         1 . A system, comprising:
 a first computing device comprising a processor, and a memory; and   machine-readable instructions stored in the memory that, when executed by the processor, cause the first computing device to at least:
 display a first user interface that includes a notification of a transaction that has occurred with a merchant, the first user interface comprising a user interface element associated with the transaction for initiating a split of the transaction; 
 display a second user interface that includes a list of contacts retrieved from the memory in response to a selection of the user interface element for initiating the split of the transaction; 
 identify a selection of a peer-to-peer system for a selected contact of the transaction from the second user interface; 
 transmit a funds request that includes an identifier for the selected contact at the peer-to-peer system and a requested amount of the transaction to a second computing device; and 
 display a third user interface that provides a repayment status for the funds request transmitted for the identifier for the selected contact based at least in part on a status request in an instance in which the funds request has been transmitted to the peer-to-peer system. 
   
     
     
         2 . The system of  claim 1 , wherein the repayment status comprises at least one of: a payment requested, a peer-to-peer system approval, or a payment received. 
     
     
         3 . The system of  claim 1 , wherein the selected contact is a first selected contact, and the repayment status comprises a first payment status for the first selected contact for the transaction and a second payment status for a second selected contact for the transaction. 
     
     
         4 . 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:
 determine the requested amount for the funds request for the selected contact based at least in part on a quantity of selected contacts for the funds request.   
     
     
         5 . The system of  claim 1 , wherein the machine-readable instructions, when executed by the processor, cause the first computing device to at least:
 dynamically relocate text information in the first user interface to the second user interface to create a viewable area for the list of contacts in the second user interface.   
     
     
         6 . The system of  claim 1 , wherein the identifier of the requestee is a peer-to-peer payment system username and providing the peer-to-peer payment system username and the requested amount of the transaction to the second computing device causes the second computing device to initiate a funds request to the requestee using the peer-to-peer payment system username. 
     
     
         7 . The system of  claim 1 , wherein the repayment status for the funds request is displayed in the third user interface in response to a selection of the transaction from the third user interface. 
     
     
         8 . A method, comprising
 displaying, by a client device, a first user interface that includes a notification of a transaction that has occurred with a merchant, the first user interface comprising a user interface element associated with the transaction for initiating a split of the transaction;   displaying by the client device, a second user interface that includes a list of contacts retrieved from a memory in response to a selection of the user interface element for initiating the split of the transaction;   identifying, by the client device, a selection of a peer-to-peer system for a selected contact of the transaction from the second user interface;   transmitting, by the client device, a funds request that includes an identifier for the selected contact at the peer-to-peer system and a requested amount of the transaction to a second computing device; and   displaying, by the client device, a third user interface that provides a repayment status for the funds request transmitted for the identifier for the selected contact based at least in part on a status request in an instance in which the funds request has been transmitted to the peer-to-peer system.   
     
     
         9 . The method of  claim 8 , wherein the first user interface is automatically displayed in response to receiving the notification from the second computing device. 
     
     
         10 . The method of  claim 8 , wherein the repayment status comprises at least one of: a payment requested, a peer-to-peer system approval, or a payment received. 
     
     
         11 . The method of  claim 8 , further comprising:
 determining, by the client device, the requested amount for the funds request for the selected contact based at least in part on a quantity of selected contacts for the funds request.   
     
     
         12 . The method of  claim 8 , wherein the selected contact is a first selected contact, and the repayment status comprises a first payment status for the first selected contact for the transaction and a second payment status for a second selected contact for the transaction. 
     
     
         13 . The method of  claim 8 , further comprising:
 relocating, by the client device, text information in the first user interface to the second user interface to create a viewable area for the list of contacts in the second user interface.   
     
     
         14 . The method of  claim 8 , wherein the identifier of the requestee is a peer-to-peer payment system username and providing the peer-to-peer payment system username and the requested amount of the transaction to the second computing device causes the second computing device to initiate a funds request to the requestee using the peer-to-peer payment system username. 
     
     
         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:
 display a first user interface that includes a notification of a transaction that has occurred with a merchant, the first user interface comprising a user interface element associated with the transaction for initiating a split of the transaction;   display a second user interface that includes a list of contacts retrieved from a memory of the first computing device in response to a selection of the user interface element for initiating the split of the transaction;   identify a selection of a peer-to-peer system for a selected contact of the transaction from the second user interface;   transmit a funds request that includes an identifier for the selected contact at the peer-to-peer system and a requested amount of the transaction to a second computing device; and   display a third user interface that provides a repayment status for the funds request transmitted for the identifier for the selected contact based at least in part on a status request in an instance in which the funds request has been transmitted to the peer-to-peer system.   
     
     
         16 . The non-transitory, computer-readable medium of  claim 15 , wherein the first user interface is automatically displayed in response to receiving the notification from the second computing device. 
     
     
         17 . The non-transitory, computer-readable medium of  claim 15 , wherein the repayment status comprises at least one of: a payment requested, a peer-to-peer system approval, or a payment received. 
     
     
         18 . 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 at least:
 determine the requested amount for the funds request for the selected contact based at least in part on a quantity of selected contacts for the funds request.   
     
     
         19 . The non-transitory, computer-readable medium of  claim 15 , wherein the selected contact is a first selected contact, and the repayment status comprises a first payment status for the first selected contact for the transaction and a second payment status for a second selected contact for the transaction. 
     
     
         20 . 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 at least:
 relocate text information in the first user interface to the second user interface to create a viewable area for the list of contacts in the second user interface.