Terminal and method for mobile payment with trusted execution environment
US-2018150826-A1 · May 31, 2018 · US
US12423674B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12423674-B2 |
| Application number | US-201916535984-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 8, 2019 |
| Priority date | Aug 8, 2019 |
| Publication date | Sep 23, 2025 |
| Grant date | Sep 23, 2025 |
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.
A Secure Transaction System can receive a request to initiate a transaction from a payment application. The request can include merchant information obtained from a QR code generated for a merchant. The Secure Transaction System can search a merchant storage resource for corresponding contact information for the merchant identified by the merchant information and communicate a password over a communication channel using the contact information for the merchant. The password sent to the merchant can be provided to the payment application in some manner and the payment application can communicate the password to the Secure Transaction System, which determines whether the verification information satisfies conditions with respect to the password for the merchant and communicates confirmation to the payment application that the transaction can proceed when the verification information satisfies the conditions.
Opening claim text (preview).
What is claimed is: 1. A Secure Transaction System, comprising: a processing system; a storage system comprising a merchant storage resource; and instructions for secure transactions stored on the storage system that when executed by the processing system, direct the secure transaction system to at least: receive, from a payment application of a computing device of a customer, a request to initiate a transaction for the customer, the request comprising merchant information encoded in a QR code that was received by the computing device of the customer via a QR scanner module; in response to the request to initiate the transaction from the payment application of the computing device of the customer: search the merchant storage resource for corresponding pre-registered contact information for a merchant identified by the merchant information; generate a one-time password for the merchant; and communicate the one-time password to the merchant over a communication channel of an email or messaging application using the pre-registered contact information for the merchant; receive, from the payment application of the computing device of the customer, verification information comprising the one-time password previously communicated to the merchant; determine whether the verification information satisfies conditions with respect to the password for the merchant, the conditions comprising accuracy, timing, and number of tries associated with the password; receive, from the payment application of the computing device of the customer, payment information for the transaction; perform a pre-authorization process with respect to the payment information received from the payment application of the computing device of the customer; and after determining that the verification information satisfies the conditions and performing the pre-authorization process, communicate confirmation to the computing device of the customer and the merchant that the transaction has processed. 2. The system of claim 1 , wherein the instructions to communicate the one-time password over the communication channel directs the system to communicate an SMS message to the messaging application. 3. The system of claim 1 , wherein the instructions to communicate the one-time password over the communication channel directs the system to communicate an email to the email application. 4. The system of claim 1 , further comprising instructions that direct the system to: in response to a pre-registration request providing contact information of the merchant for storing in the merchant storage resource, store the contact information in the merchant storage resource in association with identifying merchant information. 5. A method for secure transactions, comprising: providing a payment application to a computing device of a customer comprising a QR scanner module and electronic wallet; pre-registering contact information for a merchant, wherein the pre-registered contact information for the merchant is a third-party authentication application for the merchant, an email, a messaging application contact, or a payment application of the merchant having an authentication module; receiving, at a secure transaction system from the computing device of the customer, payment information that was received from the electronic wallet of the provided payment application of the computing device of the customer and merchant information encoded in a QR code that was received from the QR scanner module of the provided payment application of the computing device of the customer for performing a transaction; in response to receiving the payment information and the merchant information from the provided payment application of the computing device of the customer for performing the transaction: identifying, by the secure transaction system, a merchant account from the merchant information received from the provided payment application of the computing device of the customer and an associated pre-registered contact information for the merchant; generating, by the secure transaction system, a One-Time Password (OTP) for the merchant; and sending the OTP to the pre-registered contact information for the merchant; receiving a password via the provided payment application of the computing device of the customer; confirming timing associated with the password, a number of tries associated with the password, and that the password received via the provided payment application of the computing device of the customer corresponds to the OTP sent to the pre-registered contact information for the merchant; performing a pre-authorization process with respect to the payment information received from the provided payment application of the computing device of the customer; after performing the pre-authorization process and confirming the timing associated with the password, the number of tries associated with the password, and that the password received via the provided payment application of the computing device of the customer corresponds to the OTP sent to the merchant, communicating confirmation to the computing device of the customer and to the re-registered contact information for the merchant that the transaction is processed. 6. The method of claim 5 , wherein sending the OTP to the pre-registered contact information for the merchant comprises communicating the OTP to the payment application of the merchant having the authentication module. 7. The method of claim 5 , wherein sending the OTP to the pre-registered contact information for the merchant comprises communicating the OTP to the third-party authentication application of the merchant. 8. The method of claim 5 , wherein sending the OTP to the pre-registered contact information for the merchant comprises communicating an SMS with the OTP to the messaging application contact via a messaging application. 9. The method of claim 5 , wherein sending the OTP to the pre-registered contact information for the merchant comprises communicating the OTP to the email of the merchant via an email application.
using an alias or single-use codes · CPC title
using mobile network messaging services for payment, e.g. SMS · CPC title
characterised in that multiple accounts are available, e.g. to the payer · CPC title
2D bar codes · CPC title
RFID or NFC payments by means of M-devices · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.