Patent Grant
10650398
At least some embodiments disclosed in the present application relate to distributed computing with a communication system connecting a plurality of separate computer systems in general and more particularly but not limited to a communication method and system configured with separate resources on different computers for benefit redemption.
In a system having multiple computer systems connected via one or more computer networks, different portions of computing resources for processing a task may reside in different computer systems. The use of a predetermined communication protocol allows the computer systems to communicate with each other in a predetermined way to utilize the resources that are distributed among the computer systems for the processing of the task. Improvements to the communication protocol can improve the performance of the system as a whole and/or improve the functionalities of the system as a whole. In some instances, improvements to the communication protocol can improve the performance of some of the individual computer systems and/or improve the functionalities of the individual computer systems.
For example, a typical electronic payment processing system may include individual computing systems such as a transaction handler, one or more issuer processors, one or more acquirer processors, and transaction terminals. The individual computing systems in the electronic payment processing system are generally connected via one or more computer networks. Resources for processing a payment from a consumer to a merchant are typically distributed among the computing systems connected via computer networks.
For example, a typical transaction terminal of a merchant is configured with the resources to obtain consumer account identification information of a consumer to initiate a transaction message and communicate the transaction message to an acquirer processor for processing; a typical merchant account is controlled by an acquirer processor; a typical consumer account is controlled by an issuer processor; the transaction handler of the electronic payment processing system interconnects the acquirer processors and the issuer processors and has the resources to route messages from acquirer processors to responsible issuers processors based on consumer account identification information and route messages from issuer processors to responsible acquirer processors based on identification information of merchant accounts.
U.S. Pat. App. Pub. No. 2011/0087530, for example, discloses a data structure for a communication protocol in an electronic payment processing system, in which the data field for the message type identifier in a transaction message is extended to accommodate an identifier for crediting reward and an identifier for redeeming reward. As a result, the communication protocol is extended to process not only payment transactions in financial currencies, but also the crediting and redeeming of reward benefits.
The entire disclosures of the above discussed patent documents are hereby incorporated herein by reference.
The embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.
In one embodiment, a system and method is configured to process reward redemption using an electronic payment processing network without changing the communication protocol used for payment processing within the electronic payment processing network.
For example, the computing systems in
The computing system in
In
In
To facilitate the reward redemption, the portal (143) is provided to communicate with the transaction terminal (105), the reward host (513) and the issuer processor (145) to set up accounts for payment processing during balance inquiry and to process reward redemption during authorization of payments made using the account numbers (557), as further discussed below.
In one embodiment, the portal (143) of
After the registration data associating the user ID (551) with the identification of the reward account (525) is stored in the data warehouse (149) of the portal (143), the portal (143) may process the reward redemption operations in response to the user ID (551).
For example, when the transaction terminal (105) receives the user ID (551) from a user to process a purchase, the transaction terminal (105) transmits to the portal (143) a reward balance inquiry (503) that identifies the user ID (551).
Based on the registration data associating the user ID (551) with the identification of the reward account (525), the portal (143) of
Further, the portal (143) performs an account setup communication (515) with a predetermined issuer processor (145) to obtain an account number (509), selected from a plurality of account numbers (557) controlled by the issuer processor (145), for the reward transaction that is predicted to follow the reward balance inquiry (503).
As a response to the reward balance inquiry (503), the portal (143) stores data associating the account number (509) with the reward account (525) identified by the user ID (551) and transmits the balance response (505) to the transaction terminal (105). The balance response (505) illustrated in
For example, after obtaining the balance response (505), the transaction terminal (105) may present the reward balance (507) to the user of the user ID (551) and present a user interface that allows the user to request the redemption of a portion of the reward balance (507), or the reward balance (507) in its entirety.
Upon receiving the user instructions to redeem rewards consistent with the reward balance (507), the transaction terminal (105) performs an authorization communication (517) with the acquirer processor (147) using the account number (509). The authorization communication (517) includes an authorization request transmitted to the acquirer processor (147) for propagation, via the transaction handler (103), to the issuer processor (145) identified by the account number (509), and an authorization response propagated back from the issuer processor (145), via the transaction handler (103) and acquirer processor (147), to the transaction terminal (105).
In one embodiment, the authorization communication (517) is in compliance with existing communication standard for payment transactions in the electronic payment processing network, such as a payment transaction made in consumer account (146)
In
In
For example, the reward redemption operations may include the rewards host (513) reserving the portion of the redeemed rewards for subsequent settlement. For example, the reward redemption operations may include the rewards host (513) removing the redeemed rewards from the reward account (525) to hold the redeemed rewards for pending settlement.
The result of the redemption operations is propagated from the reward host (513) to the issuer processor (145) via the portal (143) using the redemption communication (521) and the reward redemption communication (519). Based on the result, the issuer processor (145) generates the authorization response for the payment transaction requested using the account number (509), approving or rejecting the payment transaction.
During settlement of the payment transaction, the issue processor (145) provides the funds according to the payment transaction to the merchant account (148) controlled by the acquirer processor (147); and the reward host (513) provides funds corresponding to aggregated redeemed rewards to the issuer processor (145).
Thus, the system of
For example, a reward redemption platform of one embodiment (e.g., implemented via the portal (143)) is configured to associate a virtual account under control of an issuer processor with a reward account (525) during the balance inquiry (551) of the reward account (525). The account number (509) of the virtual account is provided with the balance (507) of the reward account (525) to the transaction terminal (105), which allows a user to specify a redemption amount that does not exceed the reward balance (505). The transaction terminal (105) than uses the account number (509) provided within the balance result (505) responsive to the balance inquiry (503) to initiate a payment transaction in the virtual account. The issuer processor (145) is configured to communicate with the reward redemption platform (e.g., implemented via the portal (143)) to convert the redeemed rewards to funds for a payment provided by the issuer processor (145) to the acquirer processor (147) of the merchant account (148) via an electronic payment processing network. Thus, the reward transactions can be performed using the electronic payment processing network with minimum impact on the electronic payment processing network.
Thus, the reward redemption platform (e.g., implemented via the portal (143)) allows the redemption of reward benefits (e.g., loyalty rewards, such as loyalty points, miles, virtual currency) to be performed using the payment processing network configured to processing payments in consumer accounts (e.g., 146), without requiring a transaction be made in the consumer payment account using a currency issued by a government.
In one embodiment, virtual accounts or one-time use prepaid accounts are used to manage benefits in the reward accounts such that the reward redemption can be performed as payment transactions in the virtual accounts or one-time use prepaid accounts using the payment processing network.
For example, a reward redemption platform is configured to communicate with an issuer processor to assign a one-time use account for the redemption of reward benefits of a user. The assignment of the virtual account can be performed in response to a balance inquiry in the preparation for reward redemption. For example, in response to a balance inquiry from a merchant's computing system, the one-time use account is assigned and the account number is communicated to the transaction terminal to initiate a payment that is actually funded by the reward benefits. The transaction messages from the transaction terminal, to the issuer processor via the respective acquirer processor and the transaction handler are processed in a way as the processing of messages for a payment transaction in a consumer account (e.g., a credit account, a debit account, a prepaid account, etc.). At the backend, the issuer processor requests helps from the portal in redeeming rewards to support the payment transaction,
The account assigned for benefit redemption may be a one-time account, a virtual account, a prepaid account, a debit account and/or a private label account. For example, the virtual account can be assigned for the redemption of the reward benefits of the user within a predetermined period of time; and after the period of time, the virtual account is no longer valid. In the embodiment, the account is established and/or assigned solely for the redemption of reward benefits; and the account is funded solely by the reward benefits in one or more of the reward accounts of the user.
In one embodiment, the account information of the virtual account is transmitted to a merchant (or the user) in a response to a reward balance inquiry. The balance information allows the user to request the redemption of a valid amount of rewards from the reward account of the user and thus reduces the chance of rejection due to the request of a redemption amount exceeding the balance of the reward account. The account information allows the transaction terminal of the merchant to initiate a payment transaction in the virtual account in the payment processing network without modifications to the transaction terminal of the merchant, and without modifications to the acquirer processor of the merchant. In one embodiment, the payment transaction in the virtual account is performed substantially in the same way as a payment transaction in the consumer account of the user; and arrangements to enable the benefit redemption are discussed below.
In one embodiment, when the transaction request in the virtual account is received in the issuer processor of the virtual account, the issuer processor is configured to communicate with the reward redemption platform for benefit processing in accordance with the information stored to set up the virtual account and/or to assign the virtual account for the redemption of the reward benefits of the user. In response, the reward redemption platform is configured communicate with the host of the reward benefits to reserve, convert, and/or deduct the reward benefits of the user for payment to the merchant.
For example, during the authorization phase of the transaction in the virtual account, the transaction amount for the redemption is specified via an authorization request and in accordance with the reward balance reported by the host of the reward benefits. During the authorization of the transaction in the issuer processor, the issuer processor requests the reward redemption platform to authorize the transaction; and the reward redemption platform communicates with the host of reward benefits to reserve the amount of benefits to be redeemed and provide authorization. During the settlement of the transaction, the issuer processor communicates with the host of reward benefits via the reward redemption platform to deduct the redeemed benefits from the reward account of the user and transmit a payment corresponding to the redeemed benefits to the acquirer processor of the merchant.
In one embodiment, during the balance inquiry, the reward redemption platform and/or the reward host converts the balance to an equivalent account balance of the virtual account in a payment currency issued by a government (e.g., U.S. dollar). Thus, the transaction terminal of the merchant may initiate the payment transaction in the payment currency.
Alternatively, the virtual account may be configured to use a virtual currency corresponding to the reward currency provided by the reward host; and the reward currency is converted to a payment currency issued by a government (e.g., U.S. dollar) during the settlement of the reward redemption transaction; and the transaction initiated on the transaction terminal is specified in the virtual currency.
In one embodiment, when the authorization request is made in the reward currency (e.g., points, miles, virtual currency), the authorization response is configured to specify the transaction amount in a payment currency issued by a government (e.g., U.S. dollar). The monetary value of the redeemed reward benefits is communicated to the transaction terminal of the merchant via the authorization response. The settlement of transaction is based on the monetary value of the redeemed reward benefits specified in the authorization response. Since the conversion from the redeemed reward amount to a monetary value is postponed until the authorization is approved, the last conversion rate between the reward currency and the payment currency can be applied to the conversion during the authorization of the reward redemption. During the authorization, the redeemed rewards are converted to an amount of payment currency and reserved for settlement.
In one embodiment, the authorization request for the reward redemption transaction and the settlement request for the reward redemption transaction are communicated via two passes of request/response communications. In another embodiment, the authorization and settlement requests of the reward redemption transaction are combined in the same messages for one pass of request/response communications, communicated between the transaction terminal of the merchant and the issuer processor of the virtual account.
As a result of the system, the reward redemption transaction can be performed as a transaction in the virtual payment account in a way similar to a transaction in a typical consumer payment account. The virtual payment account can be set up prior to the transaction (e.g., during the reward balance inquiry, or in response to a user request); and the issuer processor is configured to communicate with the reward host, preferably via a centralized reward redemption platform, to authorize and/or settlement the requested redemption of rewards.
In one embodiment, after a merchant submits a request to get the balance of a reward account of a user to a reward redemption platform, the platform forwards the balance request to a rewards bank, which obtains the balance information and provides the balance information to the reward redemption platform. If the balance is greater than zero, the reward redemption platform submits a request for a private label payment account number to an issuer processor, which in response allocates a private label payment account for the request and communicates the account information of the allocated private label payment account to the reward redemption platform. The reward redemption platform associates the reward account of the user with the allocated private label payment account. After providing the account information and the balance information to the merchant as a response to the balance request, the merchant may use the account information to initiate a payment transaction in the payment processing network in which the issuer processor is connected. When the issuer processor receives the transaction request in the allocated private label payment account, the issuer processor communicates with the rewards bank, via the reward redemption platform, to order the conversion of rewards to a payment to the merchant. The payment is provided to the merchant from the issuer processor to the acquirer processor of the merchant in a way same as a payment is provided from a consumer payment account.
In one embodiment, a user may visit the portal of the reward redemption platform to look up the reward balance in the reward account of the user and/or request the private label payment account for the redemption of rewards from the reward accounts. In one embodiment, the private label payment account may be linked to multiple reward accounts; and the user may specify rules for the redemption of rewards from the multiple reward accounts. In one embodiment, an account identification device is provided to the user to present the account information of the private label payment account. The user may use the private label payment account in a way similar to the use of a consumer payment account issued to the user.
In one embodiment, the issuer processor (145) of the virtual accounts (or private label accounts) is implemented as a part of the transaction handler (103) which interconnects acquirer processors (e.g., 147) and issuer processors on the payment processing network (e.g., illustrated in
In
For example, when the merchant computer (501) sends a reward balance inquiry (503) to the portal (143), the portal (143) requests, via the account setup communication (515), a virtual account (523) for the reward account (525) identified in the reward balance inquiry (503), if it does not already have an associated virtual account (523). In one embodiment, the portal (143) is coupled with the data warehouse (149) to store data associating the reward account (525) and the virtual account (523).
In
In
The merchant computer (501) may present the reward balance (507) and be configured to allow the user to request the redemption of a reward amount that does not exceed the reward balance (507). In one embodiment, the merchant computer (501) includes a transaction terminal (105) connected to the acquirer processor (147) of the merchant.
Using the account number (509), the transaction terminal (105) of the merchant can initiate an authorization communication (517) in the virtual account (523) associated with the reward account (525).
In
In
In one embodiment, the portal (143) is configured to route the redemption request corresponding to the authorization request to the reward host (513) based on the association between the reward account (525) and virtual account (523) established via the account setup communication (515). In response to the redemption request, the reward host (513) is configured to reserve, deduct, and/or convert the redeemed rewards from the reward account (525). The portal (143) is configured to propagate the rejection or acceptation of the redemption request, from the reward host (513) to the issuer processor (145) via the reward redemption communication (519) and the redemption communication (521).
Thus, with the pre-redemption arrangement to set up the virtual account (523) for association with the reward account (525) prior to the reward redemption, and the redemption processing arrangement among the issuer processor (145), the portal (143) and the reward host (513), the redemption transaction can be performed via the payment processing network, without modifications to the acquirer processor (147), and the transaction handler (103).
In
In one embodiment, the computing apparatus includes one or more of: the portal (143), the issuer processor (145), the transaction handler (145), the reward host (513), the data warehouse (149), the transaction terminal (105) and the merchant computer (501), each of which can be implemented via one or more data processing systems illustrated
System
In one embodiment, the system further includes a correlator (117) to correlate user specific advertisement data (119) with transactions resulting from the user specific advertisement data (119). The correlation results (123) can be used by the profile generator (121) to improve the transaction profiles (127).
The transaction profiles (127) of one embodiment are generated from the transaction data (109) in a way as illustrated in U.S. Pat. App. Pub. No. 2010/0306029, entitled “Cardholder Clusters,” and U.S. Pat. App. Pub. No. 2010/0306032, entitled “Systems and Methods to Summarize Transaction Data,” the disclosures of which applications are hereby incorporated herein by reference.
In one embodiment, a data warehouse (149) as illustrated in
In
In one embodiment, the transaction data (109) relates to financial transactions processed by the transaction handler (103); and the account data (111) relates to information about the account holders involved in the transactions. Further data, such as merchant data that relates to the location, business, products and/or services of the merchants that receive payments from account holders for their purchases, can be used in the generation of the transaction profiles (127).
In one embodiment, the financial transactions are made via an account identification device (141), such as financial transaction cards (e.g., credit cards, debit cards, banking cards, etc.); the financial transaction cards may be embodied in various devices, such as plastic cards, chips, radio frequency identification (RFID) devices, mobile phones, personal digital assistants (PDAs), etc.; and the financial transaction cards may be represented by account identifiers (e.g., account numbers or aliases). In one embodiment, the financial transactions are made via directly using the account information (142), without physically presenting the account identification device (141).
Further features, modifications and details are provided in various sections of this description.
Centralized Data Warehouse
In one embodiment, the transaction handler (103) maintains a centralized data warehouse (149) organized around the transaction data (109). For example, the centralized data warehouse (149) may include, and/or support the determination of, spending band distribution, transaction count and amount, merchant categories, merchant by state, cardholder segmentation by velocity scores, and spending within merchant target, competitive set and cross-section.
In one embodiment, the centralized data warehouse (149) provides centralized management but allows decentralized execution. For example, a third party strategic marketing analyst, statistician, marketer, promoter, business leader, etc., may access the centralized data warehouse (149) to analyze customer and shopper data, to provide follow-up analyses of customer contributions, to develop propensity models for increased conversion of marketing campaigns, to develop segmentation models for marketing, etc. The centralized data warehouse (149) can be used to manage advertisement campaigns and analyze response profitability.
In one embodiment, the centralized data warehouse (149) includes merchant data (e.g., data about sellers), customer/business data (e.g., data about buyers), and transaction records between sellers and buyers over time. The centralized data warehouse (149) can be used to support corporate sales forecasting, fraud analysis reporting, sales/customer relationship management (CRM) business intelligence, credit risk prediction and analysis, advanced authorization reporting, merchant benchmarking, business intelligence for small business, rewards, etc.
In one embodiment, the transaction data (109) is combined with external data, such as surveys, benchmarks, search engine statistics, demographics, competition information, emails, etc., to flag key events and data values, to set customer, merchant, data or event triggers, and to drive new transactions and new customer contacts.
Transaction Profile
In
In one embodiment, the transaction profiles (127) provide intelligence information on the behavior, pattern, preference, propensity, tendency, frequency, trend, and budget of the user (101) in making purchases. In one embodiment, the transaction profiles (127) include information about what the user (101) owns, such as points, miles, or other rewards currency, available credit, and received offers, such as coupons loaded into the accounts of the user (101). In one embodiment, the transaction profiles (127) include information based on past offer/coupon redemption patterns. In one embodiment, the transaction profiles (127) include information on shopping patterns in retail stores as well as online, including frequency of shopping, amount spent in each shopping trip, distance of merchant location (retail) from the address of the account holder(s), etc.
In one embodiment, the transaction handler (103) provides at least part of the intelligence for the prioritization, generation, selection, customization and/or adjustment of an advertisement for delivery within a transaction process involving the transaction handler (103). For example, the advertisement may be presented to a customer in response to the customer making a payment via the transaction handler (103).
Some of the transaction profiles (127) are specific to the user (101), or to an account of the user (101), or to a group of users of which the user (101) is a member, such as a household, family, company, neighborhood, city, or group identified by certain characteristics related to online activities, offline purchase activities, merchant propensity, etc.
In one embodiment, the profile generator (121) generates and updates the transaction profiles (127) in batch mode periodically. In other embodiments, the profile generator (121) generates the transaction profiles (127) in real-time, or just in time, in response to a request received in the portal (143) for such profiles.
In one embodiment, the transaction profiles (127) include the values for a set of parameters. Computing the values of the parameters may involve counting transactions that meet one or more criteria, and/or building a statistically-based model in which one or more calculated values or transformed values are put into a statistical algorithm that weights each value to optimize its collective predictiveness for various predetermined purposes.
Further details and examples about the transaction profiles (127) in one embodiment are provided in the section entitled “AGGREGATED SPENDING PROFILE.”
In
In one embodiment, the user data (125) includes the characterization of the context at the point of interaction (107). Thus, the use of the user specific profile (131), selected using the user data (125), includes the consideration of the context at the point of interaction (107) in selecting the user specific advertisement data (119).
In one embodiment, in selecting the user specific advertisement data (119), the advertisement selector (133) uses not only the user specific profile (131), but also information regarding the context at the point of interaction (107). For example, in one embodiment, the user data (125) includes information regarding the context at the point of interaction (107); and the advertisement selector (133) explicitly uses the context information in the generation or selection of the user specific advertisement data (119).
In one embodiment, the advertisement selector (133) may query for specific information regarding the user (101) before providing the user specific advertisement data (119). The queries may be communicated to the operator of the transaction handler (103) and, in particular, to the transaction handler (103) or the profile generator (121). For example, the queries from the advertisement selector (133) may be transmitted and received in accordance with an application programming interface or other query interface of the transaction handler (103), the profile generator (121) or the portal (143) of the transaction handler (103).
In one embodiment, the queries communicated from the advertisement selector (133) may request intelligence information regarding the user (101) at any level of specificity (e.g., segment level, individual level). For example, the queries may include a request for a certain field or type of information in a cardholder's aggregated spending profile. As another example, the queries may include a request for the spending level of the user (101) in a certain merchant category over a prior time period (e.g., six months).
In one embodiment, the advertisement selector (133) is operated by an entity that is separate from the entity that operates the transaction handler (103). For example, the advertisement selector (133) may be operated by a search engine, a publisher, an advertiser, an ad network, or an online merchant. The user specific profile (131) is provided to the advertisement selector (133) to assist in the customization of the user specific advertisement data (119).
In one embodiment, advertising is targeted based on shopping patterns in a merchant category (e.g., as represented by a Merchant Category Code (MCC)) that has high correlation of spending propensity with other merchant categories (e.g., other MCCs). For example, in the context of a first MCC for a targeted audience, a profile identifying second MCCs that have high correlation of spending propensity with the first MCC can be used to select advertisements for the targeted audience.
In one embodiment, the aggregated spending profile is used to provide intelligence information about the spending patterns, preferences, and/or trends of the user (101). For example, a predictive model can be established based on the aggregated spending profile to estimate the needs of the user (101). For example, the factor values and/or the cluster ID in the aggregated spending profile can be used to determine the spending preferences of the user (101). For example, the channel distribution in the aggregated spending profile can be used to provide a customized offer targeted for a particular channel, based on the spending patterns of the user (101).
In one embodiment, mobile advertisements, such as offers and coupons, are generated and disseminated based on aspects of prior purchases, such as timing, location, and nature of the purchases, etc. In one embodiment, the size of the benefit of the offer or coupon is based on purchase volume or spending amount of the prior purchase and/or the subsequent purchase that may qualify for the redemption of the offer. Further details and examples of one embodiment are provided in U.S. Pat. App. Pub. No. 2008/0201226, entitled “Mobile Coupon Method and Portable Consumer Device for Utilizing Same,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, conditional rewards are provided to the user (101); and the transaction handler (103) monitors the transactions of the user (101) to identify redeemable rewards that have satisfied the respective conditions. In one embodiment, the conditional rewards are selected based on transaction data (109). Further details and examples of one embodiment are provided in U.S. Pat. App. Pub. No. 2008/0082418, entitled “Consumer Specific Conditional Rewards,” the disclosure of which is hereby incorporated herein by reference. The techniques to detect the satisfied conditions of conditional rewards can also be used to detect the transactions that satisfy the conditions specified to locate the transactions that result from online activities, such as online advertisements, searches, etc., to correlate the transactions with the respective online activities.
Further details about targeted offer delivery in one embodiment are provided in U.S. Pat. App. Pub. No. 2010/0030644, entitled “Targeted Advertising by Payment Processor History of Cashless Acquired Merchant Transaction on Issued Consumer Account,” and in U.S. Pat. App. Pub. No. 2011/0035280, entitled “Systems and Methods for Targeted Advertisement Delivery, the disclosures of which applications are hereby incorporated herein by reference.
Aggregated Spending Profile
In one embodiment, the characteristics of transaction patterns of customers are profiled via clusters, factors, and/or categories of purchases. The transaction data (109) may include transaction records; and in one embodiment, an aggregated spending profile is generated from the transaction records to summarize the spending behavior reflected in the transaction records, in a way illustrated in U.S. Pat. App. Pub. No. 2010/0306029, entitled “Cardholder Clusters,” and U.S. Pat. App. Pub. No. 2010/0306032, entitled “Systems and Methods to Summarize Transaction Data,” the disclosures of which applications are hereby incorporated herein by reference.
In one embodiment, each of the transaction records is for a particular transaction processed by the transaction handler (103). Each of the transaction records provides information about the particular transaction, such as the account number of the consumer account (146) used to pay for the purchase, the date (and/or time) of the transaction, the amount of the transaction, the ID of the merchant who receives the payment, the category of the merchant, the channel through which the purchase was made, etc. Examples of channels include online, offline in-store, via phone, etc. In one embodiment, the transaction records may further include a field to identify a type of transaction, such as card-present, card-not-present, etc.
In one embodiment, a “card-present” transaction involves physically presenting the account identification device (141), such as a financial transaction card, to the merchant (e.g., via swiping a credit card at a POS terminal of a merchant); and a “card-not-present” transaction involves presenting the account information (142) of the consumer account (146) to the merchant to identify the consumer account (146) without physically presenting the account identification device (141) to the merchant or the transaction terminal (105).
In one embodiment, certain information about the transaction can be looked up in a separate database based on other information recorded for the transaction. For example, a database may be used to store information about merchants, such as the geographical locations of the merchants, categories of the merchants, etc. Thus, the corresponding merchant information related to a transaction can be determined using the merchant ID recorded for the transaction.
In one embodiment, the transaction records may further include details about the products and/or services involved in the purchase. For example, a list of items purchased in the transaction may be recorded together with the respective purchase prices of the items and/or the respective quantities of the purchased items. The products and/or services can be identified via stock-keeping unit (SKU) numbers, or product category IDs. The purchase details may be stored in a separate database and be looked up based on an identifier of the transaction.
When there is voluminous data representing the transaction records, the spending patterns reflected in the transaction records can be difficult to recognize by an ordinary person.
In one embodiment, the voluminous transaction records are summarized into aggregated spending profiles to concisely present the statistical spending characteristics reflected in the transaction records. The aggregated spending profile uses values derived from statistical analysis to present the statistical characteristics of transaction records of an entity in a way easy to understand by an ordinary person.
Details about aggregated spending profiles of some embodiments are provided in U.S. Pat. App. Pub. No. 2010/0306029, entitled “Cardholder Clusters,” and U.S. Pat. App. Pub. No. 2010/0306032, entitled “Systems and Methods to Summarize Transaction Data,” the disclosures of which applications are hereby incorporated herein by reference.
Transaction Data Based Portal
In
Over a period of time, the transaction handler (103) accumulates the transaction data (109) from transactions initiated at different transaction terminals (e.g., 105) for different users (e.g., 101). The transaction data (109) thus includes information on purchases made by various users (e.g., 101) at various times via different purchases options (e.g., online purchase, offline purchase from a retail store, mail order, order via phone, etc.)
In one embodiment, the accumulated transaction data (109) and the corresponding account data (111) are used to generate intelligence information about the purchase behavior, pattern, preference, tendency, frequency, trend, amount and/or propensity of the users (e.g., 101), as individuals or as a member of a group. The intelligence information can then be used to generate, identify and/or select targeted advertisements for presentation to the user (101) on the point of interaction (107), during a transaction, after a transaction, or when other opportunities arise.
In one embodiment, the portal (143) is configured to receive queries identifying search criteria from the profile selector (129), the advertisement selector (133) and/or third parties and in response, to provide transaction-based intelligence requested by the queries.
For example, in one embodiment, a query is to specify a plurality of account holders to request the portal (143) to deliver the transaction profiles (127) of account holders in a batch mode.
For example, in one embodiment, a query is to identify the user (101) to request the user specific profile (131), or the aggregated spending profile, of the user (101). The user (101) may be identified using the account data (111), such as the account number, or the user data (125) such as browser cookie ID, IP address, etc.
For example, in one embodiment, a query is to identify a retail location; and the portal (143) is to provide a profile (e.g., 341) that summarizes the aggregated spending patterns of users who have shopped at the retail location within a period of time.
For example, in one embodiment, a query is to identify a geographical location; and the portal (143) is to provide a profile (e.g., 341) that summarizes the aggregated spending patterns of users who have been to, or who are expected to visit, the geographical location within a period of time (e.g., as determined or predicted based on the locations of the point of interactions (e.g., 107) of the users).
For example, in one embodiment, a query is to identify a geographical area; and the portal (143) is to provide a profile (e.g., 341) that summarizes the aggregated spending patterns of users who reside in the geographical area (e.g., as determined by the account data (111), or who have made transactions within the geographical area with a period of time (e.g., as determined by the locations of the transaction terminals (e.g., 105) used to process the transactions).
In one embodiment, the portal (143) is configured to register certain users (101) for various programs, such as a loyalty program to provide rewards and/or offers to the users (101).
In one embodiment, the portal (143) is to register the interest of users (101), or to obtain permissions from the users (101) to gather further information about the users (101), such as data capturing purchase details, online activities, etc.
In one embodiment, the user (101) may register via the issuer; and the registration data in the consumer account (146) may propagate to the data warehouse (149) upon approval from the user (101).
In one embodiment, the portal (143) is to register merchants and provide services and/or information to merchants.
In one embodiment, the portal (143) is to receive information from third parties, such as search engines, merchants, websites, etc. The third party data can be correlated with the transaction data (109) to identify the relationships between purchases and other events, such as searches, news announcements, conferences, meetings, etc., and improve the prediction capability and accuracy.
In
In one embodiment, the account identification device (141) is a plastic card having a magnetic strip storing account information (142) identifying the consumer account (146) and/or the issuer processor (145). Alternatively, the account identification device (141) is a smartcard having an integrated circuit chip storing at least the account information (142). In one embodiment, the account identification device (141) includes a mobile phone having an integrated smartcard.
In one embodiment, the account information (142) is printed or embossed on the account identification device (141). The account information (142) may be printed as a bar code to allow the transaction terminal (105) to read the information via an optical scanner. The account information (142) may be stored in a memory of the account identification device (141) and configured to be read via wireless, contactless communications, such as near field communications via magnetic field coupling, infrared communications, or radio frequency communications. Alternatively, the transaction terminal (105) may require contact with the account identification device (141) to read the account information (142) (e.g., by reading the magnetic strip of a card with a magnetic strip reader).
In one embodiment, the transaction terminal (105) is configured to transmit an authorization request message to the acquirer processor (147). The authorization request includes the account information (142), an amount of payment, and information about the merchant (e.g., an indication of the merchant account (148)). The acquirer processor (147) requests the transaction handler (103) to process the authorization request, based on the account information (142) received in the transaction terminal (105). The transaction handler (103) routes the authorization request to the issuer processor (145) and may process and respond to the authorization request when the issuer processor (145) is not available. The issuer processor (145) determines whether to authorize the transaction based at least in part on a balance of the consumer account (146).
In one embodiment, the transaction handler (103), the issuer processor (145), and the acquirer processor (147) may each include a subsystem to identify the risk in the transaction and may reject the transaction based on the risk assessment.
In one embodiment, the account identification device (141) includes security features to prevent unauthorized uses of the consumer account (146), such as a logo to show the authenticity of the account identification device (141), encryption to protect the account information (142), etc.
In one embodiment, the transaction terminal (105) is configured to interact with the account identification device (141) to obtain the account information (142) that identifies the consumer account (146) and/or the issuer processor (145). The transaction terminal (105) communicates with the acquirer processor (147) that controls the merchant account (148) of a merchant. The transaction terminal (105) may communicate with the acquirer processor (147) via a data communication connection, such as a telephone connection, an Internet connection, etc. The acquirer processor (147) is to collect payments into the merchant account (148) on behalf of the merchant.
In one embodiment, the transaction terminal (105) is a POS terminal at a traditional, offline, “brick and mortar” retail store. In another embodiment, the transaction terminal (105) is an online server that receives account information (142) of the consumer account (146) from the user (101) through a web connection. In one embodiment, the user (101) may provide account information (142) through a telephone call, via verbal communications with a representative of the merchant; and the representative enters the account information (142) into the transaction terminal (105) to initiate the transaction.
In one embodiment, the account information (142) can be entered directly into the transaction terminal (105) to make payment from the consumer account (146), without having to physically present the account identification device (141). When a transaction is initiated without physically presenting an account identification device (141), the transaction is classified as a “card-not-present” (CNP) transaction.
In one embodiment, the issuer processor (145) may control more than one consumer account (146); the acquirer processor (147) may control more than one merchant account (148); and the transaction handler (103) is connected between a plurality of issuer processors (e.g., 145) and a plurality of acquirer processors (e.g., 147). An entity (e.g., bank) may operate both an issuer processor (145) and an acquirer processor (147).
In one embodiment, the transaction handler (103), the issuer processor (145), the acquirer processor (147), the transaction terminal (105), the portal (143), and other devices and/or services accessing the portal (143) are connected via communications networks, such as local area networks, cellular telecommunications networks, wireless wide area networks, wireless local area networks, an intranet, and Internet. In one embodiment, dedicated communication channels are used between the transaction handler (103) and the issuer processor (145), between the transaction handler (103) and the acquirer processor (147), and/or between the portal (143) and the transaction handler (103).
In one embodiment, the transaction handler (103) uses the data warehouse (149) to store the records about the transactions, such as the transaction records or transaction data (109). In one embodiment, the transaction handler (103) includes a powerful computer, or cluster of computers functioning as a unit, controlled by instructions stored on a computer readable medium.
In one embodiment, the transaction handler (103) is configured to support and deliver authorization services, exception file services, and clearing and settlement services. In one embodiment, the transaction handler (103) has a subsystem to process authorization requests and another subsystem to perform clearing and settlement services.
In one embodiment, the transaction handler (103) is configured to process different types of transactions, such credit card transactions, debit card transactions, prepaid card transactions, and other types of commercial transactions.
In one embodiment, the transaction handler (103) facilitates the communications between the issuer processor (145) and the acquirer processor (147).
In one embodiment, the transaction handler (103) is coupled to the portal (143) (and/or the profile selector (129), the advertisement selector (133), the media controller (115)) to charge the fees for the services of providing the transaction-based intelligence information and/or advertisement.
For example, in one embodiment, the system illustrated in
For example, in one embodiment, the portal (143) is configured to provide transaction-based intelligence information in response to the queries received in the portal (143). The portal (143) is to identify the requesters (e.g., via an authentication, or the address of the requesters) and instruct the transaction handler (103) to charge the consumer accounts (e.g., 146) of the respective requesters for the transaction-based intelligence information. In one embodiment, the accounts of the requesters are charged in response to the delivery of the intelligence information via the portal (143). In one embodiment, the accounts of the requesters are charged a periodic subscription fee for the access to the query capability of the portal (143).
In one embodiment, the information service provided by the system illustrated in
In one embodiment, the transaction terminal (105) is configured to submit the authorized transactions to the acquirer processor (147) for settlement. The amount for the settlement may be different from the amount specified in the authorization request. The transaction handler (103) is coupled between the issuer processor (145) and the acquirer processor (147) to facilitate the clearing and settling of the transaction. Clearing includes the exchange of financial information between the issuer processor (145) and the acquirer processor (147); and settlement includes the exchange of funds.
In one embodiment, the issuer processor (145) is to provide funds to make payments on behalf of the consumer account (146). The acquirer processor (147) is to receive the funds on behalf of the merchant account (148). The issuer processor (145) and the acquirer processor (147) communicate with the transaction handler (103) to coordinate the transfer of funds for the transaction. In one embodiment, the funds are transferred electronically.
In one embodiment, the transaction terminal (105) may submit a transaction directly for settlement, without having to separately submit an authorization request.
In one embodiment, the portal (143) provides a user interface to allow the user (101) to organize the transactions in one or more consumer accounts (146) of the user with one or more issuers. The user (101) may organize the transactions using information and/or categories identified in the transaction records, such as merchant category, transaction date, amount, etc. Examples and techniques in one embodiment are provided in U.S. Pat. App. Pub. No. 2007/0055597, entitled “Method and System for Manipulating Purchase Information,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, the portal (143) provides transaction based statistics, such as indicators for retail spending monitoring, indicators for merchant benchmarking, industry/market segmentation, indicators of spending patterns, etc. Further examples can be found in U.S. Pat. App. Pub. No. 2009/0048884, entitled “Merchant Benchmarking Tool,” the disclosure of which application is hereby incorporated herein by reference.
Transaction Terminal
In one embodiment, the transaction terminal (105) includes a memory (167) coupled to the processor (151), which controls the operations of a reader (163), an input device (153), an output device (165) and a network interface (161). The memory (167) may store instructions for the processor (151) and/or data, such as an identification that is associated with the merchant account (148).
In one embodiment, the reader (163) includes a magnetic strip reader. In another embodiment, the reader (163) includes a contactless reader, such as a radio frequency identification (RFID) reader, a near field communications (NFC) device configured to read data via magnetic field coupling (in accordance with ISO standard 14443/NFC), a Bluetooth transceiver, a WiFi transceiver, an infrared transceiver, a laser scanner, etc.
In one embodiment, the input device (153) includes key buttons that can be used to enter the account information (142) directly into the transaction terminal (105) without the physical presence of the account identification device (141). The input device (153) can be configured to provide further information to initiate a transaction, such as a personal identification number (PIN), password, zip code, etc. that may be used to access the account identification device (141), or in combination with the account information (142) obtained from the account identification device (141).
In one embodiment, the output device (165) may include a display, a speaker, and/or a printer to present information, such as the result of an authorization request, a receipt for the transaction, an advertisement, etc.
In one embodiment, the network interface (161) is configured to communicate with the acquirer processor (147) via a telephone connection, an Internet connection, or a dedicated data communication channel.
In one embodiment, the instructions stored in the memory (167) are configured at least to cause the transaction terminal (105) to send an authorization request message to the acquirer processor (147) to initiate a transaction. The transaction terminal (105) may or may not send a separate request for the clearing and settling of the transaction. The instructions stored in the memory (167) are also configured to cause the transaction terminal (105) to perform other types of functions discussed in this description.
In one embodiment, a transaction terminal (105) may have fewer components than those illustrated in
In one embodiment, a transaction terminal (105) may have more components than those illustrated in
Account Identification Device
In one embodiment, the account identification device (141) includes a memory (167) coupled to the processor (151), which controls the operations of a communication device (159), an input device (153), an audio device (157) and a display device (155). The memory (167) may store instructions for the processor (151) and/or data, such as the account information (142) associated with the consumer account (146).
In one embodiment, the account information (142) includes an identifier identifying the issuer (and thus the issuer processor (145)) among a plurality of issuers, and an identifier identifying the consumer account among a plurality of consumer accounts controlled by the issuer processor (145). The account information (142) may include an expiration date of the account identification device (141), the name of the consumer holding the consumer account (146), and/or an identifier identifying the account identification device (141) among a plurality of account identification devices associated with the consumer account (146).
In one embodiment, the account information (142) may further include a loyalty program account number, accumulated rewards of the consumer in the loyalty program, an address of the consumer, a balance of the consumer account (146), transit information (e.g., a subway or train pass), access information (e.g., access badges), and/or consumer information (e.g., name, date of birth), etc.
In one embodiment, the memory includes a nonvolatile memory, such as magnetic strip, a memory chip, a flash memory, a Read Only Memory (ROM), etc. to store the account information (142).
In one embodiment, the information stored in the memory (167) of the account identification device (141) may also be in the form of data tracks that are traditionally associated with credits cards. Such tracks include Track 1 and Track 2. Track 1 (“International Air Transport Association”) stores more information than Track 2, and contains the cardholder's name as well as the account number and other discretionary data. Track 1 is sometimes used by airlines when securing reservations with a credit card. Track 2 (“American Banking Association”) is currently most commonly used and is read by ATMs and credit card checkers. The ABA (American Banking Association) designed the specifications of Track 1 and banks abide by it. It contains the cardholder's account number, encrypted PIN, and other discretionary data.
In one embodiment, the communication device (159) includes a semiconductor chip to implement a transceiver for communication with the reader (163) and an antenna to provide and/or receive wireless signals.
In one embodiment, the communication device (159) is configured to communicate with the reader (163). The communication device (159) may include a transmitter to transmit the account information (142) via wireless transmissions, such as radio frequency signals, magnetic coupling, or infrared, Bluetooth or WiFi signals, etc.
In one embodiment, the account identification device (141) is in the form of a mobile phone, personal digital assistant (PDA), etc. The input device (153) can be used to provide input to the processor (151) to control the operation of the account identification device (141); and the audio device (157) and the display device (155) may present status information and/or other information, such as advertisements or offers. The account identification device (141) may include further components that are not shown in
In one embodiment, the communication device (159) may access the account information (142) stored on the memory (167) without going through the processor (151).
In one embodiment, the account identification device (141) has fewer components than those illustrated in
For example, in one embodiment, an account identification device (141) is in the form of a debit card, a credit card, a smartcard, or a consumer device that has optional features such as magnetic strips, or smartcards.
An example of an account identification device (141) is a magnetic strip attached to a plastic substrate in the form of a card. The magnetic strip is used as the memory (167) of the account identification device (141) to provide the account information (142). Consumer information, such as account number, expiration date, and consumer name may be printed or embossed on the card. A semiconductor chip implementing the memory (167) and the communication device (159) may also be embedded in the plastic card to provide account information (142) in one embodiment. In one embodiment, the account identification device (141) has the semiconductor chip but not the magnetic strip.
In one embodiment, the account identification device (141) is integrated with a security device, such as an access card, a radio frequency identification (RFID) tag, a security card, a transponder, etc.
In one embodiment, the account identification device (141) is a handheld and compact device. In one embodiment, the account identification device (141) has a size suitable to be placed in a wallet or pocket of the consumer.
Some examples of an account identification device (141) include a credit card, a debit card, a stored value device, a payment card, a gift card, a smartcard, a smart media card, a payroll card, a health care card, a wrist band, a keychain device, a supermarket discount card, a transponder, and a machine readable medium containing account information (142).
Point of Interaction
In one embodiment, the point of interaction (107) is to provide an advertisement to the user (101), or to provide information derived from the transaction data (109) to the user (101).
In one embodiment, an advertisement is a marketing interaction which may include an announcement and/or an offer of a benefit, such as a discount, incentive, reward, coupon, gift, cash back, or opportunity (e.g., special ticket/admission). An advertisement may include an offer of a product or service, an announcement of a product or service, or a presentation of a brand of products or services, or a notice of events, facts, opinions, etc. The advertisements can be presented in text, graphics, audio, video, or animation, and as printed matter, web content, interactive media, etc. An advertisement may be presented in response to the presence of a financial transaction card, or in response to a financial transaction card being used to make a financial transaction, or in response to other user activities, such as browsing a web page, submitting a search request, communicating online, entering a wireless communication zone, etc. In one embodiment, the presentation of advertisements may be not a result of a user action.
In one embodiment, the point of interaction (107) can be one of various endpoints of the transaction network, such as point of sale (POS) terminals, automated teller machines (ATMs), electronic kiosks (or computer kiosks or interactive kiosks), self-assist checkout terminals, vending machines, gas pumps, websites of banks (e.g., issuer banks or acquirer banks of credit cards), bank statements (e.g., credit card statements), websites of the transaction handler (103), websites of merchants, checkout websites or web pages for online purchases, etc.
In one embodiment, the point of interaction (107) may be the same as the transaction terminal (105), such as a point of sale (POS) terminal, an automated teller machine (ATM), a mobile phone, a computer of the user for an online transaction, etc. In one embodiment, the point of interaction (107) may be co-located with, or near, the transaction terminal (105) (e.g., a video monitor or display, a digital sign), or produced by the transaction terminal (e.g., a receipt produced by the transaction terminal (105)). In one embodiment, the point of interaction (107) may be separate from and not co-located with the transaction terminal (105), such as a mobile phone, a personal digital assistant, a personal computer of the user, a voice mail box of the user, an email inbox of the user, a digital sign, etc.
For example, the advertisements can be presented on a portion of media for a transaction with the customer, which portion might otherwise be unused and thus referred to as a “white space” herein. A white space can be on a printed matter (e.g., a receipt printed for the transaction, or a printed credit card statement), on a video display (e.g., a display monitor of a POS terminal for a retail transaction, an ATM for cash withdrawal or money transfer, a personal computer of the customer for online purchases), or on an audio channel (e.g., an interactive voice response (IVR) system for a transaction over a telephonic device).
In one embodiment, the white space is part of a media channel available to present a message from the transaction handler (103) in connection with the processing of a transaction of the user (101). In one embodiment, the white space is in a media channel that is used to report information about a transaction of the user (101), such as an authorization status, a confirmation message, a verification message, a user interface to verify a password for the online use of the account information (142), a monthly statement, an alert or a report, or a web page provided by the portal (143) to access a loyalty program associated with the consumer account (146) or a registration program.
In other embodiments, the advertisements can also be presented via other media channels which may not involve a transaction processed by the transaction handler (103). For example, the advertisements can be presented on publications or announcements (e.g., newspapers, magazines, books, directories, radio broadcasts, television, digital signage, etc., which may be in an electronic form, or in a printed or painted form). The advertisements may be presented on paper, on websites, on billboards, on digital signs, or on audio portals.
In one embodiment, the transaction handler (103) purchases the rights to use the media channels from the owner or operators of the media channels and uses the media channels as advertisement spaces. For example, white spaces at a point of interaction (e.g., 107) with customers for transactions processed by the transaction handler (103) can be used to deliver advertisements relevant to the customers conducting the transactions; and the advertisement can be selected based at least in part on the intelligence information derived from the accumulated transaction data (109) and/or the context at the point of interaction (107) and/or the transaction terminal (105).
In general, a point of interaction (e.g., 107) may or may not be capable of receiving inputs from the customers, and may or may not co-located with a transaction terminal (e.g., 105) that initiates the transactions. The white spaces for presenting the advertisement on the point of interaction (107) may be on a portion of a geographical display space (e.g., on a screen), or on a temporal space (e.g., in an audio stream).
In one embodiment, the point of interaction (107) may be used to primarily to access services not provided by the transaction handler (103), such as services provided by a search engine, a social networking website, an online marketplace, a blog, a news site, a television program provider, a radio station, a satellite, a publisher, etc.
In one embodiment, a consumer device is used as the point of interaction (107), which may be a non-portable consumer device or a portable computing device. The consumer device is to provide media content to the user (101) and may receive input from the user (101).
Examples of non-portable consumer devices include a computer terminal, a television set, a personal computer, a set-top box, or the like. Examples of portable consumer devices include a portable computer, a cellular phone, a personal digital assistant (PDA), a pager, a security card, a wireless terminal, or the like. The consumer device may be implemented as a data processing system as illustrated in
In one embodiment, the consumer device includes an account identification device (141). For example, a smart card used as an account identification device (141) is integrated with a mobile phone, or a personal digital assistant (PDA).
In one embodiment, the point of interaction (107) is integrated with a transaction terminal (105). For example, a self-service checkout terminal includes a touch pad to interact with the user (101); and an ATM machine includes a user interface subsystem to interact with the user (101).
Hardware
In one embodiment, a computing apparatus is configured to include some of the modules or components illustrated in
In one embodiment, at least some of the modules or components illustrated in
Further, the data illustrated in
In one embodiment, the transaction handler (103) is a payment processing system, or a payment card processor, such as a card processor for credit cards, debit cards, etc.
In
In one embodiment, the inter-connect (171) interconnects the microprocessor(s) (173) and the memory (167) together and also interconnects them to input/output (I/O) device(s) (175) via I/O controller(s) (177). I/O devices (175) may include a display device and/or peripheral devices, such as mice, keyboards, modems, network interfaces, printers, scanners, video cameras and other devices known in the art. In one embodiment, when the data processing system is a server system, some of the I/O devices (175), such as printers, scanners, mice, and/or keyboards, are optional.
In one embodiment, the inter-connect (171) includes one or more buses connected to one another through various bridges, controllers and/or adapters. In one embodiment the I/O controllers (177) include a USB (Universal Serial Bus) adapter for controlling USB peripherals, and/or an IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.
In one embodiment, the memory (167) includes one or more of: ROM (Read Only Memory), volatile RAM (Random Access Memory), and non-volatile memory, such as hard drive, flash memory, etc.
Volatile RAM is typically implemented as dynamic RAM (DRAM) which requires power continually in order to refresh or maintain the data in the memory. Non-volatile memory is typically a magnetic hard drive, a magnetic optical drive, an optical drive (e.g., a DVD RAM), or other type of memory system which maintains data even after power is removed from the system. The non-volatile memory may also be a random access memory.
The non-volatile memory can be a local device coupled directly to the rest of the components in the data processing system. A non-volatile memory that is remote from the system, such as a network storage device coupled to the data processing system through a network interface such as a modem or Ethernet interface, can also be used.
In this description, some functions and operations are described as being performed by or caused by software code to simplify description. However, such expressions are also used to specify that the functions result from execution of the code/instructions by a processor, such as a microprocessor.
Alternatively, or in combination, the functions and operations as described here can be implemented using special purpose circuitry, with or without software instructions, such as using Application-Specific Integrated Circuit (ASIC) or Field-Programmable Gate Array (FPGA). Embodiments can be implemented using hardwired circuitry without software instructions, or in combination with software instructions. Thus, the techniques are limited neither to any specific combination of hardware circuitry and software, nor to any particular source for the instructions executed by the data processing system.
While one embodiment can be implemented in fully functioning computers and computer systems, various embodiments are capable of being distributed as a computing product in a variety of forms and are capable of being applied regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
At least some aspects disclosed can be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM, volatile RAM, non-volatile memory, cache or a remote storage device.
Routines executed to implement the embodiments may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically include one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations necessary to execute elements involving the various aspects.
A machine readable medium can be used to store software and data which when executed by a data processing system causes the system to perform various methods. The executable software and data may be stored in various places including for example ROM, volatile RAM, non-volatile memory and/or cache. Portions of this software and/or data may be stored in any one of these storage devices. Further, the data and instructions can be obtained from centralized servers or peer to peer networks. Different portions of the data and instructions can be obtained from different centralized servers and/or peer to peer networks at different times and in different communication sessions or in a same communication session. The data and instructions can be obtained in entirety prior to the execution of the applications. Alternatively, portions of the data and instructions can be obtained dynamically, just in time, when needed for execution. Thus, it is not required that the data and instructions be on a machine readable medium in entirety at a particular instance of time.
Examples of computer-readable media include but are not limited to recordable and non-recordable type media such as volatile and non-volatile memory devices, read only memory (ROM), random access memory (RAM), flash memory devices, floppy and other removable disks, magnetic disk storage media, optical storage media (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), among others. The computer-readable media may store the instructions.
The instructions may also be embodied in digital and analog communication links for electrical, optical, acoustical or other forms of propagated signals, such as carrier waves, infrared signals, digital signals, etc. However, propagated signals, such as carrier waves, infrared signals, digital signals, etc. are not tangible machine readable medium and are not configured to store instructions.
In general, a machine readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form accessible by a machine (e.g., a computer, network device, personal digital assistant, manufacturing tool, any device with a set of one or more processors, etc.).
In various embodiments, hardwired circuitry may be used in combination with software instructions to implement the techniques. Thus, the techniques are neither limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the data processing system.
Other Aspects
The description and drawings are illustrative and are not to be construed as limiting. The present disclosure is illustrative of inventive features to enable a person skilled in the art to make and use the techniques. Various features, as described herein, should be used in compliance with all current and future rules, laws and regulations related to privacy, security, permission, consent, authorization, and others. Numerous specific details are described to provide a thorough understanding. However, in certain instances, well known or conventional details are not described in order to avoid obscuring the description. References to one or an embodiment in the present disclosure are not necessarily references to the same embodiment; and, such references mean at least one.
The use of headings herein is merely provided for ease of reference, and shall not be interpreted in any way to limit this disclosure or the following claims.
Reference to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, and are not necessarily all referring to separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by one embodiment and not by others. Similarly, various requirements are described which may be requirements for one embodiment but not other embodiments. Unless excluded by explicit description and/or apparent incompatibility, any combination of various features described in this description is also included here.
The disclosures of the above discussed patent documents are hereby incorporated herein by reference.
In the foregoing specification, the disclosure has been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope as set forth in the following claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
The present application claims priority to Prov. U.S. Pat. App. Ser. No. 62/012,565, filed Jun. 16, 2014, the entire disclosure of which is hereby incorporated herein by reference. The present application relates to U.S. Pat. App. Pub. No. 2012/0191525 entitled “Systems and Methods to Facilitate Loyalty Reward Transactions,” U.S. Pat. App. Pub. No. 2011/0087530 entitled “Systems and Methods to Provide Loyalty Programs,” U.S. Pat. App. Pub. No. 2010/0211445 entitled “Incentives Associated with Linked Financial Accounts,” and U.S. Pat. App. Pub. No. 2009/0271262 entitled “Authorization System with Split Messaging,” the entire disclosures of which applications are hereby incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4906826 | Spencer | Mar 1990 | A |
| 4914590 | Loatman et al. | Apr 1990 | A |
| 5025372 | Burton et al. | Jun 1991 | A |
| 5401946 | Weinblatt | Mar 1995 | A |
| 5592560 | Deaton et al. | Jan 1997 | A |
| 5621812 | Deaton et al. | Apr 1997 | A |
| 5638457 | Deaton et al. | Jun 1997 | A |
| 5684990 | Boothby | Nov 1997 | A |
| 5687322 | Deaton et al. | Nov 1997 | A |
| 5710886 | Christensen et al. | Jan 1998 | A |
| 5924080 | Johnson | Jul 1999 | A |
| 5974396 | Anderson et al. | Oct 1999 | A |
| 6018723 | Siegel et al. | Jan 2000 | A |
| 6035280 | Christensen | Mar 2000 | A |
| 6055573 | Gardenswartz et al. | Apr 2000 | A |
| 6061660 | Eggleston et al. | May 2000 | A |
| 6065675 | Teicher | May 2000 | A |
| 6070147 | Harms et al. | May 2000 | A |
| 6101484 | Halbert et al. | Aug 2000 | A |
| 6119101 | Peckover | Sep 2000 | A |
| 6119933 | Wong et al. | Sep 2000 | A |
| 6216129 | Eldering | Apr 2001 | B1 |
| 6226642 | Beranek et al. | May 2001 | B1 |
| 6282516 | Giuliani | Aug 2001 | B1 |
| 6282522 | Davis et al. | Aug 2001 | B1 |
| 6285983 | Jenkins | Sep 2001 | B1 |
| 6298330 | Gardenswartz et al. | Oct 2001 | B1 |
| 6307958 | Deaton et al. | Oct 2001 | B1 |
| 6321201 | Dahl | Nov 2001 | B1 |
| 6324519 | Eldering | Nov 2001 | B1 |
| 6327574 | Kramer et al. | Dec 2001 | B1 |
| 6332126 | Peirce et al. | Dec 2001 | B1 |
| 6334110 | Walter et al. | Dec 2001 | B1 |
| 6377935 | Deaton et al. | Apr 2002 | B1 |
| 6450407 | Freeman et al. | Sep 2002 | B1 |
| 6487538 | Gupta et al. | Nov 2002 | B1 |
| 6505168 | Rothman et al. | Jan 2003 | B1 |
| 6519571 | Guheen et al. | Feb 2003 | B1 |
| 6598030 | Siegel et al. | Jul 2003 | B1 |
| 6604089 | Van Horn et al. | Aug 2003 | B1 |
| 6604239 | Kohen | Aug 2003 | B1 |
| 6631356 | Van Horn et al. | Oct 2003 | B1 |
| 6631372 | Graham | Oct 2003 | B1 |
| 6742003 | Heckerman et al. | May 2004 | B2 |
| 6834110 | Marconcini et al. | Dec 2004 | B1 |
| 6856992 | Britton et al. | Feb 2005 | B2 |
| 6901406 | Nabe et al. | May 2005 | B2 |
| 6922686 | Okamoto et al. | Jul 2005 | B2 |
| 6934508 | Ceresoli et al. | Aug 2005 | B2 |
| 6934690 | Van Horn et al. | Aug 2005 | B1 |
| 6938022 | Singhal | Aug 2005 | B1 |
| 6941376 | Mitchell et al. | Sep 2005 | B2 |
| 6996560 | Choi et al. | Feb 2006 | B1 |
| 7003476 | Samra et al. | Feb 2006 | B1 |
| 7024374 | Day et al. | Apr 2006 | B1 |
| 7024409 | Iyengar | Apr 2006 | B2 |
| 7035855 | Kilger et al. | Apr 2006 | B1 |
| 7039599 | Merriman et al. | May 2006 | B2 |
| 7062510 | Eldering | Jun 2006 | B1 |
| 7072847 | Ulenas et al. | Jul 2006 | B2 |
| 7107230 | Halbert et al. | Sep 2006 | B1 |
| 7107249 | Dively et al. | Sep 2006 | B2 |
| 7120590 | Eisen et al. | Oct 2006 | B1 |
| 7124099 | Mesaros | Oct 2006 | B2 |
| 7143143 | Thompson | Nov 2006 | B1 |
| 7146330 | Alon et al. | Dec 2006 | B1 |
| 7158943 | van der Riet | Jan 2007 | B2 |
| 7158955 | Diveley et al. | Jan 2007 | B2 |
| 7162436 | Eckel, Jr. | Jan 2007 | B1 |
| 7165037 | Lazarus et al. | Jan 2007 | B2 |
| 7177822 | Mahmood et al. | Feb 2007 | B2 |
| 7181412 | Fulgoni et al. | Feb 2007 | B1 |
| 7181419 | Mesaros | Feb 2007 | B1 |
| 7194422 | St. John Killick | Mar 2007 | B1 |
| 7194427 | Van Horn et al. | Mar 2007 | B1 |
| 7225142 | Apte et al. | May 2007 | B1 |
| 7260837 | Abraham et al. | Aug 2007 | B2 |
| 7263498 | Van Horn et al. | Aug 2007 | B1 |
| 7264152 | Tsuei et al. | Sep 2007 | B2 |
| 7269578 | Sweeney | Sep 2007 | B2 |
| 7299194 | Manganaris et al. | Nov 2007 | B1 |
| 7328169 | Temares et al. | Feb 2008 | B2 |
| 7333998 | Heckerman et al. | Feb 2008 | B2 |
| 7337127 | Smith et al. | Feb 2008 | B1 |
| 7340438 | Nordman et al. | Mar 2008 | B2 |
| 7359866 | Farat | Apr 2008 | B2 |
| 7360251 | Spalink et al. | Apr 2008 | B2 |
| 7363246 | Van Horn et al. | Apr 2008 | B1 |
| 7373311 | Lambert et al. | May 2008 | B2 |
| 7398225 | Voltmer et al. | Jul 2008 | B2 |
| 7398226 | Haines et al. | Jul 2008 | B2 |
| 7401731 | Pletz et al. | Jul 2008 | B1 |
| 7415537 | Maes | Aug 2008 | B1 |
| 7424439 | Fayyad et al. | Sep 2008 | B1 |
| 7424441 | George et al. | Sep 2008 | B2 |
| 7428498 | Voltmer et al. | Sep 2008 | B2 |
| 7444658 | Matz et al. | Oct 2008 | B1 |
| 7480627 | Van Horn et al. | Jan 2009 | B1 |
| 7490052 | Kilger et al. | Feb 2009 | B2 |
| 7493655 | Brown | Feb 2009 | B2 |
| 7496524 | Voltmer et al. | Feb 2009 | B2 |
| 7526485 | Hagan et al. | Apr 2009 | B2 |
| 7533038 | Blume et al. | May 2009 | B2 |
| 7533130 | Narayana et al. | May 2009 | B2 |
| 7536360 | Stolfo et al. | May 2009 | B2 |
| 7552069 | Kepecs | Jun 2009 | B2 |
| 7562030 | Shapira et al. | Jul 2009 | B1 |
| 7578430 | Michelsen et al. | Aug 2009 | B2 |
| 7578435 | Suk | Aug 2009 | B2 |
| 7593871 | Mesaros | Sep 2009 | B1 |
| 7613628 | Ariff et al. | Nov 2009 | B2 |
| 7613629 | Antonucci et al. | Nov 2009 | B2 |
| 7624184 | Aviani et al. | Nov 2009 | B1 |
| 7689463 | Mesaros | Mar 2010 | B1 |
| 7689469 | Mesaros | Mar 2010 | B1 |
| 7693748 | Mesaros | Apr 2010 | B1 |
| 7729945 | Katz et al. | Jun 2010 | B1 |
| 7729977 | Xiao et al. | Jun 2010 | B2 |
| 7747473 | Mesaros | Jun 2010 | B1 |
| 7752134 | Spear | Jul 2010 | B2 |
| 7828206 | Hessburg et al. | Nov 2010 | B2 |
| 7904337 | Morsa | Mar 2011 | B2 |
| 7917388 | van der Riet | Mar 2011 | B2 |
| 7933841 | Schmeyer et al. | Apr 2011 | B2 |
| 7953219 | Freedman et al. | May 2011 | B2 |
| 8050968 | Antonucci et al. | Nov 2011 | B2 |
| 8055536 | Olaiya et al. | Nov 2011 | B1 |
| 8103545 | Ramer et al. | Jan 2012 | B2 |
| 8131875 | Chen et al. | Mar 2012 | B1 |
| 8140389 | Altberg et al. | Mar 2012 | B2 |
| 8313023 | McGhie et al. | Nov 2012 | B1 |
| 8342399 | McGhie et al. | Jan 2013 | B1 |
| 8387858 | Bohn et al. | Mar 2013 | B2 |
| 8511550 | McGhie et al. | Aug 2013 | B1 |
| 8612290 | Postrel | Dec 2013 | B2 |
| 20010027413 | Bhutta | Oct 2001 | A1 |
| 20010049620 | Blasko | Dec 2001 | A1 |
| 20020004733 | Addante | Jan 2002 | A1 |
| 20020019768 | Fredrickson et al. | Feb 2002 | A1 |
| 20020032602 | Lanzillo, Jr. et al. | Mar 2002 | A1 |
| 20020032904 | Lerner | Mar 2002 | A1 |
| 20020042738 | Srinivasan et al. | Apr 2002 | A1 |
| 20020046187 | Vargas et al. | Apr 2002 | A1 |
| 20020053076 | Landesmann | May 2002 | A1 |
| 20020059100 | Shore | May 2002 | A1 |
| 20020065723 | Anderson et al. | May 2002 | A1 |
| 20020072931 | Card | Jun 2002 | A1 |
| 20020095387 | Sosa et al. | Jul 2002 | A1 |
| 20020099649 | Lee et al. | Jul 2002 | A1 |
| 20020107738 | Beach et al. | Aug 2002 | A1 |
| 20020123928 | Eldering et al. | Sep 2002 | A1 |
| 20020128908 | Levin et al. | Sep 2002 | A1 |
| 20020133400 | Terry et al. | Sep 2002 | A1 |
| 20020133405 | Newnam et al. | Sep 2002 | A1 |
| 20020138346 | Kodaka et al. | Sep 2002 | A1 |
| 20020147645 | Alao et al. | Oct 2002 | A1 |
| 20020161625 | Brito-Valladares et al. | Oct 2002 | A1 |
| 20020174013 | Freeman et al. | Nov 2002 | A1 |
| 20020194137 | Park et al. | Dec 2002 | A1 |
| 20030004808 | Elhaoussine et al. | Jan 2003 | A1 |
| 20030018652 | Heckerman et al. | Jan 2003 | A1 |
| 20030047602 | Iida et al. | Mar 2003 | A1 |
| 20030074267 | Acharya et al. | Apr 2003 | A1 |
| 20030078864 | Hardesty et al. | Apr 2003 | A1 |
| 20030115113 | Duncan | Jun 2003 | A1 |
| 20030144935 | Sobek | Jul 2003 | A1 |
| 20030191832 | Satyavolu et al. | Oct 2003 | A1 |
| 20040019518 | Abraham et al. | Jan 2004 | A1 |
| 20040024632 | Perry | Feb 2004 | A1 |
| 20040054577 | Inoue et al. | Mar 2004 | A1 |
| 20040054581 | Redford et al. | Mar 2004 | A1 |
| 20040054591 | Spaeth et al. | Mar 2004 | A1 |
| 20040073482 | Wiggins et al. | Apr 2004 | A1 |
| 20040099730 | Tuchler et al. | May 2004 | A1 |
| 20040122735 | Meshkin | Jun 2004 | A1 |
| 20040122736 | Strock et al. | Jun 2004 | A1 |
| 20040127192 | Ceresoli et al. | Jul 2004 | A1 |
| 20040133474 | Tami et al. | Jul 2004 | A1 |
| 20040181554 | Heckerman et al. | Sep 2004 | A1 |
| 20040193489 | Boyd et al. | Sep 2004 | A1 |
| 20040193685 | Proehl | Sep 2004 | A1 |
| 20040225509 | Andre | Nov 2004 | A1 |
| 20040225603 | Allen et al. | Nov 2004 | A1 |
| 20040249650 | Freedman et al. | Dec 2004 | A1 |
| 20040249710 | Smith et al. | Dec 2004 | A1 |
| 20050055275 | Newman et al. | Mar 2005 | A1 |
| 20050071225 | Bortolin et al. | Mar 2005 | A1 |
| 20050071227 | Hammad et al. | Mar 2005 | A1 |
| 20050071230 | Mankoff | Mar 2005 | A1 |
| 20050131762 | Bharat et al. | Jun 2005 | A1 |
| 20050131792 | Rowe | Jun 2005 | A1 |
| 20050160002 | Roetter et al. | Jul 2005 | A1 |
| 20050160003 | Berardi et al. | Jul 2005 | A1 |
| 20050216823 | Petersen et al. | Sep 2005 | A1 |
| 20050235310 | Bies | Oct 2005 | A1 |
| 20050251446 | Jiang et al. | Nov 2005 | A1 |
| 20060053056 | Alspach-Goss et al. | Mar 2006 | A1 |
| 20060069619 | Walker et al. | Mar 2006 | A1 |
| 20060103667 | Amit et al. | May 2006 | A1 |
| 20060143071 | Hofmann | Jun 2006 | A1 |
| 20060143075 | Carr et al. | Jun 2006 | A1 |
| 20060161527 | Dwork et al. | Jul 2006 | A1 |
| 20060167818 | Wentker et al. | Jul 2006 | A1 |
| 20060178957 | LeClaire | Aug 2006 | A1 |
| 20060190337 | Ayers, Jr. | Aug 2006 | A1 |
| 20060218038 | Grider | Sep 2006 | A1 |
| 20060224454 | Kantor et al. | Oct 2006 | A1 |
| 20060230053 | Eldering | Oct 2006 | A1 |
| 20060253320 | Heywood | Nov 2006 | A1 |
| 20060253323 | Phan et al. | Nov 2006 | A1 |
| 20060259362 | Cates | Nov 2006 | A1 |
| 20060265280 | Nakada et al. | Nov 2006 | A1 |
| 20060265429 | Pendergast et al. | Nov 2006 | A1 |
| 20060287916 | Starr et al. | Dec 2006 | A1 |
| 20060293948 | Weinblatt | Dec 2006 | A1 |
| 20070033104 | Collins et al. | Feb 2007 | A1 |
| 20070038516 | Apple et al. | Feb 2007 | A1 |
| 20070055597 | Patel et al. | Mar 2007 | A1 |
| 20070061256 | Park et al. | Mar 2007 | A1 |
| 20070067267 | Ives | Mar 2007 | A1 |
| 20070067297 | Kublickis | Mar 2007 | A1 |
| 20070084917 | Fajkowski | Apr 2007 | A1 |
| 20070100691 | Patterson | May 2007 | A1 |
| 20070124201 | Hu et al. | May 2007 | A1 |
| 20070129963 | Skibinski et al. | Jun 2007 | A1 |
| 20070156517 | Kaplan et al. | Jul 2007 | A1 |
| 20070162377 | Williams | Jul 2007 | A1 |
| 20070174295 | Abraham et al. | Jul 2007 | A1 |
| 20070179846 | Jain et al. | Aug 2007 | A1 |
| 20070192121 | Routson | Aug 2007 | A1 |
| 20070192122 | Routson et al. | Aug 2007 | A1 |
| 20070219865 | Leining | Sep 2007 | A1 |
| 20070219866 | Wolf et al. | Sep 2007 | A1 |
| 20070226056 | Belanger et al. | Sep 2007 | A1 |
| 20070226061 | Chen et al. | Sep 2007 | A1 |
| 20070239532 | Benson et al. | Oct 2007 | A1 |
| 20070244741 | Blume et al. | Oct 2007 | A1 |
| 20070260521 | Van Der Riet | Nov 2007 | A1 |
| 20070260736 | Miller | Nov 2007 | A1 |
| 20070265923 | Krassner et al. | Nov 2007 | A1 |
| 20070282681 | Shubert et al. | Dec 2007 | A1 |
| 20080004884 | Flake et al. | Jan 2008 | A1 |
| 20080021772 | Aloni et al. | Jan 2008 | A1 |
| 20080046358 | Holm-Blagg et al. | Feb 2008 | A1 |
| 20080056541 | Tani et al. | Mar 2008 | A1 |
| 20080059302 | Fordyce, III et al. | Mar 2008 | A1 |
| 20080059303 | Fordyce | Mar 2008 | A1 |
| 20080059306 | Fordyce et al. | Mar 2008 | A1 |
| 20080059307 | Fordyce, III et al. | Mar 2008 | A1 |
| 20080065507 | Morrison et al. | Mar 2008 | A1 |
| 20080071587 | Granucci et al. | Mar 2008 | A1 |
| 20080071680 | Sheets | Mar 2008 | A1 |
| 20080077487 | Davis et al. | Mar 2008 | A1 |
| 20080077499 | Ariff et al. | Mar 2008 | A1 |
| 20080082393 | Ozzie et al. | Apr 2008 | A1 |
| 20080082397 | Dennison et al. | Apr 2008 | A1 |
| 20080082418 | Fordyce et al. | Apr 2008 | A1 |
| 20080103887 | Oldham et al. | May 2008 | A1 |
| 20080103888 | Weir | May 2008 | A1 |
| 20080103968 | Bies | May 2008 | A1 |
| 20080120182 | Arnold et al. | May 2008 | A1 |
| 20080120218 | Reid et al. | May 2008 | A1 |
| 20080126261 | Lovett | May 2008 | A1 |
| 20080133350 | White et al. | Jun 2008 | A1 |
| 20080133351 | White et al. | Jun 2008 | A1 |
| 20080134228 | Dion et al. | Jun 2008 | A1 |
| 20080147731 | Narayana et al. | Jun 2008 | A1 |
| 20080154703 | Flake et al. | Jun 2008 | A1 |
| 20080154704 | Flake et al. | Jun 2008 | A1 |
| 20080154727 | Carlson | Jun 2008 | A1 |
| 20080162258 | Kala et al. | Jul 2008 | A1 |
| 20080162269 | Gilbert | Jul 2008 | A1 |
| 20080167991 | Carlson et al. | Jul 2008 | A1 |
| 20080167992 | Kokernak et al. | Jul 2008 | A1 |
| 20080177602 | Sopher et al. | Jul 2008 | A1 |
| 20080184117 | Alsbury et al. | Jul 2008 | A1 |
| 20080195465 | Redmond et al. | Aug 2008 | A1 |
| 20080195473 | Laramy et al. | Aug 2008 | A1 |
| 20080201226 | Carlson et al. | Aug 2008 | A1 |
| 20080215436 | Roberts | Sep 2008 | A1 |
| 20080217397 | Degliantoni et al. | Sep 2008 | A1 |
| 20080221972 | Megdal et al. | Sep 2008 | A1 |
| 20080235243 | Lee et al. | Sep 2008 | A1 |
| 20080242317 | Abhyanker | Oct 2008 | A1 |
| 20080255946 | Altberg et al. | Oct 2008 | A1 |
| 20080275771 | Levine | Nov 2008 | A1 |
| 20080275779 | Lakshminarayanan | Nov 2008 | A1 |
| 20080281668 | Nurminen | Nov 2008 | A1 |
| 20080281699 | Whitehead | Nov 2008 | A1 |
| 20080300973 | DeWitt et al. | Dec 2008 | A1 |
| 20080301037 | Monk | Dec 2008 | A1 |
| 20080301102 | Liang | Dec 2008 | A1 |
| 20080306790 | Otto et al. | Dec 2008 | A1 |
| 20080318559 | Porco | Dec 2008 | A1 |
| 20080319843 | Moser et al. | Dec 2008 | A1 |
| 20080319847 | Shepard | Dec 2008 | A1 |
| 20080320512 | Knight | Dec 2008 | A1 |
| 20090006203 | Fordyce, III | Jan 2009 | A1 |
| 20090006363 | Canny et al. | Jan 2009 | A1 |
| 20090018895 | Weinblatt et al. | Jan 2009 | A1 |
| 20090030793 | Fordyce, III | Jan 2009 | A1 |
| 20090036103 | Byerley et al. | Feb 2009 | A1 |
| 20090043593 | Herbrich et al. | Feb 2009 | A1 |
| 20090043648 | Mahdian et al. | Feb 2009 | A1 |
| 20090048884 | Olives et al. | Feb 2009 | A1 |
| 20090057396 | Barbour et al. | Mar 2009 | A1 |
| 20090070219 | D'Angelo et al. | Mar 2009 | A1 |
| 20090070225 | Matz et al. | Mar 2009 | A1 |
| 20090076896 | DeWitt et al. | Mar 2009 | A1 |
| 20090084842 | Vriheas et al. | Apr 2009 | A1 |
| 20090112703 | Brown | Apr 2009 | A1 |
| 20090112721 | Hammad et al. | Apr 2009 | A1 |
| 20090119160 | Woda et al. | May 2009 | A1 |
| 20090119167 | Kendall et al. | May 2009 | A1 |
| 20090119170 | Hammad et al. | May 2009 | A1 |
| 20090125396 | Otto et al. | May 2009 | A1 |
| 20090132347 | Anderson et al. | May 2009 | A1 |
| 20090132366 | Lam et al. | May 2009 | A1 |
| 20090132395 | Lam et al. | May 2009 | A1 |
| 20090132404 | King et al. | May 2009 | A1 |
| 20090144122 | Ginsberg et al. | Jun 2009 | A1 |
| 20090144146 | Levine et al. | Jun 2009 | A1 |
| 20090144201 | Gierkink et al. | Jun 2009 | A1 |
| 20090144205 | Hurry | Jun 2009 | A1 |
| 20090157511 | Spinnell et al. | Jun 2009 | A1 |
| 20090157512 | King | Jun 2009 | A1 |
| 20090172551 | Kane et al. | Jul 2009 | A1 |
| 20090172728 | Shkedi et al. | Jul 2009 | A1 |
| 20090187462 | Gevelber et al. | Jul 2009 | A1 |
| 20090192882 | Narahashi et al. | Jul 2009 | A1 |
| 20090204472 | Einhorn | Aug 2009 | A1 |
| 20090216579 | Zen et al. | Aug 2009 | A1 |
| 20090216606 | Coffman et al. | Aug 2009 | A1 |
| 20090216616 | Wang et al. | Aug 2009 | A1 |
| 20090222323 | Kelly et al. | Sep 2009 | A1 |
| 20090234708 | Heiser, II et al. | Sep 2009 | A1 |
| 20090234711 | Ramer et al. | Sep 2009 | A1 |
| 20090234715 | Heiser, II et al. | Sep 2009 | A1 |
| 20090234737 | Sarelson et al. | Sep 2009 | A1 |
| 20090248496 | Hueter et al. | Oct 2009 | A1 |
| 20090248497 | Hueter | Oct 2009 | A1 |
| 20090248511 | Mehta et al. | Oct 2009 | A1 |
| 20090249384 | Fang et al. | Oct 2009 | A1 |
| 20090254414 | Schwarz et al. | Oct 2009 | A1 |
| 20090254476 | Sharma et al. | Oct 2009 | A1 |
| 20090259518 | Harvey et al. | Oct 2009 | A1 |
| 20090271262 | Hammad | Oct 2009 | A1 |
| 20090271305 | Lal et al. | Oct 2009 | A1 |
| 20090271327 | Lal et al. | Oct 2009 | A1 |
| 20090276317 | Dixon et al. | Nov 2009 | A1 |
| 20090299846 | Brueggemann et al. | Dec 2009 | A1 |
| 20090300490 | Lejano et al. | Dec 2009 | A1 |
| 20090327892 | Douillet et al. | Dec 2009 | A1 |
| 20100030644 | Dhamodharan | Feb 2010 | A1 |
| 20100042517 | Paintin et al. | Feb 2010 | A1 |
| 20100049620 | Debow | Feb 2010 | A1 |
| 20100057549 | Boal | Mar 2010 | A1 |
| 20100057586 | Chow | Mar 2010 | A1 |
| 20100094694 | Shapiro | Apr 2010 | A1 |
| 20100106568 | Grimes | Apr 2010 | A1 |
| 20100106569 | Grimes | Apr 2010 | A1 |
| 20100114677 | Carlson et al. | May 2010 | A1 |
| 20100114683 | Wessels et al. | May 2010 | A1 |
| 20100114686 | Carlson et al. | May 2010 | A1 |
| 20100121726 | Coulter et al. | May 2010 | A1 |
| 20100121727 | Butler | May 2010 | A1 |
| 20100121767 | Coulter et al. | May 2010 | A1 |
| 20100153242 | Preston et al. | Jun 2010 | A1 |
| 20100161379 | Bene et al. | Jun 2010 | A1 |
| 20100161404 | Taylor et al. | Jun 2010 | A1 |
| 20100161457 | Katz et al. | Jun 2010 | A1 |
| 20100174607 | Henkin et al. | Jul 2010 | A1 |
| 20100174623 | McPhie et al. | Jul 2010 | A1 |
| 20100191594 | White et al. | Jul 2010 | A1 |
| 20100211469 | Salmon et al. | Aug 2010 | A1 |
| 20100250338 | Banerjee et al. | Sep 2010 | A1 |
| 20100274625 | Carlson | Oct 2010 | A1 |
| 20100274627 | Carlson | Oct 2010 | A1 |
| 20100280880 | Faith et al. | Nov 2010 | A1 |
| 20100280881 | Faith et al. | Nov 2010 | A1 |
| 20100280882 | Faith et al. | Nov 2010 | A1 |
| 20100280927 | Faith et al. | Nov 2010 | A1 |
| 20100280950 | Faith et al. | Nov 2010 | A1 |
| 20100306029 | Jolley | Dec 2010 | A1 |
| 20100306032 | Jolley | Dec 2010 | A1 |
| 20110016103 | Sivakumar et al. | Jan 2011 | A1 |
| 20110022424 | VonDerheide | Jan 2011 | A1 |
| 20110035278 | Fordyce, III et al. | Feb 2011 | A1 |
| 20110035280 | Fordyce, III et al. | Feb 2011 | A1 |
| 20110035288 | Clyne | Feb 2011 | A1 |
| 20110047072 | Ciurea | Feb 2011 | A1 |
| 20110087519 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110087530 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110087531 | Winters et al. | Apr 2011 | A1 |
| 20110087546 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110087547 | Amaro et al. | Apr 2011 | A1 |
| 20110087550 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110093324 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110093327 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110093335 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110106607 | Alfonso et al. | May 2011 | A1 |
| 20110106840 | Barrett et al. | May 2011 | A1 |
| 20110125565 | MacIlwaine et al. | May 2011 | A1 |
| 20110276383 | Heiser, II et al. | Nov 2011 | A1 |
| 20110288918 | Cervenka et al. | Nov 2011 | A1 |
| 20110302022 | Fordyce, III et al. | Dec 2011 | A1 |
| 20110302036 | Fordyce, III et al. | Dec 2011 | A1 |
| 20110302039 | Fordyce, III et al. | Dec 2011 | A1 |
| 20120041808 | Hofer et al. | Feb 2012 | A1 |
| 20120101881 | Taylor et al. | Apr 2012 | A1 |
| 20120109709 | Fordyce, III et al. | May 2012 | A1 |
| 20120109734 | Fordyce, III et al. | May 2012 | A1 |
| 20120150601 | Fisher | Jun 2012 | A1 |
| 20120185315 | VonDerheide et al. | Jul 2012 | A1 |
| 20120191525 | Singh et al. | Jul 2012 | A1 |
| 20120209679 | Casares | Aug 2012 | A1 |
| 20120215610 | Amaro et al. | Aug 2012 | A1 |
| 20120271697 | Gilman et al. | Oct 2012 | A1 |
| 20140040051 | Ovick | Feb 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 2000357204 | Dec 2000 | JP |
| 2001175761 | Jun 2001 | JP |
| 2003108897 | Apr 2003 | JP |
| 2006301866 | Nov 2006 | JP |
| 2007102340 | Apr 2007 | JP |
| 2007317209 | Dec 2007 | JP |
| 1020000037128 | Jul 2000 | KR |
| 20020074271 | Sep 2002 | KR |
| 20030080797 | Oct 2003 | KR |
| 20040040253 | May 2004 | KR |
| 20040107715 | Dec 2004 | KR |
| 1020050024746 | Mar 2005 | KR |
| 1020070043329 | Apr 2005 | KR |
| 20050078135 | Aug 2005 | KR |
| 20050089523 | Sep 2005 | KR |
| 20060034983 | Apr 2006 | KR |
| 20060095895 | Sep 2006 | KR |
| 20070030415 | Mar 2007 | KR |
| 20070070588 | Jul 2007 | KR |
| 20070075986 | Jul 2007 | KR |
| 100761398 | Sep 2007 | KR |
| 20070088955 | Dec 2007 | KR |
| 20080104398 | Dec 2008 | KR |
| 100883700 | Feb 2009 | KR |
| 1020090016353 | Feb 2009 | KR |
| 1020090059922 | Jun 2009 | KR |
| 1999022328 | May 1999 | WO |
| 1999050775 | Oct 1999 | WO |
| 2000060435 | Oct 2000 | WO |
| 2000062231 | Oct 2000 | WO |
| 2001037183 | May 2001 | WO |
| 2001039023 | May 2001 | WO |
| 2001057758 | Aug 2001 | WO |
| 2001086378 | Nov 2001 | WO |
| 2001093161 | Dec 2001 | WO |
| 2002005116 | Jan 2002 | WO |
| 2002014985 | Feb 2002 | WO |
| 2002019229 | Mar 2002 | WO |
| 2002042970 | May 2002 | WO |
| 2002071187 | Sep 2002 | WO |
| 2003025695 | Mar 2003 | WO |
| 2003043333 | May 2003 | WO |
| 2003081376 | Oct 2003 | WO |
| 2005001631 | Jan 2005 | WO |
| 2005031513 | Apr 2005 | WO |
| 2005076181 | Aug 2005 | WO |
| 2006028739 | Mar 2006 | WO |
| 2006126205 | Nov 2006 | WO |
| 2007131258 | Nov 2007 | WO |
| 2007136221 | Nov 2007 | WO |
| 2008013945 | Jan 2008 | WO |
| 2008023912 | Feb 2008 | WO |
| 2008028154 | Mar 2008 | WO |
| 2008052073 | May 2008 | WO |
| 2008055217 | May 2008 | WO |
| 2008064343 | May 2008 | WO |
| 2008067543 | Jun 2008 | WO |
| 2008121286 | Oct 2008 | WO |
| 2008144643 | Nov 2008 | WO |
| 2010017247 | Feb 2010 | WO |
| 2010141270 | Dec 2010 | WO |
| 2011017613 | Feb 2011 | WO |
| Entry |
|---|
| Bump, General FAQ's Feb. 8, 2011. |
| Carini, Robert, “Oracle's Complete Sell-Side E-Commerce Solution,” Apr. 30, 2008, 20 pages, available at http://www.oracle.com/us/products/applications/siebel/self-service-ebilling/038547.pdf. |
| Cashmore, Pete, “YouTube Ads: You Hate Em,” available at http://mashable.com/2009/04/05/youtube-ads-youhate-em/#, Apr. 5, 2009. |
| CardSelect International Prepares for Launch of Customized Loyalty Platform for Credit Cards. Business Editors. Business Wire [New York] Apr. 5, 2001: 1. |
| Georgiadis, Margo et al., “Smart data, smart decisions, smart profits: the retailer's advantage,” 22 pages, Feb. 8, 2005. Available at http://web.archive.org/web/20050208141921/http://www.mckinsey.com/practices/retail/knowledge/articles/smartdatasmartdecisions.pdf. |
| Google ad words Tracking Codes—Measuring Your Profits, Ad Words Help. Google Corporation—Book Excerpt, pp. 1-2. Retrieved from the Internet by Third Party Jun. 20, 2011: <URL: href=http://adwords.google.com/supportlawlbin/answer.py?hl=en&answer=146309. |
| International Patent Application PCT/US2011/037769, International Search Report and Written Opinion, dated Jan. 9, 2012. |
| International Patent Application PCT/US12/22417, International Search Report and Written Opinion, dated Aug. 9, 2012. |
| International Patent Application PCT/US2009/052766, International Search Report and Written Opinion, dated Mar. 11, 2010. |
| International Patent Application PCT/US2010/036076, International Search Report & Written Opinion, dated Dec. 30, 2010. |
| International Patent Application PCT/US2010/043440, International Search Report and Written Opinion, dated Feb. 24, 2011. |
| International Patent Application PCT/US2010/044449, International Search Report and Written Opinion, dated Mar. 14, 2011. |
| International Patent Application PCT/US2010/044459, International Search Report and Written Opinion, dated Mar. 28, 2011. |
| International Patent Application PCT/US2010/044706, International Search Report and Written Opinion, dated Mar. 25, 2011. |
| International Patent Application PCT/US2010/044779, International Search Report and Written Opinion, dated Mar. 31, 2011. |
| International Patent Application PCT/US2010/044786, International Seach Report and Written Opinion, dated Mar. 17, 2011. |
| International Patent Application PCT/US2010/045082, International Search Report and Written Opinion, dated Feb. 28, 2011. |
| International Patent Application PCT/US2010/050504, International Seach Report and Written Opinion, dated Apr. 21, 2011. |
| International Patent Application PCT/US2010/050923, International Seach Report and Written Opinion, dated Apr. 26, 2011. |
| International Patent Application PCT/US2010/051262, International Seach Report and Written Opinion, dated May 30, 2011. |
| International Patent Application PCT/US2010/051490, International Seach Report and Written Opinion, dated Apr. 21, 2011. |
| International Patent Application PCT/US2010/051853, International Seach Report and Written Opinion, dated Jun. 21, 2011. |
| International Patent Application PCT/US2010/052070, International Search Report and Written Opinion, dated May 31, 2011. |
| International Patent Application PCT/US2010/053061, International Search Report and Written Opinion, dated May 30, 2011. |
| International Patent Application PCT/US2012/031171, International Search Report and Written Opinion, dated Oct. 12, 2012. |
| Li, Wen-Syan, “Knowledge Gathering and Matching in Heterogeneous Databases,” Working Notes of the AAAI Spring Symposium on Information Gathering, pp. 116-1216, Mar. 27, 1995. |
| Loyalty Solutions—Issuing Rewards Services 2008, First Data Corporation. Available at http://www.firstdata.com/downloads/marketing-fs/fd_issuingrewards_ss.pdf |
| Mielikäinen, Taneli, “Privacy Problems with Anonymized Transaction Databases,” 7th International Conference on Discovery Science, pp. 219-229, Oct. 2, 2004. |
| Now You Can Bump iPhones to Connect on Facebook, Twitter and Linkedln Mashable, Feb. 8, 2011. |
| Operating Rules Women, Infants and Children (WIC) Electronic Benefits Transfer (EBT), Dec. 21, 2010. |
| Punj, Girish et al. “Cluster Analysis in Marketing Research: Review and Suggestions for Application,” Journal of Marketing Research, vol. 20, pp. 134-148, May 1983. |
| PayPal on Android Lets You Bump Phones to Send Money, by Sarah Perez, Aug. 6, 2010. |
| Scotiabank Announces Its First All-in-One Card: Integrating Smart Chip Technologies' Loyalty with Credit, Debit, and Micropayments on a Single Smart Card/ PR Newswire [New York]Jul. 31, 2001: 1. |
| Shermach, Kelly. Coalition Loyalty Programs: Finding Strength in Numbers. Card Marketing 5.3 (Apr. 2001 ): 1, 12+. |
| Van Grove, Jennifer, “Are Your Online Video Ads Driving Actual Offline Purchases?”, available at http://mashable.com/2009/05/18/video-impact/#, May 18, 2009. |
| WIC EBT Imp Guide, Oct. 22, 2010. |
| Number | Date | Country | |
|---|---|---|---|
| 20150363810 A1 | Dec 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62012565 | Jun 2014 | US |
