IP Library Granted Patent US 10,134,031
Granted Patent B2
US 10,134,031 · App. 15/585,006 · Granted Nov 20, 2018

Transaction token issuing authorities

Inventor: Kevin Laracey (Natick, MA)
Assignee: PAYPAL, INC.
G06Q20/3674G06Q20/4014
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,134,031
App. No.
15/585,006
Granted
Nov 20, 2018
Kind
B2
Abstract

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.

Claims (46)

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.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 26, 2017
From: LARACEY, KEVIN
To: PAYDIANT, INC.
Reel/Frame 043103/0525 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 26, 2017
From: PAYDIANT, LLC
To: PAYPAL, INC.
Reel/Frame 043103/0704 →
CHANGE OF NAME Recorded Jul 26, 2017
From: PAYDIANT, INC.
To: PAYDIANT, LLC
Reel/Frame 043345/0318 →
Continuity (10)
Continuation 14928690 · Oct 30, 2015
Continuation 14169067 · Jan 30, 2014
Continuation In Part 13768156 · Feb 15, 2013
Continuation In Part 13731348 · Dec 31, 2012
Continuation In Part 12846911 · Jul 30, 2010
Continuation 12846911 · Jul 30, 2010
Provisional Application 61758543 · Jan 30, 2013
Provisional Application 61362567 · Jul 8, 2010
Provisional Application 61322477 · Apr 9, 2010
Related Publication 20170236118A1 · Aug 17, 2017
Cited By (3)
US 12,299,660 US 12,561,674 US 12,705,605