Multiple tokenization for authentication
US-9280765-B2 · Mar 8, 2016 · US
US10839374B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10839374-B2 |
| Application number | US-201715610283-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 31, 2017 |
| Priority date | Jul 29, 2011 |
| Publication date | Nov 17, 2020 |
| Grant date | Nov 17, 2020 |
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.
Embodiments of the invention are directed to methods, a computer-readable medium, servers and systems for enabling merchants to pass payment tokens, instead of actual payment information, to third party HOPs and SOPs. This, for example, enables a merchant to charge a consumer, such as on a recurring basis or for a one-off purchase, without having the consumer enter payment information each time and without the merchant actually having to handle payment information. As such, merchants can avoid costs and responsibilities associated with handling and storing consumer payment data, while at the same time it also gives merchants the benefit of engaging in purchase transactions with consumers without requiring that the consumers reenter payment data each time they want to make a purchase.
Opening claim text (preview).
What is claimed is: 1. A method for processing a transaction between a user computer of a user and a merchant computer of a merchant, the method comprising: receiving, by a service provider server computer, a transaction request that includes order information in connection with the transaction between the user computer and the merchant computer, when the transaction request is received by the service provider server computer: rendering, by the service provider service computer, a hosted page to be displayed on the user computer; receiving, by the service provider server computer, user information from the user computer over a network communication channel via the hosted page displayed on; processing, by the service provider server computer, the transaction between the user computer and the merchant computer using the user information; tokenizing, by the service provider server computer, the user information, the tokenizing including: creating a unique token representing the user information, and storing the user information and the token at a database; and sending, by the service provider server computer, a copy of the token to the merchant computer, wherein the sending causes the merchant computer to submit the copy of the token in a future transaction between the merchant computer and the user computer without requiring the user to provide the user information; receiving, by the service provider server computer from the merchant computer, the transaction request further for the future transaction including the copy of the token; identifying, by the service provider server computer, the token in the database that matches the copy of the token provided by the merchant computer; obtaining, by the service provider server computer, the user information associated with the token from the database instead of receiving the user information from the user computer via another hosted page displayed on the user computer; and responsive to the obtaining, processing, by the service provider server computer, the transaction using the user information associated with the token. 2. The method of claim 1 wherein the merchant computer generates a hash of the order information and transmits the hash along with the order information. 3. The method of claim 2 further comprising: verifying the hash to ensure that the order information was not tampered with during transmission from the merchant computer. 4. The method of claim 1 wherein the user information bypasses the merchant computer. 5. The method of claim 1 , wherein the rendering further comprises: rendering, by the service provider server computer, the hosted page on behalf of the merchant, the hosted page displaying at least a portion of the order information, the hosted page comprising an information entry section for collecting user information; and providing, by the service provider server computer, the rendered hosted page to the user computer, wherein the rendered hosted page is displayed on the user computer. 6. The method of claim 5 further comprising: obtaining hosted page configurations designated by the merchant computer, wherein the hosted page is rendered in accordance with the hosted page configurations. 7. The method of claim 5 wherein the user information is received from the user computer via the information entry section of the hosted page. 8. A system, comprising: a processor; a memory device including instructions that, when executed by the processor, cause the processor to: receive a transaction request that includes order information in connection with a transaction between a user computer of a user and a merchant computer of a merchant, when the transaction request is received: render a hosted page to be displayed on the user computer; receive user information from the user computer over a network communication channel via the hosted page displayed on the user computer process the transaction between the user computer and the merchant computer using the user information; tokenize the user information, the tokenizing including: creating a unique token representing the user information, and storing the user information and the token at a database; and send a copy of the token to the merchant computer, wherein the sending causes the merchant computer to submit the copy of the token in a future transaction between the merchant computer and the user computer without requiring the user to provide the user information; receive, from the merchant computer, the transaction request for the future transaction including the copy of the token: identify the token in the database that matches the copy of the token provided by the merchant computer; obtain the user information associated with the token from the database instead of receiving the user information from the user computer via another hosted page displayed on the user computer; and responsive to the obtaining, process the transaction using the user information associated with the token. 9. The system of claim 8 wherein the merchant computer generates a hash of the order information and transmits the hash along with the order information. 10. The system of claim 9 wherein the memory device further includes instructions that, when executed by the processor, cause the processor to: verify the hash to ensure that the order information was not tampered with during transmission from the merchant computer. 11. The system of claim 8 wherein the user information bypasses the merchant computer. 12. The system of claim 8 wherein the memory device further includes instructions that, when executed by the processor, cause the processor to: render the hosted page on behalf of the merchant, the hosted page displaying at least a portion of the order information, the hosted page comprising an information entry section for collecting user information; and provide the rendered hosted page to the user computer, wherein the rendered hosted page is displayed on the user computer. 13. The system of claim 12 wherein the memory device further includes instructions that, when executed by the processor, cause the processor to: obtain hosted page configurations designated by the merchant computer, wherein the hosted page is rendered in accordance with the hosted page configurations. 14. The system of claim 12 wherein the user information is received from the user computer via the information entry section of the hosted page.
with the personal data of a user · CPC title
using electronic wallets or electronic money safes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.