System and method for location-based token transaction processing
US-11354651-B2 · Jun 7, 2022 · US
US12373843B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12373843-B2 |
| Application number | US-202217571863-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 10, 2022 |
| Priority date | May 15, 2018 |
| Publication date | Jul 29, 2025 |
| Grant date | Jul 29, 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 device receives, from a user device, a request to generate a verification code for a transaction associated with a user of the user device, and receives user profile information associated with a transaction card to be used for the transaction. The device generates a random verification code for the transaction based on the request and the user profile information, and authenticates the random verification code, based on the user profile information, to generate an authenticated random verification code. The device provides the authenticated random verification code to the user device, and receives transaction information, including the authenticated random verification code, from a merchant device associated with the transaction. The device validates the transaction based on the transaction information, and provides, to the merchant device associated with the transaction, information indicating that the transaction is validated.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: receiving, by a user device and based on receiving a request to provide a verification code for a transaction associated with a transaction card, user input initiating the transaction; establishing a communication session between the user device and a transaction device based on receiving the user input initiating the transaction; selecting, by the user device, an encryption technique from a plurality of encryption techniques; encrypting, by the user device, using the encryption technique, and based on receiving the user input initiating the transaction, a request to generate the verification code for the transaction, wherein the encryption technique comprises: encrypting data using a public encryption key, and decrypting the data using a private decryption key; automatically providing, by the user device, based on encrypting the request to generate the verification code for the transaction, the request to generate the verification code for the transaction; receiving, by the user device and based on automatically providing the request to generate the verification code for the transaction, the verification code; and providing, by the user device, using the encryption technique, and based on receiving the verification code, transaction information associated with the transaction. 2. The method of claim 1 , wherein the verification code is not on the transaction card. 3. The method of claim 1 , wherein the request to generate the verification code includes at least one of: card number information associated with the transaction card, first credential information associated with a user of the user device, second credential information associated with the user device, identifying information associated with a merchant associated with the transaction, or biometric information associated with the user. 4. The method of claim 1 , wherein the request to generate the verification code includes verification code generation instructions associated with a user profile, and wherein the verification code generation instructions indicate whether the verification code is valid for at least one of: a single transaction, a particular merchant, or a particular time period. 5. The method of claim 1 , wherein the transaction information is provided based on receiving additional transaction user input associated with the transaction. 6. The method of claim 1 , wherein the transaction information is provided automatically without additional user input. 7. The method of claim 1 , further comprising: receiving, based on providing the transaction information, order confirmation information associated with the transaction. 8. The method of claim 1 , further comprising: automatically populating, based on receiving the verification code, transaction form information including the verification code. 9. A user device, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to: receive, based on receiving a request to provide a verification code for a transaction card, user input initiating a transaction; establish a communication session between the user device and a transaction device based on receiving the user input initiating the transaction; select an encryption technique from a plurality of encryption techniques; encrypt, using the encryption technique and based on receiving the user input initiating the transaction, a request to generate the verification code for the transaction, wherein the encryption technique: encrypts data using a public encryption key, and decrypts the data using a private decryption key; automatically provide, to a transaction device and based on encrypting the request to generate the verification code for the transaction, the request to generate the verification code for the transaction; receive, from the transaction device and based on automatically providing the request to generate the verification code for the transaction, the verification code; and provide, to a merchant device associated with the transaction, using the encryption technique, and based on receiving the verification code, transaction information associated with the transaction. 10. The user device of claim 9 , wherein the request to generate the verification code includes at least one of: card number information associated with the transaction card, first credential information associated with a user of the user device, second credential information associated with the user device, identifying information associated with a merchant associated with the transaction, or biometric information associated with the user. 11. The user device of claim 9 , wherein the request to generate the verification code includes verification code generation instructions associated with a user profile. 12. The user device of claim 11 , wherein the verification code generation instructions indicate whether the verification code is valid for at least one of: a single transaction, a particular merchant, or a particular time period. 13. The user device of claim 9 , wherein the one or more processors are further configured to: receive, based on providing the transaction information, order confirmation information associated with the transaction. 14. The user device of claim 9 , wherein the one or more processors are further configured to: automatically populate, based on receiving the verification code, transaction form information including the verification code. 15. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a user device, cause the user device to: receive, based on receiving a request to provide a verification code for a transaction associated with a transaction card, user input initiating the transaction; establish a communication session between the user device and a transaction device based on receiving the user input initiating the transaction; select an encryption technique from a plurality of encryption techniques; encrypt, using the encryption technique and based on receiving the user input initiating the transaction, a request to generate the verification code for the transaction, wherein the encryption technique comprises: encrypting data using a public encryption key; and decrypting the data using a private decryption key; automatically provide, based on encrypting the request to generate the verification code for the transaction, the request to generate the verification code for the transaction; receive, based on automatically providing the request to generate the verification code for the transaction, the verification code; and automatically provide, using the encryption technique and based on receiving the verification code and without receiving additional user input, transaction information associated with the transaction. 16. The non-transitory computer-readable medium of claim 15 , wherein the request is received from a merchant device associated with the transaction. 17. The non-transitory computer-readable medium of claim 15 , wherein the request to generate the verification code includes at least one of: card number information associated with the transaction card, first credential information associated with a user of the user device, second credential information associated with the user device, identifying information associated with a merchant associated with the transaction, or bi
Payment applications installed on the mobile devices · CPC title
insuring higher security of transaction · CPC title
Pseudo-random number generators · CPC title
using the card verification value [CVV] associated with the card · CPC title
using an alias or single-use codes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.