Patent Grant
10685367
At least some embodiments of the present disclosure relate to the processing of payment transactions, such as payments made via credit cards, debit cards, prepaid cards, etc., and the redemption of the benefits of offers, such as coupons, deals, discounts, rewards, etc.
Millions of transactions occur daily through the use of payment cards, such as credit cards, debit cards, prepaid cards, etc. Payment processing systems, involving acquirer systems, issuer systems, transaction handlers to interconnect the acquirer systems and issuer systems, etc., have been developed to facilitate secure and efficient communications among parties involved in the payment transactions.
For example, U.S. Pat. App. Pub. No. 2009/0271262, published Oct. 28, 2009, discloses a first authorization request generated to include split payment data. After the first authorization request message is analyzed using a server computer, a second authorization request message is sent to a first service provider, and a third authorization request message is sent to a second service provider, to facilitate the split payment according to the split payment data.
Offers, such as coupons, deals, discounts, rewards, etc., typically involve benefits that are provided to the recipients of the offers after the redemption requirements of the respective offers are satisfied. A typical requirement involves the purchase of a product or service relevant to the corresponding offer.
Processing payments and offers using substantially separate systems have drawbacks, such as inefficient use of computation resources for security measures and processing, duplicative allocation of computation resources for the separate systems, time delay from the time when redemption requirements of offers are satisfied and the completion of the provisioning of the benefits of the offers, etc.
Some systems have been developed to at least partially integrate the payment processing and the offer processing. For example, U.S. Pat. App. Pub. No. 2011/0125565, published May 26, 2011, discloses a system to associate an offer with an account of a user in a data warehouse, in which a transaction handler is configured to identify a payment transaction in the account for a purchase eligible for the redemption of the offer. If the payment transaction is identified, the transaction handler provides the benefit of the offer to the account of the user via statement credits. For example, U.S. Pat. App. Pub. No. 2009/0112721, published Oct. 28, 2009, discloses a Value-Added Service Engine programmed to determine a benefit associated with a product after receiving transaction information identifying the product and after communicating with a supplier of the product.
U.S. Pat. App. Pub. No. 2010/0312626, published Dec. 9, 2010, discloses a transaction handler configured to receive an authorization request for a discount associated with an electronic coupon for a purchase. The electronic coupon has been received by the merchant to give the discount on a purchase by a consumer. The discount is to be debited from the sponsor account and credited to an account of the merchant.
U.S. Pat. App. Pub. No. 2011/0047019, published Feb. 24, 2011, discloses a transaction handler configured to forward a coupon authorization request message, identifying a sponsor account and a coupon, from a merchant's acquirer to a sponsor account's issuer, and when the coupon is eligible, to forward the corresponding authorization response from the issuer to the acquirer.
U.S. Pat. App. Pub. No. 2008/0133351, published Jun. 5, 2008, discloses a “Method and Apparatus for Reward Messaging, Discounting and Redemption at the Point of Interaction,” in which, upon determining that the transaction is eligible for a discount, the authorization request message is updated to indicate that it is a discount transaction, and this updated authorization request message is then forwarded to the issuer (or issuer processor) for authorization. When a promo code is used by the POS terminal or merchant system to apply or calculate a discount amount at the point of interaction, the full transaction price may be authorized by the issuer, and full transaction price less the discount amount is then cleared and settled between the acquirer and the issuer after the transaction. When a promo code is not used, the authorization system forwards an authorization request message to the issuer for the purchase amount less the discount.
U.S. Pat. App. Pub. No. 2007/0011044, published Jan. 11, 2007, discloses a host system configured to transmit an authorization request to a credit provider. After discounts available for application to the transaction are identified with the host system and from the identifier of a credit instrument, a modified transaction having a total transaction cost reduced by application of at least one of the separate discounts is coordinated between the host system and the merchant.
The disclosures of the above discussed patent documents are hereby incorporated herein by reference.
The present application includes systems and methods configured to further improve the overall system performances, including interoperability, transaction integrity, efficiency in processing payments in combination with offers, time delay in processing, resource allocation, etc., and/or to provide enhanced services.
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.
Introduction
In one embodiment, a gateway of a transaction handler of a payment processing network is configured to receive authorization requests from transaction terminals for transactions in payment accounts. The authorization requests are transmitted from the transaction terminals to the gateway without going through respective acquirer processors. The gateway is configured to determine whether offers in the accounts of the users are applicable to the transactions. The gateway, or a transaction handler, is configured to push the transactions to the acquirer processors, after processing the authorization request in view of the offers. Further details and examples are provided in the section entitled “GATEWAY.”
In one embodiment, a portal coupled to a transaction handler is configured to provide enhanced services related to the presentation of receipts, such as indication of offer benefits redeemed in the transaction. When an enhanced receipt service is available for a transaction approved via an authorization response transmitted to the acquirer processor and the transaction terminal, the authorization response is configured to indicate the availability of the enhanced receipt service. A transaction terminal that is configured to have the capability of communicating with the portal to present the enhanced receipt service can use the indication provided in the authorization response to initiate the communication for enhanced receipt services, and a conventional transaction terminal that lacks the same capability may ignore the indication provided in the authorization response. Thus, the system is compatible with conventional transaction terminals that lack such a capability, while still allowing the utilization of transaction terminals in the same network that supports such a capability and thus can provide enhanced services for users of the respective transaction terminals. Further details and examples are provided in the section entitled “RECEIPT.”
For example, the transaction handler of one embodiment is configured to determine whether a transaction in a payment account, as identified in an authorization request, received from an acquirer processor for the transaction, is eligible for the benefit of an offer associated with the payment account, and if so, split the transaction originally requested in the payment account into two or more transactions with an issuer processor of the payment account and one or more sponsor processors of the offer to apply the benefit of the offer to the authorization request for the transaction requested. The two or more transactions are combined for the transaction terminal of the merchant and/or the acquirer processor, such that the details of the two or more transactions are insulated from the transaction terminal and/or the acquirer processor. Thus, a conventional transaction terminal and/or a conventional acquirer processor can be used in the system configured to apply the benefit of an offer during the processing of a transaction initiated and completed at the transaction terminal. Further details and examples are provided in the section entitled “SPLIT TRANSACTION.”
To facilitate offer redemption via the split-transaction technique as identified above, data associating offers with account information identifying the consumer accounts or payment accounts of the users can be stored in a data warehouse coupled with the transaction handler. For example, in one embodiment of associating offers with consumer/payment accounts, a portal of the transaction handler is configured to store data representing offers, and to associate user selected offers with the financial accounts of the respective users, if the users select advertisements containing the offers. When the financial accounts are used to make payments processed by the transaction handler for purchases that satisfy the respective redemption conditions of the offers, the transaction handler and/or the portal are configured to detect such payment transactions and fulfill the offers in an automated way, such as in the embodiment of the split-transaction identified above.
For example, the advertisement providing the offer can be configured to have multiple selectable regions when the advertisement is presented in a web browser of a user. Examples of offers include discounts, incentives, rebates, coupons, rewards, cash back, etc. One of the selectable-regions contains a Uniform Resource Locator (URL) of the advertiser or merchant, which, when selected, directs the user to the website of the advertiser or merchant. A separate one of the selectable regions contains a Uniform Resource Locator (URL) of the portal of the transaction handler, which, when selected, directs the user to the portal for access to a user interface to register the offer with a financial account of the user. Examples of financial accounts of users include credit card accounts, debit card accounts, prepaid card accounts, bank accounts, etc. Some details and examples about associating offers with financial accounts are provided in the section entitled “OFFER REDEMPTION.”
After the offer is associated with the financial account of the user, the transaction handler and/or the portal are configured to detect that the user is making a payment using the financial account for a purchase that satisfies the redemption requirements of the offer. In response to the detection, the portal may optionally notify the user of the eligibility of the redemption of the offer using a communication reference associated with the financial account, and the transaction handler and/or the portal are configured to automate the processing of the offer for redemption, such as using the split-payment embodiment identified above, or via statement credits to the financial account of the user, or via benefits afforded via a loyalty program, such as reward points, loyalty points, etc. Some details and examples about offer fulfillment operations are provided in the section entitled “OFFER REDEMPTION.”
When an offer is sponsored by the merchant, the transaction handler can be configured in one embodiment to apply the benefit of the registered offer during the authorization and/or settlement of the transaction that meets the requirement for the redemption of the offer via modifying the transaction amount. For example, the authorization amount can be changed by the transaction handler to provide the benefit of the registered offer during the authorization phase of the transaction in one embodiment, and the settlement amount can be changed by the transaction handler to provide the benefit of the registered offer during the settlement phase of the transaction in another embodiment. Some details and examples about redeeming offer benefits via modifying transaction amounts are provided in the section entitled “APPLY OFFER.”
In one embodiment, a transaction terminal is configured to communicate with a portal that couples with a data warehouse storing data associating offers with financial payments accounts. The transaction terminal provides the portal with information about the transaction, such as a financial payment account that is used to make the payment and/or purchase details that identifies the items purchased, quantities of the items purchased, the unit prices of the items purchased, etc. The portal uses the information received from the transaction terminal and the data stored in the data warehouse to determine whether there is an offer applicable to the transaction that is about to be initiated on the transaction terminal using the financial payment account. If there is an applicable offer, the portal provides information about the applicable offer to the transaction terminal, such as the benefit to be applied to the transaction, the identification of the offer, a description of the offer, etc. Based on the response from the portal, the transaction terminal adjusts the transaction amount to initiate an authorization request for a transaction that includes the benefit of the applicable offer. Further details and examples are provided in the section entitled “TRANSACTION TERMINAL AND PORTAL CONNECTION.”
In one embodiment, the delivery of the benefit of an offer is specified and/or performed based on the identity of an issuer of a consumer account with which the offer is associated and using which a transaction qualifying for the offer is performed. Further details and examples are provided in the section entitled “ISSUER IDENTITY.”
Since the transaction handler records the transaction data for transactions made in various purchase channels, such as online marketplaces, offline in retail stores, phone orders, etc., the registered offer can be redeemed in an automated way, without being limited by the channel used to make the purchase and limited by the context of the purchase. Thus, the system provides a normalized, real-time, online and offline, redemption service for offers in combination with, and integrated with, the processing of payment transactions.
The transaction data, such as records of transactions made via credit accounts, debit accounts, prepaid accounts, bank accounts, stored value accounts and the like, can be further processed to optionally provide information for various services, such as reporting, benchmarking, advertising, content or offer selection, customization, personalization, prioritization, etc. In one embodiment of improving privacy protections, users are required to enroll in a service program and provide consent to allow the system to use related transaction data and/or other data for the related services, and the system is configured to provide the services while protecting the privacy of the users in accordance with the enrollment agreement and user consent.
For example, based on the transaction data, an advertising network in one embodiment is provided to present personalized or targeted advertisements/offers on behalf of advertisers. A computing apparatus of, or associated with, the transaction handler uses the transaction data and/or other data, such as account data, merchant data, search data, social networking data, web data, etc., to develop intelligence information about individual customers, or certain types or groups of customers. The intelligence information can be used to select, identify, generate, adjust, prioritize, and/or personalize advertisements/offers to the customers. The transaction handler may be further automated to process the advertisement fees charged to the advertisers, using the accounts of the advertisers, in response to the advertising activities.
Gateway
In one embodiment, a gateway of a transaction handler is configured to receive authorization requests for transactions and to process the authorization request in view of offers associated with payment accounts of the users in the data warehouse of the transaction handler. The direct connection between a transaction terminal and the gateway, bypassing acquirer processors, allows the gateway to provide offer information to the transaction terminal and to receive purchase details that may be used in the determination of the applicability of the offers.
In
The communication channel of one embodiment between the gateway (725) and the transaction terminal (105) may use Internet or wireless connections. The security of the communication channel is enhanced via encrypting sensitive information, such as account information (142) identifying the consumer account (146) in which the transaction identified in the authorization request A (168) is requested.
For example, the account information (142) provided in the authorization request A (168) is combined with a random number, and the combination of the account information (142) and the random number is encrypted for transmission from the transaction terminal (105) to the gateway (725).
In one embodiment, a correlation ID is assigned to the authorization request A (168). The correlation ID is subsequently used in the authorization response A (138) to identify the transaction associated with the authorization request A (168). When the correlation ID is used to uniquely identify the transaction within a time period, the transmission of the account information (142) in the authorization response A (138) can be avoided.
In one embodiment, a plurality of parallel communication channels are used between the gateway (725) and the transaction terminal (105), and the content of the authorization request A (168) is sliced and distributed over the plurality of parallel communication channels, such that even when information transmitted over a subset of the parallel communication channels is compromised, the compromised information does not reveal the details of the authorization request A (168), such as the account information (142).
The authorization request A (168) of one embodiment includes purchase details (169) of the transaction, such as the identification of the items (e.g., products and/or services) purchased via the transaction, the unit prices of the items, the number of units purchased via the transaction, etc. The gateway (725) is configured to store the purchase details (169) in the data warehouse (149) in association with a transaction record (301) of the transaction identified by the authorization request A (168).
The applicability of the offer (186) of one embodiment to the transaction identified by the authorization request A (168) is based on the purchase details (169). For example, the offer (186) of one embodiment is applicable to the transaction when the purchase details (169) include the identification of a specific item, an item from a specific manufacturer, and/or an item having a specific unit price, etc., and not applicable when the purchase details (169) do not meet a respective condition of the offer (186). Since such information about purchase details (169) may not be available in an authorization request communicated from a transaction terminal (e.g., 105) to the transaction handler (103) via an acquirer processor (e.g., 147), the communication channel between the gateway (725) and the transaction terminal (105), as illustrated in
In
For example, when the benefit of the offer (186) is controlled by a sponsor processor (649), the gateway (725) is configured to communicate with the transaction handler (103) to transmit an authorization request C (645) for the benefit of the offer (186) to the sponsor processor (649), and to transmit an authorization request B (641) to the issuer processor (145) of the consumer account (146) for the authorization of a transaction amount, which is the difference between the transaction amount specified in the authorization request A (168) received from the transaction terminal (105) and the benefit of the offer (186). When the sponsor processor (649) in control of the benefit of the offer (186) and the issuer processor (145) in control of the consumer account (146) approve the respective authorization requests (645 and 641) via the respective authorization responses (647 and 643), the gateway (725) provides to the transaction terminal (105) the authorization response A (138) with offer information (721).
In one embodiment, the transaction handler (103) (and/or the gateway (725)) is configured to combine the authorization response B (643) from the issuer processor (145) and the authorization response C (647) from the sponsor processor (649) to generate the authorization response A (138), in a way discussed in the section entitled “SPLIT TRANSACTION.”
The offer information (721) of one embodiment is configured to identify the application of the benefit of the offer (186) to the transaction requested by the authorization request A (168), such that the receipt generated by the transaction terminal (105) includes the offer information (721).
For example, the offer information (721) of one embodiment includes an optional receipt service indication (681), illustrated in
In
In one embodiment, the gateway (725) and the portal (143) are combined. Alternatively, separate components are used to implement the gateway (725) and the portal (143).
The offer (186) of one embodiment is sponsored by the merchant operating the transaction terminal (105). To process such an offer (186), the gateway (725) acts as the sponsor processor (649) to approve the awarding of the benefit of the offer (186) to the transaction requested by the authorization request A (168), in accordance with the terms and conditions of the offer (186). After deducting the benefit of the offer (186) from the transaction amount specified in the authorization request A (168) received from the transaction, the transaction handler (103) is configured to communicate with the issuer processor (145) for the authorization of a reduced transaction amount, and if the reduced transaction amount is approved by the issuer processor (145), the authorization response A (138) transmitted to the transaction terminal (105) is configured to identify an approved transaction amount that is smaller than the full transaction amount initially specified in the authorization request A (168). The offer information (721) identifies, as the benefit of the applicable offer (186), the difference between the transaction amount specified in the authorization request A (168) received from the transaction terminal (105) and the transaction amount approved in the authorization response A (138) provided to the transaction terminal (105).
Details and examples of applying offer benefits via changing transaction amount in one embodiment are provided in the section entitled “APPLY OFFER.”
In
In an alternative embodiment, the gateway (725) is not directly connected with the transaction handler (103). In such an alternative embodiment, after the benefit of the offer (186) is applied to the transaction request A (168) (e.g., by reducing the transaction amount in accordance with the offer (186)), the gateway (725) transmits the adjusted authorization request to the acquirer processor (147), which processes the adjusted authorization request in a way as illustrated in
In
In
For example, to indirectly cause the transaction handler (103) to submit the authorization request C (645), the gateway (725) is configured in one embodiment to generate a trigger record (613) in response to a determination that the transaction corresponding to the authorization request A (168) has an applicable benefit. The trigger record (613) is configured to instruct the transaction handler (103) to generate authorization request C (645) for the authorization request, received directly from the gateway (725) or indirectly from the gateway via the acquirer processor (147), for the respective transaction.
For example, the authorization request of one embodiment submitted by the gateway (725) may explicitly include an indicator that causes the transaction handler (103) to contact both the sponsor processor (649) of the benefit of the offer (186) and the issuer processor (145) of the consumer account (146) for the authorization response B (643) and the authorization response C (647).
In one embodiment, the gateway (725) is configured to split the transaction identified by the authorization request A (168) received from the transaction terminal (105) into two (or more) transactions, including a transaction in the consumer account (146) and one or more transactions for applying the benefit of the offer (186) controlled by the sponsor processors (e.g., 649) (and/or the gateway (725)). The gateway (725) is configured to combine the authorizations of the respective transactions, generated by the gateway (725), to generate the single authorization response A (138) for the transaction terminal (105). In such a split transaction embodiment, the gateway (725) and the transaction handler (103) process the one or more transactions for applying the benefit of the offer (186) directly, or requesting authorization of the benefit of the offer (186) (e.g., via communications (e.g., 645 and 647) with the sponsor processors (e.g., (649))), without involving the acquirer processor (147) in the application of the benefit, and after the consideration of the applicable offers (e.g., 186), the gateway (725) acts like a transaction terminal (e.g., 105) to submit, to the acquirer processor (147), an authorization request for the transaction in the consumer account (146) for the transaction amount reduced by the benefit of the offer (186), if there is any. Since the acquirer processor (147) may communicate with a different transaction handler for transactions in consumer accounts not in the payment processing network of the transaction handler (103), such a configuration allows the benefit of the offer (186) to be applied to the transaction on-the-fly via the use of the gateway (725), even when the consumer account of the applicable offer (186) is under the control of an out-of-network issuer processor associated with a separate transaction handler different from the transaction handler (103). Thus, when the payment is made via a financial payment account of a different financial payment processing network that uses a transaction handler different from the transaction handler (103) connected to the data warehouse (149), the benefit of the offer (186) hosted in the data warehouse (149) of the transaction handler (103) can still be applied to the payment transaction via the gateway (725).
In one embodiment, the gateway (725) is combined with the portal (143) to include at least some of the functions described in connection with the receipt presentation in the section entitled “RECEIPT,” such as the presentation of user interfaces to allow the user (101) to select a mini receipt or suppress paper receipts in view of electronic receipts, to allow the user (101) to enroll in an offer campaign, accept an offer, redeem loyalty/reward points, etc., during the presentation of the receipt or the authorization of the transaction, storing a copy of the receipt, and/or providing additional services based on the receipt and/or the purchase details (169), such as warranty bookkeeping, recall notification, etc.
In one embodiment, the authorization response A (138) includes various information about the consumer account (146) for presentation with the receipt of the transaction, such as the account type of the consumer account (146); the reward level of the consumer account (146); a message pre-selected by the user (101); the account balance of the consumer account (146); the loyalty/reward benefits accumulated for the consumer account (146); conditions that have been satisfied for redemption of the benefit of the offer (186) stored in association with the consumer account (146); the logo of the issuer of the consumer account (146); the logo of the sponsor of the offer (186) redeemed in the transaction; the logo of the merchant operating the transaction terminal (105); the logo of an entity operating the transaction handler (103); a piece of music representative of the issuer, the sponsor, the merchant, or the entity operating the transaction handler (103); etc. The transaction terminal (105) is configured to present such information provided in the authorization response A (138) prior to, or in connection with, the presentation of the receipt of the transaction.
The computing device can be implemented using one or more data processing systems as illustrated in
In one embodiment, the computing apparatus includes at least one of: the gateway (725) illustrated in
The computing device can be further implemented, optionally, to perform other operations discussed below, such as the operations discussed in the section entitled “TRANSACTION DATA BASED SERVICES.” Some of the hardware arrangements are discussed in the sections entitled “CENTRALIZED DATA WAREHOUSE” and “HARDWARE.”
For example, the transaction handler (103) discussed above can be used to record transaction data (109) to provide transaction data based services as illustrated in
Receipt
The receipt service indicator (681) of one embodiment is an optional field, which can be ignored by a transaction terminal (105) that does not support the service that requires an out-of-band communication connection between the transaction terminal (105) and the portal (143) of the transaction handler (103). Thus, the authorization response (e.g., 138), including the receipt service indicator, (681) is compatible with a legacy transaction terminal (105).
In
In
In
For example, when an offer (186), associated with account information (142) in the data warehouse (149) coupled with the portal (143) and the transaction handler (103), is determined to be applicable to the transaction identified by the authorization request (168), the transaction handler (103) is configured to apply the benefit of the offer (186) to the transaction. The transaction handler (103) may use one of the methods identified in the present disclosure to apply the benefit of the offer (186), such as those discussed in the sections entitled “SPLIT TRANSACTION,” “OFFER REDEMPTION,” “APPLY OFFER,” or other methods known in the field.
In
In
The receipt response (685) of one embodiment includes an electronic version of the receipt, and the transaction terminal (105) is configured to print the electronic version of the receipt for presentation to the user (101).
The receipt response (685) of one embodiment includes additional content to be included in the receipt generated by the transaction terminal (105), and the transaction terminal (105) is configured to insert the content at a predetermined location in the receipt generated by the transaction terminal (105), or at a location selected from a plurality of optional, predefined receipt locations.
For example, the additional content to be inserted in the receipt produced by the transaction terminal (105) may identify the benefit amount, the transaction amount in the authorization response (643) charged to the consumer account (146) of the user (101), and/or other information, such as an advertisement from the sponsor, a summary of the offer (186), progress statuses of the offer (186), a balance of the loyalty/reward points accumulated for the consumer account (146) (illustrated in
The receipt response (685) of one embodiment is configured to include a message identifying the application of the benefit of the offer (186) to the transaction, showing the reduced transaction amount approved by the authorization response (643) from the issuer processor (145), and/or information about the offer (186), such as an advertisement from the sponsor of the offer (186). Thus, the receipt produced on the transaction terminal (105) confirms the application of the offer (186) to the current transaction approved via the authorization response (138).
In one embodiment, the portal (143) is configured to provide an enhanced receipt service by delivering a version of the receipt electronically, using the communication reference (611) associated with the account information (142) of the user (101). For example, the electronic receipt can be transmitted to the user (101) via SMS, email, a social networking site, a digital wallet, a financial service site, a financial service software, etc., using the communication reference (611).
The portal (143) may allow the user (101) to specify a preference with regards to the receipt. For example, a receipt option in one embodiment allows the user (101) to receive an electronic version of the full receipt at the point of interaction (107) identified by the communication reference (611) and suppresses the printing of a paper version of the receipt at the transaction terminal (105).
For example, a receipt option in one embodiment allows the user (101) to receive an electronic version of the full receipt at the point of interaction (107) and receive a mini paper receipt at the transaction terminal (105). In one embodiment, the mini paper receipt omits purchase details (169) of the payment and indicates the transaction amount that is charged to the consumer account (146) and the benefit amount provided by the offer (186). In one embodiment, the mini paper receipt is configured to make a reference to the electronic version of the receipt transmitted to the point of interaction (107) at the communication reference (611) and omit further details that are presented in the electronic version of the receipt.
The transaction terminal (105) of one embodiment is configured to display the receipt response (685) on a display device, suppressing the paper receipt.
The transaction terminal (105) can be optionally configured to present a user interface that provides a set of options to allow the user (101) to suppress the full paper receipt, to print a mini paper receipt, and/or to specify a destination for the electronic receipt.
The transaction terminal (105) can be optionally configured to transmit to the portal (143) the purchase details (169) in the receipt request (683), and the portal (143) is configured to store the purchase details (169) as part of, or in association with, the transaction record (301) of the transaction approved by the authorization response (138).
Using the purchase details (169), the portal (143) can be optionally configured to generate the receipt response (685) in the form of a full receipt including the purchase details (169). The transaction terminal (105) can be optionally configured to present the receipt response (685) in a user interface and allow the user (101) to preview the receipt on the transaction terminal (105), to suppress the printing of the full paper receipt prior to the user (101) selecting an option, to print a portion of the receipt as the mini paper receipt, and/or to direct the portal (143) to transmit the electronic receipt to the point of interaction (107).
The portal (143) is optionally configured in one embodiment to store a copy of the receipt and/or the purchase details (169) in the data warehouse (149) and provide additional services based on the receipt and/or the purchase details (169), such as warranty bookkeeping, recall notification, etc.
The portal (143) is optionally configured in one embodiment to use the receipt response (685) to further direct the transaction terminal (105) to provide relevant information and/or receive input from the user (101).
For example, the portal (143) of one embodiment is configured to use the receipt response (685) to direct the transaction terminal (105) to prompt the user (101) to redeem loyalty/reward points accumulated in connection with the consumer account (146) identified by the account information (142) for the present transaction approved by the authorization response (138), in a next transaction involving the account information (142).
For example, the user (101) may select a number of loyalty/reward points in exchange for a further offer (186) that can be applied to the next payment transaction with the same merchant, or a different merchant.
For example, the user (101) may request the transaction handler (103) to apply a number of loyalty/reward points to the transaction approved by the authorization response (138) during the settlement of the transaction.
In one embodiment, after the user (101) selects/accepts a loyalty/reward points redemption offer (186), the user (101) is enrolled in a recurring offer redemption program, in which when the balance of loyalty/reward points is above a threshold, a new loyalty/reward points redemption offer (186), substantially identical or similar to the redemption offer previously selected/accepted by the user (101), is automatically generated and associated with the account information (142) of the user (101) for automated redemption in a subsequent qualified transaction (e.g., a transaction that satisfies the benefit redemption requirement of the new loyalty/reward points redemption offer (186)). For example, if the user (101) selects a previous loyalty/reward points redemption offer (186) that allows the user (101) to apply a predetermined number of loyalty/reward points as a part of the payment for a transaction with a predetermined merchant where the transaction amount is above a predetermine threshold, the new loyalty/reward points redemption offer (186) is automatically associated with the account information (142) for the user (101) in the data warehouse (149) when the balance of the loyalty/reward points of the user (101) is above a threshold, and the new loyalty/reward points redemption offer (186) allows the user (101) to apply the same predetermined number of loyalty/reward points as a part of the payment for a future transaction of an amount above the same threshold with the same predetermined merchant. In one embodiment, the same loyalty/reward points redemption offer (186) is generated automatically, based on the point balance of the user (101), until the user (101) selects/accepts a different loyalty/reward points redemption offer (186), which is then used as a template for future automated, recurring loyalty/reward points redemption offers (186). In one embodiment, the offer (186) provides the benefit for loyalty/reward points redemption according to a predetermined set of rules and conditions, and when the loyalty/reward points balance of the user (101) is above a threshold, the trigger record (613) is generated for the offer (186) to allow the detection of a transaction that satisfies the conditions of the offer (186) and the application of the benefit of the offer (186) to the detected transaction.
The portal (143) is optionally configured in one embodiment to present a new offer (186) to the user (101) via the receipt response (685) and receive user selection to accept the new offer (186), or participate in the respective offer campaign.
The portal (143) is optionally configured in one embodiment to use the receipt response (685) to present various information about the consumer account (146), such as the account type of the consumer account (146); the reward level of the consumer account (146); a message pre-selected by the user (101); the account balance of the consumer account (146); the loyalty/reward benefits accumulated for the consumer account (146); conditions that have been satisfied for redemption of the benefit of the offer (186) stored in association with the consumer account (146); the logo of the issuer of the consumer account (146); the logo of the sponsor of the offer (186) redeemed in the transaction; the logo of the merchant operating the transaction terminal (105); the logo of an entity operating the transaction handler (103); a piece of music representative of the issuer, the sponsor, the merchant, or the entity operating the transaction handler (103); etc.
In one embodiment, the transaction terminal (105) is configured to communicate with the portal (143) using a communication channel (e.g., the Internet) that is not physically secured. To secure the communication between the transaction terminal (105) and the portal (143), the transaction terminal (105) is configured to encrypt at least account information (142) used to identify the consumer account (146) for the transaction. For example, in one embodiment, the account information (142) used to identify the consumer account (146) in the receipt request (683) is combined with a random number and encrypted for transmission through the communication channel between the transaction terminal (105) and the portal (143).
In one embodiment, the transaction terminal (105) is optionally configured to further attach an identification number to the encrypted version of the account information (142) in the receipt request (683), and the portal (143) uses the identification number in the receipt response (685) to identify the receipt request (683).
To enhance communication security, the transaction terminal (105) and the portal (143) use multiple, separate channels in one embodiment. Each of the channels is used to carry a portion of the communications between the transaction terminal (105) and the portal (143). Thus, even if the security of one of the communication channels is compromised, the security of the content transmitted between the terminal (105) and the portal (143) is not compromised.
In one embodiment, the receipt request (683) and/or the receipt response (685) is secured via data transmitted via the authorization request (168) and/or the authorization response (138). For example, in one embodiment, the receipt service indicator (681) includes a code that is used to scramble or encrypt the receipt request (683) and/or the receipt response (685). For example, in one embodiment, a portion of the content to be transmitted from the transaction terminal (105) is transmitted to the portal (143) via an authorization request (168) and the transaction handler (103), and the portal (143) is configured to combine the portion of the content received via the acquirer processor (147), the transaction handler (103) and the receipt request (683) to recover the content to be transmitted from the transaction terminal (105). The recovered content may include the account information (142) identifying the consumer account (146) and/or the purchase details (169).
If the computing apparatus determines (725) that the authorization response (138) has a receipt service indicator (681) that is set to indicate an enhanced receipt, the computing apparatus communicates (729) with a portal (143) of the transaction handler (103) to obtain receipt content (e.g., via the receipt request (683) and the receipt response (685) transmitted via a communication channel separate from the communication channel used to communicate with the acquirer processor (147)).
In one embodiment, in the communication session for receipt content, the computing apparatus determines whether user interaction (731) is requested, and if so, the computing apparatus communicates (733) with the portal (143) to provide a user interface on the transaction terminal (105) to display content and receive input in accordance with requests from the portal (143).
If the computing apparatus determines (725) that no enhanced receipt is to be provided, the computing apparatus is configured to generate (727) a receipt based on the authorization response (138).
In one embodiment, the computing apparatus includes at least one of: the transaction terminal (105), the transaction handler (103), the portal (143) and the data warehouse (149), as illustrated in
Split Transaction
In
In
Further, in
In
In
Since requirements used in the trigger records (613) are in the standardized set, the operation of the transaction handler (103) in determining whether an action requested in the trigger record (613) is triggered by the authorization request (168) can be optimized for performance improvement, while supporting a variety of diverse services corresponding to actions that can be specified in trigger records (e.g., 613), such as the processing of the benefit redemptions of different offers that may have diverse redemption requirements. The use of the standardized set of requirements for trigger records (613) can reduce and limit the performance impact on the transaction handler (103) in processing payment transactions, since not all requirements are initially examined by the transaction handler (103) and the standardization permits optimized operation efficiency.
In
The system illustrated in
Further, the system as illustrated in
In
In
The offer (186) specifies a set of conditions, which, when satisfied, allow a benefit sponsored by the sponsor processor (649) to be applied to the respective transaction. Thus, when the authorization request (168) satisfies the trigger record (613) generated for the offer (186), the transaction handler (103) and/or the portal (143) (or a separate processor coupled with the transaction handler (103)) is configured to determine whether the entire set of the conditions of the offer (186) is satisfied for the award of the benefit to the respective transaction, in view of the authorization request (168) received from the acquirer processor (147).
If the benefit of the offer (186) is determined to be applicable to the transaction corresponding to the authorization request (168), the transaction handler (103) communicates an authorization request (645) to the sponsor processor (649) for the authorization of an amount to be applied to the transaction initiated on the transaction terminal (105), and separately communicates an authorization request (641) to the issuer processor (145) for the authorization of an amount from the consumer account (146) identified via the account information (142) submitted by the transaction terminal (105) to initiate the respective transaction.
In one embodiment of the generation of the authorization requests (e.g., 641, 645), the transaction handler (103) (or the portal (143), or a separate processor coupled with the transaction handler (103)) is configured to determine the transaction amounts for the authorization requests (645 and 641) based on the transaction amount requested in the authorization request (168) received from the acquirer processor (147) and the benefit specified in the offer (186).
In
In
Thus, the transaction handler (103) effectively splits the transaction corresponding to the authorization request (168) received from the acquirer processor (147) into two transactions corresponding to the authorization requests (641 and 645) to the issuer processor (145) and the sponsor processor (649), respectively.
In
In
Since the authorization responses (647 and 643) are combined by the transaction handler (103) to generate a single authorization response (138) for the acquirer processor (147), the implementation details of the application of the offer (186) are separate from the transaction terminal (105), and thus a conventional transaction terminal (105) can be used to apply the benefit of the offer (186) to the eligible transaction, without a need for modification in hardware and/or software. The transaction terminal (105) submits the transaction authorization request (168) and receives the authorization response (138), as if the transaction were processed using the consumer account (146), as identified by the account information (142), and as if the transaction were processed without the involvement of the offer (186) and/or the sponsor processor (649).
The transaction terminal (105) of one embodiment has no information about the application of the benefit of the offer (186) to the transaction initiated and approved on the transaction terminal (105). The transaction terminal (105) thus produces a receipt, which may be interpreted to indicate that the entire transaction amount is funded by the consumer account (146) identified by the account information (142). To inform the user (101) of the applicable benefit of the offer (186), the portal (143) is configured to generate and send a message to the point of interaction (107) (e.g., a mobile phone, a mobile computer, a personal media player, a personal digital assistant, a tablet computer, a digital wallet, a social networking site, an email inbox, etc.) identified by the communication reference (611) associated with the account information (142) of the user (101).
For example, a text message is transmitted in accordance with the communication reference (611) to a mobile phone of the user (101) to inform the user (101) of the application of the benefit of the offer (186) to the transaction initiated and approved on the transaction terminal (105). Alternatively or in combination, the notification about the awarded/redeemed benefit of the offer (186) can be transmitted via an email message, a web-based message, a voice message, etc.
The portal (143) of one embodiment is configured to transmit the notification message about the award/redemption of the benefit of the offer (186) in response to the authorization responses (641 and 645) from the issuer processor (145) and the sponsor processor (649), prior to or in parallel with the transmission of the authorization response (138) to the acquirer processor (147). Thus, the transmission of the notification is substantially concurrent with the propagation of the authorization of the transaction to the transaction terminal (105). As a result, the delay to the user reception of the notification is reduced.
The transaction handler (103) is configured in one embodiment to further settle the transactions corresponding to the authorization responses (643 and 647) from the issuer processor (145) and the sponsor processor (649) to effectively complete the transaction corresponding to the authorization response (138) to the acquirer processor (147).
In
In
If the offer (186) is applicable (655) to the first transaction amount, the computing device is configured to determine (657) a second transaction amount applicable to the consumer account (146) according to the offer (186) and the first transaction amount, and determine (671) a third transaction amount applicable to a sponsor account according to the offer (186). The computing device communicates (673) with the sponsor processor (649) to obtain an authorization response (647) for the third transaction amount, and communicates (659) with the issuer processor (145) to obtain an authorization response (643) for the second transaction amount.
If the computing device determines (661) that the offer (186) is applicable to the authorization request (168) received from the acquirer processor (147), the computing device is configured to combine (663) the responses (641 and 647) from the issuer processor (145) and the sponsor processor (649) to generate the authorization response (138) to the acquirer processor (147), and transmit (669) a notification about the benefit of the second transaction amount afforded by the offer (186), using the communication reference (611).
If the computing device determines (661) that the offer (186) is not applicable to the authorization request (168) received from the acquirer processor (147), the computing device is configured to generate (665) the authorization response (138) based on the authorization response (643) from the issuer processor (145).
The computing device communicates (667) the authorization response (138) for the first transaction amount to the acquirer processor (147), as a response to the authorization request (168) received from the acquirer processor (147).
Since the transaction terminal (105) is arranged to process the transactions that may or may not involve the redemption of the benefit of the offers (e.g., 186) in a conventional way, the system can be used with conventional transaction terminals (e.g., 105) without modification.
Preferably, the authorization requests (e.g., 168, 641, 645) and the authorization responses (e.g., 138, 643, 647) are in accordance with existing standards, and thus the system can be used with existing acquirer processors (e.g., 147) and issuer processors (e.g., 145) without modifications.
The computing device of one embodiment includes at least one of: the data warehouse (149), the transaction handler (103), and the portal (143). For example, the warehouse (149) is configured to store data associating the offer (186), the account information (142), and the communication reference (611), as illustrated in
In one embodiment, the computing apparatus is configured, at least in part via instructions, to: receive an authorization request (e.g., 168) identifying a transaction of a first amount in an account (e.g., 146) of a user (e.g., 101); and determine, based on data (e.g., 186 and 142) stored to associate an offer with the account, whether a benefit of the offer (e.g., 186) is applicable to the transaction. In response to a determination that the benefit of the offer is applicable to the transaction, the computing apparatus is further configured to: communicate with a sponsor processor (e.g., 649) of the benefit for authorization of the benefit of a second amount; communicate with an issuer processor (e.g., 145) of the account for authorization to a third amount determined from a difference between the first amount and the second amount; and generate a third authorization response (e.g., 138) for the authorization request based on a first authorization response (e.g., 647) for the second amount from the sponsor processor (e.g., 649) and a second authorization response (e.g., 643) for the third amount from the issuer processor (e.g., 145).
The authorization request (e.g., 168) may be received from an acquirer processor (e.g., 147) and the authorization response (e.g., 138) transmitted to the acquirer processor (e.g., 147) as a response to the authorization request (e.g., 168), where the authorization request (e.g., 168) identifies the account (e.g., 146) as a single source of payment for the transaction.
If the authorization request (168) is referred to as a third authorization request, in communicating with the sponsor processor (649) the computing apparatus is configured in one embodiment to transmit to the sponsor processor (649) a first authorization request (645) identifying the benefit and receive the first authorization response (647); and in communicating with the issuer processor (145) the computing apparatus is configured to transmit to the issuer processor (145) a second authorization request (641) identifying a second transaction amount in the account and receive the second authorization response (643).
If the third authorization request (168) identifies a third transaction amount in the account, the computing apparatus is configured in one embodiment to determine the second transaction amount by reducing the third transaction amount according to the benefit of the offer.
In one embodiment, the third authorization response (138) is generated to approve the transaction, if the first authorization response (647) approves the benefit and the second authorization response (643) approves the second transaction amount in the account; and the third authorization response (138) is generated to reject the transaction, if the first authorization response (647) rejects the benefit or the second authorization response (643) rejects the second transaction amount in the account.
When the benefit of the offer (186) of one embodiment is controlled by multiple sponsor processors, in response to the determination that the benefit of the offer is applicable to the transaction, the computing apparatus is configured to communicate with a further sponsor processor for authorization of a further benefit of the offer, in addition to communication with the sponsor processor (649); and the third authorization response (138) is generated based on a further authorization response from the further sponsor processor, the first authorization response (647), and the second authorization response (643).
The computing apparatus may optionally store a trigger record (613) identifying a first set of requirements and the offer for enhanced performance. When the trigger record (613) is used, the determining of whether the benefit of the offer is applicable to the transaction may include: determining whether the transaction satisfies the first set of requirements specified in the trigger record (613), and in response to a determination that the transaction satisfies the first set of requirements, identifying the offer based on the trigger record and determining whether a second set of requirements of the offer (186) are satisfied to qualify the transaction for the benefit.
The computing apparatus is configured in one embodiment to communicate with the sponsor processor and the issuer processor concurrently.
The computing apparatus can further store data (e.g., 611, 142) associating a communication reference with the account of the user, and transmit a notification about application of the benefit to the transaction concurrently with transmitting the third authorization response (138).
In one embodiment, a transaction amount approved in the third authorization response (138) is equal to the sum of a transaction amount approved in the first authorization response (647) and a transaction amount approved in the second authorization response (643).
For example, the computing apparatus includes a transaction handler (103) in a payment communications network interconnected by the transaction handler; and the computing apparatus uses the transaction handler (103) to communicate with the sponsor processor (649) and the issuer processor (145) using on the payment communications network.
In one embodiment, the computing apparatus includes a portal (143) to transmit a notification of a reduction in transaction amount in the account, reduced in accordance with the offer (186), to the user at a communication reference (611) associated with the account information (142) of the user (101). When the authorization request (168) is received from an acquirer processor (147), the notification can be transmitted in parallel with transmission of the third authorization response (138) to the acquirer processor (168).
In one embodiment, to determine whether the benefit of the offer (186) is applicable to the transaction, the computing apparatus is configured to: store a trigger record (613) identifying the offer (186) and a portion of requirements of the offer (186) to be satisfied by the transaction to qualify for a benefit of the offer; identifying the transaction based on matching the transaction with the portion of requirements; and after the transaction and the offer are identified via matching the trigger record with transactions, determining whether the transaction satisfies the requirements for awarding the benefit of the offer (186).
The computing apparatus has at least one processor and memory storing instructions configured to instruct the at least one processor to perform operations. For example, the computing apparatus of one embodiment includes a data warehouse (149) configured to store first data associating a communication reference (611) with an account (146) of a user and second data associating an offer (186) with the account (146) identified by the account information (142). The second data may include a trigger record (613) identifying the offer (186) and a first set of conditions that requires a transaction in the account to be satisfied. The offer (186) has a benefit applicable to a transaction satisfying a second set of conditions that includes the first set. The computing apparatus further includes a transaction handler (103) configured to process payment transactions to detect an authorization request (168) for a first transaction when the first transaction satisfies the first set of conditions specified in the trigger record (613). After the authorization request is detected, the computing apparatus identifies the offer (186) based on the trigger record (613) matching the first transaction and determines whether the second set of conditions is satisfied in view of the first transaction. If the second set of conditions is satisfied, the transaction handler is configured to communicate with a sponsor processor (649) of the benefit for authorization of the benefit, communicate with an issuer processor (145) of the account for authorization in the account, and generate a third authorization response (138) for the authorization request (168) based on a first authorization response (647) from the sponsor processor (649) and a second authorization response (643) from the issuer processor (145). The computing apparatus further includes a portal (143) configured to transmit a notification to the communication reference (611) about application of the offer to the first transaction, concurrently with transmission of the third authorization response (138).
In one embodiment, the notification is transmitted to the communication reference when the third authorization response (138) approves the first transaction; and the transaction handler (103) is configured to concurrently transmit the first authorization request (645) and the second authorization request (641).
Transaction Data Based Services
In
The transaction profiles (127) of one embodiment are generated from the transaction data (109) in a way as illustrated in
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, 341).
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) couples with 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, spend 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. For example, the centralized data warehouse (149) may include the advertisement data (135) and/or offers of benefits such as discount, reward, points, cashback, etc. The offers can be communicated to the users (e.g., 101) via the advertisement data (135) or as part of the advertisement data (135).
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 (301) 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) (and/or the portal (143)) is configured to provide at least part of the intelligence for the prioritization, generation, selection, customization and/or adjustment of the 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.
The profile generator (121) may generate and update the transaction profiles (127) in batch mode periodically, or 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.
The transaction profiles (127) of one embodiment 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.”
Non-Transactional Data
In one embodiment, the transaction data (109) is analyzed in connection with non-transactional data to generate transaction profiles (127) and/or to make predictive models.
In one embodiment, transactions are correlated with non-transactional events, such as news, conferences, shows, announcements, market changes, natural disasters, etc. to establish cause and effect relations to predict future transactions or spending patterns. For example, non-transactional data may include the geographic location of a news event, the date of an event from an events calendar, the name of a performer for an upcoming concert, etc. The non-transactional data can be obtained from various sources, such as newspapers, websites, blogs, social networking sites, etc.
When the cause and effect relationships between the transactions and non-transactional events are known (e.g., based on prior research results, domain knowledge, expertise), the relationships can be used in predictive models to predict future transactions or spending patterns, based on events that occurred recently or are happening in real time.
In one embodiment, the non-transactional data relates to events that happened in a geographical area local to the user (101) that performed the respective transactions. In one embodiment, a geographical area is local to the user (101) when the distance from the user (101) to locations in the geographical area is within a convenient range for daily or regular travel, such as 20, 50 or 100 miles from an address of the user (101), or within the same city or zip code area of an address of the user (101). Examples of analyses of local non-transactional data in connection with transaction data (109) in one embodiment are provided in U.S. patent application Ser. No. 12/614,603, filed Nov. 9, 2009, assigned U.S. Pat. App. Pub. No. 2011/0054981, and entitled “Analyzing Local Non-Transactional Data with Transactional Data in Predictive Models,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, the non-transactional data is not limited to local non-transactional data. For example, national non-transactional data can also be used.
In one embodiment, the transaction records (301) are analyzed in frequency domain to identify periodic features in spending events. The periodic features in the past transaction records (301) can be used to predict the probability of a time window in which a similar transaction would occur. For example, the analysis of the transaction data (109) can be used to predict when a next transaction having the periodic feature would occur, with which merchant, the probability of a repeated transaction with a certain amount, the probability of exception, the opportunity to provide an advertisement or offer such as a coupon, etc. In one embodiment, the periodic features are detected through counting the number of occurrences of pairs of transactions that occurred within a set of predetermined time intervals and separating the transaction pairs based on the time intervals. Some examples and techniques for the prediction of future transactions based on the detection of periodic features in one embodiment are provided in U.S. patent application Ser. No. 12/773,770, filed May 4, 2010, assigned U.S. Pat. App. Pub. No. 2010/0280882, and entitled “Frequency-Based Transaction Prediction and Processing,” the disclosure of which is hereby incorporated herein by reference.
Techniques and details of predictive modeling in one embodiment are provided in U.S. Pat. Nos. 6,119,103, 6,018,723, 6,658,393, 6,598,030, and 7,227,950, the disclosures of which are hereby incorporated herein by reference.
In one embodiment, offers are based on the point-of-service to offeree distance to allow the user (101) to obtain in-person services. In one embodiment, the offers are selected based on transaction history and shopping patterns in the transaction data (109) and/or the distance between the user (101) and the merchant. In one embodiment, offers are provided in response to a request from the user (101), or in response to a detection of the location of the user (101). Examples and details of at least one embodiment are provided in U.S. patent application Ser. No. 11/767,218, filed Jun. 22, 2007, assigned U.S. Pat. App. Pub. No. 2008/0319843, and entitled “Supply of Requested Offer Based on Point-of Service to Offeree Distance,” U.S. patent application Ser. No. 11/755,575, filed May 30, 2007, assigned U.S. Pat. App. Pub. No. 2008/0300973, and entitled “Supply of Requested Offer Based on Offeree Transaction History,” U.S. patent application Ser. No. 11/855,042, filed Sep. 13, 2007, assigned U.S. Pat. App. Pub. No. 2009/0076896, and entitled “Merchant Supplied Offer to a Consumer within a Predetermined Distance,” U.S. patent application Ser. No. 11/855,069, filed Sep. 13, 2007, assigned U.S. Pat. App. Pub. No. 2009/0076925, and entitled “Offeree Requested Offer Based on Point-of Service to Offeree Distance,” and U.S. patent application Ser. No. 12/428,302, filed Apr. 22, 2009, assigned U.S. Pat. App. Pub. No. 2010/0274627, and entitled “Receiving an Announcement Triggered by Location Data,” the disclosures of which applications are hereby incorporated herein by reference.
Targeting Advertisement
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 aggregate spending profile (341). 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 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 (341) 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 (341) to estimate the needs of the user (101). For example, the factor values (344) and/or the cluster ID (343) in the aggregated spending profile (341) can be used to determine the spending preferences of the user (101). For example, the channel distribution (345) in the aggregated spending profile (341) 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. patent application Ser. No. 11/960,162, filed Dec. 19, 2007, assigned U.S. Pat. App. Pub. No. 2008/0201226, and 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. patent application Ser. No. 11/862,487, filed Sep. 27, 2007, assigned U.S. Pat. App. Pub. No. 2008/0082418, and 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. patent application Ser. No. 12/185,332, filed Aug. 4, 2008, assigned U.S. Pat. App. Pub. No. 2010/0030644, and entitled “Targeted Advertising by Payment Processor History of Cashless Acquired Merchant Transaction on Issued Consumer Account,” and in U.S. patent application Ser. No. 12/849,793, filed Aug. 3, 2010, assigned U.S. Pat. App. Pub. No. 2011/0035280, and entitled “Systems and Methods for Targeted Advertisement Delivery,” the disclosures of which applications are hereby incorporated herein by reference.
Profile Matching
In
In one embodiment, the profile selector (129) receives the transaction profiles (127) in a batch mode. The profile selector (129) selects the user specific profile (131) from the batch of transaction profiles (127) based on the user data (125). Alternatively, the profile generator (121) generates the transaction profiles (127) in real time; and the profile selector (129) uses the user data (125) to query the profile generator (121) to generate the user specific profile (131) in real time, or just in time. The profile generator (121) generates the user specific profile (131) that best matches the user data (125).
In one embodiment, the user tracker (113) identifies the user (101) based on the user activity on the transaction terminal (105) (e.g., having visited a set of websites, currently visiting a type of web pages, search behavior, etc.).
In one embodiment, the user data (125) includes an identifier of the user (101), such as a global unique identifier (GUID), a personal account number (PAN) (e.g., credit card number, debit card number, or other card account number), or other identifiers that uniquely and persistently identify the user (101) within a set of identifiers of the same type. Alternatively, the user data (125) may include other identifiers, such as an Internet Protocol (IP) address of the user (101), a name or user name of the user (101), or a browser cookie ID, which identify the user (101) in a local, temporary, transient and/or anonymous manner. Some of these identifiers of the user (101) may be provided by publishers, advertisers, ad networks, search engines, merchants, or the user tracker (113). In one embodiment, such identifiers are correlated to the user (101) based on the overlapping or proximity of the time period of their usage to establish an identification reference table.
In one embodiment, the identification reference table is used to identify the account information (142) (e.g., account number (302)) based on characteristics of the user (101) captured in the user data (125), such as browser cookie ID, IP addresses, and/or timestamps on the usage of the IP addresses. In one embodiment, the identification reference table is maintained by the operator of the transaction handler (103). Alternatively, the identification reference table is maintained by an entity other than the operator of the transaction handler (103).
In one embodiment, the user tracker (113) determines certain characteristics of the user (101) to describe a type or group of users of which the user (101) is a member. The transaction profile of the group is used as the user specific profile (131). Examples of such characteristics include geographical location or neighborhood, types of online activities, specific online activities, or merchant propensity. In one embodiment, the groups are defined based on aggregate information (e.g., by time of day, or household), or segment (e.g., by cluster, propensity, demographics, cluster IDs, and/or factor values). In one embodiment, the groups are defined in part via one or more social networks. For example, a group may be defined based on social distances to one or more users on a social network website, interactions between users on a social network website, and/or common data in social network profiles of the users in the social network website.
In one embodiment, the user data (125) may match different profiles at a different granularity or resolution (e.g., account, user, family, company, neighborhood, etc.), with different degrees of certainty. The profile selector (129) and/or the profile generator (121) may determine or select the user specific profile (131) with the finest granularity or resolution with acceptable certainty. Thus, the user specific profile (131) is most specific or closely related to the user (101).
In one embodiment, the advertisement selector (133) uses further data in prioritizing, selecting, generating, customizing and adjusting the user specific advertisement data (119). For example, the advertisement selector (133) may use search data in combination with the user specific profile (131) to provide benefits or offers to a user (101) at the point of interaction (107). For example, the user specific profile (131) can be used to personalize the advertisement, such as adjusting the placement of the advertisement relative to other advertisements, adjusting the appearance of the advertisement, etc.
Browser Cookie
In one embodiment, the user data (125) uses browser cookie information to identify the user (101). The browser cookie information is matched to account information (142) or the account number (302) to identify the user specific profile (131), such as aggregated spending profile (341) to present effective, timely, and relevant marketing information to the user (101), via the preferred communication channel (e.g., mobile communications, web, mail, email, POS, etc.) within a window of time that could influence the spending behavior of the user (101). Based on the transaction data (109), the user specific profile (131) can improve audience targeting for online advertising. Thus, customers will get better advertisements and offers presented to them; and the advertisers will achieve better return-on-investment for their advertisement campaigns.
In one embodiment, the browser cookie that identifies the user (101) in online activities, such as web browsing, online searching, and using social networking applications, can be matched to an identifier of the user (101) in account data (111), such as the account number (302) of a financial payment card of the user (101) or the account information (142) of the account identification device (141) of the user (101). In one embodiment, the identifier of the user (101) can be uniquely identified via matching IP address, timestamp, cookie ID and/or other user data (125) observed by the user tracker (113).
In one embodiment, a look up table is used to map browser cookie information (e.g., IP address, timestamp, cookie ID) to the account data (111) that identifies the user (101) in the transaction handler (103). The look up table may be established via correlating overlapping or common portions of the user data (125) observed by different entities or different user trackers (113).
In one embodiment, the portal (143) is configured to identify the consumer account (146) based on the IP address identified in the user data (125) through mapping the IP address to a street address.
In one embodiment, the portal (143) uses a plurality of methods to identify consumer accounts (146) based on the user data (125). The portal (143) combines the results from the different methods to determine the most likely consumer account (146) for the user data (125).
Details about the identification of consumer account (146) based on user data (125) in one embodiment are provided in U.S. patent application Ser. No. 12/849,798, filed Aug. 3, 2010, assigned U.S. Pat. App. Pub. No. 2011/0093327, and entitled “Systems and Methods to Match Identifiers,” the disclosure of which is hereby incorporated herein by reference.
Close the Loop
In one embodiment, the correlator (117) is used to “close the loop” for the tracking of consumer behavior across an on-line activity and an “off-line” activity that results at least in part from the on-line activity. In one embodiment, online activities, such as searching, web browsing, social networking, and/or consuming online advertisements, are correlated with respective transactions to generate the correlation result (123) in
The correlator (117) is configured in one embodiment to identify transactions resulting from searches or online advertisements. For example, in response to a query about the user (101) from the user tracker (113), the correlator (117) identifies an offline transaction performed by the user (101) and sends the correlation result (123) about the offline transaction to the user tracker (113), which allows the user tracker (113) to combine the information about the offline transaction and the online activities to provide significant marketing advantages.
For example, a marketing department could correlate an advertising budget to actual sales. For example, a marketer can use the correlation result (123) to study the effect of certain prioritization strategies, customization schemes, etc. on the impact on the actual sales. For example, the correlation result (123) can be used to adjust or prioritize advertisement placement on a web site, a search engine, a social networking site, an online marketplace, or the like.
In one embodiment, the profile generator (121) uses the correlation result (123) to augment the transaction profiles (127) with data indicating the rate of conversion from searches or advertisements to purchase transactions. In one embodiment, the correlation result (123) is used to generate predictive models to determine what a user (101) is likely to purchase when the user (101) is searching using certain keywords or when the user (101) is presented with an advertisement or offer. In one embodiment, the portal (143) is configured to report the correlation result (123) to a partner, such as a search engine, a publisher, or a merchant, to allow the partner to use the correlation result (123) to measure the effectiveness of advertisements and/or search result customization, to arrange rewards, etc.
In one embodiment, the correlator (117) matches the online activities and the transactions based on matching the user data (125) provided by the user tracker (113) and the records of the transactions, such as transaction data (109) or transaction records (301). In another embodiment, the correlator (117) matches the online activities and the transactions based on the redemption of offers/benefits provided in the user specific advertisement data (119).
In one embodiment, the portal (143) is configured to receive a set of conditions and an identification of the user (101), determine whether there is any transaction of the user (101) that satisfies the set of conditions, and if so, provide indications of the transactions that satisfy the conditions and/or certain details about the transactions, which allows the requester to correlate the transactions with certain user activities, such as searching, web browsing, consuming advertisements, etc.
In one embodiment, the requester may not know the account number (302) of the user (101); and the portal (143) is to map the identifier provided in the request to the account number (302) of the user (101) to provide the requested information. Examples of the identifier being provided in the request to identify the user (101) include an identification of an iFrame of a web page visited by the user (101), a browser cookie ID, an IP address and the day and time corresponding to the use of the IP address, etc.
The information provided by the portal (143) can be used in pre-purchase marketing activities, such as customizing content or offers, prioritizing content or offers, selecting content or offers, etc., based on the spending pattern of the user (101). The content that is customized, prioritized, selected, or recommended may be the search results, blog entries, items for sale, etc.
The information provided by the portal (143) can be used in post-purchase activities. For example, the information can be used to correlate an offline purchase with online activities. For example, the information can be used to determine purchases made in response to media events, such as television programs, advertisements, news announcements, etc.
Details about profile delivery, online activity to offline purchase tracking, techniques to identify the user specific profile (131) based on user data (125) (such as IP addresses), and targeted delivery of advertisement/offer/benefit in some embodiments are provided in U.S. patent application Ser. No. 12/849,789, filed Aug. 3, 2010, assigned U.S. Pat. App. Pub. No. 2011/0035278, and entitled “Systems and Methods for Closing the Loop between Online Activities and Offline Purchases,” the disclosure of which application is incorporated herein by reference.
Loyalty Program
In one embodiment, the transaction handler (103) uses the account data (111) to store information for third party loyalty programs.
In one embodiment, the association between the account identifier (181) and the loyalty benefit offeror (183) in the account data (111) indicates that the user (101) having the account identifier (181) is a member of the loyalty program. Thus, the user (101) may use the account identifier (181) to access privileges afforded to the members of the loyalty programs, such as rights to access a member only area, facility, store, product or service, discounts extended only to members, or opportunities to participate in certain events, buy certain items, or receive certain services reserved for members.
In one embodiment, it is not necessary to make a purchase to use the privileges. The user (101) may enjoy the privileges based on the status of being a member of the loyalty program. The user (101) may use the account identifier (181) to show the status of being a member of the loyalty program.
For example, the user (101) may provide the account identifier (181) (e.g., the account number of a credit card) to the transaction terminal (105) to initiate an authorization process for a special transaction which is designed to check the member status of the user (101), as if the account identifier (181) were used to initiate an authorization process for a payment transaction. The special transaction is designed to verify the member status of the user (101) via checking whether the account data (111) is associated with the loyalty benefit offeror (183). If the account identifier (181) is associated with the corresponding loyalty benefit offeror (183), the transaction handler (103) provides an approval indication in the authorization process to indicate that the user (101) is a member of the loyalty program. The approval indication can be used as a form of identification to allow the user (101) to access member privileges, such as access to services, products, opportunities, facilities, discounts, permissions, which are reserved for members.
In one embodiment, when the account identifier (181) is used to identify the user (101) as a member to access member privileges, the transaction handler (103) stores information about the access of the corresponding member privilege in loyalty record (187). The profile generator (121) may use the information accumulated in the loyalty record (187) to enhance transaction profiles (127) and provide the user (101) with personalized/targeted advertisements, with or without further offers of benefit (e.g., discounts, incentives, rebates, cash back, rewards, etc.).
In one embodiment, the association of the account identifier (181) and the loyalty benefit offeror (183) also allows the loyalty benefit offeror (183) to access at least a portion of the account data (111) relevant to the loyalty program, such as the loyalty record (187) and certain information about the user (101), such as name, address, and other demographic data.
In one embodiment, the loyalty program allows the user (101) to accumulate benefits according to loyalty program rules (185), such as reward points, cash back, levels of discounts, etc. For example, the user (101) may accumulate reward points for transactions that satisfy the loyalty program rules (185); and the user (101) may use the reward points to redeem cash, gift, discounts, etc. In one embodiment, the loyalty record (187) stores the accumulated benefits; and the transaction handler (103) updates the loyalty record (187) associated with the loyalty benefit offeror (183) and the account identifier (181), when events that satisfy the loyalty program rules occur.
In one embodiment, the accumulated benefits as indicated in the loyalty record (187) can be redeemed when the account identifier (181) is used to perform a payment transaction, when the payment transaction satisfies the loyalty program rules. For example, the user (101) may redeem a number of points to offset or reduce an amount of the purchase price.
In one embodiment, when the user (101) uses the account identifier (181) to make purchases as a member, the merchant may further provide information about the purchases; and the transaction handler (103) can store the information about the purchases as part of the loyalty record (187). The information about the purchases may identify specific items or services purchased by the member. For example, the merchant may provide the transaction handler (103) with purchase details at stock-keeping unit (SKU) level, which are then stored as part of the loyalty record (187). The loyalty benefit offeror (183) may use the purchase details to study the purchase behavior of the user (101); and the profile generator (121) may use the SKU level purchase details to enhance the transaction profiles (127).
In one embodiment, the SKU level purchase details are requested from the merchants or retailers via authorization responses (e.g., as illustrated in
A method to provide loyalty programs of one embodiment includes the use of the transaction handler (103) as part of a computing apparatus. The computing apparatus processes a plurality of payment card transactions. After the computing apparatus receives a request to track transactions for a loyalty program, such as the loyalty program rules (185), the computing apparatus stores and updates loyalty program information in response to transactions occurring in the loyalty program. The computing apparatus provides to a customer (e.g., 101) an offer of a benefit when the customer satisfies a condition defined in the loyalty program, such as the loyalty program rules (185). In one embodiment, the loyalty benefit as identified in the loyalty record (187) can be redeemed in connection with a transaction in a way the benefit of an offer stored in association with the account identifier (181) is redeemed.
Examples of loyalty programs through collaboration between collaborative constituents in a payment processing system, including the transaction handler (103) in one embodiment are provided in U.S. patent application Ser. No. 11/767,202, filed Jun. 22, 2007, assigned U.S. Pat. App. Pub. No. 2008/0059302, and entitled “Loyalty Program Service,” U.S. patent application Ser. No. 11/848,112, filed Aug. 30, 2007, assigned U.S. Pat. App. Pub. No. 2008/0059306, and entitled “Loyalty Program Incentive Determination,” and U.S. patent application Ser. No. 11/848,179, filed Aug. 30, 2007, assigned U.S. Pat. App. Pub. No. 2008/0059307, and entitled “Loyalty Program Parameter Collaboration,” the disclosures of which applications are hereby incorporated herein by reference.
Examples of processing the redemption of accumulated loyalty benefits via the transaction handler (103) in one embodiment are provided in U.S. patent application Ser. No. 11/835,100, filed Aug. 7, 2007, assigned U.S. Pat. App. Pub. No. 2008/0059303, and entitled “Transaction Evaluation for Providing Rewards,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, the incentive, reward, or benefit provided in the loyalty program is based on the presence of correlated related transactions. For example, in one embodiment, an incentive is provided if a financial payment card is used in a reservation system to make a reservation and the financial payment card is subsequently used to pay for the reserved good or service. Further details and examples of one embodiment are provided in U.S. patent application Ser. No. 11/945,907, filed Nov. 27, 2007, assigned U.S. Pat. App. Pub. No. 2008/0071587, and entitled “Incentive Wireless Communication Reservation,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, the transaction handler (103) provides centralized loyalty program management, reporting and membership services. In one embodiment, membership data is downloaded from the transaction handler (103) to acceptance point devices, such as the transaction terminal (105). In one embodiment, loyalty transactions are reported from the acceptance point devices to the transaction handler (103); and the data indicating the loyalty points, rewards, benefits, etc. are stored on the account identification device (141). Further details and examples of one embodiment are provided in U.S. patent application Ser. No. 10/401,504, filed Mar. 27, 2003, assigned U.S. Pat. App. Pub. No. 2004/0054581, and entitled “Network Centric Loyalty System,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, the portal (143) of the transaction handler (103) is used to manage reward or loyalty programs for entities such as issuers, merchants, etc. The cardholders, such as the user (101), are rewarded with offers/benefits from merchants. The portal (143) and/or the transaction handler (103) track the transaction records for the merchants for the reward or loyalty programs. Further details and examples of one embodiment are provided in U.S. patent application Ser. No. 11/688,423, filed Mar. 20, 2007, assigned U.S. Pat. App. Pub. No. 2008/0195473, and entitled “Reward Program Manager,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, a loyalty program includes multiple entities providing access to detailed transaction data, which allows the flexibility for the customization of the loyalty program. For example, issuers or merchants may sponsor the loyalty program to provide rewards; and the portal (143) and/or the transaction handler (103) stores the loyalty currency in the data warehouse (149). Further details and examples of one embodiment are provided in U.S. patent application Ser. No. 12/177,530, filed Jul. 22, 2008, assigned U.S. Pat. App. Pub. No. 2009/0030793, and entitled “Multi-Vender Multi-Loyalty Currency Program,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, an incentive program is created on the portal (143) of the transaction handler (103). The portal (143) collects offers from a plurality of merchants and stores the offers in the data warehouse (149). The offers may have associated criteria for their distributions. The portal (143) and/or the transaction handler (103) may recommend offers based on the transaction data (109). In one embodiment, the transaction handler (103) automatically applies the benefits of the offers during the processing of the transactions when the transactions satisfy the conditions associated with the offers. In one embodiment, the transaction handler (103) communicates with transaction terminals (105) to set up, customize, and/or update offers based on market focus, product categories, service categories, targeted consumer demographics, etc. Further details and examples of one embodiment are provided in U.S. patent application Ser. No. 12/413,097, filed Mar. 27, 2009, assigned U.S. Pat. App. Pub. No. 2010/0049620, and entitled “Merchant Device Support of an Integrated Offer Network,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, the transaction handler (103) is configured to provide offers from merchants to the user (101) via the payment system, making accessing and redeeming the offers convenient for the user (101). The offers may be triggered by and/or tailored to a previous transaction, and may be valid only for a limited period of time starting from the date of the previous transaction. If the transaction handler (103) determines that a subsequent transaction processed by the transaction handler (103) meets the conditions for the redemption of an offer, the transaction handler (103) may credit the consumer account (146) for the redemption of the offer and/or provide a notification message to the user (101). Further details and examples of one embodiment are provided in U.S. patent application Ser. No. 12/566,350, filed Sep. 24, 2009, assigned U.S. Pat. App. Pub. No. 2010/0114686, and entitled “Real-Time Statement Credits and Notifications,” the disclosure of which is hereby incorporated herein by reference.
Details on loyalty programs in one embodiment are provided in U.S. patent application Ser. No. 12/896,632, filed Oct. 1, 2010, assigned U.S. Pat. App. Pub. No. 2011/0087530, and entitled “Systems and Methods to Provide Loyalty Programs,” the disclosure of which is hereby incorporated herein by reference.
SKU
In one embodiment, merchants generate stock-keeping unit (SKU) or other specific information that identifies the particular goods and services purchased by the user (101) or customer. The SKU information may be provided to the operator of the transaction handler (103) that processed the purchases. The operator of the transaction handler (103) may store the SKU information as part of transaction data (109), and reflect the SKU information for a particular transaction in a transaction profile (127 or 131) associated with the person involved in the transaction.
When a user (101) shops at a traditional retail store or browses a website of an online merchant, an SKU-level profile associated specifically with the user (101) may be provided to select an advertisement appropriately targeted to the user (101) (e.g., via mobile phones, POS terminals, web browsers, etc.). The SKU-level profile for the user (101) may include an identification of the goods and services historically purchased by the user (101). In addition, the SKU-level profile for the user (101) may identify goods and services that the user (101) may purchase in the future. The identification may be based on historical purchases reflected in SKU-level profiles of other individuals or groups that are determined to be similar to the user (101). Accordingly, the return on investment for advertisers and merchants can be greatly improved.
In one embodiment, the user specific profile (131) is an aggregated spending profile (341) that is generated using the SKU-level information. For example, in one embodiment, the factor values (344) correspond to factor definitions (331) that are generated based on aggregating spending in different categories of products and/or services. A typical merchant offers products and/or services in many different categories.
In one embodiment, the SKU level purchase details are requested from the merchants or retailers via authorization responses (e.g., as illustrated in
Details on SKU-level profile in one embodiment are provided in U.S. patent application Ser. No. 12/899,144, filed Oct. 6, 2010, assigned U.S. Pat. App. Pub. No. 2011/0093335, and entitled “Systems and Methods for Advertising Services Based on an SKU-Level Profile,” the disclosure of which is hereby incorporated herein by reference.
Purchase Details
In one embodiment, the transaction handler (103) is configured to selectively request purchase details via authorization responses. When the transaction handler (103) (and/or the issuer processor (145)) needs purchase details, such as identification of specific items purchased and/or their prices, the authorization responses transmitted from the transaction handler (103) is to include an indicator to request for the purchase details for the transaction that is being authorized. The merchants are to determine whether or not to submit purchase details based on whether or not there is a demand indicated in the authorization responses from the transaction handler (103).
In one embodiment, when the transaction is approved and there is a need for purchase details (169), the transaction handler (103) (or the issuer processor (145)) is to provide an indicator of the request (139) for purchase details in the authorization response (138). The optional request (139) allows the transaction handler (103) (and/or the issuer processor (145)) to request purchase details (169) from the merchant or retailer on demand. When the request (139) for purchase details is present in the authorization response (138), the transaction terminal (105) is to provide the purchase details (169) associated with the payment transaction to the transaction handler (103) directly or indirectly via the portal (143). When the request (139) is absent from the authorization response (138), the transaction terminal (105) does not have to provide the purchase details (169) for the payment transaction.
In one embodiment, prior to transmitting the authorization response (138), the transaction handler (103) (and/or the issuer processor (145)) determines whether there is a need for transaction details. When there is no need for the purchase details (169) for a payment transaction, the request (139) for purchase details (169) is not provided in the authorization response (138) for the payment transaction. When there is a need for the purchase details (169) for a payment transaction, the request (139) for purchase details is provided in the authorization response (138) for the payment transaction. The merchants or retailers do not have to send detailed purchase data to the transaction handler (103) when the authorization response message does not explicitly request detailed purchase data.
Offer Redemption
In
In
In one embodiment, when the link to the portal (143) is selected, the user (101) is to provide the account information (142) to the portal (143) via the point of interaction (107) to identify the consumer account (146) of the user (101). After both the consumer account (146) of the user (101) and the offer (186) are identified, the data warehouse (149) is to store the data to associate offer (186) with the account information (142) in the account data (111) of the user (101).
In one embodiment, the account information (142) is pre-stored in the account data (111) of the user (101). The portal (143) is to authenticate the identity of the user (101) in response to the user selection of the link to the portal (143). After the user (101) is identified via authentication, the data warehouse (149) stores the data to associate offer (186) with the account information (142) in the account data (111) of the user (101).
In one embodiment, the account data (111) of the user (101) may have multiple consumer accounts (e.g., 146) under the control of one or more issuer processors (e.g., 145). When the user (101) has multiple consumer accounts (e.g., 146), the portal (143) is to prompt the user (101) to associate the offer (186) with one of the consumer accounts (e.g., 146). The transaction handler (103) and/or the portal (143) are to monitor the activity in the consumer account (e.g., 146) with which the offer (186) is associated to detect a transaction that qualifies for the redemption of the offer (186).
After the offer (186) is associated with account information (142), the transaction handler (103) and/or the portal (143) is to monitor the transaction activities in the corresponding consumer account (146) to detect one or more transactions that qualify for the redemption of the offer (186). For example, if the user (101) uses the account information (142) in the transaction terminal (105) to pay for a qualified purchase, the transaction handler (103) and/or the portal (143) is to identify the transaction from the multiplicity of transactions processed by the transaction handler (103) and to provide the benefit to the user (101) in accordance with the offer (186).
For example, in one embodiment, when processing a transaction at the transaction handler (103), the account information (142) involved in the transaction is checked to identify the associated offers (e.g., 186). If one or more offers (e.g., 186) are identified for the transaction, the transaction record for the transaction and/or other information about the transaction is used to determine if the redemption conditions of the offer (186) are met by the transaction. If the redemption conditions of the offer (186) are met, the transaction handler (103) is to redeem the offer (186) on behalf of the user (101) via statement credits to the consumer account (146) identified by the account information (142).
In one embodiment, when the user (101) has multiple consumer accounts (e.g., 146), the transaction handler (103) and/or the portal (143) is to monitor the activity in the multiple consumer accounts to detect a transaction that qualifies for the redemption of the offer (186). When a qualified transaction is detected in a consumer account (146), the transaction handler (103) is to provide the statement credits to the consumer account (146) with which the offer (186) is associated to detect a transaction that qualifies for the redemption of the offer (186). In one embodiment, when the user (101) has multiple consumer accounts (e.g., 146), the portal (143) is to allow the user (101) to not associate the offer (186) with a particular consumer account; and when a qualified transaction is detected in an consumer account (146), the transaction handler (103) is to provide the statement credits to the consumer account (146) in which the qualified transaction occurred.
In one embodiment, the offer (186) is pre-registered in the data warehouse (149) prior to the delivery of the advertisement (205) from the advertisement sever (201) to the point of the interaction (107). For example, in one embodiment, the merchant or advertiser is to use the portal (143) to store data representing the offer (186) in the data warehouse (149). The data representing the offer (186) includes the specification of the benefit of the offer (186) and/or conditions for the redemption of the offer (186). In response, the portal (143) provides an identifier of the offer (186) to uniquely identify the offer (186) among a plurality of offers registered in the data warehouse (149). In one embodiment, the identifier of the offer (186) is included in the link to the portal (143) embedded in the advertisement (205). Thus, when the link containing the identifier of the offer (186) is selected, the identifier of the offer (186) is provided from the point of interaction (107) to the portal (143) to identify the offer (186).
In one embodiment, the pre-registration of the offer (186) in the data warehouse (149) by the merchant is not required. For example, the details of the offer (186), such as the specification of the benefit and the conditions for the redemption of the offer (186), are embedded in the link from the advertisement (205) to the portal (143). In one embodiment, the link from the advertisement (205) to the portal (143) includes a location from which the portal (143) can obtain the details of the offer (186). For example, in one embodiment, the details of the offer (186) are stored in the merchant website (203) and provided by the merchant website (203) via a web service. For example, in one embodiment, the details of the offer (186) are stored in the advertisement server (201), or a third party web service.
In
In one embodiment, when the portion (403) is selected as in
The user (101) may have already logged into the web portal (143) using the web browser running on the point of interaction (107) (e.g., as Ashley illustrated in
In
In one embodiment, the user (101) has multiple financial transaction cards supported by the web portal (143). The web portal (143) allows the user (101) to store the offer (401) with one of the financial transaction cards, as illustrated in
In another embodiment, the offer (401) is stored in association with one or more (or all) of the cards identified in the account. Thus, the offer (401) can be redeemed in an automated way, when any of the associated cards is used to make the payment for the purchases that qualify for the offer (401).
In
In one embodiment, the user (101) may also provide a phone number of a mobile phone (421) to the offer redemption site (e.g., as a user selected preference to receive mobile notification of saved offers); and once the offer (523) is saved with a card of the user (101), the offer redemption site can transmit a mobile message (537) to the user (101), as illustrated in
If the user (101) is not recognized by the offer redemption site (e.g., via a browser cookie), or the user (101) clicks the “not John” link (525) in
Further details and examples of one embodiment of offer fulfillment are provided in U.S. patent application Ser. No. 13/113,710, filed May 23, 2011, assigned U.S. Pat. App. Pub. No. 2011/0288918, and entitled “Systems and Methods for Redemption of Offers,” the disclosure of which is hereby incorporated herein by reference.
Apply Offer
The transaction handler (103) of one embodiment is configured to process authorization/settlement requests to enable to real time discount at transaction terminal (105) in accordance with the offer (186) stored, in association with the account data (111) of the user (101), in the data warehouse (149) of the transaction handler (103).
In
In
In
In one embodiment, the issuer processor (145) is configured to apply the offer (186) by change the authorization response (138).
In one embodiment, the acquirer processor (147) is configured to apply the offer (186) by change the authorization response (138) or the authorization request (168) (e.g., after receiving the authorization request (168) from the transaction terminal (105) and before transmitting the authorization request (168) having the modified transaction amount (605) to the transaction handler (103)).
In one embodiment, the transaction handler (103) further uses a communication reference (e.g., a mobile phone number, an email address, an instant message user identifier) that is stored in the account data (111) to provide a notification to the user (101) about the applicable offer (186) and the benefit of the offer (186) that has been applied to the transaction, in parallel with the processing of the authorization request (168) and/or the authorization response (138). Details and examples of using such a communication reference for notification in one embodiment are provided in U.S. patent application Ser. No. 13/152,186, filed Jun. 2, 2011, now U.S. Pat. No. 8,359,274, and entitled “Systems and Methods to Provide Messages in Real-Time with Transaction Processing,” the disclosure of which is incorporated herein by reference in its entirety.
In one embodiment, the transaction handler (103) is configured to detect the applicability of the offer (186) during the settlement phase of the transaction and apply the applicable offer (186) during settlement of the transaction.
In one embodiment, the portal (143) is configured with a user interface to allow the user (101) of the consumer account (146) specify a communication reference (611) that is stored in association with the account information (142). If the user (101) provides the communication reference (611) for association with the account information (142), the user (101) is provided with notification services using the communication reference (611). Examples of the communication reference (611) include a phone number for notification via voice mails, a mobile phone number for notification via short message service or mobile application, an email address for notification via emails, a user name in an instant messaging system for notification via instant messages, a member ID of a social networking site for notification via messages transmitted via the social networking site, etc.
In
In
In
In
In one embodiment, when the authorization response (138) received from the issuer processor (145) indicates the approval of the transaction that receives the benefit of the offer (186), the portal (143) is configured to use the communication reference (611) to send a notification to the point of interaction (107) of the user (101). The notification includes at least some of the above discussed information about the offer (186) that is applied to the authorization request (168) in the authorization response (168).
In
Prior to communicating (635) the authorization response (138) to the transaction terminal (105) via the acquirer processor (138), the computing apparatus is configured to determine whether the offer (186) is applicable; and if so, the computing apparatus configures (633) the authorization response to identify the offer (186) and the benefit applied to the transaction in accordance with the offer (186) (e.g., the reduced transaction amount).
In one embodiment, when the authorization response approves the transaction, the computing apparatus is configured to optionally transmit (637) a notification about the offer (186) to the point of interaction (107) of the user (101) using the communication reference (611).
Further details and examples of applying offer benefit via adjusting transaction amount in some embodiments are provided in U.S. patent application Ser. No. 13/676,535, filed Nov. 14, 2012 and entitled “Systems and Methods to Provide Discount at Point of Sales Terminals,” the disclosure of which is hereby incorporated herein by reference.
Transaction Terminal and Portal Connection
In
In one embodiment, when the transaction terminal (105) receives the account information (142) to initiate a transaction in the consumer account (146), the offer communication (741) in the communication channel is used to determine whether there is an applicable offer (186) for the transaction. If there is an offer (186) that is applicable to the transaction, the transaction terminal (105) is configured to adjust the transaction amount to reflect the benefit of the offer (186) applied to the transaction, prior to submitting an authorization request to the acquirer processor (147) for the authorization of an amount that takes into account the benefit of the offer (186).
For example, if the offer (186) provides a discount sponsored by the merchant, the offer communication (741) includes a message from the portal (143) identifying the discount; and the transaction terminal (105) is configured to initiate an authorization request to the acquirer processor (147) for an amount that is the difference between the original transaction amount and the discount.
In one embodiment, the authorization of the discount is controlled by the sponsor processor (649), which is in control of a financial account to fulfill the benefits provided in accordance with the offer (186). In response to the offer communication (741) from the transaction terminal (105) that identifies the account information (142), the portal (143) identifies the offer (186) and thus the associated sponsor processor (649) and submits an authorization request C (645) to the sponsor processor (649) to obtain the authorization response C (647) for the application of the benefit of the offer (186) to the proposed transaction that is about to initiated on the transaction terminal (105). If the sponsor processor (649) approves the benefit, the portal (143) identifies the benefit to the transaction terminal (105) via the offer communication (741); and in response, the transaction terminal (105) can adjust the transaction amount to include the benefit of the offer (186) and initiate a transaction for the adjusted transaction amount.
In one embodiment, the portal (143) communicates with the sponsor processor (649) directly to submit the authorization request C (645) and to obtain the authorization response C (647) for the benefit of the offer (186) applicable to the transaction. In one embodiment, the transaction handler (103) is not coupled with the data warehouse (149) and is not configured to apply the benefit of the offer (186); after the portal (143) communicates with the transaction terminal (105) to apply the benefit of the offer (186).
In one embodiment, the transaction handler (103) is coupled with the data warehouse (149). After the offer communication (741), the portal (143) is configured in one embodiment to modify trigger record (613) to prevent the transaction handler (103) from further applying the offer (186). Alternatively or in combination, the authorization request submitted from the transaction terminal (105) to the transaction handler (103) via the acquirer processor (147) is configured to include an indicator that notifies the transaction handler (103) of the application of the offer (186) at the transaction terminal (105) and thus prevents the transaction handler (103) from further applying the offer (186).
In one embodiment, the portal (143) transmits a request to the transaction handler (103) to request the transaction handler (103) to communicate with the sponsor processor (649) to submit the authorization request C (645) and to obtain the authorization response C (647) for the benefit of the offer (186) applicable to the transaction.
In one embodiment, the offer communication (741) includes a message from the transaction terminal (105) to the portal (143), where the message identifies the purchase details (169), such as identification of the items (e.g., products, services) purchased via the payment, the unit prices of the items, the number of units purchased, etc. In one embodiment, the applicability of the offer (186) is based on the purchase details (169) of the transaction.
In
In one embodiment, in response to the offer communication (741), the portal (143) directly request the transaction handler (103) to communicate with the sponsor processor (649) for the authorization of the benefit of the offer (186) applicable to the transaction in the consumer account (146) identified by the account information (142). After the sponsor processor (649) approves the provision of the benefit of the offer (186) to the transaction, the portal (143) informs the transaction terminal (105) of the benefit of the offer (186); and the transaction terminal (105) submits an authorization request for the balance of the transaction that is charged to the consumer account (146).
In one embodiment, the portal (143) is configured to indirectly instruct the transaction handler (103), via the acquirer processor (147) to communicate with the sponsor processor (649) for the authorization of the benefit of the offer (186).
For example, in one embodiment, after the offer communication (741) identifying the applicable benefit to the transaction, the portal (143) is configured to configure the trigger record (613) to include information for the transaction handler (103) to detect the corresponding authorization request submitted from the transaction terminal (105), via the acquirer processor (147), to the transaction handler (103). For example, the portal (143) may create a code, embed the code in the trigger record (613) and provide the code to the transaction terminal (105) for inclusion in the authorization request. The transaction handler (103) is configured to identify the trigger record (613) and the authorization request based on matching the code. The use of the code reduces the burden on the transaction handler (103) in processing the authorization requests, which may or may not match the trigger record (613), by reducing the requirements specified in the trigger record (613). When the code in the trigger record (613) matches with the code in the authorization request, the authorization request satisfies all the requirements of the offer (186); and thus, the accuracy of the triggered action caused by the trigger record (613) is increased.
In one embodiment, the code used to match the authorization request and the trigger record (613) is based on the account information (142) of the consumer account (146) and an identification of the transaction terminal (105) of the merchant (or an identification of the merchant). In one embodiment, the code includes a combination of the account information (142) and information of the merchant, or a hash value of the combination.
In one embodiment, the portal (143) is configured to create the trigger record (613) in response to the offer communication (741) and remove the trigger record (613) after a predetermined period of time. Thus, the number of active trigger records (613) that the transaction handler (103) is required to process or match against during the processing of the authorization requests is reduced. As a result, the performance impact, due to the implementation of the offer redemption, on the transaction handler (103) in processing authorization of transactions is reduced.
In one embodiment, the trigger record (613) instructs the transaction handler (103) to communicate with the sponsor processor (649) for the authorization of the application of the benefit of the offer (186) to the transaction. The transaction handler (103) is also configured to communicate with the issuer processor (145) for the authorization of a transaction in the consumer account in accordance with the authorization request received from the acquirer processor (147). The transaction handler (103) is configured to approve the transaction if both the issuer processor (145) and the sponsor processor (649) approve the respective transactions. In one embodiment, the transaction handler (103) is configured to settle both the transaction with the sponsor processor (649) and the transaction with the issuer processor (145) with the acquirer processor (147).
In one embodiment, the trigger record (613) is configured to instruct the transaction handler (103) to split the transaction requested by the acquirer processor (147) into two transactions with the issuer processor (145) and the sponsor processor (649) respectively, in a way similar to those discussed in section entitled “SPLIT TRANSACTION.”
In
In
In
In one embodiment, the transaction terminal (105) is configured to combine the authorization response for the transaction with the sponsor processor (649) and the transaction with the issuer processor (145) to approve or deny the purchase request.
In one embodiment, the sponsor processor (649) is an issuer processor (145) associated with a financial payment account of a sponsor of the offer (186), such as the merchant of the transaction terminal (105), a manufacturer of a product sold via the merchant, an issuer, a loyalty program administrator, or a third party.
In one embodiment, the communication channel between the transaction terminal (105) and the portal (143) may use Internet or wireless connections. The security of the communication channel is enhanced via encrypting sensitive information, such as the account information (142) identifying the consumer account (146) in which the transaction is requested. In one embodiment, the account information (142) to be transmitted from the transaction terminal (105) to the portal (143) is combined with a random number; and the combination of the account information (142) and the random number is encrypted for transmission from the transaction terminal (105) to the portal (143). In one embodiment, a correlation ID is assigned to the authorization request A (168); and the correlation ID is subsequently used in the offer communication (741) to identify the transaction.
In one embodiment, a plurality of parallel communication channels are used between the portal (143) and the transaction terminal (105); and the offer communication (741) is sliced and distributed over the plurality of parallel communication channels, such that even when information transmitted over a subset of the parallel communication channels is compromised, the compromised information does not reveal the account information (142), the purchase details (169), etc.
In one embodiment, the offer communication (741) includes purchase details (169) of the transaction, such as the identification of the items (e.g., products and/or services) purchased via the transaction, the unit prices of the items, the number of units purchased via the transaction, etc. The portal (143) is configured to store the purchase details (169) with the transaction record (301).
In one embodiment, the portal (143) to include at least some of the functions described in connection with the receipt presentation in the section entitled “RECEIPT”, such as presentation of the user interface to allow the user (101) to select a mini receipt, or suppress paper receipts in view of electronic receipts, presenting a user interface to allow the user (101) to enroll in an offer campaign, accept an offer, redeem loyalty/reward points, etc., during the presentation of the receipt or the authorization of the transaction, storing a copy of the receipt and provide additional services based on the receipt and/or the purchase details (169), such as warranty bookkeeping, recall notification, etc.
In one embodiment, the authorization response A (138) includes various information about the consumer account (146) for presentation with the receipt of the transaction, such as the account type of the consumer account (146), the reward level of the consumer account (146), a message pre-selected by the user (101), the account balance of the consumer account (146), the loyalty/reward benefits accumulated for the consumer account (146), conditions that have been satisfied for redemption of the benefit of the offer (186) stored in association with the consumer account (146), the logo of the issuer of the consumer account (146), the logo of the sponsor of the offer (186) redeemed in the transaction, the logo of the merchant operating the transaction terminal (105), the logo of an entity operating the transaction handler (103), a piece of music representative of the issuer, the sponsor, the merchant, or the entity operating the transaction handler (103), etc.
Issuer Identity
In one embodiment, offers may be initially presented or provided through an offer distribution network to users of payment accounts that are issued by different issuers, without the knowledge of the respective issuers associated with the users. In some instances, a user may have multiple payment accounts issued by different issuers; and at the time of the initial presentation of an offer to the user it may be unknown to the offer distribution network as to which of the payment accounts the user will be used to make payments for a purchase that qualifies for the benefit offer.
Issuing a statement credit to a payment account used by a user to make the payment for the purchase that qualifies for the benefit of the offer is an attractive mechanism to deliver the benefit of the offer.
However, issuer processors of the some of issuers may not be fully in compliance with a message standard for processing statement credits.
Alternatively, benefits of offers can be provided via other mechanisms, such as using a promotional code transmitted to a point of sale (POS) terminal to cause the merchant to apply a discount, changing the transaction amount during the authorization to apply the discount, meeting the requirement of an authorization request via combining authorization responses from the issuer processors and sponsor processors, etc.
In one embodiment, the mechanism to delivery the benefit of an offer to a recipient of the offer is not specified until the payment account that will be used to make the payment of a qualifying purchase is specified for the offer. After the offer is presented, the recipient of the offer is provided with an option to associate the offer with a payment account to automate the benefit redemption. When the payment account is identified for the offer, the identity of the issuer processor associated with the payment account is determined and used to select the mechanism to delivery the benefit of the offer to the recipient of the offer.
For example, if the issuer processor of the payment account specified by the recipient of the offer supports a financial transaction messaging standard for processing statement credits, the recipient of the offer is informed of the delivery of the benefit via statement credit; and a transaction handler is configured to generate a trigger record to detect a qualifying transaction and, in response the detected qualifying transaction, generate a statement credit message for the qualifying transaction that satisfies the benefit redemption requirements of the offer.
For example, if the issuer processor does not support a message standard for processing statement credits, the recipient of the offer is informed of the delivery of the benefit via an alternative mechanism (e.g., a promotional code, the change of transaction amount during authorization); and a transaction handler is configured to generate a trigger record to detect a qualifying transaction and use the alternative mechanism to deliver the benefit of the offer in response to the detection of the qualifying transaction that satisfies the benefit redemption requirements of the offer.
In some instances, a mechanism may be used for delivering the benefit of an offer without involving a transaction handler of a payment processing network. For example, a coupon code can be provided to the recipient of the offer for use with a merchant to obtain the benefit of the offer. For example, a coupon can be printed for the recipient of the offer for use with a qualified purchase. For example, an electronic coupon can be presented to the recipient of the offer for obtaining the benefit of the offer. For example, a debit card usable with a qualified transaction may be issued to the user for the benefit of the offer.
In one embodiment, how the benefit of the offer is provided to a user is not specified, until the identity of the issuer of the consumer account of the user is known (e.g., after the user associates the offer with the consumer account in ways as illustrated in
In one embodiment, the computing device includes at least one of: the media controller (149), the portal (143), the data warehouse (149), and the transaction handler (103), illustrated in the system of
In
In one embodiment, when the offer (186) is presented to the user (101), a mechanism to delivery the benefit to the user (101) is not specified.
In
After the user (101) is presented with the offer (186), the user (101) is offered the opportunity to associate the offer (186) with the account information (142) that identifies the consumer payment account (146) of the user (101) among a plurality of payment accounts in a payment processing network.
For example, the offer (186) can be associated with the account information (142) in ways as illustrated in
In
In response to the identification of the redemption method (781) for the offer (186) linked to the account information (142), the portal (143) is configured to optionally provide the user (101) with an offer communication (741) related to the redemption method (781).
For example, the offer communication (741) may be sent to the point of interaction (107) in response to the user input associating the account information (142) with the offer (186).
For example, the offer communication (741) may inform the user (101) of the delivery of the benefit of the offer (186) via statement credits, if the redemption method (781) corresponds to statement credits.
For example, the offer communication (741) may provide the user (101) a promotional code for use at the transaction terminal (105) of a merchant, if the redemption method (781) corresponds to a discount via promotional code at POS terminals.
For example, the offer communication (741) may provide the user (101) a coupon for use at the transaction terminal (105) of a merchant, if the redemption method (781) corresponds to a discount via a coupon at POS terminals.
Some of the redemption methods (e.g., 781) may require the user (101) to provide a representation of the offer (186) (e.g., a coupon, a promotional code, a debit account number, a gift certification), in addition to presenting the account information (142) to make a payment.
Some of the redemption methods (e.g., 781) do not require the user (101) to provide a representation of the offer (186) other than using the account information (142) to make a payment for a purchase that satisfies the benefit requirements of the offer (186).
When a redemption method (e.g., 781) is implemented via the transaction handler (103) detecting the qualifying transaction, the portal (143) is configured to generate a trigger record (613) to detect transaction. The trigger record (613) is configured to identify the offer (186) for further processing tasks related to the offer (186).
For example, when a transaction is detected to satisfy the requirements of the trigger record (613), other benefit redemption requirements of the offer (186) are checked. If redemption requirements of the offer (186) are all satisfied, the transaction handler (103) and/or the portal (143) is configured to provide the benefit of the offer (186) to the user (101) via the redemption method (781).
In one embodiment, the system illustrated in
The portal (143) is further configured to identify an issuer (e.g., corresponding to issuer identifier (783)) of the payment account (146) associated with the offer (186) and select, based at least in part on an identity of the issuer, a mechanism (e.g., redemption method (781)) from a plurality of mechanisms to deliver a benefit of the offer (186).
In one embodiment, the computing apparatus further includes a transaction handler (103) configured to detect a payment transaction in the payment account (146) for a purchase qualified for the benefit of the offer (186). The transaction handler (103) is further configured to provide the benefit of the offer (186) to the user (101) using the mechanism selected based at least in part on the identity of the issuer (e.g., issuer identifier (783)).
For example, when the issuer processor (145) as identified by the issuer identifier (783) supports a financial transaction messaging standard for processing statement credits, the benefit of the offer (186) is provided via a statement credit request to an issuer processor (145) associated with the issuer identifier (783).
For example, when the issuer processor (145) of the consumer account (146) of the user (101) does not support a financial transaction messaging standard for processing statement credits, the benefit is provided via a promotional code transmitted, via an authorization response for the payment transaction, to a transaction terminal initiated the payment transaction. The promotional code provided in the authorization response causes the transaction terminal (105) to apply a discount to the payment transaction as a benefit of the offer (186).
In one embodiment, a method implemented in the computing apparatus includes: receiving, in the computing apparatus from a user (101), an input associating an offer (186) provided to the user (101) with a payment account (146) identified by account information (142) of the user (101); identifying, by the computing apparatus, an issuer of the payment account (146) associated with the offer (186); selecting, by the computing apparatus based at least in part on an identity of the issuer (e.g., issuer identifier (783)), a mechanism (e.g., benefit redemption method (781)) from a plurality of mechanisms to deliver a benefit of the offer (186); detecting, by the computing apparatus, a payment transaction in the payment account (146) for a purchase qualified for the benefit of the offer (186); and providing, by the computing apparatus, the benefit of the offer (186) to the user (101) using the mechanism (e.g., benefit redemption method (781)) selected based at least in part on the identity of the issuer (e.g., issuer identifier (783)).
In one embodiment, the method further includes: notifying the user (101), at a communication reference (611) associated with the consumer account (146), about the mechanism (e.g., benefit redemption method (781)) selected to deliver the benefit of the offer (186).
In one embodiment, the mechanism (e.g., benefit redemption method (781)) selected for the offer (186) is statement credit provided to the payment account (146); and the selection is a result of a determination that an issuer processor of the issuer is in compliance with electronic financial transaction message standard for statement credit.
However, if it is determined that an issuer processor of the issuer is not in compliance with electronic financial transaction message standard for statement credit, the mechanism (e.g., benefit redemption method (781)) selected for the offer (186) as provided to the user (101) is to use an alternative benefit redemption method, such as a promotional code transmitted in an authorization response for the payment transaction that qualifies for the benefit of the offer (186), to apply the benefit at a transaction terminal that initiates the payment transaction.
In another example of the alternative benefit redemption method, the benefit of the offer (186) is applied to the payment transaction during authorization of the payment transaction.
For example, the benefit of the offer (186) can be applied to the payment transaction via adjusting a transaction amount via an authorization response of the payment transaction, as illustrated in
For example, the benefit of the offer (186) can be applied to the payment transaction via reducing a transaction amount in the payment account and generating a second transaction with a sponsor processor of the benefit, as illustrated in
In one embodiment, prior to the receiving of the input from the user, the offer (186) is communicated to the user (101) to identify a benefit without specifying a mechanism to deliver the benefit.
After the receiving of the input from the user, the portal (143) is configured to communicate to the user (101) of the payment account (146) to notify the user (101) of the mechanism (e.g., redemption method (781)) selected for the offer (186) based at least in part on the identity of the issuer (e.g., issuer identifier (783)).
In one embodiment, the user (101) is notified of the mechanism (e.g., redemption method (781)) selected for the offer (186), using a communication reference (611) pre-associated with the payment account (146) of the user (101) prior to the receiving of the input from the user (101).
In one embodiment, the user (101) is notified of the mechanism (e.g., redemption method (781)) selected for the offer (186) as a response to the input from the user (101) to associate the offer (186) with the payment account (146) of the user (101).
In one embodiment, the data warehouse (149) is configured to store data associating issuer identifiers (e.g., 783) with mechanisms (e.g., redemption method (781)) to deliver offer benefits. The selecting of the mechanism (e.g., redemption method (781)) for the offer (186) is based on the identity of the issuer (e.g., issuer identifier (783)) and the data associating issuer identifiers (e.g., 783) with mechanisms (e.g., redemption method (781)) to deliver offer benefits.
In one embodiment, the portal (143) is configured to transmit a message to a communication reference (611) pre-associated with the account information (142) of the payment account (146) of the user (101), where the message is configured to notify the user (101) of the benefit applied to the payment transaction. For example, the message can be transmitted during the authorization of the payment transaction that qualifies for the benefit of the offer (186). In one embodiment, the transmission of the message is initiated during the authorization of the payment transaction that qualifies for the benefit of the offer (186).
In one embodiment, the portal (143) is configured to generate a trigger record (613) to detect the payment transaction, in response to the input from the user (101) and the selection of the benefit redemption method/mechanism (781) for the offer (186) saved under the account information (142) of the consumer payment account (146) of the user (101). The trigger record (613) is configured to include a portion of the benefit redemption requirements of the offer (186); and when a transaction satisfying the conditions of the trigger record (613) is detected, the transaction is further processed by the portal (143), the transaction handler (103), or a separate computer (e.g., a rule engine), to determine if the benefit redemption requirements are all satisfied for the offer (186).
Details about the system in one embodiment are provided in the sections entitled “SYSTEM,” “CENTRALIZED DATA WAREHOUSE” and “HARDWARE.”
Variations
Some embodiments use more or fewer components than those illustrated in the figures.
In one embodiment, at least some of the profile generator (121), correlator (117), profile selector (129), and advertisement selector (133) are controlled by the entity that operates the transaction handler (103). In another embodiment, at least some of the profile generator (121), correlator (117), profile selector (129), and advertisement selector (133) are not controlled by the entity that operates the transaction handler (103).
In one embodiment, the products and/or services purchased by the user (101) are also identified by the information transmitted from the merchants or service providers. Thus, the transaction data (109) may include identification of the individual products and/or services, which allows the profile generator (121) to generate transaction profiles (127) with fine granularity or resolution. In one embodiment, the granularity or resolution may be at a level of distinct products and services that can be purchased (e.g., stock-keeping unit (SKU) level), or category or type of products or services, or vendor of products or services, etc.
In one embodiment, the entity operating the transaction handler (103) provides the intelligence information in real time as the request for the intelligence information occurs. In other embodiments, the entity operating the transaction handler (103) may provide the intelligence information in batch mode. The intelligence information can be delivered via online communications (e.g., via an application programming interface (API) on a website, or other information server), or via physical transportation of a computer readable media that stores the data representing the intelligence information.
In one embodiment, the intelligence information is communicated to various entities in the system in a way similar to, and/or in parallel with the information flow in the transaction system to move money. The transaction handler (103) routes the information in the same way it routes the currency involved in the transactions.
In one embodiment, the portal (143) provides a user interface to allow the user (101) to select items offered on different merchant websites and store the selected items in a wish list for comparison, reviewing, purchasing, tracking, etc. The information collected via the wish list can be used to improve the transaction profiles (127) and derive intelligence on the needs of the user (101); and targeted advertisements can be delivered to the user (101) via the wish list user interface provided by the portal (143). Examples of user interface systems to manage wish lists are provided in U.S. patent application Ser. No. 12/683,802, filed Jan. 7, 2010, assigned U.S. Pat. App. Pub. No. 2010/0174623, and entitled “System and Method for Managing Items of Interest Selected from Online Merchants,” the disclosure of which is 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 (301); and in one embodiment, an aggregated spending profile (341) is generated from the transaction records (301), in a way illustrated in
In
A “card-present” transaction typically 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 typically 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).
The transaction records (301) of one embodiment may further include details about the products and/or services involved in the purchase.
When there is voluminous data representing the transaction records (301), the spending patterns reflected in the transaction records (301) can be difficult to recognize by an ordinary person.
In
In
In
Examples of the spending frequency variables (313) and spending amount variables (315) defined for various merchant categories (e.g., 306) in one embodiment are provided in U.S. patent application Ser. No. 12/537,566, filed Aug. 7, 2009, assigned U.S. Pat. App. Pub. No. 2010/0306029, and entitled “Cardholder Clusters,” and in U.S. patent application Ser. No. 12/777,173, filed May 10, 2010, assigned U.S. Pat. App. Pub. No. 2010/0306032, and entitled “Systems and Methods to Summarize Transaction Data,” the disclosures of which applications are hereby incorporated herein by reference.
In
The transaction records (301) can be aggregated according to a buying entity, or a selling entity. For example, the aggregation (317) can be performed at account level, person level, family level, company level, neighborhood level, city level, region level, etc. to analyze the spending patterns across various areas (e.g., sellers, products or services) for the respective aggregated buying entity. For example, the transaction records (301) for a particular merchant having transactions with multiple accounts can be aggregated for a merchant level analysis. For example, the transaction records (301) for a particular merchant group can be aggregated for a merchant group level analysis. The aggregation (317) can be formed separately for different types of transactions, such as transactions made online, offline, via phone, and/or “card-present” transactions vs. “card-not-present” transactions, which can be used to identify the spending pattern differences among different types of transactions.
In
Once the cluster definitions (333) are obtained from the cluster analysis (329), the identity of the cluster (e.g., cluster ID (343)) that contains the entity ID (322) can be used to characterize spending behavior of the entity represented by the entity ID (322). The entities in the same cluster are considered to have similar spending behaviors.
In
In
Once the factor definitions (331) are obtained from the factor analysis (327), the factor definitions (331) can be applied to the variable values (321) to determine factor values (344) for the aggregated spending profile (341). Since redundancy and correlation are reduced in the factors, the number of factors is typically much smaller than the number of the original variables (e.g., 313, 315). Thus, the factor values (344) represent the concise summary of the original variables (e.g., 313, 315).
For example, there may be thousands of variables on spending frequency and amount for different merchant categories; and the factor analysis (327) can reduce the factor number to less than one hundred (and even less than twenty). In one example, a twelve-factor solution is obtained, which allows the use of twelve factors to combine the thousands of the original variables (313, 315); and thus, the spending behavior in thousands of merchant categories can be summarized via twelve factor values (344). In one embodiment, each factor is combination of at least four variables; and a typical variable has contributions to more than one factor.
In
In general, an aggregated spending profile (341) may include more or fewer fields than those illustrated in
In
In
In
The data samples can also be used to perform (365) cluster analysis (329) to identify cluster solutions (e.g., cluster definitions (333)). The cluster solutions can be adjusted (367) to improve similarity in cluster identifications based on different sets of transaction data (109). For example, cluster definitions (333) can be applied to the transactions in the time period under analysis (e.g., the past twelve months) and be applied separately to the transactions in a prior time period (e.g., the twelve months before the past twelve months) to obtain two sets of cluster identifications for various entities. The cluster definitions (333) can be adjusted to improve the correlation between the two set of cluster identifications.
Optionally, human understandable characteristics of the factors and clusters are identified (369) to name the factors and clusters. For example, when the spending behavior of a cluster appears to be the behavior of an internet loyalist, the cluster can be named “internet loyalist” such that if a cardholder is found to be in the “internet loyalist” cluster, the spending preferences and patterns of the cardholder can be easily perceived.
In one embodiment, the factor analysis (327) and the cluster analysis (329) are performed periodically (e.g., once a year, or six months) to update the factor definitions (331) and the cluster definitions (333), which may change as the economy and the society change over time.
In
Details about aggregated spending profile (341) in one embodiment are provided in U.S. patent application Ser. No. 12/777,173, filed May 10, 2010, assigned U.S. Pat. App. Pub. No. 2010/0306032, and entitled “Systems and Methods to Summarize Transaction Data,” the disclosure of which is hereby incorporated herein by reference.
In one embodiment, a set of profiles are generated from the transaction data for a plurality of geographical regions, such as mutually exclusive, non-overlapping regions defined by postal codes. Transactions of account holders residing in the regions are aggregated according to merchant categories for the respective regions and subsequently normalized to obtain preference indicators that reveal the spending preferences of the account holders in the respective regions. Each of the profiles for respective regions is based on a plurality of different account holders and/or households to avoid revealing private information about individual account holders or families. Further, the profiles are constructed in a way to make it impossible to reverse calculate the transaction amounts. Further details and examples about profiles constructed for regions in one embodiment are provided in U.S. patent application Ser. No. 13/675,301, filed Nov. 13, 2012 and entitled “Systems and Methods to Summarize Transaction data,” the disclosure of which is hereby incorporated herein by reference.
Transaction Processing and Data
In
In
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
The account identification device (141) of one embodiment 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). The account identification device (141) may optionally include a mobile phone having an integrated smartcard.
The account information (142) may be 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).
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).
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.
The account identification device (141) may include 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.
The transaction terminal (105) of one embodiment 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 general, 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. Dedicated communication channels may be 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
Typically, the transaction handler (103) is implemented using a powerful computer, or cluster of computers functioning as a unit, controlled by instructions stored on a computer readable medium. The transaction handler (103) is configured to support and deliver authorization services, exception file services, and clearing and settlement services. The transaction handler (103) has a subsystem to process authorization requests and another subsystem to perform clearing and settlement services. 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. The transaction handler (103) interconnects the issuer processors (e.g., 145) and the acquirer processor (e.g., 147) to facilitate payment communications.
In
In
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 (301), such as merchant category (306), transaction date (303), amount (304), etc. Examples and techniques in one embodiment are provided in U.S. patent application Ser. No. 11/378,215, filed Mar. 16, 2006, assigned U.S. Pat. App. Pub. No. 2007/0055597, and 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. patent application Ser. No. 12/191,796, filed Aug. 14, 2008, assigned U.S. Pat. App. Pub. No. 2009/0048884, and entitled “Merchant Benchmarking Tool,” U.S. patent application Ser. No. 12/940,562, filed Nov. 5, 2010, and U.S. patent application Ser. No. 12/940,664, filed Nov. 5, 2010, the disclosures of which applications are 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 components of systems illustrated in various figures, such as the transaction handler (103), the profile generator (121), the media controller (115), the portal (143), the profile selector (129), the advertisement selector (133), the user tracker (113), the correlator, and their associated storage devices, such as the data warehouse (149).
In one embodiment, at least some of the components such as the transaction handler (103), the transaction terminal (105), the point of interaction (107), the user tracker (113), the media controller (115), the correlator (117), the profile generator (121), the profile selector (129), the advertisement selector (133), the portal (143), the issuer processor (145), the acquirer processor (147), and the account identification device (141), can be implemented as a computer system, such as a data processing system (170) illustrated in
Further, the data illustrated in the figures, such as transaction data (109), account data (111), transaction profiles (127), and advertisement data (135), can be stored in storage devices of one or more computers accessible to the corresponding components. For example, the transaction data (109) can be stored in the data warehouse (149) that can be implemented as a data processing system 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. For example, the features described above in connection with “in one embodiment” or “in some embodiments” can be all optionally included in one implementation, except where the dependency of certain features on other features, as apparent from the description, may limit the options of excluding selected features from the implementation, and incompatibility of certain features with other features, as apparent from the description, may limit the options of including selected features together in the implementation.
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. 61/722,603, filed Nov. 5, 2012 and entitled “Systems and Methods to Provide Offer Benefits based on Issuer Identity”, the disclosure of which application is hereby incorporated herein by reference. The present application relates to U.S. Pat. App. Pub. No. 2013/0091000, published Apr. 11, 2013 and entitled “Systems and Methods to Provide Discount at Point of Sales Terminals,” U.S. Pat. App. Pub. No. 2013/0246150, published Sep. 19, 2013 and entitled “Systems and Methods to Apply the Benefit of Offers via a Transaction Handler”, U.S. Pat. App. Pub. No. 2013/0124287, published May 16, 2013 and entitled “Systems and Methods to Provide Discount at Point of Sales Terminals”, U.S. Pat. App. Pub. No. 2013-0268333, published Oct. 10, 2013 and entitled “Systems and Methods to Process Transactions and Offers via a Gateway”, and U.S. Pat. App. Pub. No. 2011/0125565, published May 26, 2011 and entitled “Systems and Methods for Multi-Channel Offer Redemption,” the disclosures of which applications are hereby incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4941090 | McCarthy | Jul 1990 | A |
| 5025372 | Burton et al. | Jun 1991 | A |
| 5117355 | McCarthy | May 1992 | A |
| 5202826 | McCarthy | Apr 1993 | A |
| 5287268 | McCarthy | Feb 1994 | A |
| 5649118 | Carlisle et al. | Jul 1997 | A |
| 5689100 | Carrithers et al. | Nov 1997 | A |
| 5708422 | Blonder et al. | Jan 1998 | A |
| 5774870 | Storey | Jun 1998 | A |
| 5794118 | Yoshinobu | Aug 1998 | A |
| 5794210 | Goldhaber et al. | Aug 1998 | A |
| RE36116 | McCarthy | Feb 1999 | E |
| 5923016 | Fredregill et al. | Jul 1999 | A |
| 5937391 | Ikeda et al. | Aug 1999 | A |
| 5956694 | Powell | Sep 1999 | A |
| 6032136 | Brake, Jr. et al. | Feb 2000 | A |
| 6138911 | Fredregill et al. | Oct 2000 | A |
| 6243687 | Powell | Jun 2001 | B1 |
| 6251017 | Leason et al. | Jun 2001 | B1 |
| 6332126 | Peirce et al. | Dec 2001 | B1 |
| 6334108 | Deaton et al. | Dec 2001 | B1 |
| 6336099 | Barnett et al. | Jan 2002 | B1 |
| 6341353 | Herman et al. | Jan 2002 | B1 |
| 6408286 | Heiden | Jun 2002 | B1 |
| 6450407 | Freeman et al. | Sep 2002 | B1 |
| 6594640 | Postrel | Jul 2003 | B1 |
| 6606745 | Maggio | Aug 2003 | B2 |
| 6663105 | Sullivan et al. | Dec 2003 | B1 |
| 6721743 | Sakakibara | Apr 2004 | B1 |
| 6741968 | Jacoves et al. | May 2004 | B2 |
| 6748365 | Quinlan et al. | Jun 2004 | B1 |
| 6820061 | Postrel | Nov 2004 | B2 |
| 6829586 | Postrel | Dec 2004 | B2 |
| 6842739 | Postrel | Jan 2005 | B2 |
| 6856820 | Kolls | Feb 2005 | B1 |
| 6865547 | Brake, Jr. et al. | Mar 2005 | B1 |
| 6910003 | Arnold et al. | Jun 2005 | B1 |
| 6915271 | Meyer et al. | Jul 2005 | B1 |
| 6947898 | Postrel | Sep 2005 | B2 |
| 6978250 | Kawan et al. | Dec 2005 | B1 |
| 7054830 | Eggleston et al. | May 2006 | B1 |
| 7072864 | Brake, Jr. et al. | Jul 2006 | B2 |
| 7096190 | Postrel | Aug 2006 | B2 |
| 7134087 | Bushold et al. | Nov 2006 | B2 |
| 7143069 | Lacivita et al. | Nov 2006 | B2 |
| 7163145 | Cohagan et al. | Jan 2007 | B2 |
| 7194423 | Walker | Mar 2007 | B2 |
| 7263507 | Brake, Jr. et al. | Aug 2007 | B1 |
| 7370811 | Turner et al. | May 2008 | B2 |
| 7376580 | Walker et al. | May 2008 | B1 |
| 7398225 | Voltmer et al. | Jul 2008 | B2 |
| 7424617 | Boyd et al. | Sep 2008 | B2 |
| 7428498 | Voltmer et al. | Sep 2008 | B2 |
| 7464859 | Hawkins | Dec 2008 | B1 |
| 7516883 | Hardesty et al. | Apr 2009 | B2 |
| 7606730 | Antonucci | Oct 2009 | B2 |
| 7624041 | Postrel | Nov 2009 | B2 |
| 7665660 | Degliantoni et al. | Feb 2010 | B2 |
| 7680688 | Hessburg et al. | Mar 2010 | B2 |
| 7686218 | Hessburg et al. | Mar 2010 | B2 |
| 7742943 | Postrel | Jun 2010 | B2 |
| 7753264 | Shafer et al. | Jul 2010 | B2 |
| 7765124 | Postrel | Jul 2010 | B2 |
| 7769630 | Postrel | Aug 2010 | B2 |
| 7777053 | Sanganbhatla et al. | Aug 2010 | B2 |
| 7828206 | Hessburg et al. | Nov 2010 | B2 |
| 7844490 | Patterson | Nov 2010 | B2 |
| 7853529 | Walker et al. | Dec 2010 | B1 |
| 7868218 | Clark et al. | Jan 2011 | B2 |
| 7870022 | Bous et al. | Jan 2011 | B2 |
| 7894634 | Chung | Feb 2011 | B2 |
| 7933800 | Main et al. | Apr 2011 | B2 |
| 7958030 | Kemper et al. | Jun 2011 | B2 |
| 8010405 | Bortolin et al. | Aug 2011 | B1 |
| 8046256 | Chien et al. | Oct 2011 | B2 |
| 8155999 | de Boer et al. | Apr 2012 | B2 |
| 8180671 | Cohagan et al. | May 2012 | B2 |
| 8260788 | Saito | Sep 2012 | B2 |
| 8265993 | Chien et al. | Sep 2012 | B2 |
| 8266031 | Norris et al. | Sep 2012 | B2 |
| 8285643 | Isaacson et al. | Oct 2012 | B2 |
| 8301593 | Hoffmann et al. | Oct 2012 | B2 |
| 8302030 | Soroca et al. | Oct 2012 | B2 |
| 8313023 | McGhie et al. | Nov 2012 | B1 |
| 8315929 | Allen-Rouman et al. | Nov 2012 | B2 |
| 8332290 | Venturo et al. | Dec 2012 | B1 |
| 8341081 | Wang et al. | Dec 2012 | B1 |
| 8342399 | McGhie et al. | Jan 2013 | B1 |
| 8401967 | Postrel | Mar 2013 | B1 |
| 8458016 | Medina, III et al. | Jun 2013 | B1 |
| 8463706 | Cervenka et al. | Jun 2013 | B2 |
| 8478640 | Postrel | Jul 2013 | B2 |
| 8511550 | McGhie et al. | Aug 2013 | B1 |
| 8523054 | Yankovich et al. | Sep 2013 | B2 |
| 8538812 | Ramer et al. | Sep 2013 | B2 |
| 8612208 | Cooper et al. | Dec 2013 | B2 |
| 8630989 | Blohm et al. | Jan 2014 | B2 |
| 8639567 | Winters | Jan 2014 | B2 |
| 8639571 | Leason | Jan 2014 | B1 |
| 8639629 | Hoffman | Jan 2014 | B1 |
| 8650124 | Singh | Feb 2014 | B2 |
| 8682715 | Cedeno | Mar 2014 | B1 |
| 8682791 | Bies et al. | Mar 2014 | B2 |
| 8725568 | Cervenka et al. | May 2014 | B2 |
| 8732082 | Karim | May 2014 | B2 |
| 8751295 | Tiku et al. | Jun 2014 | B2 |
| 8880431 | Ovick et al. | Nov 2014 | B2 |
| 8939356 | Pourfallah et al. | Jan 2015 | B2 |
| 8942992 | Zhu | Jan 2015 | B1 |
| 8965810 | Cervenka et al. | Feb 2015 | B2 |
| 9031859 | Salmon et al. | May 2015 | B2 |
| 9460436 | Ovick et al. | Oct 2016 | B2 |
| 9495690 | Ovick et al. | Nov 2016 | B2 |
| 9626678 | Ovick et al. | Apr 2017 | B2 |
| 20010034654 | L. Vigil et al. | Oct 2001 | A1 |
| 20010054003 | Chien et al. | Dec 2001 | A1 |
| 20020013728 | Wilkman | Jan 2002 | A1 |
| 20020026354 | Shoji et al. | Feb 2002 | A1 |
| 20020046116 | Hohle et al. | Apr 2002 | A1 |
| 20020052860 | Geshwind | May 2002 | A1 |
| 20020062249 | Iannacci | May 2002 | A1 |
| 20020103753 | Schimmel | Aug 2002 | A1 |
| 20020128057 | Walker et al. | Sep 2002 | A1 |
| 20020133467 | Hobson et al. | Sep 2002 | A1 |
| 20020160761 | Wolfe | Oct 2002 | A1 |
| 20020194128 | Maritzen et al. | Dec 2002 | A1 |
| 20030004808 | Elhaoussine et al. | Jan 2003 | A1 |
| 20030040964 | Lacek | Feb 2003 | A1 |
| 20030055727 | Walker et al. | Mar 2003 | A1 |
| 20030091216 | Silverbrook et al. | May 2003 | A1 |
| 20030115100 | Teicher | Jun 2003 | A1 |
| 20030120554 | Hogan et al. | Jun 2003 | A1 |
| 20030140004 | O'Leary et al. | Jul 2003 | A1 |
| 20030144907 | Cohen, Jr. et al. | Jul 2003 | A1 |
| 20030144965 | Prasad et al. | Jul 2003 | A1 |
| 20030216967 | Williams | Nov 2003 | A1 |
| 20030225618 | Hessburg et al. | Dec 2003 | A1 |
| 20030225619 | Dokken et al. | Dec 2003 | A1 |
| 20030233439 | Stone et al. | Dec 2003 | A1 |
| 20030236704 | Antonucci | Dec 2003 | A1 |
| 20030236712 | Antonucci et al. | Dec 2003 | A1 |
| 20040024739 | Copperman et al. | Feb 2004 | A1 |
| 20040039693 | Nauman et al. | Feb 2004 | A1 |
| 20040049423 | Kawashima et al. | Mar 2004 | A1 |
| 20040083170 | Bam et al. | Apr 2004 | A1 |
| 20040088216 | Bangalore | May 2004 | A1 |
| 20040088376 | McCanne et al. | May 2004 | A1 |
| 20040104760 | Ando | Jun 2004 | A1 |
| 20040117250 | Lubow et al. | Jun 2004 | A1 |
| 20040133472 | Leason et al. | Jul 2004 | A1 |
| 20040138949 | Darnton et al. | Jul 2004 | A1 |
| 20040140361 | Paul et al. | Jul 2004 | A1 |
| 20040186773 | George et al. | Sep 2004 | A1 |
| 20040203648 | Wong | Oct 2004 | A1 |
| 20040238622 | Freiberg | Dec 2004 | A1 |
| 20040249710 | Smith et al. | Dec 2004 | A1 |
| 20040249753 | Blinn et al. | Dec 2004 | A1 |
| 20040260608 | Lewis et al. | Dec 2004 | A1 |
| 20050010533 | Cooper | Jan 2005 | A1 |
| 20050021399 | Postrel | Jan 2005 | A1 |
| 20050021401 | Postrel | Jan 2005 | A1 |
| 20050033643 | Smith | Feb 2005 | A1 |
| 20050060225 | Postrel | Mar 2005 | A1 |
| 20050075932 | Mankoff | Apr 2005 | A1 |
| 20050080727 | Postrel | Apr 2005 | A1 |
| 20050091152 | Suisa | Apr 2005 | A1 |
| 20050096975 | Moshe | May 2005 | A1 |
| 20050114213 | Smith et al. | May 2005 | A1 |
| 20050119938 | Smith et al. | Jun 2005 | A1 |
| 20050149394 | Postrel | Jul 2005 | A1 |
| 20050205666 | Ward et al. | Sep 2005 | A1 |
| 20050240472 | Postrel | Oct 2005 | A1 |
| 20050240478 | Lubow et al. | Oct 2005 | A1 |
| 20050251469 | Nandakumar | Nov 2005 | A1 |
| 20050267800 | Tietzen et al. | Dec 2005 | A1 |
| 20060010033 | Thomas | Jan 2006 | A1 |
| 20060020511 | Postrel | Jan 2006 | A1 |
| 20060053056 | Alspach-Goss et al. | Mar 2006 | A1 |
| 20060059040 | Eldred et al. | Mar 2006 | A1 |
| 20060111978 | Tietzen et al. | May 2006 | A1 |
| 20060129456 | Walker et al. | Jun 2006 | A1 |
| 20060136299 | Ruhmkorf | Jun 2006 | A1 |
| 20060161478 | Turner et al. | Jul 2006 | A1 |
| 20060181515 | Fletcher et al. | Aug 2006 | A1 |
| 20060184419 | Postrel | Aug 2006 | A1 |
| 20060190337 | Ayers, Jr. et al. | Aug 2006 | A1 |
| 20060206376 | Gibbs et al. | Sep 2006 | A1 |
| 20060208064 | Mendelovich et al. | Sep 2006 | A1 |
| 20060208065 | Mendelovich et al. | Sep 2006 | A1 |
| 20060253321 | Heywood | Nov 2006 | A1 |
| 20060253392 | Davies | Nov 2006 | A1 |
| 20060259364 | Strock et al. | Nov 2006 | A1 |
| 20060259390 | Rosenberger | Nov 2006 | A1 |
| 20060261149 | Raghavendra Tulluri | Nov 2006 | A1 |
| 20060277103 | Fujita et al. | Dec 2006 | A1 |
| 20060278697 | Lovett | Dec 2006 | A1 |
| 20060287943 | Postrel | Dec 2006 | A1 |
| 20070005416 | Jackson et al. | Jan 2007 | A1 |
| 20070005510 | Bloodworth et al. | Jan 2007 | A1 |
| 20070011044 | Hansen | Jan 2007 | A1 |
| 20070038515 | Postrel | Feb 2007 | A1 |
| 20070043613 | Longest | Feb 2007 | A1 |
| 20070043619 | Leason et al. | Feb 2007 | A1 |
| 20070043620 | Leason et al. | Feb 2007 | A1 |
| 20070078719 | Schmitt et al. | Apr 2007 | A1 |
| 20070100691 | Patterson | May 2007 | A1 |
| 20070105536 | Tingo, Jr. | May 2007 | A1 |
| 20070112629 | Solomon et al. | May 2007 | A1 |
| 20070129955 | Dalmia et al. | Jun 2007 | A1 |
| 20070129998 | Postrel | Jun 2007 | A1 |
| 20070130011 | Postrel | Jun 2007 | A1 |
| 20070143178 | Citrin et al. | Jun 2007 | A1 |
| 20070168354 | Ramer et al. | Jul 2007 | A1 |
| 20070192784 | Postrel | Aug 2007 | A1 |
| 20070198338 | Heywood | Aug 2007 | A1 |
| 20070214049 | Postrel | Sep 2007 | A1 |
| 20070226059 | Postrel | Sep 2007 | A1 |
| 20070260509 | Hines et al. | Nov 2007 | A1 |
| 20070288313 | Brodson et al. | Dec 2007 | A1 |
| 20070299742 | Williams et al. | Dec 2007 | A1 |
| 20080010154 | Tietzen et al. | Jan 2008 | A1 |
| 20080011820 | Brown et al. | Jan 2008 | A1 |
| 20080011837 | Wesley | Jan 2008 | A1 |
| 20080015300 | Chrobaczek | Jan 2008 | A1 |
| 20080021784 | Hessburg et al. | Jan 2008 | A1 |
| 20080040222 | Gee | Feb 2008 | A1 |
| 20080040270 | Buchheit et al. | Feb 2008 | A1 |
| 20080059303 | Fordyce | Mar 2008 | A1 |
| 20080059306 | Fordyce et al. | Mar 2008 | A1 |
| 20080071587 | Granucci et al. | Mar 2008 | A1 |
| 20080071640 | Nguyen | Mar 2008 | A1 |
| 20080077499 | Ariff et al. | Mar 2008 | A1 |
| 20080103968 | Bies et al. | May 2008 | A1 |
| 20080120221 | Toneguzzo | May 2008 | A1 |
| 20080133350 | White et al. | Jun 2008 | A1 |
| 20080133351 | White et al. | Jun 2008 | A1 |
| 20080147496 | Bal et al. | Jun 2008 | A1 |
| 20080147534 | Ephrati et al. | Jun 2008 | A1 |
| 20080154676 | Suk | Jun 2008 | A1 |
| 20080154702 | Pleban | Jun 2008 | A1 |
| 20080154722 | Galinos | Jun 2008 | A1 |
| 20080177627 | Cefail | Jul 2008 | A1 |
| 20080195528 | Keithley | Aug 2008 | A1 |
| 20080201224 | Owens et al. | Aug 2008 | A1 |
| 20080201226 | Carlson et al. | Aug 2008 | A1 |
| 20080210753 | Plozay et al. | Sep 2008 | A1 |
| 20080217397 | Degliantoni et al. | Sep 2008 | A1 |
| 20080221986 | Soicher et al. | Sep 2008 | A1 |
| 20080222049 | Loomis et al. | Sep 2008 | A1 |
| 20080228563 | Zellner et al. | Sep 2008 | A1 |
| 20080228583 | MacDonald et al. | Sep 2008 | A1 |
| 20080230600 | Black et al. | Sep 2008 | A1 |
| 20080249861 | Carotta et al. | Oct 2008 | A1 |
| 20080270246 | Chen | Oct 2008 | A1 |
| 20080301001 | Baumgartner, IV et al. | Dec 2008 | A1 |
| 20080313034 | Wise | Dec 2008 | A1 |
| 20080313044 | Aaltonen et al. | Dec 2008 | A1 |
| 20090006203 | Fordyce, III et al. | Jan 2009 | A1 |
| 20090018909 | Grecia | Jan 2009 | A1 |
| 20090030793 | Fordyce, III | Jan 2009 | A1 |
| 20090048884 | Olives et al. | Feb 2009 | A1 |
| 20090048916 | Nuzum et al. | Feb 2009 | A1 |
| 20090076911 | Vo et al. | Mar 2009 | A1 |
| 20090076912 | Rajan et al. | Mar 2009 | A1 |
| 20090106112 | Dalmia et al. | Apr 2009 | A1 |
| 20090106115 | James et al. | Apr 2009 | A1 |
| 20090106300 | Brown | Apr 2009 | A1 |
| 20090112721 | Hammad et al. | Apr 2009 | A1 |
| 20090150235 | Blythe | Jun 2009 | A1 |
| 20090176580 | Herrmann et al. | Jul 2009 | A1 |
| 20090198572 | Jurgens | Aug 2009 | A1 |
| 20090240627 | Rodriguez et al. | Sep 2009 | A1 |
| 20090271262 | Hammad | Oct 2009 | A1 |
| 20090292595 | Tonnison et al. | Nov 2009 | A1 |
| 20090307118 | Baumgartner, IV | Dec 2009 | A1 |
| 20090307130 | Tan | Dec 2009 | A1 |
| 20090313109 | Bous | Dec 2009 | A1 |
| 20100010901 | Marshall et al. | Jan 2010 | A1 |
| 20100030688 | Patterson | Feb 2010 | A1 |
| 20100042517 | Paintin et al. | Feb 2010 | A1 |
| 20100051691 | Brooks et al. | Mar 2010 | A1 |
| 20100057551 | Blaisdell | Mar 2010 | A1 |
| 20100057553 | Ameiss et al. | Mar 2010 | A1 |
| 20100070376 | Proud et al. | Mar 2010 | A1 |
| 20100075638 | Carlson et al. | Mar 2010 | A1 |
| 20100076820 | Davis | Mar 2010 | A1 |
| 20100100484 | Nguyen et al. | Apr 2010 | A1 |
| 20100106598 | Grimes | Apr 2010 | A1 |
| 20100125737 | Kang | May 2010 | A1 |
| 20100145855 | Fordyce, III et al. | Jun 2010 | A1 |
| 20100161404 | Taylor et al. | Jun 2010 | A1 |
| 20100169215 | Balasubramanian et al. | Jul 2010 | A1 |
| 20100174596 | Gilman et al. | Jul 2010 | A1 |
| 20100211445 | Bodington | Aug 2010 | A1 |
| 20100211469 | Salmon et al. | Aug 2010 | A1 |
| 20100223145 | Dragt | Sep 2010 | A1 |
| 20100274626 | Carlson | Oct 2010 | A1 |
| 20100274659 | Antonucci et al. | Oct 2010 | A1 |
| 20100280892 | Uzunalioglu et al. | Nov 2010 | A1 |
| 20100291895 | Drzyzga et al. | Nov 2010 | A1 |
| 20100299194 | Snyder et al. | Nov 2010 | A1 |
| 20100306032 | Jolley | Dec 2010 | A1 |
| 20100312626 | Cervenka | Dec 2010 | A1 |
| 20100312631 | Cervenka | Dec 2010 | A1 |
| 20100312632 | Cervenka | Dec 2010 | A1 |
| 20100312633 | Cervenka | Dec 2010 | A1 |
| 20100312634 | Cervenka | Dec 2010 | A1 |
| 20100312635 | Cervenka | Dec 2010 | A1 |
| 20110022448 | Strock et al. | Jan 2011 | A1 |
| 20110022514 | Lal et al. | Jan 2011 | A1 |
| 20110035278 | Fordyce, III et al. | Feb 2011 | A1 |
| 20110047019 | Cervenka et al. | Feb 2011 | A1 |
| 20110047023 | Lieblang et al. | Feb 2011 | A1 |
| 20110066483 | Salmon et al. | Mar 2011 | A1 |
| 20110082739 | Pourfallah | Apr 2011 | A1 |
| 20110087530 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110087531 | Winters et al. | Apr 2011 | A1 |
| 20110103586 | Nobre | May 2011 | A1 |
| 20110125565 | MacIlwaine | May 2011 | A1 |
| 20110145148 | Hammad | Jun 2011 | A1 |
| 20110161230 | Singh | Jun 2011 | A1 |
| 20110191417 | Rathod | Aug 2011 | A1 |
| 20110218868 | Young et al. | Sep 2011 | A1 |
| 20110231258 | Winters | Sep 2011 | A1 |
| 20110238483 | Yoo et al. | Sep 2011 | A1 |
| 20110264567 | Clyne | Oct 2011 | A1 |
| 20110276493 | Graham, III et al. | Nov 2011 | A1 |
| 20110276495 | Varadarajan et al. | Nov 2011 | A1 |
| 20110288918 | Cervenka et al. | Nov 2011 | A1 |
| 20110288924 | Thomas et al. | Nov 2011 | A1 |
| 20110295675 | Reodica | Dec 2011 | A1 |
| 20120010940 | Masi | Jan 2012 | A1 |
| 20120016728 | Ahmad et al. | Jan 2012 | A1 |
| 20120035998 | Chien et al. | Feb 2012 | A1 |
| 20120041812 | Postrel | Feb 2012 | A1 |
| 20120054000 | Boppert et al. | Mar 2012 | A1 |
| 20120101881 | Taylor et al. | Apr 2012 | A1 |
| 20120101894 | Sterling et al. | Apr 2012 | A1 |
| 20120123849 | Armstrong | May 2012 | A1 |
| 20120130705 | Sun et al. | May 2012 | A1 |
| 20120150669 | Langley et al. | Jun 2012 | A1 |
| 20120179531 | Kim | Jul 2012 | A1 |
| 20120191525 | Singh et al. | Jul 2012 | A1 |
| 20120215610 | Amaro et al. | Aug 2012 | A1 |
| 20120215614 | Hochstatter et al. | Aug 2012 | A1 |
| 20120215624 | Ramer et al. | Aug 2012 | A1 |
| 20120215638 | Bennett et al. | Aug 2012 | A1 |
| 20120221446 | Grigg et al. | Aug 2012 | A1 |
| 20120226545 | Gebb et al. | Sep 2012 | A1 |
| 20120226604 | Isaacson et al. | Sep 2012 | A1 |
| 20120233074 | Dangott et al. | Sep 2012 | A1 |
| 20120239477 | Cueli et al. | Sep 2012 | A1 |
| 20120245987 | Isaacson et al. | Sep 2012 | A1 |
| 20120267432 | Kuttuva | Oct 2012 | A1 |
| 20120271689 | Etheredge et al. | Oct 2012 | A1 |
| 20120271691 | Hammad et al. | Oct 2012 | A1 |
| 20120271697 | Gilman | Oct 2012 | A1 |
| 20120271703 | Postrel | Oct 2012 | A1 |
| 20120284187 | Hammad et al. | Nov 2012 | A1 |
| 20120290420 | Close | Nov 2012 | A1 |
| 20120290950 | Rapaport et al. | Nov 2012 | A1 |
| 20120303425 | Katzin et al. | Nov 2012 | A1 |
| 20120316945 | Wolf et al. | Dec 2012 | A1 |
| 20120323663 | Leach | Dec 2012 | A1 |
| 20120323765 | Spaulding et al. | Dec 2012 | A1 |
| 20130006848 | Kuttuva | Jan 2013 | A1 |
| 20130024307 | Fuerstenberg et al. | Jan 2013 | A1 |
| 20130054336 | Graylin | Feb 2013 | A1 |
| 20130060679 | Oskolkov et al. | Mar 2013 | A1 |
| 20130066735 | Llach | Mar 2013 | A1 |
| 20130091000 | Hagey et al. | Apr 2013 | A1 |
| 20130124278 | Najm | May 2013 | A1 |
| 20130124287 | Bjorn et al. | May 2013 | A1 |
| 20130132283 | Hayhow et al. | May 2013 | A1 |
| 20130151323 | Shepard et al. | Jun 2013 | A1 |
| 20130151401 | Scipioni et al. | Jun 2013 | A1 |
| 20130173364 | Choong Cheng Shien | Jul 2013 | A1 |
| 20130197991 | Basu et al. | Aug 2013 | A1 |
| 20130246150 | Ovick et al. | Sep 2013 | A1 |
| 20130246273 | Ovick et al. | Sep 2013 | A1 |
| 20130254004 | Cervenka et al. | Sep 2013 | A1 |
| 20130254008 | Ovick et al. | Sep 2013 | A1 |
| 20130268333 | Ovick et al. | Oct 2013 | A1 |
| 20130282461 | Ovick et al. | Oct 2013 | A1 |
| 20130282586 | Ovick et al. | Oct 2013 | A1 |
| 20130325579 | Salmon et al. | Dec 2013 | A1 |
| 20130339167 | Taylor et al. | Dec 2013 | A1 |
| 20130346191 | Morris et al. | Dec 2013 | A1 |
| 20140025459 | Donlan | Jan 2014 | A1 |
| 20140040051 | Ovick et al. | Feb 2014 | A1 |
| 20140040135 | Ovick et al. | Feb 2014 | A1 |
| 20140046744 | Hagey | Feb 2014 | A1 |
| 20140095287 | Whitney | Apr 2014 | A1 |
| 20140129314 | Kim | May 2014 | A1 |
| 20140180826 | Boal | Jun 2014 | A1 |
| 20140214661 | Yankovich et al. | Jul 2014 | A1 |
| 20140222533 | Ovick et al. | Aug 2014 | A1 |
| 20140229260 | Cervenka et al. | Aug 2014 | A1 |
| 20140229319 | Roberts et al. | Aug 2014 | A1 |
| 20140257920 | Gilman et al. | Sep 2014 | A1 |
| 20140310080 | Salmon et al. | Oct 2014 | A1 |
| 20150019314 | Salmon et al. | Jan 2015 | A1 |
| 20150019435 | Ovick et al. | Jan 2015 | A1 |
| 20150106185 | Cervenka et al. | Apr 2015 | A1 |
| 20150134528 | Fineman et al. | May 2015 | A1 |
| 20160148175 | Ovick | May 2016 | A1 |
| 20160358197 | Ovick et al. | Dec 2016 | A1 |
| 20170039560 | Ovick et al. | Feb 2017 | A1 |
| 20170178143 | Ovick et al. | Jun 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 1584894 | Feb 2005 | CN |
| 2003502763 | Jan 2003 | JP |
| 2004303015 | Oct 2004 | JP |
| 20010083521 | Sep 2001 | KR |
| 20010096673 | Nov 2001 | KR |
| 1020020050219 | Jun 2002 | KR |
| 20030080111 | Oct 2003 | KR |
| 1020040016771 | Feb 2004 | KR |
| 20040028110 | Apr 2004 | KR |
| 1020040040253 | May 2004 | KR |
| 1020040077077 | Sep 2004 | KR |
| 1020050061661 | Jun 2005 | KR |
| 20060101241 | Sep 2006 | KR |
| 100717590 | May 2007 | KR |
| 1020070110241 | Nov 2007 | KR |
| 100836484 | Jun 2008 | KR |
| 20080102439 | Nov 2008 | KR |
| PA1013136 | Jun 2004 | MX |
| 2000079461 | Dec 2000 | WO |
| 2001039053 | May 2001 | WO |
| 2000049551 | May 2002 | WO |
| 2006121541 | Nov 2006 | WO |
| 2008016923 | Feb 2008 | WO |
| 2008102935 | Aug 2008 | WO |
| 2009061019 | May 2009 | WO |
| 2010093893 | Aug 2010 | WO |
| 2010135642 | Nov 2010 | WO |
| 2011028486 | Mar 2011 | WO |
| 2013138756 | Sep 2013 | WO |
| 200200475 | Jun 2003 | ZA |
| Entry |
|---|
| ISO8583—A layman's guide to understanding the ISO8583 Financial Transaction Message; http://www.lytsing.org/downloads/iso8583.pdf. |
| https://en.wikipedia.org/wiki/Split_payment (Year: 2012). |
| https://www.chasepaymentech.com/the_basics.html (Year: 2012). |
| Title: Systems and Methods for Facilitating Issuance and Redemption of a Reward, U.S. Appl. No. 13/707,280, filed Dec. 6, 2012, Inventor(s): David Shepard, et al, Status: Non Final Action dated Jun. 3, 2014. |
| Title: Systems and Methods to Provide Discount at Point of Sales Terminals, U.S. Appl. No. 13/648,849, filed Oct. 10, 2012, Inventor(s): Ryan Hagey, et al, Status: Docketed New Case—Ready for Examination, Status Date: Nov. 21, 2012. |
| Title: Systems and Methods to Provide Discount at Point of Sales Terminals, U.S. Appl. No. 13/676,535, filed Nov. 14, 2012, Inventor(s): Joseph Bjorn, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jan. 27, 2013. |
| Title: Systems and Methods to Process Payments Based on Payment Deals, U.S. Appl. No. 13/752,193, filed Jan. 28, 2013, Inventor(s): Gourab Basu, et al, Status: Docketed New Case—Ready for Examination, Status Date: Apr. 14, 2013. |
| Title: Systems and Methods to Apply the Benefit of Offers Via a Transation Handler, U.S. Appl. No. 13/804,435, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jun. 18, 2013. |
| Title: Systems and Methods to Apply the Benefit of Offers Via a Transation Handler, U.S. Appl. No. 13/923,215, filed Jun. 20, 2013, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jul. 18, 2014. |
| Title: Systems and Methods to Generate a Recepit for a Transaction, U.S. Appl. No. 13/804,450, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, Status: Publications—Issue Fee Payment. |
| Title: Systems and Methods to Process Transactions and Offers Via a Gateway, U.S. Appl. No. 13/804,463, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jun. 18, 2013. |
| Title: Systems and Methods to Enhance Security in Transactions, U.S. Appl. No. 13/957,148, filed Aug. 1, 2013, Inventor(s): Joseph Ovick, et al, Status: Non Final Action dated Sep. 23, 2014. |
| Title: Systems and Methods to Digitally Sign Transactions, U.S. Appl. No. 13/958,315, filed Aug. 2, 2013, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Oct. 17, 2013. |
| Title: Systems and Methods to Apply Benefit of Offers, U.S. Appl. No. 13/804,479, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jun. 18, 2013. |
| Title: Systems and Methods to Facilitate the Redemption of Loyalty Currency, U.S. Appl. No. 14/072,583, filed Nov. 5, 2013, Inventor(s): Nancy Kim, Status: Docketed New Case—Ready for Examination, Status Date: Dec. 3, 2013. |
| Title: Payment Processing for Qualified Transaction Items, U.S. Appl. No. 13/915,867, filed Jun. 12, 2013, Inventor(s): Mary Taylor, et al, Status: Non Final Action dated Oct. 21, 2014. |
| Title: Systems and Methods to Process Loyalty Benefits, U.S. Appl. No. 13/897,043, filed May 17, 2013, Inventor(s): Diane Salmon, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jan. 27, 2015. |
| Title: Systems and Methods to Process Loyalty Benefits, U.S. Appl. No. 14/314,629, filed Jun. 25, 2014, Inventor(s): Diane Salmon, et al, Status: Non Final Action dated Oct. 21, 2014. |
| Title: Systems and Methods to Apply Values from Stored Value Accounts to Payment Transactions, U.S. Appl. No. 13/963,665, filed Aug. 9, 2013, Inventor(s): Ryan Hagey, Status: Docketed New Case—Ready for Examination, Status Date: Sep. 25, 2013. |
| Title: Systems and Methods to Facilitate the Redemption of Offer Benefits in a Form of Third Pary Statement Credits, U.S. Appl. No. 14/538,121, filed Nov. 11, 2014, Inventor(s): Daniel Fineman, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jan. 29, 2015. |
| Title: Point of Interaction Loyalty Currency Redemption in a Transaction , U.S. Appl. No. 12/704,445, filed Feb. 11, 2010, Inventor(s): Diane Salmon, et al, Status: Non Final Action dated Oct. 22, 2014. |
| Title: Coupon Bearing Sponsor Account Transaction Authorization, U.S. Appl. No. 14/252,435, filed Apr. 14, 2014, Inventor(s): Karen Cervenka, et al, Status: Notice of Allowance Mailed—Application Received in Office of Publications, Status Date: Oct. 8, 2014. |
| Title: Coupon Bearing Sponsor Account Transaction Authorization, U.S. Appl. No. 14/577,261, filed Dec. 19, 2014, Inventor(s): Karen Cervenka, et al, Docketed New Case—Ready for Examination, Status Date: Jan. 13, 2015. |
| International Patent Application PCT/US12/59607, International Preliminary Report on Patentability, dated Apr. 15, 2014. |
| International Patent Application PCT/US12/68541, International Preliminary Report on Patentability, dated Jun. 10, 2014. |
| International Patent Application PCT/US13/23642, International Preliminary Report on Patentability, dated Aug. 5, 2014. |
| International Patent Application PCT/US2010/024057, International Search Report & Written Opinion, dated Sep. 28, 2010. |
| International Patent Application PCT/US2010/035769, International Search Report and Written Opinion, dated Jan. 12, 2011. |
| International Patent Application PCT/US2010/037646, International Search Report and Written Opinion, dated Jan. 18, 2011. |
| International Patent Application PCT/US2010/046360, International Seach Report and Written Opinion, dated Mar. 30, 2011. |
| International Patent Application PCT/US2012/059607, International Search Report and Written Opinion, dated Mar. 15, 2013. |
| International Patent Application PCT/US2012/068541, International Search Report and Written Opinion, dated Mar. 20, 2013. |
| International Patent Application PCT/US2013/023642 International Search Report and Written Opinion, dated May 30, 2013. |
| International Patent Application PCT/US2013/032307 International Search Report and Written Opinion, dated Jun. 26, 2013. |
| Simon, Jeremy M., Credit card companies promote no-signature Transactions, Published on Oct. 17, 2006. Accessed on Apr. 15, 2016, from http://www.creditcards.com/credit-card-news/popular-credit-card-introduce-no-signature-cards-1273.php. |
| Title: Systems and Methods Using Multiple Communication Channels to Transmit Data in Networks of Separate Computing Systems in Preparation for the Processing of a Subsequent Computing Task in One of the Networks, U.S. Appl. No. 14/950,992, filed Nov. 24, 2015, Inventor(s): Joseph Ovick, Status: Docketed New Case—Ready for Examination, Status Date: Jan. 7, 2016. |
| Title: Systems and Methods for Facilitating Issuance and Redemption of a Reward, U.S. Appl. No. 13/707,280, filed Dec. 6, 2012, Inventor(s): David Shepard, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jan. 28, 2017. |
| Title: Rebate Automation, U.S. Appl. No. 12/781,324, filed May 20, 2010, Inventor(s): Diane Salmon, et al, U.S. Pat. No. 9,031,859, Issue Date: May 12, 2015. |
| Title: Systems and Methods to Provide Discount at Point of Sales Terminals, U.S. Appl. No. 13/648,849, filed Oct. 10, 2012, Inventor(s): Ryan Hagey, et al, Status: Notice of Appeal Filed, Status Date: Apr. 27, 2017. |
| Title: Systems and Methods to Provide Discount at Point of Sales Terminals, U.S. Appl. No. 13/676,535, filed Nov. 14, 2012, Inventor(s): Joseph Bjorn, et al, Status: Final Rejection dated Mar. 13, 2017. |
| Title: Systems and Methods to Process Payments Based on Payment Deals, U.S. Appl. No. 13/752,193, filed Jan. 28, 2013, Inventor(s): Gourab Basu, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jun. 8, 2017. |
| Title: Systems and Methods to Apply the Benefit of Offers Via a Transaction Handler, U.S. Appl. No. 13/804,435, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, U.S. Pat. No. 9,460,436, Issue Date: Oct. 4, 2016. |
| Title: Systems and Methods to Apply the Benefit of Offers Via a Transaction Handler, U.S. Appl. No. 15/243,337, filed Aug. 22, 2016, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Sep. 6, 2016. |
| Title: Systems and Methods to Generate a Receipt for a Transaction, U.S. Appl. No. 13/804,450, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, U.S. Pat. No. 8,880,431, Issue Date: Nov. 4, 2014. |
| Title: Systems and Methods to Generate a Receipt for a Transaction, U.S. Appl. No. 14/,498,774 filed Sep. 26, 2014, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Nov. 8, 2014. |
| Title: Systems and Methods to Process Transactions and Offers Via a Gateway, U.S. Appl. No. 13/804,463, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, U.S. Pat. No. 9,495,690, Issue Date: Nov. 15, 2016. |
| Title: Systems and Methods to Process Transactions and Offers Via a Gateway, U.S. Appl. No. 15/297,757, filed Oct. 19, 2016, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Nov. 1, 2016. |
| Title: Systems and Methods to Enhance Security in Transactions, U.S. Appl. No. 13/957,148, filed Aug. 1, 2013, Inventor(s): Joseph Ovick, et al, U.S. Pat. No. 9,626,678, Issue Date: Apr. 18, 2017. |
| Title: Systems and Methods to Enhance Security in Transactions, U.S. Appl. No. 15/453,401, filed Mar. 8, 2017, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Mar. 17, 2017. |
| Title: Systems and Methods to Digitally Sign Transactions, U.S. Appl. No. 13/958,315, filed Aug. 2, 2013, Inventor(s): Joseph Ovick, et al, Status: Prosecution Suspended, Status Date: Apr. 18, 2017. |
| Title: Systems and Methods to Apply Benefits of Offers, U.S. Appl. No. 13/804,479, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, Status: Non Final Action dated Jan. 18, 2017. |
| Title: Systems and Methods to Facilitate the Redemption of Loyalty Currency, U.S. Appl. No. 14/072,583, filed Nov. 5, 2013, Inventor(s): Nancy Kim, Status: Non Final Action dated Feb. 8, 2017. |
| Title: Payment Processing for Qualified Transaction Items, U.S. Appl. No. 13/915,867, filed Jun. 12, 2013, Inventor(s): Mary Taylor, et al, Status: Docketed New Case—Ready for Examination, Status Date: Dec. 5, 2016. |
| Title: Systems and Methods to Process Loyalty Benefit, U.S. Appl. No. 14/314,629, filed Jun. 25, 2014, Inventor(s): Diane Salmon, et al, Status: Non Final Action dated Feb. 27, 2017. |
| Title: Systems and Methods to Apply Values from Stored Value Accounts to Payment Transactions, U.S. Appl. No. 13/963,665, filed Aug. 9, 2013, Inventor(s): Ryan Hagey, Status: Non Final Action Counted, Not Yet Mailed, Status Date: Apr. 30, 2017. |
| Title: Systems and Methods to Facilitate the Redemption of Offer Benefits in a Form of Third Party Statement Credits, U.S. Appl. No. 14/538,121, filed Nov. 11, 2014, Inventor(s): Daniel Fineman, et al, Status: Non Final Action dated Jan. 25, 2017. |
| Title: Point of Interaction Loyalty Currency Redemption in a Transaction, U.S. Appl. No. 12/704,445, filed Feb. 11, 2010, Inventor(s): Diane Salmon, et al, Status: Awaiting TC Resp, Issue Fee Payment Verified, Status Date: Jun. 22, 2017. |
| Title: Point of Interaction Loyalty Currency Redemption in a Transaction, U.S. Appl. No. 15/632,039, Filed On: Inventor(s): Diane Salmon, et al, Status: Application Undergoing Preexam Processing, Status Date: Jun. 23, 2017. |
| Title: Coupon Bearing Sponsor Account Transaction Authorization, U.S. Appl. No. 14/252,435, filed Apr. 14, 2014, Inventor(s): Karen Cervenka, et al, U.S. Pat. No. 8,965,810, Issue Date: Feb. 24, 2015. |
| Title: Coupon Bearing Sponsor Account Transaction Authorization, U.S. Appl. No. 14/577,261, filed Dec. 19, 2014, Inventor(s): Karen Cervenka, et al, Status: Non Final Action dated May 23, 2106. |
| Title: Systems and Methods of Using Multiple Communication Channels to Transmit Data in Networks of Separate Computing Systems in Preparation for the Processing of a Subsequent Computing Task in One of the Networks, U.S. Appl. No. 14/950,992, filed Nov. 24, 2015, Inventor(s): Joseph Ovick, Status: Docketed New Case—Ready for Examination, Status Date: Jan. 7, 2016. |
| Title: Systems and Methods for Facilitating Issuance and Redemption of a Reward, U.S. Appl. No. 13/707,280, filed Dec. 6, 2012, Inventor(s): David Shepard, et al, Status: Docketed New Case—Ready for Examination, Status Date: Aug. 29, 2015. |
| Title: Rebate Automation, U.S. Appl. No. 12/784,324, filed May 20, 2010, Inventor(s): Diane Salmon, et al, Status: Notice of Allowance Mailed—Application Received in Office of Publications, dated Oct. 14, 2014. |
| Title: Rebate Automation, U.S. Appl. No. 14/505,435, filed Oct. 2, 2014, Inventor(s): Diane Salmon, et al, Status: Docketed New Case—Ready for Examination, Status Date: Oct. 11, 2014. |
| Title: Systems and Methods to Provide Discount at Point of Sales Terminals, U.S. Appl. No. 13/648,849, filed Oct. 10, 2012, Inventor(s): Ryan Hagey, et al, Status: Docketed New Case—Ready for Examination, Status Date: May 8, 2016. |
| Title: Systems and Methods to Provide Discount at Point of Sales Terminals, U.S. Appl. No. 13/676,535, filed Nov. 14, 2012, Inventor(s): Joseph Bjorn, et al, Status: Docketed New Case—Ready for Examination, Status Date: Oct. 8, 2015. |
| Title: Systems and Methods to Process Payments Based on Payment Deals, U.S. Appl. No. 13/752,193, filed Jan. 28, 2013, Inventor(s): Gourab Basu, et al, Status: Docketed New Case—Ready for Examination, Status Date: Mar. 8, 2016. |
| Title: Systems and Methods to Apply the Benefit of Offers Via a Transaction Handler, U.S. Appl. No. 13/804,435, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, Status: Final Rejection dated Jan. 21, 2016. |
| Title: Systems and Methods to Apply the Benefit of Offers Via a Transaction Handler, U.S. Appl. No. 13/923,215, filed Jun. 20, 2013, Inventor(s): Joseph Ovick, et al, Status: Final Rejection dated Jul. 29, 2015. |
| Title: Systems and Methods to Generate a Receipt for a Transaction, U.S. Appl. No. 13/804,435, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, Status: Publications—Issue Fee Payment. |
| Title: Systems and Methods to Process Transactions and Offers Via a Gateway, U.S. Appl. No. 13/804,463, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: May 8, 2016. |
| Title: Systems and Methods to Enhance Security in Transactions, U.S. Appl. No. 13/957,148, filed Aug. 1, 2013, Inventor(s): Joseph Ovick, et al, Status: Non Final Action dated Mar. 22, 2016. |
| Title: Systems and Methods to Digitally Sign Transactions, U.S. Appl. No. 13/958,315, filed Aug. 2, 2013, Inventor(s): Joseph Ovick, et al, Status: Non Final Action dated Apr. 22, 2016. |
| Title: Systems and Methods to Apply Benefits of Offers, U.S. Appl. No. 13/804,479, filed Mar. 14, 2013, Inventor(s): Joseph Ovick, et al, Status: Docketed New Case—Ready for Examination, Status Date: Feb. 12, 2016. |
| Title: Systems and Methods to Facilitate the Redemption of Loyalty Currency, U.S. Appl. No. 14/072,583, filed Nov. 5, 2013, Inventor(s): Nancy Kim, Status: Non Final Action dated Dec. 31, 2015. |
| Title: Payment Processing for Qualified Transaction Items, U.S. Appl. No. 13/915,867, filed Jun. 12, 2013, Inventor(s): Mary Taylor, et al, Status: Docketed New Case—Ready for Examination, Status Date: Aug. 14, 2015. |
| Title: Systems and Methods to Process Loyalty Benefits, U.S. Appl. No. 13/897,043, filed May 17, 2013, Inventor(s): Diane Salmon, et al, Status: Non Final Action dated Apr. 7, 2015. |
| Title: Systems and Methods to Process Loyalty Benefits, U.S. Appl. No. 14/314,629, filed Jun. 25, 2014, Inventor(s): Diane Salmon, et al, Status: Non Final Action dated Jan. 28, 2016. |
| Title: Systems and Methods to Apply Values from Stored Value Accounts to Payment Transactions, U.S. Appl. No. 13/963,665, filed Aug. 9, 2013, Inventor(s): Ryan Hagey, Status: Non Final Action dated Mar. 22, 2016. |
| Title: Systems and Methods to Facilitate the Redemption of Offer Benefits in a Form of Third Party Statement Credits, U.S. Appl. No. 14/538,121, filed Nov. 11, 2014, Inventor(s): Daniel Fineman, et al, Status: Docketed New Case—Ready for Examination, Status Date: Jan. 29, 2015. |
| Title: Point of Interaction Loyalty Currency Redemption in a Transaction, U.S. Appl. No. 12/704,445, filed Feb. 11, 2010, Inventor(s): Diane Salmon, et al, Status: Non Final Action dated Jan. 28, 2016. |
| Title: Coupon Bearing Sponsor Account Transaction Authorization, U.S. Appl. No. 12/860,578, filed Aug. 20, 2010, Inventor(s): Karen Cervenka, et al, U.S. pat. No. 8,463,706, Issue Date: Jun. 11, 2013. |
| Title: Coupon Bearing Sponsor Account Transaction Authorization, U.S. Appl. No. 13/892,910, filed May 13, 2013, Inventor(s): Karen Cervenka, et al, U.S. Pat. No. 8,725,568, Issue Date: May 13, 2014. |
| Title: Coupon Bearing Sponsor Account Transaction Authorization, U.S. Appl. No. 14/252,435, filed Apr. 14, 2014, Inventor(s): Karen Cervenka, et al, Status: Notice of Allowance Mailed—Application Received in Office of Publications, dated Oct. 8, 2014. |
| Title: Coupon Bearing Sponsor Account Transaction Authorization, U.S. Appl. No. 14/577,261, filed Dec. 19, 2014, Inventor(s): Karen Cervenka, et al, Status: Docketed New Case—Ready for Examination, Status Date: May 8, 2016. |
| Number | Date | Country | |
|---|---|---|---|
| 20140129308 A1 | May 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61722603 | Nov 2012 | US |
