ACQUIRER DEVICE AND METHOD FOR SUPPORT OF MERCHANT DATA PROCESSING

• US 20100057786A1
• Filed: 08/26/2009
• Published: 03/04/2010
• Est. Priority Date: 08/28/2008
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: HARDY-MCGEE, LINDA R.
• Granted Patent: US 8,527,474 B2
• Time in Patent Office: Days
• US Class Current: N/A
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/0637 Strategic management or analysis, e.g. setting a goal or target of an organisation; Planning actions based on goals; Analysis or evaluation of effectiveness of goals

Abstract

A method begins with receiving an indication that one of a plurality of merchant data files includes an inconsistency with respect to a corresponding merchant profile record in a merchant profile database. The merchant data file of the plurality of merchant data files includes merchant name, merchant business address, and merchant business information. The method continues with receiving a request to authenticate the updating of the corresponding merchant profile record when the inconsistency for the one of the plurality of merchant data files is addressed by a merchant device updating the corresponding merchant profile record. The merchant device corresponds to a merchant of the one of the plurality of merchant data files. The method continues with providing an authentication response regarding the updating of the corresponding merchant profile record.

Claims

1. A method comprises:

receiving an indication that one of a plurality of merchant data files includes an inconsistency with respect to a corresponding merchant profile record in a merchant profile database, wherein a merchant data file of the plurality of merchant data files include merchant name, merchant business address, and merchant business information;

receiving a request to authenticate the updating of the corresponding merchant profile record when the inconsistency for the one of the plurality of merchant data files is addressed by a merchant device updating the corresponding merchant profile record, wherein the merchant device corresponds to a merchant of the one of the plurality of merchant data files; and

providing an authentication response regarding the updating of the corresponding merchant profile record.

2. The method of claim 1 further comprises:

updating a second one of the plurality of merchant data files based on information obtained from a second corresponding merchant device to produce a second updated merchant data file;

updating the merchant master file in accordance with the second updated merchant data file to produce an updated merchant master file; and

transmitting at least a portion of the updated merchant master file to a financial transactions processing module associated with the merchant profile database, wherein the merchant profile record is updated in accordance with the corresponding merchant data file.

3. The method of claim 1 further comprises:

receiving an indication that a second one of the plurality of merchant data files does not have a corresponding file in the merchant profile database; and

providing a request that a record be created in the merchant profile database in accordance with the second one of the plurality of merchant data files.

4. The method of claim 1 further comprises:

receiving a suggested resolution for the inconsistency;

when the inconsistency for the one of the plurality of merchant data files is resolved by the merchant device, authenticating the resolution of the inconsistency with respect to the suggested resolution; and

when the inconsistency for the one of the plurality of merchant data files is not resolved by the merchant device, resolving the inconsistency in accordance with the suggested resolution.

5. The method of claim 1, wherein the inconsistency comprises at least one of:

a status change of the merchant of the one of the plurality of data files with respect to participation in a Qualified Payment Card Agent program;

an inconsistency with the merchant name;

an inconsistency with the merchant business address;

an inconsistency with the merchant business information, which includes at least one of taxpayer information, market segment information, socioeconomic information, and

small business information.

6. The method of claim 1 further comprises:

when the resolution of the inconsistency is authenticated, updating the one of the plurality of merchant data files within the merchant master file in accordance with the resolution of the inconsistency.

7. The method of claim 1 further comprises:

receiving an indication that the one of a plurality of merchant data files includes the inconsistency from a financial transactions processing device, wherein the financial transactions processing device maintains the merchant profile database; and

accessing the merchant profile record via a merchant web site associated with the financial transactions processing device to authenticate the updating of the corresponding merchant profile record.

8. A method comprises:

receiving a request to update a merchant profile record from a merchant device, wherein the merchant profile record is stored within a merchant profile database associated with a financial transactions processing device;

authenticating the request;

when the request is authenticated, providing the merchant device with access to a merchant web site associated with the financial transactions processing device;

receiving a request to verify an updated version of the merchant profile record; and

when the updated version of the merchant profile record is verified, authenticating the updated version of the merchant profile record.

9. The method of claim 8 further comprises:

identifying a change to merchant data associated with the merchant device;

updating a corresponding merchant data file within a merchant master file; and

transmitting at least a portion of the merchant master file to a financial transactions processing module associated with the merchant profile database, wherein the merchant profile record is updated in accordance with the corresponding merchant data file.

10. The method of claim 8 further comprises:

receiving a suggested updated version of the merchant profile record;

comparing the suggested updated version with the updated version of the merchant profile record; and

when the comparison of the suggested updated version with the updated version of the merchant profile record is favorable, indicating that the updated version of the merchant profile record has been verified.

11. The method of claim 8, wherein the authenticating the request comprises:

comparing a merchant code contained within the request with a merchant code received from a financial transactions processing device; and

when the merchant code contained within the request compares favorably with the merchant code received from a financial transactions processing device, indicating authentication of the request.

12. The method of claim 8 further comprises:

receiving an indication that a merchant data file of a merchant master data file does not have a corresponding record in the merchant profile database;

requesting that the corresponding record be created in the merchant profile database in accordance with the second merchant data file that includes a merchant business name, a merchant business address, and merchant business information; and

receiving confirmation of inclusion of the corresponding record in the merchant profile database.

13. An apparatus comprises:

an interface;

memory; and

a processing module coupled to the interface and the memory, wherein the processing module is coupled to;

receive, via the interface, an indication that one of a plurality of merchant data files includes an inconsistency with respect to a corresponding merchant profile record in a merchant profile database, wherein a merchant data file of the plurality of merchant data files include merchant name, merchant business address, and merchant business information;

receive, via the interface, a request to authenticate the updating of the corresponding merchant profile record when the inconsistency for the one of the plurality of merchant data files is addressed by a merchant device updating the corresponding merchant profile record, wherein the merchant device corresponds to a merchant of the one of the plurality of merchant data files; and

provide an authentication response regarding the updating of the corresponding merchant profile record.

14. The apparatus of claim 13, wherein the processing module further functions to:

update a second one of the plurality of merchant data files based on information obtained from a second corresponding merchant device to produce a second updated merchant data file;

update the merchant master file in accordance with the second updated merchant data file to produce an updated merchant master file; and

transmit, via the interface, at least a portion of the updated merchant master file to a financial transactions processing module associated with the merchant profile database, wherein the merchant profile record is updated in accordance with the corresponding merchant data file.

15. The apparatus of claim 13, wherein the processing module further functions to:

receive, via the interface, an indication that a second one of the plurality of merchant data files does not have a corresponding file in the merchant profile database; and

provide, via the interface, a request that a record be created in the merchant profile database in accordance with the second one of the plurality of merchant data files.

16. The apparatus of claim 13, wherein the processing module further functions to:

receive, via the interface, a suggested resolution for the inconsistency;

when the inconsistency for the one of the plurality of merchant data files is resolved by the merchant device, authenticate the resolution of the inconsistency with respect to the suggested resolution; and

when the inconsistency for the one of the plurality of merchant data files is not resolved by the merchant device, resolve the inconsistency in accordance with the suggested resolution.

17. The apparatus of claim 13, wherein the processing module further functions to:

when the resolution of the inconsistency is authenticated, update the one of the plurality of merchant data files within the merchant master file in accordance with the resolution of the inconsistency.

18. The apparatus of claim 13, wherein the processing module further functions to:

receive, via the interface, an indication that the one of a plurality of merchant data files includes the inconsistency from a financial transactions processing device, wherein the financial transactions processing device maintains the merchant profile database; and

access the merchant profile record via the interface and a merchant web site associated with the financial transactions processing device to authenticate the updating of the corresponding merchant profile record.

19. An apparatus comprises:

an interface;

memory; and

a processing module coupled to the interface and the memory, wherein the processing module is coupled to;

receive, via the interface, a request to update a merchant profile record from a merchant device, wherein the merchant profile record is stored within a merchant profile database associated with a financial transactions processing device;

authenticate the request;

when the request is authenticated, provide, via the interface, the merchant device with access to a merchant web site associated with the financial transactions processing device;

receive, via the interface, a request to verify an updated version of the merchant profile record; and

when the updated version of the merchant profile record is verified, authenticate the updated version of the merchant profile record.

20. The apparatus of claim 19, wherein the processing module further functions to:

identify a change to merchant data associated with the merchant device;

update a corresponding merchant data file within a merchant master file; and

transmit, via the interface, at least a portion of the merchant master file to a financial transactions processing module associated with the merchant profile database, wherein the merchant profile record is updated in accordance with the corresponding merchant data file.

21. The apparatus of claim 19, wherein the processing module further functions to:

receive, via the interface, a suggested updated version of the merchant profile record;

compare the suggested updated version with the updated version of the merchant profile record; and

when the comparison of the suggested updated version with the updated version of the merchant profile record is favorable, indicate that the updated version of the merchant profile record has been verified.

22. The apparatus of claim 19, wherein the processing module further functions to authenticate the request by:

comparing a merchant code contained within the request with a merchant code received from a financial transactions processing device; and

when the merchant code contained within the request compares favorably with the merchant code received from a financial transactions processing device, indicating authentication of the request.

23. The apparatus of claim 19, wherein the processing module further functions to:

receive, via the interface, an indication that a merchant data file of a merchant master data file does not have a corresponding record in the merchant profile database;

request, via the interface, that the corresponding record be created in the merchant profile database in accordance with the second merchant data file that includes a merchant business name, a merchant business address, and merchant business information; and

receive, via the interface, confirmation of inclusion of the corresponding record in the merchant profile database.