METHODS AND SYSTEMS FOR MANAGING MERCHANT IDENTIFIERS

• US 20090228365A1
• Filed: 03/03/2009
• Published: 09/10/2009
• Est. Priority Date: 03/04/2008
• Status: Active Grant

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: Smith, Janet, Wong, Shoon Ping, Tomchek, Brad Michael
• Granted Patent: US 8,191,766 B2
• Time in Patent Office: Days
• US Class Current: 705/21
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/24 Credit schemes, i.e. "pay after"
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/00 Commerce
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

A method and system for processing a merchant identification request from a private label payment card issuer is provided. The issuer is communicatively coupled to a multi-party payment card interchange that includes access to a database. The database stores a plurality of historical multi-party payment card transactions. The method includes transmitting a list of private label merchant locations from the issuer to the interchange wherein the list includes physical location information relating to the private label merchants listed, processing the list at the interchange by applying thereto an identification analysis including one of merchant matching only, test transaction only, and merchant matching plus test transaction, identifying at least one private label merchant location included within the list including associating a unique identifier with the at least one identified private label merchant location, and outputting the at least one identified private label merchant location with the associated unique identifier.

Claims

1. A method of processing a merchant identification request from a private label payment card issuer, the private label payment card issuer communicatively coupled to a multi-party payment card interchange that includes access to a data warehouse and a merchant matching tool, the data warehouse for storing a plurality of historical multi-party payment card transactions, said method comprising:

transmitting a list of private label merchant locations from the private label payment card issuer to the multi-party payment card interchange, the list including physical location information relating to the private label merchants listed;

processing the private label merchant list at the merchant matching tool, the merchant matching tool configured to apply an identification analysis including one of merchant matching only, test transaction only, and merchant matching plus test transaction;

identifying at least one private label merchant location included within the private label merchant list including associating a unique identifier with the at least one identified private label merchant location; and

outputting the at least one identified private label merchant location with the associated unique identifier.

2. A method in accordance with claim 1 wherein processing the private label merchant list further comprises applying the merchant matching only analysis to the private label merchant list, wherein the merchant matching only analysis includes:

retrieving records of historical multi-party payment card transactions from the data warehouse, the records including physical location information for a merchant initiating each of the transactions and a unique identifier associated with the merchant;

substantially matching physical location information of the private label merchants included in the list with physical location information from the records of historical multi-party payment card transactions;

associating the unique identifier associated with the records of historical multi-party payment card transactions with a matching private label merchant location in the list; and

outputting the matching private label merchant locations and the unique identifier associated with each of the matched locations.

3. A method in accordance with claim 2 wherein matching physical location information of the private label merchants in the list with physical location information from the records of historical multi-party payment card transactions further comprises:

parsing the physical location information of the private label merchants in the list;

parsing the physical location information from the records of historical multi-party payment card transactions; and

intelligently matching corresponding fields in the respective information.

4. A method in accordance with claim 2 wherein matching physical location information of the private label merchants in the list with physical location information from the records of historical multi-party payment card transactions further comprises:

designating a match threshold;

calculating a match score for each private label merchant included in the list, the match score representing a confidence level in the corresponding match; and

flagging private label merchants in the list having physical location information that matches the physical location information from the records of historical multi-party payment card transactions with a match score that is greater than the designated match threshold.

5. A method in accordance with claim 1 wherein processing the private label merchant list further comprises applying the test transaction only analysis to the private label merchant list, wherein the test transaction only analysis includes:

creating a test transaction data report including test transaction data;

notifying a selected merchant to process test transaction data at a point of sale (POS) device, the selected merchant included within the list of private label merchants;

receiving an authorization request at the interchange from the POS device, the authorization request resulting from the processing of the test transaction data at the POS device, the authorization request including a unique identifier associated with the selected merchant;

identifying the selected merchant based on the received authorization request; and

outputting a location and the unique identifier of the selected merchant.

6. A method in accordance with claim 5 wherein creating a test transaction data report further comprises:

determining each private label merchant included on the private label merchant list designated for identification using the test transaction only analysis; and

generating test transaction data for each private label merchant designated for identification using the test transaction only analysis, the test transaction data including a test transaction card number, an expiration date, and a test transaction amount.

7. A method in accordance with claim 5 wherein receiving an authorization request further comprises:

processing test transaction data at the POS device of the selected merchant, the test transaction data including a test transaction card number, an expiration date, and a test transaction amount;

receiving the authorization request at the interchange from the POS device, the authorization request including the test transaction data and a unique identifier associated with the selected merchant;

detecting the test transaction data at the interchange;

capturing the unique identifier at the interchange; and

transmitting a void transaction message to the POS device in response to the authorization request.

8. A method in accordance with claim 5 wherein outputting a location and the unique identifier further comprises:

automatically transmitting an electronic message from the interchange to the private label payment card issuer each time a test transaction is processed and a selected merchant is identified.

9. A method in accordance with claim 1 wherein processing the private label merchant list further comprises applying a merchant matching plus test transaction analysis to the private label merchant list, wherein the merchant matching plus test transaction analysis includes:

applying a merchant matching analysis to the private label merchant list to identify a location for at least one of the private label merchants; and

applying a test transaction analysis to the private label merchants included on the private label merchant list not identified by the merchant matching analysis.

10. A method in accordance with claim 9 wherein applying a merchant matching analysis further comprises:

retrieving records of historical multi-party payment card transactions from the data warehouse, the records including physical location information for a merchant initiating each of the transactions and a unique identifier associated with the merchant;

substantially matching physical location information of the private label merchants included in the list with physical location information from the records of historical multi-party payment card transactions;

associating the unique identifier associated with the records of historical multi-party payment card transactions with a matching private label merchant location in the list; and

outputting the matching private label merchant locations and the unique identifier associated with each of the matched locations.

11. A method in accordance with claim 9 wherein applying a test transaction analysis further comprises:

creating a test transaction data report including test transaction data;

notifying a selected merchant to process test transaction data at a point of sale (POS) device, the selected merchant included within the list of private label merchants;

receiving an authorization request at the interchange from the POS device, the authorization request resulting from the processing of the test transaction data at the POS device, the authorization request including a unique identifier associated with the selected merchant; and

identifying the selected merchant based on the received authorization request; and

outputting a location and the unique identifier of the selected merchant.

12. A method in accordance with claim 1 further comprising outputting the private label merchant locations that did not match any physical location information from the records of historical multi-party payment card transactions.

13. A method in accordance with claim 1 wherein outputting the at least one identified private label merchant location further comprises:

transmitting the at least one identified private label merchant location with the unique identifier to the private label payment card issuer, the private label payment card issuer being in a private label payment card relationship with the identified private label merchant;

processing at the interchange a private label transaction that is initiated at the at least one identified private label merchant location; and

transmitting data associated with the private label transaction from the interchange to the private label payment card issuer for further processing.

14. A method in accordance with claim 1 wherein outputting the at least one identified private label merchant location further comprises outputting at least one report including an issuer report, an unmatched report, and a transaction data report.

15. A network-based system for processing a merchant identification request from a private label payment card issuer, said system comprising:

a point of sale (POS) device;

a computer system associated with the private label payment card issuer;

a database for storing a plurality of historical multi-party payment card transactions; and

a server system comprising a merchant matching tool (MMT) and configured to be coupled to said POS device, said computer system, and said database, said server system associated with a multi-party payment card interchange, said server system configured to;

receive a list of private label merchant locations from the issuer computer system, the list including physical location information relating to the private label merchants listed;

process the private label merchant list by applying an identification analysis thereto including one of a merchant matching only analysis, a test transaction only analysis, and merchant matching plus test transaction analysis;

identify at least one private label merchant location included within the private label merchant list including associating a unique identifier with the at least one identified private label merchant location; and

output the at least one identified private label merchant location with the associated unique identifier.

16. A system in accordance with claim 15 wherein, when applying the merchant matching only analysis to the private label merchant list, said server is further configured to:

retrieve records of historical multi-party payment card transactions from the database, the records including physical location information for a merchant initiating each of the transactions and a unique identifier associated with the merchant;

substantially match physical location information of the private label merchants included in the list with physical location information from the records of historical multi-party payment card transactions;

associate the unique identifier associated with the records of historical multi-party payment card transactions with a matching private label merchant location in the list; and

output the matching private label merchant locations and the unique identifier associated with each of the matched locations.

17. A system in accordance with claim 16 wherein, when applying the merchant matching only analysis to the private label merchant list, said server system is further configured to:

parse the physical location information of the private label merchants included in the list;

parse the physical location information from the records of historical multi-party payment card transactions; and

intelligently match corresponding fields in the respective information.

18. A system in accordance with claim 16 wherein, when applying the merchant matching only analysis to the private label merchant list, said server system is further configured to:

designate a match threshold;

calculate a match score for each private label merchant included in the list, the match score representing a confidence level in the corresponding match; and

flag private label merchants in the list having physical location information that matches the physical location information from the records of historical multi-party payment card transactions with a match score that is greater than the designated match threshold.

19. A system in accordance with claim 15 wherein, when applying the test transaction only analysis to the private label merchant list, said server system is further configured to:

select a merchant from the private label merchant list that is designated for test transaction only analysis, the selected merchant associated with the POS device;

create test transaction data for the selected merchant;

receive an authorization request from the POS device, the authorization request resulting from the processing of the test transaction data at the POS device, the authorization request including a unique identifier associated with the selected merchant;

identify the selected merchant based on the received authorization request; and

output a location and the unique identifier of the selected merchant.

20. A system in accordance with claim 19 wherein said server system is further configured to:

determine each private label merchant included on the private label merchant list designated for identification using the test transaction only analysis; and

generate test transaction data for each private label merchant designated for identification using the test transaction only analysis, the test transaction data including a test transaction card number, an expiration date, and a test transaction amount.

21. A system in accordance with claim 19 wherein said server system is further configured to:

receive the authorization request from the POS device, the authorization request resulting from the POS device processing test transaction data of a selected merchant, the test transaction data including a test transaction card number, an expiration date, and a test transaction amount;

detect the test transaction data;

capture the unique identifier; and

transmit a void transaction message to the POS device in response to the authorization request.

22. A system in accordance with claim 19 wherein said server system is further configured to automatically transmit an electronic message to the issuer computer system each time a test transaction is processed and a selected merchant is identified.

23. A system in accordance with claim 15 wherein said server system is further configured to:

apply a merchant matching analysis to the private label merchant list to identify a location for at least one of the private label merchants; and

apply a test transaction analysis to the private label merchants included on the private label merchant list not identified by the merchant matching analysis.

24. A system in accordance with claim 23 wherein said server system is further configured to:

retrieve records of historical multi-party payment card transactions from the database, the records including physical location information for a merchant initiating each of the transactions and a unique identifier associated with the merchant;

substantially match physical location information of the private label merchants included in the list with physical location information from the records of historical multi-party payment card transactions;

associate the unique identifier associated with the records of historical multi-party payment card transactions with a matching private label merchant location in the list; and

output the matching private label merchant locations and the unique identifier associated with each of the matched locations.

25. A system in accordance with claim 23 wherein said server system is further configured to:

select a merchant from the private label merchant list that is designated for test transaction analysis, the selected merchant associated with the POS device;

create test transaction data for the selected merchant;

receive an authorization request from the POS device, the authorization request resulting from the processing of the test transaction data at the POS device, the authorization request including a unique identifier associated with the selected merchant;

identify the selected merchant based on the received authorization request; and

output a location and the unique identifier of the selected merchant.

26. A system in accordance with claim 15 wherein said server system is further configured to output the private label merchant locations that did not match any physical location information from the records of historical multi-party payment card transactions.

27. A system in accordance with claim 15 wherein said server system is further configured to:

transmit the at least one identified private label merchant location with the unique identifier to said issuer computer system, the private label payment card issuer being in a private label payment card relationship with the identified private label merchant;

process a private label transaction that is initiated at the at least one identified private label merchant location; and

transmit data associated with the private label transaction to the issuer computer system for further processing.

28. A system in accordance with claim 15 wherein said server system is further configured to output at least one report including an issuer report, an unmatched report, and a transaction data report.

29. A computer program embodied on a computer readable medium for processing a merchant identification request from a private label payment card issuer, the private label payment card issuer communicatively coupled to a multi-party payment card interchange computer that is coupled to a data warehouse, the data warehouse for storing a plurality of historical multi-party payment card transactions, said program is executed by the interchange computer and comprises at least one code segment that:

receives a list of private label merchant locations from the private label payment card issuer, the list including physical location information relating to the private label merchants listed;

processes the private label merchant list by applying an identification analysis thereto including applying one of a merchant matching only analysis, a test transaction only analysis, and merchant matching plus test transaction analysis;

identifies at least one private label merchant location included within the private label merchant list including associating a unique identifier with the at least one identified private label merchant location; and

outputs the at least one identified private label merchant location with the associated unique identifier.

30. A computer program in accordance with claim 29 further comprising at least one code segment that, when applying the merchant matching only analysis to the private label merchant list:

retrieves records of historical multi-party payment card transactions from the data warehouse, the records including physical location information for a merchant initiating each of the transactions and a unique identifier associated with the merchant;

substantially matches physical location information of the private label merchants included in the list with physical location information from the records of historical multi-party payment card transactions;

associates the unique identifier associated with the records of historical multi-party payment card transactions with a matching private label merchant location in the list; and

outputs the matching private label merchant locations and the unique identifier associated with each of the matched locations.

31. A computer program in accordance with claim 30 further comprising at least one code segment that, when applying the merchant matching only analysis to the private label merchant list:

parses the physical location information of the private label merchants in the list;

parses the physical location information from the records of historical multi-party payment card transactions; and

intelligently matches corresponding fields in the respective information.

32. A computer program in accordance with claim 30 further comprising at least one code segment that, when applying the merchant matching only analysis to the private label merchant list:

designates a match threshold;

calculates a match score for each private label merchant included in the list, the match score representing a confidence level in the corresponding match; and

flags private label merchants in the list having physical location information that matches the physical location information from the records of historical multi-party payment card transactions with a match score that is greater than the designated match threshold.

33. A computer program in accordance with claim 29 further comprising at least one code segment that, when applying the test transaction only analysis to the private label merchant list:

selects a merchant from the private label merchant list that is designated for test transaction only analysis, the selected merchant associated with a point of sale (POS) device;

creates test transaction data for the selected merchant;

receives an authorization request from the POS device, the authorization request resulting from the processing of the test transaction data at the POS device, the authorization request including a unique identifier associated with the selected merchant;

identifies the selected merchant based on the received authorization request; and

outputs a location and the unique identifier of the selected merchant.

34. A computer program in accordance with claim 33 further comprising at least one code segment that:

determines each private label merchant included on the private label merchant list designated for identification using the test transaction only analysis; and

generates test transaction data for each private label merchant designated for identification using the test transaction only analysis, the test transaction data including a test transaction card number, an expiration date, and a test transaction amount.

35. A computer program in accordance with claim 33 further comprising at least one code segment that:

receives the authorization request from the POS device, the authorization request resulting from the POS device processing test transaction data of the selected merchant, the test transaction data including a test transaction card number, an expiration date, and a test transaction amount;

detects the test transaction data;

captures the unique identifier; and

transmits a void transaction message to the POS device in response to the authorization request.

36. A computer program in accordance with claim 33 further comprising at least one code segment that transmits an electronic message from the interchange to the private label payment card issuer each time a test transaction is processed and a selected merchant is identified.

37. A computer program in accordance with claim 29 further comprising at least one code segment that, when applying a merchant matching plus test transaction analysis to the private label merchant list:

applies a merchant matching analysis to the private label merchant list to identify a location for at least one of the private label merchants; and

applies a test transaction analysis to the private label merchants included on the private label merchant list not identified by the merchant matching analysis.

38. A computer program in accordance with claim 29 further comprising at least one code segment that:

transmits the at least one identified private label merchant location with the unique identifier to the private label payment card issuer, the private label payment card issuer being in a private label payment card relationship with the identified private label merchant;

processes a private label transaction that is initiated at the at least one identified private label merchant location; and

transmits data associated with the private label transaction from the interchange to the private label payment card issuer for further processing.