Abstract: Embodiments include apparatuses, methods, and systems for managing a data warehouse associated with an electronic payment transaction processing network. A first set of stores are active and a second set of stores are inactive in an offer program related to merchandise of a merchant. A first set of transaction records for a first set of transactions from the first set of stores and a second set of transaction records for a second set of transactions from the second set of stores are obtained. A first set of operations on the data warehouse for the first set of transaction records and a second set of operations on the data warehouse for the second set of transaction records may be performed. The second set of operations, different from the first set of operations, includes an update operation on the data warehouse. Other embodiments may also be described and claimed.

Abstract: Embodiments include apparatuses, methods, and systems for managing a data warehouse associated with an electronic payment transaction processing network. A first set of stores are active and a second set of stores are inactive in an offer program related to merchandise of a merchant. A first set of transaction records for a first set of transactions from the first set of stores and a second set of transaction records for a second set of transactions from the second set of stores are obtained. A first set of operations on the data warehouse for the first set of transaction records and a second set of operations on the data warehouse for the second set of transaction records may be performed. The second set of operations, different from the first set of operations, includes an update operation on the data warehouse. Other embodiments may also be described and claimed.

Abstract: Embodiments include apparatuses, methods, and systems for managing a data warehouse associated with an electronic payment transaction processing network. A first set of stores are active and a second set of stores are inactive in an offer program related to merchandise of a merchant. A first set of transaction records for a first set of transactions from the first set of stores and a second set of transaction records for a second set of transactions from the second set of stores are obtained. A first set of operations on the data warehouse for the first set of transaction records and a second set of operations on the data warehouse for the second set of transaction records may be performed. The second set of operations, different from the first set of operations, includes an update operation on the data warehouse. Other embodiments may also be described and claimed.

Abstract: A system for identifying and associating merchant attributes data of a merchant with transaction data may be integrated with existing payment processing systems to provide for detailed merchant attributes data (e.g., merchant name, merchant ownership data, and merchant address data). The system may receive and modify merchant attributes data retrieved from an external source (e.g., an acquirer computer or third party to a transaction) and store the merchant attributes data in a database. The merchant attributes data may be retrieved and correlated with transaction data and provided to entities (e.g., issuer computers) involved with the transaction for authorization decisioning, fraud analysis, and data analytics.

Abstract: Embodiments include apparatuses, methods, and systems for managing a data warehouse associated with an electronic payment transaction processing network. A first set of stores are active and a second set of stores are inactive in an offer program related to merchandise of a merchant. A first set of transaction records for a first set of transactions from the first set of stores and a second set of transaction records for a second set of transactions from the second set of stores are obtained. A first set of operations on the data warehouse for the first set of transaction records and a second set of operations on the data warehouse for the second set of transaction records may be performed. The second set of operations, different from the first set of operations, includes an update operation on the data warehouse. Other embodiments may also be described and claimed.

Abstract: Payment instruments used on behalf of a sponsor may be restricted from use at certain locations. The sponsor may indicate that use of the payment instrument at either specific merchants or certain categories of merchants is not in accordance with the sponsor's goals or values. A system evaluates every transaction request to determine if the personal account number of the payment instrument is associated with the sponsor. If so, the transaction may be further screened to determine if the transaction is from a location to be blocked, in which case a flag may be added to the transaction indicating it is from blocked location. An issuer of the payment instrument may then determine whether to approve or deny the transaction. A tool may generate a dataset of locations and/or merchant categories for use in identifying blocked locations.

Abstract: A system and method to detect changes in transaction parameters for the identification of a store of the merchant in a payment processing network. The system is configured to monitor input data, such as acquirer's merchant master file (AMMF), transaction records, to detect transaction parameters of a processing entity that partially match with the transaction parameters associated with an external, persistent identifier of the merchant and/or the store of the merchant, determine a change or difference introduced in the detect transaction parameters, and update the set of transaction parameters associated with the persistent identifier of the store of the merchant that can be used to identify the set of transaction parameters of the store in a communication external to the communication system of the payment processing network.

Abstract: A system for identifying and associating merchant attributes data of a merchant with transaction data may be integrated with existing payment processing systems to provide for detailed merchant attributes data (e.g., merchant name, merchant ownership data, and merchant address data). The system may receive and modify merchant attributes data retrieved from an external source (e.g., an acquirer computer or third party to a transaction) and store the merchant attributes data in a database. The merchant attributes data may be retrieved and correlated with transaction data and provided to entities (e.g., issuer computers) involved with the transaction for authorization decisioning, fraud analysis, and data analytics.

Abstract: A system and method to detect changes in transaction parameters for the identification of a store of the merchant in a payment processing network. The system is configured to monitor input data, such as acquirer's merchant master file (AMMF), transaction records, to detect transaction parameters of a processing entity that partially match with the transaction parameters associated with an external, persistent identifier of the merchant and/or the store of the merchant, determine a change or difference introduced in the detect transaction parameters, and update the set of transaction parameters associated with the persistent identifier of the store of the merchant that can be used to identify the set of transaction parameters of the store in a communication external to the communication system of the payment processing network.

Abstract: A system for identifying and associating merchant attributes data of a merchant with transaction data may be integrated with existing payment processing systems to provide for detailed merchant attributes data (e.g., merchant name, merchant ownership data, and merchant address data). The system may receive and modify merchant attributes data retrieved from an external source (e.g., an acquirer computer or third party to a transaction) and store the merchant attributes data in a database. The merchant attributes data may be retrieved and correlated with transaction data and provided to entities (e.g., issuer computers) involved with the transaction for authorization decisioning, fraud analysis, and data analytics.

Abstract: A system and method to detect changes in transaction parameters for the identification of a store of the merchant in a payment processing network. The system is configured to monitor input data, such as acquirer's merchant master file (AMMF), transaction records, to detect transaction parameters of a processing entity that partially match with the transaction parameters associated with an external, persistent identifier of the merchant and/or the store of the merchant, determine a change or difference introduced in the detect transaction parameters, and update the set of transaction parameters associated with the persistent identifier of the store of the merchant that can be used to identify the set of transaction parameters of the store in a communication external to the communication system of the payment processing network.

Abstract: A user interface to register merchants. The user interface is configured to allow a merchant to search and identify a set of transaction parameters that are used in authorization and/or settlement messages of payment transactions initiated for a store of the merchant and allow the merchant to obtain a store identifier representing the set of transaction parameters. The store identifier, for example, can be used to label offers of the store of the merchant. Thus, whether or not an authorization or settlement message transmitted in the payment processing network for a payment transaction is for the store can be determined based on whether or not the transaction parameters in the message match with the set of transaction parameters represented by the store identifier.

Abstract: A system and method to detect changes in transaction parameters for the identification of a store of the merchant in a payment processing network. The system is configured to monitor input data, such as acquirer's merchant master file (AMMF), transaction records, to detect transaction parameters of a processing entity that partially match with the transaction parameters associated with an external, persistent identifier of the merchant and/or the store of the merchant, determine a change or difference introduced in the detect transaction parameters, and update the set of transaction parameters associated with the persistent identifier of the store of the merchant that can be used to identify the set of transaction parameters of the store in a communication external to the communication system of the payment processing network.

Abstract: A user interface to register merchants. The user interface is configured to allow a merchant to search and identify a set of transaction parameters that are used in authorization and/or settlement messages of payment transactions initiated for a store of the merchant and allow the merchant to obtain a store identifier representing the set of transaction parameters. The store identifier, for example, can be used to label offers of the store of the merchant. Thus, whether or not an authorization or settlement message transmitted in the payment processing network for a payment transaction is for the store can be determined based on whether or not the transaction parameters in the message match with the set of transaction parameters represented by the store identifier.