Enhanced mobile wallet payment elements
US-11250422-B1 · Feb 15, 2022 · US
US2023259921A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2023259921-A1 |
| Application number | US-202318304157-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 20, 2023 |
| Priority date | Apr 24, 2020 |
| Publication date | Aug 17, 2023 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
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 initiates a financial transaction to occur; and sending the configured executable application, including information to complete the financial transaction, 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 at the first user device. 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, 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. 6 . The method of claim 5 , wherein running the version of the executable application includes outputting a confirmation of the financial transaction. 7 . The method of claim 1 , wherein configuring the executable application includes configuring the executable application to only run when within a secure environment, the secure environment including a secure enclave region of memory of the second user device. 8 . 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 financial transaction application, to a second data structure having a second format that is readable by a second financial transaction application. 9 . The method of claim 1 , wherein the financial transaction is a money transfer configured to occur from a transferor account of a user of the first user device to an account of a user of the second user device. 10 . The method of claim 1 , further comprising, receiving, during the handshake, an encryption type or a file size limit. 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 initiates a financial transaction to occur; and send the configured executable application, including information to complete the financial transaction, 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 the executable application includes a unique identifier, the unique identifier identifying at least one of the financial transaction or the first user device. 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; and output a confirmation of the financial transaction by the first user device from the version of the executable application. 17 . 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 a secure enclave region of memory of the second user device. 18 . 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 financial transaction application, to a second data structure having a second format that is readable by a second financial transaction application. 19 . The first user device of claim 11 , wherein the financial transaction is a money transfer configured to occur from a transferor account of a user of the first user device, to an account of a user of the second user device. 20 . At least one non-transitory machine readable medium including instructions, which when executed by processing circuitry of a first user device, cause the processing circuitry to perform operations to: perform 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 initiates a financial transaction to occur, the configured executable application including information to complete the financial transaction; and send a link to access the configured executable application to the second user device for execution.
insuring higher security of transaction · CPC title
Configuring for program initiating, e.g. using registry, configuration files · CPC title
Software deployment · CPC title
Unloading · CPC title
Protecting executable software · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.