Enhanced merchant identification using transaction data
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.
1. A method comprising:
receiving, by a server computer, transaction data associated with a first transaction between a user and a merchant;
retrieving, by the server computer, a string of characters of a merchant name from the transaction data;
evaluating, by the server computer, the string of characters of the merchant name with a set of rules;
normalizing, by the server computer using the set of rules, the merchant name to form a normalized merchant name, the normalized merchant name being a common format for different raw names for the merchant;
storing, by the server computer, the normalized merchant name in association with the string of characters of the merchant name in a database;
receiving, by the server computer, an authorization request message for a second transaction comprising the string of characters of the merchant name and a transaction amount;
determining, by the server computer, the normalized merchant name from the string of characters of the merchant name;
modifying, by the server computer in real time, the authorization request message to include the normalized merchant name from the database; and
transmitting, by the server computer, the authorization request message with the normalized merchant name to an issuer computer.
2. The method of claim 1 , wherein the authorization request message is a second authorization request message, and wherein the transaction data in the first transaction is present in a first authorization request message.
3. The method of claim 1 , wherein the authorization request message is received by the server computer via an acquirer computer.
4. The method of claim 1 , wherein receiving the authorization request message, determining the normalized merchant name from the string of characters of the merchant name, and transmitting the authorization request message with the normalized merchant name, occur in real time.
5. The method of claim 1 , further comprising:
determining, by the server computer, a fraud trend associated with the normalized merchant name.
6. The method of claim 1 , wherein the server computer is in a payment processing network configured to process credit and debit card transactions.
7. The method of claim 1 , further comprising:
determining, by the server computer, that a source of the transaction data is a certified data source.
8. The method of claim 1 , further comprising:
receiving an authorization response message for the second transaction from the issuer computer.
9. The method of claim 1 , wherein the authorization request message comprises an account identifier.
10. The method of claim 1 , wherein the authorization request message comprises a merchant category code.
11. The method of claim 1 , wherein the authorization request message is a second authorization request message from a POS terminal of the merchant, and wherein the transaction data are present in a first authorization request message from the POS terminal.
12. The method of claim 11 , wherein the first transaction is a first payment transaction, the second transaction is a second payment transaction, wherein the POS terminal is a first POS terminal, the string of characters is a first string of characters associated with a first raw merchant name, and wherein the first authorization request message and the second authorization request message are received from the first POS terminal via a first acquirer computer, and wherein the method further comprises:
receiving, by the server computer, a third authorization request message comprising a second string of characters different from the first string of characters from a second POS terminal of the merchant from a second acquirer computer in a third payment transaction, the second string of characters associated with a second raw merchant name;
modifying, the server computer, the third authorization request message to include the normalized merchant name; and
transmitting, by the server computer, the third authorization request message with the normalized merchant name to the issuer computer for authorization.
13. A server computer comprising:
a processor; and
a tangible non-transitory computer readable medium coupled to the processor, the tangible non-transitory computer readable medium comprising code, executable by the processor to cause the processor to perform a method comprising:
receiving transaction data associated with a first transaction between a user and a merchant;
retrieving a string of characters of a merchant name from the transaction data;
evaluating the string of characters of the merchant name with a set of rules;
normalizing using the set of rules, the merchant name to form a normalized merchant name, the normalized merchant name being a common format for different raw names for the merchant;
storing the normalized merchant name in association with the string of characters of the merchant name in a database;
receiving an authorization request message for a second transaction comprising the string of characters of the merchant name and a transaction amount;
determining the normalized merchant name from the string of characters of the merchant name;
modifying the authorization request message in real time to include the normalized merchant name from the database; and
transmitting the authorization request message with the normalized merchant name to an issuer computer.
14. The server computer of claim 13 , wherein the authorization request message is a second authorization request message, and wherein the transaction data in the first transaction is present in a first authorization request message.
15. The server computer of claim 13 , wherein the authorization request message is received by the server computer via an acquirer computer.
16. The server computer of claim 13 , wherein receiving the authorization request message, determining the normalized merchant name from the string of characters of the merchant name, and transmitting the authorization request message with the normalized merchant name occur in real time.
17. The server computer of claim 13 , wherein the method further comprises:
retrieving another string of characters of a merchant address from the transaction data;
evaluating the another string of characters of the merchant address with the set of rules; and
normalizing, using the set of rules, the merchant address to form a normalized merchant address, the normalized merchant address being another common format for different raw addresses for the merchant.
18. The server computer of claim 13 , wherein the method further comprises:
determining, by the server computer, a fraud trend associated with the normalized merchant name.
19. The server computer of claim 13 , wherein the authorization request message comprises a primary account number.
20. A system comprising:
a server computer comprising
a processor, and
a tangible non-transitory computer readable medium coupled to the processor, the tangible non-transitory computer readable medium comprising code, executable by the processor to cause the processor to perform a method comprising,
receiving transaction data associated with a first transaction between a user and a merchant,
retrieving a string of characters of a merchant name from the transaction data,
evaluating the string of characters of the merchant name with a set of rules,
normalizing using the set of rules, the merchant name to form a normalized merchant name, the normalized merchant name being a common format for different raw names for the merchant,
storing the normalized merchant name in association with the string of characters of the merchant name in a database,
receiving an authorization request message for a second transaction comprising the string of characters of the merchant name and a transaction amount,
determining the normalized merchant name from the string of characters of the merchant name,
modifying the authorization request message in real time to include the normalized merchant name from the database, and
transmitting the authorization request message with the normalized merchant name to an issuer computer; and
the issuer computer in communication with the server computer.