Method and system for trusted notifications

Patent metadata

Field	Value
Publication number	US-11146539-B2
Application number	US-201816228238-A
Country	US
Kind code	B2
Filing date	Dec 20, 2018
Priority date	Dec 22, 2017
Publication date	Oct 12, 2021
Grant date	Oct 12, 2021

Abstract

A method for trusted notifications comprises: receiving, at a first host having at least one trusted server, a request message from a sender computing device, the request message comprising a request identifier and instructions to: update, at a second host, a recipient account associated with a recipient computing device, and to make a corresponding update at the first host to a sender account associated with the sender computing device. The method further comprises authorizing, at the first host, the request message; updating the sender account; generating a secure message at the at least one trusted server, the secure message comprising the request identifier and an indication from the at least one trusted server that the update completed; and sending the secure message from the first host to the sender computing device. The secure message can be received at the sender computer device and conveyed to the recipient computing device.

First claim

What is claimed is:

1. A method for trusted notifications, comprising the steps of:
receiving, at a first remote host having at least one trusted server, from a sender computing device that is remote from the first remote host, a request message, the request message comprising a request identifier and instructions to: update, at a second remote host, an account which is associated with a recipient computing device that is remote from the second remote host, and to make a corresponding update at the first remote host to an account associated with the sender computing device;
authorizing, at the first remote host, the request message;
updating, at the first remote host, the account associated with the sender computing device;
updating, at the second remote host, the account associated with the recipient computing device by forwarding the request message from the first remote host to the second remote host;
generating a secure message at the at least one trusted server of the first remote host, the secure message comprising the request identifier and an indication from the at least one trusted server of the first remote host that the update to the account associated with the sender computing device has been completed; and
sending the secure message from the first remote host to the sender computing device.

2. The method of claim 1 , wherein the request message is a request for payment from the sender computing device to the recipient computing device.

3. The method of claim 2 , further comprising acquiring payment details, to be included in the request for payment, at the sender computing device from the recipient computing device.

4. The method of claim 1 , wherein the secure message is digitally signed by the at least one trusted server.

5. The method of claim 1 , further comprising:
receiving the secure message at the sender computing device;
conveying the secure message from the sender computing device to the recipient computing device; and
validating the secure message at the recipient computing device to confirm completion of the update.

6. The method of claim 5 , wherein the secure message is digitally signed by the at least one trusted server.

7. The method of claim 6 , wherein the step of validating the secure message at the recipient computing device involves validating the digital signature of the secure message.

8. A computing system, comprising:
at least one processor; and
a storage medium; and
instructions stored on the storage system that executed by the at least one processor, cause the at least one processor to:
receive, at a first remote host having at least one trusted server, from a sender computing device that is remote from the first remote host, a request message, the request message comprising a request identifier and instructions to: update, at a second remote host, an account which is associated with a recipient computing device that is remote from the second remote host, and to make a corresponding update at the first remote host to an account associated with the sender computing device;
authorize, at the first remote host, the request message;
update, at the first remote host, the account associated with the sender computing device;
update, at the second remote host, the account associated with the recipient computing device by forwarding the request message from the first remote host to the second remote host;
generate a secure message at the at least one trusted server of the first remote host, the secure message comprising the request identifier and an indication from the at least one trusted server of the first remote host that the update to the account associated with the sender computing device has been completed; and
send the secure message from the first remote host to the sender computing device.

9. The computing system of claim 8 , wherein the request message is a request for payment from the sender computing device to the recipient computing device.

10. The computing system of claim 9 , the instructions further causing the at least one processor to acquire payment details, to be included in the request for payment, at the sender computing device from the recipient computing device.

11. The computing system of claim 8 , wherein the secure message is digitally signed by the at least one trusted server.

12. The computing system of claim 8 , the instructions further causing the at least one processor to:
receive the secure message at the sender computing device;
convey the secure message from the sender computing device to the recipient computing device; and
validate the secure message at the recipient computing device to confirm completion of the update.

13. The computing system of claim 12 , wherein the secure message is digitally signed by the at least one trusted server.

14. The computing system of claim 13 , wherein the instructions to validate the secure message at the recipient computing device involves validating the digital signature of the secure message.

15. One or more non-transitory storage media having instructions stored thereon that when executed by a processing system, direct the processing system to at least:
receive, at a first remote host having at least one trusted server, from a sender computing device that is remote from the first remote host, a request message, the request message comprising a request identifier and instructions to: update, at a second remote host, an account which is associated with a recipient computing device that is remote from the second remote host, and to make a corresponding update at the first remote host to an account associated with the sender computing device;
authorize, at the first remote host, the request message;
update, at the first remote host, the account associated with the sender computing device;
update, at the second remote host, the account associated with the recipient computing device by forwarding the request message from the first remote host to the second remote host;
generate a secure message at the at least one trusted server of the first remote host, the secure message comprising the request identifier and an indication from the at least one trusted server of the first remote host that the update to the account associated with the sender computing device has been completed; and
send the secure message from the first remote host to the sender computing device.

16. The non-transitory media of claim 15 , wherein the request message is a request for payment from the sender computing device to the recipient computing device.

17. The non-transitory media of claim 16 , the instructions further directing the processing system to acquire payment details, to be included in the request for payment, at the sender computing device from the recipient computing device.

18. The non-transitory media of claim 15 , the instructions further directing the processing system to:
receive the secure message at the sender computing device;
convey the secure message from the sender computing device to the recipient computing device; and
validate the secure message at the recipient computing device to confirm completion of the update.

19. The non-transitory media of claim 18 , wherein the secure message is digitally signed by the at least one trusted server.

20. The non-transitory media of claim 19 , wherein the instructions to validate the secure message at the recipient computing device involves validating the digital signature of the secure message.

Assignees

• Mastercard International Inc

Inventors

• Garrett Duncan
• Beric John
• Ward Michael
• Roberts David Anthony

Classifications

• G06Q20/3255 Primary

  using mobile network messaging services for payment, e.g. SMS · CPC title

• G06Q20/3276

  using a pictured code, e.g. barcode or QR-code, being read by the M-device · CPC title

• G06Q20/42

  Confirmation, e.g. check or permission by the legal debtor of payment · CPC title

• G06Q20/3274

  using a pictured code, e.g. barcode or QR-code, being displayed on the M-device · CPC title

• G06Q20/3278

  RFID or NFC payments by means of M-devices · CPC title