US20200380599A1

US20200380599A1 - Circular rotational interface for display of consumer credit information

Info

Publication number: US20200380599A1
Application number: US16/851,525
Authority: US
Inventors: Jeremy Wasser; Michelle Felice-Steele; Melinda Nies; Luke Giltner
Original assignee: Consumerinfo com Inc
Current assignee: Consumerinfo com Inc
Priority date: 2012-11-30
Filing date: 2020-04-17
Publication date: 2020-12-03
Also published as: US10963959B2; US9916621B1; US11132742B1; US10366450B1; US20180225756A1; US11308551B1; US11651426B1; US9830646B1

Abstract

A credit score user interface that may comprise a circular visual interface to view a consumer's credit information is disclosed herein. Sections of the circular visual interface may correspond to credit categories, where each section is sized according to the impact of the associated credit category on the consumer's credit score. One of the category sections may be selected, and credit information about a specific consumer that is related to that section may be displayed. The selected credit category may change based on touch input. A change in selection may cause new credit information related to the newly selected credit category to be displayed about the specific consumer.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference in their entirety under 37 CFR 1.57.
This application is related to, but does not claim priority from, U.S. patent application Ser. No. 10/452,155, filed May 30, 2003, now U.S. Pat. No. 7,610,229; U.S. patent application Ser. No. 12/606,060, filed Oct. 26, 2009, now U.S. Pat. No. 8,015,107; patent application Ser. No. 11/150,480, filed Jun. 10, 2005, now U.S. Pat. No. 7,593,891; patent application Ser. No. 12/563,779, filed Sep. 21, 2009, now U.S. Pat. No. 7,925,582; U.S. patent application Ser. 13/326,803, filed Dec. 15, 2011, and U.S. Prov. Pat. App. No. 60/384,650, filed May 30, 2002. The disclosures of the above-listed applications are all hereby incorporated by reference as if set forth herein in their entireties.

BACKGROUND

This disclosure relates to the field of consumer credit information and particularly to the presentation of credit score and credit report information.
The credit report and credit score are an important indicator of a consumer's financial health. Consequently, monitoring their credit reports and having a high credit score is important to consumers for many reasons. A high credit score may qualify a consumer for various financial programs and/or allow a consumer to receive favorable rates is such programs, such as loan applications, rental applications, real estate mortgages, and so on. The credit report may allow a user to view the underlying data affecting their credit score. Thus, many consumers have a substantial interest in finding ways to improve their credit scores and understand their credit reports.
There is much information available to consumers as to how to improve credit scores. For example, sources provide advice to consumers to pay off loans, to establish certain numbers of credit accounts, to establish new loans, to raise or lower credit card limits, and so on. However, this advice is generic to all consumers and does not provide information specific to a particular consumer's situation. The question for many consumers then is “How is my particular credit data affecting my credit score?”.
To determine effective actions to take, it is often necessary to analyze a consumer's underlying credit information. However, paper credit reports are often confusing to consumers, and do not explain the effects of particular pieces of data contained within the credit report. Furthermore, consumers often do not know how their credit activities affect their credit score or how their credit score is calculated. This translates into consumers struggling to use and analyze their credit information in meaningful ways, or develop effective strategies to raise their credit score.

SUMMARY

Thus, it would be advantageous for consumers to be able to quickly view and understand how credit information affects their credit score. In particular, it would be advantageous for consumers to be able to visualize their particular credit information and understand how it is affecting their current credit score. It would also be advantageous for consumers to visualize the impact of specific credit data upon their credit score, either individually, or by category.
Consumers are interacting more every day with mobile devices, such as smart phones, tablets, and the like. However, information that consumers traditionally view in the form of printed materials don't optimize interaction capabilities of such mobile devices. Discussed herein are systems and methods for generating user interfaces that display credit information of consumers in manners that are specifically tailored for optimal use on mobile devices, such as user interfaces that optimize the user's ability to interface with credit data and to explore such credit data. In particular, the user interfaces described herein are dynamically created using credit data specific to a particular consumer
In an embodiment, a mobile application can display and receive input from various user interfaces, including a circular pie chart representing input categories to a credit score calculation. The circular pie chart interface allows a user to rotate the pie chart relative to a pointer indicator so that when the indicator points to a portion of the pie chart associated with an input category, summary information may be displayed about how that input category impacts a credit score.
One embodiment may be a computer-readable medium comprising instructions configured to cause one or more computer processors to perform operations. The operations may include, among others, receiving credit score user interface data. The data may comprise a consumer's credit score based on a credit score algorithm and/or a consumer's summary credit information associated with respective categories of credit information used in calculation of the consumer's credit score. The instructions may also cause a processor to generate a user interface configured for display on a touch sensitive computing device, where the user interface comprises (1) a plurality of sections of a circular visual computer interface, wherein each section of the plurality of sections is associated with a category of credit information and each section of the plurality of sections is sized according to weight of the associated category's impact on the consumer's credit score and (2) a visual section indicator that indicates one of the plurality of sections as selected within the circular visual computer interface. The instructions may also cause a processor to access the credit summary information associated with a selected category of credit information. The user interface may be configured to depict the circular visual computer interface rotating in response to a dragged touch input on the displayed circular visual computer interface. Additionally, the rotation may cause the visual section indicator to indicate a particular section as selected within the circular visual computer interface, and display a portion of the consumer's credit summary information for the category associated with the particular section of the circular visual computer interface that is indicated as selected by the visual section indicator.
Some embodiments may comprise a computerized method that may be performed by a computer system. The computer system (comprising one or more computing devices) may receive a credit report, credit score, and credit summary information regarding a specific consumer, where the credit report and credit score have been generated by a credit bureau. The computer system may store the consumer's credit report, credit score and credit summary information in memory. The computer system may generate a spin-wheel user interface, the spin-wheel user interface comprising a plurality of spin-wheel user interface sections associated with a credit category. The spin-wheel user interface sections may be sized proportional to the credit score impact of each section's associated credit category. The computer system may access at least a first portion of the consumer's credit summary information in computer memory to display first credit category data specific to the consumer associated with a first selected spin-wheel user interface section, the first selected spin-wheel user interface section being displayed as selected using a visual selection indicator. Additionally, the computer system may receive a touch input from a user via a touch screen interface. The computer system may rotate the spin-wheel user interface according to the received touch screen interface input until a second selected spin-wheel user interface section is displayed as selected by the visual selection indicator. The computer system may access at least a second portion of the consumer's credit summary information in computer memory to display second credit category data specific to the consumer associated with the second selected spin-wheel user interface section, and display the second credit category data associated with the second selected spin-wheel user interface section.
Another embodiment may be a mobile computing device comprising at least a data store configured to store a consumer's credit report and summary credit information, a touch screen display configured to receive touch screen input; one or more processors; and a user interface module executable on the one or more processors. The user interface module may be configured to at least receive credit information specific to a consumer comprising at least a portion of the consumer's credit report and summary credit information, store the credit information in the data store, display a visual circular rotational user interface comprising a plurality of visual credit category sections, the visual credit category sections sized proportionate to a credit category's impact on a credit score associated with the consumer, display a visual credit category section indicator configured to indicate a selected visual credit category section, access a first portion of the credit information specific to the consumer in the data store, wherein the first portion of the credit information corresponds to data associated with the selected visual credit category section, display the first portion of the credit information specific to the consumer, receive a touch screen input over an area corresponding to the visual circular rotational user interface, rotate the visual circular rotational user interface relative to a direction indicated by the touch screen input, access a second portion of the credit information specific to the consumer in the data store, wherein the second portion of the credit information corresponds to data associated with a second selected visual credit category section, and display the second portion of the credit information specific to the consumer.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram showing information exchange between a mobile computing device of a user and a credit report system that generates a credit score visualization of the user for display on the user's mobile computing device, as used in an embodiment.

FIG. 2 is a flowchart illustrating processes taken to deliver credit information to a user's mobile computing device, as used in an embodiment.

FIG. 3 is a flowchart illustrating processes taken to use a rotational circular user interface to display credit information, as used in an embodiment.

FIG. 4 is a sample rotational user interface and related user interfaces for analyzing credit report data, as used in an embodiment.

FIG. 5 is a sample rotational user interface and related user interfaces for analyzing credit report data, as used in an embodiment.

FIG. 6 is a sample rotational user interface and related user interfaces for analyzing credit report data, as used in an embodiment.

FIG. 7 is a sample rotational user interface and related user interfaces for analyzing credit report data, as used in an embodiment.

FIG. 8 is a sample rotational user interface and related user interfaces for analyzing credit report data, as used in an embodiment.

FIG. 9 is a sample credit report user interface for analyzing credit report accounts, as used in an embodiment.

FIG. 10 is a sample block diagram representing hardware and/or software components of an example embodiment.

DETAILED DESCRIPTION

Overview

This disclosure illustrates credit summary user interface that includes a “spin-wheel” user interface and a credit category user interface, as used in some embodiments, to analyze and visualize credit data for a specific consumer. The spin-wheel user interface, (also called a visual circular user interface or a circular rotational user interface, or any combination thereof) both displays credit information about a specific consumer and allows for user input to control the display of additional credit information about the consumer either in the spin-wheel user interface and/or the credit category user interface. In one embodiment, the spin-wheel includes discrete pie chart sections of a circular whole. Each pie chart section of the spin-wheel is associated with a credit data input category that is used to calculate a credit score according to a credit score algorithm. For example, sections may include a credit usage, payment history, age of accounts, types of accounts, and credit inquiries. Each pie chart section of the spin-wheel may be sized according to the weight of its corresponding category. For example, FIG. 4 illustrates one embodiment where 30% of a credit score is determined on credit usage. Therefore, the corresponding section 407 of the pie chart is sized so it covers 30% of the spin-wheel pie chart region. In some embodiments, the center of the spin-wheel user interface may display credit information such as a consumer's credit score, when the credit score was last updated, the corresponding risk level of the consumer, and/or other data, based on a consumer's credit data transferred to the user device. Depending on the embodiment, the quantity and sizes of the various sections may vary from consumer to consumer, between geographic regions, or otherwise to indicate relative proportions of that certain types of data have towards a particular consumer's credit score.
In some embodiments, a user device displaying such an interface, such as computing device 162, receives credit score data or information to populate the spin-wheel user interface from a credit bureau or intermediary system such as credit report system 100, including a consumer's credit score. The credit data may be separated, at least in part, into categories, such as the five categories discussed above. The received credit data may also include summary credit information associated with each category of input credit information, such as summary credit data attributes, that may be displayed in a related credit summary data window.
FIG. 4, discussed further below, illustrates an example credit summary user interface 400 including a spin-wheel user interface 420 (or simply “spin-wheel” 420) and a credit category user interface 408. In some embodiments, the credit summary user interface 400 may also comprise a visual section indicator 413 and a credit category user interface 408. The section indicator 413 indicates a currently selected section of the spin-wheel by pointing to a section on the spin-wheel. The credit category user interface 408 displays credit information specific to the consumer about a currently selected credit category. For example, because the section indicator 413 in FIG. 4 is pointing to the credit usage section 407 of the spin-wheel, credit usage information is displayed in the credit category user interface 408. Thus, the consumer's credit information, such as the consumer having used 50% of his available credit, is displayed in the summary window.
The spin-wheel 420 can be rotated to alter the spin-wheel section selected by the section indicator 413. In some embodiments, a user may use a touch screen on a mobile device, such as an iPad, iPhone or Android device, to touch the screen to alter the rotational position of the spin-wheel. For example, the spin-wheel may rotate when a touch is registered within an unselected section of the spin-wheel. In such an embodiment, the spin-wheel may rotate so that the touched section is now selected by the section indicator 413, resulting in altering the credit category user interface 408 to contain information about the category associated with the newly selected section.
In some embodiments, a user may touch and remain touching with the spin-wheel 420, and drag their touch across the spin-wheel in a direction consistent with rotating the spin-wheel. In such an embodiment, the spin-wheel 420 may rotate proportionately with the touch movement. Because of the rotation of the spin-wheel 420, a new section may be indicated by the selection indicator 413, and thus the credit category user interface 408 may be updated according to the newly selection section as described above.

High Level Data Flow

FIG. 1 is a block and flow diagram of an embodiment of a credit score and report visualization computing system, in conjunction with related components. The entire visualization system may be a single computing device or a plurality of computing devices connected by a network or distributed computing system.
In an embodiment, various software modules are included in the credit score and report visualization system, which may be stored on the system itself, or on computer readable storage media separate from the system and in communication with the system via a network or other appropriate means. The credit score visualization system may include a credit data gathering module 150, which performs various tasks of gathering data used by the credit report visualization system. Such data may include, for example, credit data 103 retrieved from credit data database 108. Such a database 108 may comprise one or more credit bureaus and their databases, which usually receive information from raw data sources 166, such as banks and creditors.
The credit data may be retrieved via a network 160, via a dedicated communication channel, or by other means. In an embodiment, credit bureau 108 transmits credit data to the credit score visualization system 100 via a secured communication channel to ensure the privacy and security of the credit data.
In an embodiment, credit data is gathered on demand as required by the credit score visualization system. In another embodiment, credit data 103 is gathered on a periodic basis independent of requests for information to the credit score visualization system. In another embodiment, credit data is stored on the credit score visualization system (for example, in client computing device 162 or credit data gathering module 150), in which case, retrieval of credit data from a credit bureau may not be necessary. The credit data may include a complete credit report about a consumer, summary data, such as credit attributes (also referred to as credit variables) that are calculated using various modules, such as Experian's STAGG (standard aggregation variables) attributes, and/or credit data inputs to calculate a complete or partial credit score. Each credit data input may be associated with a particular category of credit inputs, for example credit usage, payment history, age of accounts, types of accounts, and credit inquiries. In some embodiments, credit data gathering module 150 may calculate the Summary/STAGG attributes or perform other modifications on the credit report or other credit data gathered.
Data gathering module 150 may also gather information about how a credit score is calculated. This may include algorithms, formulas, executable code, statistical variables, and the like. This information may be used to visualize the significance of each type of data in calculating a credit score. In an embodiment, the models and/or algorithms are retrieved from credit data database 108 on an on-demand basis as needed by the credit score visualization system. In another embodiment, the models and/or algorithms are retrieved on a periodic basis. In another embodiment, the credit score visualization system internally stores the models and/or algorithms (for example, stored on the client computing device 162).
In an embodiment, the credit score visualization system further includes user interface module 110, which may include executable instructions for constructing user interfaces or otherwise interacting with end users. User interface module 110 may include portions that are executed by the credit report system 100 and/or by the computing device 162. Thus, discussion herein of operations performed by the user interface module 110 may be performed entirely by the credit report system 100, entirely by the computing device 162, or some portions may be performed by the credit report system 100 while other portions are performed by the computing device 162. Furthermore, other computing systems may also perform all or some of the processes discussed with reference to the user interface module 110.
In one embodiment, the user interface module 110 may access data from credit data gathering module 150 or credit data database/credit bureau 108, and use that data to construct user interfaces that assist the user in visualizing a credit score and the underlying data used to construct a credit score. Such visualization may be presented to the end user and are designed to be easily manipulated and/or understood by the user. In an embodiment, the user interfaces transmitted by user interface module 110 are interactive. Various embodiments of the user interfaces that may be provided by user interface module 110, including a rotational circular visual interface (also referred to as a “spin-wheel”), are shown and described throughout this specification. Variations on such interfaces and other possible interfaces will be known to those of skill in the art.
User interface module 110 may be configured to construct user interfaces of various types. In an embodiment, user interface module 110 constructs web pages to be displayed in a web browser or computer/mobile application. The web pages may, in an embodiment, be specific to a type of device, such as a mobile device or a desktop web browser, to maximize usability for the particular device. In an embodiment, user interface module 110 may also interact with a client-side application, such as a mobile phone application (an “app”) or a standalone desktop application, and provide data to the application as necessary to display underlying credit score information.
Client computing device 162, which may comprise software and/or hardware that implements the user interface module 110, may be an end user computing device that comprises one or more processors able to execute programmatic instructions. Examples of such a computing device 162 are a desktop computer workstation, a smart phone such as the apple iPhone, a computer laptop, a tablet PC such as the iPad, a video game console, or any other device of a similar nature. In some embodiments, the client computing device 162 may comprise a touch screen that allows a user to communicate input to the device using their finger(s) or a stylus on a display screen. The computing device 162 (or any of the computing systems described herein, such as credit report system 100), as described in detail under FIG. 10 may comprise storage systems such as a hard drive or memory, or comprise any other non-transitory data storage medium. The storage systems may be configured to store executable instructions that may be executed by one or more processors to perform computerized operations on the client computing device, accept data input from a user (e.g. on the touch screen), and/or provide output to a user using the display. These executable instructions may be transmitted to another device for execution or processing by the device to implement the systems and methods described herein.
The computing device 162 may be connected to the credit report system 100, including credit data gathering module 150 or credit data database / credit bureau 108 via a network 160. The client device may be connected to the network 160, which may include any combination of networks, such as local area, wide area, Internet, etc., by way of a wired network, such as an ethernet LAN or cable modem, or via a wireless method, such as through an 802.11 access point or via a cell phone network. The network 160 allows computing devices to send (i.e. transmit) and receive electronic transmissions.
The computing device 162 may also comprise one or more client program applications, such as a mobile “app” (e.g. iPhone or Android app) that may be used to visualize data, and initiate the sending and receiving of messages in the credit score visualization system. This app may be distributed (e.g. downloaded) over the network to the client computing device directly from a credit bureau 108, from the credit report system 100, credit data gathering module 150, or from various third parties such as an apple iTunes repository. In some embodiments, the application may comprise a set of visual interfaces that may comprise templates to display a consumer's credit data information from a credit report or associated attributes. In some embodiments, as described above, visual user interfaces may be downloaded from another server or service, such as the credit report system 100. This may comprise downloading web page or other HTTP/HTTPS data from a web server and rendering it through the “app”. In some embodiments, no special “app” need be downloaded and the entire interface may be transmitted from a remote Internet server to computing device 162, such as transmission from a web server that is a part of the credit report system 100 to an iPad, and rendered within the iPad's browser.
FIG. 1 also illustrates an exemplary process for accessing credit data of a particular user, rendering the credit data within visual circular user interfaces, and linking that credit data to specific information in the credit data. Depending on the embodiment, the process illustrated by interactions 1-5 of FIG. 1 may include fewer or additional interactions and/or the interactions may be performed in an order different than is illustrated.
Beginning with interaction (1), the computing device 162 may transmit to credit report system 100 a request for a credit report and/or credit attributes, such as a credit summary user interface that includes a spin-wheel user interface and a credit category user interface, which may be generated based on underlying credit data. Such underlying credit data may include, but is not limited to, information about credit or debt accounts (such as the amount of available credit in accounts associated with a consumer, the age of open credit accounts, the types of accounts, the payment history on accounts, and past inquiries into credit reports or credit score).
In some embodiments, such a request may be accompanied with an authentication or authorization request. For example, in some embodiments, access to credit data may be restricted based on user identification. An authentication scheme may comprise submitting a user name and password to the credit report system 100, or any other authentication mechanism known by those skilled in the art. The authentication request may have occurred prior to the request for data access, or during the request. In some embodiments, although a user may authenticate, only certain users will be authorized to receive credit report data. For example, the credit report system 100 may comprise memory storing a list of users or types of users that may gain access to their credit data, such as paying users. In some embodiments, no authentication is necessary and credit data may be freely accessed by all users. Such a request may also include a request for the algorithms or user interfaces that may be used by an “app” or browser to render and interact with the requested credit data.
In some embodiments, some functionality may be accessible by unauthenticated users, and other functionality only accessible to authenticated users. The authenticated and unauthenticated sections may have the same features, similar features, or different features. In an embodiment, the authenticated section offers additional features not available in the unauthenticated section. For example, credit data or credit-related information is used in the various systems and methods described herein. This information may be stored in member accounts or automatically retrieved based on member account data. In such an embodiment, the credit-related information may be automatically pre-populated, so that members need not enter that information, while unauthenticated users would enter their information manually.
In interaction (2) of FIG. 1, the credit report system 100 may retrieve a credit report (and/or other credit data or other financial data) and/or calculate attributes. In some embodiments, the credit data gathering module 150, upon receiving a request from the computing device 162, may retrieve a credit score, credit report, and/or STAGG attributes (or other custom required attributes) from its local storage and fulfill the access request without consulting a credit bureau. For example, the data gathering module may have previously received a credit report and credit score from a credit bureau for that user and would have the report cached in its local storage. In some embodiments, the credit report and score may be periodically retrieved for users from a credit bureau in order to have it locally on file. Alternatively, or in combination, the data gathering module 150 may retrieve in real time the credit report, credit score and/or summary credit attributes from the credit bureau/database 108.
The data gathering module 150 may also calculate any attributes required by the visual user interfaces implemented by the user interface module 110. For example, summary credit attributes are typically calculated by credit bureaus that summarize credit data. These summary credit attributes can be requested along with, or as an alternate to, a credit report. However, the data gathering module 150 may also compile the summary attributes based on the credit report, or calculate custom (e.g. non-STAGG) attributes based on the credit report. For example, one summary attribute may comprise a calculation of the amount of available credit for a consumer. Such an attribute may be calculated based upon summing up all of the un-used credit available in a consumer's accounts. This final figure may then be associated with the credit report and stored in the data gathering module for later transfer to a client computing device 162. These calculations may be performed on demand or periodically.
In addition to retrieving credit reports, scores, and attributes, the data gathering module 150 may, in some embodiments, retrieve algorithms and other user interfaces such as a circular rotational user interface for transfer to the client device. These may be stored locally on disk within the credit data gathering module 150, or retrieved from a credit database. For example, a specific credit score algorithm may be retrieved from a credit bureau 108 and/or known in advance by the credit data gathering module 150. Based on the formula, the credit data gathering module may alter or generate a credit summary user interface (and/or other user interface) to reflect the specific formula. For example, as shown in FIG. 4, “credit usage” data may make up 30% of a credit score. However, this figure could be a percentage that is instead calculated on demand based upon a formula information sent to the credit data gathering module 150.
After retrieving and or calculating the information, interaction (3) of FIG. 1 illustrates the credit report system 100 transmitting the credit report and attributes, via the network, to the computing device's 162 user interface module 110. This information may be transmitted using a text credit report format, an XML format, using web services APIs, or any other organized data structure or protocol for transferring the information between the credit report system 100 and the computing device 162. Alternatively, this information may be transmitted to the client computing device 162 as a part of a web page and accompanying web page user interfaces to be rendered with an app or a browser, such as software code configured to generate the various visual features of the credit summary user interface discuss herein. In this embodiment, the credit report system may act as a web page or web site configured to provide static, scriptable, or executable code and data that may be used to implement the entire invention, even with a client computing device 162 only capable of web browsing.
In interaction (4), the user interface module 110 may then store the received credit information, and parse the credit report and attributes for data required to render the user interface. This may include organizing in a data structure one or more received attributes and data contained within the credit report into credit data categories such as credit usage, age of accounts, types of accounts, payment history, and credit inquiries. Additionally, this may involve calculating any additional attributes or summarization data based on the credit report for use in displaying summary information about the credit report to a user. As noted above, depending on the embodiment certain features discussed with reference to the user interface module 110 may be performed by the credit report system 100. Thus, the above-noted organization and calculations may be performed partially or entirely by the credit report system 100 in certain embodiments.
As described in more detail in FIG. 3 and its associated discussion, the user interface module 110 then displays a credit summary user interface including a spin-wheel user interface that allows a user to select a credit category using a touch screen, and displays detailed or summarized credit information pertinent to the selected category (e.g., in a credit category user interface). By way of example, FIGS. 4-8 illustrate circular rotational user interfaces that may be used in some embodiments.
Interaction (5) illustrates that, in some embodiments, the summarized data displayed for each category (e.g., in the credit category user interface) may be linkable to a displayable portion of a credit report on the computing device 162. For example, by touching a specific piece of data within the credit category user interface and/or the spin-wheel user interface, the user may be automatically directed to a portion of the user's credit report displaying detailed information regarding the clicked data. With reference to FIG. 4, for example, if “Total Credit Limit” 410 was touched in the credit usage user interface 411, the client device 162 and/or credit report system 100 may direct the user to a portion of their credit report listing all account information, including each individual credit limit for each account and/or other data related to the user's total credit limit. Advantageously, this allows a user to easily browse and visualize a high level overview of their credit data and drill down into their detailed credit report for further information.

Credit Reports and Credit Bureaus

The credit report system 100 may be separate from a credit bureau or credit data database 108. One of the purposes of the credit report system is to interface with the credit bureau or any database that has data that will eventually be rendered by computing device 162. The credit report system 100 may request and extract the appropriate credit data for a specific consumer based on a user using the computing device 162. This allows for a single point of contact for computing device 162 interaction. The credit report system 100 can then be configured to request from and receive data from credit bureaus or other credit databases.
Alternatively, the credit report system 100 may be executed by a credit bureau itself. In this case, the credit report system and the credit bureau functionality may be combined, with no need to transfer data over a wide area network between them. In some embodiments, the client computing device 162 may be configured to interact directly with a credit bureau over a network, to access a credit report and summary attributes. In this case, any custom attribute creation or processing needed must be performed by the computing device 162.
Example Method of Obtaining and/or Generating Data for Credit Summary User Interface
FIG. 2 is a flowchart illustrating one embodiment of a method of retrieving a credit report and/or attributes/summarized credit data and generating data that may be used to render a credit summary user interface, as well as possibly other user interfaces for display to the user. In various embodiments, fewer blocks or additional blocks may be included in the process, or various blocks may be performed in an order different from that shown in FIG. 2. In particular, the blocks in FIG. 2 may be performed by computing device 162, credit report system 100 or credit database/bureau 108 (or any combination thereof), depending on which computing device/software service has access to the required credit data.
As one skilled in the art would recognize, credit bureaus make their data available to consumers and businesses, usually (but not limited to) for the purpose of checking a consumer's credit history and credit score. A credit bureau's credit report may include, among other things, data concerning payment history (such as current accounts and late payments), credit usage and availability, the age of financial accounts, the types of financial accounts, and inquiries into credit reports or credit scores. This data may be collected from one or more raw data sources 166 (FIG. 1) which may comprise information from consumers' banks, mortgagors, lendors, creditors, services, utilities, public records, and other institutions where a consumer holds a financial account. The data may include a status of each account, such as when the last bill was paid, how late a recent payment is or how behind a consumer is on their account, a payment history, the available credit allowed in an account, the account balance, and when an account was opened and/or closed, among other credit information.
Beginning in block 200, the requestor, for example the credit report system's 100 credit data gathering module 150 (or in some embodiments, the computing device itself 162) issues a request to a credit bureau or other credit database for credit information about a consumer, such as a credit report, and associated attributes. The request may be issued by sending it over an electronic wide area network, such as the Internet. The credit bureau receives this request, and may, if necessary, charge and/or authenticate the requestor by methods known in the art.
Next, in block 201, the credit bureau may either retrieve cached, precalculated, and/or precompiled credit data, report, score, and/or attributes about the consumer, or create a report on the fly by accessing specific credit information for a consumer. For example, based on information periodically collected by the credit bureau 108 from raw data 166 sources disclosed above, the credit bureau 108 may compile credit information into a credit report, wherein the data may be organized by credit categories such as credit usage, payment history, age of accounts, types of accounts, and credit inquiries, among others.
Moving to block 202, the credit bureau 108 may then use the collected credit information to calculate a credit score, based on a proprietary or publicly-known formula, using credit data associated with various credit categories in a predetermined proportion, for example. The credit bureau may also calculate and/or create the attributes that are often associated with a credit report. These attributes may be summary variables that summarize data related to individual accounts. For example, one summary attribute may be a calculation of the total max credit for all credit card accounts.
In block 203, the credit report, the credit score, and/or the summary attributes may be transmitted back to the requestor, such as the credit report system 100, and may be stored within the requestor's data storage such as a hard drive. In block 204, any additional attributes to be used in generating the various user interfaces of the credit summary user interface (e.g., by the client device and/or the credit report system) may be calculated by the credit report system (or alternatively, these attributes may be calculated at the client computing device 162). Such a calculation is based on the information received by the requestor such as the credit score, credit report information (e.g. account trade lines, etc), and received attributes. These may be different summary attributes than the default summary attributes.
Next, in block 205, the credit report, credit score, and all required attributes may be transmitted to the computing device 162 if necessary, and stored within its data storage 162. In other embodiments, the actual credit data may not be transmitted to the computing device 162 and, rather, software code (e.g., HTML, Java, Perl, Ruby, Python, etc.) may be transmitted to the computing device 162. For example, code that is usable by the computing device 162 to render the credit summary user interface may be transmitted, without transmitting a data structure that separately includes the actual credit data.
In some embodiments, the system distinguishes between the initial transmission of credit data required for user interfaces, and subsequent transmissions of user interface data so that it may transmit only portions that are necessary to update a spin-wheel user interface data for a new credit category. This may be done, for example, using an XMLHttpRequest (XHR) mechanism, a data push interface, or other communication protocols.
Example Method of Displaying and User Interactions with a Spin-wheel User Interface
FIG. 3 illustrates a method implemented by the user interface module 110 and other related software and hardware that allows this user interactivity. In various embodiments, fewer blocks or additional blocks may be included in the process, or various blocks may be performed in an order different from that shown in FIG. 3.
In block 301, the client device receives the information from either credit report system 100 or another credit database or credit bureau, as described in FIG. 2. This information may then be stored for convenient access within the device during a user application sessions, or across user sessions. The data may be stored in a data structure using any number of formats such as a relational database, XML data, HTML data, common separated values (CSV) data, or other formats.
Throughout the method described in FIG. 3, the credit report system 100 or credit bureau 108 may transmit user interface data or credit report data, such as summary attributes, to the computing device 162. The updated data may be used then by the client computer to update the displayed user interface so that the user may see the information. For example, a user may relaunch the application and upon relaunch, the user interface module 110 may perform an additional request to refresh its stored credit report, credit score and/or summary data for a consumer in order to display the most up to date information. In some embodiments, after a selection of a new spin-wheel section (described below), the user interface module 110 may query the credit report system or credit database/bureau 108 for credit report and summary information to be displayed for that category in real-time. This may be accomplished using asynchronous methods, by way of example, AJAX or web services, or any remote API.
Next, in block 302, a credit summary user interface may be generated for a particular category. A credit summary user interface, such as the ones shown in FIGS. 4-8, may comprise a spin-wheel 420 divided into credit data sections (e.g., sections 403-407), a section indicator 413, and a credit category user interface 408.
The sections of the spin-wheel 420 may be generated by dynamically rendering the circular user interface (for example, interface 420 from FIG. 4 including middle section 402, and category sections 403-407). For example, category sections may be associated with credit categories such as number of credit inquiries, credit usage, payment history, age of accounts, and types of accounts. To determine a credit score, a credit bureau may weigh the impact of each credit category according to a formula. The weights of this formula may be known by the user interface module, by storing the weights within the computing device's 162 memory. In some embodiments, these weights may have been transferred to the computing device, with the formula data originating at the credit bureau 108 or the credit report system 100. The weights of the credit score formula may then be used to appropriately size each category section of the spin-wheel 420. For example, if 30% weight in the credit score is for credit usage data, then the credit usage section 407 of the spin-wheel 420 may be sized as 30% of the spin-wheel 420.
The credit score formula weights used may depend on the geographic location of a user. For example, because of differences in culture, education, standard of living, available credit, housing values, or other macro economic factors, a credit bureau may use a different credit formula for a user who lives in Topeka, Kansas, than a user who lives in Brooklyn, N.Y. This may include different weights for the credit score data categories in a credit score formula. The credit bureau 108 and/or the credit report system 100 may determine the appropriate location to use to determine the weights in a variety of ways, e.g., based on contact data of the consumer (e.g. primary house address of the specific consumer), or computing device 162 location based on GPS or IP address of the computing device. Based on the location, the appropriate weights may be selected by the credit bureau or credit report system 100 to send to the computing device 162. In some embodiments, the personal computing device 162 may select the appropriate formula weights to use, such as based on data received from the credit report system 100. For example, if the computing device 162 has a stored mapping of location to weights, then the computing device 162 may determine its location and the associated weights to use. These weights may then be used to dynamically scale the spin-wheel category sections and corresponding description text.
Alternatively, among other methods, the spin-wheel may be generated using pre-sized image templates. For example, if a credit score formula's category weightings are known, the sizes of the spin-wheel sections may be pre-sized according to the known weightings. In some embodiments, the user interface module may have multiple sets of image templates based on different formulas used by different credit bureaus, and the computing device 162 may select the appropriate templates using a mapping.
Center section 402 may also be generated by the user interface module 110. In some embodiments, the center section 402 of the spin-wheel interface 420 may display the consumer's credit score, the date the score was last updated, the risk level associated with the score, and/or other data associated with the consumer. User interface module 110 may access a mapping of risk levels (e.g. low, medium, high, etc) to various score levels. The score mapped risk level associated with the credit score may then be displayed. In some embodiments, the risk level may be colored based on the relative risk level of the specific consumer (e.g. red for high, orange for medium, green for low, blue for very low, etc.). In some embodiments, when the spin-wheel is rotated, the center section 402 such that the text remains upright.
Other portions of the spin-wheel user interface may then be generated by the user interface module, for example, the section indicator 413 and credit category user interface 408 may be displayed on the computing device's display screen (e.g. a touch screen).
Moving to block 303, the credit category user interface may be updated to include information associated with the particular data in the selected credit category (e.g., the credit category indicated by the section indicator 413). A number of credit report fields, summary attributes, and/or custom attributes, associated with a particular category, may be selected by a programmer, user, or administrator for display within the credit category user interface 408. For example, for the credit usage category, within credit category user interface 408, the attribute associated with total credit used 414 may be displayed. Likewise, values 410 of the attributes associated with credit available, total credit and retail credit debt and total credit limit may also be displayed. The credit information associated with the category may also allow for the dynamic display of pie charts based on the information associated with the category. For example, the relative amount of credit used may be displayed in a pie chart 409 according to its makeup of revolving debt and remaining credit available.
In addition to credit information and attributes derived from a credit report, information not stored within the credit report and associated with the credit category may also be displayed. For example, text used to describe each attribute may be stored in an image template for use with its associated credit category. Alternatively, the computer device 162 and/or credit report system 100 may store mappings of descriptions for credit categories or attributes and credit data associated with those credit categories or attributes. For example, the text displayed the “My Credit Used” and “Credit Available”, etc., may be associated with attributes or data values received. Data associated with the credit category, and not a specific attribute, may also be displayed and associated within the window (such as category description text 415).
Such associations may be dynamic based on the received data from the credit report, or static. For example, description of a category may be considered static text, whereas attribute values derived from a consumer's credit report may be dynamic text. Dynamic text associations may be updated when new credit data is received by computing device 162. For example, variables or database entries, stored in memory or long term storage of the user interface module and/or computing device 162 and associated with credit categories, may be altered to reflect values of received credit data. These values may then be used for display when a specific category is selected.
Next, in block 304, the user interface module 110 may then receive input from a touch screen on the computing device 162, or any other user input device. For example, using a touch screen, a user may press and hold a section of the spin-wheel 420. For example, a user may touch and hold down their finger 416 on the spin-wheel as depicted in FIG. 4. The user may then move their touched finger vertically (and/or horizontally or diagonally) on the touch screen. By doing so, as described in block 305, the user interface module 110 may rotate the wheel in a direction that corresponds to the touched finger (e.g. a swipe). For example, if a user dragged their finger vertically up in FIG. 4, the user interface module 110 may initiate display of a counterclockwise rotation of the spin-wheel 420. If the user dragged their finger down in FIG. 4, the user interface module may initiate display of a clockwise rotation of the spin-wheel 420. The spin-wheel's exact movement need not match the finger movement exactly, but it may be desirable to rotate the spin-wheel in the same general direction as finger movement. In some embodiments, the spin-wheel may be rotated by tracking the finger on the touch screen in a rotational movement around the center section, instead of strictly vertical. The movement of the finger need only identify whether to rotate the wheel in a counterclockwise or clockwise fashion.
Once rotation of the spin-wheel 420 has ceased, the section indicator 413 will point to a particular section (and related category) within the spin-wheel 420. For example, in FIG. 4, if the spin-wheel was rotated counterclockwise by touch input, the section indicator may eventually point to the Age of Accounts section 403 instead of the Credit Usage section 407.
Next, in block 306, when the section indicator 413 points to a new section (or when the user's touch is removed and the section indicator points to a new section), the credit category user interface 408 may be updated with information associated with the corresponding credit category. Thus, if the section indicator 413 points to the Age of Accounts section 403, the credit category user interface 408 may be updated with credit data associated with Age of Accounts of the particular user. FIG. 5 illustrates one example of credit data associated with Age of Accounts that may be displayed in the credit category user interface 408. This may involve displaying the age of the user's oldest account and/or an average age of the user's accounts. FIGS. 4-8 show various examples of credit information categories that may be selected, thus causing the credit category user interface to be updated with credit data of the particular user associated with the different credit categories.
In some embodiments, the information displayed in the credit category user interface may be interactive and linked to more detailed consumer credit information contained within a credit report. For example, in block 307 of FIG. 3 some embodiments may receive a touch screen input over the summary information. By way of example, FIG. 4 displays a credit category user interface 408 containing information about credit usage. This window may include summary information about credit usage in various types of debt, such as real estate and other debt, installment debt, and credit and retail card debt. This information may be calculated by using summary attributes, or custom credit summary attributes calculated by the personal computing device 162 or the credit report system 100.
In some embodiments, the user interface module 110 may be configured to associate specific detailed information in a credit report with the summary information displayed in the credit category user interface. Using the example above, the credit and retail card debt and its associated displayed value may be linked to data in the credit report. By way of illustration, when a user touches (or clicks) a location on or near the summary description text or value for “credit and retail card debt,” the user interface module may launch an associated user interface (such as the one illustrated in FIG. 9), where the user may now be shown associated detailed account information.
In block 307, if a user touches the specific category of information or corresponding value, then information about that attribute or category may be displayed in block 308. For example, once a user touches “credit and retail card debt,” that user may be shown the their Chase Manhattan 900, Charles Schwab 901, and Macy's 902 (FIG. 9) open retail and credit card accounts. Information about the accounts status may be displayed, including their credit balances, whether those accounts are current, the type of account, and include a clickable or touchable link (e.g. 903). If the link is followed, the user interface module 110 may display trade line account information for the specific account, such as specific transactions for a credit card.
The location at which specific credit information about a consumer is placed within the user interfaces associated with the visual circular rotational interface may also vary in various embodiments. For example, additional credit information and/or summary credit data may be displayed within a selected slice/section. In another embodiment, additional credit information and/or summary credit data may be shown in an internal window within the user's mobile application or web browser. In other embodiments, additional credit information and/or summary credit data may be shown in a separate pop-up window. In another embodiment, additional credit information and/or summary credit data may be shown on a separate web page, or in a separate application.

Example User Interfaces

FIGS. 4-8 illustrate a sample credit summary user interface as user interfaces with the various user interface controls within the credit summary user interface. In various embodiments, the user interfaces shown in FIGS. 4-8 may be presented as a web page, as a mobile application, as a stand-alone application, or by other communication means. In other embodiments, analogous interfaces may be presented using audio or other forms of communication. In an embodiment, the interface shown in FIGS. 4-8 are configured to be interactive and respond to various user interactions. Such user interactions may include clicks with a mouse, typing with a keyboard, touches and/or gestures on a touch screen, voice commands, and/or the like. As one skilled in the art would recognize, the systems and methods described herein are compatible with various types of input in addition to, or as a replacement for, the touch screen input described.
As described above, FIG.4 illustrates a credit summary user interface 400 that includes a spin-wheel user interface 420 and a credit category user interface showing information related to a “Credit Usage” 411 category for a specific individual consumer (who in some embodiments may be the user of the client computing device 162 or another individual). Various summary attributes and other data related to the credit category for the individual consumer may be displayed when the credit usage section 407 of the spin-wheel 420 is selected (e.g., by rotating the spin-wheel 420 so the section indicator 413 points to the credit usage section 407. The credit category user interface 408 may display the approximate weight of a currently selected category in generation of the user's credit score, a general description of the category (including a description of how it impacts your score), summary data (e.g. credit attributes), any default summary attributes, and/or custom attributes. For example, in the embodiment of FIG. 4, credit usage information includes a total credit used out of available credit, an amount of which is revolving debt or available credit, an amount of credit and retail debt available, and a total credit limit in area 410, as well as a percentage of total credit used 414, among others. Alternatively, or in combination, this information may be dynamically rendered using a pictorial graph such as a pie chart 409. For example, in pie chart 409, it depicts revolving debt in one section of a pie chart out of the total credit available. Other credit information may also be displayed as it pertains to the specific consumer. For example, the amount of total debt, real estate debt, installment debt, credit and retail card debt, and revolving debt may be displayed.
In some embodiments, the “age of accounts” 501 may be a credit category that can be selected by the spin-wheel, as depicted in FIG. 5. Like the user interfaces illustrated in FIG. 4, the user interface module 110 may display the percentage weight of impact that data in the age of accounts category has on the consumer's credit score, and display a description of the age of accounts category (including a description of how it impacts your score). It may also display the oldest age of an account for a credit user, and display a comparison to the national average consumer's age of their oldest account. The data received in order to make that comparison may be compiled in a credit bureau 108 or the credit report system 100 and be transferred to and received by the computing device 162. Similarly, an average age of all accounts of a consumer may be displayed, with a similar comparison being performed 506. In addition, other user interface elements, such as the “view my accounts” button 504 may be displayed that link to other information in a credit report. In this case, the “view my accounts” button may be a user interface screen such as the one shown in FIG. 9 where all accounts for a consumer may be displayed.
In some embodiments, the “types of accounts” 601 may be a credit category that can be selected by the spin-wheel, as depicted in FIG. 6. Like the user interfaces illustrated in FIG. 4, the user interface module 110 may display the percentage weight of impact that data in the types of accounts category has on the consumer's credit score, and display a description of the types of accounts category (including a description of how it impacts your score). Section 603 of the credit summary display window may contain an indicator of quantity and/or quality of various types of accounts, such as open real estate loans (mortgages, refinanced loans, etc.), open installment loans (auto loans, student loans, etc.), open credit cards (VISA, mastercard, etc.), and open retail cards (gas cards, department store cards, etc.). Such an indicator may be a color grading or other representation of high, medium high, medium, medium low, low quality, etc. Or, as displayed the quality grading may be represented in a series of symbols such as the shown stars, where more stars equals higher quality of accounts. The quality may be determined by accessing summary credit score attributes indicating the quality of accounts or analyzing the credit report. Such analysis may be performed by either the computing device 162, the credit report system 100, or the credit bureau 108. The results may then be transferred to the computing device 162 if necessary.
In some embodiments, the “payment history” 701 may be a credit category that can be selected by the spin-wheel, as depicted in FIG. 7. Like the user interfaces illustrated in FIG. 4, the user interface module 110 may display the percentage weight of impact that the payment history category may have on the consumer's credit score, and display a description of the payment history category (including a description of how it impacts your score). Information about specific summary attributes related to payment history, such as description text and a value, may be displayed in the credit category user interface 703. The display may include a short description of the summary attribute, a summary quantity related to the attribute for the specific consumer, a long description text of the attribute, and whether the attribute value has a positive or negative impact on credit score. Such attributes may include whether payments on accounts are ever late, the time since the last late payment, whether any accounts are out for collection, the worst current status, outstanding legal records concerning payment history, and the worst status ever of an account, among others not shown. Whether the value has a positive or negative value on credit score may be represented by an icon to represent status, such as a check mark for a positive impact (or lack of negative impact), and an exclamation point for a negative impact.
In some embodiments, the “credit inquiries” 801 may be a credit category that can be selected by the spin-wheel, as depicted in FIG. 8. Like the user interfaces illustrated in FIG. 4, the user interface module 110 may display the percentage weight of impact that the inquiries category may have on the consumer's credit score, and display a description of the inquiries category (including a description of how it impacts your score). The credit data summary window may indicate, using a visual indicator such as a sub window or icons, the amount of credit inquiries of a specific consumer's credit report. For example, in FIG. 8, the example consumer has only one inquiry on his or her credit report, as indicated by the sub window 804 and the number icon the sub window is pointed to. The number of credit inquiries may be correlated with an amount of credit risk in the user interface , such as “Low Risk” as displayed in sub window 804. The associated credit risk may be color coded. For example, the “1” inquiry indicator may be green to indicate low risk, with the colors gradually transitioning to a red icon for 8+, corresponding to high risk. The amount of risk corresponding to the indicator may be determined by the user interface module 110, the credit report system 100, or the credit bureau 108, and transferred to computing device 162 if necessary.
Each individual piece of information, both the description and/or the value displayed for all the summary window data, may be linked to specific credit data in a consumer's report that may be displayed, as described under FIG. 3.
In addition to comparison of national averages as shown in FIG. 5, the spin-wheel interface in general may also be used to display other credit information, such as a spin-wheel credit user interface that a user could use to browse the average “good score” consumer credit attributes/summary information, (e.g., a score master, see incorporated provisional). For example, in some embodiments, the center of the credit wheel may display an indicator that a consumer is or is not considered a score master. Additionally, it may display a potential score master's minimum, top, or average score, and/or risk associated with that score. The credit category user interface 408 may contain example information about a credit master. For example, in FIG. 4, where it lists 50% credit used 414, a score master's percentage of credit used could be displayed alongside the consumer's percentage of credit used so that a user can make an easy comparison and decide to lower or raise their available credit in the future. As another embodiment, an example or average score master's complete credit information may be displayed in the spin-wheel interface 420 instead of a consumer's information, and may display information about an average score master or example score master in the credit category user interface 408 when a particular section is selected.
In some embodiments, the spin-wheel sections and/or the center area may be altered visually to indicate strengths and/or weaknesses of a consumer's credit information. For example, the credit usage information in the credit category user interface 408 in FIG. 4 may be certain color, such as green, to indicate a credit score strength if the data within that category impacts the credit score positively. These colors may be a part of a continuum of colors where relative strengths and weaknesses can be displayed. Another category of the spin-wheel 420, for example payment history category 406 as shown in FIG. 7, may be red or any color associated with negativity if a consumer's payment history information negatively affects a consumer's credit score. Additionally, information within the credit category user interface 408 may be color coded to indicate to a user whether a certain input within a credit category affects a credit score positively or negatively, as depicted in FIG. 8 showing summaries about “collection accounts”, “legal records”, “accounts ever late”, etc.

Example System Implementation and Architecture

FIG. 10 is a block diagram showing an embodiment of computing device 162, which may be in communication with network 160 and various computing systems, such as credit report system 100 and credit bureau/database 108, that are also in communication with the network 160. The computing device 162 may be used to implement systems and methods described herein.
As described above, some embodiments may include portions that are executed by the credit report system 100 and/or by the computing device 162, or are entirely executed by the credit report system 100 or the computing device 162. Thus, discussion herein of any structure (e.g. cpu, memory, etc) of the computing device 162 or operations performed by the computing device 162 or user interface module 110 may be equally applied to the credit report system 100, Furthermore, other computing systems may also perform all or some of the processes discussed with reference to the user interface module 110.
The computing device 162 includes, for example, a personal computer that is IBM, Macintosh, iOS, Android or Linux/Unix compatible or a server or workstation. In one embodiment, the computing device 162 comprises a server, a laptop computer, a smart phone, a personal digital assistant, a kiosk, or an media player, for example. In one embodiment, the exemplary computing device 162 includes one or more central processing unit (“CPU”) 905, which may each include a conventional or proprietary microprocessor. The computing device 162 further includes one or more memory 930, such as random access memory (“RAM”) for temporary storage of information, one or more read only memory (“ROM”) for permanent storage of information, and one or more mass storage device 920, such as a hard drive, diskette, solid state drive, or optical media storage device. Typically, the modules of the computing device 162 may be connected to the computer using a standard based bus system 980. In different embodiments, the standard based bus system could be implemented in Peripheral Component Interconnect (“PCI”), Microchannel, Small Computer System Interface (“SCSI”), Industrial Standard Architecture (“ISA”) and Extended ISA (“EISA”) architectures, for example. In addition, the functionality provided for in the components and modules of computing device 162 may be combined into fewer components and modules or further separated into additional components and modules, and executed in software, hardware, or a combination of hardware and software.
The computing device 162 is generally controlled and coordinated by operating system software, such as iOS, Android, Chrome OS, Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix, Linux, SunOS, Solaris, iOS, Blackberry OS, or other compatible operating systems. In Macintosh systems, the operating system may be any available operating system, such as MAC OS X. In other embodiments, the computing device 162 may be controlled by a proprietary operating system. Conventional operating systems control and schedule computer processes for execution, perform memory management, provide file system, networking, I/O services, and provide a user interface functionality usable by the user interface module 110, such as a graphical user interface (“GUI”), among other things.
The exemplary computing device 162 may include one or more commonly available input/output (I/O) devices and interfaces 910, such as a keyboard, mouse, touchscreen, and printer. In one embodiment, the I/O devices and interfaces 910 include one or more display devices, such as a monitor or touchscreen 940, that allows the visual presentation of data to a user. More particularly, a display device provides for the presentation of GUIs, application software data, and multimedia presentations, for example. The computing device 162 may also include one or more multimedia devices, such as speakers, video cards, graphics accelerators, and microphones, for example.
In the embodiment of FIG. 10, the I/O devices and interfaces 910 provide a communication interface to various external devices. In the embodiment of FIG. 10, the computing device 162 is electronically coupled to a network 160 (as shown in FIG. 1), which comprises one or more of a LAN, WAN, and/or the Internet, for example, via a wired, wireless (such as 802.11 networks or a cell phone network), or combination of wired and wireless, communication link. The network 160 communicates with various computing devices and/or other electronic devices via wired or wireless communication links.
In some embodiments information may be provided to the computing device 162 over the network 160 from a credit report system 100 and/or a credit bureau or database 108. Similarly, in some embodiments, information may be provided to the credit report system 100 over the network 160 from a credit bureau or database 108. The credit report system 100 and the credit bureau/database 108 may include one or more internal and/or external data sources. The data sources may include internal and external data sources which store, for example, credit bureau data and/or other consumer data. In some embodiments, one or more of the databases or data sources may be implemented using a relational database, such as Sybase, Oracle, CodeBase and Microsoft® SQL Server as well as other types of databases such as, for example, a flat file database, an entity-relationship database, and object-oriented database, and/or a record-based database.
In the embodiment of FIG. 10, the computing device 162 includes a user interface module 110 that may be stored in the mass storage device 920 as executable software codes that are executed by the CPU 905. This and other modules in the computing device 162 may include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. In the embodiment shown in FIG. 10, the computing device 162 is configured to the execute the user interface module 110 in order to for example, receive credit report and summary attributes regarding a specific consumer, generate a spin-wheel user interface, access and display category data for a specific consumer based on a spin-wheel section selection, receive touch screen input, rotate the spin-wheel according to the received input, display new credit summary category data for the specific consumer associated with the selected category, and perform other methods as described herein (such as the processes described with respect to FIGS. 2 and 3).
User interface module 902 may generate and render circular rotational visual user interfaces based on upon the received credit information. By interacting with these user interfaces, a user of computing device 162 may view various information about credit data categories and see how their credit data is affecting their credit score. Exemplary embodiments of user interfaces presented by such a section is shown in FIGS. 4-8.
In general, the word “module,” as used herein, refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, Java, Lua, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamic link library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software modules configured for execution on computing devices may be provided on a computer readable medium, such as a compact disc, digital video disc, flash drive, magnetic disc, or any other tangible medium, or as a digital download (and may be originally stored in a compressed or installable format that requires installation, decompression or decryption prior to execution). Such software code may be stored, partially or fully, on a memory device of the executing computing device, such as the computing device 162, for execution by the computing device. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Generally, the modules described herein refer to logical modules that may be combined with other modules or divided into sub-modules despite their physical organization or storage.
Like the computing device 162, credit report system 100 and credit bureau/database 108 may comprise similar computing hardware, software, and functionality as described above for computing device 162.

Other

Each of the processes, methods, and algorithms described in the preceding sections may be embodied in, and fully or partially automated by, code modules executed by one or more computer systems or computer processors comprising computer hardware. The code modules may be stored on any type of non-transitory computer-readable medium or computer storage device, such as hard drives, solid state memory, optical disc, and/or the like. The systems and modules may also be transmitted as generated data signals (for example, as part of a carrier wave or other analog or digital propagated signal) on a variety of computer-readable transmission mediums, including wireless-based and wired/cable-based mediums, and may take a variety of forms (for example, as part of a single or multiplexed analog signal, or as multiple discrete digital packets or frames). The processes and algorithms may be implemented partially or wholly in application-specific circuitry. The results of the disclosed processes and process steps may be stored, persistently or otherwise, in any type of non-transitory computer storage such as, for example, volatile or non-volatile storage.
The various features and processes described above may be used independently of one another, or may be combined in various ways. All possible combinations and subcombinations are intended to fall within the scope of this disclosure. In addition, certain method or process blocks may be omitted in some implementations. The methods and processes described herein are also not limited to any particular sequence, and the blocks or states relating thereto can be performed in other sequences that are appropriate. For example, described blocks or states may be performed in an order other than that specifically disclosed, or multiple blocks or states may be combined in a single block or state. The example blocks or states may be performed in serial, in parallel, or in some other manner. Blocks or states may be added to or removed from the disclosed example embodiments. The example systems and components described herein may be configured differently than described. For example, elements may be added to, removed from, or rearranged compared to the disclosed example embodiments.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Any process descriptions, elements, or blocks in the flow diagrams described herein and/or depicted in the attached figures should be understood as potentially representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of the embodiments described herein in which elements or functions may be deleted, executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those skilled in the art.
All of the methods and processes described above may be embodied in, and partially or fully automated via, software code modules executed by one or more general purpose computers. For example, the methods described herein may be performed by the credit report system 100, consumer computing device 162, and/or any other suitable computing device. The methods may be executed on the computing devices in response to execution of software instructions or other executable code read from a tangible computer readable medium. A tangible computer readable medium is a data storage device that can store data that is readable by a computer system. Examples of computer readable mediums include read-only memory, random-access memory, other volatile or non-volatile memory devices, CD-ROMs, magnetic tape, flash drives, and optical data storage devices.
It should be emphasized that many variations and modifications may be made to the above-described embodiments, the elements of which are to be understood as being among other acceptable examples. All such modifications and variations are intended to be included herein within the scope of this disclosure. The foregoing description details certain embodiments of the invention. It will be appreciated, however, that no matter how detailed the foregoing appears in text, the invention can be practiced in many ways. As is also stated above, it should be noted that the use of particular terminology when describing certain features or aspects of the invention should not be taken to imply that the terminology is being re-defined herein to be restricted to including any specific characteristics of the features or aspects of the invention with which that terminology is associated. The scope of the invention should therefore be construed in accordance with the appended claims and any equivalents thereof.

Claims

1. (canceled)

2. A system comprising:

a memory; and

one or more processors configured to:

receive payment history data, wherein the payment history data comprises at least consumer's payment history associated with respective categories of information;

generate user interface data configured for display on a touch sensitive computing device, the user interface data configured to display a plurality of sections of a circular visual computer interface, wherein each section of the plurality of sections is associated with a category of information;

receive a selection of a section of the plurality of sections from the touch sensitive computing device;

update the user interface data to display a visual section indicator that indicates one of the plurality of sections as selected within the circular visual computer interface;

access the payment history data associated with the selected category of information; and

display summary information regarding at least a portion of the payment history data for the selected category of information associated with the selected section of the circular visual computer interface that is indicated as selected by the visual section indicator.

3. The system of claim 2, wherein each section of the plurality of sections is a predetermined size according to an associated category's weighting within a credit score algorithm.

4. The system of claim 2, wherein the user interface data is configured to depict the circular visual computer interface rotating in response to a dragged touch input on the displayed circular visual computer interface.

5. The system of claim 4, wherein the rotation causes the visual section indicator to indicate a particular section as selected by the circular visual computer interface.

6. The system of claim 2, wherein the user interface data is configured to cause rotation of the circular visual computer interface based on a user selection of a category.

7. The system of claim 2, wherein the visual selection indicator is of a respective color selected from a continuum of colors, the selected color presented in the corresponding section indicating a relative positive or negative effect of the credit information associated with the section.

8. The system of claim 7, wherein selecting the particular color comprises selecting a first color if the category of credit information associated with the particular section positively affects a consumer's credit score, or selecting a second color if the category of credit information associated with the particular section negatively affects the consumer's credit score.

9. The system of claim 2, wherein the displayed portion of the information associated with the selected section includes information describing one or more inputs usable to determine an effect on the consumer's credit score, wherein each input is presented, at least in part, as a particular color selected based on a positive or negative effect of the input.

10. The system of claim 2, wherein the user interface data is configured to respond to user interactions comprising voice commands.

11. A computer-implemented method comprising:

receiving payment history data, wherein the payment history data comprises at least consumer's payment history associated with respective categories of information;

generating user interface data configured for display on a touch sensitive computing device, the user interface data configured to display a plurality of sections of a circular visual computer interface, wherein each section of the plurality of sections is associated with a category of information;

receiving a selection of a section of the plurality of sections from the touch sensitive computing device;

updating the user interface data to display a visual section indicator that indicates one of the plurality of sections as selected within the circular visual computer interface;

accessing the payment history data associated with the selected category of information; and

displaying summary information regarding at least a portion of the payment history data for the selected category of information associated with the selected section of the circular visual computer interface that is indicated as selected by the visual section indicator.

12. The method of claim 11, wherein each section of the plurality of sections is a predetermined size according to an associated category's weighting within a credit score algorithm.

13. The method of claim 11, wherein the user interface data is configured to depict the circular visual computer interface rotating in response to a dragged touch input on the displayed circular visual computer interface.

14. The method of claim 13, wherein the rotation causes the visual section indicator to indicate a particular section as selected by the circular visual computer interface.

15. The method of claim 11, wherein the user interface data is configured to cause rotation of the circular visual computer interface based on a user selection of a category.

16. The method of claim 11, wherein the visual selection indicator is of a respective color selected from a continuum of colors, the selected color presented in the corresponding section indicating a relative positive or negative effect of the credit information associated with the section.

17. The method of claim 16, wherein selecting the particular color comprises selecting a first color if the category of credit information associated with the particular section positively affects a consumer's credit score, or selecting a second color if the category of credit information associated with the particular section negatively affects the consumer's credit score.

18. method of claim 11, wherein the displayed portion of the information associated with the selected section includes information describing one or more inputs usable to determine an effect on the consumer's credit score, wherein each input is presented, at least in part, as a particular color selected based on a positive or negative effect of the input.

19. method of claim 11, wherein the user interface data is configured to respond to user interactions comprising voice commands.