VERIFYING IDENTITY THROUGH USE OF AN INTEGRATED RISK ASSESSMENT AND MANAGEMENT SYSTEM

• US 20120109802A1
• Filed: 02/28/2011
• Published: 05/03/2012
• Est. Priority Date: 10/29/2010
• Status: Abandoned Application

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Griffin, Maura Louise, Harman, Mary Palmer, Stigler, Teresa Hegdahl, Turner, Donna Dee, Shiflet, Robert
• Application Number:
  US13/036,926
• Publication Number:
  US 20120109802A1
• Time in Patent Office: Days
• US Class Current: 705/35
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/08 Insurance

Abstract

Embodiments of the present invention relate to systems, apparatus, methods and computer program products for integrated risk management. More specifically, embodiments of the present invention provide for identity verification based, at least in part, on comparing transaction data received from multiple financial institutions to data associated with a current financial transactions, such as type of transaction, transaction amount or the like. The transaction data provides for basing identity verification on how a customer, a counterparty or both previously transacted, in that transaction patterns can be identified to understanding who the transacting customer or counterparty is. In additional embodiments the identity verification may be based, at least in part on other data, such as financial institution relationship data, non-financial institution transaction and/or relationship data, customer/counterparty data or the like.

Claims

1. An apparatus for identity verification, the apparatus comprising:

a computing platform including at least one processor and a memory;

a risk database stored in the memory and configured to receive and store financial institution data, from a plurality of financial institutions, wherein the financial institution data includes transaction data; and

an identity verification routine stored in the memory, executable by the processor and configured to receive an identity verification request, determine if one or more identities associated with the request are verifiable based, at least in part, on the transaction data in the risk database, and communicate an identity verification response.

2. The apparatus of claim 1, wherein the identity verification routine is further configured to receive the identity verification request, wherein the identity verification request is requesting identity verification for a customer, a counterparty or both the customer and counterparty involved in a financial transaction.

3. The apparatus of claim 2, wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on how the customer, the counterparty or both the customer and counterparty previously transacted as determined from the transaction data.

4. The apparatus of claim 1, wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the transaction data in the database and a type of financial transaction associated with the request.

5. The apparatus of claim 1, wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the transaction data in the database and an amount of a financial transaction associated with the request.

6. The apparatus of claim 1, wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on identifiable transaction patterns in the transaction data.

7. The apparatus of claim 1, wherein the risk database is further configured to receive and store the financial institution data, from the plurality of financial institutions, wherein the financial institution data includes financial relationship data and wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the financial relationship data.

8. The apparatus of claim 1, wherein the risk database is further configured to receive and store non-financial institution data from one or more non-financial institutions, wherein the non-financial institution data includes non-financial institution transaction data and wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the non-financial institution transaction data.

9. The apparatus of claim 1, wherein the risk database is further configured to receive and store non-financial institution data from one or more non-financial institutions, wherein the non-financial institution data includes non-financial institution relationship data and wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the non-financial institution relationship data.

10. The apparatus of claim 9, wherein the risk database is further configured to receive and store non-financial institution data from one or more non-financial institutions, wherein the non-financial institution data includes one or more of merchant relationship data, health care organization relationship data, government agency relationship data, social network relationship data, or communication services relationship data.

11. The apparatus of claim 1, wherein the risk database is further configured to receive and store one or more of customer data or counterparty data, and wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the customer data or counterparty data.

12. The apparatus of claim 11, wherein the customer data or counterparty data includes computing device identifying data and wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the computing device identifying data.

13. The apparatus of claim 11, wherein the customer data or counterparty data includes biometric data and wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the biometric data.

14. The apparatus of claim 1, wherein the customer data or counterparty includes customer demographics data or counterparty demographics data and wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the customer demographics data or counterparty demographics data.

15. The apparatus of claim 1, wherein the identity verification routine is further configured to determine if one or more identities are verifiable based, at least in part, on a current geographic location of the parties associated with the one or more identities.

16. The apparatus of claim 1, wherein the risk database is further configured to receive negative file data and wherein the identity verification routine is further configured to determine if the one or more identities are verifiable based, at least in part, on the negative file data.

17. The apparatus of claim 1, wherein the identity verification routine is further configured to generate and initiate communication of an identity contradiction alert based on a failure of an identity to be verified.

18. The apparatus of claim 17, wherein the identity verification routine is further configured to generate and initiate communication of the identity contradiction alert to one or more of financial institutions, non-financial institutions or customers.

19. A method for identity verification, the method comprising:

receiving, at a risk database stored in computing device memory, financial institution data from a plurality of financial institutions, including transaction data;

receiving, via a computing device, an identity verification request;

determining, via a computing device processor, if one or more identities associated with the request are verifiable based, at least in part, on the transaction data in the risk database; and

communicating, via a computing device, an identity verification response based on a result of the determination.

20. The method of claim 19, wherein receiving the identity verification request further comprises receiving, via the computing device, the identity verification request, wherein the identity verification request is requesting identity verification for a customer, a counterparty or both the customer and counterparty involved in a financial transaction.

21. The method of claim 20, wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on how the customer, the counterparty or both the customer and counterparty previously transacted as determined from the transaction data.

22. The method of claim 19, wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the transaction data in the database and a type of financial transaction associated with the request.

23. The method of claim 19, wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the transaction data in the database and an amount of a financial transaction associated with the request.

24. The method of claim 19, wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on identifiable transaction patterns in the transaction data.

25. The method of claim 19, wherein receiving the financial institution data further comprises receiving, at the risk database stored in computing device memory, the financial institution data, from the plurality of financial institutions, wherein the financial institution data includes financial relationship data and determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the financial relationship data.

26. The method of claim 19, wherein receiving the financial institution data further comprises receiving, at the risk database stored in computing device memory, non-financial institution data from one or more non-financial institutions, wherein the non-financial institution data includes non-financial institution transaction data and wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the non-financial institution transaction data.

27. The method of claim 19, wherein receiving the financial institution data further comprises receiving, at the risk database stored in computing device memory, non-financial institution data from one or more non-financial institutions, wherein the non-financial institution data includes non-financial institution relationship data and wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the non-financial institution relationship data.

28. The method of claim 27, wherein receiving the financial institution data further comprises receiving, at the risk database stored in computing device memory, non-financial institution data from one or more non-financial institutions, wherein the non-financial institution data includes one or more of merchant relationship data, health care organization relationship data, government agency relationship data, social network relationship data, or communication services relationship data.

29. The method of claim 19, wherein receiving the financial institution data further comprises receiving, at the risk database stored in computing device memory, one or more of customer data or counterparty data, and wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the customer data or counterparty data.

30. The method of claim 29, wherein receiving the financial institution data further comprises receiving, at the risk database stored in computing device memory, the customer data or counterparty data including computing device identifying data and wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the computing device identifying data.

31. The method of claim 29, wherein receiving the financial institution data further comprises receiving, at the risk database stored in computing device memory, the customer data or counterparty data including biometric data and wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the biometric data.

32. The method of claim 29, wherein receiving the financial institution data further comprises receiving, at the risk database stored in computing device memory, the customer data or counterparty data including customer demographics data or counterparty demographics data and wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the customer demographics data or counterparty demographics data.

33. The method of claim 19, wherein determining further comprises determining, via the computing device processor, if one or more identities are verifiable based, at least in part, on a current geographic location of the parties associated with respective identities.

34. The method of claim 19, wherein receiving the financial institution data further comprises receiving, at the risk database stored in computing device memory, negative file data and wherein determining further comprises determining, via the computing device processor, if the one or more identities are verifiable based, at least in part, on the negative file data.

35. The method of claim 19, further comprising generating and initiating communication of, via a computing device processor, an identity contradiction alert based on a failure of an identity to be verified.

36. The method of claim 35, wherein generating and initiating further comprises generating and initiating communication of, via a computing device processor, the identity contradiction alert to one or more of financial institutions, non-financial institutions or customers.

37. A computer program product comprising:

a computer-readable medium comprising;

a first set of codes for causing a computer to receive financial institution data from a plurality of financial institutions, including transaction data;

a second set of codes for causing a computer to receive an identity verification request;

a third set of codes for causing a computer to determine if one or more identities associated with the request are verifiable based, at least in part, on the transaction data in the risk database; and

a fourth set of codes for causing a computer to communicate an identity verification response based on a result of the determination.

38. The computer program product of claim 37, wherein the second set of codes is further configured to cause the computer to receive the identity verification request, wherein the identity verification request is requesting identity verification for a customer, a counterparty or both the customer and counterparty involved in a financial transaction.

39. The computer program product of claim 38, wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on how the customer, the counterparty or both the customer and counterparty previously transacted as determined from the transaction data.

40. The computer program product of claim 37, wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the transaction data in the database and a type of financial transaction associated with the request.

41. The computer program product of claim 37, wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the transaction data in the database and an amount of a financial transaction associated with the request.

42. The computer program product of claim 37, wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on identifiable transaction patterns in the transaction data.

43. The computer program product of claim 37, wherein the first set of codes is further configured to cause the computer to receive the financial institution data, from the plurality of financial institutions, wherein the financial institution data includes financial relationship data and wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the financial relationship data.

44. The computer program product of claim 37, wherein the first set of codes is further configured to cause the computer to receive non-financial institution data from one or more non-financial institutions, wherein the non-financial institution data includes non-financial institution transaction data and wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the non-financial institution transaction data.

45. The computer program product of claim 37, wherein the first set of codes is further configured to cause the computer to receive non-financial institution data from one or more non-financial institutions, wherein the non-financial institution data includes non-financial institution relationship data and wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the non-financial institution relationship data.

46. The computer program product of claim 45, wherein the first set of codes is further configured to cause the computer to receive non-financial institution data from one or more non-financial institutions, wherein the non-financial institution data includes one or more of merchant relationship data, health care organization relationship data, government agency relationship data, social network relationship data, or communication services relationship data.

47. The computer program product of claim 37, wherein the first set of codes is further configured to cause the computer to receive one or more of customer data or counterparty data, and wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the customer data or counterparty data.

48. The computer program product of claim 47, wherein the first set of codes is further configured to cause the computer to receive the customer data or counterparty data including computing device identifying data and wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the computing device identifying data.

49. The computer program product of claim 47, wherein the first set of codes is further configured to cause the computer to receive the customer data or counterparty data including biometric data and wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the biometric data.

50. The computer program product of claim 47, wherein the first set of codes is further configured to cause the computer to receive the customer data or counterparty data including customer demographics data or counterparty demographics data and wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the customer demographics data or counterparty demographics data.

51. The computer program product of claim 37, wherein the third set of codes is further configured to cause the computer to determine if one or more identities are verifiable based, at least in part, on a current geographic location of the parties associated with respective identities.

52. The computer program product of claim 37, wherein the first set of codes is further configured to cause the computer to receive negative file data and wherein the third set of codes is further configured to cause the computer to determine if the one or more identities are verifiable based, at least in part, on the negative file data.

53. The computer program product of claim 37, further comprising a fifth set of codes for causing a computer to generate and initiate communication of an identity contradiction alert based on a failure of an identity to be verified.

54. The computer program product of claim 53, wherein the fifth set of codes is further configured to cause the computer to generate and initiate communication of the identity contradiction alert to one or more of financial institutions, non-financial institutions or customers.