Management of E-Commerce Data by Consumers

A system and a method for electronic commerce allowing consumers to centrally receive and send electronic data from multiple merchants. The system includes a central server having software which gathers the electronic data including emails and event notifications from member merchants directed to consumers accounts who maintain and register accounts on a centralized server. The system provides a web-based browser interface through which the consumer is able to view and edit the information in the database, to exert control over what information is made available to each merchant, and to view emails and event notifications directed to the consumer's account on the server.

DETAILED DESCRIPTION

In one or more embodiments, a system and method is provided for enabling consumers and merchants to store and maintain a comprehensive information profile (hereinafter “centralized information account”30) in a centralized data server7that is accessible over a distributed electronic network, such as the Internet32. The information account30may be used to store any type of data desired by the consumer, including, for example, demographic information, financial information, medical information, family information, contact information, documents, multimedia files, etc. Furthermore, the information account may be used to store any type of data desired by the participating merchants including, for example, sale event information, specialized targeted catalogs, merchants coupons, merchants promotions, sale history, customer purchase history, multimedia files, etc. The centralized data repository is preferably accessible via a network by any authorized network device. In various embodiments, no specialized application programs are required to be permanently downloaded to the consumer's computer in order to access the central information account.

According to certain embodiments, at the consumer's direction, selected information in the central information account30may be accessed and, if desired, shared with authorized merchants6, Financial Enterprises8, business partners or any other entity that requires certain of the consumer's information. The terms “merchant”, “vendor” and “business partner” are used herein in a general sense to refer to persons, businesses, enterprises or entities that make products or services available to consumers. As used herein, the terms “consumer,” “buyer,” and “user” are interchangeable.

Merchant's Server-side software or temporary consumer-side software may, in some embodiments, be used to manage communications with the central Data Server7hereafter referred as “CDS”, central information account30and to automatically integrate central information account data into a process executed by the CDS software.

The data in the central information account is preferably stored in a SQL database alternatively using a tagged data format. In one embodiment, the data in the information account may be stored using the Extensible Markup Language (XML) data format, which is an open standard for describing data from the World Wide Web Consortium (“W3C”). As is known in the art, XML tags are used to define the types of information that are represented by the data element. The XML standard provides a great deal of flexibility in that custom tags may be defined for any type of information that the consumer may desire to store in the information account. Using any well-known XML-related querying, parsing, transforming and/or filtering techniques, and individual data elements in the information account may be accessed, updated, deleted, created, or otherwise manipulated.

The central information account30may be structured as one or more data aggregates, e.g., XML data aggregates. An entire XML data aggregate is stored within a data field of a database table. This data field is a long text field containing all of the information associated with the given record. In one embodiment, all consumer information in the central information account may be stored in a single XML data aggregate comprising consumer information elements and sub-elements. Attributes may also be associated with any element and sub-element in order to provide additional information. A transformation or filtering mechanism, such as “Style Sheets,” may be applied to the single XML data stream in order to extract only selected data elements there from at the direction of the consumer.

In an alternative embodiment, the central information account30may be normalized into a plurality of discrete data aggregates, each aggregate representing a predetermined information profile29. An information profile refers to a package of consumer information relating to specific products, services offered by one or more merchants. For example, prescribing to sales events from specific merchants or loyalty card rewards for specific products.

Access constraints implemented in the system of the present invention according to one or more embodiments as described herein allow for the establishment of data profiles28and information profile29. A data profile refers to a group of consumer data elements that are authorized by the consumer to be delivered to specific merchants at the request of the consumer. In other words, the data profile includes data from the central information account that may be used to in order retrieve information for use in commerce with any merchant that is a member of the CDS7. In much the same way that a consumer may have one information account which specific data elements groups are each valid only on specified exchanges. For example, a loyalty card application might contain all consumer information that would be required to complete the application as defined in data profile28. Individual information may be retrieved from the information account and transmitted by to authorized merchant at the request of the consumer in order to complete the membership application.

Exemplary embodiments of the present invention will now be described with reference to the drawings, in which like numerals represent like elements throughout the several figures. A high-level block diagram of a system in accordance with an exemplary embodiment of the present invention is shown in and described with reference toFIG. 1. As shown, a central data server7(CDS) is provided for storing consumer and merchant information that may be easily accessed from any network device attached to the network32. The network32may comprise any telecommunication and/or data network, whether public or private, such as a local area network, a wide area network, an intranet, an internet and any combination thereof and may be wireline and/or wireless. Various methodologies as described herein may be practiced in the context of distributed computing environments. The network32thus provides for the open and seamless distribution of consumer information to and from the central information account30.

In the system illustrated inFIG. 1, the high level exemplary operating environment encompasses various network devices for accessing and reading associated computer-readable media having stored thereon data and/or computer-executable instructions for implementing various methods of the present invention of data storage, management and distribution. Generally, a network device includes a communication device for transmitting and receiving data and/or computer-executable instructions over the network32, and a memory for storing data and/or computer-executable instructions. A network device may also include a processor for processing data and executing computer-executable instructions, as well as other internal and peripheral components that are well known in the art (e.g., input and output devices). A network device may generally comprise any device that is capable of communicating with the resources of the network32. A network device in this embodiment comprises Central Data Server7, Consumer's Device3, merchant database servers9and financial enterprise server8. Any server in the system may interact with another server and the central data server7via the network32and can host a web server comprising one or more websites.

A consumer device3may comprise a desktop computer, a laptop computer, digital assistant (PDA), and the like. These and other types of consumer devices3will be apparent to one of ordinary skill in the art. For convenience, the following explanation will be made with reference to a client device3generically, but, unless otherwise indicated, it will be understood that the principles and concepts described will also encompass wired or wireless devices, as consumer device3illustrated inFIG. 1. Moreover, although exemplary embodiments will be described herein in the context of the Internet or a web-based environment, it will be appreciated that the various principles and methods of operation will be applicable or may be practiced in other environments as well.

According to a preferred embodiment, a consumer device3may execute a browser or another suitable application for interacting with web-server31hosted by a central data server7and other network devices. Through a graphical user interface provided by the web-server31, the web-server31may require the consumer2(i.e., the operator of the consumer device3) to input certain information pertaining to or associated with the consumer. The present invention allows the consumer to input information elements that can be transmitted from the central information account30to the merchants6for processing. Although exemplary embodiments of the present invention will be described herein in the context of a web-based environment, those skilled in the art will appreciate that other environments are suitable as well.

In general, the central information account30may be any data structure for storing consumer information. Preferably, however, the information account30is stored as a tagged data structure, such as one or more XML data aggregates. The data in the central information account30is preferably encrypted so that anyone gaining unauthorized access to the central information account30will not be able to read the data. Also, in a preferred embodiment, each information account30in the central data server7is encrypted separately, so that someone authorized to access the information account of one consumer may not also gain access to the information account of another consumer.

In accordance with a preferred embodiment, the consumers may maintain sole responsibility for storing and updating the information in the information account30. Only the consumer, or those authorized by the consumer, may use the information account30to complete e-commerce or other electronic commerce activities. Consumers create an information account30either through a website hosted by the central data server7or by submission of information account by merchants6or by the financial enterprise8.

Upon creation of a central information account30, a consumer may be given an identification number, a username and/or a password. Other types of consumer authentication information are known in the art and may also be used in the context of the present invention. The system ofFIG. 1can provide the consumer with a variety of authentication services and methods34known in the art for accessing the information account30, transferring selected information to a merchants and/or allowing a merchant6limited and constrained access to the information account30, as described in further herein.

Authentication methods34include public/private key infrastructure, certificated authentication, IP authentication, Private questions, Key Entry, Crypto Key, Active Directory Authentication, LDAP Authentication and other authentication methods known to those skilled in the art.

Financial Enterprise/Clearing Agent8may be given the authorization from the consumer2to access its central information account30using one of the data profiles28stored in the central data server7(CDS). After authentication with the CDS7using authentication services34the financial enterprise/clearing agent8is able to retrieve consumer data elements to be processed for financial transactions submitted by merchants6or any financial transactions requested by consumer2and stored as a coded request in the central information account30. In a particular example a consumer2may request a credit card from the financial enterprise/clearing agent8using the central data server7and central information account30data elements. Further example may include a consumer request from the financial enterprise8to receive detailed transaction information.

Data profile28is a set of pointers to the data stored in the central information account30. The data profile may include xml tags to point and define data elements that could be delivered to merchants6or financial enterprises8in a controlled manner avoiding repetitive data entry by the consumer8. The data profile includes XML tags, or database field names used to point to data elements stored in the central information account30. The consumer may select specific data elements to be saved into one data profile28for specific merchants and another data profile28to be associated with another group of merchants6or financial enterprises8. Upon request from merchant database server9only a specific data profile can be used to access customer's central information account30.

Information profile29is a set of data filter definition to non consumer originated data (mostly merchant data) stored in the central information account30. The merchants6can send to the information account electronic data including emails, catalogs, coupons, events notifications, sales items, sales history and other targeted marketing information as defined in the information profile29. The information profile29may include xml tags or object names to define filtered data elements that could be delivered by merchants6or financial enterprises8in a controlled manner so the merchant database servers will process only information defined in the profile and upload that information to the central data server7, avoiding sending information not requested by consumer2and not defined in the information profile29. The information profile includes filter definition including XML tags, database field names and object names to data elements that can be stored in the central information account30. The consumer may select specific information elements to be retrieved or filtered from merchant database server9and financial enterprises8using one information profile29for specific merchants and another information profile29to be associated with another group of merchants6or financial enterprises8. Upon submission of information profile29to the merchants or financial enterprises, the information profile29will be used to process the data elements as defined in the profile in order to upload to the central data server7only requested information as indicated in the profile29. For example one profile may include email submission only and the second profile may include emails, catalogs and sales events submissions by the merchants6who have authorized access to the central data server30and to the specific consumers through their central information account30.

Upon creation of the central information account30merchants6upload to the central data server7targeted marketing data15based on the information profile29entered by the consumer2. Information profile29will be discussed in detail inFIG. 2. The merchants6can upload to the central information account electronic data including emails, catalogs, coupons, events notifications, sales items, sales history and other targeted marketing information. The uploaded information is stored in the CDS7in any data structure for storing consumer information known in the art. Preferably, however, the information uploaded by the merchant6into central information account30should be stored as a tagged data structure, such as one or more XML data aggregates.

Those skilled in the art will appreciate that the illustration and discussion of exemplary embodiments with reference toFIG. 1is provided as a generalized example only. Specific details regarding data formats and network communication protocols have been omitted, as such details are well known in the art. Furthermore, the present invention is not intended to be limited to the use of any particular data formats or protocols. Any existing or future formats or protocols may be used without departing from the spirit and scope of the invention. Furthermore, many network components were not shown or discussed with reference toFIG. 1, such as gateways, routers, hubs, switches, firewalls, DNS servers, authentication servers, certificate authorities, and the like. The functions and roles of such network components are also well known in the art and need not be described in detail herein.

FIG. 2provides an abstract illustration of a central information account30in accordance with an exemplary embodiment of the present invention as described herein. In the illustrated embodiment, the consumer information is stored in the central information account30as a single tagged (delimited) data stream. Those skilled in the art will recognize that XML provides a suitable tagged data format for use in connection with the present invention. However, other tagged data formats can be employed as well. Thus, references to the XML standard in connection with exemplary embodiments of the present invention are not intended to limit the scope of the present invention. The single XML data stream comprises a plurality of consumer information elements52and plurality of merchant information elements53. A consumer information element52and merchant information element53may be divided into any number and/or level of sub-elements. As is well known in the art, an XML consumer information element and merchant information element may also be associated with one or more attributes. An attribute54may provide additional information about the content, structure or formatting of a consumer information element52and the merchant information element53.

A consumer information element52may comprise any type of data or information, including text strings, objects, files, applications, etc. Obviously, the more consumer information that is stored in the central information account30, the larger the XML data stream will be. The size of the XML data stream is limited only by the hardware and software limitations of the system (e.g., memory size, processor speed, bandwidth, etc).

A merchant information element53may comprise any type of data or information, including text strings, objects, emails, web files, digital files, applications, etc. Obviously, the more consumer information that is stored in the central information account30, the larger the XML data stream will be. The size of the XML data stream is limited only by the hardware and software limitations of the system (e.g., memory size, processor speed, bandwidth, etc).

An information account30is preferably unique to a single consumer2. Each central information account30is stored in the central data server7may thus comprise a discrete XML data stream. Each central information account30stored in the central data server7may be individually encrypted. For example, one method for encrypting an information account30may involve use of the consumer's2public key. Accordingly, only someone having access to the consumer's private key will be able to decrypt the consumer's information. Many other and/or additional methods for encrypting information accounts30and/or the entire central data server7will occur to those skilled in the art.

As depicted inFIG. 2, illustrates an exemplary database schema55in accordance with one or more exemplary embodiments of the present invention as disclosed herein. The central information account data30may be stored in any database management systems known in the art. The preferred embodiment depicts SQL server56with database schema55used for database management system. In particular, the database schema56represents the situation where the information account30is segmented into multiple discrete data aggregates, the same as the XML tags. The database schema56may include the same or similar data fields as the XML schema52and53.

FIG. 3provides an abstract illustration of a central information account30in accordance with an exemplary embodiment of the present invention as described herein. In the illustrated embodiment, the consumer information is stored in the central information account30as a single tagged (delimited) data stream. Those skilled in the art will recognize that XML provides a suitable tagged data format for use in connection with the present invention. However, other tagged data formats can be employed as well. Thus, references to the XML standard in connection with exemplary embodiments of the present invention are not intended to limit the scope of the present invention. The central information account data30may be stored in any database management systems known in the art. In the preferred embodiment SQL database server is used for database management system. In particular, a database schema is used where the information account30is segmented into multiple discrete data aggregates, the same as the XML tags defining the central information account30data elements. The database schema may include data fields for columns definition the SQL database or will use data elements of the XML schema to be stored as XML data, stored into corresponding data tables in the SQL database.

An information account30is preferably unique to a single consumer2. Each central information account30is stored in the central data server7may thus comprise a discrete XML data stream. Each central information account30stored in the central data server7may be individually encrypted. For example, one method for encrypting an information account30may involve use of the consumer's2public key. Accordingly, only someone having access to the consumer's private key will be able to decrypt the consumer's information. Many other and/or additional methods for encrypting information accounts30and/or the entire central data server7will occur to those skilled in the art.

Web-server31integrated with the central data server7provides a graphical user interface enabling the consumer2to interact with the central data server7and the central information account30. The web-server31may require the consumer2(i.e., the operator of the consumer device3) to input certain information pertaining to or associated with the consumer and then enable the consumer to view/edit/delete the data elements in the central information account30. Furthermore, the web-server31may provide programmable interfaces to the merchants and other network devices in order to access the records stored in the central data server7.

Data profile28is a set of pointers to the data stored in the central information account30. The data profile may include xml tags to point and define data elements that could be delivered to merchants6or financial enterprises8in a controlled manner avoiding repetitive data entry by the consumer8. The data profile includes XML tags, or database field names used to point to data elements stored in the central information account30. The consumer may select specific data elements to be saved into one data profile28for specific merchants and another data profile28to be associated with another group of merchants6or financial enterprises8. Upon request from merchant database server9only a specific data profile can be used to access customer's central information account30.

Information profile29is a set of data filter definition to non consumer originated data (mostly merchant data) stored in the central information account30. The merchants6can send to the information account electronic data including emails, catalogs, coupons, events notifications, sales items, sales history and other targeted marketing information as defined in the information profile29. The information profile29may include xml tags or object names to define filtered data elements that could be delivered by merchants6or financial enterprises8in a controlled manner so the merchant database servers will process only information defined in the profile and upload that information to the central data server7, avoiding sending information not requested by consumer2and not defined in the information profile29. The information profile includes filter definition including XML tags, database field names and object names to data elements that can be stored in the central information account30. The consumer may select specific information elements to be retrieved or filtered from merchant database server9and financial enterprises8using one information profile29for specific merchants and another information profile29to be associated with another group of merchants6or financial enterprises8. Upon submission of information profile29to the merchants or financial enterprises, the information profile29will be used to process the data elements as defined in the profile in order to upload to the central data server7only requested information as indicated in the profile29. For example one profile may include email submission only and the second profile may include emails, catalogs and sales events submissions by the merchants6who have authorized access to the central data server30and to the specific consumers through their central information account30.

FIG. 4is a generalized interaction diagram illustrating the interaction between various system components of certain exemplary embodiments of the present invention in connection with consumer-controlled storing, managing and/or distributing information and with the Financial Enterprises direct integration with vendor database servers. The exemplary embodiments discussed with reference toFIG. 4employ a web-browser to manage communication and data session between the client device3and the central data server web-server31. Alternative embodiments employing a server-side application instead of the web-server31will be discussed below. Those skilled in the art will appreciate the differences between the interactions involving the network devices as web-server31, consumer devices3and merchant database servers9.

With respect to consumers2, the system is optimized to provide all of the targeted marketing information provided by the merchants and purchasing information with the merchants to the consumer thereby allowing the consumer to verify the information. The system can establish an editing session between the consumer's device3(consumer's computer) and the CDS7through its web server31to permit the consumer to select from options such as which credit card to use, which loyalty cards to register, the shipping address, and the shipping means.

In an alternate embodiment, a consumer2can register with the CDS7prior to purchasing a product from a specific merchant and the consumer details would be provided to the merchant database server9by the CDS at the time of purchase. In yet another embodiment, the merchant6sends an email message to a consumer2through the CDS7wherein the email message contains the proper links to the CDS to allow the consumer to register with the CDS prior to purchasing a product. In yet another embodiment, a known (registered) consumer can access the CDS7to amend the consumer's stored central information account30and alert the participating merchants6of this change.

In the preferred embodiment, the consumer2has the option of indicating directly to the merchants6that the consumer is a registered consumer with the CDS7. The merchant's database server9has means to determine and verify that a consumer is a registered consumer on the CDS7. If the consumer claims to be a registered consumer, merchant's offers, catalog and other data as defined in the information profile28is forwarded to the CDS. If the consumer does not claim to be a registered consumer, then the merchant's web server software acquires the consumer's data from the customer input form and uploads the information to the CDS7to be stored in the central information account30. In the preferred embodiment, the merchant's database server9determines which products can be sold to the consumer using CDS7. For instance, a consumer2in one state may not be able to purchase a firearm if the law governing the consumer or merchant does not permit such a transaction and it is the merchant obligation to verify these laws. The merchant's database servers9evaluates the information acquired from its particular data entry forms or central account information30received from the CDS7to determine if the information from the consumer is sufficient, and is abided by the law in order to complete the purchase transaction or other merchant's business transactions. In the preferred embodiment, the consumer is provided the option of registering with the CDS directly or through the participating merchants and financial enterprises.

When registering through a merchant and if the consumer elects to become a CDS registered consumer, then the merchant's database server9connects the consumer2to the CDS7directly or through a URL. In an alternate embodiment, the merchant's database server9forwards the registration data to the CDS9after the registration data is collected on the merchant database server9. The registration connection between the CDS and merchant database server can be established in any manner as known in the art. For example, in one embodiment the merchant's database server9sends the proper links to connect the consumer's browser with the CDS to allow the consumer to register with the CDS. In another embodiment, the merchant's database server software sends an email message to the consumer wherein the email message contains the proper links to the CDS to allow the consumer to register with the CDS.

In an alternative embodiment, the merchant can also send a consumer's information profile12to the consumer which the consumer browser or email service forwards to the CDS7. The CDS7prompts the consumer for the consumer's information profile12which is preferably stored in XML format and uploaded to the CDS by the browser or using email service. In one embodiment, information profile12is part of the email message or the browser content. In another embodiment, the information profile12is in a file attached to the email message or sent as FTP upload to the CDS.

In the preferred embodiment, the registration information includes the consumer's identification number, email address, passphrase, default payment parameters, default shipping address, and default shipping means; however this list is not meant as a limitation. In alternate embodiments, the registration can include different information.

In the preferred embodiment, the authentication services34may use and store the Internet address for a consumer's browser, the consumer's email address, originating URL, browser cookie, private/public keys, cryptographic keys, digital certificates, SSO cookies and other authentication files used by the authentication services34.

In another embodiment, an email message from the merchant6to the consumer2comprises a merchant's catalog and sale events and a link to the CDS Web page where the consumer can use in order to register with the CDS7. In another embodiment, the consumer enters either the Internet address for the CDS web-server31or the direct Internet address for the registration process on the CDS. In another embodiment, the email message contains connection software which connects the consumer to the CDS. In one embodiment, the connection software is part of the email message. In another embodiment, the connection software is in a file attached to the email message.

Once the consumer accesses the CDS for first time registration, the CDS web-server31prompts the consumer for registration information and/or consumer profile12. In the preferred embodiment, the registration information includes the consumer's identification number, email address, cryptographic keys, default payment parameters, default shipping address, default information profile29, default data profile28and default shipping means, however this list is not meant as a limitation. In alternate embodiments, the registration information can include different information.

Before the registration process commences the CDS7web-server31determines if the consumer is known to the CDS7, thus avoiding double entry of central account information30for the same consumer supplied by the consumer during a prior registration process. If the CDS software determines at the beginning of the registration process that the information provided by the consumer is insufficient to identify the consumer, then the CDS software prompts the consumer for entry of the complete registration data.

Once a consumer is registered in the CDS, the consumer's browser displays the consumer's information to the consumer who can amend the consumer's information using techniques known in the art. The consumer is able to add, delete or modify the consumer's information. Once the consumer completes his or her amendments, the consumer selects to either save or cancel the amendments.

Prior art methods of consolidating consumer payment methods and preferred vendor information are designed for the convenience of the vendors, as a way of improving their ability to efficiently conduct commerce. In contrast, the present invention is designed to aid the consumer in controlling personal information, which the vendors might otherwise exploit at will. The invention accordingly provides an interface designed to implement the consumer's instructions regarding the entry and management of the consumer's information, and to give the consumer tools for the maintenance of privacy and for control of access to personal and/or financial information.

To the extent prior art services aid the consumer, they merely relieve the consumer of the need to repeatedly enter account numbers and billing and shipping addresses. This is accomplished, however, by giving merchants and vendors relatively unfettered access to the consumer's information. The consumer's purchasing habits and interests, in particular, are treated not as private, personal information; indeed, this information is treated as a commodity, to be bought and sold among information brokers and marketing professionals.

The present invention provides a consumer-centric repository for this private financial and behavioral information. The methods of the invention allow the consumer to control what information is shared with what vendors, to control what sales and promotional information is to be received, and to filter out or block delivery of unwanted promotional materials. Changes in credit card information, such as card numbers and expiration dates, can be made to the consumer-controlled CDS, and this information will be propagated to merchants and vendors as purchases are made, i.e. in the course of normal business.

The invention operates on a computer network having a centralized data server (the CDS) which comprises a web server and a database containing consumer information (the CDS database) organized into fields and records. Via a user's personal computer having browser software, the invention provides a method for presenting and editing the consumer information in the database, comprising, at the user's computer, receiving a web page from the web server and displaying a rendering of the page in the browser window. The web pages will, in the embodiments describe below, present data in a spreadsheet-like format consisting of at least one row and a plurality of columns. Editing pages will present the data in editable form, and will transmit any changes made by the consumer to the database for recordation.

Referring now toFIG. 6, the consumer is presented with a browser window displaying a list of consumer-selected retailers; in this particular embodiment the information is presented in a spreadsheet-like format. In this format, each row represents a record in the CDS database. The left-most column contains a tool icon, and clicking on this icon brings up an editing window wherein the data in the record can be altered. The second column contains the “delete” icon, a button which enables deletion of the entire record represented by that row. Columns labeled Retailer Name, Retailer Account, Logon ID and Retailer Password are self-explanatory. In one embodiment of the invention, display of the passwords on this and all other pages is blocked, unless the user has passed a security check specific to the consumer's individual CDS. This security check may, by way of example, take the form of a master password or pass phrase, alone or in combination with a USB security dongle, a security token, or a digital certificate. The sixth column features icons identifying the retailer associated with the row or record; this icon is a button which provides the url of the retailer's site to the user's browser, and opens that page in the browser. The on/off buttons reflect consumer preferences, as set and described in connection withFIG. 7. Text-labeled buttons above the list bring up help windows, and alternately hide and display the retailer information. Buttons along the top of the window are consistent from window to window, and are used to navigate the site and move among the information display pages.

FIG. 7is a browser window wherein the data displayed inFIG. 6is entered. The name of the retailer may be typed in or selected from a scrolling menu. Account number, Logon ID, and password can be entered. Yes/No buttons are selected by the consumer to indicate whether or not the consumer has a membership or discount card with the retailer, whether or not the consumer wishes to receive email, promotional flyers, or coupons from the retailer, and whether or not the consumer wishes to provide the retailer with CDS credentials or card credentials

FIG. 8is a browser window presenting a spreadsheet-like display of vendor details. The first two columns function as described above. Columns labeled Website, Vendor Name, Street, City, Region (State), Country, Postal Code, Telephone, Fax, Email, Vendor Account, Logon ID, and Password are self-explanatory. The icons in the fourth column are buttons which open the vendor's web site in the browser.

FIG. 9is a browser window wherein the data displayed inFIG. 8is entered. Each field is labeled with the corresponding column ofFIG. 8in which the entered data will be displayed.

FIG. 10is a browser window wherein information specific to retailer web sites is displayed. The contents of columns 1-7 have been described above. This window adds the date on which the record was created, and the date on which it was most recently edited. This window enables the user to note which records are old and may contain stale information; the user may wish to verify, update, or delete records after a certain period of time has passed. Users who take the precaution of changing passwords at regular intervals can identify any sites that have yet to be assigned new passwords.

FIG. 11is a browser window wherein the data displayed inFIG. 10is entered. Each field is labeled with the corresponding column ofFIG. 8in which the entered data will be displayed. The Web Site ID is chosen from a scrolling list of already-existing records, and existing data in the indicated fields will be displayed in editable form. The “Insert” button causes any new data to be entered into the CDS.

FIG. 12is a browser window which displays incoming email messages from retailers, from whom the user has elected to receive promotional announcements, flyers, coupons, and other e-mailed materials. Each incoming email message is a new record, represented here as a row in the spreadsheet-like layout. The receiving e-mail address for these messages is preferably associated with the CDS server, so that the consumer's pre-set filters and preferences can be applied prior to display in this window. This spares the user's everyday email account from what could become a blizzard of promotional messages. Alternatively, the browser can be given access to the local inbox of the user, as generated by an email client program such as Outlook™, Thunderbird™, Opera™, or the like.

The first column contains icons, which are buttons that bring up the associated email message in a new window. The second column contains delete buttons for each record. The Subject, From, Reply To, and Sent Date are self-explanatory; these columns contain the same information that would be displayed by an email client. The seventh column contains buttons, preferably in the form of readily-identifiable merchant logos, which deliver the url of the vendor's home page or logon page to the browser, and cause the page to be opened. If there is a url specific to the offer or event being advertised, it can be accessed through the new window display invoked by the icon in column 1. The Preview column contains buttons that display any coupons present as graphic elements in the body of the email, in a pop-up browser window. Preferably, participating merchants will employ a set format for emails, which identifies coupons to the system.

FIG. 13shows a browser window that displays a calendar of events, typically sales or other limited-time promotions, that are available on specific dates. Preferably, participating merchants will employ a set format for dates, such as an ICS file, so that the system will recognize them and add them to the calendar.

FIG. 14shows a browser window that displays information about the consumer's store credit cards, loyalty cards, membership cards, and accounts, in a spreadsheet-style format. The first two columns function as described above. The column entitled “Card Title” identifies the merchant or product vendor. The fourth column contains icons in the form of readily-identifiable merchant or vendor logos; these icons are buttons that cause the merchant's or vendor's home page or logon page to be opened in a new browser window. “Card Account” is the account number. “Bar Code Type” specifies the bar code type for the bar codes that are typically present on consumer loyalty cards; the code identifies the account of the holder to checkout scanners at retail stores. “Code 128” indicates the most common bar code symbology, and enables the conversion of the account number in column 5 to the barcode displayed in column 10. Other symbologies, such as U.P.C. and EAN-8, can be specified if the vendor employs such codes. Card Type identifies whether the card is a membership, loyalty, discount, or other type. Buttons on the lower right enable the user to generate and print membership, bank, loyalty, and discount cards having the requisite barcodes, which can be presented for scanning at a point of sale terminal. On a mobile device such as a smart phone, PDA, or tablet, the displayed bar code can be scaled up and scanned directly from the display screen of the device.

FIG. 15shows a browser window that displays information about the consumer's bank cards and accounts, in a spreadsheet-style format. The icons in the first column bring up a window in which the record can be edited. The second column links to the user's digital certificate, key, or PIN, and provides the number itself or a file path to the needed certificate, as required for on-line access to the account. The third column contains buttons that delete the associated record. Bank/Card Account, LogOn ID, and Bank Password are self-explanatory. The seventh column contains icons, here in the form of bank logos, which are buttons that open the bank's home page or logon page in a new window. The Get Emails and Get Flyers on/off buttons indicate the user's preferences, set as described in connection withFIG. 16.

FIG. 16is a browser window wherein the data displayed inFIG. 15is entered. The name of the bank is selected from a scrolling menu. Account number, Logon ID, and password can be entered. Yes/No buttons are selected by the consumer to indicate whether or not the consumer wishes to receive email or promotional flyers from the bank.

In an alternate embodiment as depicted onFIG. 4, a financial enterprise/clearing agent8can access directly a merchant's database server9using authentication services34. The financial enterprise/clearing agent8can access the consumer's profile16stored on the merchant database server and then use that profile to access the CDS7for any business transaction conducted with the merchants using financial information managed by financial enterprise/clearing agent8. The consumer's profile16is a merchant sub-set of consumer data provided by the CDS from the central information account30belonging to this said consumer. In a specific example, a consumer2registered with the CDS7during a session with a merchant database server9for purchasing a product from a specific merchant would get financial authorization from a financial enterprise/clearing agent8, and then the consumer details would be provided to the a financial enterprise/clearing agent8by the merchant database server9at the time of purchase or at the time of other business transaction.

In the system illustrated inFIG. 5is similar toFIG. 1with the integration of Data Storage Card/Smart Card1and is a high level exemplary operating environment implementing various methods of the present invention. A consumer data storage card or smart card device1referred herein as “smart card device” may comprise a card display12, an integrated circuit computer17and the like. This smart card device1and other types of consumer devices3including PDA, cell phone and laptop will be apparent to one of ordinary skill in the art. For convenience, the following g explanation will be made with reference to a smart card device1. The smart card device has means to connect to the network32using network devices known in the art. Generically, but, unless otherwise indicated, it will be understood that the principles and concepts described will also encompass wired or wireless devices, as client device3illustrated inFIG. 1. Moreover, although exemplary embodiments will be described herein in the context of the Internet or a web-based environment, it will be appreciated that the various principles and methods of operation will be applicable or may be practiced in other environments as well. The data storage card/smart card device1is able to communicate with the central data7and input or receive information from the associated central information account30after authentication using authentication services34. In particular the data storage card/smart card I is able input cryptographic keys and other customer data into the central information account30, while receiving merchant's data6through the central data server7.

Those skilled in the art will appreciate that the illustration and discussion of exemplary embodiments with reference toFIG. 5is provided as a generalized example only. Specific details regarding data formats and network communication protocols have been omitted, as such details are well known in the art. Furthermore, the present invention is not intended to be limited to the use of any particular data formats or protocols. Any existing or future formats or protocols may be used without departing from the spirit and scope of the invention. Furthermore, many network components were not shown or discussed with reference toFIG. 5, such as gateways, routers, hubs, switches, firewalls, DNS servers, authentication servers, certificate authorities, and the like. The functions and roles of such network components are also well known in the art and need not be described in detail herein.

Although the present invention has been described in detail for purpose of illustration, it is understood that such detail is solely for that purpose, and variations can be made therein by those skilled in the art without departing from the scope of the invention. The preceding descriptions of the operations of the present invention are merely illustrative. In various embodiments of the disclosed inventions operational steps may be added, eliminated, performed in parallel or performed in a differing order. The apparatus and process of the present invention is defined by the following claims.