Authorizing Transactions Using Mobile Device Based Rules
US-2016132880-A1 · May 12, 2016 · US
US11823145B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11823145-B2 |
| Application number | US-202017107145-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 30, 2020 |
| Priority date | Nov 30, 2020 |
| Publication date | Nov 21, 2023 |
| Grant date | Nov 21, 2023 |
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.
Methods and systems are presented for providing a framework to securely integrate third-party logic into electronic transaction processing workflow. Third-party programming code that implements different third-party logic may be obtained and stored in a repository. A transaction processing request is received from a third-party server, and an instance of a transaction processing module is instantiated within an operating runtime environment to process a transaction according to a workflow. When the instance of the transaction processing module has reached an interruption point, the instance of the transaction processing module is suspended, and a third-party programming code is executed within an isolated runtime environment. The third-party programming code is configured to provide an output value based on attributes of the transaction. The instance of the transaction processing module then determines whether to authorize or deny the transaction based in part on the output value.
Opening claim text (preview).
What is claimed is: 1. A system, comprising: one or more hardware processors; a repository storing a plurality of third-party programming codes corresponding to a plurality of merchants, wherein each third-party programming code in the plurality of third-party programming codes comprises (i) information associated with a corresponding merchant and (ii) third-party logic that is associated with the corresponding merchant and provided by a third-party merchant server of the corresponding merchant; and a non-transitory memory storing instructions associated with a logic integration module and a transaction processing module, wherein the instructions, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations comprising: receiving an electronic payment transaction request from a device via a particular third-party merchant server; in response to receiving the electronic payment transaction request, instantiating an instance of the transaction processing module in a first runtime environment, wherein the instance of the transaction processing module is configured to process an electronic payment transaction associated with the electronic transaction payment request in the first runtime environment; providing, via the instance of the transaction processing module, a user interface on the device; obtaining, via the user interface on the device, user data associated with the electronic payment transaction; determining a particular merchant associated with the particular third-party merchant server based on the user data; identifying, from the plurality of third-party programming codes stored in the repository, a particular third-party programming code corresponding to the particular merchant; suspending the instance of the transaction processing module; while the instance of the transaction processing module is suspended, executing the particular third-party programming code in a second runtime environment, wherein the second runtime environment is isolated from the first runtime environment; providing, to the particular third-party programming code executed in the second runtime environment via an application programming interface, at least a portion of the user data, wherein the particular third-party programming code is configured to generate an output value based on the at least the portion of the user data; obtaining the output value generated by the particular third-party programming code executed in the second runtime environment, wherein the output value indicates whether to accept or reject the electronic payment transaction by the particular merchant; resuming the instance of the transaction processing module; and processing the electronic payment transaction based at least in part on the output value, wherein the processing comprises authorizing, denying, or further processing the electronic payment transaction based at least in part on the output value. 2. The system of claim 1 , wherein the processing the electronic payment transaction is further based on the user data. 3. The system of claim 1 , wherein the operations further comprise transmitting, to the particular third-party merchant server, an indication that the electronic payment transaction is either authorized, denied, or further processed based on the output value. 4. The system of claim 1 , wherein the second runtime environment restricts the particular third-party programming code from accessing a networked component associated with the first runtime environment. 5. The system of claim 1 , wherein the second runtime environment restricts the particular third-party programming code from accessing a system level service associated with the first runtime environment. 6. The system of claim 1 , wherein the operations further comprise transmitting, to the particular third-party programming code via the application programming interface, a set of attributes associated with the electronic payment transaction, wherein the particular third-party programming code is configured to generate the output value further based on the set of attributes. 7. The system of claim 1 , wherein the user data comprises at least one of a shipping address, a billing address, a payment card number, a payment card type, or an expiration date of a payment card. 8. A method performed by a computer system that includes one or more hardware processors, a memory storing a logic integration module and a transaction processing module, and a repository storing a plurality of third-party programming codes corresponding to a plurality of merchants, wherein each third-party programming code in the plurality of third-party programming codes comprises (i) information associated with a corresponding merchant and (ii) third-party logic that is associated with the corresponding merchant and provided by a third-party merchant server of the corresponding merchant, the method comprising: receiving, by the computer system, an electronic payment transaction request from a device via a particular third-party merchant server; in response to receiving the electronic payment transaction request, instantiating, by the computer system, an instance of the transaction processing module in a first runtime environment, wherein the instance of the transaction processing module is configured to process an electronic payment transaction associated with the electronic payment transaction request in the first runtime environment; providing, by the computer system and via the instance of the transaction processing module, a user interface on the device; receiving, by the computer system and via the user interface on the device, user data associated with the electronic payment transaction; determining, by the computer system, a particular third party merchant associated with the third-party merchant server based on the user data; identifying, by the computer system from the plurality of third-party programming code stored in the repository, a particular third-party programming code corresponding to the particular merchant; suspending, by the computer system, the instance of the transaction processing module; while the instance of the transaction processing module is suspended, executing, by the computer system, the particular third-party programming code in a second runtime environment, wherein the second runtime environment is isolated from the first runtime environment; providing, by the computer system and to the particular third-party programming code executed in the second runtime environment via an application programming interface, at least a portion of the user data, wherein the particular third-party programming code is configured to generate an output value based on the at least the portion of the user data; obtaining, by the computer system, the output value generated by the particular third-party programming code executed in the second runtime environment, wherein the output value indicates whether to accept or reject the electronic payment transaction by the particular merchant; resuming, by the computer system, the instance of the transaction processing module; and processing, by the computer system, the electronic payment transaction based at least in part on the output value, wherein the processing comprises authorizing, denying, or further processing the electronic payment transaction based at least in part on the output value. 9. The method of claim 8 , wherein the processing the electronic payment transaction is further based on the user data. 10. The method of claim 9 , wherein the output value indicates a denial of the electronic payment transaction based on a first portion of the user data obtained via the user inte
involving a third party · CPC title
involving event detection and direct action · CPC title
Bill distribution or payments · CPC title
involving fraud or risk level assessment in transaction processing · CPC title
Biometric identity checks · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.