Abstract: A method for inferring a merchant geolocation includes: storing a plurality of transaction data entries, each including an account identifier, merchant identifier, and transaction time; storing a plurality of merchant profiles, each including a merchant identifier and geolocation; identifying a first set of transaction data entries, each entry including a common merchant identifier; identifying a second set of transaction data entries, each entry including a different merchant identifier corresponding to a merchant within a predetermined distance of a merchant corresponding to the common merchant identifier; transmitting an identification value associated with each transaction data entry in the first and second sets; receiving geolocation data entries for each identification value, each entry including a location time and geolocation; and identifying an updated merchant geolocation for the merchant corresponding to the common merchant identifier based on the geolocation included in geolocation entries that ma

Abstract: A network operator intermediates a cashless transaction by sending a payment device issuer an outbound clearing data file enriched with cleansed merchant data. Issuers that choose to participate in the merchant data cleansing service are provided with the cleansed, and optionally augmented, merchant information. Before providing the cleansed and/or augmented merchant information, a determination is made of whether a “do not recognize” call is likely, based upon a determination by a computing device of whether or not the merchant is on a “watch-list” of merchants. The “watch-list” is previously generated based upon one or several factors, including whether or not a minimum number or percentage of previous transactions have resulted in charge-backs, whether DNR transactions associated with the merchant were previously reported, or if an acquirer, issuer, or third-party payment provider recommends the merchant for inclusion.