Electronic device for controlling electronic payment and method therefor
US-11232456-B2 · Jan 25, 2022 · US
US11699152B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11699152-B2 |
| Application number | US-202117389984-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 30, 2021 |
| Priority date | Jan 19, 2015 |
| Publication date | Jul 11, 2023 |
| Grant date | Jul 11, 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.
Systems (100, 900), methods, and machine-executable data structures for the processing of data for the secure creation, administration, manipulation, processing, and storage of electronic data useful in the processing of electronic payment transactions and other secure data processes. Aspects of such systems (100) include trusted platforms (120) by which networked communication devices (110) and merchant systems (130) may registered as trusted entities 110′, 130. Information associated with particular payment means, such as accounts or payment tokens, can be stored on device(s) secure data sets known as virtual or electronic wallets (112), or in the form of secure payment tokens. Among other improvements, the invention enables the use of multiple payment accounts to fund purchases and other electronic transactions.
Opening claim text (preview).
The invention claimed is: 1. A computer-implemented method comprising: using signals generated by at least one user input interface of a user device, and signals received from a merchant transaction system via at least one near-field communication interface: generating, by at least one third-party wallet application at the user device, a requested transaction data set, the requested transaction data set comprising at least an identifier associated with a merchant and a transaction amount payable to the merchant; in response to further signals generated by the at least one user input interface: generating, by at least one trusted wallet application at the user device, a transaction authorization request data set comprising data representing at least the merchant, the transaction amount payable to the merchant, at least two transaction payment funding sources, and a portion of the transaction amount payable to the merchant to be funded using each of the plurality of transaction payment funding sources; using a communication interface of the user device: routing, by the at least one trusted wallet application, the transaction authorization request data set to a transaction processing system; receiving, by the at least one trusted wallet application from the transaction processing system, in response to the transaction authorization request data set, a dynamic card token comprising the transaction amount payable to the merchant, and a single transaction payment funding source identifier; passing, by the at least one trusted wallet application to the at least one third-party wallet application, the dynamic card token; sending, by the at least one third-party wallet application, the dynamic card token to the merchant transaction system; and receiving, at the user device, a confirmation message that the transaction is complete. 2. The computer-implemented method of claim 1 , comprising: displaying, at a touch sensitive input-output display interface of the user device, an interactive slider graphical device adapted to enable a user of the user device to designate a desired portion of the transaction amount payable to the merchant to be funded using at least one of the plurality of payment funding sources; and using signals generated in response to user designation of the desired portion: generating the same or another transaction authorization request data set. 3. The computer-implemented method of claim 1 , wherein the plurality of transaction payment funding sources comprises at least any two of: a least one currency debit account, at least one currency credit account, and at least one non-currency value account. 4. The computer-implemented method of claim 3 , wherein at least of the at least one currency debit account and at least one currency credit account comprises a gift account. 5. The computer-implemented method of claim 3 , wherein the at least one non-currency value account comprises at least one of a loyalty points account, a rewards points account, and a gift account. 6. The computer-implemented method of claim 1 , wherein the plurality of transaction payment funding sources comprises at least one of: a loyalty points account, a rewards points account, and a gift account; which is not acknowledged by said merchant as a transaction payment funding source. 7. The computer-implemented method of claim 1 , wherein the generated transaction authorization request data set comprises data interpretable by the transaction processing platform as an instruction to cause the amount payable to the merchant to be funded using at least one interim funding source. 8. The computer-implemented method of claim 7 , wherein the at least one interim funding source is not represented by the data representing the at least two transaction payment funding sources. 9. The computer-implemented method of claim 1 , wherein the transaction authorization request data set is formatted in accordance with a payment protocol, the payment protocol providing a discretionary data field, and the discretionary data field comprises data encoded to represent the at least two payment funding sources and the portion of the transaction amount payable to the merchant to be funded using each of the plurality of payment funding sources. 10. A computer-implemented method comprising: using a communication interface at a user device: establishing, by a third-party wallet application on the user device, a transaction communication session with a merchant transaction system; using signals generated by a user input interface at the user device, and signals received from a merchant transaction system via the transaction communication session: generating, by a third-party wallet application at the user device, a requested transaction data set, the requested transaction data set comprising at least an identifier associated with a merchant and a transaction amount payable to the merchant; in response to further signals generated by the user input interface: generating, by a trusted wallet application at the user device, a transaction authorization request data set comprising data representing at least the merchant, the transaction amount payable to the merchant, at least two transaction payment funding sources, and a portion of the transaction amount payable to the merchant to be funded using each of the plurality of transaction payment funding sources; using a communication interface at the device: route, by the trusted wallet application, the transaction authorization request data set to a transaction processing system; receiving, by the trusted wallet application from the transaction processing system, in response to the transaction authorization request data set, a dynamic card token comprising the transaction amount payable to the merchant, and a single transaction payment funding source identifier; passing, by the trusted wallet application to the third-party wallet application, the dynamic card token; sending, by the third-party wallet application, the dynamic card token to the merchant transaction system; and receiving, at the user device, a confirmation message that the transaction is complete. 11. The computer-implemented method of claim 10 , wherein the transaction communication session is established by execution of stored, machine-interpretable instructions associated with a merchant transaction application. 12. The computer-implemented method of claim 10 , wherein the transaction communication session is established by execution of stored, machine-interpretable instructions associated with a network browser application. 13. The computer-implemented method of claim 11 , wherein the plurality of transaction payment funding sources comprises at least any two of: a least one currency debit account, at least one currency credit account, and at least one non-currency value account. 14. The computer-implemented method of claim 12 , wherein at least of the at least one currency debit account and at least one currency credit account comprises a gift account. 15. The computer-implemented method of claim 12 , wherein the at least one non-currency value account comprises at least one of a loyalty points account, a rewards points account, and a gift account. 16. The computer-implemented method of claim 10 , wherein the plurality of transaction payment funding sources comprises at least one of: a loyalty points account, a rewards points account, and a gift account; which is not acknowledged by said merchant as a transaction payment funding source. 17. The computer-implemented method of claim 10 , wh
using electronic wallets or electronic money safes · CPC title
the neutral party being a clearing house · CPC title
specially adapted for electronic shopping systems · CPC title
Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists · CPC title
involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.