Matching Merchant Names from Transaction Data

Abstract

A computer system processes a merchant name from transaction data to determine a matched merchant name. The computer system retrieves a retrieved merchant name from transaction data, obtains a processed merchant name from the retrieved merchant name, and matches the processed merchant name to one of a collection of standard merchant names, where the retrieved merchant name may be a name variation of a standard merchant name. At least one character of the retrieved merchant name may be altered to obtain the processed merchant name. For example, characters may be deleted from the accessed merchant name or characters may be ignored from a portion of the retrieved merchant name.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to an Internet web site providing an online account statement web page having hyperlinks, and especially having hyperlinked special offer indicia for a special offer related to a transaction entry on the online account statement.

2. Related Art

Currently, credit card companies and the like provide online access for their customers to obtain information regarding a credit card account of the customer. The customer can access the information on the credit card account from a web site of the credit card company via the Internet. Such information generally available at a web site of a credit card company includes balance information, payment information, available cash, total minimum payment due, and a transaction history. Such web sites may also contain advertisements having a hyperlink to the advertising merchant. However, such advertisements are not related to the transactions of the customer. Instead, the advertisements are, for example, displayed on each web page viewed by a customer or displayed on a revolving basis with other advertisements on various web pages viewed by customers.

SUMMARY OF THE INVENTION

Aspects of the embodiments address one or more of the issues mentioned above by providing methods, computer readable media, and apparatuses for retrieving a retrieved merchant name from transaction data, obtaining a processed merchant name from the retrieved merchant name, and matching the processed merchant name to one of a collection of standard merchant names.

With another aspect of the embodiments, at least one character of the retrieved merchant name may be altered to obtain the processed merchant name. With some embodiments, at least one character may be deleted from the retrieved merchant name or characters may be ignored from a portion of the retrieved merchant name.

With another aspect of the embodiments, the retrieved merchant name may be a name variation of a standard merchant name.

With another aspect of the embodiments, a processing system accesses an accessed merchant name from a transaction data structure, compares the accessed merchant name with entry names in the merchant look-up table, repeats the comparing until the retrieved merchant name matches one of the entry names in the merchant look-up table, and determines a determined merchant name from the matched entry.

Aspects of the embodiments may be provided in a computer-readable medium having computer-executable instructions to perform one or more of the process steps described herein.

These and other aspects of the embodiments are discussed in greater detail throughout this disclosure, including the accompanying drawings.

Definitions

A “computer” refers to any apparatus that is capable of accepting a structured input, processing the structured input according to prescribed rules, and producing the results of the processing as output. Examples of a computer include: a computer; a general purpose computer; a supercomputer; a mainframe; a super mini-computer; a mini-computer; a workstation; a micro-computer; a server; an interactive television; a web appliance; a telecommunications device with internet access; a hybrid combination of a computer and an interactive television; and application-specific hardware to emulate a computer and/or software. A computer can be stationary or portable. A computer can have a single processor or multiple processors, which can operate in parallel and/or not in parallel. A computer also refers to two or more computers connected together via a network for transmitting or receiving information between the computers. An example of such a computer includes a distributed computer system for processing information via computers linked by a network.

A “computer-readable medium” refers to any storage device used for storing data accessible by a computer. Examples of a computer-readable medium include: a magnetic hard disk; a floppy disk; an optical disk, such as a CD-ROM and a DVD; a magnetic tape; a memory chip; and a carrier wave used to carry computer/readable electronic data, such as those used in transmitting and receiving e-mail or in accessing a network.

“Software” refers to prescribed rules to operate a computer. Examples of software include: software; code segments; instructions; computer programs; and programmed logic.

A “computer system” refers to a system having a computer, where the computer comprises a computer-readable medium embodying software to operate the computer.

A “network” refers to a number of computers and associated devices that are connected by communication facilities. A network involves permanent connections such as cables or temporary connections such as those made through telephone, wireless, or other communication links. Examples of a network include: an internet, such as the Internet; an intranet; a local area network (LAN); a wide area network (WAN); and a combination of networks, such as an internet and an intranet.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other features and advantages of the invention will be apparent from the following, more particular description of a preferred embodiment of the invention, as illustrated in the accompanying drawings. The left most digits in the corresponding reference number indicate the drawing in which an element first appears.

FIG. 1 illustrates a flowchart of an exemplary embodiment of the invention.

FIG. 2 illustrates an exemplary enroll/login web page.

FIG. 3 illustrates an exemplary account selection web page.

FIG. 4 illustrates an exemplary online account statement web page.

FIG. 5 illustrates an exemplary merchant home page.

FIG. 6 illustrates an exemplary merchant web page with links to the merchant web site.

FIG. 7 illustrates an exemplary merchant web page with a link to a merchant special offer web page.

FIG. 8 illustrates a plan view for a computer system for the invention.

FIG. 9 illustrates an exemplary merchant entry for the merchant database.

FIG. 10 illustrates a flow chart for analyzing a merchant name in the transaction history.

FIG. 11 illustrates an exemplary online account statement web page for a second exemplary embodiment of the invention.

FIG. 12 illustrates an exemplary merchant web page for the second exemplary embodiment.

FIG. 13 illustrates an exemplary merchant entry for the merchant database for the second exemplary embodiment.

FIG. 14 illustrates an optional exemplary merchant entry for the merchant database for the second exemplary embodiment.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENT OF THE INVENTION

An exemplary embodiment of the invention is discussed in detail below. While specific exemplary embodiments are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations can be used without parting from the spirit and scope of the invention. The embodiments and examples discussed herein are non-limiting examples.

A company provides online account statements for its customers via a web site provided by or for the company. The company can be, for example, a credit card company, a debit card company, a bank, a savings and loan, a brokerage firm, a financial institution, a department store, a store selling goods and/or services, a catalogue merchant, a telecommunications company, a utility company, an Internet-based company, a rewards program provider, a technology provider for such companies, or the like. After initially enrolling with the web site, a customer can log in to the web site to view an online account statement for one or more accounts with the company. For an account selected, or if the customer has a single account with the company, an online account statement web page is provided for the account. The online account statement web page includes a transaction history of the account.

The transaction history includes hyperlinked indicia for transactions listed in the transaction history. The linked indicia includes, for example, hyperlinked merchant names and hyperlinked special offer indicia. The hyperlinked special offer indicia provide the customer with special offers from merchants listed in the transaction history and/or from related and/or competing merchants. The hyperlinked special offers identified for the customer are related to the transaction entries in the transaction history of the online account statement web page for the customer. The special offers can be customized for the customer.

The special offer provided by the hyperlink of the online account statement can be provided only to customers who are enrolled with the online account statement service. The special offer can be redeemable, for example, online at the merchant web site, at a physical merchant location by a printable coupon, or via a telephone through use of a special tracking code.

FIG. 1 illustrates a flowchart for an exemplary embodiment of the invention. The flowchart illustrated in FIG. 1 is with reference to a web site provided by or for a company providing online account statements for its customers. The invention is provided by a server side and not a client side in a client-server relationship.

FIG. 1 is discussed in relation to FIGS. 2-7, which illustrate exemplary web pages for an exemplary embodiment of the invention. For the exemplary embodiment illustrated with the FIGS. 2-7, the company is a credit card company, and the online account statement is an online credit card account statement.

In block 101 of FIG. 1, an enrollment/login web page is initially provided. An exemplary enroll/login web page for an exemplary embodiment of the invention is illustrated in FIG. 2. This initial page is provided to all customers desiring access to their online account statements.

In block 102, if a customer desiring to access the online account statement is accessing the web site for the first time, the customer is enrolled. A customer is enrolled by entering, for example: a valid account number (e.g., area 201); verifying specific pieces of information (e.g., card verification code (CVC), card verification value (CVV), mother's maiden name, and/or social security number); and selecting a user name and a password. Upon enrollment, the customer accepts terms and conditions for receiving the online account statement.

In block 103, once the customer is enrolled, the customer can log in. To log in, the customer is required to enter a correct user name and password combination. If the customer is already enrolled, the customer can log in (e.g., area 202).

The enroll/login web page can also provide for accepting users who are not yet customers of the company (e.g., area 203).

Once logged in, the web site determines in block 104 if the customer has more than one account. If the customer has more than one account, flow proceeds to block 105. If the customer has one account, flow proceeds to block 107.

In block 105, an account selection web page is provided as an interstitial web page. An exemplary account selection web page for an exemplary embodiment of the invention is illustrated in FIG. 3. The account selection web page lists the multiple accounts of the customer (e.g., area 301). The customer is requested to select one of the displayed accounts. In block 106, the web site receives an account selection from the customer. Once the account selection is received, flow proceeds to block 107.

In block 107, an online account statement web page is provided for the customer. An exemplary online account statement web page is illustrated in FIG. 4 for an exemplary embodiment of the invention. The online account statement page can include customer information for the account, for example: customer name (e.g., area 401); billing address (e.g., area 402); telephone number; balance information for the account (e.g., area 403); payment information for the account (e.g., area 404); available credit for the account (e.g., area 405); a total minimum payment due and corresponding due date for the account (e.g., area 406); and any current offers being promoted by the company unrelated to the transaction history of the customer (e.g., conventional advertising of products and/or services of the company). The online account statement may also include advertisements form third parties, which are unrelated to the transaction history of the customer (e.g., areas 407 and 408).

The online account statement includes a transaction history (e.g., area 409). The transaction history can be for current activity or past activity of the account of the customer. Current activity can include, for example, all activity in the account since the most recent statement date. Past activity of the account can include, for example, activity from one or more previous statements, from one or more payments on the account, from a year (e.g., a year end account report), from a rolling period (e.g., the past 4 weeks or the past 12 months), or from a predetermined or customer selected date range. As an option, an interstitial web page can be provided to the customer with a selection of current activity, for example, since the most recent statement, past activity from one or more previous statements, or activity over a date range.

The transaction history of the online account statement includes zero or more transaction entries (e.g., area 410). Each transaction entry corresponds to a discrete activity of the account. Each transaction entry in the transaction history can include fields for, for example: a posting date (e.g., area 411), which is the date the entry was posted to the account; a transaction date (e.g., area 412), which is the date the merchant entered as the date of the transaction; a reference number (e.g., area 413), which is a reference number associated with the transaction to identify individual transactions for merchant processing, settlement, and dispute; a card type (e.g., area 414), which is an identifier of the type of card, such as MC for a MasterCard credit card, V for a Visa credit card, A for an American Express credit card, and a D for a Discover credit card; a category (.g., area 415), which is a category designating how the charge is to be treated for purposes of calculating finance charges, such as, C for retail purchases at the annual percentage rate (APR) for retail purchases and A for transferred balances at the APR for transferred balances; a merchant description (e.g., area 416), including, for example, a merchant name (e.g., “GAP #0611/THE”), a merchant address (e.g., “WILMINGTON Del.”), and an optional merchant telephone number; a charge (e.g., area 417) for the amount charged to the account for the transaction entry; and a credit (e.g., area 418) for the amount credited to the account for the transaction entry.

One or more of the transaction entries in the transaction history are displayed as hyperlinked transaction entries. A hyperlinked transaction entry can be designated, for example, by varying the format of the transaction entry (e.g., underline, bold, italics, color, and/or font size) for some or all of the transaction entry. When the user clicks on the hyperlinked transaction entry, a merchant web page is opened that contains information specific to that merchant and/or the transaction entry. In FIG. 4, a hyperlinked transaction entry is designated via a hyperlinked merchant name. FIG. 4 includes non-hyperlinked merchant names (e.g., area 419) and hyperlinked merchant names (e.g., area 420). For area 420, the exemplary hyperlinked merchant name is underlined (i.e., GAP #0611/THE) and in a different color than the rest of the transaction history.

Each transaction entry can include one or more hyperlinked special offer indicia related to the transaction entry. For example, the indicia can be a red icon shaped like a sales tag and having the word “SAVE” therein (e.g., area 421). The hyperlinked special offer indicia can be situated as part of the transaction entry. For example, the hyperlinked special offer indicia can be directly adjacent to, approximately next to, or collocated with the merchant name in the transaction entry. Other techniques can be used to draw attention to a special offer related to the transaction history, for example: a red icon shaped like a sales tag and having the word “VALUE” or other special offer word or words therein; a special icon (e.g., a gold star) to indicate a special offer or a special merchant; an icon indicating the type of savings (e.g., “%” indicating a percentage off or “$” indicating a credit or dollars off); or a rollover pop-up image and text box. By clicking on the hyperlinked special offer indicia, a merchant web page is opened that contains one or more special offers related to the respective transaction entry in the transaction history.

As an option, instead of opening a merchant web page, an online registration faun is provided when the customer clicks on the hyperlinked special offer indicia. The registration form can be for, for example: a product and/or a service of the merchant; a warranty; or a reservation (e.g., a reservation for a restaurant, a movie, a play, a concert, or travel). The registration form can be populated with information provided by the customer when the customer enrolled. For example, the name, telephone number, e-mail address, credit card number, and/or substitute credit card number of the customer obtained during enrollment of the customer can be used to populate the registration form. The customer can complete any additional information required on the registration form and can elect to send the registration form to the merchant. If the customer so elects, the registration form is passed to the merchant, and the merchant thereafter contacts the customer regarding the special offer.

For each different merchant name, each hyperlinked special offer indicia can have a different hyperlink (e.g., areas 421 and 422).

As an option, the same merchant name can have different hyperlinked special offer indicia. With this option, the special offer for the transaction entry can be selected based on, for example, a rolling serial determination, a random determination, a determination based on an analysis of the transaction entry and/or the customer. For example, if the merchant is a company selling camping equipment, various special offers are available depending on the analysis of the transaction entry. For instance, if the transaction entry is for a customer having a transaction with the company, a special offer of free shipping is offered; if the transaction entry is for a customer having a transaction with a competitor of the company, a special offer of $5 off is offered; and if the transaction entry is for a customer having a transaction with a related merchant to the company (e.g., a campground), a special offer of free shipping and 10% off is offered.

As another option, the same merchant name can have one or more different hyperlinked special offer indicia associated therewith. Decisions on which special offers to offer the customer and how many can be selected are based on, for example, a rolling serial determination, a random determination, a determination based on an analysis of the transaction entry and/or the customer. For example, if the merchant is a company selling camping equipment, two special offers are selected. For instance, a first special offer of free shipping is offered from the merchant, and a second special offer is offered for a related merchant (e.g., a campground) for a free night at the campground if two are booked.

When the online account statement page is generated for the customer, the web site determines for each transaction entry in the transaction history whether the transaction entry is hyperlinked and whether a special offer is associated with the transaction entry. The selection of which transaction entries in the transaction history to hyperlink and which to provide special offers is discussed further below with respect to FIGS. 8-10.

As an option, the online account statement can include a hyperlinked special offer summary indicia. The indicia is hyperlinked to a web page that presents a listing and/or a description of all matched merchants having special offers related to the transaction history of the customer. The listing can be arranged, for example, chronologically per the transaction history, alphabetically, in a predetermined ranking based on arrangements between the merchants and the company, or the like. The listing can coincide with the date range in the transaction history or can be different (e.g., a predetermined date range, such as the last 6 months, or a customer selected date range).

As a further option, the hyperlinked special offer summary indicia can be a summary box in, for example, the heading of the online account statement. The summary box can identify the various merchants having special offers related to the transaction history of the customer. The summary box can include a personal message for the customer.

In block 108 of FIG. 1, the customer clicks on a hyperlink in the transaction history indicating a selection for a merchant web page, and the selection is received by the web server. For example, referring to FIG. 6, the customer clicks on a hyperlinked merchant name (e.g., “GAP NO 0611/THE” of area 420) or clicks on a hyperlinked special offer indicia (e.g., the “SAVE” tag of area 421).

In block 109, the merchant web page is provided to the customer. An exemplary merchant web page for an exemplary embodiment of the invention is illustrated in FIG. 5. The web server for the company with which the customer has the account, and not the web server for the merchant, generates the merchant web page. The merchant web page includes, for example: a merchant logo (e.g., area 501); a merchant description (e.g., area 502); a merchant name and a merchant address (e.g., area 503); a merchant telephone number (e.g., area 504); a merchant customer service telephone number (e.g., area 505); a hyperlinked merchant home page indicia (e.g., area 506); a hyperlinked merchant store locator web page indicia (e.g., area 507); a hyperlinked merchant customer service web page indicia (e.g., area 508); and a hyperlinked special offer indicia (e.g., areas 509 and 510). The hyperlinked special .offer indicia can be, for example, a stylized red tag having the word “SAVE” therein. Other types of indicia can be used as discussed above for the hyperlinked special offer indicia of the online account statement web page.

As an option, the merchant web page can include a hyperlinked dispute resolution indicia. With this feature, a dispute resolution regarding a transaction entry in the transaction history is initiated. The indicia is hyperlinked to, for example, a web page for the company (e.g., an e-form for the customer to fill out) or another web site to resolve the dispute. The hyperlinked dispute resolution indicia can also be provided as part of the online account statement.

In block 110, the web server receives a selection from the customer for one of the hyperlinks on the merchant web page. If the customer clicks on the hyperlinked merchant home page indicia (e.g., area 506), flow proceeds to block 111. If the customer clicks on the hyperlinked merchant store locator web page indicia (e.g., area 507), flow proceeds to block 112. If the customer clicks on the hyperlinked merchant customer service web page indicia (e.g., area 508), flow proceeds to block 113. If the customer clicks on the hyperlinked special offer indicia (e.g., area 509 or area 510), flow proceeds to block 114.

In block 111, the customer clicked on the hyperlinked merchant home page indicia, and the customer is linked to the merchant home page. An exemplary merchant web page with links to the merchant web site for an exemplary embodiment of the invention is illustrated in FIG. 6. By clicking on a hyperlinked merchant home page indicia (e.g., area 506), the merchant home page (e.g., area 601) is displayed.

In block 112, the customer clicked on the hyperlinked merchant store locator web page indicia on the merchant web page, and the customer is linked to the merchant store locator web page. Referring to the example in FIG. 6, by clicking on a hyperlinked merchant store locator web page indicia (e.g., area 507), the merchant store locator web page (e.g., area 602) is displayed.

In block 113, the customer clicked on the hyperlinked merchant customer service web page indicia on the merchant web page, and the customer is linked to the merchant customer service web page. Referring to the example in FIG. 6, by clicking on a hyperlinked merchant customer service web page indicia (e.g., area 508), the merchant customer service web page (e.g., area 603) is displayed.

In block 114, if the customer clicked on the hyperlinked special offer indicia on the merchant web page, the customer is linked to a merchant special offer web page. An exemplary merchant special offer web page for an exemplary embodiment of the invention is illustrated in FIG. 7. By clicking on a hyperlinked merchant home page indicia (e.g., area 509 or area 510), a merchant special offer web page (e.g., area 701) is displayed. The merchant special offer web page can be, for example: an advertisement for a special offer (e.g., a sale or a credit) from the merchant; a special offer customized to the customer; loyalty program information; a web page having hyperlinks for various products and/or services of the merchant; or an interstitial web page. The special offer provided on the merchant special offer web page can be used for online shopping with the merchant, a printable coupon for taking to the merchant, or information for use with a telephone sale with the merchant.

The merchant special offer web page can include a special offer code (e.g., area 702). The special offer code can be used by the customer for one or more additional transactions with the merchant. The special offer code can uniquely identify the special offer, the company providing the account to the customer, and/or the customer. In FIG. 7, the special offer code in area 702 is used in this example for online shopping with the merchant.

The merchant special offer web page can be established only to be available via navigating the online account statement. The merchant can use tracking codes obtained via the path navigation to the merchant special offer web page and beyond to fulfill the special offer and to report on one or more orders and/or closed sales.

As an option, the merchant special offer web page is for a special offer for a company different from the merchant identified in the transaction entry of the online account statement web page. Instead, the special offer can be from, for example: a subsidiary or related company; a partner company; a merchant selling a related and/or complimentary product and/or service (for example, if the customer purchased a boat, the related merchant sells nautical supplies or boat trailers); or a competitor of the merchant identified in the transaction entry. As an example, a transaction entry in the transaction history for a fine restaurant can have a hyperlinked special offer indicia from the restaurant itself, another fine restaurant in the same vicinity, and/or a gourmet foods distributor. To distinguish the types of special offers, hyperlinked special offer indicia from the merchant in the transaction entry can be one style, and hyperlinked special offer indicia from a merchant different from the one in the transaction entry can be another style (e.g., a different icon, color, or font).

As an option, and as discussed above, the merchant special offer web page can include special offers from one or more merchants.

As an option, the merchant special offer web page can include an active accept indicia with the special offer. The active accept indicia can be, for example, a radio button with the text “Accept Offer” or “Buy Now.” The active accept indicia can be, for example, located next to or incorporated with the special offer. If the customer clicks on the active accept indicia, the customer accepts the special offer, and an order is automatically placed with the merchant using the information provided by the customer when the customer enrolled. The enrollment information regarding the customer is transmitted to the merchant to fill the accepted special offer. The enrollment information of the customer transmitted to the merchant can include, for example: name, telephone number, e-mail address, credit card number or substitute credit card number, and/or expiration date of credit card. By clicking on the active accept indicia, the customer can accept the special offer without needing to navigate through additional web pages or the merchant's web site.

As an option, if the customer clicks on a hyperlinked special offer indicia in the online account statement web page (e.g., area 421), flow can proceed directly from block 108 to block 114 without displaying the merchant web page.

In blocks 111-114, the web pages created can be static web pages and/or dynamic web pages (i.e., web pages created on the fly). These web pages can be generated either by the web server of or for the company having the account with the customer or by the web site provided by or for the merchant presenting the material in the provided web page. The web pages are generated on the server side and not the client side. No additional software is needed by the customer on the client side to generate the web pages. The provided web page can be opened within the web browser used by the customer, or it can be opened in a separate window.

FIG. 8 illustrates a plan view for a computer system for implementing a web site of the invention. The computer system 801 includes a computer 802 for implementing the invention. The computer 802 includes a computer-readable medium 803 having software for implementing the invention and/or software to operate the computer 802 in accordance with the invention. The computer-readable medium 803 additionally includes a transaction database 804 and a merchant database 805. The merchant database 805 includes a merchant look-up table 806. The computer system 801 includes a connection to a network 807. A computer 808 also includes a connection to the network 807. The computer system 801 and the computer 808 communicate via the network 807.

In an exemplary embodiment, the computer system 801 implements a web server and provides web pages in accordance with the invention, and the network 807 is the Internet. The computer 808 includes a web browser, communicates with the web server implemented by the computer system 801, and receives web pages from the computer system 801. The server side (i.e., the computer system 801), and not the client side (i.e., the computer 808), provides the web pages. As an option, the computer 808 can be a computer system.

In FIG. 8, software, the transaction database 804, and the merchant database 805 are described and illustrated as part of the computer-readable medium 803. Alternatively, software, the transaction database 804, and the merchant database 805 can more generally be part of the computer 802 or the computer system 801.

In FIG. 8, the transaction database 804 and the merchant database 805 are illustrated as part of the computer 802. Alternatively, the transaction database 804 can be incorporated more generally as part of the computer system 801. Likewise, the merchant database 805 can be incorporated more generally as part of the computer system 801.

The transaction database 804 contains information for populating the online account statement web page (e.g., FIG. 4). For each customer, the transaction database 804 includes a transaction history for each account of each customer of the company. Each transaction history includes the transaction entries described above.

The merchant database 805 contains information for populating the merchant web page (e.g., FIG. 5). The merchant database 805 includes merchant entries for a number of merchants that can be identified in the transaction history in the online account statement. In generating the merchant web page in block 109, the computer system 801 accesses a merchant entry in the merchant database 805 to populate the merchant web page.

FIG. 9 illustrates an exemplary merchant entry 900 in the merchant database. The merchant entry 900 includes the following fields, for example: a merchant identification 901; a merchant name 902; a merchant address 903; a merchant description 904; a merchant logo path 905; a merchant corporate telephone number 906; a merchant corporate customer service telephone number 907; a merchant home page uniform resource locator (URL) 908; a merchant store locator web page URL 909; a merchant customer service web page URL 910; and a merchant special offer web page URL 911. For more than one special offer, additional merchant special offer web page URL's are provided. The additional special offers can be from the merchant and/or one or more other merchants. Other possible fields for the merchant entry include: a merchant rating URL (e.g., as available online from the Better Business Bureau (BBB)); additional merchant special offer web page URLs; special offer descriptions; merchant offer image path; and icon paths for a print button for printable coupon redemption, a telephone button for telephone coupon redemption, or a computer button for online coupon redemption. Each of the fields (or optionally zero or more of the fields) for the merchant entry 900 has an on/off indicator to control when the data is to be displayed on the merchant web page.

Referring to the exemplary merchant web page in FIG. 5, the merchant name 902 and the merchant address 903 are used to populate area 503. The merchant description 904 is used to populate area 502. The merchant logo path 905 is used to identify the path for displaying the merchant logo in area 501. The merchant corporate telephone number 906 is used to populate area 504. The merchant customer service telephone number 907 is used to populate area 505. The merchant home page URL 908 is used to provide the hyperlink for area 506. The merchant store locator web page URL 909 is used to provide the hyperlink for area 507. The merchant customer service web page URL 910 is used to provide the hyperlink for area 508. The merchant special offer web page URL 911 is used to provide the hyperlink for areas 509 and 510.

FIG. 10 illustrates a flow chart for analyzing a merchant name in the transaction history of the online account statement. Specifically, the flowchart is for determining whether a transaction entry in the transaction history should be indicated as a hyperlinked transaction entry (e.g., a hyperlinked merchant name) and whether a hyperlinked special offer indicia should be included with the transaction entry.

In block 1001, for each merchant name in each transaction entry in the transaction history of the online account statement web page, the computer system 801 compares the merchant name from the transaction database 804 with variations on the merchant name in the merchant database 805. The computer system 801 determines if the merchant name from the transaction database 804 matches with a merchant name 902 in the merchant database 805. To assist in the matching, the merchant look-up table 806 is provided. The merchant look-up table 806 includes possible variations of the merchant name for a merchant in the transaction history. For example, for the merchant name 902 of “Wal-Mart,” potential occurrences of the merchant name may include: “Wal-Mart Store 123” and “Wal-Mart Store 234.”

As a supplement to, or instead of, using the merchant look-up table 806, wildcard-based queries can be provided for potential iterations of the merchant name. For example, for the merchant name “Wal-Mart,” and if the wildcard is an asterisk (“*”), the following wildcard entries can be included, for example, in the merchant look-up table 806: “*Wal-Mart*,” “*Wal-Mart,” and “*Wal Mart*.”

In block 1002, it is determined if a match occurred between the merchant name in the transaction history and a merchant name 902 in the merchant database 805. If a match did not occur, flow proceeds to block 1003. If a match occurred, flow proceeds to block 1004.

In block 1003, no match occurred, and the transaction entry in the transaction history of the online account statement for the merchant is not indicated as being hyperlinked (e.g., area 419 in FIG. 4).

In block 1004, the merchant name for the transaction entry in the transaction database 804 matched with a merchant name 902 in the merchant database 805. The transaction entry for the transaction history of the online account statement is displayed as a hyperlinked transaction entry (e.g., area 420 in FIG. 4).

In block 1005, it is determined if a special offer exists for the merchant identified in the transaction entry. Initially, the on/off indicator for the merchant special offer web page URL 911 is examined. If the on/off indicator is off, no special offer exists for the merchant. If the on/off indicator is on, a special offer may exist. Next, the presence of an entry in the field 911 is determined. If no entry in the field 911 is present, no special offer exists for the merchant. If an entry in the field 911 is present, a special offer exists for the merchant. The same conditions are checked for additional merchant special offer web page URL's.

In block 1006, if a special offer does not exist, flow proceeds to block 1007, and if a special offer exists, flow proceeds to block 1008.

In block 1007, a special offer does not exist, and the transaction entry is displayed as a hyperlinked transaction entry in the transaction history of the online account statement (e.g., area 420 in FIG. 4).

In block 1008, a special offer exists, and a hyperlinked special offer indicia (e.g., area 421 in FIG. 4) is displayed with the hyperlinked transaction entry in the transaction history of the online account statement (e.g., area 420 in FIG. 4).

As an option, flow can proceed from block 1003 to block 1005. With this option, in block 1007, the transaction entry is displayed as determined in block 1003, and in block 1008, the transaction entry is not displayed as a hyperlinked transaction entry but does include a hyperlinked special offer indicia. As an example of this option, a merchant name in a transaction entry of the transaction history is not hyperlinked, but a hyperlinked special offer indicia is located next to the merchant name in the transaction entry for a special offer from a competitor of the merchant named in the transaction entry.

The previous discussion of the invention is hereinafter referred to as the first exemplary embodiment of the invention. In a second exemplary embodiment of the invention, a description of the special offer is provided with the merchant web page. With such a description, the inventors discovered that a much higher than expected number of customers clicked on the special offer indicia on the merchant web page. FIGS. 11-13 illustrate the second exemplary embodiment of the invention.

FIG. 11 illustrates an exemplary online account statement web page for the second exemplary embodiment of the invention. The exemplary online account statement web page of FIG. 11 is similar to the exemplary online account statement web page of FIG. 4 but in a different format. The features in FIG. 11 that are the same as those in FIG. 4 are identified with the same reference numerals as those in FIG. 4. A distinguishing difference between the exemplary online account statement web pages of FIGS. 4 and 11 is the hyperlinked special order indicia. In FIG. 11, the exemplary hyperlinked special order indicia is a red icon shaped like a sales tag and having the word “VALUE” therein (e.g., area 1101), whereas the exemplary hyperlinked special order indicia in FIG. 4 is a red icon shaped like a sales tag and having the word “SAVE” therein (e.g., area 421). As explained above, by clicking on the hyperlinked special offer indicia, a merchant web page is opened that contains one or more special offers related to the respective transaction entry in the transaction history.

A distinguishing difference between the merchant web pages of the first and second exemplary embodiments is the description of the special offer. In the second exemplary embodiment, a description of the special offer is included with the merchant web page provided in block 109. In contrast, for the first exemplary embodiment, a description of the special offer is provided in the merchant special offer web page from block 114. FIG. 12 illustrates an exemplary merchant web page for the second exemplary embodiment. The exemplary merchant web page of FIG. 12 is similar to the exemplary merchant web page of FIG. 5, and the features in FIG. 12 that are the same as those in FIG. 5 are identified with the same reference numerals as those in FIG. 5.

Including the features discussed above for a merchant web page in the first exemplary embodiment, a merchant web page of the second exemplary embodiment includes: a hyperlinked special offer indicia (e.g., area 1201); a title or brief description for the special offer (e.g., area 1202); a description of the special offer (e.g., area 1203); and an additional information indicia, such as a radio button (e.g., area 1204). (The exemplary description of the special offer in area 1203 is for illustration purposes and exemplifies text.) Other types of indicia besides the stylized red tag can be used for the hyperlinked special offer indicia as discussed above for the hyperlinked special offer indicia of the online account statement web page. To access the merchant special offer web page via block 114, the user clicks on the hyperlinked special offer indicia (e.g., area 1201) or the additional information indicia (e.g., area 1204).

Another difference between the merchant web pages of the first and second exemplary embodiments is the inclusion of additional special offers on the merchant web page of the second exemplary embodiment. The additional special offers provide the customer with access to special offers beyond the initial one selected. The additional special offers can be provided, for example: directly on the merchant web page; via a menu selection, such as a drop-down menu of various merchants and/or special offers; or via an interstitial web page providing selections of various merchants and/or special offers. If the additional special offers are provided directly on the merchant web page, a similar format can be used as for the single special offer (e.g., areas 1201-1204), and/or any other web page presentation technique can be used (e.g., banners, pop-up windows, and/or child windows).

For example, in FIG. 12, if the user clicks on a drop-down menu selector (e.g., area 1205), a drop-down menu (e.g., area 1206) is displayed. The drop-down menu contains a listing of merchants and/or special offers for the customer. The merchants and/or special offers can be selected based on, for example: a rolling serial determination, a random determination, or a determination based on an analysis of the transaction entry and/or the customer. For the example in FIG. 12, merchants with or related transactions in the transaction history are displayed in one section of the drop-down menu (e.g., area 1207), and other merchants (e.g., without or unrelated to transactions in the transaction history) are displayed in another section of the drop-down menu (e.g., area 1208). Clicking on a merchant and/or special offer in the drop-down menu provides for the customer a merchant web page corresponding to the clicked-on merchant and/or special offer.

To populate the merchant web page of the second exemplary embodiment, appropriate fields are added to the merchant entries in the merchant database 805. FIG. 13 illustrates an exemplary merchant entry 1300 in the merchant database for the second exemplary embodiment of the invention. In addition to the exemplary fields discussed above for the exemplary merchant entry 900, the exemplary merchant entry 1300 includes the following fields, for example: a special offer title 1301; and a special offer description 1302. Referring to the exemplary merchant web page in FIG. 12, the special offer title 1301 is used to populate area 1202, and the special offer description 1302 is used to populate area 1203.

As an option to having a single special offer, a number of special offers can be associated with a merchant, as discussed above for the first exemplary embodiment. For each additional special offer, appropriate fields are added to the merchant entries in the merchant database 805. FIG. 14 illustrates an exemplary merchant entry 1400 in the merchant database for this option. In addition to the exemplary fields discussed above for the exemplary merchant entry 900, the exemplary merchant entry 1400 includes the following fields, for example, for two special offers: a first special offer title 1401; a first special offer description 1402; a first merchant special offer web page URL 1403; a second special offer title 1404; a second special offer description 1405; and a second merchant special offer web page URL 1406. For more than two special offers, similar additional fields can be added to the merchant entry. The one or more special offers can be from the merchant and/or one or more other merchants.

Although the invention has been described for use with the Internet, web servers, and web pages, other types of networks, networking devices, and networked displayable information can be used with the invention, as will be appreciated by those skilled in the art.

The embodiments and examples discussed herein are non-limiting examples.

While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should instead be defined only in accordance with the following claims and their equivalents.

Claims

1. A computer-assisted method comprising: receiving, by a computer system, a retrieved merchant name retrieved from transaction data;determining, by the computer system, merchant name variations based on the retrieved merchant name;querying, by the computer system, a merchant names database comprising a plurality of standard merchant names using the merchant name variations; andmatching, by the computer system, the retrieved merchant name to one of the plurality of standard merchant names.

2. The method of claim 1, wherein the determining comprises: altering at least one character of the retrieved merchant name to obtain the merchant name variations.

3. The method of claim 2, wherein the determining comprises: deleting the at least one character of the retrieved merchant name.

4. The method of claim 1, wherein the retrieved merchant name comprises a center portion, a beginning portion, and an ending portion.

5. The method of claim 4, wherein the determining comprises: ignoring all characters associated with the beginning portion of the retrieved merchant name.

6. The method of claim 4, wherein the determining comprises: ignoring all characters associated with the ending portion of the retrieved merchant name.

7. A computer-assisted method comprising: receiving, by a computer system, merchant name retrieved from transaction data;querying, by the computer system, a merchant names database comprising a plurality of merchant name variations and their corresponding standard merchant names; andmatching, by the computer system, the retrieved merchant name to one of the plurality of standard merchant names.

8. The method of claim 7, wherein the merchant names database is a merchant look-up table.

9. The method of claim 7, wherein the querying is a wildcard-based querying for potential iterations of the retrieved merchant name.

10. An apparatus comprising: at least one memory; andat least one processor coupled to the at least one memory and configured to perform, based on instructions stored in the at least one memory:receiving a retrieved merchant name retrieved from transaction data;determining merchant name variations based on the retrieved merchant name;querying a merchant names database comprising a plurality of standard merchant names using the merchant name variations; andmatching the retrieved merchant name with one of a plurality of standard merchant names.

11. The apparatus of claim 10, wherein the at least one processor is further configured to perform: deleting at least one character from the retrieved merchant name.

12. The apparatus of claim 10, wherein the at least one processor is further configured to perform: ignoring all characters associated with a beginning portion of the retrieved merchant name.

13. The apparatus of claim 10, wherein the at least one processor is further configured to perform: ignoring all characters associated with an ending portion of the retrieved merchant name.

14. A computer-readable storage medium storing computer-executable instructions that, when executed, cause a processor to perform a method comprising: receiving a retrieved merchant name retrieved from transaction data;determining merchant name variations based on the retrieved merchant name;querying a merchant names database comprising a plurality of standard merchant names using the merchant name variations; andmatching the retrieved merchant name with one of a plurality of standard merchant names.

15. The computer-readable medium of claim 14, said method further comprising: altering at least one character of the retrieved merchant name to obtain the processed merchant name.

16. The computer-readable medium of claim 14, said method further comprising: deleting at least one character of the retrieved merchant name.

17. The computer-readable medium of claim 14, said method further comprising: ignoring all characters associated with a beginning portion of the retrieved merchant name.

18. The computer-readable medium of claim 14, said method further comprising: ignoring all characters associated with an ending portion of the retrieved merchant name.

19. An apparatus comprising: a transaction data structure;a merchant look-up table;a processing system configured to perform: accessing an accessed merchant name from the transaction data structure;comparing the accessed merchant name with entry names in the merchant look-up table until the accessed merchant name matches one of the entry names; anddetermining a determined merchant name from the matched entry.

20. The apparatus of claim 19, wherein the processing system is further configured to perform: ignoring a beginning sequence of characters in the accessed merchant name when matching the accessed merchant name with the matched entry.

21. The apparatus of claim 19, wherein the processing system is further configured to perform: ignoring an ending sequence of characters in the accessed merchant name when matching the accessed merchant name with the matched entry.

22. The apparatus of claim 19, wherein the processing system is further configured to perform: generating a hyperlinked transaction entry based on the determined merchant name.