Merchant configured advertised incentives funded through statement credits

Description

FIELD

Implementations generally relate to advertised incentives by merchants to encourage consumers to make or complete purchases facilitated and managed by an issuer or transaction handler, and more particularly to a statement credit incentive to a consumer's payment device account with the issuer or transaction handler offered by a merchant to encourage the consumer to make a purchase from the merchant and also on the consumer's account with the issuer or transaction handler.

BACKGROUND

Merchants often use techniques to prompt consumers into making a particular purchase. These techniques are commonly in the form of monetary incentives, relying on the principle that a lower price will result in increased sales. Merchants may employ these techniques, for example, to help clear inventory before a new season's merchandise is released, to ease the release of a new product, to increase sales near the end of the fiscal year, to compete with a competitor over particular products, or to generally spur sales.

Monetary incentives may come in the form of a “sale” (i.e. temporary reduction in price at the register), a mail-in rebate (i.e. a refund of part or all of the purchase price by mail), or a store credit (i.e. credit that can be applied to another store purchase). These incentives usually only apply to a particular product and have a time component. For example, a sale may only apply to a particular brand of dishwasher purchased on a particular holiday weekend and a rebate may only be valid for computers purchased within two weeks before the start of classes at a university.

For some credit transactions, a merchant may also use a statement credit as a monetary incentive. A statement credit is an amount refunded back to a credit account and which appears on the account holder's account statement. Using a statement credit as a monetary incentive involves two distinct transactions. In the first transaction, the merchant charges the full amount to a customer's credit account. In the second transaction, the amount of the monetary incentive is then refunded back to the customer's credit account as a statement credit.

Statement credit campaigns offer an advantage for merchants over other types of monetary incentive programs because a transaction handler, such as Visa Inc. or MasterCard Inc, largely handles the administration of the campaign. Once a statement credit campaign is arranged and initiated between a merchant and transaction handler, the transaction handler tracks the statement credit, matches the statement credit to qualifying purchases, and credits the amount of the statement credit to the purchaser's account. The transaction handler then collects the aggregate amount of the statement credits made to multiple purchasers from the merchant.

Transaction handlers also benefit from statement credit campaigns. These campaigns, in combination with other campaigns and programs, lead to increased loyalty to a particular transaction handler and increase the general usage of a particular handler. In addition, statement credit campaigns can also spur usage of one transaction handler over other transaction handlers in individual purchasing decisions because of the monetary incentives available.

One difficulty with statement credit campaigns is the effort required to set up such campaigns. One or more merchants must negotiate with a transaction handler to identify purchases that qualify under the campaign, the effective time period of the campaign, the procedure for dealing with returns of the purchased item, as well as other details. The complexity, time, and corresponding cost of setting up a statement credit campaign effectively limits such campaigns to large merchants or large product manufactures offering statement credits across multiple merchants. Small and medium sized businesses are effectively barred from using this type of monetary incentive due to the setup cost.

Once a statement credit campaign is set up, it is generally inflexible as to changes in the types of products, services, or effective time period. These elements are generally part of the collaboration between the transaction handler and merchant, and are not easily modified. Merchants are therefore locked into a specific statement credit configuration, such as for a set time or for a set product. This, unfortunately, prevents merchants from dynamically using this type of monetary incentive to push specific products or services on an as-needed basis. In addition, it is currently very difficult for a merchant to target a statement credit campaign to a specific individual or set of individuals. For example, it is currently difficult for an online store to target a statement credit to the top 10% of its most frequent customers. This current one-size-fits-all system for statement credit campaigns severely limits the merchant's use of such campaigns.

A general problem for merchants, especially small to mid-sized merchants, is how to efficiently administer any monetary incentive program where money is refunded to the purchaser, whether it is a rebate program, a store credit, or a statement credit campaign. Larger merchants may undertake this responsibility themselves. However, the more processing a merchant must undertake, the more likely the administrative costs of the program will outweigh any benefits. In order to reduce administrative costs, some merchants arrange for third parties to handle the processing and other administrative aspects of these programs. In any case, the projected benefit of the program must be substantially more than the administrative costs. A program with a low administration cost would therefore be more highly desired.

Therefore, there are many factors impeding the use of statement credits, especially by small and medium sized businesses and by larger businesses that may want to use statement credits in a flexible manner to target different products or different customers at different times. Accordingly, it would be an advance in the art of commerce to provide a system that enables merchants to independently establish statement credit campaigns, modify the details of the campaigns as desired, and offload the burden of processing the statement credit to the transaction handler.

SUMMARY

Implementations relate to a computer implemented method of receiving an account activation for an account of an account holder, receiving a statement credit trigger from a merchant and matching a purchase meeting the requirements for a qualifying purchase as defined in the statement credit trigger, made on an account of an account holder, e.g., an account with an issuer or with the merchant. The method may then comprise a transaction handler crediting the account of the account holder with an amount of the statement credit, collecting an amount of the qualifying transaction from the account, and collecting the amount of the statement credit from a responsible party, and paying to the merchant's account the collected amount for the qualifying transaction, not necessarily in that order.

In one implementation, the statement credit trigger is received from the account holder directly. In this implementation, the merchant embeds a script corresponding to the statement credit trigger on its retail website that allows the account holder, incident to making a qualifying purchase on the account holder's account, to interact directly with the scrip. This enables the account holder to apply for the statement credit identified in the statement credit trigger to the transaction handler, or agent thereof, from the merchant's website. Alternately, the account holder may also apply for the statement credit identified in the statement credit trigger directly from the transaction handler's website or a third party website instead of from the merchant's retail website. The third party web site can be an Etail site with links to the merchant's site or any web site that agrees to be an advertisement publisher, such as content web sites with an agreement with a search engine site such as Google that returns advertisements in relation to search responses, where the content web-site may get advertisements from such as Google to display on the content web-site, which also may have some relation to the content otherwise displayed on the content web-site. This could be, e.g., advertisements that Google itself might display with a search query response that identifies prominently the content web site.

In another implementation, the statement credit trigger is received directly from the merchant before, or simultaneously with, the execution of a transaction meeting the requirements of transaction information identifying a qualifying purchase, contained in the statement credit trigger. The transaction can be on the account of an account holder. The merchant provides the statement credit trigger to the transaction handler on behalf of the account holder. The account holder does not need to take any additional steps, aside from making the qualifying purchase on the account holder's account, for which the merchant has agreed with the transaction handler the statement credit will be applied.

A method and apparatus is disclosed which may comprise providing, via a computing device, a merchant interface allowing a merchant to create an advertised incentive trigger comprising an advertised incentive configuration, including defining a qualifying purchase transaction, and to activate the advertising incentive trigger; storing in a database the advertised incentive configuration and an indication that the merchant has activated the advertising incentive trigger; receiving, via the computing device, while the advertising incentive trigger is activated, an authorization request from the merchant to authorize a qualifying purchase transaction; and executing, via the computing device, the advertised incentive with respect to a consumer payment system account of a consumer upon which consumer payment system account the qualifying purchase transaction was authorized.

The method and apparatus may include the interface comprising a portal to a transaction handler transaction handling system and the advertised incentive may comprise a statement credit incentive. To activate the advertised incentive trigger may include a user registering to obtain the advertised incentive.

The method and apparatus may further comprise crediting, via the computing device, the consumer payment account of the account holder according to the statement credit; debiting, via the computing device, the consumer payment account of the account holder according to the qualifying purchase transaction; and, debiting, via the computing device, an account of at least one entity responsible for funding the statement credit.

Defining the qualifying purchase transaction may comprise at least one of: defining one of a product and a service, to be purchased in the qualifying purchase transaction; defining a time period in which to complete the qualifying purchase; defining a consumer purchase account consumer purchase device with which to complete the qualified purchase transaction; and defining a merchant location where the qualifying purchase transaction is to occur. The system and method may comprise a tangible machine readable medium storing instructions, the instructions, when executed by a computing device, causing the computing device to perform the method.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram illustrating the functional blocks of an exemplary implementation, where each block performs a function and does not necessarily represent a physical item;

FIG. 2 is a flowchart illustrating an exemplary process for collecting and processing statement credits;

FIGS. 3(a) and 3(b) are respective exploded views of display screens featuring exemplary screen shots for rending on one or more display devices incident to a triggering of a statement credit event;

FIG. 4 illustrates an exemplary payments processing system for processing transactions conducted with merchants by account holders thereof, wherein, for each transaction, there is a provision of a service or good by a merchant to an account holder for the transaction on an account of the account holder, there is an authorizing and remunerating of an electronic payment by the account holder in conducting the transaction on the account with the merchant, and there is a authorizing and remunerating of an electronic payment by the merchant, or other responsible party, in fulfilling a statement credit to the account holder;

FIG. 5 illustrates systems housed within an interchange center to provide online and offline transaction processing for transactions conducted using the payments processing system of FIG. 4; and

FIG. 6 illustrates another view of the components of FIG. 4.

DETAILED DESCRIPTION

Referring to FIG. 1, a block diagram illustrates functional blocks by which a Merchant 100 displays an advertised incentive to an Account Holder 102 while engaged in on-line or other shopping with the Merchant 100. The advertised incentive may be displayed on the Merchant's 100 website or in the Merchant's 100 brick and mortar store, or otherwise dynamically conveyed to the Account Holder, such as on an advertisement publisher web site. An advertised incentive according to aspects of an embodiment of the presently disclosed subject matter also is referred to as a statement credit trigger, e.g., when the advertised incentive is a statement credit. Statement credit triggers both announce the statement credit advertised incentive to the Account Holder and also allow for statement credits to be tracked and matched to qualifying purchases for purposes of granting the statement credit and also for auditing of the effectiveness of a statement credit advertised incentive program. A qualifying purchase is a purchase that meets the requirements of an advertised incentive.

The Account Holder 102 creates a statement credit request registering for an statement credit advertised incentive on a Statement Credit Trigger Device 104. A Statement Credit Trigger Device 104 may be a computing device (e.g., a special purpose computer) such as a server, a mainframe computer, a mobile telephone, a personal digital assistant, a personal computer, a laptop, an email enabled device, or a web enabled device having one or more processors (e.g., a Central Processing Unit, a Graphical Processing Unit, or a microprocessor), which permits the Account Holder 102 to interact, e.g., with the merchant or other entity web sit displaying the statement credit trigger, and to, e.g., in some cases provide registration information.

Registration, if conducted, requires, e.g., the Account Holder to provide the name of the Account Holder 102 name, an identifier for the account of the Account Holder 102 (e.g.; a debit card, prepaid card or credit card number), and acceptance of the terms and conditions associated with the advertised incentive, such as a statement credit advertised incentive. Alternately, the Merchant 100 may create a statement credit trigger on behalf of the Account Holder 102 specifically or account holders in general, using the Statement Credit Trigger Device 104, e.g., by communicating the statement credit trigger to a Transaction Handler 108. In this case, no action is required by the Account Holder 102 for registration.

A Transaction Handler 108, or agent thereof, has access to a Statement Credit Trigger Database 110, a Transaction Database 112, a Matching Engine 114, and a Statement Credit Processor 116. The Statement Credit Trigger Database 110 receives and stores the information defining a qualifying purchase as contained in a statement credit trigger from the Statement Credit Trigger Device 104. It will be understood that this receipt and storage may occur at the time the Merchant initiates and activates the statement credit advertised incentive trigger or a the time an Account Holder 102 clicks on the Merchant 100 or other advertisement site advertisement for the advertised incentive or simply clicks onto the web site of the Merchant 100.

The Transaction Database 112 contains financial transactions for the Account Holder 102 processed by the Transaction Handler 108. The Matching Engine 114 queries the Statement Credit Trigger Database 110 and the Transaction Database 112 to match a qualifying purchase transaction with the requirements contained in a statement credit trigger. A qualifying purchase is a purchase that satisfies all the requirements of the advertised incentive as configured by the Merchant 100 and included in the statement credit advertised incentive trigger. For example, an advertised incentive may require a purchase to be made on a particular card, for a particular product, and during a particular time, or other additional requirements, such as at a particular merchant location.

When the Matching Engine 114 matches a statement credit trigger set of requirements with a qualifying purchase, the Matching Engine 114 notifies the Statement Credit Processor 116. Upon notification, the Statement Credit Processor 116 initiates a statement credit transaction between the Merchant 100 and the Account Holder 102 where funds are transferred from the Merchant 100 to the Account Holder 102 in the amount of the statement credit, which could also take place in the course of authorization by the Transaction Handler 108 of the payment from the account of the Account Holder 102 for the qualifying transaction and the crediting of the account of the Merchant 100 of the payment for the qualifying transaction.

To facilitate the statement credit transaction, the Statement Credit Processor 116 can credit the account of the Account Holder 102 with the amount of the statement credit. This transaction can then appear on the account statement for the account of the Account Holder 102 as a credit, which is equivalent to a payment and thereby offsets any amount owed on the account up to the amount of the credit. In addition, the Statement Credit Processor 116 collects the amount of the statement credit from the Merchant 100 or some other responsible entity, e.g. a supplier of the Merchant when, e.g., the supplier is sponsoring and paying for the statement credit advertised incentive program alone or together with the Merchant 100.

Turning to FIG. 2, a flowchart illustrates an exemplary process 200 for offering and processing statement credits. Advertised incentive account activation information is received from the Merchant, or an agent thereof, in operation 202. Once the advertised incentive account activation information is received, an advertised incentive account is created for the Merchant in operation 204. In one implementation, real time access to and manipulation of, the advertised incentive account by the Merchant 100 allows for a Merchant 100 to define any number of custom advertised incentives, such as statement credit incentives, based on any criteria a Merchant 100 desires. In addition, such real time access and manipulation allows for Merchants 100 to instantly activate or deactivate any particular advertised incentive. Once an advertised incentive is deactivated, Account Holders 102 will no longer be offered the corresponding credit statement and indications of qualifying transaction purchases for otherwise qualifying transactions will no longer be identified by the Matching Engine 114 for that particular advertised incentive.

Once the advertised incentive account is created for the Merchant 100 in operation 204, advertised incentive configuration information is received from the Merchant in operation 206. The configuration information is used to define one or more advertised incentives, such as statement credit advertised incentives, and may include the amount of the statement credit, the terms and conditions, the requirements for a qualifying purchase, and an advertisement image. In addition, the configuration information can be used to instantly activate or deactivate an advertised incentive or change other details of an advertised incentive, including changes in the terms and conditions, the amount of the statement credit, the requirements for a qualifying purchase, and the advertisement image. In one implementation, each advertised incentive will be assigned a globally unique identifier that enables the advertised incentive to be uniquely identified during subsequent processing. The combination of operations 202-206 comprises the creation and activation of a statement credit advertisement incentive program.

A statement credit trigger is received from an account holder or merchant in operation 208. The statement credit trigger is created, in one embodiment, when an account holder registers for an advertised incentive. The Account Holder 102 can register for an advertised incentive using a computer, a mobile phone, or other web enabled device. Alternately, the Merchant 100 can register the Account Holder 102 for an advertised incentive on behalf of the Account Holder 102. In one implementation, the statement credit trigger received from the Account Holder 102 or Merchant 100 in operation 208 contains an acknowledgement of the terms and conditions for the advertised incentive, the name of the Account Holder 102, the account number, and a globally unique identifier for the advertised incentive, such as the statement credit.

In one implementation, a single statement credit trigger may be associated with multiple advertised incentives for a particular Merchant 100. Responding to a statement credit trigger by registering for one advertised incentive would, therefore, qualify an Account Holder 102 for all the other advertised incentives associated with the statement credit trigger. Alternately, in another implementation, an advertised incentive trigger, such as a statement credit trigger, may be associated with a single advertised incentive, i.e., a single statement credit program.

Transaction information is received from the Merchant 100 in operation 210. The Transaction information represents information concerning a financial transaction, such as one between the Merchant 100 and the Account Holder 102.

Qualifying transactions are identified in operation 212. Qualifying transactions are those that meet the requirements of a particular advertised incentive, e.g., as identified in a statement credit trigger. For example, a given advertised incentive, such as a statement credit, may only relate to a particular product, purchased on a particular date, within a particular time after the creation of the statement credit trigger for the given advertised incentive, e.g., a statement credit. Only a purchase that meet all the requirements, as defined by the Merchant 100, e.g., in the advertised incentive statement credit trigger, for an advertised incentive is deemed a qualifying purchase transaction.

The requirements identified in a statement credit trigger are matched with a transaction to identify a qualifying transaction in operation 214. To satisfy a match, the requirements in the statement credit trigger for a given statement credit advertised incentive must match the pertinent factors regarding the qualifying transaction for the given advertised incentive. In one implementation, a match requires that an account number associated with the statement credit trigger match the account number used to make the qualifying purchase, e.g., where the advertised incentive is personal to a given Account Holder 102, such as one clicking on the advertised incentive statement credit trigger on the web site of the Merchant 100, like a display of the advertisement.

If the requirements in a statement credit trigger and a purchase for a given advertised incentive do not match (operation 216), i.e., there is not a qualifying purchase, no further action is taken and the process flow ends at operation 222. However, if the requirements in a statement credit trigger and a purchase transaction for a given advertised incentive do match (operation 216), then the account of the Account Holder 102 is credited with the amount of the statement credit at operation 218, where the advertised incentive is a statement credit. The statement credit is equivalent to a payment and, to the extent of the statement credit amount, offsets any amount owed by the Account Holder 102. In addition, the amount of the statement credit is collected from the merchant or other responsible entity, or both, in operation 220. Operations 218 and 220 can be viewed as a second transaction, in addition to the initial transaction of the purchase of goods or services by the Account Holder 102 from the merchant 100, constituting a qualifying purchase. In this second transaction, the Merchant 100 is charged for all or a portion of the amount of the initial qualifying transaction according to the amount of the agreed upon statement credit.

In another implementation, advertised incentive, such as the amount of the statement credit can be collected from a third party instead of the merchant. For example, the third party may be the manufacturer of the product that is the target of the advertised incentive. In this implementation, the merchant, or agent thereof, configures the timing, placement, appearance, and duration of the advertised incentive, i.e., after the advertised incentive trigger, according to the responsible third party's specifications, and the responsible third party funds or partly funds the advertised incentive, such as the statement credit, for deposit into the account of the Account Holder who made the qualifying purchase of the manufacture's product from the Merchant 100.

In yet another implementation, the amount of the statement credit can be collected from the Merchant 100 and/or any number of third parties. In this implementation, the Merchant 100 and/or any number of manufacturers, distributors, or other parties with an interest in selling the particular product that is the target of the advertised incentive, can fund or partially fund the statement credit.

Once the amount of the statement credit has been collected from the account of the Merchant, or other responsible party, no further action is taken and the process flow ends at operation 222.

By way of example, FIG. 3(a) depicts a partial view of a Display Screen 300 or a pop-up generated thereon. Display Screen 300 features a screenshot as viewed by an Account Holder 102, and may be displayed as all or part of any advertisement publisher web site, as discussed above. Using Display Screen 300, a Merchant 100 can present an advertised incentive trigger to an Account Holder 102 and the Account Holder can register for the advertised incentive, such as a statement credit, or otherwise initiate pursuit of the advertised incentive by becoming identified with an advertised incentive, such as a statement credit, or simply become informed of the existence of the particular advertised incentive. Information relating to a statement credit trigger is communicated to the Account Holder 102 and also perhaps to a transaction handler at the time of such registration or other activation by the Account Handler of the pursuit of the advertised incentive.

The contents of Display Screen 300 contain an example Shopping Cart 302 for an online retailer. The Shopping Cart 302 contains an Inventory 304 of the contents of the Shopping Cart 302, including the item name, the unit price, the quantity, the total price, the subtotal, the shipping cost and the total cost. The Shopping Cart 302 also contains an Advertised Incentive Banner 306.

In one implementation, the Shopping Cart 302 is provided by the web server of the Merchant 100 while the contents of the Advertised Incentive Banner 306 is provided by the web server of the Transaction Handler 108, based on information received from the Merchant 100 identifying the advertised incentive requirements, such as the requirements for a statement credit incentive. The code that renders the Shopping Cart 302 includes a script that sends the globally unique identifier for the advertised incentive to the web server of the Transaction Handler 108 and reserves an area on the Shopping Cart 302 for the Advertised Incentive Banner 306. The web server of the Transaction Handler 108 provides content directly to the reserved area of the Shopping Cart 302 (i.e., the Advertised Incentive Banner 306).

In another implementation, an advertised incentive image provided by the merchant may also be included in the Advertised Incentive Banner 306. The advertised incentive image is provided as part of the advertised incentive configuration. When an advertised incentive is requested, e.g., by the Account Holder clicking on the advertised Incentive Banner 306 script on Shopping Cart 302, the web server of the transaction handler 108 may send text, an image, or a combination of both to populate the content of the Advertised Incentive banner 306.

In the present implementation, illustrated by way of example in FIG. 3(a), the Advertised Incentive Banner 306 is intended to incentivize the Account Holder 102 to complete the purchase of the items already added to the Shopping Cart 302 within some selected period of time, such as two hours, as noted in FIG. 3(a). In another implementation, the Merchant 100 may configure the Advertised Incentive Banner 306 to incentivize the Account Holder 102 to add an item to the Shopping Cart 302. For example, if the Merchant desires to incentivize a specific product, an Advertised Incentive Banner 306 may be configured to appear on the page illustrated in FIG. 3(a) or alternatively on an information page for that product. Such placement will incentivize the Account Holder 102 to add the product to the Shopping Cart 302. In yet another implementation, the Merchant may place multiple Advertised Incentive Banners 306 at various locations on the web site of the Merchant 100 to simultaneously provide different types of incentives. In such an implementation, each advertised incentive may be independently configured.

The Merchant 100 may disable an advertised incentive at any time by changing the configuration for the advertised incentive contained in the advertised incentive account created with the advertised incentive trigger. In one implementation, the Merchant 100 may provide alternate content for the advertised incentive when the advertised incentive is disabled. In this implementation, the Advertised Incentive Banner 306 will display an advertised banner when the advertised incentive is enabled, but show different content, such as an informational banner, when the advertised incentive is disabled. In such an embodiment, no changes need to be made to the website of the Merchant 100 to activate or deactivate the advertised incentive. Therefore, advertised incentives can be easily and instantly enabled or disabled using the advertised incentive account with or without modification to the web site of the Merchant. Alternatively, where the advertised incentive, such as the statement credit, is defined through an advertised incentive trigger created by the Merchant 100 on the web site of the Merchant 100 the incentive can be disabled by the Merchant 100 on the web site of the Merchant 100, e.g., by removing the Advertised Incentive Banner 306.

To register for the advertised incentive, the Account Holder begins by activating the Advertised Incentive Banner 306. Activation can be accomplished by clicking (i.e. using a mouse on a standard computer), by touching (i.e. using the screen on a touch enabled computing device), or otherwise selecting the Advertised Incentive Banner 306. Upon activation of the Advertised Incentive Banner 306, a request is sent to the web server of the Transaction Handler 108 for a statement credit registration Form. Horizontal and vertical icons 318, 320 can be activated by a user to scroll the image on the display screen, respectively, horizontally and vertically.

By way of example, FIG. 3(b) depicts a portion of a Display Screen 308. The Display Screen 308 features a screenshot, as viewed by an Account Holder 102, of a Statement Credit Registration Form 310. The Statement Credit Registration Form 310 is hosted by the web server of the Transaction Handler 108 and may be a full web page, a separate pop-up page, or embedded content in an existing page. The Statement Credit Registration Form 310 contains terms and conditions 312, which were provided by the merchant upon configuration of the advertised incentive. In addition, the Statement Credit Registration Form 310 contains an Account Information Section 314.

Registration is complete when the Account Holder accepts the Terms and Conditions 312 and provides a name and account number in the Account Information Section 314. The registration information, along with the globally unique identifier for the advertised incentive, is submitted to the Transaction Handler 108 and a statement credit trigger has been created according to this embodiment.

In one implementation, a cookie is stored on the web browser of the Account Holder by the web server of the Transaction Handler 108. The cookie contains a globally unique identifier that identifies the registration information for a single account holder. Multiple cookies may be stored on a web browser if multiple Account Holders use the same computer or if the Account Holder registers for more than one advertised incentive program, such as multiple statement credit incentive programs. Upon the display of the Statement Credit Registration Form 310 by the web server of the Transaction Handler, previously provided registration information stored on the web server of the Transaction Handler can be referenced by a cookie. When such a cookie is present, the Account Holder 102 may be presented with the option to register in Statement Credit Registration Form 310 by selecting an item from the Previously Registered Section 316. The registration information listed in Previously Registered Section 316 is populated by the web server of the Transaction Handler 108 based on a globally unique registration information identifier stored in the cookie.

Storing and referencing registration information by cookies allows for an Account Holder to easily register for an advertised incentive. Instead of providing any information, the Account Holder 102 merely needs to select the appropriate account that had already been registered for the same or different advertised incentive. In addition, this method is secure because the cookie only stores the globally unique identifier for an Account Holder 102. The sensitive registration information is stored on the web server of the Transaction Handler 108 only. However, the globally unique identifier allows the web server of the Transaction Handler 108 to associate a cookie with a particular Account Holder 102 and recall the previously provided registration information for the Account Holder 102.

In another implementation, the merchant may register the account holder's eligibility for an advertised incentive on behalf of the account holder. This implementation would be most appropriate for merchants who have an identifier for the account holder's account (e.g.; card on file) because the merchant would have all the information necessary to register the account holder for the advertised incentive. In this implementation, the merchant may choose to provide the content for the advertised incentive banner instead of relying on the transaction handler to provide the content. In yet another implementation, the merchant may wish to automatically give incentives in the form of statement credits to certain highly valued customers, regardless of what the customer may purchase, as a general incentive for the highly valued customer to continue to patronize the merchant's web site.

In yet another implementation, the same method described above may be used with a brick and mortar store in addition to a web-based store. An account holder may register for an advertised incentive before visiting a brick and mortar store or at the store itself. As long as the account holder registers for the advertised incentive before making a qualifying purchase, the account holder may use a terminal provided by the store, a wireless handheld device, or any other Internet connected device to register for an advertised incentive.

In still another implementation, a merchant may host, or have hosted, a web site at a web service in order to sell its advertised goods and service. The web service, which may include one or more web servers, receives advertised incentive configuration information from the merchant, such as by the merchant operating a client to access the web service. A unique identifier is assigned by the web service to the advertised incentive configuration information. Thereafter, the web service receives a request from a client to be served a web page that includes an advertised incentive based on the unique identifier. In this case, the advertised incentive is a statement credit that is being offered to a user operating the client.

The web service serves the requested web page to the client who is accessing the merchant's web site using a browser executing on the client. The web page served to the client by the web service will include the advertised incentive which advertises the statement credit. In response to the served web page that included the advertised incentive, there is received at the web service from the client, a statement credit trigger. The statement credit trigger may be received in response to the user of the client ‘clicking’ on a displayed icon corresponding to the advertised incentive based on the unique identifier. Here, the user's “click” is intended as an act to purchase a corresponding good or service from the Merchant 100 for which the merchant 100 is offering, via the advertised incentive, a statement credit to the user if the user conducts a transaction for the purchase on an account issued by an issuer 404 to the user. Thereafter, transaction data is received from the Merchant 100, where the transaction data may include a plurality of transaction between the Merchant 100 and one or more consumers.

When the transaction data has been determined, using predetermined criteria, to include a qualifying transaction conducted on the account issued by the issuer 404 to the user, and when a predetermined dataset in the statement credit trigger matches a predetermined dataset in the qualifying transaction, a transmission is sent for delivery to the issuer 404 of the account of the user. The transmission will include a financial message giving instructions to credit to the account of the user for an amount corresponding to the statement credit trigger. A corresponding transmission will be sent for delivery to an issuer 404 of an account issued by an issuer 404 to a sponsor of the statement credit trigger, where the corresponding transmission will include a financial message giving instructions to debit the sponsor's account for the amount of the statement credit trigger. As such, the user's account is credited for the statement credit as advertised on the web page, and the sponsor of the statement credit has its account debited for the amount of the user's statement credit.

In the foregoing implementation, at any time, the merchant, the sponsor, or agents thereof, can, in real time, revoke the statement credit offer on the web page so that no other user can take advantage of the statement credit offer. For instance, when the merchant depletes inventory of a good or service for which a statement credit is being advertised on the merchant's web site, the merchant can use a client to communicate with the web service to update the web page to remove the statement credit from the web page. Note also that the sponsor can be, a manufacturer, a supplier, a distributor, and a combination of the foregoing.

Referring to FIG. 4, an Account Holder 102 conducts a financial transaction with a Merchant 100. By way of example, the financial transaction with the Merchant 100 may have been incentivized by a statement credit defined by the Merchant 100 through an advertised incentive. The diagram of FIG. 4 depicts an exemplary process 400 of a particular financial transaction system.

Account Holder 102 presents an electronic payment device (i.e.; a credit card) to a Merchant 100, as indicated by arrow 458, as tender for a financial transaction such as a purchase of goods. Those of skill in the art will recognize that other financial transactions and instruments other than credit cards may also be used, including, but not limited to, a credit card, debit card, prepaid card, cellular telephone, Personal Digital Assistant (PDA), etc. For purposes of illustration and explanation, however, reference will be made to a credit card.

As part of the transaction, the payment device of the Account Holder 102 can be a The payment device is read by a reader operated by the Merchant 100, whereupon account information is read from the payment device and a request for authorization is transmitted to the an Acquirer 406 for the Merchant 100, as indicated by arrow 466. Each Acquirer 406 is a financial organization that processes credit card transactions for businesses, for example the Merchant 100, and can be licensed as a member of a transaction handler 108 such as a credit card association (i.e., Visa Inc.®, MasterCard®, etc.) As such, each Acquirer 406 establishes a financial relationship with one or more merchants such as Merchant 100.

The Acquirer 406 transmits the account information to the Transaction Handler 108, as indicated by arrow 470, and the Transaction Handler 108 in turn routes the request to the Issuer 404 of the Account Holder 102, such as an issuing bank, as indicated by arrow 476. The Issuer 404 returns authorization information to the Transaction Handler 109, as indicated by arrow 474, who returns the information to the Merchant 100 through the Acquirer 406, as indicated by arrows 468 and 462. The Merchant 100 now knowing whether the credit card account of the Account Holder 102 is valid and supports a sufficient credit balance, may complete the transaction and the Account Holder 102 in turn receives goods and/or services in exchange, as indicated by arrow 456. Most credit card associations instruct merchants that, after receiving authorization, the detailed credit card account information obtained from the point of sale magnetic stripe scanner must be deleted.

To reconcile the financial transactions and provide for remuneration, information about the transaction is provided by the Merchant 100 to the Acquirer 406, as indicated by arrow 466, who in turn routes the transaction data to the Transaction Handler 108, as indicated by arrow 470 who then provides the transaction data to the appropriate Issuer 404, as indicated by arrow 476). The Issuer 404 then provides funding for the transaction to the Transaction Handler 108, as indicated by arrow 474, e.g., through a settlement bank (not shown). The funds are then forwarded to the Merchant's 100 Acquirer 406, as indicated by arrow 468, who in turn credits the account of the Merchant 100 for the transaction conducted, as indicated by arrow 462, e.g., less a transaction handler/acquirer discount, if applicable. The Issuer 404, then bills the Account Holder 102, as indicated by arrow 450), and the Account Holder 102 pays the Issuer 404, as indicated by arrow 452, with possible interest or fees.

Each of the Issuer 404, Merchant 100, Acquirer 406 and the Transaction Handler 108 may have access to information resources having one or more of the following databases: transaction database 482, merchant database 484, accounts database 480, Statement Credit Trigger Database 488, Advertised Incentive Configuration Database 494, and/or other database 486, some or all of which may be combined in functionality with others of the group of databases just mentioned, or some subset(s) of such group, or be divided into one or more databases performing the same functionality separately or cooperatively. Some or all of these databases, or subsets thereof, can be connected by a network, Internet, virtual private network, LAN, WAN or by other means known to those skilled in the art. Moreover, not every participant must necessarily have access to any or all of the databases. Each database can assign read, write, and query permissions as appropriate to the various participants. For example, a Merchant 100 may have read access to the accounts database 480 and the Issuer or Transaction Handler 108 may have read and write access.

The transaction database 482 is designed to store some or all of the transaction data originating at the Merchant 100 that used a payment device for each transaction conducted between an Account Holder 102 and the Merchant 100. The transaction data can include information associated with the consumer payment device account of an Account Holder 102, such as, date, time, and location among other more specific information including the amount of the transaction. The transaction database can be searched using account information, date and time (or within proximity thereof), or by any other field stored in the database.

The Advertised Incentive Configuration Database 494 is designed to store configuration information provided by the Merchant 100 for advertised incentives. For example, whether the advertised incentive is enabled or disabled on the web site of the Merchant 100, or on some other advertisement publishing site or the site of the Transaction Handler 108 and/or Issuer 404, the valid time period for the advertised incentive, the type of incentive, e.g., including a statement credit, and if so the amount or percentage of the credit, and other requirements for a qualifying purchase, such as the product or service to be purchased, the type of payment, including the use of a particular consumer payment device associated with the Issuer 404 and/or the Transaction Handler 108, the location of the purchase, including on-line or from a consumer mobile communication device, etc. and text and graphics to be displayed on the advertised incentive banner, are stored in this database. It will be understood that in one embodiment when the Merchant has selected some or all of these requirements included within the Configuration Information, and indicates the incentive is to be in place, or activates the banner displaying the advertised incentive, or otherwise “turns on” the advertised incentive, the Merchant has created and set in place an advertised incentive trigger. Also, when the Merchant 100 chooses to turn off the advertised incentive, i.e., make it no longer active and subject to being executed by a consumer, and thus earning the incentive, the Merchant “turns off” i.e., deactivates the trigger.

The Statement Credit Trigger Database 488 is designed to store registration information for advertised incentives, which may include some portions or all of the above noted contents for the Advertised Incentives Database 94, and the two may also be combined. A statement credit trigger, in one embodiment may be created in the Statement Credit Trigger Database 488 when an Account Holder 102 is directly or indirectly registered with an advertised incentive. An Account Holder 102 can directly register with an advertised incentive by providing the registration information, as indicated by arrow 490. Alternately, a Merchant 100 can indirectly register the Account Holder 102, as indicated by arrow 492, with an advertised incentive by providing the registration information on behalf of the Account Holder. As noted above, for an Account Holder 102 to qualify for an advertised incentive, such as a statement credit, the statement credit trigger must be created before a qualified purchase is made and not have been “turned off” by the Merchant 100. That is, in one embodiment, where the Merchant 100, the Transaction Handler 108 and/or the Issuer 404 decide that registration by the Account Holder 102 for the creation of n advertised incentive trigger, then entries into the Statement Credit Trigger Database 488 may not be required for a trigger, and the information put into the advertisement Incentive Configuration Database 494 may be all that is required to establish an advertised incentive trigger. Similarly, all of this data may be incorporated into a combined Statement credit Trigger Database and Advertised Incentive configuration database for purposes of retaining information needed to create an advertised incentive trigger and define how the system responds to an Account Holder 102 qualifying for the defined advertised incentive when the trigger is activated.

The Merchant Database 484 is designed to store information about each Merchant 100. The Merchant Database 484 can contain information such as the unique identification of each Merchant 100, an identifier for each point of sale device in use by the Merchant 100, and location(s) of the Merchant 100.

The Accounts Database 480 is designed to store account information for payment devices associated with an Accounts Holder 102. The Accounts Database 480 can store part or all of an account number, unique encryption key, account information, account name, globally unique identifier for the Account Holder 102 and/or the consumer payment device account(s) of the Account Holder 102. The information from the Accounts Database 480 can be associated with information from the Transactions Database 482.

After registering for an advertised incentive, when such is required, an Account Holder 102 initiates a qualifying purchase transaction with a Merchant 100 by presenting a consumer payment device, as indicated by arrow 458 to the Merchant 100. The consumer payment device is typically presented at a Point Of Sale/Service (“POS”) terminal (not shown in FIG. 4) at which data thereon is read. Certain transaction information is transmitted from the POS terminal in route to the Merchant's (n) 410 Acquirer (i) 406. The transaction information can include account information, account name, transaction balance, transaction time, transaction date, and transaction location, product/service identifier, merchant/POS identifier, etc. Sensitive information includes information such as account number and account holder name that identify and associate a particular account with a particular account holder. This transaction information may be transmitted via a less secure communication medium. In addition, a transmission of transaction data may occur with weak or no encryption between two or more points from the point of origin, such as the point of sale device at the Merchant 100, and the ultimate destination, such as the Acquirer 406.

These points can include, without limitation, from the reader at the POS, the POS terminal at the Merchant 100 and a network router or computer that is connected to a network but is housed and maintained by the Merchant 100 and between the Merchant 100 and the Acquirer 406. The communication channel could be Ethernet, wireless internet, satellite, microwave transmission, infrared transmission, or other known communication protocols. Some or all of the transmission may also be stored for record keeping, archival or data mining purposes with little or no encryption, e.g., in one or more of the above noted databases or combinations of those databases. For example, the Merchant 100 may store transaction data, including certain account information in, e.g., an accounts on file database (not shown) of the Merchant's 100, for reuse later.

In this process, transaction information relating to the qualifying purchase transaction is retrieved from the POS at a Merchant 106 or from some other computing device and/or related database at the Merchant 100. The transaction information is comprised of account information together with other information about the transaction itself: time, date, location, value, product/service, type of payment, etc. Certain of the transaction information is considered sensitive information including, without limitation, account number, credit card verification number, and account name.

Upon completion of the qualifying purchase transaction, transaction information relating to the advertised incentive, such as the statement credit, is used to initiate a second transaction that largely mimics the path of the qualifying purchase transaction except in the opposite direction. Thus, the statement credit is a transfer of funds from the Merchant 100 and/or another responsible entity, to the Account Holder 102, or a pseudo transfer wherein the amount is simply credited against the outstanding balance in the account of the Account Holder 102.

FIG. 4 further illustrates a payment processing network that may make use of any suitable telecommunications network and may involve different hardware, different software and/or different protocols then those discussed below. FIG. 4 is a global telecommunications network that supports purchase and cash transactions using any bankcard, travel and entertainment cards, and other private label and proprietary cards. The network also supports ATM transactions for other networks, transactions using paper checks, transactions using smart cards and transactions using other financial instruments.

These transactions are processed through the payment processing network's authorization, clearing and settlement services. Authorization is when an issuer approves or declines a sales transaction before a purchase is finalized or cash is dispersed. Clearing is when a transaction is delivered from an acquirer to an issuer for posting to the customer's account. Settlement is the process of calculating and determining the net financial position of each member for all transactions that are cleared. The actual exchange of funds is a separate process.

Transactions can be authorized, cleared and settled as either a dual message or a single message transaction. A dual message transaction is sent twice—the first time with only information needed for an authorization decision, an again later with additional information for clearing and settlement. A single message transaction is sent once for authorization and contains clearing and settlement information as well. Typically, authorization, clearing and settlement all occur on-line.

The system/method illustrated by way of example and partially schematically in FIG. 4 can include one or more transaction handlers 108, access points 430, 432, acquirers 406, and issuers 404. Other entities such as drawee banks and third party authorizing agents may also connect to the network through an access point. An interchange center is a data processing center that may be located anywhere in the world. In one implementation, there are two in the United States and one each in the United Kingdom and in Japan. Each interchange center houses the computer systems and databases that are used to perform the consumer payment network transaction processing. The interchange center serves as the control point for the telecommunication facilities of the network, which comprise high speed leased lines or satellite connections based on IBM SNA protocol. Preferable, the communication lines that connect an interchange center (including one or more Transaction Handlers 108) to remote entities use dedicated high-bandwidth telephone circuits or satellite connections based on the IBM SNA-LU0 communication protocol. Messages are sent over these lines using any suitable implementation of the ISO 8583 standard.

Access points 430, 432 are typically made up of small computer systems located at a processing center that interface between the center's host computer and the interchange center. The access point facilitates the transmission of messages and files between the host and the interchange center supporting the authorization, clearing and settlement of transactions. Telecommunication links between the Acquirer 406 and its access point, and between the access point and Issuer 404 are typically local links within a center and use a proprietary message format as preferred by the center.

A data processing center (such as is located within an Acquirer 406, Issuer 404, or other entity) houses processing systems that support merchant and business locations and maintain customer data and billing systems. Preferably, each processing center is linked to one or two interchange centers. Processors are connected to the closest interchange, and if the financial/payment network experiences interruptions, the network automatically routes transactions to a secondary interchange center. Each interchange center is also linked to all of the other interchange centers. This linking allows processing centers to communicate with each other through one or more interchange centers. Also, processing centers can access the networks of other programs through the interchange center. Further, the network ensures that all links have multiple backups. The connection from one point of the network to another is not usually a fixed link; instead, the interchange center chooses the best possible path at the time of any given transmission. Rerouting around any faulty link occurs automatically.

FIG. 5 illustrates an example of an interchange center system 240 housed within an interchange center (not shown) to provide on-line and off-line transaction processing. For dual message transaction, authorization system 242 provides authorization. System 242 supports on-line and off-line functions, and its files include internal system tables, a customer database and a merchant central file. The on-line functions of system 242 support dual message authorization processing. This processing involves routine cardholder and card verification and stand-in processing, and other functions such as file maintenance. Off-line functions can include reporting, billing and generating recovery bulletins. Reporting includes authorization reports, exception files and advice file reports, POS reports and billing reports. A bridge from system 242 to system 246 makes it possible for members using system 242 to communicate with members using system 246 and access the SMS gateways to outside networks.

Clearing and settlement system 244 clears and settles previously authorized dual message transactions. Operating on a global basis, system 244 collects financial and non-financial information and distributes reports between members. It also calculates fees, charges and settlement totals and produces reports to help with reconciliation. A bridge (not shown) forms an interchange between system 244 processing centers and system 248 processing centers.

Single message system 246 processes full financial transactions. System 246 can also process dual message authorization and clearing transactions, and communicates with system 242 using a bridge and accesses outside networks as required. System 246 processes Visa, Plus Interlink and other card transactions. The SMS files comprise internal system tables that control system access and processing, and the cardholder database, which contains files of cardholder data used for PIN verification and stand-in processing authorization. System 246 on-line functions perform real-time cardholder transaction processing and exception processing for authorization as well as full financial transactions. System 246 also accumulates reconciliation and settlement totals. System 246 off-line functions process settlement and funds transfer requests and provide settlement and activities reporting. Settlement service 248 consolidates the settlement functions of system 244 and 246, including Interlink, into a single service for all products and services. Clearing continues to be performed separately by system 244 and system 246.

FIG. 6 illustrates another view of components of FIG. 5 as a telecommunications network 254. Integrated payment system 250 is the primary system for processing all on-line authorization and financial request transactions. System 250 reports both dual message and single message processing. In both cases, settlement occurs separately. The three main software components are the common interface function 252, authorization system 242 and single message system 246.

Common interface function 252 determines the processing required for each message received at an interchange center. It chooses the appropriate routing, based on the source of the message (system 242, 244 or 246), the type of processing request and the processing network. This component performs initial message editing, and, when necessary, parses the message and ensures that the content complies with basic message construction rules. Common interface function 252 routes messages to their system 242 or system 246 destinations.

The VisaNet® system is an example component of the transaction handler 108 in the payment processing system 400 of FIG. 4. Presently, the VisaNet® system is operated in part by Visa Inc. As of 2007, the VisaNet® system Inc. was processing around 300 million transaction daily, on over 1 billion accounts used in over 170 countries. Financial institutions numbering over 16,000 connected through the VisaNet® system to around 30 million merchants. In 2007, around 81 billion transactions for about 4 trillion U.S. dollars were cleared and settled through the VisaNet® system, some which involved a communication length of around 24,000 miles in around two (2) seconds.

Persons skilled in the art will understand that graphic advertisements are being placed by advertisement publishers, such as, Google and other advertisement engines on any site that wishes to be an “advertisement publisher” and making huge amounts of money by doing so from this form of advertising. A issuer or a transaction handler can add a coupon to any advertisement publisher site or even onto the issuer's or transaction handler's own site(s). As such a multi-URL advertisement can be delivered as a single advertisement on any such web site/page, such as a banner advertisement or occupying unused real estate on the existing page. A user can activate the advertisement, such as by clicking on the advertisement, and, e.g., go to the “advertiser” site, or a pop-up on the present site being visited.

The single advertisement can invite the user, e.g., “Click here and get a Visa® hosted statement credit form.” When a user clicks on a cookie can be left with a correlation ID, so subsequent clicks may not require the user to supply account information. The single advertisement can invite the user to, e.g., “Click here and launch Enhanced Card Services or any other Visa® service,” or “Click to receive a 10% statement credit if you pay with your Visa® card.”

The system/method according to embodiments of the disclosed subject matter may serve to provide a merchant a service which can provide actual metrics back to merchants, e.g., by track actual fulfillment of advertised incentive offers. No point of sale involvement by the merchant is required. No point of sale changes are required, e.g., training of check out clerks, etc. Consumers can be induced to click and pay attention to advertisements even if they don't use them. The system and method can drive payments to an issuer or transaction handler, such as Visa® from merchants and suppliers of branded products. The system and method can be utilized for all manner of account card transactions, such as card not present (“CNP”), Web transactions or portable user communication device transactions, including card on file and card not on file, transactions, but also, in addition, card present store transactions. Appropriate security measures for CNP transactions may be employed as are well known in the art.

It will also be understood by those skilled in the art that the system and method of the presently disclosed subject matter can serve to provide a merchant with a service which can enable merchants to define their own kickers and offers, i.e., advertised incentives, such as statement credit incentives. It can increase the velocity of offers made by or on behalf of a merchant and thus in turn increase the velocity of payment transactions, including qualifying transactions. The system and method can reduce the existing requirements for involvement and coordination between the merchant and the entity associated with running current offer campaigns, especially dynamically changing incentive/offer campaigns, such as statement credit campaigns, as to which the merchant may desire a good degree of dynamically executable flexibility, such as in designing and in activating and deactivating the incentive program.

It can also reduce the ongoing technology burden for merchants to update their web site for kickers and offers, such as advertised incentives. A merchant, according to one embodiment, can make a single change to their web-site, or to an advertisement already appearing on the web site or the web site of another advertisement publisher, or to an advertisement appearing on the web site of an issuer or transaction handler, such as through a portal to the web site of the transaction handler. the merchant can then manage ad hoc offers and changes to offers, such as advertised incentives, especially ones that are desired to be very dynamic in content, requirements, and time available, such as statement credit advertised incentives, without further changes to the advertisement, the merchant site or the advertisement publishing site.

An example of such a system and method may be placed on an advertising publishing site, as an example www.sci-kids.com/myorangetoasterblog. The advertisements could be banner advertisements and could be coded and placed by a merchant, the site itself or an issuer or transaction handler or advertisement publishing broker, such as Google. The publisher site could have a special page for advertisements or the advertisement may appear on a popular page on the site, such as Sci-kids.com (“Surendra's site”), or could be related to a specific topic covered by the page or being discussed on the page, such as a blog page. the topic, as an example could be “Orange Colored Toasters.” Key words, metatags and the like can be on the site/page, e.g., to draw search engines, such as Google to the site, e.g., for advertisement placement, such as Try Rightcliq by Visa.

As another example of a system and method according to aspects of embodiments of the disclosed subject matter, as part of a one time activity, the issuer or transaction handler, such as Visa® can bring on a merchant, such as by having the merchant log on to a Merchant Offer Portal, e.g., on the Visa® transaction handler web site, or on the main web site of Visa®. The merchant can enter terms of an advertised incentive program, such as a statement credit program, and activate the service so the advertised incentive program appears on the merchant web site or other publishing web site with or without advertisements for the merchant, thus establishing a trigger, such as an advertised incentive, such as a statement credit, trigger. The merchant can return anytime later to the Merchant Offer Portal, and turn off the incentive program, i.e., deactivate the trigger, and e.g., the advertisement banner will disappear from the appropriate web site(s). The terms of an advertised incentive campaign can be passed to the statement credit processor 116, e.g., in daily batches.

Through the log on using the Merchant Offer Portal, details of the advertised incentive, such as a statement credit program, can be captured and stored by, e.g., the transaction handler, such as Visa®. Thus the details comprising the advertised incentive program trigger can be made available by the merchant to the transaction handler, though also subject to future modification by the merchant. The incentive program, such as the statement credit incentive program, may be subject to configuration by the merchant. such configuration may be done by the merchant through the portal, and may include defining the substance of the incentive itself, such as the amount of a statement credit, and the activation/deactivation of the incentive program, i.e., activating the trigger or deactivating the trigger. Periodically, according to an embodiment, such as each evening, a batch of statement credit activated triggers can be compared to actual transactions for which the transaction handler authorized payments during that day and qualifying purchase transactions identified by the activated triggers, and appropriate transactions as noted above made to implement the incentive, such as the statement credit. Optionally an alert can be sent to the customer of the implemented statement credit, before sending the usual account statement of the statement credit transaction.

A Merchant can pick real estate on its check out page and make a one time change to the merchant's system. It can be on the check out page or any other page which will help encourage a sale. When the merchant isn't using the advertised incentive service, the space is blank or contains a simple message unrelated to advertised incentives. When the merchant has the service turned on, i.e., the advertised incentive trigger is activated, the merchant has the ability to create/modify the message and the terms, and the transaction processor powers the back end.

The message can be, as an example, “Click here, fill out your Visa® details, and receive a 10% Visa® statement credit if you complete this purchase in the next 2 hours!” A user clicks the link and a new window or a pop-up can then be launched. Alternatively it could be a wholly new window and not a true pop-up. This new window/pop-up could present the user with an opportunity to enroll in the advertised incentive program, such as by entering an account number for a payment account card of the user and the name of the user, e.g., in response to a prompt, such as, “Create Statement Credit Request—would you like to receive a 10% credit on your account for this purchase?” The purchase can them be made, e.g., using the card for which the information was previously entered in registering and the statement credit is received by the card account holder.

The following is a disclosure by way of example of a computing device which may be used with the presently disclosed subject matter. The description of the various components of a computing device is not intended to represent any particular architecture or manner of interconnecting the components. Other systems that have fewer or more components may also be used with the disclosed subject matter. A communication device may constitute a form of a computing device and may at least include a computing device. The computing device may include an inter-connect (e.g., bus and system core logic), which can interconnect such components of a computing device to a data processing device, such as a processor(s) or microprocessor(s), or other form of partly or completed programmable or pre-programmed logic circuitry, such as a controller or microcontroller, a digital signal processor, or any other form of device that can fetch instructions, operate on fetched instructions or pre-loaded/pre-programmed instructions, to carry out logic operations that, together, perform operations of processes and whole processes and functionalities as described in the present disclosure.

The data processing device may be formed by customized logic or by application specific integrated circuit (“ASIC”) logic such as gate arrays or standard cells or the like, implementing customized logic on the base ASIC architecture. The interconnect may connect the data processing device to memory. The interconnect may be internal to the data processing device, such as coupling a microprocessor to on board cache memory or external memory such as main memory, or a disk drive. Commercially available microprocessors, one or more of which could be a computing device or part of a computing device, include a PA-RISC series microprocessor from Hewlett-Packard Company, an 80×86 or Pentium series microprocessor from Intel Corporation, a PowerPC microprocessor from IBM, a Sparc microprocessor from Sun Microsystems, Inc, or a 68xxx series microprocessor from Motorola Corporation.

The inter-connect in addition to interconnecting such as microprocessor(s) and memory may also interconnect such elements to a display controller and display device, and/or to peripheral devices such as input/output (I/O) devices, e.g., through an input/output controller(s). Typical I/O devices can include a mouse, a keyboard(s), a modem(s), network interfaces, printers, scanners, video cameras and other devices which are well known in the art. The inter-connect may include one or more buses connected to one another through various bridges, controllers and/or adapters. In one embodiment the I/O controller includes a Universal Serial Bus (“USB”) adapter for controlling USB peripherals, and/or an IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.

The memory may include any tangible computer-readable media, which may include but are not limited to recordable and non-recordable type media such as volatile and non-volatile memory devices, such as volatile Random Access Memory (“RAM”), typically implemented as dynamic RAM (“DRAM”) which requires power continually in order to refresh or maintain the data in the memory, and non-volatile Read Only Memory (“ROM”), and other types of non-volatile memory, such as a hard drive, flash memory, etc. Non-volatile memory typically may include a magnetic hard drive, a magnetic optical drive, or an optical drive (e.g., a DVD RAM, a CD ROM, a DVD or a CD), or other type of memory system which maintains data even after power is removed from the system.

A server could be made up of one or more computing devices. Servers can be utilized, e.g., in a network to host a network database, compute necessary variables and information from information in the database(s), store and recover information from the database(s), track information and variables, provide interfaces for uploading and downloading information and variables, and/or sort or otherwise manipulate information and data from the database(s). In one embodiment a server can be used in conjunction with other computing devices positioned locally or remotely to perform certain calculations and functions.

In general, the routines executed to implement the embodiments of the disclosed subject matter may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions usually referred to as “computer programs,” or “software.” The computer programs typically comprise instructions stored at various times in various tangible memory and storage devices in a computing device, such as in cache memory, main memory, internal or external disk drives, and other remote storage devices, such as a disc farm, and when read and executed by a processor(s) in the computing device, cause the computing device to perform a method(s), e.g., process and operation steps to execute an element(s) as part of some aspect(s) of the disclosed subject matter.

In one embodiment, a user terminal can be a computing device, such as a in the form of a PDA, a cellular phone, a notebook computer, a personal desktop computer, etc. Alternatively, the traditional communication server communications client(s) may be used in some embodiments of the present invention.

While some embodiments of the disclosed subject matter have been described in the context of fully functioning computing devices and computing systems, those skilled in the art will appreciate that various embodiments of the disclosed subject matter are capable of being distributed, e.g., as a program product in a variety of forms and are capable of being applied regardless of the particular type of computing device machine or computer-readable media used to actually effect the distribution.

In various embodiments, hardwired circuitry, such as an ASIC(s), may be used in combination with software instructions to implement an aspect(s) of the disclosed subject matter. Thus, the techniques are not limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by any part of the computing device(s). Various functions and operations which have been described as being performed by or caused by software code to simplify description, will be understood by those skilled in the art to mean that the function(s) results from execution of the code by a processor, as a computing device or part of a computing device.

Although some of the drawings illustrate a number of operations in a particular order, operations which are not order dependent may be reordered and other operations may be combined or broken out. While some reordering or other groupings may have been specifically mentioned, others will be apparent to those of ordinary skill in the art and so the disclosed subject matter does not present an exhaustive list of alternatives.

It should also be recognized that the aspects of the disclosed subject matter may be implemented in parallel or seriatim in hardware, firmware, software or any combination(s) thereof co-located or remotely located at least in part from each other. The disclosed subject matter has been described with reference to one or more specific exemplary embodiments thereof.

It will be evident that various modifications may be made to the disclosed subject matter without departing from the broader spirit and scope of the disclosed subject matter as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense for explanation of aspects of the disclosed subject matter rather than a restrictive or limiting sense.

The various operations or acts in a method or process may be performed in the order shown, or may be performed in another order. Additionally, one or more process or method operations may be omitted or one or more process or method operations may be added to the methods and processes. An additional operation, block, or action may be added in the beginning, end, or intervening existing elements of the methods and processes. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods for various implements. Moreover, it is understood that a functional operation of described methods or processes, and combinations thereof can be implemented by computer program instructions that, when executed by a processor, create means for implementing the functional operations. The instructions may be included in computer readable medium that can be loaded onto a general purpose computer, a special purpose computer, or other programmable apparatus.

It is understood that the examples and implementations described herein are for illustrative purposes only and that various modifications or changes in light thereof will be suggested to persons skilled in the art and are to be included within the spirit and purview of this application and scope of the appended claims.

Claims

1. A method comprising: providing a computing apparatus comprising: a transaction handler to process transactions of an account holder,a communication portal, coupled to the transaction handler, configured to receive communications from a merchant computing device regarding advertised incentives for display in a shopping cart of the merchant, andat least one database, coupled for access by the transaction handler, configured to store registration information for advertised incentives;providing, by the communication portal, a merchant interface to allow the merchant to create an advertised incentive program by specifying an advertised incentive program configuration, the merchant interface further allowing the merchant to instantly activate the advertised incentive program and to instantly deactivate the advertised incentive program, the advertised incentive program configuration defining an advertised incentive and defining what transaction is qualified for the advertised incentive, and the merchant interface further allowing the merchant to disable the advertised incentive based on receiving, from the merchant computing device, a change in configuration for the advertised incentive;receiving, as part of the advertised incentive program configuration, via the communication portal, an advertised incentive image and an alternate image;storing, in the at least one database, the advertised incentive program configuration and an indication that the merchant has activated the advertised incentive program;receiving, from a server that provides the shopping cart, an assigned identifier for the advertised incentive;sending, by the transaction handler, to the server, based on the advertised incentive program configuration, content for an advertised incentive banner of the shopping cart for display to the account holder, the content to include the advertised incentive image when the advertised incentive is enabled and to include the alternate image when the advertised incentive is disabled, the sending the content to control the shopping cart in a website of the merchant so as to display the advertised incentive image when activated by the account holder in the shopping cart, and to enable a transaction using the advertised incentive when a purchase device of the merchant generates an authorization request for the transaction;reserving, by software rendering the website, an area in the shopping cart for the advertised incentive banner;providing, by the transaction handler, the content directly to the reserved area;receiving, by the transaction handler, while the advertised incentive program is activated, the authorization request from the purchase device to authorize a qualifying purchase transaction, the qualifying purchase transaction qualifying for the advertised incentive according to the advertised incentive program configuration;executing, by the transaction handler, the advertised incentive with respect to a payment account of the account holder, upon which payment account the qualifying purchase transaction was authorized; andin response to receiving the authorization request, sending, by the transaction handler, to the purchase device, authorization data to cause the purchase device to complete the qualifying purchase transaction.
2. The method of claim 1, wherein the advertised incentive comprises a statement credit incentive.
3. The method of claim 2, further comprising receiving input from the account holder to register for the advertised incentive.
4. The method of claim 3, further comprising: crediting the payment account of the account holder according to the statement credit incentive;debiting the payment account of the account holder according to the qualifying purchase transaction; anddebiting an account of at least one entity responsible for funding the statement credit.
5. The method of claim 2, further comprising: crediting the payment account of the account holder according to the statement credit incentive;debiting the payment account of the account holder according to the qualifying purchase transaction; anddebiting an account of at least one entity responsible for funding the statement credit.
6. The method of claim 2, wherein the advertised incentive program configuration defines what transaction is qualified for the advertised incentive via at least one of: defining one of a product or a service, to be purchased in the qualifying purchase transaction;defining a time period in which to complete the qualifying purchase transaction;defining a consumer purchase account with which to complete the qualifying purchase transaction; ordefining a merchant location where the qualifying purchase transaction is to occur.
7. The method of claim 1, further comprising receiving input from the account holder to register for the advertised incentive.
8. The method of claim 1, wherein the advertised incentive program configuration defines what transaction is qualified for the advertised incentive via at least one of: defining one of a product or a service, to be purchased in the qualifying purchase transaction;defining a time period in which to complete the qualifying purchase transaction;defining a consumer purchase account with which to complete the qualifying purchase transaction; ordefining a merchant location where the qualifying purchase transaction is to occur.
9. The method of claim 1, further comprising storing a cookie on a web browser of the account holder, and receiving the assigned identifier for the advertised incentive from the cookie.
10. The method of claim 9, wherein the assigned identifier further identifies registration information for the account holder.
11. The method of claim 9, further comprising using the cookie to recall previously-provided registration information for the account holder.
12. The method of claim 1, wherein the advertised incentive banner is configured so that the account holder can register for the advertised incentive by activating the advertised incentive banner.
13. The method of claim 12, further comprising receiving, upon activation of the advertised incentive banner, a request for a statement credit registration form.
14. The method of claim 1, wherein the content for the advertised incentive banner of the shopping cart further includes text.
15. A non-transitory, tangible machine readable medium storing instructions, the instructions, when executed by a computing device, causing the computing device to: provide, by a communication portal, a merchant interface allowing a merchant to create an advertised incentive program by specifying an advertised incentive program configuration, the merchant interface further allowing the merchant to instantly activate the advertised incentive program and to instantly deactivate the advertised incentive program, the advertised incentive program configuration defining an advertised incentive and defining what transaction is qualified for the advertised incentive, the communication portal coupled to a transaction handler, and the communication portal configured to receive communications from a merchant computing device regarding advertised incentives for display in a shopping cart of the merchant, and the merchant interface further allowing the merchant to disable the advertised incentive based on receiving, from the merchant computing device, a change in configuration for the advertised incentive;receive, as part of the advertised incentive program configuration, via the communication portal, an advertised incentive image and an alternate image;store in at least one database the advertised incentive program configuration and an indication that the merchant has activated the advertising incentive program, the at least one database coupled for access by the transaction handler, and configured to store registration information for advertised incentives;receive, from a server that provides the shopping cart, an assigned identifier for the advertised incentive;send, by the transaction handler, to the server, based on the advertised incentive program configuration, content for an advertised incentive banner of the shopping cart for display to an account holder, the content to include the advertised incentive image when the advertised incentive is enabled and to include the alternate image when the advertised incentive is disabled, the sending the content to control the shopping cart in a website of the merchant so as to display the advertised incentive image when activated by the account holder in the shopping cart, and to enable a transaction using the advertised incentive when a purchase device of the merchant generates an authorization request for the transaction;reserve, by software rendering the website, an area in the shopping cart for the advertised incentive banner;provide, by the transaction handler, the content directly to the reserved area;receive, by the transaction handler, while the advertised incentive program is activated, the authorization request from the purchase device to authorize a qualifying purchase transaction, the qualifying purchase transaction qualifying for the advertised incentive according to the advertised incentive program configuration;execute, by the transaction handler, the advertised incentive with respect to a payment account of the account holder, upon which payment account the qualifying purchase transaction was authorized; andin response to receiving the authorization request, send, by the transaction handler, to the purchase device, authorization data to cause the purchase device to complete the qualifying purchase transaction.
16. The non-transitory, tangible machine readable medium of claim 15, wherein the advertised incentive includes a statement credit incentive.
17. A system comprising: a communication portal configured to receive communications from a merchant computing device regarding advertised incentives for display in a shopping cart of the merchant, the communication portal further configured to provide a merchant interface allowing a merchant to create an advertised incentive program by specifying an advertised incentive program configuration, the merchant interface further allowing the merchant to instantly activate the advertised incentive program and to instantly deactivate the advertised incentive program, the advertised incentive program configuration defining an advertised incentive and defining what transaction is qualified for the advertised incentive, the communication portal further configured to receive, as part of the advertised incentive program configuration, an advertised incentive image and an alternate image, and the merchant interface further allowing the merchant to disable the advertised incentive based on receiving, from the merchant computing device, a change in configuration for the advertised incentive;at least one database storing the advertised incentive configuration and an indication that the merchant has activated the advertised incentive program, the at least one database configured to store registration information for advertised incentives; anda transaction handler to process transactions of a consumer, the transaction handler configured to receive, from a server that provides the shopping cart, an assigned identifier for the advertised incentive, and to send content for an advertised incentive banner of the shopping cart for display to the consumer, the content to include the advertised incentive image when the advertised incentive is enabled and to include the alternate image when the advertised incentive is disabled, the sending the content to control the shopping cart in a website of the merchant so as to display the advertised incentive image when activated by the consumer in the shopping cart, and to enable a transaction using the advertised incentive when a purchase device of the merchant generates an authorization request for the transaction;the server further configured to reserve, by software rendering the website, an area in the shopping cart for the advertised incentive banner;the transaction handler further configured to provide the content directly to the reserved area;the transaction handler further configured to receive, while the advertised incentive program is activated, the authorization request from the merchant to authorize a qualifying purchase transaction, the qualifying purchase transaction qualifying for the advertised incentive according to the advertised incentive program configuration;the transaction handler further configured to execute the advertised incentive with respect to a consumer payment account of the consumer upon which consumer payment account the qualifying purchase transaction was authorized;the transaction handler further configured to, in response to receiving the authorization request, send, by the transaction handler, to the purchase device, authorization data to cause the purchase device to complete the qualifying purchase transaction.
18. The system of claim 17, wherein the advertised incentive comprises a statement credit incentive.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of Prov. U.S. Pat. App. Ser. No. 61/316,336, filed Mar. 22, 2010 and entitled “Merchant Configured Advertised Incentives Funded Through Statement Credits,” the disclosure of which is hereby incorporated herein by reference.

US Referenced Citations (561)

Number	Name	Date	Kind
4613904	Lurie	Sep 1986	A
5401946	Weinblatt	Mar 1995	A
5592560	Deaton et al.	Jan 1997	A
5604921	Alanara	Feb 1997	A
5621812	Deaton et al.	Apr 1997	A
5638457	Deaton et al.	Jun 1997	A
5684990	Boothby	Nov 1997	A
5687322	Deaton et al.	Nov 1997	A
5710886	Christensen et al.	Jan 1998	A
5745036	Clare	Apr 1998	A
5806045	Biorge et al.	Sep 1998	A
5870030	DeLuca et al.	Feb 1999	A
5923016	Fredregill et al.	Jul 1999	A
5924080	Johnson et al.	Jul 1999	A
5945653	Walker et al.	Aug 1999	A
5974396	Anderson et al.	Oct 1999	A
6035280	Christensen et al.	Mar 2000	A
6061660	Eggleston	May 2000	A
6067529	Ray et al.	May 2000	A
6070147	Harms et al.	May 2000	A
6119101	Peckover	Sep 2000	A
6216129	Eldering	Apr 2001	B1
6222914	McMullin	Apr 2001	B1
6282522	Davis	Aug 2001	B1
6285983	Jenkins	Sep 2001	B1
6292786	Deaton et al.	Sep 2001	B1
6298330	Gardenswartz	Oct 2001	B1
6307958	Deaton et al.	Oct 2001	B1
6313732	DeLuca et al.	Nov 2001	B1
6318631	Halperin	Nov 2001	B1
6318911	Kitahara	Nov 2001	B1
6321201	Jenkins	Nov 2001	B1
6332126	Peirce et al.	Dec 2001	B1
6334108	Deaton et al.	Dec 2001	B1
6334110	Walter	Dec 2001	B1
6377935	Deaton et al.	Apr 2002	B1
6505046	Baker	Jan 2003	B1
6505168	Rothman	Jan 2003	B1
6519571	Guheen	Feb 2003	B1
6578006	Saito et al.	Jun 2003	B1
6606745	Maggio	Aug 2003	B2
6647257	Owensby	Nov 2003	B2
6647269	Hendrey et al.	Nov 2003	B2
6685093	Challa et al.	Feb 2004	B2
6736322	Gobburu et al.	May 2004	B2
6749120	Hung et al.	Jun 2004	B2
6775539	Deshpande	Aug 2004	B2
6856992	Britton et al.	Feb 2005	B2
6877665	Challa et al.	Apr 2005	B2
6901406	Nabe	May 2005	B2
6912398	Domnitz	Jun 2005	B1
6922686	Okamoto et al.	Jul 2005	B2
6938022	Singhal	Aug 2005	B1
6941376	Mitchell et al.	Sep 2005	B2
6996560	Choi	Feb 2006	B1
7003476	Samra	Feb 2006	B1
7013286	Aggarwal et al.	Mar 2006	B1
7024374	Day	Apr 2006	B1
7024409	Iyengar	Apr 2006	B2
7028906	Challa et al.	Apr 2006	B2
7035855	Kilger et al.	Apr 2006	B1
7039599	Merriman	May 2006	B2
7054830	Eggleston et al.	May 2006	B1
7062510	Eldering	Jun 2006	B1
7072847	Ulenas et al.	Jul 2006	B2
7107249	Dively	Sep 2006	B2
7120590	Eisen	Oct 2006	B1
7158943	Van Der Riet	Jan 2007	B2
7158955	Dively	Jan 2007	B2
7165037	Lazarus et al.	Jan 2007	B2
7177822	Mahmood et al.	Feb 2007	B2
7181412	Fulgoni	Feb 2007	B1
7194422	St. John Killick	Mar 2007	B1
7225142	Apte	May 2007	B1
7257545	Hung	Aug 2007	B1
7260837	Abraham	Aug 2007	B2
7264152	Tsuei et al.	Sep 2007	B2
7269578	Sweeney	Sep 2007	B2
7299194	Manganaris	Nov 2007	B1
7308254	Rissanen	Dec 2007	B1
7328169	Temares	Feb 2008	B2
7330110	Heintzman et al.	Feb 2008	B1
7337127	Smith	Feb 2008	B1
7340438	Nordman et al.	Mar 2008	B2
7360251	Spalink et al.	Apr 2008	B2
7373311	Lambert et al.	May 2008	B2
7401032	Golden et al.	Jul 2008	B1
7424439	Fayyad et al.	Sep 2008	B1
7424441	George	Sep 2008	B2
7444658	Matz et al.	Oct 2008	B1
7464859	Hawkins	Dec 2008	B1
7467106	Levine et al.	Dec 2008	B1
7490052	Kilger et al.	Feb 2009	B2
7493655	Brown	Feb 2009	B2
7526485	Hagan et al.	Apr 2009	B2
7529687	Phan	May 2009	B1
7533038	Blume	May 2009	B2
7536360	Stolfo et al.	May 2009	B2
7552069	Kepecs	Jun 2009	B2
7562030	Shapira	Jul 2009	B1
7578435	Suk	Aug 2009	B2
7613628	Ariff et al.	Nov 2009	B2
7665660	Degliantoni et al.	Feb 2010	B2
7668785	Hammad	Feb 2010	B1
7680688	Hessburg et al.	Mar 2010	B2
7686218	Hessburg et al.	Mar 2010	B2
7729977	Xiao et al.	Jun 2010	B2
7747524	Brown	Jun 2010	B2
7792518	Trioano	Sep 2010	B2
7828206	Hessburg et al.	Nov 2010	B2
7912751	Allos	Mar 2011	B1
7937291	Carlson et al.	May 2011	B2
7970705	Patterson	Jun 2011	B2
8019685	Patterson	Sep 2011	B2
8046256	Chien et al.	Oct 2011	B2
8050969	Golden et al.	Nov 2011	B2
8099318	Moukas et al.	Jan 2012	B2
8103588	Patterson	Jan 2012	B2
8229819	Ransom et al.	Jul 2012	B2
8311845	Vengroff et al.	Nov 2012	B2
8313023	McGhie et al.	Nov 2012	B1
8341038	Rolf et al.	Dec 2012	B1
8342399	McGhie et al.	Jan 2013	B1
8355948	Mason	Jan 2013	B2
8359274	Yoder et al.	Jan 2013	B2
8407148	Yoder et al.	Mar 2013	B2
8448072	Lai et al.	May 2013	B1
8478692	Carlson et al.	Jul 2013	B2
8511550	McGhie et al.	Aug 2013	B1
8554670	Blank et al.	Oct 2013	B1
8670925	Gluck	Mar 2014	B2
8750906	Winkler et al.	Jun 2014	B2
8751295	Tiku et al.	Jun 2014	B2
9058604	Carr et al.	Jun 2015	B2
9076303	Park et al.	Jul 2015	B1
9097544	Dhanani et al.	Aug 2015	B2
9324088	Yoder et al.	Apr 2016	B2
9443253	Carlson et al.	Sep 2016	B2
9466075	Carlson et al.	Oct 2016	B2
9477967	Spears et al.	Oct 2016	B2
20010027413	Bhutta	Oct 2001	A1
20010037205	Joao	Nov 2001	A1
20010049620	Blasko	Dec 2001	A1
20010054003	Chien et al.	Dec 2001	A1
20020002597	Morrell, Jr.	Jan 2002	A1
20020004733	Addante	Jan 2002	A1
20020004754	Gardenswartz et al.	Jan 2002	A1
20020042738	Srinivasanet et al.	Apr 2002	A1
20020046187	Vargaset et al.	Apr 2002	A1
20020049644	Kargman	Apr 2002	A1
20020049664	Hoffman et al.	Apr 2002	A1
20020053076	Landesmann	May 2002	A1
20020059100	Shore	May 2002	A1
20020060246	Gobburu et al.	May 2002	A1
20020065713	Awada et al.	May 2002	A1
20020065723	Anderson et al.	May 2002	A1
20020070278	Hung et al.	Jun 2002	A1
20020072972	Lamont	Jun 2002	A1
20020077871	Udelhoven et al.	Jun 2002	A1
20020082918	Warwick	Jun 2002	A1
20020082920	Austin et al.	Jun 2002	A1
20020091569	Kitaura et al.	Jul 2002	A1
20020095333	Jokinen et al.	Jul 2002	A1
20020099649	Lee et al.	Jul 2002	A1
20020102993	Hendrey et al.	Aug 2002	A1
20020103703	Spetalnick	Aug 2002	A1
20020123928	Eldering et al.	Sep 2002	A1
20020128916	Beinecke, III	Sep 2002	A1
20020138346	Kodaka	Sep 2002	A1
20020174013	Freeman et al.	Nov 2002	A1
20020174036	Coyle	Nov 2002	A1
20030018530	Walker et al.	Jan 2003	A1
20030033179	Katz et al.	Feb 2003	A1
20030033242	Lynch et al.	Feb 2003	A1
20030046153	Robibero	Mar 2003	A1
20030047602	Iida et al.	Mar 2003	A1
20030058261	Challa et al.	Mar 2003	A1
20030093314	Leung et al.	May 2003	A1
20030191832	Satyavolu et al.	Oct 2003	A1
20030212595	Antonucci	Nov 2003	A1
20030220841	Maritzen	Nov 2003	A1
20030225618	Hessburg et al.	Dec 2003	A1
20030225630	Kakuta	Dec 2003	A1
20030230630	Whipple et al.	Dec 2003	A1
20040010447	Asayama	Jan 2004	A1
20040019518	Abraham	Jan 2004	A1
20040054575	Marshall	Mar 2004	A1
20040054581	Redford	Mar 2004	A1
20040054591	Spaeth et al.	Mar 2004	A1
20040093512	Sample	May 2004	A1
20040122735	Meshkin	Jun 2004	A1
20040122736	Strock et al.	Jun 2004	A1
20040144839	Warwick	Jul 2004	A1
20040148224	Gauthier et al.	Jul 2004	A1
20040167815	DeLaHunt	Aug 2004	A1
20040193685	Proehl	Sep 2004	A1
20040225509	Andre	Nov 2004	A1
20040225603	Allen et al.	Nov 2004	A1
20040267611	Hoerenz	Dec 2004	A1
20050055275	Newman et al.	Mar 2005	A1
20050060248	O'Neal	Mar 2005	A1
20050071225	Bortolin et al.	Mar 2005	A1
20050071227	Hammad et al.	Mar 2005	A1
20050071235	Nguyen et al.	Mar 2005	A1
20050125342	Schiff	Jun 2005	A1
20050131761	Trika et al.	Jun 2005	A1
20050133590	Rettenmyer et al.	Jun 2005	A1
20050144074	Fredregill et al.	Jun 2005	A1
20050160002	Roetter	Jul 2005	A1
20050210387	Alagappan et al.	Sep 2005	A1
20050216334	Mehrabani-Farsi	Sep 2005	A1
20050216823	Petersen et al.	Sep 2005	A1
20050240474	Li	Oct 2005	A1
20050242179	Warwick	Nov 2005	A1
20050267812	Jensen et al.	Dec 2005	A1
20060002189	Berkman	Jan 2006	A1
20060004613	Roller et al.	Jan 2006	A1
20060053056	Alspach-Goss et al.	Mar 2006	A1
20060085252	Kersenbrock	Apr 2006	A1
20060085260	Yamagishi	Apr 2006	A1
20060085263	Greer et al.	Apr 2006	A1
20060111967	Forbes	May 2006	A1
20060122921	Comerford et al.	Jun 2006	A1
20060143071	Hofmann	Jun 2006	A1
20060143075	Carr et al.	Jun 2006	A1
20060161527	Dwork et al.	Jul 2006	A1
20060167818	Wentker et al.	Jul 2006	A1
20060173736	Huyser et al.	Aug 2006	A1
20060178957	LeClaire	Aug 2006	A1
20060190337	Ayers, Jr.	Aug 2006	A1
20060200403	Friss	Sep 2006	A1
20060212900	Ismail et al.	Sep 2006	A1
20060235746	Hammond et al.	Oct 2006	A1
20060242017	Libes et al.	Oct 2006	A1
20060247978	Davis	Nov 2006	A1
20060289631	Stretch et al.	Dec 2006	A1
20060293948	Weinblatt	Dec 2006	A1
20060293959	Hogan	Dec 2006	A1
20070027771	Collins et al.	Feb 2007	A1
20070038516	Apple et al.	Feb 2007	A1
20070045405	Rothschild	Mar 2007	A1
20070055597	Patel	Mar 2007	A1
20070067267	Ives	Mar 2007	A1
20070067297	Kublickis et al.	Mar 2007	A1
20070084917	Fajkowski	Apr 2007	A1
20070094114	Bufford et al.	Apr 2007	A1
20070100691	Patterson et al.	May 2007	A1
20070106464	Yamada	May 2007	A1
20070106556	Edwards et al.	May 2007	A1
20070124201	Hu et al.	May 2007	A1
20070136131	Mankoff	Jun 2007	A1
20070136135	Loeger et al.	Jun 2007	A1
20070156470	Granucci et al.	Jul 2007	A1
20070162377	Williams	Jul 2007	A1
20070174295	Abraham	Jul 2007	A1
20070192121	Routson	Aug 2007	A1
20070192122	Routson et al.	Aug 2007	A1
20070208671	Brown et al.	Sep 2007	A1
20070208704	Ives	Sep 2007	A1
20070219865	Leining	Sep 2007	A1
20070219866	Wolf et al.	Sep 2007	A1
20070226056	Belanger	Sep 2007	A1
20070226061	Chen et al.	Sep 2007	A1
20070239521	Khadpe et al.	Oct 2007	A1
20070239532	Benson et al.	Oct 2007	A1
20070241189	Slavin et al.	Oct 2007	A1
20070244741	Blume	Oct 2007	A1
20070260523	Schadt et al.	Nov 2007	A1
20070260736	Miller	Nov 2007	A1
20070265920	Bistriceanu et al.	Nov 2007	A1
20070265921	Rempe et al.	Nov 2007	A1
20070265923	Krassner et al.	Nov 2007	A1
20070282681	Shubert et al.	Dec 2007	A1
20080004884	Flake	Jan 2008	A1
20080021784	Hessburg et al.	Jan 2008	A1
20080021785	Hessburg et al.	Jan 2008	A1
20080027810	Lerner et al.	Jan 2008	A1
20080040229	Gholston	Feb 2008	A1
20080059302	Fordyce, III	Mar 2008	A1
20080059303	Fordyce, III	Mar 2008	A1
20080059306	Fordyce, III	Mar 2008	A1
20080059307	Fordyce, III et al.	Mar 2008	A1
20080071587	Granucci et al.	Mar 2008	A1
20080071680	Sheets	Mar 2008	A1
20080077487	Davis	Mar 2008	A1
20080082393	Ozzie et al.	Apr 2008	A1
20080082418	Fordyce, III	Apr 2008	A1
20080103887	Oldham	May 2008	A1
20080103968	Bies et al.	May 2008	A1
20080120182	Arnold et al.	May 2008	A1
20080120218	Reid et al.	May 2008	A1
20080133345	Cordery et al.	Jun 2008	A1
20080133350	White et al.	Jun 2008	A1
20080133351	White et al.	Jun 2008	A1
20080133366	Evans et al.	Jun 2008	A1
20080134228	Dion et al.	Jun 2008	A1
20080147481	Robinson et al.	Jun 2008	A1
20080154654	Niessen et al.	Jun 2008	A1
20080154703	Flake	Jun 2008	A1
20080154704	Flake	Jun 2008	A1
20080154727	Carlson	Jun 2008	A1
20080162258	Kala et al.	Jul 2008	A1
20080162269	Gilbert	Jul 2008	A1
20080163257	Carlson et al.	Jul 2008	A1
20080167000	Wentker et al.	Jul 2008	A1
20080167961	Wentker et al.	Jul 2008	A1
20080167991	Carlson et al.	Jul 2008	A1
20080167992	Kokernak	Jul 2008	A1
20080177602	Sopher et al.	Jul 2008	A1
20080183480	Carlson et al.	Jul 2008	A1
20080184117	Alsbury et al.	Jul 2008	A1
20080195465	Redmond et al.	Aug 2008	A1
20080195466	Wright	Aug 2008	A1
20080195473	Laramy	Aug 2008	A1
20080201226	Carlson	Aug 2008	A1
20080201472	Bistriceanu et al.	Aug 2008	A1
20080215429	Ramer et al.	Sep 2008	A1
20080215436	Roberts et al.	Sep 2008	A1
20080217397	Degliantoni et al.	Sep 2008	A1
20080221972	Megdal et al.	Sep 2008	A1
20080221975	Steul	Sep 2008	A1
20080222038	Eden et al.	Sep 2008	A1
20080228563	Zellner et al.	Sep 2008	A1
20080228582	Fordyce et al.	Sep 2008	A1
20080233984	Franklin	Sep 2008	A1
20080235091	Holliday	Sep 2008	A1
20080235243	Lee et al.	Sep 2008	A1
20080242317	Abhyanker	Oct 2008	A1
20080248815	Busch	Oct 2008	A1
20080262915	Gojkovic	Oct 2008	A1
20080300973	DeWitt et al.	Dec 2008	A1
20080313011	Rose et al.	Dec 2008	A1
20080318559	Porco et al.	Dec 2008	A1
20080319843	Moser	Dec 2008	A1
20080319847	Shepard	Dec 2008	A1
20080319889	Hammad	Dec 2008	A1
20080320512	Knight	Dec 2008	A1
20090006183	Paintin et al.	Jan 2009	A1
20090006203	Fordyce, III	Jan 2009	A1
20090006214	Lerman et al.	Jan 2009	A1
20090006363	Canny	Jan 2009	A1
20090018895	Weinblatt et al.	Jan 2009	A1
20090030793	Fordyce, III	Jan 2009	A1
20090043593	Herbrich et al.	Feb 2009	A1
20090070207	Engel et al.	Mar 2009	A1
20090070219	D'Angelo	Mar 2009	A1
20090070225	Matz et al.	Mar 2009	A1
20090076896	DeWitt et al.	Mar 2009	A1
20090076925	DeWitt et al.	Mar 2009	A1
20090081990	Granucci et al.	Mar 2009	A1
20090089169	Gupta et al.	Apr 2009	A1
20090099932	Ahopelto	Apr 2009	A1
20090112703	Brown	Apr 2009	A1
20090112721	Hammad et al.	Apr 2009	A1
20090119160	Woda	May 2009	A1
20090119167	Kendall	May 2009	A1
20090119170	Hammad et al.	May 2009	A1
20090132346	Duggal et al.	May 2009	A1
20090132347	Anderson et al.	May 2009	A1
20090132365	Gruenhagen et al.	May 2009	A1
20090132366	Lam	May 2009	A1
20090144201	Gierkink et al.	Jun 2009	A1
20090150211	Bayne	Jun 2009	A1
20090150232	Tyler et al.	Jun 2009	A1
20090157511	Spinnell	Jun 2009	A1
20090171747	Lanning et al.	Jul 2009	A1
20090172551	Kane	Jul 2009	A1
20090172728	Shkedi et al.	Jul 2009	A1
20090182634	Park et al.	Jul 2009	A1
20090192882	Narahashi	Jul 2009	A1
20090203387	Wold et al.	Aug 2009	A1
20090216579	Zen et al.	Aug 2009	A1
20090216616	Wang et al.	Aug 2009	A1
20090216620	Lee	Aug 2009	A1
20090222323	Kelly	Sep 2009	A1
20090222337	Sergiades	Sep 2009	A1
20090222348	Ransom et al.	Sep 2009	A1
20090234708	Heiser, II	Sep 2009	A1
20090234711	Ramer et al.	Sep 2009	A1
20090234737	Sarelson	Sep 2009	A1
20090248496	Hueter	Oct 2009	A1
20090248497	Hueter	Oct 2009	A1
20090248511	Mehta et al.	Oct 2009	A1
20090249384	Fang et al.	Oct 2009	A1
20090254414	Schwartz et al.	Oct 2009	A1
20090259518	Harvey et al.	Oct 2009	A1
20090265228	Sterling et al.	Oct 2009	A1
20090271275	Regmi et al.	Oct 2009	A1
20090271305	Lal et al.	Oct 2009	A1
20090271327	Lal	Oct 2009	A1
20090276304	Dorr	Nov 2009	A1
20090299941	McColgan et al.	Dec 2009	A1
20090319638	Faith et al.	Dec 2009	A1
20090327151	Carlson et al.	Dec 2009	A1
20090327286	Ge et al.	Dec 2009	A1
20090327331	Mathew et al.	Dec 2009	A1
20100008255	Khosravy et al.	Jan 2010	A1
20100010888	Maertz	Jan 2010	A1
20100017275	Carlson et al.	Jan 2010	A1
20100030688	Patterson	Feb 2010	A1
20100049588	Debow	Feb 2010	A1
20100049620	Debow	Feb 2010	A1
20100057549	Boal	Mar 2010	A1
20100057553	Ameiss et al.	Mar 2010	A1
20100057573	Singhal	Mar 2010	A1
20100082420	Trifiletti et al.	Apr 2010	A1
20100090901	Smith et al.	Apr 2010	A1
20100106568	Grimes	Apr 2010	A1
20100106569	Grimes	Apr 2010	A1
20100106570	Radu et al.	Apr 2010	A1
20100106596	Grimes	Apr 2010	A1
20100114677	Carlson	May 2010	A1
20100114683	Wessels	May 2010	A1
20100114686	Carlson	May 2010	A1
20100114703	Steelberg et al.	May 2010	A1
20100125490	Kiciman et al.	May 2010	A1
20100131415	Sartipi	May 2010	A1
20100136898	Farrow	Jun 2010	A1
20100138838	Lin et al.	Jun 2010	A1
20100145778	Fordyce, III et al.	Jun 2010	A1
20100145786	Fordyce, III et al.	Jun 2010	A1
20100153206	Gersovitz	Jun 2010	A1
20100167823	Winkler	Jul 2010	A1
20100169170	Fordyce, III et al.	Jul 2010	A1
20100174596	Gilman et al.	Jul 2010	A1
20100174623	McPhie	Jul 2010	A1
20100211694	Razmov et al.	Aug 2010	A1
20100241498	Chung et al.	Sep 2010	A1
20100250351	Gillenson et al.	Sep 2010	A1
20100262461	Bohannon	Oct 2010	A1
20100274566	Carlson	Oct 2010	A1
20100274625	Carlson	Oct 2010	A1
20100274627	Carlson	Oct 2010	A1
20100274653	Hammad	Oct 2010	A1
20100274655	Postrel	Oct 2010	A1
20100274866	Hammad et al.	Oct 2010	A1
20100280880	Faith	Nov 2010	A1
20100280881	Faith	Nov 2010	A1
20100280882	Faith	Nov 2010	A1
20100280914	Carlson	Nov 2010	A1
20100280927	Faith	Nov 2010	A1
20100280950	Faith	Nov 2010	A1
20100306029	Jolley	Dec 2010	A1
20100306032	Jolley	Dec 2010	A1
20100325047	Carlson et al.	Dec 2010	A1
20100325048	Carlson et al.	Dec 2010	A1
20110010292	Giordano et al.	Jan 2011	A1
20110022448	Strock et al.	Jan 2011	A1
20110029363	Gillenson et al.	Feb 2011	A1
20110029430	Norris et al.	Feb 2011	A1
20110029440	Motoyama et al.	Feb 2011	A1
20110035265	King et al.	Feb 2011	A1
20110035288	Clyne	Feb 2011	A1
20110047012	Sherman	Feb 2011	A1
20110047017	Lieblang et al.	Feb 2011	A1
20110054981	Faith et al.	Mar 2011	A1
20110065376	Forutanpour et al.	Mar 2011	A1
20110072035	Gaucas et al.	Mar 2011	A1
20110078004	Swanson, Sr.	Mar 2011	A1
20110087530	Fordyce, III et al.	Apr 2011	A1
20110087531	Winters et al.	Apr 2011	A1
20110093324	Fordyce, III et al.	Apr 2011	A1
20110125509	Lidstrom et al.	May 2011	A1
20110125565	Macllwaine et al.	May 2011	A1
20110131096	Frew et al.	Jun 2011	A1
20110131135	Carlson et al.	Jun 2011	A1
20110161142	Dunn et al.	Jun 2011	A1
20110161150	Steffens et al.	Jun 2011	A1
20110202401	Magadi et al.	Aug 2011	A1
20110208575	Bansal et al.	Aug 2011	A1
20110231258	Winters	Sep 2011	A1
20110246306	Blackhurst et al.	Oct 2011	A1
20110258026	Prince	Oct 2011	A1
20110270719	Hollars et al.	Nov 2011	A1
20110288906	Thomas et al.	Nov 2011	A1
20110288918	Cervenka et al.	Nov 2011	A1
20110288922	Thomas et al.	Nov 2011	A1
20110288924	Thomas et al.	Nov 2011	A1
20110288925	Thomas et al.	Nov 2011	A1
20110295670	Thomas et al.	Dec 2011	A1
20110295671	Thomas et al.	Dec 2011	A1
20110302011	Yoder	Dec 2011	A1
20110307318	LaPorte et al.	Dec 2011	A1
20110313837	Katz et al.	Dec 2011	A1
20120036034	Golden et al.	Feb 2012	A1
20120059702	Yoder et al.	Mar 2012	A1
20120066062	Yoder et al.	Mar 2012	A1
20120066064	Yoder et al.	Mar 2012	A1
20120072997	Carlson et al.	Mar 2012	A1
20120078697	Carlson et al.	Mar 2012	A1
20120078699	Carlson et al.	Mar 2012	A1
20120101894	Sterling et al.	Apr 2012	A1
20120109730	Yoder et al.	May 2012	A1
20120130859	Wolfe et al.	May 2012	A1
20120136704	Carlson	May 2012	A1
20120150609	Walker et al.	Jun 2012	A1
20120179367	Niu	Jul 2012	A1
20120191525	Singh et al.	Jul 2012	A1
20120197720	Bezancon et al.	Aug 2012	A1
20120209675	Tyler et al.	Aug 2012	A1
20120209777	Tredeau et al.	Aug 2012	A1
20120215637	Hermann	Aug 2012	A1
20120239472	Tyler et al.	Sep 2012	A1
20120239479	Amaro et al.	Sep 2012	A1
20120239498	Ramer et al.	Sep 2012	A1
20120244948	Dhillon et al.	Sep 2012	A1
20120252558	Mishra et al.	Oct 2012	A1
20120259695	Glassman et al.	Oct 2012	A1
20120259704	Monteverde	Oct 2012	A1
20120259842	Oman et al.	Oct 2012	A1
20120265545	Hwang et al.	Oct 2012	A1
20120265591	Hwang et al.	Oct 2012	A1
20120271689	Etheredge et al.	Oct 2012	A1
20120271691	Hammad et al.	Oct 2012	A1
20120271697	Gilman et al.	Oct 2012	A1
20120271703	Postrel	Oct 2012	A1
20120271706	Ransom et al.	Oct 2012	A1
20120278173	Vaidyanathan et al.	Nov 2012	A1
20120290950	Rapaport et al.	Nov 2012	A1
20120303425	Katzin et al.	Nov 2012	A1
20120310670	Pruitt	Dec 2012	A1
20120310838	Harris et al.	Dec 2012	A1
20120323664	Klems	Dec 2012	A1
20120330744	Aissa	Dec 2012	A1
20130006709	Kosta	Jan 2013	A1
20130030934	Bakshi et al.	Jan 2013	A1
20130046621	Asseoff et al.	Feb 2013	A1
20130046626	Grigg et al.	Feb 2013	A1
20130060585	Hornbaker et al.	Mar 2013	A1
20130080225	Rajaram	Mar 2013	A1
20130080237	Hart	Mar 2013	A1
20130085869	Carlson et al.	Apr 2013	A1
20130124417	Spears et al.	May 2013	A1
20130132205	Harris	May 2013	A1
20130132283	Hayhow et al.	May 2013	A1
20130144704	Williams et al.	Jun 2013	A1
20130151323	Shepard et al.	Jun 2013	A1
20130166365	Yoder et al.	Jun 2013	A1
20130173364	Choong Cheng Shien et al.	Jul 2013	A1
20130179264	Wilson	Jul 2013	A1
20130191195	Carlson et al.	Jul 2013	A1
20130191198	Carlson et al.	Jul 2013	A1
20130204703	Carlson et al.	Aug 2013	A1
20130210461	Moldavsky et al.	Aug 2013	A1
20130218664	Carlson et al.	Aug 2013	A1
20130218670	Spears et al.	Aug 2013	A1
20130238413	Carlson et al.	Sep 2013	A1
20130246148	Ross et al.	Sep 2013	A1
20130246150	Ovick et al.	Sep 2013	A1
20130262188	Leibner et al.	Oct 2013	A1
20130275222	Amaro et al.	Oct 2013	A1
20130332255	Carlson et al.	Dec 2013	A1
20130346170	Epstein et al.	Dec 2013	A1
20140074575	Rappoport	Mar 2014	A1
20140129306	Rappoport et al.	May 2014	A1
20140129313	Rappoport et al.	May 2014	A1
20140172534	Spears et al.	Jun 2014	A1
20140236672	Yoder et al.	Aug 2014	A1
20150120429	Salmon et al.	Apr 2015	A1
20150134528	Fineman et al.	May 2015	A1
20160196572	Yoder et al.	Jul 2016	A1

Foreign Referenced Citations (43)

Number	Date	Country
2000357204	Dec 2000	JP
2001501328	Jan 2001	JP
2009501891	Jan 2009	JP
1020010096672	Nov 2001	KR
1020030008894	Jan 2003	KR
1020040045622	Jun 2004	KR
20040107715	Dec 2004	KR
1020050113156	Dec 2005	KR
20070030415	Mar 2007	KR
1020080002731	Jan 2008	KR
20080104398	Dec 2008	KR
9922328	May 1999	WO
9950775	Oct 1999	WO
0003328	Jan 2000	WO
0060435	Oct 2000	WO
0062231	Oct 2000	WO
0137183	May 2001	WO
0139023	May 2001	WO
0157758	Aug 2001	WO
0193161	Dec 2001	WO
0205116	Jan 2002	WO
0214985	Feb 2002	WO
0219229	Mar 2002	WO
0242970	May 2002	WO
02071187	Sep 2002	WO
03025695	Mar 2003	WO
03081376	Oct 2003	WO
2005001631	Jan 2005	WO
2005072382	Aug 2005	WO
2005076181	Aug 2005	WO
2006028739	Mar 2006	WO
2006126205	Nov 2006	WO
2007131258	Nov 2007	WO
2007136221	Nov 2007	WO
2008013945	Jan 2008	WO
2008023912	Feb 2008	WO
2008055217	May 2008	WO
2008064343	May 2008	WO
2008067543	Jun 2008	WO
2008144643	Nov 2008	WO
2009144010	Dec 2009	WO
2010036915	Apr 2010	WO
2010141270	Dec 2010	WO

Non-Patent Literature Citations (77)

Entry
Cashmore, Pete, “YouTube Ads: YouHate Em,” available at http://mashable.com/2009/04/05/youtube-ads-youhate-em/#, Apr. 5, 2009.
International Patent Application PCT/US09/52766, International Search Report and Written Opinion, Mar. 11, 2010.
International Patent Application PCT/US2010/036076, International Search Report & Written Opinion, Dec. 30, 2010.
International Patent Application PCT/US2011/029401, International Search Report and Written Opinion,Dec. 20, 2011.
International Patent Application PCT/US2011/039051, International Search Report and Written Opinion, Feb. 17, 2012.
International Patent Application PCT/US2011/046702, International Search Report and Written Opinion, Feb. 28, 2012.
International Patent Application PCT/US2011/052465, International Search Report and Written Opinion, Mar. 2, 2012.
Li, Wen-Syan, “Knowledge Gathering and Matching in Heterogeneous Databases,” Working Notes of the AAAI Spring Symposium on Information Gathering, pp. 116-1216, Mar. 27, 1995.
Mielikäinen, Taneli, “Privacy Problems with Anonymized Transaction Databases,” 7th International Conference on Discovery Science, pp. 219-229, Oct. 2, 2004.
Punj, Girish et al. “Cluster Analysis in Marketing Research: Review and Suggestions for Application,” Journal of Marketing Research, vol. 20, pp. 134-148, May 1983.
Van Grove, Jennifer, “Are Your Online Video Ads Driving Actual Offline Purchases?”, available at http://mashable.com/2009/05/18/video-impact/#, May 18, 2009.
Anil Bawa-Cavia, “Sensing the Urban—Using location-based social network data in urban analysis”, Working Paper, Sep. 20, 2010.
Credit Card Finder: “Compare Cash Back Credit Cards and Credit Card Offers”; http://www.plasticrewards.com/, 2009, 1 page.
Credit Card Finder: “Cash Back Reward Credit Cards”; http://www.plasticrewards.com/creditcard/cash-back-reward/, 2009, 3 pages.
Credit Card Finder: “Airline Miles Reward Credit Cards”; http://www.plasticrewards.com/airline-miles-reward!, 2009, 2 pages.
Credit Card Finder: “Gas Reward Credit Cards”; http://www.plasticrewards.com/creditcard/gas-reward/, 2009, 3 pages.
Credit Card Finder: “Travel Reward Credit Cards”; http://www.plasticrewards.com/credit-card/travel-reward, 2009, 3 pages.
Credit Card Finder: “Reward Credit Cards”; http://www.plasticrewards.com/credit-card/reward/, 2009, 3 pages.
Credit Card Finder: “Hotel Reward Credit Cards”; http://www.plasticrewards.com/credit-card/hotel-reward/, 2009, 2 pages.
CreditCardGuide.com: “Use Cash Back Credit Cards”; http://www.creditcardguide.com/cashback.html/, 2009, 3 pages.
CreditCardGuide.com: “Cash Back Credit Cards”; http://www.creditcardguide.com/cashback2.htmll, 2009, 2 pages.
CreditCardGuide.com: “Use Reward Credit Cards”; http://www.creditcardguide.com/reward-point-credit-cards.html/, 2009, 3 pages.
CreditCardGuide.com: “Gas Rebate Credit Cards”; http://www.creditcardguide.com/gascards.html/, 2009, 2 pages.
CreditCardGuide.com: “With Airline Credit Cards, Frequent Flyer credit cards, and Travel Reward Credit Cards”; http://www.creditcardguide.com/airline-frequent-flyer-cards.html/, 2009,4 pages.
CreditCardGuide.com: “Use hotel reward credit cards and travel reward credit cards”; http://www.creditcardguide.com/hotel-reward-credit-cards.html/, 2009, 2 pages.
CreditCardGuide.com: “Dining and entertainment credit cards”; http://www.creditcardguide.com/dining-entertainment.html/, 2009, 3 pages.
CreditCardGuide.com: “Car rebate credit cards”; http://www.creditcardguide.com/car-rebate.html/, 2009, 2 pages.
CreditCardGuide.com: “Use retail reward credit cards and brand name reward credit cards”; http//www.creditcardguide.com/retail-brand-credit-cards.html/, 2009, 2 pages.
CreditCardGuide.com: “Use home improvement reward credit cards”; http://www.creditcardguide.com/home-improvement-credit-cards.html/, 2009, 2 pages.
CreditCardGuide.com: “Financial reward credit cards”; http://www.creditcardguide.com/financial-reward-credit-cards.html/, 2009, 2 pages.
CreditCardGuide.com: “Foundation and charity credit cards”; http://www.creditcardguide.com/foundations-charities.html/, 2009, 3 pages.
CreditCardGuide.com: “Sports and outdoor enthusiast credit cards”; http://www.creditcardguide.com/sports-outdoors.html/, 2009, 2 pages.
International Patent Application PCT/US2009/058412, International Search Report and Written Opinion, May 11, 2010.
International Patent Application PCT/US2012/029273, International Search Report and Written Opinion, Oct. 29, 2012.
International Patent Application PCT/US2011/059410 International Search Report and Written Opinion, Apr. 11, 2013.
International Patent Application PCT/US2013/022572 International Search Report and Written Opinion, Apr. 22, 2013.
International Patent Application PCT/US2013/024421 International Search Report and Written Opinion, May 8, 2013.
International Patent Application PCT/US13/24421, International Preliminary Report on Patentability,Aug. 5, 2014.
Anil Bawa-Cavia, “Sensing the Urban—Using location-based social network data in urban analysis”, Working Papter, Sep. 20, 2010.
Systems and Methods to Provide and Adjust Offers, U.S. Appl. No. 13/774,139, filed Feb. 22, 2013, Mark Carlson, et al, Mar. 16, 2016.
Systems and Methods to Provide and Adjust Offers, U.S. Appl. No. 15/231,413, filed Aug. 8, 2016, Mark Carlson, et al, Aug. 22, 2016.
Systems and Methods to Process Referrals in Offer Campaigns, U.S. Appl. No. 13/755,362, filed Jan. 31, 2013, Mark Carlson, et al, Allowed—Notice of Allowance Not Yet Mailed, May 27, 2016.
Systems and Methods to Process Referrals in Offer Campaigns, U.S. Appl. No. 15/252,670, filed Aug. 31, 2016, Mark Carlson, et al, Sep. 14, 2016.
Systems and Methods to Process an Offer Campaign Based on Ineligibility, U.S. Appl. No. 13/766,280, filed Feb. 13, 2013, Joseph Spears, et al, May 8, 2016.
Systems and Methods to Provide Generalized Notifications, U.S. Appl. No. 13/679,555, filed Nov. 16, 2012, Joseph Spears, et al, Non Final Action Mailed, Jan. 8, 2016.
Systems and Methods to Process Referrals Between Offer Campaigns, U.S. Appl. No. 13/915,076, Mark Carlson, et al, filed Jun. 11, 2013, Non Final Action Mailed, Apr. 27, 2016.
Systems and Methods to Program Interaction with a User Through Transactions in Multiple Accounts, U.S. Appl. No. 14/021,673, filed Sep. 9, 2013, Douglas Rappoport, Sep. 8, 2016.
Systems and Methods to Facilitate an Offer Campaign Based on the Transactions with Different Merchants, U.S. Appl. No. 14/072,674, filed Nov. 5, 2013, Douglas Rappoport, et al, Non Final Action Mailed, Jun. 7, 2016.
Systems and Methods to Facilitate an Offer Campaign Based on the Result of a Competition, U.S. Appl. No. 14/073,595, filed Nov. 6, 2013, Douglas Rappoport, et al, Non Final Action Mailed, Aug. 8, 2016.
Systems and Methods to Facilitate Programming of an Offer Campaign, U.S. Appl. No. 14/134,852, filed Dec. 19, 2013, Joseph Spears, et al, Jan. 26, 2014.
Systems and Methods to Provide a User Interface for Redemption of Loyalty Rewards, U.S. Appl. No. 14/523,185, filed Oct. 24, 2014, Diane Salmon, et al, Non Final Action Mailed, May 3, 2016.
Systems and Methods to Facilitate the Redemption of Offer Benefits in a Form of Third Party Statement Credits, U.S. Appl. No. 14/538,121, filed Nov. 11, 2014, Daniel Fineman, et al, Jan. 29, 2015.
Real-Time Statement Credits and Notifications, U.S. Appl. No. 12/566,350, filed Sep. 24, 2009, Mark Carlson, et al, Non Final Action Mailed, Aug. 1, 2016.
Systems and Methods to Provide Messages in Real-time with Transaction Processing, U.S. Appl. No. 13/776,319, filed Feb. 25, 2013, Jeanette Yoder, et al, Jun. 13, 2014.
Systems and Methods to Provide Messages in Real-time with Transaction Processing, U.S. Appl. No. 15/072,132, Jeanette Yoder, et al, Apr. 6, 2016.
Systems and Methods to Rank and Select Triggers for Real-time Offers, U.S. Appl. No. 13/198,493, filed Aug. 4, 2011, Jeanette Yoder, et al, Sep. 8, 2016.
Systems and Methods to Provide Real-time Offers Via a Cooperative Database, U.S. Appl. No. 13/225,185, filed Sep. 2, 2011, Jeanette Yoder, et al, Non Final Action Mailed, Sep. 28, 2015.
Systems and Methods to Provide Real-time Offers Via a Cooperative Database, U.S. Appl. No. 14/265,138, filed Apr. 29, 2014, Jeanette Yoder, et al, May 17, 2014.
Systems and Methods to Present Triggers for Real-time Offers, U.S. Appl. No. 13/205,205, filed Aug. 8, 2011, Jeanette Yoder, et al, Final Rejection Mailed, Jun. 22, 2015.
Systems and Methods to Reward User Interactions, U.S. Appl. No. 13/288,713, filed Nov. 3, 2011, Mark Carlson, et al, Aug. 8, 2016.
Systems and Methods to Program Operations for Interaction with Users, U.S. Appl. No. 13/237,457, filed Sep. 20, 2011, Mark Carlson, et al, Nov. 8, 2016.
Systems and Methods to Program Operations for Interaction with Users, U.S. Appl. No. 13/314,115, filed Dec. 7, 2011, Mark Carlson, et al, Non Final Action Mailed, Jul. 30, 2014.
Systems and Methods to Modify Interaction Rules During Run Time, U.S. Appl. No. 13/237,467, filed Sep. 20, 2011, Mark Carlson, et al, Aug. 8, 2016.
Systems and Methods to Combine Transaction Terminal Location Data and Social Networking Check-in, U.S. Appl. No. 13/420,541, filed Mar. 14, 2012, Leigh Amaro, et al, Aug. 17, 2015.
Systems and Methods to Combine Transaction Terminal Location Data and Social Networking Check-in, U.S. Appl. No. 13/915,245, filed Jun. 11, 2013, Leigh Amaro, et al, Final Rejection Mailed, Dec. 2, 2014.
Systems and Methods to Provide Offer Communications to Users Via Social Networking Sites, U.S. Appl. No. 13/431,828, filed Mar. 27, 2012, Ayman Hammad, et al, Nov. 8, 2016.
Systems and Methods to Present and Process Offers, U.S. Appl. No. 13/744,844, filed Jan. 18, 2013, Mark Carlson, et al, Feb. 8, 2016.
Systems and Methods to Redeem Offers Based on a Predetermined Geographic Region, U.S. Appl. No. 13/744,839, filed Jan. 18, 2013, Mark Carlson, et al, May 8, 2016.
Systems and Methods to Process Offers Via Mobile Devices, U.S. Appl. No. 13/786,716, filed Mar. 6, 2013, Mark Carlson, et al, Non Final Action Mailed, May 4, 2016.
Systems and Methods to Provide a User Interface to Control an Offer Campaign, U.S. Appl. No. 13/630,295, filed Sep. 28, 2012, Mark Carlson, et al, May 8, 2016.
Systems and Methods to Process Referrals Between Offer Campaigns, U.S. Appl. No. 13/915,076, filed Jun. 11, 2013, Mark Carlson, et al, Non Final Action Mailed, Apr. 27, 2016.
Systems and Methods to Facilitate an Offer Campaign Based on Transactions with Different Merchants, U.S. Appl. No. 14/072,674, filed Nov. 5, 2013, Douglas Rappoport, et al, Non Final Action Mailed, Jun. 7, 2016.
Systems and Methods to Facilitate an Offer Campaign Based on the Result of a Competition, U.S. Appl. No. 14/073,595, filed Nov. 6, 2013, Douglas Rappoport, et al, Dec. 13, 2013.
Real-time Statement Credits and Notifications, U.S. Appl. No. 12/566,350, filed Sep. 24, 2009, Mark Carlson, et al, Feb. 8, 2016.
Systems and Methods to Provide Messages in Real-time with Transaction Processing, U.S. Appl. No. 15/072,132, filed Mar. 16, 2016, Jeanette Yoder, et al, Apr. 6, 2016.
Systems and Methods to Program Operations for Interaction with Users, U.S. Appl. No. 13/237,457, filed Sep. 20, 2011, Mark Carlson, et al, Jul. 13, 2016.
Systems and Methods to Provide Offer Communications to Users Via Social Networking Sites, U.S. Appl. No. 13/431,828, filed Mar. 27, 2012, Ayman Hammad, et al, Jul. 26, 2016.

Related Publications (1)

	Number	Date	Country
	20110231235 A1	Sep 2011	US

Provisional Applications (1)

	Number	Date	Country
	61316336	Mar 2010	US

Merchant configured advertised incentives funded through statement credits

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Abstract