Facilitating sending, receiving, and updating of payments using message and payment queues

Patent metadata

Field	Value
Publication number	US-10467602-B2
Application number	US-201514645006-A
Country	US
Kind code	B2
Filing date	Mar 11, 2015
Priority date	Mar 11, 2015
Publication date	Nov 5, 2019
Grant date	Nov 5, 2019

Abstract

The present disclosure relates to systems, methods, and devices for sending and receiving payments using an integrated payment and messaging system. In particular, the integrated payment and messaging system allows users to send and receive electronic payments as well as exchange messages. For example, one or more implementations involve facilitating message exchanges and payment transactions using push notifications via separate message and payment queues. To illustrate, one or more implementations involve pushing status updates to a payment transaction using a payment queue specific to a user. Additionally, one or more implementations involve associating payment transactions with messages within a messaging thread for providing updates to each user in the messaging thread.

First claim

What is claimed is:

1. A method comprising:
receiving, at one or more servers from a first client device associated with a user, a request from the user to send a payment to a co-user as part of a payment transaction, the request including a payment amount;
sending, by the one or more servers to a payment network, a charge request against a payment credential of the user for the payment amount of the payment request;
receiving, at the one or more servers from the payment network, a successful charge response indicating that the charge request was successful;
pushing, by the one or more servers in response to the successful charge response via one or more payment queues, a payment initiation message to the first client device associated with the user and a second client device associated with the co-user, the one or more payment queues comprising communications media at the one or more servers that temporarily store data sent to, and received from, the user and the co-user and in communication with a first group of servers of the one or more servers, the first group of servers processing payment transaction information with the payment network;
sending, by the one or more servers to the second client device via one or more message queues in parallel with the payment initiation message to the second client device via a second payment queue of the one or more payment queues, a message indicating the payment for entry into a messaging thread between the users at the second client device, the one or more message queues comprising communications media at the one or more servers that temporarily store data sent to, and received from, the user and the co-user and in communication with a second group of servers of the one or more servers separate from the first group of servers, the second group of servers comprising a message database maintaining an archive of messaging threads involving the user and the co-user;
writing, by the second group of servers to the message database, the message indicating the payment at the same time as, or after, sending the message to the second client device via a recipient message queue of the one or more message queues;
receiving, at the one or more servers, a status update for the payment transaction; and
pushing, by the one or more servers, the status update for the payment transaction to the first client device and the second client device via the one or more payment queues.

2. The method as recited in claim 1 , further comprising:
generating a transaction identifier for the payment transaction; and
associating the transaction identifier with the message indicating the payment.

3. The method as recited in claim 2 , wherein receiving the status update for the payment transaction comprises:
identifying the transaction identifier in connection with the status update; and
determining, based on the transaction identifier, that the status update is associated with the payment transaction.

4. The method as recited in claim 2 , wherein associating the transaction identifier with the message indicating the payment comprises:
generating a message identifier for the message; and
mapping the message identifier to the transaction identifier.

5. The method as recited in claim 1 , wherein the payment initiation message comprises the payment amount, a sender ID, a sequence ID, transaction ID, a status identifier, and a recipient ID; and
the message indicating the payment comprises a link to the payment amount in the payment initiation message such that the message indicating the payment displays the payment amount from the payment initiation message.

6. The method as recited in claim 5 , further comprising, in response to the receipt of the status update for the payment transaction, incrementing the sequence ID of the payment initiation message; and
determining which client devices to push message status update for the payment transaction based on a current sequence ID of the client devices.

7. The method as recited in claim 1 , wherein pushing, by the one or more servers, the status update for the payment transaction consists of sending any changes to the payment initiation message based on the received status update for the payment transaction.

8. The method as recited in claim 1 , wherein the status update comprises a transaction completion update.

9. The method as recited in claim 1 , further comprising:
obtaining, from the second client device, a sequence ID indicating a most recent update received by the second client device via the second payment queue of the one or more payment queues;
determining that the sequence ID obtained from the second client device does not match a sequence ID maintained in the second payment queue indicating a most recent update sent to the second client device; and
pushing changes corresponding to sequence IDs after the sequence ID obtained from the second client device and up to the sequence ID maintained in the second payment queue.

10. A system comprising:
at least one server; and
at least one non-transitory computer readable storage medium storing instructions thereon, that, when executed by the at least one server, cause the system to:
receive, from a first client device associated with a user, a request from the user to send a payment to a co-user as part of a payment transaction, the request including a payment amount;
send, to a payment network, a charge request against a payment credential of the user for the payment amount of the payment request;
receive, from the payment network, a successful charge response indicating that the charge request was successful;
push, in response to the successful charge response via one or more payment queues, a payment initiation message to the first client device associated with the user and a second client device associated with the co-user, the one or more payment queues comprising communications media at one or more servers that temporarily store data sent to, and received from, the user and the co-user and in communication with a first group of servers of the one or more servers, the first group of servers processing payment transaction information with the payment network;
send, to the second client device via one or more message queues in parallel with the payment initiation message to the second client device via a second payment queue of the one or more payment queues, a message indicating the payment for entry into a messaging thread between the users at the second client device, the one or more message queues comprising communications media at the one or more servers that temporarily store data sent to, and received from, the user and the co-user and in communication with a second group of servers of the one or more servers separate from the first group of servers, the second group of servers comprising a message database maintaining an archive of messaging threads involving the user and the co-user;
write, by the second group of servers to the message database, the message indicating the payment at the same time as, or after, sending the message to the second client device via a recipient message queue of the one or more message queues;
receive a status update for the payment transaction; and
push the status update for the payment transaction to the first client device and the second client device via the one or more payment queues.

11. The system as recited in claim 10 , further comprising instructions that, when executed by the at least one server, cause the system to:
generating a transaction identifier for the payment transaction; and
associating the transaction identifier with the message indicating the payment.

12. The system as reci

Assignees

• Facebook Inc

Inventors

• Davis Stephen Moore
• Yu Xunjie
• Sarnoff Aaron Alexander
• Fein Jeremy David

Classifications

• G06Q20/4016

  involving fraud or risk level assessment in transaction processing · CPC title

• G06Q20/10 Primary

  specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems · CPC title

• G06Q20/223

  based on the use of peer-to-peer networks · CPC title

• H04L51/046

  Interoperability with other network applications or services · CPC title

• G06Q20/405

  Establishing or using transaction specific rules · CPC title