Electronic device for controlling electronic payment and method therefor
US-11232456-B2 · Jan 25, 2022 · US
US11687928B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11687928-B2 |
| Application number | US-202117387711-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 28, 2021 |
| Priority date | Jan 19, 2015 |
| Publication date | Jun 27, 2023 |
| Grant date | Jun 27, 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 ), 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. Common application programming interfaces executed by devices ( 110 ) may facilitate push and pull processes between electronic wallets ( 112 ) and other secure data stores ( 136, 120, 160 ). Users ( 190 ) may thereby initiate and complete electronic transactions directly from within applications on trusted devices ( 110 ′).
Opening claim text (preview).
The invention claimed is: 1. A computer-implemented method comprising: receiving a first set of signals from a merchant application on a user device, the first set of signals including data representing a merchant certificate used as part of a query of a plurality of secure payment tokens in at least one persistent memory of the user device, each secure payment token comprising data representing an identifier associated with one of a plurality of sources of transaction payment resources and a security key uniquely associated with said source of transaction payment resources; initiating on the user device, in response to the first set of signals, a payment transaction process, the payment transaction process generating, 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; verifying, at the user device, a merchant certificate associated with the merchant identifier; selecting, from the plurality of secure payment tokens stored in the at least one persistent memory, at least one secure payment token associated with the merchant; generating, at a universal wallet application on the user device, transaction authorization request data sets, each transaction authorization request data set comprising at least one of the selected at least one secure payment token, and at least one transaction payment amount; receiving, at a user input interface of the user device, a user selection identifying one of the plurality of sources of transaction payment resources; generating a transaction authorization request data set on the user device, the generated transaction authorization request data set comprising at least one of: the selected at least one secure payment token associated with the selected source of transaction payment resources, or the transaction amount payable to the merchant; sending, using at least one network communication interface at the user device, the generated transaction authorization request data set to a merchant backend server to be routed to a server associated with the identified source of payment resources; and receiving confirmation that the transaction was completed. 2. The computer-implemented method of claim 1 , wherein generation and routing of the transaction authorization request data set is conditioned upon receipt by the at least one data processor of a fourth set of signals generated by the at least one user input interface, the fourth set of signals comprising at least a secure identifier associated with an authorized user of the device. 3. The computer-implemented method of claim 1 , comprising: receiving, from the same or another server associated with the identified source of payment resources, a secure transaction authorization request data set; and routing the secure transaction authorization request data set to a transaction processing system associated with the merchant. 4. The computer-implemented method of claim 1 , wherein at least a portion of the transaction payment resources represent currency. 5. The computer-implemented method of claim 1 , wherein at least a portion of the transaction payment resources represent non-currency redeemable points. 6. A computer-implemented method comprising: initiating at a user device, in response to a first set of signals generated by at least one user input interface, a payment transaction process, the payment transaction process generating, 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; verifying, at the user device, a merchant certificate associated with the merchant identifier; selecting, from a plurality of secure payment tokens stored in at least one persistent memory, at least one secure payment token associated with the merchant, each secure payment token comprising data representing an identifier associated with one of a plurality of sources of transaction payment resources; and initiating a first wallet application on the user device; displaying, at an output display, a human-interpretable user interface adapted to solicit a user selection of one of: a plurality of sources of payment resources to be applied toward satisfaction of a requested transaction, at least one of the sources of payment resources associated with the source of payment resources identified by the first one of the plurality of secure payment tokens, or at least a second of the sources of payment resources not associated with the source of payment resources identified by the first one of the plurality of secure payment tokens; receiving, at a user input interface, a user selection of one of the plurality of sources of payment resources to be applied toward satisfaction of a related transaction; when the user selection of one of the plurality of sources of payment resources corresponds to the source of payment resources identified by the first one of the plurality of secure payment tokens: generating, at the user device, a transaction authorization request data set comprising at least the first one of the plurality of secure payment tokens, and sending the transaction authorization request data set to a merchant backend server to be routed to a server associated with the source of payment resources identified by the first one of the plurality of secure payment tokens; and receiving confirmation that the transaction was completed. 7. The computer-implemented method of claim 6 , comprising: when the user selection of one of the plurality of sources of payment resources does not correspond to the source of payment resources identified by the first one of the plurality of secure payment tokens: initiating a second wallet application on the user device; and generating a transaction authorization request data set comprising at least the second one of the plurality of secure payment tokens. 8. The computer-implemented method of claim 7 , comprising: routing, using at least one network communication interface, a transaction authorization request data set generated by either the first or the second wallet application to a transaction processing system associated with the merchant. 9. The computer-implemented method of claim 6 , wherein at least a portion of the transaction payment resources represent currency. 10. The computer-implemented method of claim 6 , wherein at least a portion of the transaction payment resources represent non-currency redeemable points. 11. A computer-implemented method comprising: initiating, at the user device, a merchant transaction application associated with a merchant; verifying, at the user device, a merchant certificate associated with the merchant; selecting, from a plurality of secure payment tokens stored in the at least one persistent memory, at least one secure payment token associated with the merchant, the at least one secure payment token comprising data associated with an authorized payment amount and a financial service provider by which the authorized payment amount was authorized; generating, at the user device, a requested transaction data set, the requested transaction data set comprising at least an identifier associated with the merchant and a transaction amount payable to the merchant; and displaying, at an output display, a human-interpretable user interface adapted to solicit a user selection of a merchant checkout process and a virtual wallet application payment process, the virtual wallet application process associated with a virtual wallet application; receiving, at a
characterised in that multiple accounts are available, e.g. to the payer · 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
the neutral party being a clearing house · CPC title
with the personal data of a user · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.