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

Patent metadata

Field	Value
Publication number	US-2016267447-A1
Application number	US-201514645006-A
Country	US
Kind code	A1
Filing date	Mar 11, 2015
Priority date	Mar 11, 2015
Publication date	Sep 15, 2016
Grant date	—

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; sending, by the one or more servers to the second client device via one or more message queues, a message indicating the payment for entry into a messaging thread between the users at the second client device; 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 , wherein the status update comprises a transaction cancellation update.

10 . 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; receiving, at the one or more servers from the payment network, a successful charge response from the payment network for the payment amount; adding, by the one or more servers in response to the successful charge notification, a payment initiation message to a sender payment queue associated with the user; adding, by the one or more servers in response to the successful charge notification, a message indicating the payment to a sender message queue associated with the user, the message indicating the payment comprising a transaction identifier associated with the payment transaction; and updating, by the one or more servers, the client device of the user, a recipient payment queue, and a recipient message queue by:
pushing the payment initiation message from the sender payment queue to the client device and the recipient payment queue, and
pushing the message indicating the payment transaction from the sender message queue to the client device and the recipient message queue.

11 . The method as recited in claim 10 , wherein adding the message indicating the payment to the sender message queue comprises generating, in response to the successful charge notification, the transaction identifier for the payment transaction.

12 . The method as recited in claim 11 , further comprising:
generating a message identifier for the message comprising the transaction identifier; and mapping the transaction identifier to the message identifier.

13 . The method as recited in claim 10 , further comprising updating a client device of the co-user by pushing the payment initiation message from the recipient payment queue to the client device of the co-user, and pushing the message indicating the payment transaction from the recipient message queue to the client device of the co-user.

14 . The method as recited in claim 10 , further comprising:
receiving, from the payment network, a transaction completion response indicating that the payment network has successfully completed the payment transaction; and pushing, in response to the transaction completion response, a transaction completion status update for the payment transaction to the recipient payment queue in association with the transaction identifier.

15 . The method as recited in claim 14 , further comprising updating a sequence ID associated with the payment initiation message based on receipt of the transaction completion response.

16 . The method as recited in claim 15 , further comprising adding the payment initiation message to the sender payment queue and the message indicating the payment to the sender message queue in parallel.

17 . A device comprising:
at least one processor; and at least one non-transitory computer readable storage medium storing instructions thereon, that, when executed by the at least one processor, cause the device to:
receive, from a payment queue associated with the user, a response indicating that the one or more servers initiated a payment transaction between the user and a co-user;
receive, from a message queue associated with the user, a message indicating the payment transaction;
provide the message indicating the payment transaction within a messaging thread between the user and the co-user, wherein the message indicating the payment transaction comprises a payment amount associated with the payment transaction;
receive, from the sender payment queue, a status update for the payment transaction; and
update, based on the status update from the sender payment queue, the message indicating the payment transaction within the messaging thread.

18 . The device as recited in claim 17 , further comprising instructions that, when executed by the at least one processor, cause the device to:
receive a user selection of the message indicating the payment transaction; and display, within the mess

Assignees

• Facebook Inc

Inventors

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

Classifications

• G06Q20/405

  Establishing or using transaction specific rules · CPC title

• H04L51/046

  Interoperability with other network applications or services · CPC title

• G06Q20/10 Primary

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

• H04L51/08

  Annexed information, e.g. attachments · CPC title

• G06Q20/223

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