System and method for secure distribution of resource transfer request data

Patent metadata

Field	Value
Publication number	US-12177365-B2
Application number	US-202318482174-A
Country	US
Kind code	B2
Filing date	Oct 6, 2023
Priority date	Nov 20, 2020
Publication date	Dec 24, 2024
Grant date	Dec 24, 2024

Abstract

A computer-implemented method is disclosed. The method includes: receiving, via a client device, a resource transfer request for resources to be transferred to a transferee account; generating a secure data object based on request data of the resource transfer request, the secure data object including a first hash computed based on an input string comprising a transferee account identifier; signing the secure data object using a private key of a transferee resource account management system; and sending the signed secure data object to a messaging address associated with a transferor account.

First claim

The invention claimed is:

1. A computing system, comprising:
a processor; and
a memory coupled to the processor, the memory storing computer-executable instructions that, when executed by the processor, configure the processor to:
receive, via a client device, a resource transfer request for resources to be transferred to a transferee account;
generate a secure data object based on request data of the resource transfer request, the secure data object including a first hash computed based on a concatenated byte stream comprising resource transfer parameters;
sign the secure data object using a private key of a transferee resource account management system; and
send the signed secure data object to a messaging address associated with a transferor account.

2. The computing system of claim 1 , wherein the instructions, when executed, further configure the processor to:
validate the secure data object by:
verifying that a signature associated with the secure data object is valid using a public key corresponding to the private key of the transferee resource account management system; and
computing a second hash based on one or more resource transfer parameters included in the secure data object and comparing the second hash to the first hash to confirm that the one or more resource transfer parameters have not been modified after the signing.

3. The computing system of claim 2 , wherein validating the secure data object further comprises confirming that a unique identifier included in the secure data object has not been used previously.

4. The computing system of claim 3 , wherein confirming that the unique identifier has not been used previously comprises sending a request to the transferee resource account management system to confirm that no resource transfers to accounts at the transferee resource account management system have been processed using the unique identifier.

5. The computing system of claim 2 , wherein the instructions, when executed, further configure the processor to:
after verifying that the signature associated with the secure data object is valid, configure a transfer of the requested resources from the transferor account to the transferee account identified by the account information using a real-time resource transfer rail.

6. The computing system of claim 5 , wherein the secure data object indicates a quantity of resources associated with the resource transfer and wherein configuring the transfer comprises configuring a transfer of the quantity of resources identified in the secure data object.

7. The computing system of claim 5 , wherein the secure data object includes a unique identifier and wherein configuring the transfer comprises embedding the unique identifier in transfer data associated with the resource transfer.

8. The computing system of claim 5 , wherein the instructions, when executed, further configure the processor to provide, to a computing device associated with the transferor account, identification information for a transferee that is identified in the secure data object.

9. The computing system of claim 1 , wherein the secure data object includes a unique identifier and wherein the first hash is computed based, in part, on the unique identifier.

10. The computing system of claim 1 , wherein generating the secure data object comprises obtaining account information for the transferee account directly from the transferee resource account management system.

11. A computer-implemented method, comprising:
receiving, via a client device, a resource transfer request for resources to be transferred to a transferee account;
generating a secure data object based on request data of the resource transfer request, the secure data object including a first hash computed based on a concatenated byte stream comprising resource transfer parameters;
signing the secure data object using a private key of a transferee resource account management system; and
sending the signed secure data object to a messaging address associated with a transferor account.

12. The method of claim 11 , further comprising:
validating the secure data object by:
verifying that a signature associated with the secure data object is valid using a public key corresponding to the private key of the transferee resource account management system; and
computing a second hash based on one or more resource transfer parameters included in the secure data object and comparing the second hash to the first hash to confirm that the one or more resource transfer parameters have not been modified after the signing.

13. The method of claim 12 , wherein validating the secure data object further comprises confirming that a unique identifier included in the secure data object has not been used previously.

14. The method of claim 13 , wherein confirming that the unique identifier has not been used previously comprises sending a request to the transferee resource account management system to confirm that no resource transfers to accounts at the transferee resource account management system have been processed using the unique identifier.

15. The method of claim 12 , further comprising:
after verifying that the signature associated with the secure data object is valid, configure a transfer of the requested resources from the transferor account to the transferee account identified by the account information using a real-time resource transfer rail.

16. The method of claim 15 , wherein the secure data object indicates a quantity of resources associated with the resource transfer and wherein configuring the transfer comprises configuring a transfer of the quantity of resources identified in the secure data object.

17. The method of claim 15 , wherein the secure data object includes a unique identifier and wherein configuring the transfer comprises embedding the unique identifier in transfer data associated with the resource transfer.

18. The method of claim 11 , wherein the secure data object includes a unique identifier and wherein the first hash is computed based, in part, on the unique identifier.

19. The method of claim 11 , wherein generating the secure data object comprises obtaining the account information for the transferee account directly from the transferee resource account management system.

20. A computer-implemented method, comprising:
at a first resource account management system:
generating a secure data object based on request data of a resource transfer request for resources to be transferred to a transferee account at the first resource account management system, the secure data object indicating including a first hash computed based on an input string comprising a transferee account identifier;
signing the secure data object using a private key of the first resource account management system; and
sending the secure data object to a messaging address associated with a transferor account;

at a second resource account management system:
validating the secure data object by:
verifying that a signature associated with the secure data object is valid using a public key corresponding to the private key of the first resource account management system; and
computing a second hash based on one or more resource transfer parameters included in the secure data object and comparing the second hash to the first hash to confirm that the one or more resource transfer parameters have not been modified after the signing.

Assignees

• Toronto Dominion Bank

Inventors

• Dunjic Milos
• Joheb Asad
• Tax David Samuel

Classifications

• G06F9/5011

  the resources being hardware resources other than CPUs, Servers and Terminals · CPC title

• G06F21/606

  by securing the transmission between two devices or processes · CPC title

• G06F21/64

  Protecting data integrity, e.g. using checksums, certificates or signatures · CPC title

• H04L2209/56

  Financial cryptography, e.g. electronic payment or e-cash · CPC title

• H04L9/3247 Primary

  involving digital signatures · CPC title