Patent Grant
9569789
The present disclosure relates generally to systems and methods for providing marketing partners an automated platform for managing promotions, and more particularly to systems and methods for establishing and maintaining loyalty incentive programs and other promotions that permit consumers to receive discounts and notices of discounts without requiring a coupon to be redeemed.
Loyalty incentive or reward programs are used as a form of highly customizable and targeted marketing. A loyalty program provider will attract customers who signup for a loyalty program. Shopping benefits such as discounts are offered to the customers by the provider. The provider then markets to merchants that the provider can bring customers to the merchant. For example, a loyalty program provider may approach a merchant, such as the clothing retailer GAP® Inc., with an offer to bring customers to the GAPS in exchange for a fee. The provider would then send a solicitation (via email or regular mail) to its customers offering, for example, a 10% discount coupon that may be redeemed at the GAP® on a particular day. The success of the solicitation can be assessed based on the number of coupons redeemed.
In such a loyalty solicitation, the merchant would pay the loyalty program provider a percentage of the sales (e.g., 10%) that result from the solicitation. The merchant benefits from the increased sales. The loyalty program provider benefits from the commission that it receives, and the customers benefit from the received discount.
There are several areas that could be improved in such traditional loyalty programs. For example, such traditional programs suffer from leakage. Leakage occurs when the merchant does not fully report sales resulting from the solicitation. Leakage results in loss revenues for the loyalty program provider. Further, administration marketing programs such as coupon redemption is costly. For example, setting up and maintaining offers, eligibility criteria, redemption criteria, reporting criteria and other functions of a promotion system traditionally requires business analysts of the reward program platform provider to manually configure the platform. What is needed is a marketing and promotions platform that enables intelligent, automated (e.g., via application programming interfaces) interfaces with a reward platform.
In one embodiment, a computing platform includes application programming interfaces that enable third parties to create, configure, manage, modify, update, delete, report on, and enhance reward offers and marketing programs. For example, a program provider may wish to create a custom application (“partner application”) that serves as a front-end or interface with the computing platform. The partner application accesses the computing platform via various application programming interfaces (APIs). Although in various embodiments, steps may occur in any order, in an embodiment a marketing program is set up and merchants are associated with the marketing program. Offers are created and associated with the program and/or the merchant and customers are offered and signed up for the offers.
In one embodiment an automated marketing system, comprises: a network interface communicating with a memory, the memory communicating with a processor for automated marketing and storing a computer program and a plurality of application programming interfaces (APIs); and the processor, when executing a computer program, performs operations. The operations include receiving, by the processor and via an offer setup API, a first offer setup request, wherein the offer setup API is from the plurality of APIs; parsing, by the processor, the offer set up request into a plurality of first offer parameters; validating, by the processor, at least one of the offer setup request and the first offer parameters; in response to the validating, notifying, by the processor, a first approver of the offer setup request; receiving, by the processor and from the first approver, an approval of the offer set up request; saving, by the processor and to the memory, a first offer comprising the first offer parameters, wherein the first offer is associated with a first marketing program; and determining, by the processor, a first population comprising a plurality of transaction accounts that comply with first offer criteria, wherein the first offer parameters comprise the first offer criteria.
In an embodiment, the first offer criteria comprise at least one of a customer identifier, a customer demographic, a customer location, spend frequency, a spend threshold, a spend history, an award cap, a tiered reward requirement, a product identifier, a product category, a stock-keeping unit (SKU), a universal product code (UPC), a QR code, a merchant, a merchant type, an industry, a merchant location.
In one embodiment, operations performed by the system include receiving via an enrollment API from the plurality of APIs, a first enrollment setup-request; validating the first enrollment setup-request, wherein the validating comprises determining that the first enrollment setup request is associated with at least one of the first offer and a second offer; receiving an approval of the first enrollment setup-request from at least one of the first approver and the second approver; parsing the first enrollment setup request into first enrollment parameters and saving the first offer enrollment parameters to the memory and receiving a first offer acceptance from a first user associated with a first transaction account from the first population.
In another embodiment, a method for operating a loyalty incentive program includes the following steps: a list of participating merchants is received; a list of participating account holders is received; a record of charge corresponding to a purchase by an account holder customer is received from a merchant, and upon receipt, an account of the account holder customer is debited by the amount of the charge, a merchant identification contained in the record of charge is compared with the list of participating merchants, and an account holder identification contained in the record of charge is compared with the list of participating account holders. If the account holder is a participating account holder and the merchant is a participating merchant, then it is determined whether the record of charge qualifies for a rebate credit. If the record of charge qualifies for a rebate credit, then the rebate credit is provided to an account of the account holder customer.
In another embodiment, a method includes the following steps: participation of a merchant in a loyalty incentive program is solicited; an over from a participating merchant is received; enrollment of an account holder customer to the loyalty incentive program is solicited; the offer is provided to an enrolled account holder customer; information is received which relates to a purchase by the enrolled account holder customer in accordance with the offer from the participating merchant; an amount of a discount in accordance with the offer is calculated; and the amount of the discount is provided to a transaction account provider so that an account of the enrolled account holder customer is credited in the amount of the discount.
In an embodiment, a method for managing a rewards program includes monitoring spend data associated with a transaction account. The spend data may be analyzed and compared to a set of criteria (spend levels at particular merchants, spend level on classes of products, spend level in a particular region). The transaction account may then be assigned to one or more transaction account populations based on spend data and criteria. The spend data associated with the transaction account is also analyzed to determine whether a beneficiary of the transaction account qualifies for a reward in accordance with a rewards program. Where the spend data complies with the rules governing the rewards program, a reward (e.g. a credit of monetary value to the transaction account, a merchant prepaid account, a discount, a credit of loyalty points) is provided to a beneficiary of the transaction account. The spend data activities associated with the transaction accounts of the population are also monitored. Where the activities comply with criteria associated with the transaction account population, a rewards offer (an offer of a credit of monetary value to the transaction account, a merchant prepaid account, a discount, a credit of loyalty points) is sent to owner of transaction accounts associated with the population.
In an embodiment, the criteria may be established by a merchant or a prepaid account issuer. Enrollment in a transaction account population may be automatic or may include registration by the owner of the transaction account. Further features of various embodiments, as well as the structure and operation of various embodiments are described in detail below with reference to the accompanying drawings.
A more complete understanding of the present disclosure may be derived by referring to the detailed description and claims when considered in connection with the Figures, wherein like reference numbers refer to similar elements throughout the Figures, and:
The present disclosure is directed to a system and method for providing loyalty incentives to an account holder customer and operating a loyalty incentive program. The present system is now described in more detail herein in terms of an exemplary embodiment. This is for convenience only and is not intended to limit the application of the present disclosure. While specific configurations and arrangements are discussed, it should be understood that this is done for illustrative purposes only. In fact, after reading the following description, it will be apparent to one skilled in the relevant art(s) how to implement the following exemplary embodiments. A person skilled in the pertinent art will recognize that other configurations and arrangements can be used without departing from the spirit and scope of the present disclosure. It will be apparent to a person skilled in the pertinent art that this disclosure can also be employed in a variety of other applications.
The terms “user,” “end user,” “consumer,” “customer,” “participant,” and/or the plural form of these terms are used interchangeably throughout herein to refer to those persons or entities capable of accessing, using, being affected by and/or benefiting from the tool that the present disclosure provides for the rewards program described herein. This includes both individual consumers and corporate customers such as, for example, small businesses.
Furthermore, the terms “service provider,” “service establishment,” “business” or “merchant” may be used interchangeably with each other and shall mean any person, entity, distributor system, software and/or hardware that is a provider, broker and/or any other entity in the distribution chain of goods or services. For example, a service provider may be a retail store, a hotel company, an airline company, a travel agency, an on-line merchant or the like.
A “transaction account” as used herein refers to an account associated with an open account or a closed account system (as described below). The transaction account may exist in a physical or non-physical embodiment. For example, a transaction account may be distributed in non-physical embodiments such as an account number, frequent-flyer account, telephone calling account or the like. Furthermore, a physical embodiment of a transaction account may be distributed as a financial instrument.
A financial transaction instrument may be traditional plastic transaction cards, titanium-containing, or other metal-containing, transaction cards, clear and/or translucent transaction cards, foldable or otherwise unconventionally-sized transaction cards, radio-frequency enabled transaction cards, or other types of transaction cards, such as credit, charge, debit, pre-paid or stored-value cards, or any other like financial transaction instrument. A financial transaction instrument may also have electronic and communications functionality. Such functionality may be enabled, for example, by: a network of electronic circuitry that is printed or otherwise incorporated onto or within the transaction instrument (and typically referred to as a “smart card”); a fob having a transponder and an RFID reader; and/or near field communication (NFC) technologies. For more information regarding NFC, refer to the following specifications all of which are incorporated by reference herein: ISO/IEC 18092/ECMA-340, Near Field Communication Interface and Protocol-1 (NFCIP-1); ISO/IEC 21481/ECMA-352, Near Field Communication Interface and Protocol-2 (NFCIP-2); and EMV 4.2 available at http://www.emvco.com/default.aspx.
“Open cards” are financial transaction cards that are generally accepted at different merchants. Examples of open cards include the American Express®, Visa®, MasterCard® and Discover® cards, which may be used at many different retailers and other businesses. In contrast, “closed cards” are financial transaction cards that may be restricted to use in a particular store, a particular chain of stores or a collection of affiliated stores. One example of a closed card is a pre-paid gift card that may only be purchased at, and only be accepted at, a clothing retailer, such as the clothing retailer Gap®, Inc.
Stored value cards are forms of transaction instruments associated with transaction accounts, wherein the stored value cards provide cash equivalent value that may be used within an existing payment/transaction infrastructure. Stored value cards are frequently referred to as gift, pre-paid or cash cards, in that money is deposited in the account associated with the card before use of the card is allowed. For example, if a customer deposits ten dollars of value into the account associated with the stored value card, the card may only be used for payments together totaling no more than ten dollars.
With regard to use of a transaction account, users may communicate with service providers in person (e.g., at the box office), telephonically, or electronically (e.g., from a user computer via the Internet). During the interaction, the service provider may offer goods and/or services to the user. The service provider may also offer the user the option of paying for the goods and/or services using any number of available transaction accounts. Furthermore, the transaction accounts may be used by the service provider as a form of identification of the user. The service provider may have a computing unit implemented in the form of a computer-server, although other implementations are possible.
In general, transaction accounts may be used for transactions between the user and service provider through any suitable communication means, such as, for example, a telephone network, intranet, the global, public Internet, a point of interaction device (e.g., a point of sale (POS) device, personal digital assistant (PDA), mobile telephone, kiosk, etc.), online communications, off-line communications, wireless communications, and/or the like.
An “account,” “account number” or “account code,” as used herein, may include any device, code, number, letter, symbol, digital certificate, smart chip, digital signal, analog signal, biometric or other identifier/indicia suitably configured to allow a consumer to access, interact with or communicate with a financial transaction system. The account number may optionally be located on or associated with any financial transaction instrument (e.g., rewards, charge, credit, debit, prepaid, telephone, embossed, smart, magnetic stripe, bar code, transponder or radio frequency card).
The account number may be distributed and stored in any form of plastic, electronic, magnetic, radio frequency (RE), NFC, wireless, audio and/or optical device capable of transmitting or downloading data from itself to a second device. A customer account number may be, for example, a sixteen-digit credit card number. Each credit card issuer has its own numbering system, such as the fifteen-digit numbering system used by American Express Company of New York, N.Y.
A merchant account number may be, for example, any number or alpha-numeric characters that identifies a particular merchant for purposes of card acceptance, account reconciliation, reporting and the like.
It should be noted that the transfer of information in accordance with various embodiments may be done in a format recognizable by a merchant system or account issuer. In that regard, by way of example, the information may be transmitted from an READ device to an RFID reader, or from the RFID reader to the merchant system in magnetic stripe or multi-track magnetic stripe format.
Because of the proliferation of devices using magnetic stripe format, the standards for coding information in magnetic stripe format were standardized by the International Organization for Standardization in ISO/IEC 7811-n (characteristics for identification cards) which are incorporated herein by reference. The ISO/IEC 7811 standards specify the conditions for conformance, physical characteristics for the card (warpage and surface distortions) and the magnetic stripe area (location, height and surface profile, roughness, adhesion, wear and resistance to chemicals), the signal amplitude performance characteristics of the magnetic stripe, the encoding specification including technique (MFM), angle of recording, bit density, flux transition spacing variation and signal amplitude, the data structure including track format, use of error correction techniques, user data capacity for ID-1, ID-2 and ID-3 size cards, and decoding techniques, and the location of encoded tracks.
Typically, magnetic stripe information is formatted in three tracks. Certain industry information must be maintained on certain portions of the tracks, while other portions of the tracks may have open data fields. The contents of each track and the formatting of the information provided to each track is controlled by the ISO/IEC 7811 standard. For example, the information must typically be encoded in binary. Track 1 is usually encoded with user information (i.e., name) in alphanumeric format. Track 2 is typically comprised of discretionary and nondiscretionary data fields. In one example, the nondiscretionary field may comprise 19 characters and the discretionary field may comprise 13 characters. Track 3 is typically reserved for financial transactions and includes enciphered versions of the user's personal identification number, country code, current units amount authorized per cycle, subsidiary accounts, and restrictions.
As such, where information is provided in accordance with an embodiment, it may be provided in magnetic stripe track format. For example, the counter values, authentication tags and encrypted identifiers may be forwarded encoded in all or a portion of a data stream representing data encoded in, for example, track 2 or track 3 format.
Persons skilled in the relevant arts will understand the breadth of the terms used herein and that the exemplary descriptions provided are not intended to be limiting of the generally understood meanings attributed to the foregoing terms.
It is noted that references in the specification to “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it would be within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
In an embodiment and with references to
TAP may collaborate with a loyalty program provider to produce the reward or incentive program. While, as used herein, “loyalty program provider” (LPP) refers to an external, third-party provider of marketing packages that may be provided to CMs in accordance with various embodiments, TAP may internally administer loyalty programs, such as restaurant or travel marketing program. Therefore, to distinguish from programs provided by an LPP, TAPs internal loyalty programs will be referred to herein as a “TAP marketing program” or simply a “TAP program.” In the figures, the service mark. “TailorMade” is used to refer to an example loyalty program offered by an LPP. Accordingly, although embodiments will be described herein in the environment of such collaboration between a TAP and an LPP, one of skill in the pertinent art(s) will recognize that a registered card program can be implemented with or without a loyalty program provider or other types of providers without departing from the spirit and scope of the present disclosure.
As shown in
As shown in
The CM may be provided the option to enroll more than one card and link each second and additional card to a primary enrolled card, which is illustrated in
In the embodiment illustrated in
For marketing programs administered by TAP, registered card engine (“RCE”) 138 may include its own calculation of discount 432 for purchases made by registered CMs with merchants participating in TAP's marketing program. Further, LPP 460 may be responsible for calculation of discount 462 for purchases made at merchants participating in marketing programs administered by LPP 460. A merchant may be a participating merchant for a plurality of externally administered and/or internally administered marketing programs. Therefore, these offer and merchant databases may include a field identifying each offer and merchant to one or more marketing programs, as further described below with reference to
Another input to RCE 138 are merchant ROCs 436, which may be compiled as a daily transaction file and stored in transaction database 136 (shown in
A problem to be overcome in implementing a loyalty incentive program as described herein is how to deal with returns. For example, assume an account holder makes a purchase for $100 and receives a 10% discount (also called a rebate or incentive) on his or her account. If the account holder then returns the purchased goods to the merchant, it is desirable to be able to ascertain whether the purchase involved an incentive so that a return credit can be made in the appropriate amount. This problem is solved by providing a mechanism for dealing with returns. In the embodiment of
RCE 138 has the capability to convert the discount amount to an equivalent of membership reward points which may be redeemable in accordance with membership rewards program. Typically, a membership rewards program offers goods or travel packages in exchange for membership reward points. Moreover, the discount amount may be a combination of a monetary credit and an equivalent of reward points. To implement such conversions, as well as to support service fee calculation, etc. RCE 138 may include a configuration table 434. Configuration table 434 may include fields for each marketing program and corresponding information for converting the calculated discount (i.e., the rebate credit) between a monetary credit and/or an equivalence in membership rewards points (shown as “CM (%, $, Pts)”). Further, since a discount offer may be represented in units of monetary amount off or percent off a purchase price, or in terms of membership rewards points, then for internally calculated discounts 432, RCE uses configuration table 434 to match program, merchant, and conversion terms (shown as “SE (%, $)”) to convert the offer terms to the desired units for discount calculation, Configuration table 434 may also have a field for TAP's service fees for each program and participating merchants, and service fees may be in units such percent of purchase or monetary amount (shown as “TAP (%, $)”). Further, since a merchant may be submitting the same offer for more than one marketing program, configuration table includes a “priority” field that is used to identify repeated offers and ensure that the CM receives only a single rebate credit on a purchase that is eligible to receive a discount pursuant to multiple marketing programs.
The calculated discount (or discount reversal, if relating to a return) is provided to TAP settlement systems 470 for transactions on Prop registered cards, or to GNS settlement systems 480 for transactions on GNS registered cards. An AR system of TAP settlement systems 470 processes the discount amount and provides the rebate credit (as a monetary credit or an equivalence in reward points, or both) on CM's credit statement. If the rebate credit includes membership reward points, then information relating the rebate credit is also provided to membership rewards 472 for appropriate record keeping for that CM. AP systems of TAP settlement systems 470 processes the merchant debit in accordance with CM's rebate credit, as well as any service fee charged by TAP for providing the services described herein. Further detail regarding processing of matched transactions via TAP settlement systems is described below with reference to
RCE 138 may further have the capability to provide TAP with reporting 490, which may include a marketing analysis or monitoring of the success of various marketing programs and information relating to account holder participation therein. Reporting 490 thereby permits TAP to target CMs and deliver merchant offers that are desirable to its registered CMs and/or merchants.
Offer DB 452 may comprise a plurality of offers. In an embodiment, the offers may be predetermined offers and/or offers based on merchant criteria. The offers may be configured to be delivered electronically through reporting 490. The electronic delivery may include delivery via email, text messaging, instant messaging and/or social networking distribution (e.g., via Facebook, Twitter, Myspace, Linked-in). The electronic delivery may be automatic or require a manual input. The offers may be accessible by RCE 138. These offers may be based upon specific parameters which define at least one of a reward, a merchant and/or class of merchants, characteristics of a targeted CM, a predetermined qualification threshold, and the like. RCE 138 may analyze the parameters to identify intended recipients of the offers. RCE 138 may also analyze the parameters to determine characteristics for a CM population. This capability allows the merchant to quickly and inexpensively target the CM with customized marketing and/or offers. This capability also allows the merchant to provide an offer to targeted CMs before a target list is pulled.
In an embodiment, reporting 490 may be configured to deliver offers to CMs with particular behaviors and/or patterns (e.g., spending behaviors, reward usage behaviors, etc). RCE 138 may be configured to define a particular CM population based on merchant targeted marketing efforts, CM spending patterns, CM demographic data and/or the like. For example, RCE 138 may identify a CM population that spends a predetermined amount of money on electronics in a predetermined period of time. Further, RCE 138 may identify a merchant who offers electronics for purchase, but does not capture significant spending from the identified CM population. In other words, the CMs who spend a predetermined amount on electronics are not spending significant amounts on electronics with the identified merchant. RCE 138 may analyze the CM spending to compare the total amount of spending on a particular class of items (e.g., electronics). RCE 138 may also analyze such CM spending based on merchants that receive the CM spend, to determine the proportions of spending at a particular merchant, class of merchants, and/or the like. Such information may be compared to a predetermined threshold spending amount or proportions of spending at particular merchants and/or classes of merchants. The comparison allows, for example, a merchant to target CMs that do not typically spend significant amounts with a particular merchant or class of merchant, but the CMs buy the types of products and/or services offered by the merchant or class of merchants.
CM populations may be initially created based on, for example, historical data. The historical data accessible to a financial processor, such as spend level data, is leveraged using various data clustering and/or data appending techniques. The CM populations may also be created based on, for example, current spending patterns. The current spend patterns available to a financial processor (e.g., current authorized transactions, posted transactions, and the like) may be leveraged using various data clustering and/or data appending techniques. Associations may be established among entities (e.g. CMs), among merchants, and between entities and merchants. In an embodiment, RCE 138 may receive passively collected spend level data for a transaction of a plurality of CMs, aggregate the collected spend level data for a plurality of CMs, and cluster the CMs into subsets of the plurality of CMs, based on the aggregated spend level data.
The collection of the spend level data may be passive. For instance, passively collecting spend level data of a CM includes acquiring the spend level data in response to a transaction by a CM with a merchant. In an embodiment, the spend level data may be integral to information processed in a transaction for goods and/or services with a merchant. For instance, a survey and/or survey responses are not needed to capture spend level data, but such data may be used to supplement the data discussed herein. Collecting the spend level data may include acquiring the spend level data from a merchant. In an embodiment, passively collecting the spend level data of a CM includes collecting the spend level data from a transaction database. In yet another embodiment, passively collecting the spend level data includes reconciling the spend level data, transferring the spend level data to a host, organizing spend level data into a format, saving the spend level data to a memory, gathering the spend level data from the memory, and/or saving the spend level data to a database. For instance, if a CM performs a transaction (such as by using a transaction account), spend level data (such as transaction data and/or consumer account data) related to the transaction may be captured and stored in a memory, database, and/or multiple databases. Spend level data (such as transaction data and/or consumer account data) may be stored locally with the merchant, remotely by the merchant and/or transmitted to a remote host (e.g., financial processor) for storing and processing.
In one embodiment, aggregating the collected spend level data includes combining a selectable range of collected spend level data. The selectable range may be a period of time (e.g., time range) and/or from a particular geographic region. The period may be any suitable period and/or periods such as a minute, an hour, a period of hours, one day, one week, one month, a period of days, a period of months, one year, or more than one year. The periods may be consecutive or non-consecutive. In an embodiment, the selectable range may be a value, such as values of spend exceeding a pre-selected threshold. The selectable range may also include frequency, such as spend level data occurring at a particular frequency.
In an embodiment, the spend level data may be segmented by a gender of the entity (e.g., male or female), such that only data collected from merchants in transactions with men are processed by RCE 138. This data may be aggregated, clustered, assigned a weighed percentile and analyzed in accordance with the previous descriptions. Using this exemplary embodiment of the system, preferences, attributes, and inferences of a selected demographic may be obtained. In one embodiment, spend level data segmented geographically (e.g., zip code) or by other regions can reveal which regions are most compelling to a merchant and/or marketer.
Any demographic included within the characteristic data may be selected for pre-segmenting the spend level data. In an embodiment, the spend level data may be segmented by an attribute (e.g., homeowner designation), and data collected from merchants in transactions with entities that are homeowners may be processed by RCE 138. This data may be aggregated, clustered, assigned a weighed percentile and analyzed in accordance with the previous descriptions. From this procedure, a holistic picture of homeowners segmented into different clusters may be created. More than one demographic or attribute may be selected and the spend level data may be pre-segmented any suitable number of times in any suitable order. Additionally, in one embodiment, a particular demographic may be selected to be removed from the larger set of all available spend level data. For instance, the spend level data of very high income entities may be selected for removal and data collected from merchants in transactions with very high income entities may be excluded from processing by RCE 138. The remaining data may be aggregated, clustered, assigned a weighed percentile and analyzed in accordance with the previous descriptions. Using this embodiment, outliers may be removed from the results, Additional details regarding combining CMs into populations are disclosed in, for example, U.S. application Ser. No. 12/690,669, entitled “System And Method For Clustering a Population Using Spend level Data” and filed on Jan. 20, 2010, which is hereby incorporated by reference in its entirety.
The CM populations may be established based on historical data or on current spending patterns, as discussed above, and in one embodiment are modified based on current spending habits. For example, spend level data may be actively captured and used to modify CM populations. As CM spending habits change, the groups are modified to provide greater accuracy for delivering rewards, merchant offers and the like. For example, a CM may be placed in a population of CMs whose spend level data suggests that they attend public entertainment events (e.g. movies, concerts, and the like). As time passes, the system may analyze a shift in the spend level data which suggests that the CM (possibly due to a having a new baby) attends less public entertainment events and spends more for home entertainment items, such as for example, home electronics equipment. In response to the shift in spend level data, RCE 138 may associate the CM with a new CM population which receives rewards offers for electronics. Further, RCE 138 may also remove a CM from a particular CM population based on current spend level data, wherein the CM was originally placed in a CM population based on historical spend level data, but no longer exhibits spending behavior consistent with the historical spend level data.
In one embodiment, in response to the determination that the CM population is spending on electronics, but not with a particular identified merchant, reporting 490 may send the CM population a reward offer from the identified merchant. The rewards offer may be designed to encourage the CM population to buy electronics from the identified merchant, with whom the CM population had not previously conducted significant business.
The terms of a rewards offer may define a trigger event, such as a threshold spending amount at a particular merchant or class of merchants, or for a class of items. The reward offer may be provided electronically to the CM population based on a trigger event in real time). A trigger event may be any action identified by the merchant or the account issuer. The trigger event may be based on spend data, geographic region spend, CM population size, time of year, or any other event. The event may be identified by the merchant, CM and/or account issuer. For example, the trigger event may be based on spend data. In response to a CM population reaching a predetermined spend level on a class of products (e.g. electronics), the rewards offer may be sent to the CM population via email. Similarly, the trigger event may be based on a CM population size. In response to the CM population reaching a predetermined level, a rewards offer is sent to the CM population. In another example, the merchant and a product supplier or manufacturer may create a joint offer, which provides a reward offer if a CM buys a particular item (e.g. a particular model laptop computer) or class of items (e.g. any Sony® television).
In an embodiment, a merchant may wish to market rewards offers to CM populations based on CMs spending at other merchants. For example, a merchant that sells home improvement items (e.g. Home Depot) may wish to market its products and services to a CM population that spends a predetermined amount on electronics. The merchant may formulate a set of criteria to develop a CM population based on spend data for electronics purchases (e.g. televisions) and/or spend data at particular electronics merchants (e.g. Best Buy). Thereafter, rewards offers from the merchant are provided to the CM population in response to a trigger event.
In an embodiment, the identified merchant offer is provided in conjunction with an existing rewards program. For example, the CM may be eligible for a reward based on the CM's pre-existing participation in a rewards program. The reward offer is provided in addition to the existing reward. For example, a CM is provided with a credit based on a particular transaction at a particular merchant. The transaction may also result in the CM becoming a member of a particular CM population that is provided with a rewards offer (e.g. an additional discount with the identified merchant based on the loyal spending behavior). As such, the CM receives the pre-existing reward and the reward offer based on the CM becoming a member of a CM population.
In an embodiment, a CM is automatically enrolled in a program to receive e-mail rewards based on criteria determined by a merchant or account issuer. In an embodiment, a CM may be invited to join a CM population that is eligible to receive rewards offers. The CM may receive a notification which indicates that the CM is eligible to receive rewards offers. The notification may provide for an opt-out period during which the CM can request that the CM is not sent the rewards offers based on the CM's inclusion in a CM population. The notification may also provide that the CM register to receive the rewards offers by taking some affirmative action, such as for example, registering the CM's account via a webpage and/or contacting the account issuer and requesting to be included in the CM population associated with the rewards offers.
RCE 138 may be configured to administer rewards associated with a prepaid transaction account. Such configuration may occur directly or via API's that are included in RCP 130. The prepaid transaction account may comprise embedded rewards, including for example, credits to the prepaid transaction account, merchant specific rewards (e.g. merchant gift cards), discounts, and the like. The rewards may be customized by a merchant. The rewards may be offered in conjunction the pre-paid transaction cards (e.g. American Express Gift Cards, Home Depot Gift Card). Offers may be customized by an individual merchant or a group of merchants. This ability to customize offers allows local and regional merchants to offer rewards to customers that were previously unavailable because of the cost and complexity of administering a rewards program. Further, providing rewards with a prepaid transaction account allows those who are not credit card users to participate in rewards programs traditionally reserved for credit card account holders.
In an embodiment, a prepaid transaction account has an embedded reward which is configured by an offering merchant. For example, a merchant may configure a reward which provides a credit on purchases of certain products and/or services (e.g. dry cleaning services) at the merchant or within a group of cooperating merchants. The reward may also be based on transactions conducted in a geographic or other region. In one embodiment, the reward may be limited or restricted for use in a similar or other geographic region. The rewards may be offered through a prepaid account, such as a prepaid transaction card, available for purchase through the offering merchant. The prepaid transaction account may be used with any merchant who accepts transaction accounts from the account issuer associated with the prepaid transaction card. Further, the prepaid transaction account may be configured with pre-determined reward criteria from the offering merchant. For example, when seventy percent of the total value of the prepaid card is spent with the offering merchant, a reward is issued. The reward may be issued in the form of a credit to the prepaid transaction account, or may be provided in some other fashion (e.g. another gift card from the offering merchant).
In an embodiment, participation in the rewards program associated with the prepaid transaction account may be automatic or may require registration. Registration may be provided by accessing a webpage and providing identifying information. Registration may also be achieved by contacting an account issuer and requesting that a particular prepaid transaction account be associated with a rewards program.
In an embodiment, any prepaid transaction account associated with an account issuer may participate in any rewards program offered by the account issuer. The transaction account may be registered with the account issuer for a particular rewards program selected by a prepaid transaction account owner. Where the activities associated with the transaction account conform to the rules governing the rewards program, a reward is provided to the prepaid transaction account owner.
Cancellations 440 of registered accounts by enrolled CMs are communicated to loyalty program provider 460 as well as to enrollment 120 so as to maintain enrollee database 134 with up-to-date enrolled CM information. Cancellations 440 may arise, for example, from a CM reporting a lost or stolen card or a CM requesting TAP to deregister one or more of its registered cards from the registered card program. In an embodiment, enrollee database 134 may be provided with timely and consistent updates to reflect lost and stolen cards. Cancellations 440 may also include deregistration of a CM from one or more particular marketing programs administered by TAP or LPP 460.
Further description will now be provided with respect to solicitation 110 and enrollment 120. As noted above with reference to
Solicitation 110 may further include a pre-solicitation process prior to sending a solicitation email to a targeted CM. The pre-solicitation process may involve determining which CMs should be targeted and which offer clusters and particular marketing programs the CM may be eligible to participate in pursuant to the registered card program. Accordingly, TAP may collaborate with LPP 460 to identify appropriate CMs for email solicitation based on TAP's data on a CM's spending preferences and the LPP's clusters of merchant offers. These identified, targeted CMs may then reviewed so as to exclude solicitation of any targeted CNN having opted out of receiving direct marketing materials from TAP or LPP 460. TAP then provides LPP 460 with a marketing list of targeted CMs and associated identifying information (such as salutation, name, gender, and zip code). The marketing list may further be provided to LPP 460 with a given effective period during which solicitation mails may be sent, since the list should be updated periodically to exclude CMs from the list that have since opted out of receiving marketing materials. Upon receipt of the marketing list from TAP, loyalty program provider sends out email invitations to the targeted CMs.
Enrollment 120 may provide an option to the CM to participate in the registered card program as a preferred enrollee. For example, during enrollment an account holder may choose to be eligible for “premium” offers in exchange for paying an enrollment fee. Alternatively, the CM may wish to forego payment of any enrollment fee and be eligible for “everyday” offers. Preferred (i.e., premium) customers may also be eligible for everyday offers. TAP's registered card program may therefore offer tiers of offer packages corresponding to the “premium” and “everyday” tiers of enrolled account holders. Accordingly, RCE 138, during transaction matching, may consider whether an enrolled CM is registered as a premium account holder or an everyday account holder so as to identify CM purchases that qualify for a premium offer and/or an everyday offer.
An embodiment, the TAP collaborates with loyalty program provider 460 will now be described in greater detail with reference to
Merchant offer database 452 may include an offer ID, a corresponding merchant ID, a start and end date for the particular offer, a description, and whether the offer is a premium offer, as described above. Since TAP and LPP may each administer marketing programs, and since there may be multiple loyalty program providers, merchant offer database 452 may also include a field identifying each TAP or LPP marketing program to which the offer belongs,
In this embodiment, output file 444 includes CM's RCnumber as a substitute for the CM's actual transaction account number, Output file 444 is provided to LPP for discount calculation, and the level of security associated with LPP's network may prohibit allowing LPP using the actual account number as a means to identify the transaction for discount calculation. However, it should be understood that for internally calculated discounts 432 (described in
Once TAP identifies credit ROCs from participating merchants, TAP may compare them to transaction debits stored in transaction database 136 (see
At step 670, CM information in enrollee database 134 is used to match registered CMs with ROCs extracted in step 660, and each matched transactions is provided with a transaction ID. In step 680, output file 444 is created of transactions matched in step 670. At step 690, output file 444 is provided to loyalty program provider for discount/discount reversal calculation.
As shown in
Methodologies unique to processing of account holder returns by means of a return logic policy in accordance with an embodiment are now described with reference to
If in line 1 there is no exact matched transaction identified with the return, then, in line 2, the first transaction in the past 60 days which is greater than the amount of the return is identified with the return. As shown in line 2, transaction “6” for $5000 is the first matched transaction having an amount greater than the return. Since transaction “6” was not discounted, then no action is taken with regard to debiting CM. If CM claims that the return is part of transaction “5” and “2”, then a debit from the CM's account is made in the amount of the rebate credits (15% and 15%) for those transactions. If there is no transaction matched in lines 1 or 2, then in line 3, if the sum of the return is equal or smaller than the sum of all transactions in the past 60 days, then it is assumed that the return refers to TM transactions up to $1000, and a debit to CM's account is provided in accordance with the discounts on TM transactions 2 and 5.
The present system or any part(s) or function(s) thereof may be implemented using hardware, software or a combination thereof and may be implemented in one or more computer systems or other processing systems. However, the manipulations performed by embodiments were often referred to in terms, such as matching or selecting, which are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary, or desirable in most cases, in any of the operations described herein. Rather, the operations may be machine operations. Useful machines for performing the various embodiments include general purpose digital computers or similar devices.
In fact, in one embodiment, the embodiments are directed toward one or more computer systems capable of carrying out the functionality described herein. An example of a computer system 1300 is shown in
The computer system 1300 includes one or more processors, such as processor 1304. The processor 1304 is connected to a communication infrastructure 1306 (e.g., a communications bus, cross-over bar, or network). Various software embodiments are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the relevant art(s) how to implement various embodiments using other computer systems and/or architectures.
Computer system 1300 can include a display interface 1302 that forwards graphics, text, and other data from the communication infrastructure 1306 (or from a frame buffer not shown) for display on the display unit 1330.
Computer system 1300 also includes a main memory 1308, such as for example random access memory (RAM), and may also include a secondary memory 1310. The secondary memory 1310 may include, for example, a hard disk drive 1312 and/or a removable storage drive 1314, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive 1314 reads from and/or writes to a removable storage unit 1318 in a well known manner. Removable storage unit 1318 represents a floppy disk, magnetic tape, optical disk, etc. which is read by and written to by removable storage drive 1314. As will be appreciated, the removable storage unit 1318 includes a computer usable storage medium having stored therein computer software and/or data.
In alternative embodiments, secondary memory 1310 may include other similar devices for allowing computer programs or other instructions to be loaded into computer system 1300. Such devices may include, for example, a removable storage unit 1318 and an interface 1320. Examples of such may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an erasable programmable read only memory (EPROM), or programmable read only memory (PROM)) and associated socket, and other removable storage units 1318 and interfaces 1320, which allow software and data to be transferred from the removable storage unit 1318 to computer system 1300.
Computer system 1300 may also include a communications interface 1324. Communications interface 1324 allows software and data to be transferred between computer system 1300 and external devices. Examples of communications interface 1324 may include a modem, a network interface (such as an Ethernet card), a communications port, a Personal. Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communications interface 1324 are in the form of signals 1328 which may be electronic, electromagnetic, optical or other signals capable of being received by communications interface 1324. These signals 1328 are provided to communications interface 1324 via a communications path (e.g., channel) 1326. This channel 1326 carries signals 1328 and may be implemented using wire or cable, fiber optics, a telephone line, a cellular link, a radio frequency (RF) link and other communications channels.
In this document, the terms “computer program medium” and “computer usable medium” are used to generally refer to media such as removable storage drive 1314 and a hard disk installed in hard disk drive 1312. These computer program products provide software to computer system 1300.
Computer programs (also referred to as computer control logic) are stored in main memory 1308 and/or secondary memory 1310. Computer programs may also be received via communications interface 1324. Such computer programs, when executed, enable the computer system 1300 to perform the features as discussed herein. In particular, the computer programs, when executed, enable the processor 1304 to perform the features of various embodiments. Accordingly, such computer programs represent controllers of the computer system 1300.
In an embodiment, software may be stored in a computer program product and loaded into computer system 1300 using removable storage drive 1314, hard drive 1312 or communications interface 1324. The control logic (software), when executed by the processor 1304, causes the processor 1304 to perform the functions of various embodiments as described herein.
In another embodiment, hardware components such as application specific integrated circuits (ASICs). Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s).
One skilled in the art will appreciate that system 1300 may employ any number of databases in any number of configurations. Further, any databases discussed herein may be any type of database, such as relational, hierarchical, graphical, object-oriented, and/or other database configurations. Common database products that may be used to implement the databases include DB2 by IBM (White Plains, N.Y.), various database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access or Microsoft SQL Server by Microsoft Corporation (Redmond, Wash.), or any other suitable database product. Moreover, the databases may be organized in any suitable manner, for example, as data tables or lookup tables. Each record may be a single file, a series of files, a linked series of data fields or any other data structure. Association of certain data may be accomplished through any desired data association technique such as those known or practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, using a key field in the tables to speed searches, sequential searches through all the tables and files, sorting records in the file according to a known order to simplify lookup, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in pre-selected databases or data sectors.
More particularly, a “key field” partitions the database according to the high-level class of objects defined by the key field. For example, certain types of data may be designated as a key field in a plurality of related data tables and the data tables may then be linked on the basis of the type of data in the key field. The data corresponding to the key field in each of the linked data tables is preferably the same or of the same type. However, data tables having similar, though not identical, data in the key fields may also be linked by using AGREP, for example. In accordance with one aspect of system 1300, any suitable data storage technique may be utilized to store data without a standard format. Data sets may be stored using any suitable technique, including, for example, storing individual files using an ISO/IEC 7816-4 file structure; implementing a domain whereby a dedicated file is selected that exposes one or more elementary files containing one or more data sets; using data sets stored in individual files using a hierarchical filing system; data sets stored as records in a single file (including compression, SQL accessible, hashed via one or more keys, numeric, alphabetical by first tuple, etc.); Binary Large Object (BLOB); stored as ungrouped data elements encoded using ISO/IEC 7816-6 data elements; stored as ungrouped data elements encoded using ISO/IEC Abstract Syntax Notation (ASN.1) as in ISO/IEC 8824 and 8825; and/or other proprietary techniques that may include fractal compression methods, image compression methods, etc.
In one embodiment, the ability to store a wide variety of information in different formats is facilitated by storing the information as a BLOB. Thus, any binary information can be stored in a storage space associated with a data set. As discussed above, the binary information may be stored on the financial transaction instrument or external to but affiliated with the financial transaction instrument. The BLOB method may more data sets as ungrouped data elements formatted as a block of binary via a fixed memory offset using either fixed storage allocation, circular queue techniques, or best practices with respect to memory management (e.g., paged memory, least recently used, etc.). By using BLOB methods, the ability to store various data sets that have different formats facilitates the storage of data associated with system 1300 by multiple and unrelated owners of the data sets. For example, a first data set which may be stored may be provided by a first party, a second data set which may be stored may be provided by an unrelated second party, and yet a third data set which may be stored, may be provided by an third party unrelated to the first and second party. Each of these three exemplary data sets may contain different information that is stored using different data storage formats and/or techniques. Further, each data set may contain subsets of data that also may be distinct from other subsets.
As stated above, in various embodiments of system 1300, the data can be stored without regard to a common format. However, in one exemplary embodiment, the data set (e.g., BLOB) may be annotated in a standard manner when provided for manipulating the data onto the financial transaction instrument. The annotation may comprise a short header, trailer, or other appropriate indicator related to each data set that is configured to convey information useful in managing the various data sets. For example, the annotation may be called a “condition header”, “header”, “trailer”, or “status”, herein, and may comprise an indication of the status of the data set or may include an identifier correlated to a specific issuer or owner of the data. In one example, the first three bytes of each data set BLOB may be configured or configurable to indicate the status of that particular data set; e.g., LOADED, INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED. Subsequent bytes of data may be used to indicate for example, the identity of the issuer, user, transaction/membership account identifier or the like. Each of these condition annotations are further discussed herein.
The data set annotation may also be used for other types of status information as well as various other purposes. For example, the data set annotation may include security information establishing access levels. The access levels may, for example, be configured to permit only certain individuals, levels of employees, companies, or other entities to access data sets, or to permit access to specific data sets based on the transaction, merchant, issuer, user or the like. Furthermore, the security information may restrict/permit only certain actions such as accessing, modifying, and/or deleting data sets. In one example, the data set annotation indicates that only the data set owner or the user are permitted to delete a data set, various identified users may be permitted to access the data set for reading, and others are altogether excluded from accessing the data set. However, other access restriction parameters may also be used allowing various entities to access a data set with various permission levels as appropriate.
The data, including the header or trailer may be received by a stand-alone interaction device configured to add, delete, modify, or augment the data in accordance with the header or trailer. As such, in one embodiment, the header or trailer is not stored on the transaction device along with the associated issuer-owned data but instead the appropriate action may be taken by providing to the transaction instrument user at the stand-alone device, the appropriate option for the action to be taken. System 1300 contemplates a data storage arrangement wherein the header or trailer, or header or trailer history, of the data is stored on the transaction instrument in relation to the appropriate data.
One skilled in the art will also appreciate that, for security reasons, any databases, systems, devices, servers or other components of system 1300 may consist of any combination thereof at a single location or at multiple locations, wherein each database or system 1300 includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like.
In addition to those described above, the various system components discussed herein may include one or more of the following: a host server or other computing systems including a processor for processing digital data; a memory coupled to the processor for storing digital data; an input digitizer coupled to the processor for inputting digital data; an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor; a display device coupled to the processor and memory for displaying information derived from digital data processed by the processor; and a plurality of databases. Various databases used herein may include: client data; merchant data; financial institution data; and/or like data useful in the operation of the present system. As those skilled in the art will appreciate, user computer may include an operating system (e.g., Windows NT, 95/98/2000, OS2, UNIX, Linux, Solaris, MacOS, etc.) as well as various conventional support software and drivers typically associated with computers. The computer may include any suitable personal computer, network computer, workstation, minicomputer, mainframe or the like. User computer can be in a home or business environment with access to a network. In an exemplary embodiment, access is through a network or the Internet through a commercially-available web-browser software package.
As used herein, the term “network” includes any cloud, cloud computing system or electronic communications system or method which incorporates hardware and/or software components. Communication among the parties may be accomplished through any suitable communication channels, such as, for example, a telephone network, an extranet, an intranet, Internet, point of interaction device (point of sale device, personal digital assistant (e.g., iPhone®, Palm Pilot®, Blackberry®), cellular phone, kiosk, etc.), online communications, satellite communications, off-line communications, wireless communications, transponder communications, local area network (LAN), wide area network (WAN), virtual private network (VPN), networked or linked devices, keyboard, mouse and/or any suitable communication or data input modality. Moreover, although the system is frequently described herein as being implemented with TCP/IP communications protocols, the system may also be implemented using IPX, Appletalk, IP-6, NetBIOS, OSI, any tunneling protocol (e.g. IPsec, SSH), or any number of existing or future protocols. If the network is in the nature of a public network, such as the Internet, it may be advantageous to presume the network to be insecure and open to eavesdroppers. Specific information related to the protocols, standards, and application software utilized in connection with the Internet is generally known to those skilled in the art and, as such, need not be detailed herein. See, for example, D
“Cloud” or “Cloud computing” includes a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. Cloud computing may include location-independent computing, whereby shared servers provide resources, software, and data to computers and other devices on demand. For more information regarding cloud computing, see the NIST's (National Institute of Standards and Technology) definition of cloud computing at http://esrc.nist.gov/groups/SNS/cloud-computing/cloud-def-v15.doc (last visited Feb. 4, 2011), which is hereby incorporated by reference in its entirety.
The disclosure may be described herein in terms of functional Hock components, screen shots, optional selections and various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, system 1300 may employ various integrated circuit components, e.g., memory elements, processing elements, logic elements, lookup tables, and/or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of system 1300 may be implemented with any programming or scripting language such as C, C++, Java, COBOL, assembler, PERL, Visual Basic, SQL Stored Procedures, extensible markup language (XML), with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that system 1300 may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and/or the like. Still further, system 1300 could be used to detect or prevent security issues with a client-side scripting language, such as JavaScript, VBScript or the like. For a basic introduction of cryptography and network security, see any of the following references: (1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,” by Bruce Schneier, published by John Wiley & Sons (second edition, 1995); (2) “Java Cryptography” by Jonathan Knudson, published by O'Reilly & Associates (1998); (3) “Cryptography & Network Security: Principles & Practice” by William Stallings, published by Prentice Hall; all of which are hereby incorporated by reference.
These software elements may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions that execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Accordingly, functional blocks of the block diagrams and flowchart illustrations support combinations of means for performing the specified functions, combinations of steps for performing the specified functions, and program instruction means for performing the specified functions. It will also be understood that each functional block of the block diagrams and flowchart illustrations, and combinations of functional blocks in the block diagrams and flowchart illustrations, may be implemented by either special purpose hardware-based computer systems which perform the specified functions or steps, or suitable combinations of special purpose hardware and computer instructions. Further, illustrations of the process flows and the descriptions thereof may make reference to user windows, web pages, web sites, web forms, prompts, etc. Practitioners will appreciate that the illustrated steps described herein may comprise in any number of configurations including the use of windows, web pages, web forms, popup windows, prompts and/or the like. It should be further appreciated that the multiple steps as illustrated and described may be combined into single web pages and/or windows but have been expanded for the sake of simplicity. In other cases, steps illustrated and described as single process steps may be separated into multiple web pages and/or windows but have been combined for simplicity.
Practitioners will appreciate that there are a number of methods for displaying data within a browser-based document. Data may be represented as standard text or within a fixed list, scrollable list, drop-down list, editable text field, fixed text field, pop-up window, and/or the like. Likewise, there are a number of methods available for modifying data in a web page such as, for example, free text entry using a keyboard, selection of menu items, check boxes, option boxes, and/or the like.
In one embodiment, RCP 130 includes application programming interfaces that enable third parties to create, configure, manage, modify, update, delete, report on, and enhance reward offers and marketing programs. For example, a program provider (e.g., an LPP or TAP) may wish to create a custom application (“partner application”) that serves as a front-end or interface to RCP 130. The partner application accesses RCP 130 via various application programming interfaces (APIs). In one embodiment, the APIs may include a partner registration API, an offer set-up API, an enrollment API, a transaction API, a trigger API, a partner registration API, a reporting API and a marketing channel API, RCP 130 is a robust extensible platform that enables, in various embodiments, a variety of APIs for accessing a variety of functions. While some APIs may correspond directly to a function that may be desired by a partner, others may provide access to core functionality such as, for example, APIs for accessing workflow functionality or for accessing database query functionality.
Partner registration API 1405 may enable a marketing partner to access RCP 130 in order to register with and configure access to RCP 130, In one embodiment, a developer portal provides an interface to partner users and a registration request is sent via partner registration API 1405 to RCP 130, RCP 130 validates the registration request and executes a workflow to provision a partner user identification code (“user id”) and an API access code, RCP 130 saves a partner profile in the partner database 1410. In one embodiment, RCP 130 allocates memory, databases, file structure and/or other system resources to be used by partner users in testing and in production. In an embodiment, based upon a workflow and/or predefined business rules, RCP 130 executes logic to approve the registration request. The process to approve the registration request may be completely automated and/or may comprise steps whereby RCP administrators provide a manual approval. RCP 130 sends the registration information (e.g., user id and access code) to the partner user. A partner user and/or a RCP administrator may also access RCP 130 via partner registration API 1405 in order to update partner details, and terminate the partner if needed.
Offer setup API 1415 may allow a partner to build their own offer set up tool, may provide access to their own internal users, and/or may allow the partner to open up the tool to external users of their application or service (e.g., a user base of merchants or a company representing merchants). In one embodiment, offer setup API 1415 enables receiving a offer setup request; parsing the offer set up request into offer parameters; validating the offer setup request and/or the offer parameters; notifying a first approver of the offer setup request; receiving from the first approver, an approval of the offer set up request; saving an offer comprising the first offer parameters; associating the offer associated with a marketing program; and determining a first population of transaction accounts that comply with first offer criteria.
In one embodiment, the parsing includes applying logical and/or business rules to a request to divide, reorganize, translate and/or augment the data associated with a request. In various embodiments, parsing may be accomplished as part of the data validation process and/or as part of populating the data in a database. Data validation includes applying logical and/or business rules in order to ensure that data is received in, for example, an expected format and/or structure and that the data conforms in content to business rules that govern the data. Business rules used to parse the data may be based upon, for example, a partner, an offer, a product, an industry, a promotion, a program, a transaction processor, an issuer or any combination of these or other factors. Data that fails validation may cause an error to be sent to the system that sent the data and/or may cause RCP 130 administrator staff to examine and or modify the data.
Thus, a RCP 138 user (e.g., a partner) may use offer setup API 1415 to configure marketing programs and offers and to determine a population of transaction accounts that may be eligible for a program. Such data may be useful to a marketing partner in analyzing and targeting a particular promotion. Offer setup API 1415 may also enable a partner to specify criteria (e.g., define qualifying transactions, behaviors, events or thresholds) that qualify for a reward. The offer criteria may include any combination of a customer identifier, a customer demographic, a customer location, spend frequency, a spend threshold, a spend history, an award cap, a tiered reward requirement, a product identifier, a product category, a stock-keeping unit (SKU), a universal product code (UPC), a QR code, a merchant, a merchant type, an industry, a merchant location. Thus, offer set up API 1415 enables a partner to enter, maintain, analyze reward eligibility and configure RCP 130 to execute the offer. These constructs may enable highly targeted marketing promotions tailored to the specific needs of the partner, or the partner's user base. Any or all of these factors may also be used to exclude transaction accounts that may participate in an offer and/or provide criteria for excluding or withholding a reward.
In various embodiments, offer setup API also enables a partner to configure how offer costs are collected from a participating service establishment (e.g., merchant). For example, offer costs can be debited from the merchant account associated with where the qualifying transaction actually occurred (e.g., where a customer transacted), or from a single merchant specified by the partner. Offer setup API also enables a partner to configure the amount, currency and manner in which rewards are distributed. For example, in addition to fulfilling via statement credits, output files can be generated and passed to the partner to enable new types of fulfillment such as social currency. In an embodiment, RCP 130 determines that a qualifying transaction (and or event) has occurred and calculates a reward for a member or transaction account. Distributing the reward may include crediting a first transaction account, crediting a second transaction account, crediting a rewards account associated with the first transaction account, performing a currency conversion, crediting a social networking currency and sending reward data to a third party, where the third party applies the reward based upon the reward data.
Enrollment API 1420 may enable RCP 130 to capture enrollments from programs set up through the offer set up API. It may enable a partner to build their own enrollment functionality and embed the feature into their application. For example, a partner may design a rewards program and wish to solicit participation and enable enrollment in the program using a variety of different methods such as via an email message, a link, a uniform resource locator (URL), customized web page, a web page hosted by the automated marketing system, a social networking web site, an app, a text message and a mobile application. Thus, the partner may define, via the enrollment API, that a web page be generated and hosted via RCP 130 and used to receive and process enrollments in a program. In an embodiment, the partner may define, via the enrollment API, a custom web page (or URL) by which enrollment may occur and, optionally, may define a access requirements (e.g., user id/password) for enrolling in a program.
The partner may use (e.g., via a custom application or website) enrollment API 1420 to enter and configure enrollment parameters in RCP 130. Enrollment parameters may include defining an enrollment process, instructions for generating a hosted enrollment page, a referral uniform resource locator (URL), a user id, a password, a passcode, an enrollment timeframe, and an enrollment cap, and enrollee (e.g., offer or program participant) tracking data requirements. The enrollee tracking requirements may include a user id, email address, password, product code, and transaction location; thus, the enrollment API is useful in defining how a transaction account or member may enroll in a program and defining data and events by which the partner may track a member's activity. Thus, a partner, program provider or issuer may capture the user ID/e-mail/phone number/password, product category, or other unique identifier(s) (QR code or marketing channel information) and/or may track this information during a program in order to enable additional reporting metrics, specific product opt-ins, and/or the trigger API functionality (discussed below).
Reporting API 1425 may enable real-time, or near real-time, results to an interfacing system (e.g., partner system). Using reporting API 1425, the partner can also define reports and data to be distributed to third parties such as, for example, program participants (merchants and customer), news sites, social media networks, etc. Reporting API may provide the ability to define and/or access a wide range of cumulative and incremental metrics. The metrics may include, for example, number of enrollments, CV, avg. ROC, number discounts, money discounts (or alternate fulfillment method). The partner and the partner's users will also have the ability to opt-in for in-depth pre/post-campaign metrics. Additional fields captured during enrollment can also be appended to reporting data and passed back to the partner.
Transaction API 1430 may enable a partner to define transactions and/or events that trigger data to be shared with a third party. For example, a transaction account issuer may allow their customers (e.g., transaction account owners) to opt-in to triggered data sharing so that when a customer initiates a transaction, data regarding that transaction is posted to a user's social networking account. For example, a customer swipes a transaction account card at a local florist when purchasing flowers, RCP 138 receives transaction details from the transaction account authorization process, and details regarding the transaction (e.g., merchant name, location, transaction amount, product, product type, time of transaction, etc.) are sent via transaction API to the Facebook account of the consumer. Thus, in one embodiment, RCP 138 leverages the transaction account authorization process to provide a new capability which allows customers to share transaction information in real-time.
Transaction API 1430 may enable a real-time service allowing customers to automatically share their spend behavior with social networks, smartphone applications, and other 3rd party destinations. In one embodiment, customers opt-in for this service, and select criteria for their spend information will be shared (e.g. “only share transactions at restaurants, but never share transactions at jewelry stores.”)
In one embodiment, RCP 138 receives, via transaction API 1430, a data sharing opt-in associated with the first transaction account, wherein the data sharing opt-in defines data sharing transactions for which the first user authorizes personal data sharing. RCP 138 obtains transaction notification data for a transaction authorization request associated with the first transaction account and determines that the transaction authorization request qualifies as a data sharing transaction. RCP 130 sends data associated with the transaction authorization request to at least one of a web site, a social networking site, a social networking application, a third party, an individual, and a social networking account of a friend.
Trigger API 1435 may enable a partner to define conditions and/or events that trigger a message or data (“alerts”) to be sent passed to the partner or other 3rd parties. In one embodiment, trigger API 1435 enables a partner to configure and manage managed alerts, or alerts for its users who are merchants (or representing merchants). The partner may configure trigger alerts based on any data accessible to RCP 138 (e.g., customer, merchant or product specific data), any calculation or business rule associated with the data (e.g., a counter, accumulation or threshold)
In an embodiment, RCP 130 receives, via a trigger API, a triggered event request defining triggered alert parameters for triggered offer alerts, wherein the triggered event parameters define offer alerts based upon at least one of; a number of enrollments for an offer; a number of authorization requests associated with an offer, a number of authorization requests associated with a transaction account, an award cap, an award threshold, a tiered reward requirement, a product identifier, a product category, a stock-keeping unit (SKU), a QR code, a universal product code (UPC), a merchant, a merchant type, an industry, a merchant location, and an marketing program result. In an embodiment, RCP 130 receives, via a trigger API, a triggered event request defining triggered alert parameters for triggered customer alerts, wherein the triggered event parameters define customer alerts based upon at least one of: offer progress, program progress, authorization requests associated with an offer, spend associated with an offer, spend associated with a program, spend associated with a merchant, a cross promotion, a second offer, an offer achievement and a customized message. RCP 138 monitors it's databases and event logs for criteria for which a trigger is defined, formats a trigger alert and distributes the alert according to distribution criteria defined by the particular trigger parameters.
Marketing channel API 1440 may enable a partner to query offer database 452 and/or other data sources. For example, via offer setup API 1415 a restaurant offers for 5% credit for all meals purchased on Sundays and offers 1% of the transaction value to marketing partners that sign up customers. A marketing channel partner (e.g., Groupon) uses marketing channel API 1440 to query the database, find this offer and opt-in to promoting the offer through the marketing channel. The marketing channel partner uses marketing channel API to determine merchant name, offer details (logo, Ts & Cs, dates etc.), offer construct, merchant location (address and longitude/latitude) for use in the promotion.
In one embodiment, RCP 130 receives, from a requestor and via a marketing channel API, a marketing channel request for a list of at least one of marketing channels, offers and programs. RCP 130 sends, via the marketing channel API, the list to the requestor associated with the marketing channel request. The list includes a merchant name, program details, offer details, offer terms and conditions, an advertisement, a logo and/or a merchant location. RCP receives, via the marketing channel API, a marketing channel opt-in request associates the requestor with at least one of a marketing channel, a program and an offer associated with the opt-in request.
The detailed description of exemplary embodiments herein makes reference to the accompanying drawings and pictures, which show the exemplary embodiment by way of illustration and its best mode. While these exemplary embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the disclosure. Thus, the detailed description herein is presented for purposes of illustration only and not of limitation. For example, the steps recited in any of the method or process descriptions may be executed in any order and are not limited to the order presented. Moreover, any of the functions or steps may be outsourced to or performed by one or more third parties. Furthermore, any reference to singular includes plural embodiments, and any reference to more than one component may include a singular embodiment.
Benefits, other advantages, and solutions to problems have been described herein with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any elements that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of the disclosure. The scope of the disclosure is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean “one and only one” unless explicitly so stated, but rather “one or more.” Moreover, where a phrase similar to at least one of A, B, or C′ is used in the claims or specification, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C. All structural, chemical, and functional equivalents to the elements of the above-described exemplary embodiments that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Further, a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
This application is a continuation of U.S. Ser. No. 13/153,890 entitled “System and Method for Administering Marketing Programs” filed on Jun. 6, 2011. The '890 application is a continuation-in-part of U.S. Ser. No. 12/857,389 entitled “System and Method for E-Mail Based Rewards” filed on Aug. 16, 2010. The '389 application claims priority to U.S. Ser. No. 11/779,734, entitled “Loyalty Incentive Program Using Transaction Cards,” filed on Jul. 18, 2007. The '734 application claims priority to U.S. Provisional Ser. No. 60/831,457, filed Jul. 18, 2006. The entire disclosures of each are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4833308 | Humble | May 1989 | A |
| 4882675 | Nichtberger et al. | Nov 1989 | A |
| 5025372 | Burton et al. | Jun 1991 | A |
| 5467269 | Flaten | Nov 1995 | A |
| 5471669 | Lidman | Nov 1995 | A |
| 5729693 | Holda-Fleck | Mar 1998 | A |
| 5918211 | Sloane | Jun 1999 | A |
| 5923016 | Fredregill et al. | Jul 1999 | A |
| 5948040 | DeLorme et al. | Sep 1999 | A |
| 5953706 | Patel | Sep 1999 | A |
| 6009411 | Kepecs | Dec 1999 | A |
| 6018718 | Walker et al. | Jan 2000 | A |
| 6035280 | Christensen | Mar 2000 | A |
| 6039244 | Finsterwald | Mar 2000 | A |
| 6222914 | McMullin | Apr 2001 | B1 |
| 6266649 | Linden et al. | Jul 2001 | B1 |
| 6321208 | Barnett et al. | Nov 2001 | B1 |
| 6330543 | Kepecs | Dec 2001 | B1 |
| 6332126 | Peirce et al. | Dec 2001 | B1 |
| 6336099 | Barnett et al. | Jan 2002 | B1 |
| 6343317 | Glorikian | Jan 2002 | B1 |
| 6360167 | Millington et al. | Mar 2002 | B1 |
| 6370514 | Messner | Apr 2002 | B1 |
| 6381603 | Chan et al. | Apr 2002 | B1 |
| 6414635 | Stewart et al. | Jul 2002 | B1 |
| 6430539 | Lazarus et al. | Aug 2002 | B1 |
| 6434534 | Walker et al. | Aug 2002 | B1 |
| 6542814 | Polidi et al. | Apr 2003 | B2 |
| 6584448 | Laor | Jun 2003 | B1 |
| 6587835 | Treyz et al. | Jul 2003 | B1 |
| 6606619 | Ortega et al. | Aug 2003 | B2 |
| 6691915 | Thaxton et al. | Feb 2004 | B1 |
| 6738711 | Ohmura et al. | May 2004 | B2 |
| 6748365 | Quinlan et al. | Jun 2004 | B1 |
| 6882290 | French et al. | Apr 2005 | B2 |
| 6883708 | Fiedler et al. | Apr 2005 | B1 |
| 6904408 | McCarthy et al. | Jun 2005 | B1 |
| 6937995 | Kepecs | Aug 2005 | B1 |
| 7003476 | Samra et al. | Feb 2006 | B1 |
| 7010497 | Nyhan et al. | Mar 2006 | B1 |
| 7016860 | Modani et al. | Mar 2006 | B2 |
| 7054830 | Eggleston et al. | May 2006 | B1 |
| 7072851 | Wilcox et al. | Jul 2006 | B1 |
| 7107238 | Hatakama et al. | Sep 2006 | B2 |
| 7120591 | Solomon et al. | Oct 2006 | B1 |
| 7139793 | Lala et al. | Nov 2006 | B2 |
| 7146328 | Solomon et al. | Dec 2006 | B1 |
| 7165037 | Lazarus et al. | Jan 2007 | B2 |
| 7302429 | Wanker | Nov 2007 | B1 |
| 7392224 | Bauer et al. | Jun 2008 | B1 |
| 7428505 | Levy et al. | Sep 2008 | B1 |
| 7430521 | Walker et al. | Sep 2008 | B2 |
| 7455226 | Hammond | Nov 2008 | B1 |
| 7472073 | Masi | Dec 2008 | B1 |
| 7493268 | Kepros et al. | Feb 2009 | B2 |
| 7496520 | Handel et al. | Feb 2009 | B1 |
| 7499889 | Golan et al. | Mar 2009 | B2 |
| 7506805 | Chakravarthy | Mar 2009 | B1 |
| 7512551 | Postrel | Mar 2009 | B2 |
| 7596566 | Patwardhan | Sep 2009 | B1 |
| 7599858 | Grady et al. | Oct 2009 | B1 |
| 7618318 | Ciancio et al. | Nov 2009 | B2 |
| 7630935 | Loeger et al. | Dec 2009 | B2 |
| 7647278 | Foth | Jan 2010 | B1 |
| 7653572 | Thompson | Jan 2010 | B1 |
| 7660743 | Messa et al. | Feb 2010 | B1 |
| 7665660 | Degliantoni et al. | Feb 2010 | B2 |
| 7668749 | Kepros et al. | Feb 2010 | B2 |
| 7676467 | Kozyrczak et al. | Mar 2010 | B1 |
| 7681786 | Chakravarthy | Mar 2010 | B1 |
| 7706808 | Aggarwal et al. | Apr 2010 | B1 |
| 7711586 | Aggarwal et al. | May 2010 | B2 |
| 7734486 | Mortimore, Jr. | Jun 2010 | B2 |
| 7739134 | Mortimore, Jr. | Jun 2010 | B2 |
| 7742954 | Handel et al. | Jun 2010 | B1 |
| 7743002 | Hernandez | Jun 2010 | B2 |
| 7747524 | Brown | Jun 2010 | B2 |
| 7752328 | Mortimore, Jr. et al. | Jul 2010 | B2 |
| 7765119 | Messa et al. | Jul 2010 | B2 |
| 7788141 | Sim | Aug 2010 | B1 |
| 7797199 | Forshaw et al. | Sep 2010 | B2 |
| 7801760 | Handel et al. | Sep 2010 | B2 |
| 7806328 | Chakravarthy | Oct 2010 | B2 |
| 7814029 | Siegel | Oct 2010 | B1 |
| 7844488 | Merriman et al. | Nov 2010 | B2 |
| 7844490 | Patterson | Nov 2010 | B2 |
| 7865513 | Welch et al. | Jan 2011 | B2 |
| 7870022 | Bous et al. | Jan 2011 | B2 |
| 7899704 | Thompson | Mar 2011 | B1 |
| 7925540 | Orttung et al. | Apr 2011 | B1 |
| 7933810 | Morgenstern | Apr 2011 | B2 |
| 7937330 | Handel et al. | May 2011 | B2 |
| 7941374 | Orttung et al. | May 2011 | B2 |
| 7958017 | Rempe et al. | Jun 2011 | B1 |
| 7962381 | Handel et al. | Jun 2011 | B2 |
| 7966213 | Messa et al. | Jun 2011 | B2 |
| 7970666 | Handel | Jun 2011 | B1 |
| 7991664 | Stone | Aug 2011 | B1 |
| 8073719 | Orttung et al. | Dec 2011 | B2 |
| 8078496 | Postrel | Dec 2011 | B2 |
| 8082270 | Goyal | Dec 2011 | B2 |
| 8090707 | Orttung et al. | Jan 2012 | B1 |
| 8095402 | Orttung et al. | Jan 2012 | B2 |
| 8108304 | Loeger et al. | Jan 2012 | B2 |
| 8117073 | Orttung et al. | Feb 2012 | B1 |
| 8121953 | Orttung et al. | Feb 2012 | B1 |
| 8126771 | Walker et al. | Feb 2012 | B2 |
| 8126776 | Messa et al. | Feb 2012 | B2 |
| 8131588 | Walker et al. | Mar 2012 | B2 |
| 8140387 | Heywood | Mar 2012 | B2 |
| 8145522 | Warren et al. | Mar 2012 | B2 |
| 8160922 | Postrel | Apr 2012 | B2 |
| 8170916 | Dicker et al. | May 2012 | B1 |
| 8175926 | Handel et al. | May 2012 | B1 |
| 8180682 | Narayanaswami et al. | May 2012 | B2 |
| 8180796 | Mah et al. | May 2012 | B1 |
| 8249934 | Agarwal et al. | Aug 2012 | B2 |
| 8438061 | Grimes | May 2013 | B2 |
| 8459551 | Lee et al. | Jun 2013 | B2 |
| 8463643 | Bennett | Jun 2013 | B2 |
| 8463706 | Cervenka et al. | Jun 2013 | B2 |
| 8463851 | Bennett et al. | Jun 2013 | B2 |
| 8468053 | Bennett | Jun 2013 | B2 |
| 8473334 | Gibbs | Jun 2013 | B2 |
| 8484088 | Orttung et al. | Jul 2013 | B1 |
| 8484093 | Bennett et al. | Jul 2013 | B2 |
| 8489456 | Burgess et al. | Jul 2013 | B2 |
| 8494901 | Magadi et al. | Jul 2013 | B2 |
| 8494914 | Mesaros | Jul 2013 | B2 |
| 8504423 | Rotbard et al. | Aug 2013 | B2 |
| 8515810 | Grimes | Aug 2013 | B2 |
| 8517258 | Taylor et al. | Aug 2013 | B2 |
| 8543470 | Grady et al. | Sep 2013 | B2 |
| 8560389 | Burgess et al. | Oct 2013 | B2 |
| 8573477 | Bennett et al. | Nov 2013 | B2 |
| 8573491 | Bennett et al. | Nov 2013 | B2 |
| 8606630 | Fordyce, III et al. | Dec 2013 | B2 |
| 8615426 | Carlson | Dec 2013 | B2 |
| 8621068 | Zohar et al. | Dec 2013 | B2 |
| 8621215 | Iyer | Dec 2013 | B1 |
| 8626579 | Fordyce, III et al. | Jan 2014 | B2 |
| 8639567 | Winters | Jan 2014 | B2 |
| 8650071 | Pointer et al. | Feb 2014 | B2 |
| 8725635 | Klein et al. | May 2014 | B2 |
| 8874674 | Allison et al. | Oct 2014 | B2 |
| 9009082 | Marshall et al. | Apr 2015 | B1 |
| 9031866 | Ng et al. | May 2015 | B1 |
| 20010014868 | Herz et al. | Aug 2001 | A1 |
| 20010020242 | Gupta et al. | Sep 2001 | A1 |
| 20010037254 | Glikman | Nov 2001 | A1 |
| 20010054003 | Chien et al. | Dec 2001 | A1 |
| 20020069079 | Vega | Jun 2002 | A1 |
| 20020069312 | Jones | Jun 2002 | A1 |
| 20020082920 | Austin et al. | Jun 2002 | A1 |
| 20020095357 | Hunter et al. | Jul 2002 | A1 |
| 20020138343 | Weatherford et al. | Sep 2002 | A1 |
| 20020178056 | Lim | Nov 2002 | A1 |
| 20030004802 | Callegari | Jan 2003 | A1 |
| 20030027630 | Kelly et al. | Feb 2003 | A1 |
| 20030028518 | Mankoff | Feb 2003 | A1 |
| 20030033211 | Haines et al. | Feb 2003 | A1 |
| 20030061093 | Todd | Mar 2003 | A1 |
| 20030078832 | Alvarez et al. | Apr 2003 | A1 |
| 20030208442 | Cockrill et al. | Nov 2003 | A1 |
| 20030233278 | Marshall | Dec 2003 | A1 |
| 20040006509 | Mannik et al. | Jan 2004 | A1 |
| 20040039686 | Klebanoff | Feb 2004 | A1 |
| 20040098326 | James | May 2004 | A1 |
| 20040122736 | Strock et al. | Jun 2004 | A1 |
| 20040153389 | Lortscher | Aug 2004 | A1 |
| 20040225509 | Andre et al. | Nov 2004 | A1 |
| 20040225573 | Ling | Nov 2004 | A1 |
| 20040243468 | Cohagan et al. | Dec 2004 | A1 |
| 20050010472 | Quatse et al. | Jan 2005 | A1 |
| 20050021401 | Postrel | Jan 2005 | A1 |
| 20050065848 | Mitchell et al. | Mar 2005 | A1 |
| 20050071225 | Bortolin et al. | Mar 2005 | A1 |
| 20050071227 | Hammad et al. | Mar 2005 | A1 |
| 20050071228 | Bortolin et al. | Mar 2005 | A1 |
| 20050071230 | Mankoff | Mar 2005 | A1 |
| 20050096976 | Nelms | May 2005 | A1 |
| 20050149394 | Postrel | Jul 2005 | A1 |
| 20050159996 | Lazarus et al. | Jul 2005 | A1 |
| 20050192863 | Mohan | Sep 2005 | A1 |
| 20050240477 | Friday et al. | Oct 2005 | A1 |
| 20050246272 | Kitada et al. | Nov 2005 | A1 |
| 20050273388 | Roetter | Dec 2005 | A1 |
| 20060004633 | Ashbaugh | Jan 2006 | A1 |
| 20060026067 | Nicholas et al. | Feb 2006 | A1 |
| 20060041480 | Briggs | Feb 2006 | A1 |
| 20060053056 | Alspach-Goss et al. | Mar 2006 | A1 |
| 20060064372 | Gupta | Mar 2006 | A1 |
| 20060074749 | Kline | Apr 2006 | A1 |
| 20060076400 | Fletcher | Apr 2006 | A1 |
| 20060085240 | Salehi-sedeh et al. | Apr 2006 | A1 |
| 20060095434 | McCullough et al. | May 2006 | A1 |
| 20060111930 | Ayer et al. | May 2006 | A1 |
| 20060116800 | Obradovich et al. | Jun 2006 | A1 |
| 20060122874 | Postrel | Jun 2006 | A1 |
| 20060129426 | Pearson | Jun 2006 | A1 |
| 20060136299 | Ruhmkorf | Jun 2006 | A1 |
| 20060155603 | Abendroth et al. | Jul 2006 | A1 |
| 20060155641 | Postrel | Jul 2006 | A1 |
| 20060167753 | Teague et al. | Jul 2006 | A1 |
| 20060178932 | Lang | Aug 2006 | A1 |
| 20060195359 | Robinson et al. | Aug 2006 | A1 |
| 20060212355 | Teague et al. | Sep 2006 | A1 |
| 20060224449 | Byerley et al. | Oct 2006 | A1 |
| 20060241859 | Kimchi et al. | Oct 2006 | A1 |
| 20060242011 | Bell et al. | Oct 2006 | A1 |
| 20060253321 | Heywood | Nov 2006 | A1 |
| 20060258397 | Kaplan et al. | Nov 2006 | A1 |
| 20060259364 | Strock et al. | Nov 2006 | A1 |
| 20060271552 | McChesney et al. | Nov 2006 | A1 |
| 20070000997 | Lambert et al. | Jan 2007 | A1 |
| 20070010942 | Bill | Jan 2007 | A1 |
| 20070022019 | Sherwin et al. | Jan 2007 | A1 |
| 20070033104 | Collins et al. | Feb 2007 | A1 |
| 20070038515 | Postrel | Feb 2007 | A1 |
| 20070038516 | Apple et al. | Feb 2007 | A1 |
| 20070050258 | Dohse | Mar 2007 | A1 |
| 20070061223 | Rodriguez et al. | Mar 2007 | A1 |
| 20070073599 | Perry et al. | Mar 2007 | A1 |
| 20070083428 | Goldstein | Apr 2007 | A1 |
| 20070094114 | Bufford | Apr 2007 | A1 |
| 20070129995 | Brandow | Jun 2007 | A1 |
| 20070130000 | Assanassios | Jun 2007 | A1 |
| 20070136135 | Loeger et al. | Jun 2007 | A1 |
| 20070146812 | Lawton | Jun 2007 | A1 |
| 20070150349 | Handel et al. | Jun 2007 | A1 |
| 20070192178 | Fung et al. | Aug 2007 | A1 |
| 20070192192 | Haberman et al. | Aug 2007 | A1 |
| 20070198354 | Senghore et al. | Aug 2007 | A1 |
| 20070198432 | Pitroda et al. | Aug 2007 | A1 |
| 20070208879 | Liu | Sep 2007 | A1 |
| 20070210152 | Read | Sep 2007 | A1 |
| 20070214040 | Patel et al. | Sep 2007 | A1 |
| 20070244741 | Blume et al. | Oct 2007 | A1 |
| 20070244811 | Tumminaro | Oct 2007 | A1 |
| 20070260513 | Pavlov | Nov 2007 | A1 |
| 20070260523 | Schadt | Nov 2007 | A1 |
| 20070288312 | Wang | Dec 2007 | A1 |
| 20070288372 | Behar et al. | Dec 2007 | A1 |
| 20080004917 | Mortimore, Jr. | Jan 2008 | A1 |
| 20080004919 | Stubbs | Jan 2008 | A1 |
| 20080004980 | Hernandez | Jan 2008 | A1 |
| 20080005148 | Welch et al. | Jan 2008 | A1 |
| 20080021772 | Aloni et al. | Jan 2008 | A1 |
| 20080032720 | Mamdani et al. | Feb 2008 | A1 |
| 20080033857 | Moses | Feb 2008 | A1 |
| 20080040211 | Walker et al. | Feb 2008 | A1 |
| 20080040288 | Mortimore, Jr. et al. | Feb 2008 | A1 |
| 20080052140 | Neal et al. | Feb 2008 | A1 |
| 20080052151 | Xie et al. | Feb 2008 | A1 |
| 20080059220 | Roth et al. | Mar 2008 | A1 |
| 20080065491 | Bakman | Mar 2008 | A1 |
| 20080082418 | Fordyce et al. | Apr 2008 | A1 |
| 20080091445 | Mihic | Apr 2008 | A1 |
| 20080091528 | Rampell et al. | Apr 2008 | A1 |
| 20080091537 | Miller et al. | Apr 2008 | A1 |
| 20080091549 | Chang et al. | Apr 2008 | A1 |
| 20080091828 | Mortimore, Jr. | Apr 2008 | A1 |
| 20080092162 | Lundy et al. | Apr 2008 | A1 |
| 20080109317 | Singh et al. | May 2008 | A1 |
| 20080109489 | Sherwood | May 2008 | A1 |
| 20080120155 | Pliha | May 2008 | A1 |
| 20080126515 | Chambers et al. | May 2008 | A1 |
| 20080147450 | Mortimore, Jr. | Jun 2008 | A1 |
| 20080147514 | Shuster et al. | Jun 2008 | A1 |
| 20080147773 | Aaron | Jun 2008 | A1 |
| 20080154664 | Kuo et al. | Jun 2008 | A1 |
| 20080162206 | Mak et al. | Jul 2008 | A1 |
| 20080167991 | Carlson et al. | Jul 2008 | A1 |
| 20080189169 | Turpin et al. | Aug 2008 | A1 |
| 20080195475 | Lambert et al. | Aug 2008 | A1 |
| 20080196060 | Varghese | Aug 2008 | A1 |
| 20080201197 | Orttung et al. | Aug 2008 | A1 |
| 20080201224 | Owens et al. | Aug 2008 | A1 |
| 20080201432 | Orttung et al. | Aug 2008 | A1 |
| 20080210753 | Plozay et al. | Sep 2008 | A1 |
| 20080255940 | Perreault et al. | Oct 2008 | A1 |
| 20080262925 | Kim | Oct 2008 | A1 |
| 20080270223 | Collins et al. | Oct 2008 | A1 |
| 20080270251 | Coelho et al. | Oct 2008 | A1 |
| 20080276270 | Kotaru et al. | Nov 2008 | A1 |
| 20080294624 | Kanigsberg et al. | Nov 2008 | A1 |
| 20090006142 | Orttung et al. | Jan 2009 | A1 |
| 20090006143 | Orttung et al. | Jan 2009 | A1 |
| 20090006188 | Guo et al. | Jan 2009 | A1 |
| 20090006194 | Sridharan et al. | Jan 2009 | A1 |
| 20090012839 | Fusillo et al. | Jan 2009 | A1 |
| 20090018916 | Seven et al. | Jan 2009 | A1 |
| 20090030609 | Orttung et al. | Jan 2009 | A1 |
| 20090030742 | Orttung et al. | Jan 2009 | A1 |
| 20090030769 | Orttung et al. | Jan 2009 | A1 |
| 20090030779 | Tollinger et al. | Jan 2009 | A1 |
| 20090037264 | Del Favero et al. | Feb 2009 | A1 |
| 20090055292 | Chong et al. | Feb 2009 | A1 |
| 20090063268 | Burgess et al. | Mar 2009 | A1 |
| 20090063351 | Schmeyer | Mar 2009 | A1 |
| 20090076912 | Rajan et al. | Mar 2009 | A1 |
| 20090094048 | Wallace | Apr 2009 | A1 |
| 20090140799 | Kasperkovitz | Jun 2009 | A1 |
| 20090150272 | Blythe | Jun 2009 | A1 |
| 20090156310 | Fargo | Jun 2009 | A1 |
| 20090163227 | Collins | Jun 2009 | A1 |
| 20090164314 | Blythe | Jun 2009 | A1 |
| 20090171842 | Blythe | Jul 2009 | A1 |
| 20090171853 | Georgiou et al. | Jul 2009 | A1 |
| 20090182718 | Waclawik et al. | Jul 2009 | A1 |
| 20090210261 | Mortimore, Jr. et al. | Aug 2009 | A1 |
| 20090228365 | Tomchek et al. | Sep 2009 | A1 |
| 20090247193 | Kalavade | Oct 2009 | A1 |
| 20090247282 | Cheng | Oct 2009 | A1 |
| 20090248457 | Munter et al. | Oct 2009 | A1 |
| 20090248543 | Nihalani et al. | Oct 2009 | A1 |
| 20090259499 | Bhojwani et al. | Oct 2009 | A1 |
| 20090265236 | Schultz et al. | Oct 2009 | A1 |
| 20090271263 | Regmi et al. | Oct 2009 | A1 |
| 20090276306 | Hicks | Nov 2009 | A1 |
| 20090287562 | Bosch et al. | Nov 2009 | A1 |
| 20090288012 | Hertel et al. | Nov 2009 | A1 |
| 20090289111 | Motycka et al. | Nov 2009 | A1 |
| 20090313109 | Bous et al. | Dec 2009 | A1 |
| 20090319353 | Palmeri | Dec 2009 | A1 |
| 20090327062 | Botes | Dec 2009 | A1 |
| 20090327174 | Honkala | Dec 2009 | A1 |
| 20100057565 | Au-Yeung et al. | Mar 2010 | A1 |
| 20100076777 | Paretti et al. | Mar 2010 | A1 |
| 20100079336 | Skibiski et al. | Apr 2010 | A1 |
| 20100082418 | Loeger et al. | Apr 2010 | A1 |
| 20100088174 | Cohagan et al. | Apr 2010 | A1 |
| 20100094697 | Cananaugh | Apr 2010 | A1 |
| 20100094698 | Cawley | Apr 2010 | A1 |
| 20100094699 | Beal | Apr 2010 | A1 |
| 20100106568 | Grimes | Apr 2010 | A1 |
| 20100106569 | Grimes | Apr 2010 | A1 |
| 20100106578 | Allio et al. | Apr 2010 | A1 |
| 20100106596 | Grimes | Apr 2010 | A1 |
| 20100114661 | Alderfer | May 2010 | A1 |
| 20100114686 | Carlson et al. | May 2010 | A1 |
| 20100131840 | Walker et al. | May 2010 | A1 |
| 20100138299 | Preston et al. | Jun 2010 | A1 |
| 20100145744 | Beck et al. | Jun 2010 | A1 |
| 20100145762 | Coladonato et al. | Jun 2010 | A1 |
| 20100145778 | Fordyce et al. | Jun 2010 | A1 |
| 20100145786 | Fordyce, III et al. | Jun 2010 | A1 |
| 20100145860 | Pelegero | Jun 2010 | A1 |
| 20100153194 | Oram | Jun 2010 | A1 |
| 20100179879 | Cunningham et al. | Jul 2010 | A1 |
| 20100191572 | Newman et al. | Jul 2010 | A1 |
| 20100211419 | Nickolayev et al. | Aug 2010 | A1 |
| 20100228613 | Anderson et al. | Sep 2010 | A1 |
| 20100241502 | Walker et al. | Sep 2010 | A1 |
| 20100241559 | O'Connor et al. | Sep 2010 | A1 |
| 20100250351 | Gillenson et al. | Sep 2010 | A1 |
| 20100250356 | Gillenson et al. | Sep 2010 | A1 |
| 20100257047 | Foodman et al. | Oct 2010 | A1 |
| 20100262456 | Feng et al. | Oct 2010 | A1 |
| 20100312629 | Wolf et al. | Dec 2010 | A1 |
| 20100324990 | D'Angelo et al. | Dec 2010 | A1 |
| 20100332307 | Parento | Dec 2010 | A1 |
| 20110004497 | Mortimore, Jr. et al. | Jan 2011 | A1 |
| 20110022448 | Strock et al. | Jan 2011 | A1 |
| 20110022455 | Wolf et al. | Jan 2011 | A1 |
| 20110029363 | Gillenson et al. | Feb 2011 | A1 |
| 20110029364 | Roeding et al. | Feb 2011 | A1 |
| 20110029367 | Olson et al. | Feb 2011 | A1 |
| 20110035266 | Patterson | Feb 2011 | A1 |
| 20110040539 | Szymczyk et al. | Feb 2011 | A1 |
| 20110047023 | Lieblang et al. | Feb 2011 | A1 |
| 20110055880 | Archer | Mar 2011 | A1 |
| 20110066483 | Salmon et al. | Mar 2011 | A1 |
| 20110066548 | Rodin | Mar 2011 | A1 |
| 20110078030 | Borst et al. | Mar 2011 | A1 |
| 20110078055 | Faribault et al. | Mar 2011 | A1 |
| 20110083101 | Sharon et al. | Apr 2011 | A1 |
| 20110087530 | Fordyce et al. | Apr 2011 | A1 |
| 20110087531 | Winters et al. | Apr 2011 | A1 |
| 20110093327 | Fordyce et al. | Apr 2011 | A1 |
| 20110093335 | Fordyce et al. | Apr 2011 | A1 |
| 20110093361 | Morales | Apr 2011 | A1 |
| 20110106607 | Alfonso et al. | May 2011 | A1 |
| 20110119133 | Igelman et al. | May 2011 | A1 |
| 20110125565 | MacIlwaine et al. | May 2011 | A1 |
| 20110137716 | Reuthe et al. | Jun 2011 | A1 |
| 20110137717 | Reuthe et al. | Jun 2011 | A1 |
| 20110137721 | Bansal | Jun 2011 | A1 |
| 20110145047 | Chetty et al. | Jun 2011 | A1 |
| 20110145149 | Valdes et al. | Jun 2011 | A1 |
| 20110161154 | McLaughlin et al. | Jun 2011 | A1 |
| 20110178928 | Carmichael et al. | Jul 2011 | A1 |
| 20110184792 | Butcher et al. | Jul 2011 | A1 |
| 20110191150 | Blackhurst et al. | Aug 2011 | A1 |
| 20110218031 | Bryant et al. | Sep 2011 | A1 |
| 20110225033 | Schmeyer et al. | Sep 2011 | A1 |
| 20110231224 | Winters | Sep 2011 | A1 |
| 20110231235 | MacIlwaine et al. | Sep 2011 | A1 |
| 20110231246 | Bhatia et al. | Sep 2011 | A1 |
| 20110238469 | Gershman et al. | Sep 2011 | A1 |
| 20110246280 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246281 | Satyavolu et al. | Oct 2011 | A1 |
| 20110246287 | Wright et al. | Oct 2011 | A1 |
| 20110246299 | Satyavolu et al. | Oct 2011 | A1 |
| 20110251883 | Satyavolu et al. | Oct 2011 | A1 |
| 20110251891 | Satyavolu et al. | Oct 2011 | A1 |
| 20110251934 | Satyavolu et al. | Oct 2011 | A1 |
| 20110264490 | Durvasula et al. | Oct 2011 | A1 |
| 20110270617 | Pacheco E Murta et al. | Nov 2011 | A1 |
| 20110270666 | Welsh et al. | Nov 2011 | A1 |
| 20110276373 | Juszczak et al. | Nov 2011 | A1 |
| 20110276377 | Kim et al. | Nov 2011 | A1 |
| 20110282702 | Mortimore, Jr. | Nov 2011 | A1 |
| 20110288918 | Cervenka et al. | Nov 2011 | A1 |
| 20110295689 | Brady | Dec 2011 | A1 |
| 20110295749 | Scalisi | Dec 2011 | A1 |
| 20110302011 | Yoder et al. | Dec 2011 | A1 |
| 20110313840 | Mason et al. | Dec 2011 | A1 |
| 20110313874 | Hardie et al. | Dec 2011 | A1 |
| 20110320250 | Gemmell et al. | Dec 2011 | A1 |
| 20120004964 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004965 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004966 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004967 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004968 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004969 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004970 | Satyavolu et al. | Jan 2012 | A1 |
| 20120004975 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010932 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010933 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010934 | Walker et al. | Jan 2012 | A1 |
| 20120010936 | Satyavolu et al. | Jan 2012 | A1 |
| 20120010937 | Hanson et al. | Jan 2012 | A1 |
| 20120022923 | Walker et al. | Jan 2012 | A1 |
| 20120023122 | Gregov et al. | Jan 2012 | A1 |
| 20120029996 | Lang et al. | Feb 2012 | A1 |
| 20120030048 | Manley et al. | Feb 2012 | A1 |
| 20120035997 | Burgess et al. | Feb 2012 | A1 |
| 20120036079 | Sushil et al. | Feb 2012 | A1 |
| 20120036178 | Gavini et al. | Feb 2012 | A1 |
| 20120046958 | Pynadath | Feb 2012 | A1 |
| 20120047008 | Alhadeff et al. | Feb 2012 | A1 |
| 20120053987 | Satyavolu et al. | Mar 2012 | A1 |
| 20120059701 | Van Der Veen et al. | Mar 2012 | A1 |
| 20120066037 | Glen | Mar 2012 | A1 |
| 20120066046 | Satyavolu et al. | Mar 2012 | A1 |
| 20120066050 | Satyavolu et al. | Mar 2012 | A1 |
| 20120066051 | Black et al. | Mar 2012 | A1 |
| 20120066062 | Yoder et al. | Mar 2012 | A1 |
| 20120072270 | Waylonis et al. | Mar 2012 | A1 |
| 20120078689 | Rothschild | Mar 2012 | A1 |
| 20120101881 | Taylor et al. | Apr 2012 | A1 |
| 20120109751 | Binenstock et al. | May 2012 | A1 |
| 20120150740 | Isaacson et al. | Jun 2012 | A1 |
| 20120197707 | Cohagan | Aug 2012 | A1 |
| 20120203604 | Baker et al. | Aug 2012 | A1 |
| 20120203846 | Hull et al. | Aug 2012 | A1 |
| 20120209672 | Winner et al. | Aug 2012 | A1 |
| 20120209695 | Winner et al. | Aug 2012 | A1 |
| 20120209696 | Winner et al. | Aug 2012 | A1 |
| 20120209771 | Winner et al. | Aug 2012 | A1 |
| 20120220308 | Ledlie | Aug 2012 | A1 |
| 20120221437 | Yoo | Aug 2012 | A1 |
| 20120221479 | Schneck et al. | Aug 2012 | A1 |
| 20120226530 | Gebb et al. | Sep 2012 | A1 |
| 20120239479 | Amaro et al. | Sep 2012 | A1 |
| 20120278127 | Kirakosyan et al. | Nov 2012 | A1 |
| 20120296724 | Faro et al. | Nov 2012 | A1 |
| 20120303425 | Katzin et al. | Nov 2012 | A1 |
| 20120303430 | Tiku et al. | Nov 2012 | A1 |
| 20130013396 | Vinson et al. | Jan 2013 | A1 |
| 20130024256 | Wolf et al. | Jan 2013 | A1 |
| 20130040654 | Parish | Feb 2013 | A1 |
| 20130041902 | Swann et al. | Feb 2013 | A1 |
| 20130060623 | Walker et al. | Mar 2013 | A1 |
| 20130073336 | Heath | Mar 2013 | A1 |
| 20130073361 | Silver | Mar 2013 | A1 |
| 20130073366 | Heath | Mar 2013 | A1 |
| 20130073371 | Bosworth et al. | Mar 2013 | A1 |
| 20130073374 | Heath | Mar 2013 | A1 |
| 20130073376 | Heath | Mar 2013 | A1 |
| 20130073377 | Heath | Mar 2013 | A1 |
| 20130073387 | Heath | Mar 2013 | A1 |
| 20130073388 | Heath | Mar 2013 | A1 |
| 20130073389 | Heath | Mar 2013 | A1 |
| 20130073400 | Heath | Mar 2013 | A1 |
| 20130073473 | Heath | Mar 2013 | A1 |
| 20130073568 | Federov et al. | Mar 2013 | A1 |
| 20130091000 | Hagey et al. | Apr 2013 | A1 |
| 20130103472 | Burgess et al. | Apr 2013 | A1 |
| 20130110604 | Rooke et al. | May 2013 | A1 |
| 20130124283 | Kaulbach | May 2013 | A1 |
| 20130132175 | Claessen et al. | May 2013 | A1 |
| 20130132183 | Klein et al. | May 2013 | A1 |
| 20130151602 | McClelland et al. | Jun 2013 | A1 |
| 20130173320 | Bank et al. | Jul 2013 | A1 |
| 20130173478 | Farhi | Jul 2013 | A1 |
| 20130178280 | Ganz | Jul 2013 | A1 |
| 20130179246 | Ross et al. | Jul 2013 | A1 |
| 20130191195 | Carlson et al. | Jul 2013 | A1 |
| 20130212177 | Friedman | Aug 2013 | A1 |
| 20130218653 | Rooke et al. | Aug 2013 | A1 |
| 20130238412 | Boncyk et al. | Sep 2013 | A1 |
| 20130246146 | Fischer et al. | Sep 2013 | A1 |
| 20130246185 | Hardman et al. | Sep 2013 | A1 |
| 20130260727 | Knudson et al. | Oct 2013 | A1 |
| 20130262209 | Boyer | Oct 2013 | A1 |
| 20130268333 | Ovick et al. | Oct 2013 | A1 |
| 20130275192 | Aissa | Oct 2013 | A1 |
| 20130304563 | Haupt et al. | Nov 2013 | A1 |
| 20130325946 | Allison, Jr. et al. | Dec 2013 | A1 |
| 20140006129 | Heath | Jan 2014 | A1 |
| 20140006132 | Barker | Jan 2014 | A1 |
| 20140025451 | Knowles et al. | Jan 2014 | A1 |
| 20140025452 | Knowles et al. | Jan 2014 | A1 |
| 20140025453 | Knowles et al. | Jan 2014 | A1 |
| 20140025460 | Knowles et al. | Jan 2014 | A1 |
| 20140046744 | Hagey | Feb 2014 | A1 |
| 20140046748 | Nagarajan et al. | Feb 2014 | A1 |
| 20140108108 | Artman et al. | Apr 2014 | A1 |
| 20140164199 | Wilkes | Jun 2014 | A1 |
| 20150039393 | Jain | Feb 2015 | A1 |
| 20150170256 | Pettyjohn | Jun 2015 | A1 |
| 20150248702 | Chatterton | Sep 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 0186378 | Nov 2001 | WO |
| 2012024109 | Feb 2012 | WO |
| 2012106114 | Aug 2012 | WO |
| 2012170088 | Dec 2012 | WO |
| 2013015846 | Jan 2013 | WO |
| 2014106207 | Jul 2014 | WO |
| 2015102889 | Jul 2015 | WO |
| 2015134947 | Sep 2015 | WO |
| Entry |
|---|
| USPTO; Final Office Action dated Apr. 11, 2011 in U.S. Appl. No. 12/857,389. |
| USPTO; Final Office Action dated Apr. 5, 2011 in U.S. Appl. No. 12/857,424. |
| Todorova, Aleksandra, “The Best Rewards Programs,” www.smartmoney.com, Sep. 2005, pp. 1-2. |
| Todorova, Aleksandra, “Capital One Tests a New Type of Debit Card,” www.smartmoney.com, Jun. 2007, pp. 1-2. |
| Nickel, “Citi Thank You Redemptions: No Thanks,” www.fivecentnickel.com, Sep. 2005. |
| www.americanexpress.com/gift Feb. 25, 2005. |
| USPTO; Office Action dated Nov. 26, 2010 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Nov. 26, 2010 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Apr. 30, 2010 in U.S. Appl. No. 11/779,737. |
| USPTO; Advisory Action dated Jan. 6, 2011 in U.S. Appl. No. 11/779,737. |
| USPTO; Final Office Action dated Oct. 15, 2010 in U.S. Appl. No. 11/779,737. |
| USPTO; Advisory Action dated Jul. 11, 2011 in U.S. Appl. No. 12/857,389. |
| USPTO; Advisory Action dated Jul. 11, 2011 in U.S. Appl. No. 12/857,424. |
| PCT; International Search Report and Written Opinion dated Nov. 27, 2011 in Application No. PCT/US2011/047012. |
| USPTO; Office Action dated Nov. 10, 2011 in U.S. Appl. No. 13/153,890. |
| USPTO; Final Office Action dated Apr. 5, 2012 in U.S. Appl. No. 13/153,890. |
| PCT; International Search Report and Written Opinion dated Jun. 19, 2012 in Application No. PCT/US2012/027810. |
| PCT; International Search Report and Written Opinion dated Jul. 6, 2012 in Application No. PCT/US2012/027664. |
| PCT; International Search Report and Written Opinion dated May 8, 2012 in Application No. PCT/US2012/021648. |
| USPTO; Office Action dated Nov. 15, 2012 in U.S. Appl. No. 13/443,100. |
| USPTO; Advisory Action dated Nov. 23, 2012 in U.S. Appl. No. 13/466,412. |
| International Preliminary Report on Patentability dated Dec. 7, 2012 in Application No. PCT/US2011/047012. |
| USPTO; Office Action dated Aug. 3, 2012 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Aug. 17, 2012 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Aug. 30, 2012 in U.S. Appl. No. 13/188,693. |
| USPTO; Office Action dated Aug. 30, 2012 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Sep. 6, 2012 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Sep. 14, 2012 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Sep. 17, 2012 in U.S. Appl. No. 13/021,237. |
| USPTO; Office Action dated Oct. 9, 2012 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Oct. 19, 2012 in U.S. Appl. No. 13/411,281. |
| USPTO; Office Action dated Oct. 12, 2012 in U.S. Appl. No. 13/439,768. |
| USPTO; Final Office Action dated Oct. 12, 2012 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Oct. 15, 2012 in U.S. Appl. No. 13/594,528. |
| USPTO; Office Action dated Oct. 18, 2012 in U.S. Appl. No. 13/593,204. |
| Dan Oshinsky, “Jet Blue's $1 Million Twitter Hashtag,” Aug. 18, 2010, 4 pages, retrieved from: http://danoshinsky.com/2010/08/18/a-social-media-case-study-jetblue-vs-sun-country/. |
| www.americanexpress.com/gift/faq from Feb. 25, 2005, 2 pages. |
| USPTO; Office Action dated Sep. 23, 2013 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Oct. 4, 2013 in U.S. Appl. No. 13/468,880. |
| USPTO; Advisory Action dated Oct. 7, 2013 in U.S. Appl. No. 12/857,424. |
| USPTO; Final Office Action dated Oct. 30, 2013 in U.S. Appl. No. 11/779,734. |
| USPTO; Restriction Requirement dated Oct. 30, 2013 in U.S. Appl. No. 13/889,288. |
| USPTO; Final Office Action dated Oct. 31, 2013 in U.S. Appl. No. 13/889,305. |
| USPTO; Advisory Action dated Nov. 5, 2013 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Nov. 5, 2013 in U.S. Appl. No. 13/889,285. |
| USPTO; Office Action dated Nov. 6, 2013 in U.S. Appl. No. 13/889,272. |
| USPTO; Office Action dated Jul. 19, 2013 in U.S. Appl. No. 13/715,423. |
| USPTO; Office Action dated Aug. 14, 2013 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Aug. 14, 2013 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Aug. 26, 2013 in U.S. Appl. No. 13/889,305. |
| USPTO; Office Action dated Aug. 27, 2013 in U.S. Appl. No. 13/889,285. |
| USPTO; Final Office Action dated Aug. 28, 2013 in U.S. Appl. No. 13/443,100. |
| USPTO; Office Action dated May 23, 2013 in U.S. Appl. No. 13/734,693. |
| International Preliminary Report on Patentability dated on May 23, 2013 in Application No. PCT/US2012/027810. |
| USPTO; Advisory Action dated Jun. 6, 2013 in U.S. Appl. No. 13/466,445. |
| International Preliminary Report on Patentability dated on Jun. 28, 2013 in Application No. PCT/US2012/027664. |
| USPTO; Office Action dated Nov. 22, 2013 in U.S. Appl. No. 13/889,299. |
| USPTO; Final Office Action dated Nov. 26, 2013 in U.S. Appl. No. 13/734,693. |
| USPTO; Notice of Allowance dated Dec. 17, 2013 in U.S. Appl. No. 13/594,528. |
| USPTO; Office Action dated Jan. 3, 2014 in U.S. Appl. No. 13/889,288. |
| USPTO; Advisory Action dated Jan. 14, 2014 in U.S. Appl. No. 13/889,285. |
| USPTO; Office Action dated Jan. 15, 2014 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Jan. 29, 2014 in U.S. Appl. No. 13/889,307. |
| USPTO; Office Action dated Jan. 30, 2014 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Feb. 3, 2014 in U.S. Appl. No. 13/593,204. |
| International Preliminary Report on Patentability dated on Feb. 3, 2014 in Application No. PCT/US2013/028209. |
| USPTO; Advisory Action dated Feb. 5, 2014 in U.S. Appl. No. 13/734,693. |
| USPTO; Final Office Action dated Feb. 11, 2014 in U.S. Appl. No. 13/715,423. |
| USPTO; Office Action dated Feb. 12, 2014 in U.S. Appl. No. 13/468,931. |
| Golson, “Major League Baseball Rolling out Thousands of iBeacons for Opening Day,” Jan. 30, 2014, pp. 2-3, retrieved from http://www.macrumors.com/2014/01/30/mlb-ibeacon-rollout/ on Feb. 12, 2014. |
| D Arthur, S Vassilvitskii , “k-means++: The advantages of careful seeding”, Proceedings of the eighteenth annual ACM-SIAM symposium on Discrete algorithms, pp. 1027-1035, 2007, dl.acm.org. |
| AK Jain, “Data clustering: 50 years beyond K-means”, Pattern Recognition Letters, 2010, pp. 1-33, Elsevier. |
| K-means++ Wikipedia Page, pp. 1-4, page last modified on Nov. 18, 2013, http://en.wikipedia.org/wiki/K-means++ retrieved from the web Nov. 21, 2013. |
| USPTO; Final Office Action dated Mar. 6, 2013 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Jan. 7, 2013 in U.S. Appl. No. 13/467,503. |
| USPTO; Final Office Action dated Jan. 7, 2013 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Jan. 10, 2013 in U.S. Appl. No. 13/468,931. |
| USPTO; Final Office Action dated Jan. 31, 2013 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Jan. 31, 2013 in U.S. Appl. No. 13/467,910. |
| USPTO; Final Office Action dated Feb. 14, 2013 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Jan. 4, 2013 in U.S. Appl. No. 13/593,204. |
| USPTO; Final Office Action dated Mar. 1, 2013 in U.S. Appl. No. 13/439,768. |
| USPTO; Final Office Action dated Mar. 4, 2013 in U.S. Appl. No. 13/594,528. |
| USPTO; Advisory Action dated May 22, 2013 in U.S. Appl. No. 13/188,693. |
| USPTO; Advisory Action dated Mar. 15, 2013 in U.S. Appl. No. 13/593,204. |
| USPTO; Advisory Action dated Mar. 18, 2013 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Mar. 19, 2013 in U.S. Appl. No. 13/021,237. |
| USPTO; Advisory Action dated Mar. 19, 2013 in U.S. Appl. No. 13/468,931. |
| International Search Report and Written Opinion dated Mar. 22, 2013 in Application No. PCT/2013/028209. |
| USPTO; Advisory Action dated Mar. 28, 2013 in U.S. Appl. No. 13/411,281. |
| USPTO; Office Action dated Apr. 11, 2013 in U.S. Appl. No. 12/857,424. |
| USPTO; Advisory Action dated Apr. 12, 2013 in U.S. Appl. No. 13/467,910. |
| USPTO; Final Office Action dated May 2, 2013 in U.S. Appl. No. 13/468,880. |
| International Preliminary Report on Patentability dated on May 7, 2013 in Application No. PCT/US2012/021648. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/021,237. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Feb. 26, 2014 in U.S. Appl. No. 13/889,305. |
| USPTO; Office Action dated Mar. 7, 2014 in U.S. Appl. No. 13/889,285. |
| USPTO; Office Action dated Mar. 11, 2014 in U.S. Appl. No. 13/153,890. |
| USPTO; Final Office Action dated Mar. 13, 2014 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Apr. 25, 2014 in U.S. Appl. No. 13/889,299. |
| USPTO; Final Office Action dated Apr. 28, 2014 in U.S. Appl. No. 13/889,288. |
| USPTO; Advisory Action dated Apr. 30, 2014 in U.S. Appl. No. 13/715,423. |
| USPTO; Final Office Action dated May 5, 2014 in U.S. Appl. No. 13/411,281. |
| International Search Report and Written Opinion dated Dec. 7, 2012 in Application No. PCT/2012/056231. |
| International Preliminary Report on Patentability dated on Aug. 22, 2013 in Application No. PCT/US2012/056231. |
| USPTO; Office Action dated Oct. 11, 2013 in U.S. Appl. No. 13/245,636. |
| USPTO; Office Action dated Feb. 5, 2014 in U.S. Appl. No. 13/245,636. |
| USPTO; Office Action dated Jun. 24, 2014 in U.S. Appl. No. 13/468,880. |
| USPTO; Final Office Action dated May 13, 2014 in U.S. Appl. No. 13/476,910. |
| USPTO; Final Office Action dated May 20, 2014 in U.S. Appl. No. 13/593,204. |
| USPTO; Notice of Allowance dated May 22, 2014 in U.S. Appl. No. 13/245,636. |
| USPTO; Final Office Action dated May 29, 2014 in U.S. Appl. No. 13/468,931. |
| USPTO; Advisory Action dated Jun. 2, 2014 in U.S. Appl. No. 13/889,272. |
| USPTO; Advisory Action dated Jul. 8, 2014 in U.S. Appl. No. 13/889,299. |
| USPTO; Office Action dated Jun. 5, 2014 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 13/467,503. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 12/857,389. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 13/466,412. |
| USPTO; Final Office Action dated Jun. 16, 2014 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Jun. 11, 2014 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Jun. 30, 2014 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Jun. 30, 2014 in U.S. Appl. No. 13/889,305. |
| USPTO; Notice of Allowance dated Jul. 2, 2014 in U.S. Appl. No. 13/889,285. |
| USPTO; Advisory Action dated Jul. 2, 2014 in U.S. Appl. No. 13/889,288. |
| USPTO; Office Action dated Jul. 14, 2014 in U.S. Appl. No. 13/889,307. |
| Examination Report dated Aug. 11, 2014 in New Zealand Application No. 623019. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 13/466,412. |
| USPTO; Advisory Action dated Jul. 30, 2014 in U.S. Appl. No. 13/411,281. |
| USPTO; Office Action dated Jul. 30, 2014 in U.S. Appl. No. 13/794,301. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Aug. 7, 2014 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Oct. 20, 2014 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated Aug. 13, 2014 in U.S. Appl. No. 13/153,890. |
| USPTO; Office Action dated Aug. 14, 2014 in U.S. Appl. No. 13/794,145. |
| USPTO; Office Action dated Aug. 14, 2014 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Aug. 15, 2014 in U.S. Appl. No. 13/794,374. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 13/021,237. |
| USPTO; Office Action dated Oct. 17, 2014 in U.S. Appl. No. 11/779,734. |
| USPTO; Advisory Action dated Sep. 3, 2014 in U.S. Appl. No. 12/857,389. |
| USPTO; Advisory Action dated Jul. 30, 2014 in U.S. Appl. No. 13/593,204. |
| USPTO; Advisory Action dated Sep. 5, 2014 in U.S. Appl. No. 13/889,305. |
| USPTO; Office Action dated Sep. 17, 2014 in U.S. Appl. No. 13/794,226. |
| USPTO; Office Action dated Oct. 8, 2014 in U.S. Appl. No. 13/734,693. |
| USPTO; Office Action dated Oct. 3, 2014 in U.S. Appl. No. 12/857,424. |
| USPTO; Advisory Action dated Sep. 2, 2014 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Oct. 9, 2014 in U.S. Serial No. 13/926,789. |
| USPTO; Advisory Action dated Jul. 31, 2014 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Oct. 17, 2014 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Oct. 23, 2014 in U.S. Appl. No. 13/715,770. |
| USPTO; Advisory Action dated Oct. 24, 2014 in U.S. Appl. No. 13/153,890. |
| USPTO; Office Action dated Oct. 29, 2014 in U.S. Appl. No. 13/926,884. |
| USPTO; Office Action dated Oct. 29, 2014 in U.S. Appl. No. 13/926,895. |
| USPTO; Office Action dated Nov. 7, 2014 in U.S. Appl. No. 13/715,792. |
| USPTO; Office Action dated Nov. 7, 2014 in U.S. Appl. No. 13/715,423. |
| USPTO; Office Action dated Dec. 29, 2014 in U.S. Appl. No. 13/188,693. |
| USPTO; Office Action dated Jan. 9, 2015 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Jan. 16, 2015 in U.S. Appl. No. 13/889,299. |
| USPTO; Final Office Action dated Jan. 28, 2015 in U.S. Appl. No. 13/889,307. |
| USPTO; Final Office Action dated Jan. 30, 2015 in U.S. Appl. No. 13/794,301. |
| USPTO; Final Office Action dated Feb. 11, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Final Office Action dated Feb. 13, 2015 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Feb. 26, 2015 in U.S. Appl. No. 13/941,306. |
| USPTO; Office Action dated Feb. 27, 2015 in U.S. Appl. No. 13/443,100. |
| USPTO; Office Action dated Mar. 2, 2015 in U.S. Appl. No. 13/686,608. |
| USPTO; Final Office Action dated Mar. 13, 2015 in U.S. Appl. No. 13/794,374. |
| USPTO; Final Office Action dated Mar. 23, 2015 in U.S. Appl. No. 13/926,789. |
| Search Report and Written Opinion dated Feb. 16, 2015 in Singapore Application No. 11201400788P. |
| Written Opinion dated Aug. 5, 2015 in Singapore Application No. 11201400788P. |
| USPTO; Advisory Action dated Sep. 29, 2015 in U.S. Appl. No. 13/686,608. |
| USPTO; Notice of Allowance dated Sep. 29, 2015 in U.S. Appl. No. 13/715,792. |
| USPTO; Office Action dated Oct. 8, 2015 in U.S. Appl. No. 13/941,306. |
| USPTO; Advisory Action dated Oct. 13, 2015 in U.S. Appl. No. 13/021,237. |
| USPTO; Advisory Action dated Oct. 16, 2015 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Oct. 16, 2015 in U.S. Appl. No. 13/443,100. |
| USPTO; Advisory Action dated Oct. 22, 2015 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Oct. 26, 2015 in U.S. Appl. No. 13/476,910. |
| USPTO; Final Office Action dated Oct. 26, 2015 in U.S. Appl. No. 13/467,503. |
| USPTO; Advisory Action dated Nov. 17, 2015 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Nov. 17, 2015 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Feb. 1, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Feb. 2, 2016 in U.S Appl. No. 13/926,789. |
| USPTO; Final Office Action dated Feb. 2, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated Feb. 9, 2016 in U.S. Appl. No. 13/794,374. |
| USPTO; Final Office Action dated Feb. 9, 2016 in U.S. Appl. No. 13/794,272. |
| USPTO; Final Office Action dated Feb. 11, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Final Office Action dated Feb. 11, 2016 in U.S. Appl. No. 13/926,884. |
| USPTO; Final Office Action dated Feb. 12, 2016 in U.S Appl. No. 13/926,895. |
| USPTO; Office Action dated Feb. 12, 2016 in U.S. Appl. No. 13/593,204. |
| USPTO; Office Action dated Feb. 19, 2016 in U.S. Appl. No. 13/468,931. |
| Office Action dated Feb. 29, 2016 in Canadian Application No. 2,874,582. |
| USPTO; Office Action dated Feb. 29, 2016 in U.S. Appl. No. 13/686,608. |
| USPTO; Office Action dated Mar. 4, 2016 in U.S. Appl. No. 13/466,412. |
| USPTO; Office Action dated Mar. 4, 2016 in U.S. Appl. No. 13/794,226. |
| USPTO; Office Action dated Mar. 7, 2016 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Mar. 17, 2016 in U.S. Appl. No. 13/889,305. |
| USPTO; Advisory Action dated Mar. 18, 2016 in U.S. Appl. No. 13/439,768. |
| USPTO; Advisory Action dated Mar. 18, 2016 in U.S. Appl. No. 13/411,281. |
| USPTO; Advisory Action dated Mar. 25, 2016 in U.S. Appl. No. 13/794,301. |
| USPTO; Advisory Action dated Mar. 28, 2016 in U.S. Appl. No. 14/065,883. |
| White, “Deals as Debit Rewards? Bank of America Brings Back Debit Card Rewards With a Twist,” Jan. 25, 2012, 2 pages, retrieved from http://moneyland.time.com/2012/01/25/deals-as-debit-rewards-bank-of-america-brings-back-debit-card-rewards-with-a-twist/. |
| Owen, et al., “Improving the Value and Performance of Online Offers,” A First Data White Paper, First Data Corporation, 2012, 10 pages. |
| Noyes, “Card-Linked Offers Update,” Transaction World Magazine, Jul. 2012, 2 pages. |
| USPTO; Advisory Action dated Jun. 15, 2015 in U.S. Appl. No. 13/715,770. |
| USPTO; Office Action dated Jun. 19, 2015 in U.S. Appl. No. 13/794,301. |
| USPTO; Office Action dated Jun. 25, 2015 in U.S. Appl. No. 13/889,307. |
| USPTO; Advisory Action dated Jun. 25, 2015 in U.S. Appl. No. 13/734,693. |
| USPTO; Advisory Action dated Jun. 26, 2015 in U.S. Appl. No. 13/794,145. |
| USPTO; Advisory Action dated Jun. 29, 2015 in U.S. Appl. No. 13/715,792. |
| USPTO; Office Action dated Jul. 10, 2015 in U.S. Appl. No. 13/794,374. |
| USPTO; Advisory Action dated Jul. 10, 2015 in U.S. Appl. No. 12/857,424. |
| USPTO; Office Action dated Jul. 10, 2015 in U.S. Appl. No. 13/411,281. |
| USPTO; Final Office Action dated Jul. 17, 2015 in U.S. Appl. No. 13/188,693. |
| USPTO; Final Office Action dated Jul. 20, 2015 in U.S. Appl. No. 13/686,608. |
| USPTO; Advisory Action dated Jul. 21, 2015 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Jul. 23, 2015 in U.S. Appl. No. 13/466,445. |
| USPTO; Office Action dated Aug. 4, 2015 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Aug. 5, 2015 in U.S. Appl. No. 13/926,789. |
| USPTO; Final Office Action dated Aug. 5, 2015 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Aug. 7, 2015 in U.S. Appl. No. 13/889,299. |
| USPTO; Office Action dated Aug. 11, 2015 in U.S. Appl. No. 13/926,895. |
| USPTO; Final Office Action dated Aug. 12, 2015 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Aug. 17, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Aug. 17, 2015 in U.S. Appl. No. 13/439,768. |
| USPTO; Office Action dated Aug. 19, 2015 in U.S. Appl. No. 13/926,884. |
| USPTO; Office Action dated Aug. 28, 2015 in U.S. Appl. No. 13/794,272. |
| Examination Report dated Mar. 24, 2015 in Australian Application No. 2012316453. |
| USPTO; Advisory Action dated Jun. 3, 2015 in U.S. Appl. No. 13/794,226. |
| Tang, “Approac to detection of community's consensus and interest,” Institute of Systems Science, 2008, Springer-Verlag, pp. 17-29. |
| USPTO; Office Action dated Mar. 27, 2015 in U.S. Appl. No. 13/466,445. |
| USPTO; Final Office Action dated Apr. 3, 2015 in U.S. Appl. No. 13/926,884. |
| USPTO; Final Office Action dated Apr. 3, 2015 in U.S. Appl. No. 13/715,770. |
| USPTO; Final Office Action dated Apr. 7, 2015 in U.S. Appl. No. 13/926,895. |
| USPTO; Advisory Action dated Apr. 8, 2015 in U.S. Appl. No. 13/794,301. |
| USPTO; Office Action dated Apr. 8, 2015 in U.S. Appl. No. 13/021,237. |
| USPTO; Final Office Action dated Apr. 8, 2015 in U.S. Appl. No. 13/794,145. |
| USPTO; Final Office Action dated Apr. 13, 2015 in U.S. Appl. No. 13/734,693. |
| USPTO; Advisory Action dated Apr. 17, 2015 in U.S. Appl. No. 13/889,307. |
| USPTO; Final Office Action dated Apr. 17, 2015 in U.S. Appl. No. 13/715,792. |
| USPTO; Advisory Action dated Apr. 23, 2015 in U.S. Appl. No. 13/794,334. |
| USPTO; Advisory Action dated Apr. 23, 2015 in U.S. Appl. No. 14/065,883. |
| USPTO; Final Office Action dated Apr. 30, 2015 in U.S. Appl. No. 12/857,424. |
| Notice of Acceptance dated May 8, 2015 in New Zealand Application No. 623019. |
| USPTO; Advisory Action dated May 8, 2015 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated May 13, 2015 in U.S. Appl. No. 11/779,734. |
| USPTO; Office Action dated May 19, 2015 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated May 28, 2015 in U.S. Appl. No. 13/467,503. |
| Lee et al., “iJADE eMiner—A Web Based Mining Agent Based on Intelligent Java Agent Development Environment (iJADE) on Internet Shopping,” Advances in Knowledge Discovery and Data Mining, 2001, Springer-Verlag, pp. 28-40. |
| USPTO; Advisory Action dated Jun. 3, 2015 in U.S. Appl. No. 13/794,374. |
| USPTO; Final Office Action dated Mar. 25, 2015 in U.S. Appl. No. 13/794,226. |
| USPTO; Advisory Action dated Jun. 11, 2015 in U.S. Appl. No. 13/926,789. |
| Burke, “Hybrid Recommender Systems: Survey and Experiments,” User modeling and user-adapted interaction, 2002, Kluwer Academic Publishers, pp. 331-370. |
| Aimeur et al., “Alambic: a privacy-preserving recommender system for electronic commerce,” Feb. 27, 2008, Springer-Verlag, pp. 307-334. |
| USPTO; Office Action dated Dec. 4, 2015 in U.S. Appl. No. 13/794,145. |
| USPTO; Office Action dated Dec. 17, 2015 in U.S. Appl. No. 13/715,770. |
| USPTO; Office Action dated Dec. 31, 2015 in U.S. Appl. No. 13/734,693. |
| USPTO; Final Office Action dated Dec. 30, 2015 in U.S Appl. No. 14/065,883. |
| USPTO; Advisory Action dated Jan. 6, 2016 in U.S. Appl. No. 13/443,100. |
| USPTO; Final Office Action dated Jan. 11, 2016 in U.S Appl. No. 13/411,281. |
| USPTO; Advisory Action dated Jan. 11, 2016 in U.S. Appl. No. 13/467,503. |
| USPTO; Office Action dated Jan. 14, 2016 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Jan. 14, 2016 in U.S Appl. No. 13/794,301. |
| USPTO; Office Action dated Jan. 15, 2016 in U.S. Appl. No. 13/889,299. |
| USPTO; Advisory Action dated Jan. 15, 2016 in U.S. Appl. No. 13/476,910. |
| USPTO; Office Action dated Jan. 20, 2016 in U.S. Appl. No. 13/889,307. |
| Pashtan, et al., “Personal Service Areas for Mobile Web Applications,” IEEE Internet Computing, 2004, ieeexplore.ieee.org, 7 pages. |
| Pandey, et al., “Exploiting User Profiles to Support Differentiated Services in Next-Generation Wireless Networks,” Network, IEEE, 2004, ieeexplore.ieee.org, 23 pages. |
| Liapis, et al., Implementing a Low-Cost, Personalized and Location Based Service for Delivering Advertisements to Mobile Users, Athens Information Technology, Oct. 2008, ieeexplore.ieee.org, 49 pages. |
| Park, et al, “Location-Based Recommendation System using Bayesian User's Preference Model in Mobile Devices,” Ubiquitous Intelligence and Computing, 2007, Springer-Verlag Berlin Heidelberg, 10 pages. |
| Office Action dated Oct. 26, 2015 in Canadian Application No. 2,863,576. |
| Notice of Acceptance dated Nov. 30, 2015 in Australian Application No. 2012316453. |
| Office Action dated Dec. 10, 2015 in Canadian Application No. 2,849,271. |
| USPTO; Office Action dated Jun. 3, 2016 in U.S. Appl. No. 14/065,883. |
| USPTO; Office Action dated Jun. 3, 2016 in U.S. Appl. No. 12/857,424. |
| USPTO; Notice of Allowance dated Jun. 3, 2016 in U.S. Appl. No. 13/593,204. |
| USPTO; Final Office Action dated Jun. 8, 2016 in U.S. Appl. No. 12/857,389. |
| USPTO; Office Action dated Jun. 9, 2016 in U.S. Appl. No. 13/926,895. |
| USPTO; Final Office Action dated Jun. 10, 2016 in U.S. Appl. No. 13/466,412. |
| USPTO; Final Office Action dated Jun. 13, 2016 in U.S. Appl. No. 13/468,931. |
| USPTO; Final Office Action dated Jun. 15, 2016 in U.S. Appl. No. 13/686,608. |
| USPTO; Office Action dated Jun. 17, 2016 in U.S. Appl. No. 13/468,880. |
| USPTO; Office Action dated Jun. 17, 2016 in U.S. Appl. No. 13/941,306. |
| USPTO; Final Office Action dated Jun. 17, 2016 in U.S. Appl No. 13/794,145. |
| USPTO; Advisory Action dated Jun. 24, 2016 in U.S. Appl. No. 13/715,770. |
| USPTO; Final Office Action dated Jul. 1, 2016 in U.S. Appl. No. 13/794,226. |
| USPTO; Final Office Action dated Jul. 5, 2016 in U.S Appl. No. 13/889,305. |
| USPTO; Advisory Action dated Jul. 6, 2016 in U.S. Appl. No. 13/468,931. |
| USPTO; Office Action dated Jul. 7, 2016 in U.S. Appl. No. 14/284,817. |
| USPTO; Notice of Allowance dated Jul. 13, 2016 in U.S. Appl. No. 11/779,734. |
| USPTO; Final Office Action dated Jul. 28, 2016 in U.S. Appl. No. 13/889,272. |
| USPTO; Final Office Action dated Aug. 12, 2016in U.S. Appl. No. 13/889,299. |
| “What is a token in programming?” Quora, pp. 1-3, retrieved from https://www.quora.com/What-is-a-token-in-programming on May 31, 2016. |
| Examination Report dated Feb. 26, 2016 in Australian Application No. 2015201925. |
| USPTO; Office Action dated Mar. 31, 2016 in U.S. Appl. No. 13/889,288. |
| USPTO; Final Office Action dated Apr. 14, 2016 in U.S Appl. No. 13/715,770. |
| Ricci, et al.; “Recommendation and Personalization in eCommerce”, Proceedings of the AH'2002 Workshop on Recommendation and Personalization in eCommerce, Malaga, Spain, May 28, 2002, pp. 1-160. |
| Ghose, et al., “Opinion Mining using Econometrics: A case study on Reputation Systems”, Department of Information, Operations, and Management Sciences, Annual Meeting, 2007. |
| USPTO; Notice of Allowance dated Apr. 18, 2016 in U.S Appl. No. 13/734,693. |
| USPTO; Advisory Action dated Apr. 15, 2016 in U.S. Appl. No. 13/926,789. |
| USPTO; Advisory Action dated Apr. 21, 2016 in U.S. Appl. No. 13/794,272. |
| Office Action dated Apr. 25, 2016 in Canadian Application No. 2,888,085. |
| USPTO; Advisory Action dated May 21, 2016 in U.S. Appl. No. 13/926,884. |
| USPTO; Advisory Action dated May 2, 2016 in U.S. Appl. No. 13/794,334. |
| USPTO; Office Action dated Apr. 15, 2016 in U.S. Appl. No. 13/188,693. |
| USPTO; Office Action dated May 19, 2016 in U.S. Appl. No. 13/926,895. |
| USPTO; Notice of Allowance dated May 25, 2016 in U.S Appl. No. 13/439,768. |
| Pang, et al., “Opinion mining and sentiment analysis”, Foundations and trends in information retrieval, vol. 2, No. 1-2 ,(2008)1-135. |
| Pavlovic, “Dynamics, robustness and fragility of trust”, Formal Aspects in Secruity and Trust, 2009—Springer. |
| Resnick, et al., “Recommender Systems”, Mar. 1997, Communications of the ACM, vol. 40,No. 3, pp. 56-58. |
| USPTO; Advisory Action dated Apr. 22, 2016 in U.S. Appl. No. 13/794,374. |
| Number | Date | Country | |
|---|---|---|---|
| 20120232982 A1 | Sep 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60831457 | Jul 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13153890 | Jun 2011 | US |
| Child | 13477806 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12857389 | Aug 2010 | US |
| Child | 13153890 | US | |
| Parent | 11779734 | Jul 2007 | US |
| Child | 12857389 | US |
