Inspecting event indicators

• US 10,152,712 B2
• Filed: 05/10/2006
• Issued: 12/11/2018
• Est. Priority Date: 05/10/2006
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Inventors: Schimpf, Brian C., Stern, Edith H., Weir, Robert C., Willner, Barry E.
• Primary Examiner(s): Hewitt, II, Calvin L
• Assistant Examiner(s): Asgari, Sima
• Application Number:
  US11/431,380
• Publication Number:
  US 20070265807A1
• Time in Patent Office: 4,598 Days
• Field of Search: 705 1, 705 50-500
• 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 method comprising:

associating, by an aggregating server, a plurality of private keys and a plurality of corresponding public keys with a plurality of user accounts;

communicating, by the aggregating server via a network, a first public key from the plurality of public keys to a device associated with a user account from the plurality of user accounts;

receiving, by the device, the first public key from the aggregating server;

generating, by the device, a plurality of tokens based on the first public key;

transmitting, by the device, the plurality of tokens to a plurality of transaction entities associated with the user account;

receiving, by the aggregating server from a first transaction entity of the plurality of transaction entities, via the network, a first event message comprising a first token;

determining, by the aggregation server, that the first token was not previously used by the first transaction entity;

determining, by the aggregating server, based on the determining that the first token was not previously used by the first transaction entity and using the plurality of private keys, that the first token was generated using the first public key;

determining, by the aggregating server, based on the first token, a first event description for the first event message;

generating, by the aggregating server, a first event indicator comprising the first event description for the first event message;

deriving, by the aggregating server, from a plurality of event types, a first event type associated with the first event message;

receiving, by the aggregating server, from a second transaction entity, a second event message comprising a second token;

generating, by the aggregating server, a second event indicator based on the second event message, wherein the second event indicator is associated with the first event type;

compiling, by the aggregating server, a group of event indicators associated with the first event type, wherein the group of event indicators comprises at least the first event indicator and the second event indicator;

receiving, by the aggregating server, login information associated with the user account; and

presenting, by the aggregating server, the compiled group of event indicators on the device associated with the user account, based on receiving the login information.

2. The method of claim 1, further comprising:

providing, by the aggregating server, an interface on the device associated with the user account, wherein the interface provides at least one of viewing, filtering, querying, searching, sorting, printing, downloading, or deleting the compiled group of event indicators, to a user associated with the user account.

3. The method of claim 1, further comprising:

determining that the first token was previously used by the first transaction entity; and

disregarding the first event message, based on the determining that the first token was previously used by the first transaction entity.

4. The method of claim 1, wherein the first event description is determined further based on the determining the first token was generated using the first public key.

5. The method of claim 1, wherein the first transaction entity comprises a bank.

6. The method of claim 1, further comprising:

decrypting, by the aggregating server, the first token using a first private key corresponding to the first public key; and

generating a first token value, based on the decrypted first token.

7. The method of claim 6, wherein the first event type is derived further based on the first token value.

8. The method of claim 1, wherein generating the plurality of tokens comprise:

encrypting, by the device, a plurality of token values using the first public key.

9. A system, comprising:

an aggregating server comprising one or more first hardware processors and a first non-transitory memory storing first instructions that when executed by the one or more first hardware processors cause the one or more first hardware processors to perform first operations comprising;

associating a plurality of private keys and a plurality of corresponding public keys with a plurality of user accounts; and

communicating, via a network, a first public key from the plurality of public keys to a device associated with a user account from the plurality of user accounts; and

the device comprising one or more second hardware processors and a second non-transitory memory storing second instructions that when executed by the one or more second hardware processors cause the one or more second hardware processors to perform second operations comprising;

receiving the first public key from the aggregating server;

generating a plurality of tokens based on the first public key; and

transmitting the plurality of tokens to a plurality of transaction entities associated with the user account;

wherein the first operations further comprise;

receiving, from a first transaction entity of the plurality of transaction entities, via the network, a first event message comprising a first token;

determining that the first token was not previously used by the first transaction entity;

determining, based on the determining that the first token was not previously used by the first transaction entity token by and using the plurality of private keys, that the first token was generated using the first public key;

determining, based on the first token, a first event description for the first event message;

generating a first event indicator comprising the first event description for the first event message;

deriving, from a plurality of event types, a first event type associated with the first event message;

receiving, from a second transaction entity, a second event message comprising a second token;

generating a second event indicator based on the second event message, wherein the second event indicator is associated with the first event type;

compiling a group of event indicators associated with the first event type, wherein the group of event indicators comprises at least the first event indicator and the second event indicator;

receiving login information associated with the user account; and

presenting the compiled group of event indicators on the device associated with the user account, based on receiving the login information.

10. The system of claim 9, wherein the first operations further comprise:

providing, by the aggregating server, an interface on the device associated with the user account, wherein the interface provides at least one of viewing, filtering, querying, searching, sorting, printing, downloading, or deleting the compiled group of event indicators to a user associated with the user account.

11. The system of claim 9, wherein the first operations further comprise:

determining that the first token was previously used by the first transaction entity; and

disregarding the first event message, based on the determining that the first token was previously used by the first transaction entity.

12. The system of claim 9, wherein the first event description is determined further based on the determining the first token was generated using the first public key.

13. The system of claim 9, wherein the first transaction entity comprises a credit card company.

14. The system of claim 9, wherein the first operations further comprise:

decrypting the first token using a first private key corresponding to the first public key; and

generating a first token value, based on the decrypted first token.

15. The system of claim 14, wherein the first event type is derived further based on the first token value.

16. The system of claim 9, wherein generating the plurality of tokens comprise:

encrypting a plurality of token values using the first public key.