DEBIT-BASED IDENTITY THEFT MONITORING AND PREVENTION

1 - 87 . (canceled)

88 . A method of monitoring an account and reporting account activity using a system including a central computer in communication with a computer network, the method comprising:

storing, by the central computer, a unique key in a database, the unique key being based on consumer information associated with the consumer;

receiving, by the central computer, an event key for an account event;

determining, by the central computer, that the account event is associated with the consumer by (i) comparing the event key with the stored unique key and (ii) determining, based on the comparing, that the event key and the stored unique key match;

generating, by the central computer and based on the determined match, a notification including an event listing of one or more account events having event keys that match the unique key associated with the consumer; and

providing, by the central computer, the generated notification to a consumer computer associated with the consumer.

89 . The method of claim 88 , wherein the provided notification includes an instruction specifying how to generate a disagreement notification.

90 . The method of claim 88 , further comprising:

receiving, from the consumer computer, a disagreement notification; and

based on the received disagreement notification, freezing consumer account information associated with the consumer.

91 . The method of claim 90 , wherein freezing the consumer account information prevents any transaction associated with financial information of the consumer.

92 . The method of claim 88 , further comprising:

receiving, from the consumer computer, a disagreement notification; and

based on the received disagreement notification, providing a notice to an event provider device associated with the account event.

93 . The method of claim 88 , further comprising:

receiving the consumer information from the consumer computer;

standardizing the received consumer information to a format for the central computer; and

based on the received consumer information, generating the unique key using the standardized consumer information.

94 . The method of claim 93 , wherein the received consumer information is received from a plurality of devices, the method further comprising merging the received consumer information.

95 . The method of claim 93 further comprising generating the event key, wherein the unique key and the event key are generated according to a same formula.

96 . The method of claim 88 , wherein the database is a first database, the method further comprising:

receiving the consumer information and vendor information from a vendor device;

comparing the received vendor information to vendor information stored in a second database;

based on comparing the received and stored vendor information, generating the unique key.

97 . The method of claim 88 , wherein:

the account event is based on account event information received from an event provider device; and

the account event comprises an event type.

98 . The method of claim 97 , wherein the one or more account events of the event listing are limited to those of one or more event types, including the event type of the account event.

99 . The method of claim 98 further comprising:

accessing consumer preferences stored in the database;

determining, based on the accessed preferences, the one or more event types.

100 . The method of claim 98 , wherein the event type is one of: a new account inquiry, a returned check, a payment device order, a lost or stolen account information, an account closure, an account freeze, or an account freeze lift.

101 . The method of claim 88 further comprising determining the account event is valid by determining the account event is from an authorized source or by determining the event is in a format or structure of the central computer.

102 . A system for monitoring an account and reporting account activity, the system comprising:

a processor; and

a non-transitory computer-readable medium containing a set of instructions that, when executed by the processor, cause the processor to perform operations comprising:

storing a unique key in the database, the unique key being based on consumer information associated with the consumer;

receiving, from the event provider computer, an event key for an account event;

determining that the account event is associated with the consumer by (i) comparing the event key with the stored unique key and (ii) determining, based on the comparing, that the event key and the stored unique key match;

generating based on the determined match, a notification including an event listing of one or more account events having event keys that match the unique key associated with the consumer; and

providing the generated notification to a consumer computer associated with the consumer.

103 . The system of claim 102 , the operations further comprising:

receiving, from the consumer computer, a disagreement notification; and

based on the received disagreement notification, providing a notice to an event provider device associated with the account event.

104 . The system of claim 102 , the operations further comprising:

receiving the consumer information from the consumer computer;

standardizing the received consumer information to a format for the central computer; and

based on the received consumer information, generating the unique key using the standardized consumer information.

105 . The system of claim 104 , the operations further comprising generating the event key, wherein the unique key and the event key are generated according to a same formula.

106 . The system of claim 102 , wherein:

the account event is based on account event information received from an event provider device;

the account event comprises an event type; and

the one or more account events of the event listing are limited to those of one or more event types, including the event type of the account event.

107 . The system of claim 102 , the operations further comprising determining the account event is valid by determining the account event is from an authorized source or by determining the event is in a format or structure of the central computer.