Abstract: Provided is an emergency management system including at least one processor in communication with an electronic payment processing network, the electronic payment processing network including a transaction processing system, a plurality of merchant systems associated with merchant locations, and a plurality of issuer systems. The at least one processor is programmed or configured to retrieve, from the electronic payment processing network, transaction data associated with a plurality of transactions and determine an operational status of at least one first entity associated with the plurality of transactions based on the difference between a first transaction count and a second transaction count, and in response to determining the operation status of the at least one first entity, automatically communicate a message to at least one second entity based on the operational status of the at least one first entity.

Abstract: A system and method may retrieve transaction data for a plurality of electronic payment system transactions. The transaction data may describe a plurality of electronic payment transactions between a payment network system and a plurality of merchants. The transaction data may include a transaction location and a merchant store number. The system and method may parse the transaction data to identify the transaction location and the merchant store number and analyze the retrieved and parsed transaction data to identify one or more centroids for at least a portion of the retrieved and parsed transaction data. The one or more centroids may correspond to a merchant location for each transaction of the retrieved and parsed transaction data. The system and method may then clean the retrieved and parsed transaction data having a transaction location outside a threshold distance from the one or more centroids to include accurate merchant store number data.

Abstract: Provided is a method for managing source identifiers of clustered records, which may include receiving a plurality of records, each having identification data associated with a source thereof. The records may be sorted into a first plurality of clusters. A first source identifier may be generated for each cluster. Update data associated with an update to the records may be received. At least some of the records may be sorted into a second plurality of clusters. A first cluster of the second plurality of clusters may have first identification data different from at least one cluster of the first plurality of clusters, and a second cluster of the second plurality of clusters may have identification data that substantially matches the at least one cluster. Whether to assign the first source identifier to the first or second cluster may be determined. A system and computer program product are also disclosed.

Abstract: The disclosure relates to test kits and methods for detecting the presence of multiple human papilloma vims polynucleotides in a biological sample.

Abstract: Provided is a method for managing source identifiers of clustered records, which may include receiving a plurality of records, each having identification data associated with a source thereof. The records may be sorted into a first plurality of clusters. A first source identifier may be generated for each cluster. Update data associated with an update to the records may be received. At least some of the records may be sorted into a second plurality of clusters. A first cluster of the second plurality of clusters may have first identification data different from at least one cluster of the first plurality of clusters, and a second cluster of the second plurality of clusters may have identification data that substantially matches the at least one cluster. Whether to assign the first source identifier to the first or second cluster may be determined. A system and computer program product are also disclosed.

Abstract: A system and computer-implemented method distributes rewards and loyalty points in a payment network based on purchase patterns. The system and method may receive purchase data corresponding to a plurality of purchases where the purchase data includes a merchant, a purchase location, and a purchase time. The system and method may then determine a shopping pattern based on the purchase data. The shopping pattern may indicate a probability that a first purchase transaction beginning at a first store will proceed to a second purchase transaction at a second store. The system and method may also receive further purchase data corresponding to a user computer system and compare it to the shopping pattern. The system and method may then send, to the user computer system, one or more of rewards and loyalty points corresponding to the second store when the further purchase data includes the first store.

Abstract: Provided is a method for managing source identifiers of clustered records, which may include receiving a plurality of records, each having identification data associated with a source thereof. The records may be sorted into a first plurality of clusters. A first source identifier may be generated for each cluster. Update data associated with an update to the records may be received. At least some of the records may be sorted into a second plurality of clusters. A first cluster of the second plurality of clusters may have first identification data different from at least one cluster of the first plurality of clusters, and a second cluster of the second plurality of clusters may have identification data that substantially matches the at least one cluster. Whether to assign the first source identifier to the first or second cluster may be determined. A system and computer program product are also disclosed.

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: 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: Provided is an emergency management system including at least one processor in communication with an electronic payment processing network, the electronic payment processing network including a transaction processing system, a plurality of merchant systems associated with merchant locations, and a plurality of issuer systems. The at least one processor is programmed or configured to retrieve, from the electronic payment processing network, transaction data associated with a plurality of transactions and determine an operational status of at least one first entity associated with the plurality of transactions based on the difference between a first transaction count and a second transaction count, and in response to determining the operation status of the at least one first entity, automatically communicate a message to at least one second entity based on the operational status of the at least one first entity.

Abstract: Provided is a system for determining a status of at least one merchant during or after an emergency event including at least one processor to retrieve historical transaction data for at least one merchant associated with a merchant category code (MCC), determine a first transaction count for the at least one merchant based on the historical transaction data for the at least one merchant, retrieve current transaction data for the at least one merchant, determine a second transaction count for the at least one merchant based on the current transaction data for the at least one merchant, classify the at least one merchant based at least partially on a comparison between the first transaction count and the second transaction count, and display a classification of the at least one merchant based on classifying the at least one merchant. A method and computer program product are also disclosed.

Abstract: A system and method may retrieve transaction data for a plurality of electronic payment system transactions. The transaction data may describe a plurality of electronic payment transactions between a payment network system and a plurality of merchants. The transaction data may include a transaction location and a merchant store number. The system and method may parse the transaction data to identify the transaction location and the merchant store number and analyze the retrieved and parsed transaction data to identify one or more centroids for at least a portion of the retrieved and parsed transaction data. The one or more centroids may correspond to a merchant location for each transaction of the retrieved and parsed transaction data. The system and method may then clean the retrieved and parsed transaction data having a transaction location outside a threshold distance from the one or more centroids to include accurate merchant store number data.

Abstract: In one embodiment, the location or zip code of purchasers in a card present electronic transaction may be reviewed and compared to the reported location or zip code of a merchant. If the difference or variance from the customer zip code or location to the customer location or zip code is over a threshold, the merchant is indicating as requiring additional attention.

Abstract: Provided is a method for managing source identifiers of clustered records, which may include receiving a plurality of records, each having identification data associated with a source thereof. The records may be sorted into a first plurality of clusters. A first source identifier may be generated for each cluster. Update data associated with an update to the records may be received. At least some of the records may be sorted into a second plurality of clusters. A first cluster of the second plurality of clusters may have first identification data different from at least one cluster of the first plurality of clusters, and a second cluster of the second plurality of clusters may have identification data that substantially matches the at least one cluster. Whether to assign the first source identifier to the first or second cluster may be determined. A system and computer program product are also disclosed.

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 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: Provided is a system for determining a status of at least one merchant during or after an emergency event including at least one processor to retrieve historical transaction data for at least one merchant associated with a merchant category code (MCC), determine a first transaction count for the at least one merchant based on the historical transaction data for the at least one merchant, retrieve current transaction data for the at least one merchant, determine a second transaction count for the at least one merchant based on the current transaction data for the at least one merchant, classify the at least one merchant based at least partially on a comparison between the first transaction count and the second transaction count, and display a classification of the at least one merchant based on classifying the at least one merchant. A method and computer program product are also disclosed.

Abstract: In one embodiment, the location or zip code of purchasers in a card present electronic transaction may be reviewed and compared to the reported location or zip code of a merchant. If the difference or variance from the customer zip code or location to the customer location or zip code is over a threshold, the merchant is indicating as requiring additional attention.

Abstract: A valve is provided including a first valve member and a second valve member. The first valve member includes a first step and a first orifice adjacent the first step. The second valve member includes a second step and a second orifice adjacent the second step. The second valve member is movable relative to the first valve member between an open position, in which the first orifice is fluidly connected the second orifice, and a closed position, in which the first orifice is substantially fluidly disconnected from the second orifice. The first and second steps are fluidly connected to the second orifice and substantially fluidly disconnected from the first orifice when the second valve member is in the closed position, and the first and second steps are fluidly connected to the first and second orifices when the second valve member is in the open position.

Abstract: A valve is provided including a first valve member and a second valve member. The first valve member includes a first step and a first orifice adjacent the first step. The second valve member includes a second step and a second orifice adjacent the second step. The second valve member is movable relative to the first valve member between an open position, in which the first orifice is fluidly connected the second orifice, and a closed position, in which the first orifice is substantially fluidly disconnected from the second orifice. The first and second steps are fluidly connected to the second orifice and substantially fluidly disconnected from the first orifice when the second valve member is in the closed position, and the first and second steps are fluidly connected to the first and second orifices when the second valve member is in the open position.