Abstract: A system includes a rule engine to determine details of loyalty reward currency redemption from one or more reward accounts as part of the processing of a payment transaction in a payment account of a user. The redemption details are determined based on user preferences and rules of the loyalty programs, and transmitted to the user during the authorization of the payment transaction. During the authorization and/or within a time window after the authorization, but before the settlement of the payment transaction, the user may provide a confirmation message that may accept, reject, or modify the redemption details. A transaction handler is configured to authorize and/or settle the payment transaction, as modified by the redemption details initially computed by the rule engine and subsequently confirmed, rejected or modified by the user via an optional confirmation message.

Abstract: A system includes a rule engine to determine details of loyalty reward currency redemption from one or more reward accounts as part of the processing of a payment transaction in a payment account of a user. The redemption details are determined based on user preferences and rules of the loyalty programs, and transmitted to the user during the authorization of the payment transaction. During the authorization and/or within a time window after the authorization, but before the settlement of the payment transaction, the user may provide a confirmation message that may accept, reject, or modify the redemption details. A transaction handler is configured to authorize and/or settle the payment transaction, as modified by the redemption details initially computed by the rule engine and subsequently confirmed, rejected or modified by the user via an optional confirmation message.

Abstract: A system includes a rule engine to determine details of loyalty reward currency redemption from one or more reward accounts as part of the processing of a payment transaction in a payment account of a user. The redemption details are determined based on user preferences and rules of the loyalty programs, and transmitted to the user during the authorization of the payment transaction. During the authorization and/or within a time window after the authorization, but before the settlement of the payment transaction, the user may provide a confirmation message that may accept, reject, or modify the redemption details. A transaction handler is configured to authorize and/or settle the payment transaction, as modified by the redemption details initially computed by the rule engine and subsequently confirmed, rejected or modified by the user via an optional confirmation message.

Abstract: A system includes a rule engine to determine details of loyalty reward currency redemption from one or more reward accounts as part of the processing of a payment transaction in a payment account of a user. The redemption details are determined based on user preferences and rules of the loyalty programs, and transmitted to the user during the authorization of the payment transaction. During the authorization and/or within a time window after the authorization, but before the settlement of the payment transaction, the user may provide a confirmation message that may accept, reject, or modify the redemption details. A transaction handler is configured to authorize and/or settle the payment transaction, as modified by the redemption details initially computed by the rule engine and subsequently confirmed, rejected or modified by the user via an optional confirmation message.

Abstract: A system includes a rule engine to determine details of loyalty reward currency redemption from one or more reward accounts as part of the processing of a payment transaction in a payment account of a user. The redemption details are determined based on user preferences and rules of the loyalty programs, and transmitted to the user during the authorization of the payment transaction. During the authorization and/or within a time window after the authorization, but before the settlement of the payment transaction, the user may provide a confirmation message that may accept, reject, or modify the redemption details. A transaction handler is configured to authorize and/or settle the payment transaction, as modified by the redemption details initially computed by the rule engine and subsequently confirmed, rejected or modified by the user via an optional confirmation message.

Abstract: A method is used in a system that includes a financial service provider coordinating accounts issued by an issuer to cardholders requesting credit from merchants. Each merchant has an acquirer with whom the financial service provider also coordinates the accounts. The method can be performed by a merchant sending a transmission to its acquirer including a request for a transaction against one account to which the merchant receives a denial or prior to receiving such a denial. The merchant then requests information from the financial service provider who responds by sending the requested information, upon which the merchant determines whether to extend the credit. When the method is performed by a financial service provider, in response to the denial received by one merchant or prior to such denial, the financial service provider receives a transmission from the merchant including a request for information about the account.

Abstract: A system and method configured to use an authorization messaging system for payment processing to communicate, in real time during authorization of a payment transaction, loyalty reward information, such as reward balance and conversion rate between a loyalty currency and a payment currency. For example, loyalty currency conversion rate is provided in real time via the authorization response that also provides the loyalty currency balance that is redeemable for the payment transaction. The system and method allows the conversion rate to be customized and/or personalized based on the identities of the user, the merchant and the loyalty program. Merchant may provide add-on offers for certain users.

Abstract: In one aspect, a computing apparatus includes: a data warehouse to store data associating a plurality of account identifiers with an offer having a predefined purchase requirement and an aggregated purchase requirement for a benefit; and a transaction handler configured to process a plurality of transactions. The transaction handler is further configured to determine whether each of the plurality of transactions satisfies a predefined purchase requirement, identify a set of transactions each satisfying the predefined purchase requirement, and determine whether the set of transactions satisfies an aggregated purchase requirement for the benefit. In one example, the transaction handler is configured to provide the benefit via statement credits when the set of transactions satisfies the aggregated purchase requirement.

Abstract: A computer receives information that a request is made to authorize a transaction for a sale of a product by a merchant to an account holder in a transaction conducted on a consumer account issued to the account holder. When the computer confirms that the transaction is authorized and that the transaction occurs within a predetermined time period for which there is a rebate associated with the product and a corresponding sponsor financially responsible for the rebate, the computer communicates that the rebate is to be debited to an account of the sponsor and either: (i) given as a discount by the merchant at the point of sale to the account holder; or (ii) credited to an account issued to the account holder by the issuer.

Abstract: A system includes a rule engine to determine details of loyalty reward currency redemption from one or more reward accounts as part of the processing of a payment transaction in a payment account of a user. The redemption details are determined based on user preferences and rules of the loyalty programs, and transmitted to the user during the authorization of the payment transaction. During the authorization and/or within a time window after the authorization, but before the settlement of the payment transaction, the user may provide a confirmation message that may accept, reject, or modify the redemption details. A transaction handler is configured to authorize and/or settle the payment transaction, as modified by the redemption details initially computed by the rule engine and subsequently confirmed, rejected or modified by the user via an optional confirmation message.

Abstract: A system including a transaction handler configured to split a transaction, initiated between an acquirer processor representing a merchant and an issuer processor representing a user of a payment account, into separate transactions with the issuer processor and one or more sponsor processors in control of reward accounts of the user for the redemption of loyalty rewards. User preferences and rules of the loyalty programs for the redemption of the loyalty rewards are stored to facilitate the determination of the redemption details in an automated way, such that the user (and/or the merchant) does not have to specify the redemption details. A portal may optionally notify the user of the award/redemption of the benefit of an offer using a communication channel separate from the transaction terminal that initiates and approves the transaction between the account holder and the merchant.

Abstract: A system including a transaction handler configured to split a transaction, initiated between an acquirer processor representing a merchant and an issuer processor representing a user of a payment account, into separate transactions with the issuer processor and one or more sponsor processors in control of reward accounts of the user for the redemption of loyalty rewards. The transaction handler may communicate with the sponsor processors in parallel or in sequence to reserve and release rewards, and may provide a partial authorization for the transaction in response to each authorization for reward redemption from a respective reward account without a subsequent, updated authorization request for the transaction in the payment account of the user.

Abstract: A computing apparatus includes: a data warehouse to store data associating a plurality of account identifiers with an offer having a predefined purchase requirement and an aggregated purchase requirement for a benefit; and a transaction handler configured to process a plurality of transactions. The transaction handler is further configured to determine whether each of the plurality of transactions satisfies a predefined purchase requirement, identify a set of transactions each satisfying the predefined purchase requirement, and determine whether the set of transactions satisfies an aggregated purchase requirement for the benefit. In one example, the transaction handler is configured to provide the benefit via statement credits when the set of transactions satisfies the aggregated purchase requirement.

Abstract: A computer receives information that a request is made to authorize a transaction for a sale of a product by a merchant to an account holder in a transaction conducted on a consumer account issued to the account holder. When the computer confirms that the transaction is authorized and that the transaction occurs within a predetermined time period for which there is a rebate associated with the product and a corresponding sponsor financially responsible for the rebate, the computer communicates that the rebate is to be debited to an account of the sponsor and either: (i) given as a discount by the merchant at the point of sale to the account holder; or (ii) credited to an account issued to the account holder by the issuer.

Abstract: A computing apparatus includes: a transaction handler to process transactions; a portal to receive from users enrollment input identifying account identifiers of the users and respective loyalty programs; and a data warehouse to store data associating the account identifiers with the respective loyalty programs. In response to an authorization request received in the transaction handler for a payment transaction identifying a first account identifier, the computing apparatus is to use the data warehouse to determine whether the first account identifier is enrolled with a loyalty program; and if the first account identifier is enrolled with a first loyalty program, the computing apparatus is to use the transaction handler to request purchase details from the merchant via a response to the authorization request, and determine benefits to be awarded to the user of the first account identifier.

Abstract: A benchmarking tool generates reports for delivery to a merchant illustrating a performance of the merchant as compared to the performance of the merchant's peers. The performance is illustrated through metrics that algorithmically combine data on transactions of consumers with the merchant or its peers, respectively. The metrics may be further subdivided into consumer groups such as new consumers, consumers that have shopped within the merchant in the past, consumers that no longer shop within the merchant, or consumers that use a commercial account to pay for purchases. The reports may be rendered in a graphical display for use by the merchant.

Abstract: Account holder identification is used to access and retrieve the account holder's accounts and attributes thereof. A user interface receives a selected account for which merchants having conducted transactions on the selected account are retrieved and displayed on the user interface. The account holder selects which merchants are to receive updated attributes of the selected account, such as a new expiration, a new billing address, a new credit limit, a name change of the account holder, etc. Each user selected merchant is notified of the user selected attributes of the user selected account.

Abstract: A benchmarking tool accesses a database comprising a plurality of transaction records, each of the records comprising transaction data on a purchase transaction. A first subset of the transaction records is determined that occur within a predetermined time period and are associated with a first merchant. A second subset of the transaction records is determined that occur within the predetermined time period and are associated with a merchant peer group. The first subset of transaction records are processed to determine a first metric for the first merchant. The second subset of transaction records are processed to determine a second metric for the merchant peer group. The first metric is compared to the second metric to indicate performance of the first merchant relative to performance of the merchant peer group.

Abstract: A system, apparatus, computer readable media, and method are disclosed for generating analytics on customers of service provider merchants. In an example, a transaction record associated with an account identifier of a customer that purchased a first service from a first merchant may be processed and a service date for the first service may be determined. Other transaction records comprising the account identifier and that satisfy a temporal filter may be identified. Each of the other transaction records may include transaction data associated with at least one of: (1) purchase of another service to be provided within a first predetermined amount of time of the service date, and (2) purchase of a product within a second predetermined amount of time of the service date. A spending profile including information on the first service, the service date, and the transaction data for each of the other transaction records may be generated.

Abstract: A system, apparatus, computer readable media, and method are disclosed for generating analytics on customers of service provider merchants. In an example, a transaction record associated with an account identifier of a customer that purchased a first service from a first merchant may be processed and a service date for the first service may be determined. Other transaction records comprising the account identifier and that satisfy a temporal filter may be identified. Each of the other transaction records may include transaction data associated with at least one of: (1) purchase of another service to be provided within a first predetermined amount of time of the service date, and (2) purchase of a product within a second predetermined amount of time of the service date. A spending profile including information on the first service, the service date, and the transaction data for each of the other transaction records may be generated.