Transfer via transaction app

Patent metadata

Field	Value
Publication number	US-11663587-B2
Application number	US-202016858104-A
Country	US
Kind code	B2
Filing date	Apr 24, 2020
Priority date	Apr 24, 2020
Publication date	May 30, 2023
Grant date	May 30, 2023

Abstract

Systems and methods may generally include sending an executable application, which when executed, automatically causes a monetary transfer. An example method may include performing, at a first user device, a handshake with a second user device, receiving, during the handshake, an operating capability of the second user device, and configuring, based on the operating capability of the second user device, an executable application, which when executed, automatically causes a monetary transfer to occur. The configured executable application may be sent to the second user device for execution.

First claim

What is claimed is:

1. A method comprising:
performing, at a first user device, a handshake with a second user device;
receiving, during the handshake, an operating capability of the second user device;
configuring, using a processor of the first user device and based on the operating capability of the second user device, an executable application, which when executed, automatically causes a monetary transfer to occur; and
sending the configured executable application, including information indicative of a transferor account and an amount for executing the monetary transfer, to the second user device for execution.

2. The method of claim 1 , wherein the configured executable application is a single run executable application that deletes itself after running.

3. The method of claim 1 , wherein configuring the executable application includes encrypting the executable application.

4. The method of claim 1 , wherein the operating capability of the second user device is based on at least one of a device type, an operating system, a hardware component, or a secure environment.

5. The method of claim 1 , further comprising, receiving, during the handshake, an encryption type or a file size limit.

6. The method of claim 1 , further comprising, in response to receiving an indication that the second user device has run the configured executable application, running, at the first user device, a version of the executable application configured according to an operating capability of the first user device.

7. The method of claim 6 , wherein running the version of the executable application includes outputting a confirmation of the monetary transfer.

8. The method of claim 1 , wherein configuring the executable application includes configuring the executable application to only run within a secure environment of the second user device, the secure environment including an enclave region of memory of the second user device.

9. The method of claim 1 , wherein the configured executable application includes a handler configured to convert a first data structure created by the first user device, using a first format of a first monetary transfer application, to a second data structure having a second format that is readable by a second monetary transfer application.

10. The method of claim 1 , wherein the money transfer is configured to occur from the transferor account, which is an account of a user of the first device, to an account of a user of the second user device.

11. A first user device comprising:
processor circuitry; and
memory, including instructions, which when executed by the processing circuitry, causes the processing circuitry to perform operations to:
initiate a handshake with a second user device;
receive, during the handshake, an operating capability of the second user device;
configure, based on the operating capability of the second user device, an executable application, which when executed, automatically causes a monetary transfer to occur; and
send the configured executable application, including information indicative of a transferor account and an amount for executing the monetary transfer, to the second user device for execution.

12. The first user device of claim 11 , wherein the configured executable application is a single run executable application that deletes itself after running.

13. The first user device of claim 11 , wherein to configure the executable application, the instructions further cause the processing circuitry to encrypt the executable application.

14. The first user device of claim 11 , wherein the operating capability of the second user device is based on at least one of a device type, an operating system, a hardware component, or a secure environment.

15. The first user device of claim 11 , wherein an encryption type or a file size limit is received during the handshake.

16. The first user device of claim 11 , wherein the instructions further cause the processing circuitry to, in response to receiving an indication that the second user device has run the configured executable application, run, at the first user device, a version of the executable application configured according to an operating capability of the first user device.

17. The first user device of claim 16 , wherein a confirmation of the monetary transfer is output by the first user device from the version of the executable application.

18. The first user device of claim 11 , wherein the configured executable application is configured to only run within a secure environment of the second user device, the secure environment including an enclave region of memory of the second user device.

19. The first user device of claim 11 , wherein the configured executable application includes a handler configured to convert a first data structure created by the first user device, using a first format of a first monetary transfer application, to a second data structure having a second format that is readable by a second monetary transfer application.

20. The first user device of claim 11 , wherein the money transfer is configured to occur from the transferor account, which is an account of a user of the first device, to an account of a user of the second user device.

Assignees

• Wells Fargo Bank Na

Inventors

• Kalaboukis Chris Theodore
• Maeng Joon
• Ramanathan Ramanathan
• Rao Abhijit
• Shetti Abhijit

Classifications

• G06F8/61

  Installation · CPC title

• G06Q20/3676

  Balancing accounts · CPC title

• G06Q40/02 Primary

  Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03) · CPC title

• G06F9/44505

  Configuring for program initiating, e.g. using registry, configuration files · CPC title

• G06Q20/382 Primary

  insuring higher security of transaction · CPC title