Transaction token issuing authorities
US-9639837-B2 · May 2, 2017 · US
US10134031B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10134031-B2 |
| Application number | US-201715585006-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 2, 2017 |
| Priority date | Apr 9, 2010 |
| Publication date | Nov 20, 2018 |
| Grant date | Nov 20, 2018 |
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, apparatus, processes, computer program code and means for conducting transactions are described which allow a first party to a transaction to identify a second party to a transaction.
Opening claim text (preview).
The invention claimed is: 1. A system, comprising: a non-transitory memory storing instructions; and one or more hardware processors coupled to the non-transitory memory and configured to execute the instructions to cause the system to perform operations comprising: receiving an encoded token; decoding the encoded token to obtain token data and to obtain identification of a server to use in completing a transaction; providing the token data to a device; receiving, from the server and after a process transaction request is received by the server based on the identification, an electronic message identifying one or more payment accounts of a user available to be used for the transaction, wherein the process transaction request includes a) the token data captured by the device and associated with transaction information and b) the transaction information; selecting, based on input from the user, one of the one or more payment accounts; and transmitting the selected one of the one or more payment accounts to the server for completing the transaction. 2. The system of claim 1 , wherein the identification is based on a Uniform Resource Locator (URL) in the encoded token or based on a Uniform Resource Indicator (URI) in the encoded token. 3. The system of claim 1 , wherein: the receiving the encoded token, the decoding, the providing, the receiving the electronic message, the selecting, and the transmitting are performed by a mobile device of the user; and the transaction is completed without storing the one or more payment accounts on the mobile device. 4. The system of claim 1 , wherein the token data further comprises a token value associated with the transaction. 5. The system of claim 1 , wherein the server is associated with one of a plurality of different providers that perform transaction processing. 6. The system of claim 1 , wherein the encoded token is generated as part of initiating the transaction between two parties. 7. The system of claim 1 , wherein different encoded tokens are generated for different transactions. 8. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause performance of operations comprising: receiving an encoded token; decoding the encoded token to obtain token data and to obtain identification of a server to use in completing a transaction; providing the token data to a device of another party; receiving, from the server and after a process transaction request is received by the server based on the identification, an electronic message identifying one or more payment accounts of a user available to be used for the transaction, wherein the process transaction request includes a) the token data captured by the device and associated with transaction information and b) the transaction information; selecting, based on input from the user, one of the one or more payment accounts; and transmitting the selected one of the one or more payment accounts to the server for completing the transaction. 9. The non-transitory machine-readable medium of claim 8 , wherein the identification is based on a Uniform Resource Locator (URL) in the encoded token or based on a Uniform Resource Indicator (URI) in the encoded token. 10. The non-transitory machine-readable medium of claim 8 , wherein: the receiving the encoded token, the decoding, the providing, the receiving the electronic message, the selecting, and the transmitting are performed by a mobile device of the user; and the transaction is completed without storing the one or more payment accounts on the mobile device. 11. The non-transitory machine-readable medium of claim 8 , wherein the token data further comprises a token value associated with the transaction. 12. The non-transitory machine-readable medium of claim 8 , wherein the server is associated with one of a plurality of different providers that perform transaction processing. 13. The non-transitory machine-readable medium of claim 8 , wherein the encoded token is generated as part of initiating a transaction between two parties. 14. The non-transitory machine-readable medium of claim 8 , wherein different encoded tokens are generated for different transactions. 15. A computer-implemented method for conducting a transaction involving multiple parties, comprising: receiving an encoded token; decoding the encoded token to obtain token data and to obtain identification of a server to use in completing a transaction; providing the token data for electronic capture by a merchant device; receiving, from the server and after a process transaction request is received by the server based on the identification, an electronic message identifying one or more payment accounts of a user available to be used for the transaction, wherein the process transaction request includes a) the token data captured by the merchant device and associated with transaction information b) the transaction information; selecting, based on input from the user, one of the one or more payment accounts; and transmitting the selected one of the one or more payment accounts to the server for completing the transaction. 16. The computer-implemented method of claim 15 , wherein the identification is based on a Uniform Resource Locator (URL) in the encoded token or is based on a Uniform Resource Indicator (URI) in the encoded token. 17. The computer-implemented method of claim 15 , wherein: the receiving the encoded token, the decoding, the providing, the receiving the electronic message, the selecting, and the transmitting are performed by a mobile device of the user; and the transaction is completed without storing the one or more payment accounts on the mobile device. 18. The computer-implemented method of claim 15 , wherein the token data further comprises a token value associated with the transaction. 19. The computer-implemented method of claim 15 , wherein the server is associated with one of a plurality of different providers that perform transaction processing. 20. The computer-implemented method of claim 15 , wherein different encoded tokens are generated for different transactions.
Identity check for transactions · CPC title
involving authentication · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.