Inspecting event indicators

• US 20070265807A1
• Filed: 05/10/2006
• Published: 11/15/2007
• Est. Priority Date: 05/10/2006
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Weir, Robert, Schimpf, Brian, Stern, Edith, Willner, Barry
• Granted Patent: US 10,152,712 B2
• Time in Patent Office: Days
• US Class Current: 702/188
• 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/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• 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/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G07F 7/1016 Devices or methods for securing the PIN and other transaction-data, e.g. by encryption arrangements for secret communication, see H04L9/00

Abstract

A user inspects at least one indicator of an event. The user enables a token corresponding to an account of an aggregating entity to be received by a transaction entity and identifies at least one type of event of interest to be reported by the transaction entity to the aggregating entity. The user obtains and inspects at least one indicator from the account of the aggregating entity, where each obtained indicator is adapted to be created by the aggregating entity based upon an event message received from the transaction entity. The event message comprises the token, which is adapted to be used by the aggregating entity to identify the account and the event message corresponds to an occurrence of an event of at least one type of event of interest to be reported by the transaction entity to the aggregating entity.

Claims

1. A computer implemented method for inspecting at least one indicator of an event, comprising:

enabling a token to be received by a transaction entity, said token corresponding to an account of an aggregating entity;

identifying at least one type of event of interest to be reported by said transaction entity to said aggregating entity;

obtaining at least one indicator from said account of said aggregating entity, said at least one indicator adapted to be created by said aggregating entity based upon an event message received from said transaction entity; and

inspecting said at least one indicator;

wherein;

said event message comprises said token, which is adapted to be used by said aggregating entity to identify said account; and

said event message corresponds to an occurrence of an event of at least one type of event of interest to be reported by said transaction entity to said aggregating entity.

2. The method according to claim 1, wherein said enabling a token to be received by a transaction entity comprises obtaining at least one token from either said aggregating entity or a third party, and distributing at least one token to said transaction entity.

3. The method according to claim 1, wherein said enabling a token to be received by a transaction entity comprises allowing said transaction entity to receive at least one token from either said aggregating entity or a third party.

4. The method according to claim 1, wherein said enabling a token to be received by a transaction entity comprises generating at least one token based upon information received from said aggregating entity and distributing at least one token to said transaction entity.

5. The method according to claim 1, wherein said identifying at least one type of event of interest to be reported by said transaction entity to said aggregating entity comprises identifying at least one type of event of interest from a list provided by at least one of said transaction entity and said aggregating entity.

6. The method according to claim 1, wherein said obtaining at least one indicator from said account of said aggregating entity comprises logging into a web site made available by said aggregating entity and performing at least one of viewing, filtering, querying, searching, sorting, printing, downloading and deleting said at least one indicator.

7. The method according to claim 1, wherein said inspecting said at least one indicator comprises inspecting a description that does not directly provide the identity of parties associated with said event.

8. The method according to claim 1, wherein said inspecting said at least one indicator comprises inspecting a description of a transaction that does not directly provide account information associated with said transaction or an amount of said transaction.

9. The method according to claim 1, wherein said inspecting said at least one indicator comprises inspecting said at least one indicator to identify identity fraud.

10. The method according to claim 1, wherein said inspecting said at least one indicator comprises inspecting said at least one indicator for monitoring events related to persons entrusted to transact on behalf of a user of said aggregating entity.

11. The method according to claim 10, wherein said user comprises a business and said persons entrusted to transact on behalf of said user comprise employees of said business.

12. The method according to claim 1, further comprising providing at least one token to at least one additional transaction entity, wherein:

each of said at least one additional transaction entity is adapted to send event messages to said aggregating entity upon the occurrence of a specified type of event, each event message comprising at least one token, said aggregating entity is adapted to aggregate at least one indicator corresponding to said occurrence of said specified type of event with any previous indicators in said account based upon said token received with said event message.

13. The method according to claim 1, wherein said transaction entity comprises a bank or a creditor.

14. A computer system to inspect at least one indicator of an event, comprising:

a module to enable a token to be received by a transaction entity, said token corresponding to an account of an aggregating entity;

a module to identify at least one type of event of interest to be reported by said transaction entity to said aggregating entity;

a module to obtain at least one indicator from said account of said aggregating entity, said at least one indicator adapted to be created by said aggregating entity based upon an event message received from said transaction entity; and

a module to inspect said at least one indicator;

wherein;

said event message comprises said token, which is adapted to be used by said aggregating entity to identify said account; and

said event message corresponds to an occurrence of an event of at least one type of event of interest to be reported by said transaction entity to said aggregating entity.

15. The system according to claim 14, wherein said module to enable a token to be received by a transaction entity obtains at least one token from either said aggregating entity or a third party, and distributes at least one token to said transaction entity.

16. The system according to claim 14, wherein said module to enable a token to be received by a transaction entity enables said transaction entity to receive at least one token from either said aggregating entity or a third party.

17. The system according to claim 14, wherein said module to enable a token to be received by a transaction entity generates at least one token based upon information received from said aggregating entity and distributes at least one token to said transaction entity.

18. The system according to claim 14, wherein said module to identify at least one type of event of interest to be reported by said transaction entity to said aggregating entity identifies at least one type of event of interest from a list provided by at least one of said transaction entity and said aggregating entity.

19. The system according to claim 14, wherein said module to obtain at least one indicator from said account of said aggregating entity comprises a web browser adapted to log into a web site made available by said aggregating entity and to perform at least one of viewing, filtering, querying, searching, sorting, printing, downloading and deleting said at least one indicator.

20. The system according to claim 14, wherein said module to inspect said at least one indicator displays a description that does not directly provide the identity of parties associated with said event.

21. The system according to claim 14, wherein said module to inspect said at least one indicator displays a description of a transaction that does not directly provide account information associated with said transaction or an amount of said transaction.

22. The system according to claim 14, wherein said module to inspect said at least one indicator displays occurrences of events of financial transactions that are monitored to identify identity fraud.

23. The system according to claim 14, wherein said module to inspect said at least one indicator displays events related to persons entrusted to transact on behalf of a user of said aggregating entity.

24. The system according to claim 23, wherein said user comprises a business and said persons entrusted to transact on behalf of said user comprise employees of said business.

25. The system according to claim 14, wherein said module to enable a token to be received by a transaction entity provides at least one token to at least one additional transaction entity, wherein:

each of said at least one additional transaction entity is adapted to send event messages to said aggregating entity upon the occurrence of a specified type of event, each event messages comprising at least one token, said aggregating entity is adapted to aggregate at least one indicator corresponding to said occurrence of said specified type of event with any previous indicators in said account based upon said token received with said event message.

26. The system according to claim 14, wherein said transaction entity comprises a bank or a creditor.

27. A computer program product to inspect at least one indicator of an event, comprising:

a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code configured to enable a token to be received by a transaction entity, said token corresponding to an account of an aggregating entity;

computer usable program code configured to identify at least one type of event of interest to be reported by said transaction entity to said aggregating entity;

computer usable program code configured to obtain at least one indicator from said account of said aggregating entity, said at least one indicator adapted to be created by said aggregating entity based upon an event message received from said transaction entity; and

computer usable program code configured to inspect said at least one indicator;

wherein;

said event message comprises said token, which is adapted to be used by said aggregating entity to identify said account; and

said event message corresponds to an occurrence of an event of at least one type of event of interest to be reported by said transaction entity to said aggregating entity.

28. The computer program product according to claim 27, wherein said computer usable program code configured to enable a token to be received by a transaction entity obtains at least one token from either said aggregating entity or a third party, and distributes at least one token to said transaction entity.

29. The computer program product according to claim 27, wherein said computer usable program code configured to enable a token to be received by a transaction entity enables said transaction entity to receive at least one token from either said aggregating entity or a third party.

30. The computer program product according to claim 27, wherein said computer usable program code configured to enable a token to be received by a transaction entity generates at least one token based upon information received from said aggregating entity and distributes at least one token to said transaction entity.

31. The computer program product according to claim 27, wherein said computer usable program code configured to identify at least one type of event of interest to be reported by said transaction entity to said aggregating entity identifies at least one type of event of interest from a list provided by at least one of said transaction entity and said aggregating entity.

32. The computer program product according to claim 27, wherein said computer usable program code configured to obtain at least one indicator from said account of said aggregating entity comprises a web browser adapted to log into a web site made available by said aggregating entity and to perform at least one of viewing, filtering, querying, searching, sorting, printing, downloading and deleting said at least one indicator.

33. The computer program product according to claim 27, wherein said computer usable program code configured to inspect said at least one indicator displays a description that does not directly provide the identity of parties associated with said event.

34. The computer program product according to claim 27, wherein said computer usable program code configured to inspect said at least one indicator displays a description of a transaction that does not directly provide account information associated with said transaction or an amount of said transaction.

35. The computer program product according to claim 27, wherein said computer usable program code configured to inspect said at least one indicator displays occurrences of events of financial transactions that are monitored to identify identity fraud.

36. The computer program product according to claim 27, wherein said computer usable program code configured to inspect said at least one indicator monitors events related to persons entrusted to transact on behalf of a user of said aggregating entity.

37. The computer program product according to claim 36, wherein said user comprises a business and said persons entrusted to transact on behalf of said user comprise employees of said business.

38. The computer program product according to claim 27, wherein said computer usable program code configured to enable a token to be received by a transaction entity provides at least one token to at least one additional transaction entity, wherein:

each of said at least one additional transaction entity is adapted to send event messages to said aggregating entity upon the occurrence of a specified type of event, each event messages comprising at least one token, said aggregating entity is adapted to aggregate at least one indicator corresponding to said occurrence of said specified type of event with any previous indicators in said account based upon said token received with said event message.

39. The computer program product according to claim 27, wherein said transaction entity comprises a bank or a creditor.