Secure authentication and payment system

• US 10,127,550 B2
• Filed: 08/22/2017
• Issued: 11/13/2018
• Est. Priority Date: 07/06/2001
• Status: Expired due to Term

• Current Assignee: Aliaswire, Inc.
• Original Assignee: Aliaswire, Inc.
• Inventors: Mohsenzadeh, Hossein
• Primary Examiner(s): Hamilton, Lalita M
• Application Number:
  US15/683,359
• Publication Number:
  US 20170352032A1
• Time in Patent Office: 448 Days
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/16 Payments settled via telecommunication systems
• CPC Class Codes: G06Q 20/305 using wired telephone networks
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]

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.

Claims

1. A server comprising:

a processor, the processor including one or more program modules configured to;

send a message to a client device, wherein the message provides instructions for a target to access the server to receive payment;

receive one or more messages from the client device, the one or more messages including an alias stored on the server to the target, a transaction identifier assigned by the server identifying a transaction, and a target financial account information;

authenticate the one or more messages from the client device by searching for a stored alias and a stored transaction identifier associated with the alias in a database that matches the alias and transaction identifier in the one or more messages; and

in response to authentication of the one or more messages from the client device, provide instructions to transfer a payment amount from an originator financial account to a target financial account associated with the target financial account information included in the one or more messages.

2. The server of claim 1, wherein the one or more program modules are further configured to store and link the target financial account information to the stored alias in the database.

3. The server of claim 2, wherein the one or more program modules are further configured to:

receive the alias assigned by the server, a subsequent transaction identifier identifying a subsequent transaction, and a subsequent payment amount for the subsequent transaction;

retrieve stored target financial account information associated with the received alias from the database; and

provide instructions to transfer the subsequent payment amount from the originator financial account to the target financial account associated with the stored target financial account information.

4. The server of claim 3, wherein the subsequent transaction identifier is selected from the group consisting of an email address, a telephone number, a numeric string, an alphanumeric string, a hash identifier, a uniform resource locator (URL), a coded URL, a coded string, and a combination thereof.

5. The server of claim 3, wherein the subsequent transaction identifier is embedded in a coded uniform resource locator (URL).

6. The server of claim 1, wherein the stored alias is an email address.

7. The server of claim 1, wherein the stored alias is a telephone number.

8. The server of claim 1, wherein the transaction identifier is selected from the group consisting of an email address, a telephone number, a numeric string, an alphanumeric string, a hash identifier, a uniform resource locator (URL), a coded URL, coded string, or a combination thereof.

9. The server of claim 1, wherein the transaction identifier is embedded in a coded uniform resource locator (URL).

10. A server comprising:

a processor, the processor including one or more program modules configured to;

send a message to a client device using an alias previously assigned by the processor and stored in a database, wherein the message provides instructions for a target to access the server to receive a payment amount for a transaction and the message includes a transaction identifier generated for the transaction;

receive from the client device, one or more messages including at least an alias and the transaction identifier from the target for the transaction; and

authenticate the one or more messages from the client device by searching for the previously stored alias and the generated transaction identifier associated with the alias in the database that matches the received alias and the received transaction identifier in the one or more messages,

wherein the alias identifies a party to the transaction and the transaction identifier identifies the transaction.

11. The server of claim 10, wherein the one or more messages is selected from the group consisting of a text message, an email message, a message initiated from a web browser, a message initiated from a mobile application, a message initiated from an interactive voice response system, a wireless network message, an Internet Protocol type message, a system message, a peer to peer message, a computer originated message, and a combination thereof.

12. A server comprising:

a processor, the processor including one or more program modules configured to;

send a message to a client device using an alias and transaction identifier for a transaction stored in a database of the server, wherein the message provides instructions for the target to access the server to receive a payment amount for the transaction;

receive one or more messages from the client device, the one or more messages including a received transaction identifier from the target; and

authenticate the one or more messages from the client device by searching for the stored transaction identifier in a database that matches the received transaction identifier in the one or more messages,

wherein the alias identifies a party to the transaction and the received transaction identifier and the stored transaction identifier identifies the transaction.

13. The server of claim 12, wherein the one or more messages is selected from the group consisting of a text message, an email message, a message initiated from a web browser, a message initiated from a mobile application, a message initiated from an interactive voice response system, a wireless network message, an Internet Protocol type message, a system message, a peer to peer message, a computer originated message, and a combination thereof.

14. The server of claim 12, wherein the one or more program modules are configured to:

determine whether the payment amount is above a threshold; and

in response to the payment amount being above a threshold, authenticating the message to be authenticated via a voiceprint previously stored in the database.

15. The server of claim 12, wherein the one or more program modules are configured to:

in response to authenticating the one or more messages, provide instructions to another server to initiate transfer of the payment amount from an originator financial account to a target financial account.

16. The server of claim 15, wherein transferring the payment amount includes providing instructions to the another server to debit the payment amount from the originator financial account.

17. The server of claim 15, wherein transferring the payment amount includes crediting the payment amount to the target financial account.

18. The server of claim 12, wherein the one or more program modules are configured to:

receive one or more messages including the alias and a subsequent payment amount for a subsequent transaction;

retrieve previously stored information associated with the received alias from the database; and

provide instructions to transfer the subsequent payment amount from an originator financial account to a target financial account.

19. The server of claim 12, wherein the generated transaction identifier is selected from the group consisting of an email address, a telephone number, a numeric string, an alphanumeric string, a hash identifier, a uniform resource locator (URL), a coded URL, a coded string, and a combination thereof.

20. The server of claim 19, wherein the generated transaction identifier is embedded in a coded uniform resource locator (URL).