Secure authentication and payment system

• US 9,530,129 B2
• Filed: 05/19/2015
• Issued: 12/27/2016
• Est. Priority Date: 10/25/2006
• Status: Active Grant

• Current Assignee: Leading Software Limited
• Original Assignee: Payfont Limited
• Inventors: Lanc, David
• Primary Examiner(s): Robinson, Kito R
• Application Number:
  US14/716,519
• Publication Number:
  US 20150254661A1
• Time in Patent Office: 588 Days
• Field of Search: 705/44
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/325 using wireless networks
• CPC Class Codes: G06Q 20/3255 using mobile network messaging services for payment, e.g. SMS
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• 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/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 20/409 Device specific authentication in transaction processing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

The present invention provides a service for allowing secure financial transactions to be carried out, the service involving authenticating a user'"'"'s identity and/or status as part of a financial transaction with another party and in the event that the user is authenticated arranging for the transaction to be completed without revealing the user'"'"'s financial details and/or other personal details to that other party. Authentication data and transaction data may be communicated over any suitable communications channel(s). The invention provides a trusted authentication and payment environment that protects a user'"'"'s financial details, but allows them to be securely authenticated and arranges for transactions to be fulfilled, while providing other parties with reassurance that transactions will be completed. In this way, fraud and theft due to misappropriation of financial details can be minimized.

Claims

1. A computer-implemented method for facilitating electronic transactions between a first party and one or more second parties, comprising:

establishing a first relationship with the first party, the first relationship defining a dynamically controllable and selectable selection of;

at least one user-specified and user-specific authentication method selected from a plurality of stored authentication methods of different types operating on an authentication device over a plurality of different communication channels and useable to authenticate the identity of the first party in a non-predictable and anonymous manner; and

a preferred electronic communication channel selected from one or more suitable communication channels for completion of one or more of the plurality of stored authentication method using the authentication device;

establishing a second relationship with at least one of said one or more second parties;

storing one or more associations between payment methods and transactions, the one or more associations specified by the first party; and

upon receiving an authentication request related to a transaction with one or more of the second parties;

controlling the authentication device to validate the identity of the first party by presenting the first party with at least one of the previously selected user-specified and user-specific stored authentication methods on the authentication device over the preferred communication channel; and

upon successful authentication using the at least one of the previously selected user-specified and user-specific stored authentication methods on the authentication device over the preferred communication channel, initiating the transaction with said one or more second parties using one or more payment methods associated with the transaction.

2. The method of claim 1, wherein the associations associate payment methods with types of transactions.

3. The method of claim 2, wherein the associations associate payment methods with a particular second party.

4. The method of claim 1, further comprising:

upon receiving an authentication request related to the transaction and prior to the initiating step, validating the transaction against one or more parameters.

5. The method of claim 4, wherein the one or more parameters include one or more selected from the group consisting of:

payment type, payment value, transaction frequency, transaction velocity, bulk spend within a period, credit risk, and fraud risk.

6. The method of claim 1, wherein said transaction comprises a purchase of goods or services.

7. The method of claim 1, wherein said transaction comprises a disbursement of cash from a cash disbursement mechanism.

8. The method of claim 1, wherein said transaction comprises a money transfer.

9. The method of claim 1, wherein the transaction includes executing a first financing method for the transaction.

10. The method of claim 1, wherein the entire transaction is completed without identifying any financial information of the consumer to the first of said one or more second parties.

11. The method of claim 1, wherein the plurality of stored authentication methods of different types include interactive voice recognition via a voice telecommunications channel.

12. The method of claim 11, wherein the interactive voice recognition is directed to a predetermined telecommunications device.

13. The method of claim 1, wherein the plurality of stored authentication methods of different types include a fingerprint-based authentication method implemented on a device including both a fingerprint reader and a mobile telecommunications apparatus.

14. The method of claim 1, wherein the plurality of stored authentication methods are not associated with the transaction.

15. The method of claim 1, wherein the plurality of stored authentication methods are not prescribed by the second party involved in the transaction.

16. The method of claim 1, wherein information about the first party is not transmitted until the second party is ready to transfer possession of a subject of the transaction to the first party.

17. The method of claim 16, wherein the information about the first party includes a ship-to address.

18. The method of claim 1, wherein the plurality of stored authentication methods of different types operate on different communication channels from the transaction.

19. The method of claim 1, wherein at least one of the plurality of stored authentication methods utilize one or more selected from the group consisting of:

IP protocol data and device identity data.