SYSTEM AND METHOD TO MANAGE INFORMATION FOR CONDUCTING SECURE TRANSACTIONS
First Claim
1. A system for conducting secure electronic transactions, the system comprising:
- one or more physical processors;
storage media storing machine-readable instructions that cause the one or more physical processors;
to receive a transaction request comprising first transaction information from a first user;
to store at least some of the first transaction information;
to generate a system-generated code and associate the system-generated code with at least one of the stored transaction information and pre-existing first user information;
to transmit the system-generated code to the first user;
to receive a user-sent code from a second user with second transaction information;
to validate the user-sent code and determine any stored transaction information and pre-existing first user information associated with the user-sent code;
to cause an authorization decision to be rendered for a transaction associated with the stored transaction information and pre-existing first user information associated with the user-sent code and second transaction information; and
to transmit the authorization decision to at least one of the first user and the second user;
wherein the system-generated code does not contain any transaction method information and is at least one of time-limited, one-time use, and limited to use with a single transaction partner.
0 Assignments
0 Petitions
Accused Products
Abstract
In a secure electronic transaction method, a unique code associated with a payer and payer'"'"'s selected transaction method is generated, responsive to a request from the payer computing platform to conduct a transaction using that transaction method. A unique code received from a recipient is validated by attempting to match it with a stored unique code associated with a payer and payer'"'"'s selected transaction method. Information received from the payer, recipient, and/or a transaction authorization network is stored in electronic storage. The unique code associated with the payer does not contain any transaction method information and is at least one of time-limited, one-time use, and limited to use with a single transaction partner.
40 Citations
23 Claims
-
1. A system for conducting secure electronic transactions, the system comprising:
-
one or more physical processors; storage media storing machine-readable instructions that cause the one or more physical processors; to receive a transaction request comprising first transaction information from a first user; to store at least some of the first transaction information; to generate a system-generated code and associate the system-generated code with at least one of the stored transaction information and pre-existing first user information; to transmit the system-generated code to the first user; to receive a user-sent code from a second user with second transaction information; to validate the user-sent code and determine any stored transaction information and pre-existing first user information associated with the user-sent code; to cause an authorization decision to be rendered for a transaction associated with the stored transaction information and pre-existing first user information associated with the user-sent code and second transaction information; and to transmit the authorization decision to at least one of the first user and the second user; wherein the system-generated code does not contain any transaction method information and is at least one of time-limited, one-time use, and limited to use with a single transaction partner. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18)
-
-
19. A system for conducting secure electronic transactions, the system comprising:
-
one or more processors configured to execute computer program modules, the computer program modules comprising; a code generation module configured to generate a unique code associated with a payer and payer'"'"'s selected transaction method, responsive to a request from the payer computing platform to conduct a transaction using that transaction method; a code validation module configured to validate a unique code received from a recipient by attempting to match it with a stored unique code associated with a payer and payer'"'"'s selected transaction method; an interface module configured to communicate with at least one of the payer, the recipient, and a transaction authorization network; a logging module configured to log in electronic storage at least one of information received from the payer, information received from the recipient, information received from the transaction authorization network, information generated by the code generation module, information generated by the code validation module, and information generated by the interface module; wherein the unique code associated with the payer does not contain any transaction method information and is at least one of time-limited, one-time use, and limited to use with a single transaction partner. - View Dependent Claims (20)
-
-
21. A system for conducting secure electronic transactions, the system comprising:
-
one or more physical processors; storage media storing machine-readable instructions that cause the one or more physical processors; to receive a transaction request comprising a selected transaction method from a first user; to generate a system-generated code and associate the system-generated code with the first user; to transmit the system-generated code to the first user; to receive a user-sent code from a second user; to determine that the user-sent code is associated with the first user; and to cause an authorization decision to be rendered for a transaction associated with the first user, the selected transaction method, and identification information associated with the selected transaction method; wherein the system-generated code does not contain any transaction method information and is at least one of time-limited, one-time use, and limited to use with a single transaction partner.
-
-
22. A secure electronic transaction method, comprising:
-
generating a unique code associated with a payer and payer'"'"'s selected transaction method, responsive to a request from the payer computing platform to conduct a transaction using that transaction method; validating a unique code received from a recipient by attempting to match it with a stored unique code associated with a payer and payer'"'"'s selected transaction method; communicating with at least one of the payer, the recipient, and a transaction authorization network; logging in electronic storage at least one of information received from the payer, information received from the recipient, information received from the transaction authorization network, information generated by generating the unique code associated with the payer, information generated by validating the unique code received from the recipient, and information generated by communicating; wherein the unique code associated with the payer does not contain any transaction method information and is at least one of time-limited, one-time use, and limited to use with a single transaction partner. - View Dependent Claims (23)
-
Specification