Generating a random verification code for a transaction
US-10496998-B1 · Dec 3, 2019 · US
US11222340B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11222340-B2 |
| Application number | US-201916699939-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 2, 2019 |
| Priority date | May 15, 2018 |
| Publication date | Jan 11, 2022 |
| Grant date | Jan 11, 2022 |
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 device and from an application of a user device different from the device, a request, based on a user interaction with the application, to generate a verification code required for a transaction between a merchant and a user of the user device, wherein the merchant provides the application which is a software application to the user device, wherein the transaction includes card information, associated with a transaction card, that does not include the verification code, wherein the transaction card is associated with the user, and wherein the merchant is associated with the transaction; generating, by the device, the verification code based on the request and based on user profile information, wherein the user profile information is associated with the transaction card, and wherein the user profile information includes information indicating that the verification code is valid within a particular time period; authenticating, by the device and based on the user profile information, the verification code to generate an authenticated verification code; encrypting, by the device, a first message that comprises the generated authenticated verification code with a public key and a second key; providing, by the device, the encrypted first message to the application, wherein the application provides transaction information, that is associated with the transaction and includes the authenticated verification code, to a merchant device that is associated with the merchant and is different from the device and user device; receiving, by the device and from the merchant device, the transaction information, wherein the device receives the transaction information based on: the device providing the authenticated verification code to the application, and the application providing the transaction information to the merchant device; determining, by the device and based on receiving the transaction information, that the generated authenticated verification code is being utilized within the particular time period; validating, by the device, the transaction based on determining that the generated authenticated verification code is being utilized within the particular time period; encrypting, by the device and based on validating the transaction, a second message, that is different from the first message and comprises information indicating that the transaction is validated, with the public key and the second key, wherein the second key is used to decrypt at least one of the encrypted first message or the encrypted second message; and providing, the encrypted second message to the merchant device. 2. The method of claim 1 , wherein the user device includes a mobile device and the application is a mobile device application associated with the mobile device, and wherein receiving the request to generate the authenticated verification code comprises: receiving the request from the mobile device application. 3. The method of claim 1 , wherein the user device includes a computer device and the application is a browser application associated with the computer device, and wherein receiving the request to generate the authenticated verification code comprises: receiving the request from the browser application. 4. The method of claim 1 , wherein the user device includes a mobile device, and wherein receiving the request to generate the authenticated verification code comprises: receiving the request from a call initiated by the mobile device. 5. The method of claim 1 , wherein the user device includes a smart device, and wherein receiving the request to generate the authenticated verification code comprises: receiving the request from the smart device based on a voice command provided to the smart device. 6. The method of claim 1 , further comprising: updating a dynamically updatable record associated with an account of the user to associate the authenticated verification code with the account; and wherein validating the transaction comprises: validating the transaction based on the dynamically updatable record. 7. The method of claim 1 , wherein the application populates a transaction form, associated with the transaction, having the authenticated verification code, and wherein the transaction information includes the transaction form. 8. The method of claim 1 , wherein the authenticated verification code is generated using a random number generator. 9. The method of claim 1 , wherein the user profile information indicates a type of the authenticated verification code to generate. 10. A device, comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories, configured to: receive, from an application of a user device different from the device, a request, based on a user interaction with the application, to generate a verification code required for a transaction between a merchant and a user of the user device, wherein the merchant provides the application which is a software application to the user device, wherein the transaction includes card information, associated with a transaction card that does not include the verification code, wherein the transaction card is associated with the user, and wherein the merchant is associated with the transaction; generate the verification code for the transaction based on the request and based on user profile information, wherein the user profile information is associated with the transaction card, and wherein the user profile information includes information indicating that the verification code is valid within a particular time period; authenticate, based on the user profile information, the verification code to generate an authenticated verification code; encrypt a first message that comprises the generated authenticated verification code with a public key and a second key; provide the encrypted first message to the application, wherein the application provides transaction information, that is associated with the transaction and includes the authenticated verification code, to a merchant device that is associated with the merchant and is different from the device and the user device; receive, from the merchant device, the transaction information, wherein the device receives the transaction information based on: the device providing the authenticated verification code to the application, and the application providing the transaction information to the merchant device; determine, based on receiving the transaction information, that the generated authenticated verification code is being utilized within the particular time period; validate the transaction based on determining that the generated authenticated verification code is being utilized within the particular time period; and encrypt, based on validating the transaction, a second message, that is different from the first message and comprises information indicating that the transaction is validated, with the public key and the second key, wherein the second key is used to decrypt at least one of the encrypted first message or the encrypted second message; and provide the encrypted second message to the merchant device. 11. The device of claim 10 , wherein the user device includes a mobile device and the application is a mobile device application associated with the mobile device, and wherein the one or more processors, when receiving the request to generate the authenticated verification code, are configured to: receive the request from the mobile device application. 12. The device of claim 10
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.