WO2001077975A1

WO2001077975A1 - Automated self-service forms transaction service

Info

Publication number: WO2001077975A1
Application number: PCT/US2001/008910
Authority: WO
Inventors: James H. Wolfston; Michael Hitchcock
Original assignee: Collegenet, Inc.
Priority date: 2000-04-06
Filing date: 2001-03-20
Publication date: 2001-10-18
Also published as: AU2001247609A1

Abstract

An automated forms transactions service is provided by, for example, an application service provider (ASP) (18) so that many Users (22), such as individuals, small businesses or organizations, can set-up and conduct automated forms or other electronic commerce with their Customers (24) over a global computer network (10) such as the Internet. In one implementation, the ASP (18) hosts a server computer that is accessible via the Internet (10). The Users (22) access a form template from the server (12) to create automated transaction forms for collecting information needed to effect automated forms transactions. The transaction service ASP (18) obtains transaction information from automated transaction forms that are completed by Customers (24). The ASP (18) transmits to the Users (12) the customer identifying information and product or service selections made by Customers (24) to process the automated forms transaction, and the ASP (18) transmits customer financial information (e.g., credit card or other electronic financial information) to a financial institution.

Description

Automated Self-Service Forms Transaction Service

Field of the Invention

The present invention relates to electronic commerce as provided over a global computer network and, in particular, to an automated forms transaction service that provides hosted registration services for multiple users.

Background and Summary of the Invention

Electronic commerce is all the rage. Large businesses and technologically sophisticated businesses are quickly developing electronic commerce computer network sites that are accessible by the many computer users with access to the global computer network, commonly called the Internet.

While the development of basic Internet sites has been greatly simplified, developing and maintaining an electronic commerce computer network site requires technological sophistication. In addition to obtaining the computer facilities or services required to host such a site, significant programming and financial arrangements are required to build and maintain even the simplest electronic commerce site.

An electronic commerce site will typically require complex security network systems, as well as one or more databases to track and organize customer registration information, the underlying financial transaction information, etc. In addition, complex and expensive arrangements and coordination with financial institutions are required to execute the transactions. The burden and expense of constructing these components are daunting for most businesses and organizations.

An ad hoc group (e.g., a non-profit group) or an extra curricular academic organization offering a service or activity would typically be unable to establish a network site that could support automated forms with or without related financial transactions. Examples of such groups includes friends organizing an informal golf tournament, an extra-curricular high school drama club selling tickets to a play, collecting sign-ups and fees for a ski trip, etc. The difficulty in implementing electronic commerce transactions over the Internet contrasts with the ease by which information can be disseminated over the Internet. While many small groups and businesses can readily provide on the Internet information about services or even goods that they offer, the complexity of effecting financial transactions limits the ability of such organizations to conduct online registration and electronic commerce.

The present invention provides an automated forms transaction service by which Users, such as individuals, small businesses, or organizations, etc. can use a global computer network such as the Internet to set-up and conduct electronic commerce with their Customers over such a network. For example, the automated forms transaction service may be provided by an application service provider (ASP) that provides the service to many Users.

In one implementation, the ASP hosts a server computer that is accessible via the Internet. The Users access a self-service form template from the server to create online registration transaction forms for collecting information from User's Customers needed to effect online registration transactions. The online registration transaction forms would typically include multiple information fields including: product or service selection fields by which the Customer selects or identifies goods or services to be purchased; customer identification fields by which the Customer provides identifying information such as name, address, email address, etc.; customer billing fields by which the Customer provides financial information (e.g., credit card information or other information suited to electronic transactions); etc.

The transaction service ASP obtains transaction information from online registration transaction forms that are completed by Customers. The ASP transmits to the Users the customer identifying information and the product or service selections made by Customers so that the User can process the online registration transaction. The ASP transmits the customer financial information (e.g., credit card or other electronic financial information) to a financial institution such as a bank for settlement. The ASP makes a financial receipts transfer to each User according to settlements obtained from the financial institution for transactions between the Users and Customers. The present invention provides an automated forms transaction service and method by which an application service provider can host automated forms transactions for multiple Users. This service and method can allow many individuals, small businesses or other organizations to set-up and conduct online registration, for example, without incurring the major expense of establishing their own automated forms (e.g., electronic commerce) transaction capabilities.

Additional objects and advantages of the present invention will be apparent from the detailed description of the preferred embodiment thereof, which proceeds with reference to the accompanying drawings. Brief Description of the Drawings

Fig. 1 is a block diagram of a computer system that may be used to implement the present invention.

Fig. 2 is a flow diagram of a user-side automated forms transaction service set-up method by which a User arranges for an automated forms transaction service to be provided by an application service provider.

Fig. 3 is a diagram of an exemplary automated form template from which a User creates a customized automated form.

Fig. 4 is a flow diagram of an application service provider automated forms transaction service set-up method by which an application service provider provides Users with automated forms transaction capabilities.

Fig. 5 is a flow diagram of a transaction method for an automated forms transaction service.

Detailed Description of Preferred Embodiments

FIG. 1 illustrates a computer network 10, such as the worldwide public computer network called the Internet, with multiple client computers 12 and 14 that communicate with a server 16. In an exemplary implementation, each of client computers 12 and 14 is a personal computer running commercially available network browser software, such as Netscape Navigator from Netscape Corporation or Internet Explorer from Microsoft Corporation. Server 16 is a computer that provides services or information to client computers 12 and 14. Server 16 runs network server software that coordinates communications with client computers 12 and 14. For example, information transferred between client computers 12 and 14 and server 16 are formatted in a hypertext mark-up language (HTML) and can include text, programs, graphics, video, and audio portions, as is known in the art. In one implementation, server 16 is operated by an application service provider (ASP) 18 and is connected to secure data storage database 20. It will be appreciated that although illustrated as a single computer, server 16 and secure data storage 20 may include multiple server computers and data storage units that may be located together or at different locations.

ASP 18 provides an online or automated forms transaction service by which operators of user clients 12, referred to as Users 22, may establish automated forms or other electronic commerce transaction capabilities to offer goods or services to the operators of customer clients 16. Users 22 may establish the automated forms capabilities on behalf of themselves individually, or other entities such as businesses, organizations, etc., to offer goods or services to their customers. For reference purposes, both the operators of user clients 12 and any entities they act on behalf of are referred to interchangeably as Users 22.

Accordingly, ASP 18 is separate from Users 22 and, typically, is a vendor of an automated forms transaction service that is provided to Users 22.

The operators of customer clients 14, referred to as Customers 24, access the automated forms transaction capabilities of Users 22 on behalf of themselves, or other entities such as businesses, organizations, etc., to purchase goods or services from Users 22. The operators of customer clients 14 and any entities they act on behalf of are referred to interchangeably as Customers 24. Customers 24 are typically separate entities from ASP18 and Users 22.

In one implementation, server 16 executes or runs a forms engine of the type described in U.S. Patent Application No. 09/325,533, which is assigned to the assignee of the present invention. As described below, Users 22 are provided one or more form templates from which to create in a self-service manner online or automated transaction forms for collecting information needed to effect online registration or other electronic commerce transactions. The automated transaction forms would typically include multiple information fields including: product or service selection fields by which the Customer 24 selects or identifies goods or services to be purchased; customer identification fields by which the Customer 24 provides identifying information such as name, address, email address, etc.; customer billing fields by which the Customer 24 provides financial information (e.g., credit card information or other information suited to electronic transactions); shipping fields- by which the Customer 24 indicates where goods are to be sent or services provided; etc. In one implementation, a User 22 creates an automated transaction form from, or by selecting from, one or more predefined form templates that are provided from server 16 by ASP 18. Each form created by a User 22 is hosted on server 16 by ASP 18 at a unique network address such as a Uniform Resource Locator (URL). The automated transaction forms are accessed by Customers 24 to effect a purchase of goods or services offered by the User 22.

In some implementations, a User 22 might have a relatively simple network site that describes the goods or services being offered. The network site could include a graphic control button or link by which a Customer 24 could purchase the goods or services. The graphic control button or link could transfer or link the Customer 24 to the unique network address of the User's automated transaction form on server 16. The Customer 24 may be linked transparently to server 16 and the automated form of a User 22, as within an HTML frame of the network site of the User 22, with no outward indication of having left that network site. In another implementation, a Customer 24 may be explicitly informed of being connected to another network site to effect the automated form transaction.

In the simplest implementation, a User 22 might have no network site other than the automated transaction form that is hosted by ASP 18 on server 16.

Customers 24 of such a User 22 may be directed to the network address (e.g.,

URL) of that automated transaction form by information other than a network site, such as printed or other advertising.

Fig. 2 is a flow diagram of a user-side automated forms transaction service set-up method 50 by which a User 22 arranges for an automated forms transaction service to be provided by ASP 18.

Process block 52 indicates that a User 22 accesses via the global computer network an automated forms transaction service network portal of automated forms transaction service ASP 18.

Process block 54 indicates that User 22 is prompted to and registers with an automated forms transaction service at the automated forms transaction service network portal. Registration may include, for example, the User 22 establishing a user name and password for secure access to the automated forms transaction service network portal and providing User-identifying information to ASP 18 according to information fields rendered on user client 12 by server 16. The User-identifying information may include the name of the User individual, the name of any business or other organization or entity on behalf of which the individual is acting, the address of the individual, business or other entity, a telephone number, an email address, and a User network site address, if any. In some implementations, registration of User 22 may be performed at other times in method 50.

Process block 56 indicates that User 22 is prompted to and creates, selects, or specifies at least one automated transaction form. In one implementation, User 22 creates the automated transaction form from, or by selecting from, one or more predefined form templates that are provided by ASP 18 and hosted on server 16.

Fig. 3 is a diagram of an exemplary automated form template 60, as rendered on a display screen of a user client 12, from which User 22 creates a customized automated form. Template 60 includes a field 62 in which User 22 designates one or more products or services to be selectable by a Customer 24, and a field 64 in which User 22 designates the prices of the one or more products or services to be selectable by a Customer 24. Form template 60 is of a simplified type in that other data fields relating to standard online or automated transaction information from or about a Customer 24 are provided as default fields. Such default fields may include, for example, the name, shipping address, billing address, and financial information (e.g., credit card, debit account, or other electronic commence financial information) of the Customer 24. As a result, creation of an online or automated transaction form by User 22 is simplified by reducing the numbers of fields that must be manually specified by User 22. It will be appreciated that in other implementations, form templates could allow User 22 to specify any of such fields, as well as creating additional custom data fields. Moreover, form templates could optionally allow User 22 to select one of multiple selectable appearances for the automated transaction forms when they are rendered for Customers 24. In some implementations, Users 22 may be able to include the name or other indicia (e.g., trademarks) for their businesses or organizations on the automated transaction forms. Creation of the automated transaction forms may include the option for Users 22 to preview them before concluding their creation. Process block 70 indicates that User 22 is prompted for and provides data transfer information, including a data transfer destination and a data transfer format, for transferring to User 22 information that ASP 18 obtains from Customers 24 who complete the automated transaction forms. Typically, the data transfer destination will be a location on the global computer network and the data transfer format may be any of a variety of available database or other structured data formats.

Process block 72 indicates that User 22 is prompted for and provides financial receipts transfer information to ASP 18 according to information fields rendered on user client 12 by server 16. The financial receipts transfer information may include, for example, bank account and bank routing information by which ASP 18 can transfer to User 22 funds or other financial instruments that are received from Customers 24. In some implementations, ASP 18 may collect a service charge for financial receipts transferred to User 22. For example, the service charge may be a percentage of the financial receipts that are transferred to User 22.

Process block 74 indicates that User 22 is provided a network link to a unique network address (e.g., URL) where the automated transaction form is to be located on server 16. User 22 may explicitly direct Customers 24 to the unique network address of the automated transaction form or may link to the form from a network site of the User 22. In some implementations, User 22 may link to the automated transaction form within a frame of network site of the User 22.

Process block 76 indicates that User 16 is prompted for and provides financial billing information (e.g., credit card, debit account, or other electronic commence financial information) to be charged a form activation fee to activate each automated transaction form to be accessed by Customers 24.

Fig. 4 is a flow diagram of an ASP automated forms transaction service set-up method 100 by which an ASP 18 provides Users 22 with automated forms transaction capabilities over a computer network. Process block 102 indicates that ASP 18 provides and maintains an automated forms transaction service network site or portal. For example, such a portal may be maintained on server 16 with access to it available from computer network 10, such as the global computer network called the Internet. Process block 104 indicates that ASP 18 provides one or more automated transaction form templates with which User 22 can create, select, or specify ah automated transaction form to be used by Customers 24. In one implementation, the automated transaction form template may be of the type described above with reference to Fig. 3. In other implementations, the automated transaction form template could allow all customer transaction information, other than financial information, to be specified by User 22. The financial information fields would typically be specified by ASP 18 so that it could effect financial settlement with a financial institution (e.g., a bank).

Process block 106 indicates that ASP 18 obtains and stores in a database 20 an automated transaction form that is specified by User 22 from an automated transaction form template.

Process block 108 indicates that ASP 18 obtains and stores in a database 20 data transfer information, including a data transfer destination and a data transfer format, for transferring to User 22 information obtained from Customers 24 who complete automated transaction forms. Typically, the data transfer destination will be a network address that is accessible via the global computer network 10.

Process block 110 indicates that ASP 18 obtains and stores in a database 20 financial receipts transfer information according to which ASP 18 can transfer to User 22 funds or other financial instruments that are received from Customers 24.

Process block 112 indicates that ASP collects from User 22 a form activation fee for activating the automated form of User 22. For example, ASP 18 may collect the form activation fee by obtaining from User 22 financial information, such as credit card, debit account, or other electronic commerce financial information. Process block 114 indicates that ASP 18 assigns a unique network address (e.g., URL) for the automated transaction form of User 22 and notifies User 22 of the network address.

Process block 116 indicates that ASP 18 makes the automated transaction form of the User 22 available to the global computer network 10.

Fig. 5 is a flow diagram of a transaction method 130 for an automated forms transaction service in which an ASP 18 handles automated forms or other electronic commerce transactions with Customers 24 on behalf of Users 22.

Process block 132 indicates that a User 22 directs Customers 24 to its automated transaction form at a network address hosted by ASP 18. User 22 may direct Customers 24 to the automated forms transaction form via a network link at an originating network site, which link would access the automated transaction form for completion by the Customer 24. The originating network site from which the automated transaction form is linked may be maintained by the User 22 or another entity. The accessing of or link to the automated transaction form may be rendered at the customer client 14 as a frame that appears to be provided by the originating network site or may appear as a distinct network transaction site. Alternatively, User 22 may direct Customers 24 to the automated transaction form by otherwise distributing the unique network address of the automated transaction form, such as by print or other advertising, etc.

Process block 134 indicates that a Customer 24 completes and submits an automated transaction form to effect a transaction with User 22. In completing and submitting the automated transaction form, the Customer 24 provides customer transaction information that includes his name, shipping address, billing address, and financial information (e.g., credit card, debit account, or other electronic commerce financial information), as well as specifying the goods or services and associated prices being ordered or purchased.

Process block 136 indicates that ASP 18 stores the customer transaction information in database 20. Process block 138 indicates that ASP 18 transfers the customer transaction information to the data transfer destination and in the data transfer format specified by User 22. In one implementation, the customer transaction information is transferred periodically in batches (e.g., daily), commonly resulting in customer transaction information from multiple transactions being transferred in each batch. Also, the customer transaction information that is transferred to the data transfer destination typically would not include the financial information that is provided by Customers 24. Process block 140 indicates that ASP 18 submits the financial information provided by Customers 24 to a financial institution (e.g., a bank) for settlement. Settlement includes conventional processing of financial information, such as credit card information, to effect a financial transfer from, or debit of an account of, Customer 24. Settlement may also include processing of financial information other than credit cards, such as "electronic money" and related financial instruments that are under development.

Process block 142 indicates that ASP 18 makes a financial receipts transfer to User 22 upon confirmed settlement of the financial information submitted to the financial institution. The financial receipts transfer effects a funds transfer from ASP 18 to User 22. In one implementation, the financial receipts transfer to User 22 is made subject to a transaction service charge made by ASP 18.

One aspect of the implementations described above is that ASP 18 provides processing and settlement of financial information on behalf of Users 22. However, some transactions between Users and Customers might not include remuneration and so might not require processing and settlement of financial information by ASP 18. It will be appreciated, however, that the present invention could be utilized for transactions that do not include remuneration. For such transactions, Users 22 could define a transaction form from a transaction form template that does not obtain financial information from Customers 24.

Having described and illustrated the principles of our invention with reference to an illustrated embodiment, it will be recognized that the illustrated embodiment can be modified in arrangement and detail without departing from such principles. It should be understood that the programs, processes, or methods described herein are not related or limited to any particular type of computer apparatus, unless indicated otherwise. Various types of general purpose or specialized computer apparatus may be used with or perform operations in accordance with the teachings described herein. Elements of the illustrated embodiment shown in software may be implemented in hardware and vice versa.

In view of the many possible embodiments to which the principles of our invention may be applied, it should be recognized that the detailed embodiments are illustrative only and should not be taken as limiting the scope of our invention. Rather, we claim as our invention all such embodiments as may come within the scope and spirit of the following claims and equivalents thereto.

Claims

1. A computer-implemented automated forms transaction service method for effecting an automated form transaction on a global computer network on behalf of plural Users offering goods or services to plural Customers, comprising: hosting plural automated transaction forms that are accessible via the global computer network and are defined at least in part by the Users, the automated transaction forms being accessed by Customers to initiate with the Users automated forms transactions relating to goods or services; obtaining from automated transaction forms that are completed by

Customers transaction information that includes customer identifying information, customer financial information, and a specification of a good or service to which the financial transaction relates; and transmitting to the Users the customer identifying information and specifications from automated transaction forms completed by Customers.

2. The method of claim 1 further comprising transmitting the customer financial information to a financial institution for settlement.

3. The method of claim 2 further comprising a financial receipts transfer to each User according to settlements obtained from the financial institution for transactions between the User and a Customer.

4. The method of claim 3 further comprising applying against the financial receipts transfer to the User a transaction service charge for performing the automated forms transaction service method.

5. A computer-implemented automated forms transaction service method for a global computer network, comprising: providing an automated transaction form template that is accessible by a User over the global computer network to create an automated transaction form with which to effect with a Customer an automated forms transaction on the global computer network; obtaining from the User data transfer information and financial receipts transfer information, the data transfer information facilitating a transfer to the User of data obtained from the automated transaction form when it is completed by the Customer and the financial receipts transfer information facilitating a financial receipts transfer to the User according to a financial settlement based upon financial data obtained from the automated transaction form when it is completed by the Customer; a financial receipts transfer to the User according to financial settlements based upon financial information designating a unique network address for the automated transaction form and providing the network address to the User; and posting the automated transaction form at the network address.

6. The method of 5 further comprising obtaining from automated transaction forms that are completed by Customers transaction information that includes customer identifying information, customer financial information, and a specification of a good or service to which the financial transaction relates.

7. The method of claim 6 further comprising providing to the User the customer identifying information and specifications from automated transaction forms completed by Customers.

8. The method of claim 5 further comprising transmitting the customer financial information to a financial institution for settlement.

9. The method of claim 8 further comprising a financial receipts transfer to each User according to settlements obtained from the financial institution for transactions between the User and a Customer.

10. The method of claim 8 further comprising not transmitting the financial information to the User.

11 An application service provider automated forms transaction service method by which an application service provider services automated forms transactions conducted between Customers and plural Users over a global computer network, comprising: processing on behalf of the Users automated transaction forms having customer transaction information for effecting financial transactions between the Customers and the Users, the customer transaction information in each form including transaction data and financial data; transmitting the transaction data to the Users; transmitting the financial data to a financial institution to effect financial settlement for the financial transactions on behalf of the Users; and transmitting financial receipts information to the User to effect a financial transfer to the User according to the financial data.

12. The method of claim 11 further comprising maintaining the automated transaction forms of the plural Users at a network site accessible from the global computer network.

13. The method of claim 12 further comprising obtaining from the Users a form activation fee for each automated transaction form that is maintained at the network site.

14. The method of claim 13 further comprising obtaining from the Users a transaction fee for each transaction for which financial receipts information is transmitted to the User.

15. The method of claim 11 further comprising obtaining from the Users a transaction fee for each transaction for which financial receipts information is transmitted to the User.

16. A business method, comprising: hosting at a network site that is accessible to a global computer network automated transaction forms by which plural Customers submit transaction and financial information to effect financial transactions relating to goods or services offered by the Users, each automated transaction form being defined at least in part by one of the Users; transmitting the transaction data to the Users without effecting any transfer of the goods or services being offered by the Users; transmitting the financial data to a financial institution to effect financial settlement for the financial transactions on behalf of the Users; and transmitting financial receipts information to the User to effect a financial transfer to the User according to the financial data.