Communicating event messages corresponding to event indicators

• US 20070265945A1
• Filed: 05/10/2006
• Published: 11/15/2007
• Est. Priority Date: 05/10/2006
• Status: Abandoned Application

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Weir, Robert, Schimpf, Brian, Stern, Edith, Willner, Barry
• Application Number:
  US11/431,381
• Publication Number:
  US 20070265945A1
• Time in Patent Office: Days
• US Class Current: 705/35
• 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 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

An event message is created that is associated with an event of interest to a user. A transaction entity obtains a token that corresponds to an account of an aggregating entity. Additionally, at least one type of event is identified. Each identified type of event comprises an event type that is of interest to a user and is intended by the user to be reported to the aggregating entity. The transaction entity identifies an occurrence of an event that corresponds to a previously identified type of event and creates an event message that includes the token. The transaction entity then transmits the event message to the aggregating entity. The transmitted event message is adapted to correspond to at least one indicator of the occurrence of the event that is provided by the aggregating entity for review by the user.

Claims

1. A computer implemented method for creating an event message associated with an event, comprising:

obtaining a token that corresponds to an account of an aggregating entity;

identifying at least one type of event of interest to a user that is intended to be reported to said aggregating entity;

identifying an occurrence of an event that is an identified type of event;

creating an event message in response to identifying said occurrence of said event, said event message comprising said token; and

transmitting said event message to said aggregating entity, said event message adapted to correspond to at least one indicator of said occurrence of said event that is provided by said aggregating entity for review by said user.

2. The method according to claim 1, wherein said obtaining a token that corresponds to an account of an aggregating entity comprises obtaining said token from at least one of said user or said aggregating entity.

3. The method according to claim 1, wherein said identifying at least one type of event of interest to a user that is intended to be reported to said aggregating entity comprises identifying at least one of a bank withdrawal, a bank deposit and a credit card use.

4. The method according to claim 1, wherein said creating an event message in response to identifying said occurrence of said event further comprises specifying at least one description of said event, which is provided in addition to said token with said event message.

5. The method according to claim 4, wherein said specifying at least one description of said event comprises specifying a description of said occurrence of said event without directly providing the identity of said user or a transaction entity associated with said occurrence of said event.

6. The method according to claim 4, wherein said specifying at least one description of said event comprises specifying a description of a transaction without directly providing account information associated with said transaction or an amount of said transaction.

7. The method according to claim 4, wherein said specifying at least one description of said event comprises encoding said occurrence of said event in a contextually meaningless text.

8. The method according to claim 1, wherein said creating an event message in response to identifying said occurrence of said event further comprises specifying at least one description for each of said event and at least one different event that are combined into said event message in addition to said token.

9. The method according to claim 1, wherein said creating an event message in response to identifying said occurrence of said event and said transmitting said event message to said aggregating entity are implemented by executing a script that creates said event message and communicates said event message to said aggregating entity.

10. The method according to claim 1, further comprising creating an audit trail corresponding to each event message transmitted to said aggregating entity.

11. The method according to claim 1, further comprising placing credentials required to transmit event messages to said aggregating entity in a credential vault.

12. The method according to claim 1, further comprising generating a security credential adapted to be exchanged with said aggregating entity.

13. A computer system to create an event message associated with an event, comprising:

a module to store a token that corresponds to an account of an aggregating entity;

a module to store at least one type of event of interest to a user that is intended to be reported to said aggregating entity;

a module to identify an occurrence of an event that is an identified type of event;

a module to create an event message in response to identifying said occurrence of said event, said event message comprising said token; and

a module to transmit said event message to said aggregating entity, said event message adapted to correspond to at least one indicator of said occurrence of said event that is provided by said aggregating entity for review by said user.

14. The system according to claim 13, wherein said module to store a token that corresponds to an account of an aggregating entity is further adapted to receive a communication of said token from at least one of said user or said aggregating entity.

15. The system according to claim 13, wherein said module to store at least one type of event of interest to a user that is intended to be reported to said aggregating entity stores at least one of a bank withdrawal, a bank deposit and a credit card use type of event.

16. The system according to claim 13, wherein said module to create an event message in response to identifying said occurrence of said event further specifies at least one description of said event, which is provided in addition to said token with said event message.

17. The system according to claim 16, wherein at least one description of said event comprises a description of said occurrence of said event without directly providing the identity of said user or a transaction entity associated with said occurrence of said event.

18. The system according to claim 16, wherein at least one description of said event comprises a description of a transaction without directly providing account information associated with said transaction or an amount of said transaction.

19. The system according to claim 16, wherein at least one description of said event comprises a description that encodes said occurrence of said event in a contextually meaningless text.

20. The system according to claim 13, wherein said module to create an event message in response to identifying said occurrence of said event creates an event message that includes at least one description for each of said event and at least one different event that are combined into said event message in addition to said token.

21. The system according to claim 13, wherein said module to create an event message in response to identifying said occurrence of said event and said module to transmit said event message to said aggregating entity comprise a script that creates said event message and communicates said event message to said aggregating entity.

22. The system according to claim 13, further comprising a module that creates an audit trail corresponding to each event message transmitted to said aggregating entity.

23. The system according to claim 13, further comprising a credentials vault that stores credentials required to transmit event messages to said aggregating entity.

24. The system according to claim 13, further comprising a security credential that is adapted to be exchanged with said aggregating entity.

25. A computer program product to create an event message associated with 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 store a token that corresponds to an account of an aggregating entity;

computer usable program code configured to store at least one type of event of interest to a user that is intended to be reported to said aggregating entity;

computer usable program code configured to identify an occurrence of an event that is an identified type of event;

computer usable program code configured to create an event message in response to identifying said occurrence of said event, said event message comprising said token; and

computer usable program code configured to transmit said event message to said aggregating entity, said event message adapted to correspond to at least one indicator of said occurrence of said event that is provided by said aggregating entity for review by said user.

26. The computer program product according to claim 25, wherein said computer usable program code configured to store a token that corresponds to an account of an aggregating entity is further adapted to receive a communication of said token from at least one of said user or said aggregating entity.

27. The computer program product according to claim 25, wherein said computer usable program code configured to store at least one type of event of interest to a user that is intended to be reported to said aggregating entity stores at least one of a bank withdrawal, a bank deposit and a credit card use type of event.

28. The computer program product according to claim 25, wherein said computer usable program code configured to create an event message in response to identifying said occurrence of said event further comprises computer usable program code configured to specify at least one description of said event, which is provided in addition to said token with said event message.

29. The computer program product according to claim 28, wherein said computer usable program code configured to create an event message in response to identifying said occurrence of said event provides a description of said occurrence of said event without directly providing the identity of said user or a transaction entity associated with said occurrence of said event.

30. The computer program product according to claim 28, wherein said computer usable program code configured to create an event message in response to identifying said occurrence of said event provides a description of a transaction without directly providing account information associated with said transaction or an amount of said transaction.

31. The computer program product according to claim 28, wherein said computer usable program code configured to create an event message in response to identifying said occurrence of said event provides a description that encodes said occurrence of said event in a contextually meaningless text.

32. The computer program product according to claim 25, wherein said computer usable program code configured to create an event message in response to identifying said occurrence of said event further comprises computer usable program code configured to combine at least one description for each of said event and at least one different event into said event message in addition to said token.

33. The computer program product according to claim 25, wherein said computer usable program code configured to create an event message in response to identifying said occurrence of said event and said computer usable program code configured to transmit said event message to said aggregating entity comprise a script that creates said event message and communicates said event message to said aggregating entity.

34. The computer program product according to claim 25, further comprising computer usable program code configured to create an audit trail corresponding to each event message transmitted to said aggregating entity.

35. The computer program product according to claim 25, further comprising computer usable program code configured to interact with a credentials vault to store credentials required to transmit event messages to said aggregating entity.

36. The computer program product according to claim 25, further comprising computer usable program code configured to exchange a security credential with said aggregating entity.