Secure authentication and payment system
DCFirst Claim
Patent Images
1. A method of conducting a financial transaction between an originator and a target, comprising:
- authenticating that the originator is authorized to conduct the said financial transaction based on credentials previously stored in an authorized user database;
receiving at a server one or more messages that include at least an alias and a payment amount;
retrieving target financial account information previously stored from a database based on the said alias;
providing instructions to transfer the payment amount from an originator financial account to a target financial account by the server based on target financial account information identified by the alias.
3 Assignments
Litigations
0 Petitions
Accused Products
Abstract
A transaction and payment and processing system securely conducts transactions over the public telephone network. The transactions may be between and among entities of any type such as individuals, merchants, utilities, banks, etc. Nothing more than access to a telephone is required after initial registration of a user.
174 Citations
149 Claims
-
1. A method of conducting a financial transaction between an originator and a target, comprising:
-
authenticating that the originator is authorized to conduct the said financial transaction based on credentials previously stored in an authorized user database; receiving at a server one or more messages that include at least an alias and a payment amount; retrieving target financial account information previously stored from a database based on the said alias; providing instructions to transfer the payment amount from an originator financial account to a target financial account by the server based on target financial account information identified by the alias. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 34, 101)
-
-
31. A method of conducting financial transactions, comprising:
-
sending a message to a target from a server, wherein the message provides instructions for the target to access the server to receive payment for a first transaction; receiving an alias, a transaction identifier, and a target financial account information at a server; authenticating by matching the received alias and received transaction identifier with a stored alias and a stored transaction identifier stored in a database, providing instructions by the server to transfer a payment amount from an originator financial account to a target financial account based on the target financial account information. - View Dependent Claims (32, 33, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70)
-
-
71. A method of conducting financial transactions, comprising:
-
sending a message to a target from a server using a first alias, wherein the message provides instructions for the target to access the server to receive a payment amount, the message includes a first transaction identifier for a first transaction; receiving, at the server, at least a second alias, and a second transaction identifier for the first transaction; searching for a previously stored first alias and a previously stored first transaction identifier in a database based a second alias, and a second transaction identifier; authenticating by matching the second alias and second transaction identifier with the previously stored first alias and the previously stored first transaction identifier. - View Dependent Claims (72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 102, 103, 104, 105, 106, 107, 108, 109, 110)
-
-
111. A method of conducting financial transactions, comprising:
-
sending a message to a target from a server using an alias for the target, wherein the message provides instructions for the target to access the server to receive a payment amount and the message includes a first transaction identifier for a first transaction; receiving, at the server, a second transaction identifier for the first transaction; searching for the previously stored first transaction identifier in a database based on the second transaction identifier; authenticating by at least matching the second transaction identifier with the first transaction identifier in the database. - View Dependent Claims (112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149)
-
Specification