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 will be provided with the cleansed, and optionally augmented, merchant information. Providing this data to the issuer could be used to help reduce costs associated with “do not recognize” calls by cardholders, disputed charges, and charge-backs. With cleansed data provided in the clearing record, a device holder would be given access to this cleansed information about the merchant where a transaction took place through their statement. The present disclosure also provides for augmenting the clearing record data to include merchant-specific add-on and/or aggregate data not presently included in the transaction clearing record, yet useful to the issuer both in form and content.

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 will be provided with the cleansed, and optionally augmented, merchant information. Providing this data to the issuer could be used to help reduce costs associated with “do not recognize” calls by cardholders, disputed charges, and charge-backs. With cleansed data provided in the clearing record, a device holder would be given access to this cleansed information about the merchant where a transaction took place through their statement. The present disclosure also provides for augmenting the clearing record data to include merchant-specific add-on and/or aggregate data not presently included in the transaction clearing record, yet useful to the issuer both in form and content.

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 will be provided with the cleansed, and optionally augmented, merchant information. Providing this data to the issuer could be used to help reduce costs associated with “do not recognize” calls by cardholders, disputed charges, and charge-backs. With cleansed data provided in the clearing record, a device holder would be given access to this cleansed information about the merchant where a transaction took place through their statement. The present disclosure also provides for augmenting the clearing record data to include merchant-specific add-on and/or aggregate data not presently included in the transaction clearing record, yet useful to the issuer both in form and content.

Abstract: Determining whether two merchant location database entries are describing the same merchant location. A subject merchant location database entry and comparison candidate merchant location database entries include a DBA name field, a street address field, and one or more additional descriptive fields descriptive of one or more predetermined characteristics of the respective merchant location. The subject merchant location database entry is compared to a set populated with candidate merchant location database entries, candidates having a predetermined minimum textural similarity with the subject merchant location database entry on the basis of each entry's DBA name field or street address field.

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.

Abstract: Determining whether two merchant location database entries are describing the same merchant location. A subject merchant location database entry and comparison candidate merchant location database entries include a DBA name field, a street address field, and one or more additional descriptive fields descriptive of one or more predetermined characteristics of the respective merchant location. The subject merchant location database entry is compared to a set populated with candidate merchant location database entries, candidates having a predetermined minimum textural similarity with the subject merchant location database entry on the basis of each entry's DBA name field or street address field.

Abstract: A solution to resolve ambiguous merchant data in connection with processing a cashless transaction request in a real-time manner. Provided according to the present disclosure are a system and method including a binary-searchable non-transitory computer-readable medium is configure to store a first set of unambiguous merchant identification data having plural data entries therein, each entry corresponding to a merchant. A binary search of the first set of unambiguous merchant identification data is carried out using search keys based upon the ambiguous merchant identification data to determine whether one or more entries of the first set satisfies at least one of a second set of partial match criteria for comparing the ambiguous merchant identification data with the first set of unambiguous merchant identification data.

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 will be provided with the cleansed, and optionally augmented, merchant information. Providing this data to the issuer could be used to help reduce costs associated with “do not recognize” calls by cardholders, disputed charges, and charge-backs. With cleansed data provided in the clearing record, a device holder would be given access to this cleansed information about the merchant where a transaction took place through their statement. The present disclosure also provides for augmenting the clearing record data to include merchant-specific add-on and/or aggregate data not presently included in the transaction clearing record, yet useful to the issuer both in form and content.

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 will be provided with the cleansed, and optionally augmented, merchant information. Providing this data to the issuer could be used to help reduce costs associated with “do not recognize” calls by cardholders, disputed charges, and charge-backs. With cleansed data provided in the clearing record, a device holder would be given access to this cleansed information about the merchant where a transaction took place through their statement. The present disclosure also provides for augmenting the clearing record data to include merchant-specific add-on and/or aggregate data not presently included in the transaction clearing record, yet useful to the issuer both in form and content.

Abstract: A method and system for processing raw address data using a computer device coupled to a database are provided. The method includes receiving, at the computer device, raw data from a first party, the raw data including a raw street address. The method includes formatting the raw street address using the computer device and separating the formatted street address into at least one token using the computer device wherein each token includes one or more characters indicating a portion of the raw street address. The method further includes creating a standardized street address from the at least one token based on one or more conditions, wherein the one or more conditions facilitate determining at least one of inclusion, exclusion, and position of the at least one token in the standardized street address.

Abstract: A solution to resolve ambiguous merchant data in connection with processing a cashless transaction request in a real-time manner. Provided according to the present disclosure are a system and method including a binary-searchable non-transitory computer-readable medium is configure to store a first set of unambiguous merchant identification data having plural data entries therein, each entry corresponding to a merchant. A binary search of the first set of unambiguous merchant identification data is carried out using search keys based upon the ambiguous merchant identification data to determine whether one or more entries of the first set satisfies at least one of a second set of partial match criteria for comparing the ambiguous merchant identification data with the first set of unambiguous merchant identification data.

Abstract: A solution to disambiguate ambiguous merchant data in connection with processing a cashless transaction request in a real-time manner. Provided according to the present disclosure are a system and method including a binary-searchable non-transitory computer-readable medium is configure to store a first set of unambiguous merchant identification data having plural data entries therein, each entry corresponding to a merchant. A binary search of the first set of unambiguous merchant identification data is carried out using search keys based upon the ambiguous merchant identification data to determine whether one or more entries of the first set satisfies at least one of a hierarchical second set of partial match criteria for comparing the ambiguous merchant identification data with the first set of unambiguous merchant identification data.

Abstract: A solution to disambiguate ambiguous merchant data in connection with processing a cashless transaction request in a real-time manner. Provided according to the present disclosure are a system and method including a binary-searchable non-transitory computer-readable medium is configure to store a first set of unambiguous merchant identification data having plural data entries therein, each entry corresponding to a merchant. A binary search of the first set of unambiguous merchant identification data is carried out using search keys based upon the ambiguous merchant identification data to determine whether one or more entries of the first set satisfies at least one of a hierarchical second set of partial match criteria for comparing the ambiguous merchant identification data with the first set of unambiguous merchant identification data.

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 will be provided with the cleansed, and optionally augmented, merchant information. Providing this data to the issuer could be used to help reduce costs associated with “do not recognize” calls by cardholders, disputed charges, and charge-backs. With cleansed data provided in the clearing record, a device holder would be given access to this cleansed information about the merchant where a transaction took place through their statement. The present disclosure also provides for augmenting the clearing record data to include merchant-specific add-on and/or aggregate data not presently included in the transaction clearing record, yet useful to the issuer both in form and content.

Abstract: A method and system for processing raw address data using a computer device coupled to a database are provided. The method includes receiving, at the computer device, raw data from a first party, the raw data including a raw street address. The method includes formatting the raw street address using the computer device and separating the formatted street address into at least one token using the computer device wherein each token includes one or more characters indicating a portion of the raw street address. The method further includes creating a standardized street address from the at least one token based on one or more conditions, wherein the one or more conditions facilitate determining at least one of inclusion, exclusion, and position of the at least one token in the standardized street address.

Abstract: An object oriented representation for sending network protocol requests between a first and a second process in a computer network. In an object oriented implementation of a protocol stack a network definition object is used for defining an interface to a communication endpoint for a client application and a network address object for defining the communication endpoint. The protocol stack is formed by layers of instances of a protocol interface class object for defining protocol interface for a protocol layer in the protocol stack and a protocol layer class object for defining the protocol layers in the stack. The network protocol requests are sent in an instance of one of a set of network operation classes each of which correspond to a method in the protocol interface class. The client requests are wrapped in the network operation object which contains all the necessary information so the request can be presented to the appropriate protocol layer object in the protocol stack.

Abstract: An object oriented protocol interface for establishing a communication path between communication endpoints in a computer network. The generic nature of the interface allows any and several protocol layers to be developed from the same set of protocol class objects. The interface to a communication endpoint for a client application is defined by instantiating a network definition object for the communication endpoint from a network definition class object. The communication endpoint itself is represented by instantiating a network address object from a network address class object. The protocol layers which form the protocol stack are derived from a set of protocol interface objects from a protocol interface class object and a set of protocol layer objects from a protocol layer class object. The objects forming each of the layers in the protocol stack differ in their capabilities according to their respective layer and the protocol which is provided by the protocol stack.