MERCHANT DEVICE AND METHOD FOR SUPPORT OF MERCHANT DATA PROCESSING

• US 20100077464A1
• Filed: 08/26/2009
• Published: 03/25/2010
• Est. Priority Date: 09/23/2008
• Status: Abandoned Application

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: HARDY-MCGEE, LINDA R.
• Application Number:
  US12/548,134
• Publication Number:
  US 20100077464A1
• Time in Patent Office: Days
• US Class Current: 726/5
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 20/409 Device specific authentication in transaction processing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

A method begins by accessing a merchant web site that is associated with a merchant profile database. The method continues by receiving a log-in page. The method continues by providing log-in information of a merchant via the log-in page. The method continues, when the log-in information is confirmed, by receiving a merchant information page that contains data of a merchant profile record of the merchant profile database. The method continues by providing a response regarding the data of the merchant information page.

Claims

1. A method comprises:

accessing a merchant web site that is associated with a merchant profile database;

receiving a log-in page;

providing log-in information of a merchant via the log-in page;

when the log-in information is confirmed, receiving a merchant information page that contains data of a merchant profile record of the merchant profile database, wherein the merchant profile record identifies the merchant; and

providing a response regarding the data of the merchant information page.

2. The method of claim 1, wherein the accessing the merchant web site comprises:

transmitting an access request to an acquirer device; and

upon granting of the access request, receiving a forwarding address to the merchant web site.

3. The method of claim 1, wherein the accessing the merchant web site comprises:

accessing the merchant web site via a financial transactions processing device.

4. The method of claim 1, wherein the response comprises at least one of:

a certification regarding accuracy and completeness of the data of the merchant information page; and

an update data request.

5. The method of claim 4 further comprises, when the response is the update data request:

providing updated data to a field of the merchant information page; and

receiving a confirmation of data entry pending approval.

6. The method of claim 5 further comprises:

when a previous updating of the data of the merchant information page has not yet been approved;

receiving an update request information page in response to update data request;

receiving a selection to withdraw the previous updating of the data;

providing a request to withdraw the previous updating of the data;

when the request to withdraw the previous updating of the data has been processed, providing current updating data to the field or another field of the merchant information page; and

receiving another confirmation of data entry pending approval.

7. The method of claim 1, wherein the response comprises at least one of:

opting-in to a Qualified Payment Card Agent (QPCA) program; and

opting-out of the QPCA program.

8. The method of claim 1, wherein the data comprises:

a merchant name;

a merchant business address; and

merchant business information.

9. The method of claim 1 further comprises:

providing log-in information of a conglomerate entity via the log-in page;

when the log-in information is confirmed, receiving the merchant information page that contains data of one of a plurality of merchant profile records of the merchant profile database, wherein the plurality of merchant profile records corresponds to a plurality of merchants associated with the conglomerate entity;

receiving selection of another one of the plurality of merchants; and

receiving the merchant information page that contains data of another one of a plurality of merchant profile records that corresponds to the another one of the plurality of merchants.

10. An apparatus comprises:

an interface;

memory; and

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

access, via the interface, a merchant web site that is associated with a merchant profile database;

receive, via the interface, a log-in page;

provide, via the interface, log-in information of a merchant in accordance with the log-in page;

when the log-in information is confirmed, receive, via the interface, a merchant information page that contains data of a merchant profile record of the merchant profile database, wherein the merchant profile record identifies the merchant; and

provide, via the interface, a response regarding the data of the merchant information page.

11. The apparatus of claim 10, wherein the processing module further functions to access the merchant web site by:

transmitting, via the interface, an access request to an acquirer device; and

upon granting of the access request, receiving, via the interface, a forwarding address to the merchant web site.

12. The apparatus of claim 10, wherein the processing module further functions to access the merchant web site by:

accessing, via the interface, the merchant web site via a financial transactions processing device.

13. The apparatus of claim 10, wherein the response comprises at least one of:

a certification regarding accuracy and completeness of the data of the merchant information page; and

an update data request.

14. The apparatus of claim 13, wherein the processing module further functions to, when the response is the update data request:

provide, via the interface, updated data to a field of the merchant information page; and

receive, via the interface, a confirmation of data entry pending approval.

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

when a previous updating of the data of the merchant information page has not yet been approved;

receive, via the interface, an update request information page in response to update data request;

receive, via the interface, a selection to withdraw the previous updating of the data;

provide, via the interface, a request to withdraw the previous updating of the data;

when the request to withdraw the previous updating of the data has been processed, provide, via the interface, current updating data to the field or another field of the merchant information page; and

receive, via the interface, another confirmation of data entry pending approval.

16. The apparatus of claim 10, wherein the response comprises at least one of:

opting-in to a Qualified Payment Card Agent (QPCA) program; and

opting-out of the QPCA program.

17. The apparatus of claim 10, wherein the data comprises:

a merchant name;

a merchant business address; and

merchant business information.

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

provide, via the interface, log-in information of a conglomerate entity via the log-in page;

when the log-in information is confirmed, receive, via the interface, the merchant information page that contains data of one of a plurality of merchant profile records of the merchant profile database, wherein the plurality of merchant profile records corresponds to a plurality of merchants associated with the conglomerate entity;

receive, via the interface, selection of another one of the plurality of merchants; and

receive, via the interface, the merchant information page that contains data of another one of a plurality of merchant profile records that corresponds to the another one of the plurality of merchants.