Sending and receiving payments using a message system

Abstract

The present disclosure relates to systems, methods, and devices that provide a transactional payment system. In particular, the transactional payment system allows users of a messaging system to send and receive electronic payments to and from other users of the messaging system. A messaging application on a client device can receive payment information input (such as a payment amount and payment method) from a sender for making a payment to a recipient. The messaging application can send a payment message including the payment information to a messaging system, and the messaging system coordinates a payment process based on the payment information. During the payment process, the messaging system can provide status updates to the sender and receiver of the payment via status messages that are included in a message thread corresponding to the sender and the recipient.

1 - 20 . (canceled) 
     
     
         21 . A method comprising:
 receiving, at a message system comprising at least one server device, a payment message from a first client device associated with a sender, the payment message defining a payment from the sender to a recipient;   providing, by the message system to a second client device associated with the recipient, a recipient status message for display within a message thread on the second client device, the recipient status message comprising information corresponding to the payment;   providing, by the message system to the first client device, a sender status message for display within a message thread on the first client device, the sender status message comprising sender transaction information comprising a payment amount portion;   initiating, utilizing a transaction identifier associated with the payment, a transaction to process the payment by sending a payment authorization request to a payment network;   receiving, from the payment network, an indication that a payment authorization for the transaction failed; and   in response to receiving the indication that the payment authorization for the transaction failed:
 sending a first status update to the first client device associated with the sender, the first status update causing an update to the sender status message within the message thread on the first client device to indicate that the payment authorization for the transaction failed; and 
 sending a second status update to the second client device associated with the sender, the second status update causing an update to the recipient status message within the message thread on the second client device to indicate that the transaction was canceled. 
   
     
     
         22 . The method of  claim 21 , wherein sending the first status update to the first client device associated with the sender comprises sending a description of a reason that the payment authorization for the transaction failed for display within the message thread. 
     
     
         23 . The method of  claim 22 , wherein sending the second status update to the second client device associated with the recipient comprises excluding, from the recipient status message, the reason that the payment authorization for the transaction failed. 
     
     
         24 . The method of  claim 21 , wherein receiving the indication that the payment authorization for the transaction failed comprises receiving an indication that the payment authorization for the transaction failed due to insufficient funds in a payment account associated with the sender. 
     
     
         25 . The method of  claim 21 , further comprising providing, within the second status update, an option to correct a reason that the payment authorization for the transaction failed. 
     
     
         26 . The method of  claim 21 , further comprising identifying, within the payment message, payment information that defines the payment from the sender to the recipient, the payment information comprising a sender identifier, a recipient identifier, and a payment amount. 
     
     
         27 . The method of  claim 26 , further comprising:
 generating the transaction identifier associated with the payment;   associating the transaction identifier with the payment information; and   providing the transaction identifier within the sender status message and the recipient status message.   
     
     
         28 . A non-transitory computer readable medium comprising instructions that, when executed by at least one processor, cause a computer device to:
 receive, at a message system comprising at least one server device, a payment message from a first client device associated with a sender, the payment message defining a payment from the sender to a recipient;   provide, by the message system to a second client device associated with the recipient, a recipient status message for display within a message thread on the second client device, the recipient status message comprising information corresponding to the payment;   provide, by the message system to the first client device, a sender status message for display within a message thread on the first client device, the sender status message comprising sender transaction information comprising a payment amount portion;   initiate, utilizing a transaction identifier associated with the payment, a transaction to process the payment by sending a payment authorization request to a payment network;   receive, from the payment network, an indication that a payment authorization for the transaction failed; and   in response to receiving the indication that the payment authorization for the transaction failed:
 send a first status update to the first client device associated with the sender, the first status update causing an update to the sender status message within the message thread on the first client device to indicate that the payment authorization for the transaction failed; and 
 send a second status update to the second client device associated with the sender, the second status update causing an update to the recipient status message within the message thread on the second client device to indicate that the transaction was canceled. 
   
     
     
         29 . The non-transitory computer readable medium of  claim 28 , further comprising instructions that, when executed by the at least one processor, cause the computer device to send the first status update to the first client device associated with the sender by sending a description of a reason that the payment authorization for the transaction failed for display within the message thread. 
     
     
         30 . The non-transitory computer readable medium of  claim 29 , further comprising instructions that, when executed by the at least one processor, cause the computer device to send the second status update to the second client device associated with the recipient by excluding, from the recipient status message, the reason that the payment authorization for the transaction failed. 
     
     
         31 . The non-transitory computer readable medium of  claim 28 , further comprising instructions that, when executed by the at least one processor, cause the computer device to receive the indication that the payment authorization failed by receiving an indication that the payment authorization for the transaction failed due to insufficient funds in a payment account associated with the sender. 
     
     
         32 . The non-transitory computer readable medium of  claim 28 , further comprising instructions that, when executed by the at least one processor, cause the computer device to provide, within the second status update, an option to correct a reason that the payment authorization for the transaction failed. 
     
     
         33 . The non-transitory computer readable medium of  claim 28 , further comprising instructions that, when executed by the at least one processor, cause the computer device to identify, within the payment message, payment information that defines the payment from the sender to the recipient, the payment information comprising a sender identifier, a recipient identifier, and a payment amount. 
     
     
         34 . The non-transitory computer readable medium of  claim 33 , further comprising instructions that, when executed by the at least one processor, cause the computer device to:
 generate the transaction identifier associated with the payment;   associate the transaction identifier with the payment information; and   provide the transaction identifier within the sender status message and the recipient status message.   
     
     
         35 . A system comprising:
 at least one processor; and   a non-transitory computer readable medium comprising instructions that, when executed by the at least one processor, cause the system to:
 receive, at a message system comprising at least one server device, a payment message from a first client device associated with a sender, the payment message defining a payment from the sender to a recipient; 
 provide, by the message system to a second client device associated with the recipient, a recipient status message for display within a message thread on the second client device, the recipient status message comprising information corresponding to the payment; 
 provide, by the message system to the first client device, a sender status message for display within a message thread on the first client device, the sender status message comprising sender transaction information comprising a payment amount portion; 
 initiate, utilizing a transaction identifier associated with the payment, a transaction to process the payment by sending a payment authorization request to a payment network; 
 receive, from the payment network, an indication that a payment authorization for the transaction failed; and 
 in response to receiving the indication that the payment authorization for the transaction failed:
 send a first status update to the first client device associated with the sender, the first status update causing an update to the sender status message within the message thread on the first client device to indicate that the payment authorization for the transaction failed; and 
 send a second status update to the second client device associated with the sender, the second status update causing an update to the recipient status message within the message thread on the second client device to indicate that the transaction was canceled. 
 
   
     
     
         36 . The system of  claim 35 , further comprising instructions that, when executed by the at least one processor, cause the system to send the first status update to the first client device associated with the sender by sending a description of a reason that the payment authorization for the transaction failed for display within the message thread. 
     
     
         37 . The system of  claim 36 , further comprising instructions that, when executed by the at least one processor, cause the system to send the second status update to the second client device associated with the recipient by excluding, from the recipient status message, the reason that the payment authorization for the transaction failed. 
     
     
         38 . The system of  claim 35 , further comprising instructions that, when executed by the at least one processor, cause the system to receive the indication that the payment authorization failed by receiving an indication that the payment authorization for the transaction failed due to insufficient funds in a payment account associated with the sender. 
     
     
         39 . The system of  claim 35 , further comprising instructions that, when executed by the at least one processor, cause the system to provide, within the second status update, an option to correct a reason that the payment authorization for the transaction failed. 
     
     
         40 . The system of  claim 35 , further comprising instructions that, when executed by the at least one processor, cause the system to:
 identify, within the payment message, payment information that defines the payment from the sender to the recipient, the payment information comprising a sender identifier, a recipient identifier, and a payment amount;   generate the transaction identifier associated with the payment;   associate the transaction identifier with the payment information; and   provide the transaction identifier within the sender status message and the recipient status message.