Agile OTP generation
US-9118663-B1 · Aug 25, 2015 · US
US11961089B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11961089-B2 |
| Application number | US-202117235082-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 20, 2021 |
| Priority date | Apr 20, 2021 |
| Publication date | Apr 16, 2024 |
| Grant date | Apr 16, 2024 |
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, methods, articles of manufacture, and computer-readable media. A web browser of a device may receive selection of a uniform resource locator (URL). An operating system may download an application from an application server based on the URL. The application may identify a plurality of applications installed on the device and select a first institution corresponding to a first application. The application may receive a cryptogram from a contactless card associated with the first institution and transmit the cryptogram to an authentication server. The application may receive an authentication result specifying the authentication server decrypted the cryptogram. The web browser may receive, based on the decryption of the cryptogram, an account number, an expiration date associated with the account number, and a card verification value (CVV) associated with the account number. The web browser may provide the account number, expiration date, and CVV to a server associated with the application.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method, comprising: receiving, by a web browser executing on a processor of a device, selection of a uniform resource locator (URL) in a merchant web page, the merchant web page associated with a transaction; downloading, by an operating system (OS) executing on the processor, an application from an application server based on the URL, wherein the URL is directed to the application at the application server; identifying, by the application, a plurality of financial institution applications installed on the device; selecting, by the application, a first financial institution application of the plurality of financial institution applications based on a respective score for each financial institution application, wherein the first financial institution application is associated with a first financial institution, wherein the respective scores are computed based on: (i) an amount of time that has elapsed since the respective financial institution application was used on the device, and (ii) a number of times the respective financial institution application has been used on the device; receiving, by the application, a cryptogram from a contactless card associated with the first financial institution; transmitting, by the application, the cryptogram to an authentication server of the first financial institution; receiving, by the application, an authentication result specifying the authentication server decrypted the cryptogram; receiving, by the web browser based on the decryption of the cryptogram by the authentication server, an account number, an expiration date associated with the account number, and a card verification value (CVV) associated with the account number; and providing, by the web browser, the account number, the expiration date, and the CVV to a server associated with the application to process the transaction. 2. The method of claim 1 , the method further comprising: receiving, by the web browser, a confirmation for the processed transaction; and displaying, by the web browser, the confirmation. 3. The method of claim 2 , further comprising: storing, by the web browser, a cookie on the device based on a received indication from the server associated with the application, the indication specifying payment for the transaction has been processed using the account number, the expiration date, and the CVV. 4. The method of claim 3 , further comprising prior to providing the account number, the expiration date, and the CVV to the server associated with the application: receiving, by the application, input comprising an email address; transmitting, by the application, the email address to the authentication server; determining, by the application, a phone number associated with the email address; receiving, by the device, a one-time passcode from the authentication server, wherein the device is associated with the phone number; receiving, by the application, an input value; comparing, by the application, the input value to the one-time passcode; and determining, by the application based on the comparison, that the input value matches the one-time passcode, wherein the application transmits the cryptogram to the authentication server based at least in part on the determination that the input value matches the one-time passcode. 5. The method of claim 3 , further comprising subsequent to providing the account number, the expiration date, and the CVV to the server associated with the application: receiving, by the web browser, a second selection of the URL in the merchant web page, the second selection of the URL to process a second transaction using the application; downloading, by the OS, the application from the application server based on the URL; identifying, by the application, the cookie on the device; selecting, by the application based on the cookie, the contactless card associated with the first financial institution; requesting, by the application from the authentication server, the account number, the expiration date, and the CVV, wherein the application requests the account number, the expiration date, and the CVV without requiring the verification of another cryptogram generated by the contactless card based on a token in the cookie; receiving, by the application from the authentication server based on the request, the account number, the expiration date, and the CVV; and providing, by the application, the account number, the expiration date, and the CVV to the server associated with the application to process the second transaction. 6. The method of claim 1 , further comprising: receiving, by the web browser, a selection of a second URL in a second merchant web page, the selection of the second URL to process a second transaction; downloading, by the OS, a second application from the application server based on the second URL; selecting, by the second application, a second financial institution corresponding to a second financial institution application of the plurality of financial institution applications installed on the device; receiving, by the second application, a second cryptogram from a second contactless card associated with the second financial institution; receiving, by the second application, an authentication result specifying a second authentication server associated with the second financial institution decrypted the second cryptogram; receiving, by the web browser from the second authentication server and based on decryption of the second cryptogram by the second authentication server, a virtual account number, an expiration date for the virtual account number, and a CVV for the virtual account number; and providing, by the web browser, the virtual account number, the expiration date for the virtual account number, and CVV for the virtual account number to a web server hosting the second merchant web page to process the second transaction. 7. The method of claim 1 , wherein the URL comprises a first identifier of a first merchant associated with the merchant web page and a customer identifier, wherein the first merchant is one of a plurality of merchants, wherein the merchant web page is one of a plurality of merchant web pages on a web server, wherein the web server hosts the plurality of merchant web pages, wherein each merchant web page is associated with a respective one of the plurality of merchants, wherein each merchant is associated with a respective identifier of a plurality of identifiers, the plurality of identifiers including the first identifier, wherein the server associated with the application comprises one of a payment processing server or the web server. 8. The method of claim 1 , wherein the scores are further computed based on: (iii) one or more rules. 9. A system, comprising: a processor; and a memory storing instructions that when executed by the processor cause the processor to: receive, by a web browser executing on the processor, selection of a uniform resource locator (URL) in a merchant web page, the merchant web page associated with a transaction; download, by an operating system (OS) executing on the processor, an application from an application server based on the URL, wherein the URL is directed to the application at the application server; identify, by the application, a plurality of financial institution applications installed on the system; select, by the application, a first financial institution application of the plurality of financial institution applications based on a respective score for each financial institution application, wherein the first financial institution application is associated with a first financial institution, wherein the respective scores are computed b
using the card verification value [CVV] associated with the card · CPC title
Software deployment · CPC title
Contactless payments by cards · CPC title
insuring higher security of transaction · CPC title
One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.