U.S. Patent 7,853,515

Title:  Electronic bond and guaranty process and business method

U.S. Patent 7,853,515
Issue Date:  December 14, 2010


What is claimed is:

1. A method of conducting an on-line auction for a seller of goods, comprising: hosting an on-line auction through a computer of a client-server environment; allowing the seller of the on-line auction to accept bids from a bidder through the computer of a client-server environment; allowing the seller of the on-line auction to reject bids from another bidder through the computer of a client-server environment; and providing a guarantee for the on-line auction through the computer of a client-server environment with a level of the guarantee being determined based on historical data recorded for a participant of the on-line auction.

2. The method of claim 1, wherein the providing a guarantee includes allowing the seller to reject bids from the another bidder based upon the determination of whether payment by the another bidder for the on-line auction can be guaranteed.

3. A method for conducting an on-line auction, comprising: providing a server on which an on-line auction is hosted; enabling a seller to list a pending on-line auction on the server; enabling a bidder to bid on the pending on-line auction via a web browser executing on a client device; providing a link upon completion of the on-line auction that enables a winning bidder to rate an experience with respect to the completed on-line auction, the link taking the web browser executing on the client device of the winning bidder to a location where the experience can be rated; and reviewing the rated experience to determine whether a guarantee will be offered in a subsequent auction by the seller.

4. The method of claim 3, wherein reviewing the rated experience comprises determining whether a preferred guarantee will be offered to the winning bidder.

5. A method for conducting an on-line auction, comprising: hosting an on-line auction through a computer of a client-server environment; providing a guarantee for the on-line auction through the computer of a client-server environment with a level of the guarantee being determined based on historical data recorded for a participant of the on-line auction.

6. A method for conducting on-line auctions, comprising: hosting a first on-line auction through a computer of a client-server environment; recording an evaluation parameter of a seller of the first on-line auction; hosting a second on-line auction including the seller through a computer of a client-server environment; and providing a guarantee for the second on-line auction with a level of the guarantee being based on historical data recorded for the seller from the first on-line auction.

7. A method for conducting on-line auctions, comprising: hosting a first on-line auction through a computer of a client-server environment; recording an evaluation parameter of a seller of the first on-line auction; hosting a second on-line auction including the seller through a computer of a client-server environment; and determining whether to offer a guarantee for the second on-line auction based on historical data recorded for the seller including the first on-line auction.



(1) Field of Invention

The present invention relates to the field of electronic commerce conducted in a client-server network environment, typically, the World Wide Web. Specifically, the invention relates to issuing performance bonds and guaranties over the Internet, as in cases where the party to be bonded is an Internet seller or bidder in an on-line auction environment.

(2) Background Art

The growth of electronic commerce has been accompanied by new risks to consumers. Enabling long-distance, anonymous transactions between individuals, user-to-user auction sites on the World Wide Web have given rise to severe problems of fraud and intellectual property piracy. These activities are also common on sites operated by fraudulent sellers themselves.

Various solutions have been attempted. Electronic escrow services, where a third party is injected between buyer and seller to verify that a quid pro quo exchange occurs, represent one proposed solution. But such services, such as escrow.com, have proven to be of limited value and have gained only limited market acceptance, mainly because escrow services (a) create unavoidable delays in effecting the exchange and (b) add significant costs to every transaction, even when the exchange goes well. Moreover, since escrow transactions must be arranged on an individual basis, the use of an on-line escrow approach is simply not feasible for high-volume sellers.

Another problem plaguing online auctions today is that of “deadbeat bidders,” bidders who win an auction but never pay for the item purchased. Deadbeat bidders not only cost the seller a sale to other bidders who would have honored their contractual obligation to pay, but deadbeat bidders also cause sellers out-of-pocket expenses, since the auction company’s commission typically must be paid by the seller whether or not she receives payment from the winning bidder. Escrow does not address the problem of deadbeat bidders, nor do electronic payment services, such as PayPal.

What is needed is a solution that effectively eliminates the risk of buying and selling over the Internet while adding little or no transactional cost in terms of time and money.

Performance bonding is a known means of legally shifting the risk of a given loss, a performance bond being a contractual agreement between the surety, the principal and the obligee whereby the surety agrees to protect the obligee if the principal defaults in performing the principal’s contractual obligations. Black’s Law Dictionary, 6.sup.th Ed.

A guaranty is similar in purpose to a bond. A guaranty is a collateral agreement for performance of another’s undertaking in which the guarantor agrees to satisfy the debt of another (the debtor), only if and when the debtor fails to repay (secondarily liable).

Collateral is property which is pledged as security for the satisfaction of a debt or performance of a principal obligation.

Letters of credit are a known means of facilitating transactions, whereby a bank or other institution agrees to honor demands for payment made in compliance with specified conditions.

A penal sum is a monetary sum agreed upon in a bond to be forfeited if the condition of the bond is not fulfilled. In this document, the term “coverage limit” may be used interchangeably with penal sum.

Automatic means of adding an electronic image and accompanying text to an Internet auction listing or other World Wide Web page is also known. For example, the company known as Honesty.com enables Internet auction sellers to visit the Honesty.com Web site, enter an auction site name, auction number, email address and password, and then have the Honesty.com logo and a unique “hit counter” added to the given auction listing automatically.

Means of searching the Internet and World Wide Web for infringing uses of digital images and text is also known, such as the automated search technology designed by iParadigms for plagiarism.org or the techniques known as “digital watermarking” or “fingerprinting.”

Merchant card services enabling Visa or MasterCard transactions in real-time over the Internet are known.


The disclosed invention provides an automated, computer-implemented, network-based method by which Internet sellers can obtain either a performance bond or a guaranty in real time and immediately deploy a unique seal evidencing this contractual protection for buyers. The bond and the guaranty are contractual vehicles which serve to indemnify buyers against the risk of non-performance or nonconforming deliveries by sellers. Bonds for bidders, which assure sellers of payment when a bonded bidder wins an auction, are also disclosed.

In the preferred embodiment, the potential bond applicant first visits the Web site of the bond/guaranty company (“Company”) and registers. The registered user then applies for either (1) a general suretyship performance bond which will offer security to purchasers in all of a seller’s eligible Internet transactions up to the penal sum for all claims in aggregate or (2) a guaranty for a specific single Internet auction.

Upon submission, the seller’s application is processed automatically through evaluation software with reference to various databases, performing automated analysis of the risk-worthiness of the user, the authenticity of the information submitted, and other checks. The seller then receives immediate approval or rejection of the application. If the application is accepted, the terms and price of the bond or guaranty are quoted to the applicant. The seller then pays by credit card, and a unique seal which identifies the newly formed bond or guaranty is displayed to the applicant. This seal can be automatically added to certain auction listings by CGI script, or the seller can manually add the HTML code referencing this logo to her HTML documents, whether these are hosted on her own site or a third party auction site.

In the preferred embodiment, potential buyers activate their coverage under the seller’s bond or guaranty by “clicking through” a link in the seal to a page on the bonding/guaranty company site and submitting the information requested therein. Confirmation of coverage is then sent to the potential buyer by email. Alternately, coverage can be automatic for anyone who buys from a bonded seller, requiring no activation by the buyer.

If a seller defaults, the buyer submits a claim, including confirmation of coverage activation, if required. The Company evaluates the claim and reimburses the buyer if warranted. Thereafter, the Company takes appropriate action for reimbursement from the seller, such as charging the seller’s credit card.

In this way, the present invention offers a more effective, less expensive, infinitely scalable and virtually “invisible” solution to the problem of making the Internet a secure marketplace.

Various security measures for reducing piracy of the seal or otherwise misrepresenting a seller’s status are disclosed. Various revenue models are also disclosed which allow shifting of cost to the most efficient payer. A seal which includes a “bond margin” counter is also disclosed.

In one alternative embodiment, the Company’s risk is significantly reduced through a process by which the bond applicant’s credit card used for sequential preauthorizations that serve to reserve a portion of the funds available in the given account as collateral. Other forms of collateral, such as an irrevocable letter of credit, can be substituted by special arrangement with the Company.

In another alternative embodiment, the Company and a third party auction site operator work collaboratively through real-time data sharing so as to enable the third party auction site operator to serve the Company’s seal in portions of the auction site under the exclusive control of the auction site operator.

Another significant alternative embodiment provides for the bonding of bidders as well as sellers. In this embodiment, bidders can open a deposit account with the Company that allows instantaneous payment of a bonded seller at the close of an auction.


FIG. 1 depicts the basic steps by which an exchange between an Internet seller and buyer is transacted.

FIG. 2A depicts an exchange between an Internet seller and buyer wherein the present invention is used to provide a bond or guaranty.

FIG. 2B presents a flow chart depicting a high level, general overview of the steps involved in guaranty contract formation and claims resolution under the present invention.

FIG. 3, included for comparison, depicts the basic steps by which an exchange between an Internet seller and buyer is transacted through an escrow service.

FIG. 4A depicts a flow chart of a typical site registration process.

FIG. 4B depicts a uniquely numbered identifying Seal which signifies that the given Internet seller is bonded; this Seal is to be displayed in HTML documents wherein sale is offered.

FIG. 4C depicts a Seal signifying that the given Internet auction is guaranteed.

FIG. 5 presents a high level flow chart documenting the process by which an application is submitted, evaluated, and processed and the resulting bond or guaranty contract, if any, formed.

FIG. 6 depicts a flow chart documenting the bond application evaluation subprocess.

FIG. 7 depicts a flow chart documenting the guaranty application evaluation subprocess.

FIG. 8 depicts a flow chart documenting the process of “flagging” an individual.

FIG. 9 depicts a flow chart documenting the process by which a registered user’s Experience Rating is assigned.

FIG. 10 depicts an example Verification/Activation Page, to which potential purchasers or bidders “click-through” in order to verify that the given seller is bonded or the given auction guaranteed and to activate their right to protection under the given bond or guaranty.

FIG. 11 depicts a flow chart documenting the process by which a potential bidder activates her coverage under a bond or guaranty.

FIG. 12A depicts a flow chart detailing the process by which a claim is made and resolved.

FIG. 12B depicts a flow chart detailing the claims payment and collection process.

FIG. 12C depicts a flow chart detailing the claim dispute resolution process.

FIG. 13 depicts a high-level map of the databases used in the present invention, identifying the key relationships between them.

FIGS. 14A through 14D depict different revenue models to which the current invention can be applied.

FIG. 15 depicts a flow chart detailing the process by which a bond that makes use of preauthorized charges to a credit card as collateral is put into effect and maintained.

FIG. 16A presents a timeline illustrating the relationship of a bond to the Company’s risk exposure as a result of that bond.

FIG. 16B presents another timeline illustrating an example of the relationship between the time period during which a bond is effective and the time period during which a claim against that bond can be made.

FIG. 17A depicts a map of the database relationship that enables co-operation of and data sharing by an auction site and a bonding company.

FIG. 17B depicts an excerpt from an HTML page that is an auction listing, wherein a special seal evidencing a bond is displayed.

FIG. 18 depicts a sequence of five moments in time demonstrating the effects of different events on the margin of bond coverage over and above potential claims thereon.

FIG. 19 depicts a flowchart documenting the process by which a bidder is bonded and a bidder deposit account is created.

FIG. 20 depicts a flowchart that ties together previous discussion by illustrating the many different results that can occur after the closing of an auction in the context of potential bonding of both sellers and bidders.


So as to highlight the key components of the present invention, the following detailed description uses the example of an Internet auction as a paradigmatic case of electronic commerce. It is known to one ordinarily skilled in the art that Internet auctions are but a single form of electronic commerce and that the present invention applies to other forms.

It is also known that Internet sellers represent but a single class of bond/guaranty purchasers and that the present invention can be readily applied to serve any number of “off-line” markets through the collateral reservation process and others described below.

It is also known to a person of ordinary skill in the art that the Internet represents a client-server environment. Thus, when an Internet buyer or seller is mentioned in this document, it is understood that, typically, she is accessing an HTML document hosted on a server by sending an HTTP request from her client computer, with Web browser software properly installed, to the server computer through the Internet. HTTP server, firewall, data storage and processor hardware configurations are known, and server software is assumed to be properly installed on this hardware.

All steps in the processes described with respect to the present invention are executed in software installed on the Company’s hardware unless it is expressly stated that the step is taken by a human: staff member, applicant, or other person. The software to execute these steps is known to one of ordinary skill in the art. Several databases, each of which contain several records with at least one data field per record, are depicted. Some data fields serve as repositories for information as it is input by a human; other fields contain values which are assigned by a formula which references other fields as factors. As is plain to one skilled in the art, the databases are relational, and most relationships are many-to-many.

The present invention contemplates a Web site (the “Site”) which is operated by a bonding/guaranty company (the “Company”), and, in certain embodiments, a Web site operated by an auction company (“Auctioneer”).

By way of introduction, an example of the process by which a typical user-to-user exchange occurs via Internet auction is depicted in FIG. 1. The Seller 101 creates and uploads to the auction site’s server an HTML auction listing 102 which is then viewed by potential bidders 103. The eventual high bidder 104 places her bid through the Web site where the auction listing appears 102. At the close of the auction, the Seller 101 sends an email to the Buyer 104 detailing her payment address. Buyer 104 then sends payment to Seller 101, also conveying her shipping address. Buyer 101 then ships item.

FIG. 2A depicts a similar user-to-user exchange. This time, however, the Seller 201 purchases a guaranty or bond from the Company 205 per the present invention before uploading the auction listing 202. The transaction is otherwise similar to that depicted in FIG. 1, except that, when bidding on the auction, the Buyer 204 also activates her right to protection under the bond or guaranty by clicking on the Seal 410 or 420 which appears in bonded or guaranteed auction listings.

FIG. 2B depicts a high-level flow chart of the guaranty process, which is essentially similar to that used in bonding. Each of the key steps therein is covered in greater detail in subsequent discussion.

Included for comparison, FIG. 3 demonstrates that using an escrow service adds several more steps to the transaction than the present invention requires.

FIG. 4A depicts the basic steps of registration with the Company Site. For reference in later discussion, FIGS. 4B and 4C depict the Seal which plays a key role in the present invention. This Seal (410 for bonds and 420 for guaranties) includes an image (411, 421), preferably a .gif or .jpg image, and text (412, 422) which are applied to a seller’s auction listing or other HTML document to notify the public of the bond or guaranty. The means by which these Seals (410 and 420) are created and added to HTML documents so as to be viewable by the public are discussed below. When the hyperlink in the text (412, 422) is clicked, a new browser window is spawned, and the Bond Activation/Verification Page (FIG. 10) discussed below is displayed therein. A second hyperlink (“Contact Us”) appears in this text (412, 422) and links to a form on the Site, the Reports Page, which enables submission of a report of suspicious activity.

FIG. 5 illustrates a flow diagram documenting the process by which a bond or guaranty is applied for, evaluated, legally bound and deployed. Sub-processes are broken out in more detail in later figures.

Having registered with the Site, the registered user logs in 501, views information about bonds and guaranties, and selects whether she wants to apply for a bond or guaranty 502. If the bond choice is selected, the User selects the desired bond duration 503 and penal sum from a menu and submits information requested in a variety of data fields 504. The requested information includes fields such as: a1. Principal type of merchandise or services sold, which is selected from a menu including computer software, hardware, clothing, music and video media, and other merchandise categories a2. Percentage of sales derived from the category chosen in a1 a3. Secondary type of merchandise (same menu) a4. Percentage of sales derived from the category chosen in a3 b. Expected total revenue from Internet sales b2. Last year’s total revenue from Internet sales c. Average# of transactions d. User’s Social Security# e. User’s bank 1 f. Bank account number at bank 1 g. User’s bank 2 h. Bank account number at bank 2 i. User’s employer j. Employer’s address k. Employer’s city l. Employer’s state m. Employer’s postal code n. Employer’s country o. Employer’s phone p. Employer’s fax q. Employer’s email r. Employer’s web site s. Credit Reference 1 (credit card, other loan institution) t. Account number for Reference 1 u. Credit Ref 2 v. Account number for Credit Ref 2 w. Annual income x. All email accounts used by seller (repeating field) y. All web sites (by URL) used by seller (auction sites, personal sites, etc.) (repeating field) z. Credit card to be charged–type (MC/Visa/AmEx) aa. Card number ab. Card exp. date ac. Name on card ad. Billing zip ae. Answers to various questions such as “Do you sell home-made copies of commercial software?” are also requested af. Previous bond number, if any ag. Password for the previous bond, if any

Typically, the more credit references and dependable identifying information the user provides, the more likely she is to be approved for a bond and/or the less expensive that bond will be, as discussed below in reference to FIG. 6, since such information helps to reduce the Company’s risk. If the seller wishes to take advantage of instant payment from bonded bidders’ deposit accounts per the process described in FIG. 19, routing numbers for wire transfers must also be provided.

When the application is submitted, a new record is created 504 in the Applications Database. The application is evaluated 505 per the Automated Bond Application Review Process depicted in FIG. 6. This sub-process returns a result 509: in the case of rejection, the user’s browser is directed back to the selection page 502. Alternately, (arrow not shown) the user can be sent back to the application page 504 to correct noted defects in the application. In the case of approval, the acceptance page is displayed, including a quoted price for the requested bond 511. If the user agrees to purchase at the quoted price 513, the charge to her credit card charge is finalized 515, a new record is created 515 in the Bonds Database 1301, (FIG. 13) a unique Seal 410 is generated automatically and stored on the Site server 517, and the Provisional Bond Contract becomes legally binding 517. The HTML code for the Bond Seal 410 is displayed 517 to the applicant so that she can copy this code and use it in her offers for sale. The HTML referencing the seller’s Seal can also be retrieved later by the seller visiting her account page on the Site.

Alternately, (not depicted graphically) the Company can require that the bonded seller first submit the URL of each page wherein the Seal will be displayed before the HTML code which renders the Seal is made available. Requiring URL submission of each Web page wherein the Seal is to be displayed may enable greater accuracy in Company policing for pirated Seals.

The Provisional Bond Contract is only valid for a specified period of time and is not renewable. It serves primarily to enable instant binding of a bond, a significant benefit to sellers, while not exposing Company to extended risk. After the Provisional Bond is bound 517, a manual review 520 is conducted by Company staff of the bond application, who pull credit reports and review submitted information. If the seller appears credit-worthy, the Staff authorizes issuance of a Formal Bond 523 by entering the result in the bond application and finalizing the review process. The Formal bond then issues prior to the expiration of the Provisional Bond, thereby rendering the latter null and void. The bonded seller is automatically notified of the issuance of the Formal Bond 523 but is not required to take any further action, since supplanting the Provisional Bond with the contractual rights and obligations of the Formal Bond does not change the appearance of the Bond Seal 410. If Staff decides applicant does not merit the Company’s undertaking the obligations of Formal Bond, Staff enters the result in the appropriate field in the bond application record and finalizes the review process. Thereafter, the Provisional Bond expires, and the seller is automatically notified 522. In this case, the Seal image 411, which resides on the Company’s servers, will be automatically replaced with a new image which indicates that the Provisional Bond has expired.

Returning to the top of FIG. 5, if the registered User chooses to apply for a guaranty, the first time she purchases a guaranty, she will be required to enter much of the same information as is required in the bond application 506. Thereafter, subsequent guaranty applications by the same account holder are much shorter so as to be more convenient. The abbreviated guaranty application requests the following information: a. Auction site where item to be guaranteed is listed b. Auction identification number c. Seller’s email address used in that auction listing (used to access the listing) d. Type of merchandise being sold (select from menu) e. Guaranty amount or estimated closing value f. Check box answers to questions such as: “Is all merchandise authentic and authorized for sale?” g. If credit card is already on file, then the User simply authorizes the charge; if credit card is not on file, then User provides credit card information.

While the above fields pertain to a specific auction, the present invention also contemplates a single submission form containing multiple repetitions of the above fields so that several auction guaranty applications can be submitted at one time, which reduces unnecessary re-entering of data that does not change from auction to auction, such as a credit card number, if such is not already stored.

Upon submission, the application is processed 507 according to the Automated Guaranty Application Review Process detailed in FIG. 7. If the application is approved, then the User is prompted to provide her password for the given auction account 510 and email address if the one being used in the given auction is different from the one already provided. This password is never stored anywhere by the Company and therefore must be entered each time an auction is to be guaranteed. This password is used to gain editing access to the specified auction listing so that the Company’s CGI script technology can automatically append the HTML which produces the Seal 420 to the existing HTML of the specified auction listing. If the User is not accepted, her browser is redirected to the begin page 502 or, alternately, back to the Guaranty Application page 506 (arrow not shown) to correct any defects in her application.

Once the password is submitted 510, which also signifies the applicant’s authorization to charge her credit card, a new record is created 512 in the Guaranty Database, a new, unique Guaranty Seal image 421 is created and stored 512 on the Company server, and the CGI script which appends the Seal HTML to the given auction listing is run 512. If the CGI script successfully adds the Guaranty Seal HTML to the specified auction listing, the credit card transaction is finalized 516, the Guaranty Contract is consummated 518, and the confirmation page is displayed 518 in the applicant’s browser, informing her that the Guaranty is active, and the Seal added to the specified auction. If the CGI script fails, the User is re-prompted for her email address and password 510.

FIG. 6 depicts a flow chart documenting the steps of the Automated Bond Application Review Process. Information in newly submitted applications is input into this software process 601, and a result–acceptance with price quote 615 or rejection 613, with or without reasons–is output. In evaluating the application, the software will produce a rejection result 613 if any significant fields are left blank 602 or if any admissions 603 are made in the application that indicate that the given seller is an intellectual property pirate or other illegitimate seller. Next, the contact information provided in the application is checked against the information contained in all the corresponding fields in all records in the Flagged Individuals Database 1303. If a high certainty correlation exists between the contact information provided in the application and that in a Flagged Individual record, such as an identical email address, then the applicant is consider flagged 604 and is rejected 613.

If the application survives the initial cuts, a Risk Exposure Level is assigned 605. This number is the product of a formula which includes several factors, such as: the coverage value being requested (higher revenue sellers will yield greater risk exposure), the types of merchandise, and the number and verifiability of credit references.

Data is checked to determine whether the applicant has previously been bonded by the Company 606. If so, she will already have an Experience Rating, which is determined per the Experience Rating Process depicted in FIG. 9 below. If the applicant has applied in the past, a manual credit review may have already been conducted on that individual and an in-house Credit Rating assigned to her. The Experience Rating, if any, and Credit Rating are factored in with the information contained in the application itself to assign a Risk Worthiness Level 607 or 610 to each application. The Risk Worthiness Level is compared to the Risk Exposure Level 612, and the application is either accepted or denied. If accepted, a credit card preauthorization is performed 609. Provided that the credit card is valid 614, a price quote for the bond is output 615, the sub-process depicted in FIG. 6 ends, and the main process depicted in FIG. 5 resumes 616. If the application is denied, comparison is made between the applicant’s Risk Worthiness Level and that required for shorter potential bond durations and lower penal sums to see whether the given applicant may qualify for a less risky bond 608. If so, then a new bond duration and rate is selected 611 for use in the price quote. If the applicant is not sufficiently risk-worthy even for a reduced risk bond, then rejection 613 is output 616.

FIG. 7 depicts the Automated Guaranty Application Review Process, which is similar to the bond evaluation sub-process. One difference is that the result is strictly binary; there is no option of reducing the amount of coverage in order to guaranty a non-guaranteeable auction. Also, note that in the preferred embodiment, the prices for guaranties are fixed according to the value of the item; thus, a quote is not necessary, simply the outputting of acceptance and confirmation of price. As an alternative embodiment, prices can be set to vary according to the Risk Worthiness Level of the applicant, in which case a quote would be necessary.

FIG. 8 illustrates another supporting process, that by which individuals are flagged. The Flagging Process starts with the discovery of information about a given person 800, through some means other than the filing of a claim, which might be of such a discrediting nature that, if true, the Company would not want to issue bonds or guaranties to that person. Receipt of such information is a “triggering event” 801. For instance, a triggering event could be a notice to the Company by the police reporting an intellectual property pirate.

In a particular alternative embodiment (not depicted graphically), the Company performs intellectual property monitoring searches on the Internet. Each discovery of an instance of piracy would be a triggering event so that searches would, over time, create a database of known pirates, a valuable tool in reducing Company risk exposure.

After the triggering event, the information received is examined manually by staff to determine whether the event can be directly attributed to a specific individual 801. If not, then the triggering event is discarded 808. If so, then the contact information identifying that individual, which may be as little as an email address or may be a full compliment of contact information with the individual’s name, is input by staff for automatic searching against the records in the Registered User Database to see whether the person may be a registered user 802. If the individual involved does indeed appear to be a registered user, then the Experience Rating process 803 depicted in FIG. 10 is followed, and the Flagging Process ends 808.

If the event apparently does not involve a registered user, then a staff member investigates 804 to determine whether the damaging information is credible, whether the contact information associated with the event is correct (contact info need not be complete, just accurate), and whether the magnitude of the event is such that it warrants flagging of this individual 805. If flagging is appropriate, then a new record is created 806 in the Flagged Individuals Database 1303, and all information available on the individual and event are entered in the appropriate fields 807. If flagging is not warranted, then the process ends 808, and the information is discarded.

The Experience Rating Process, depicted in flow chart form in FIG. 9, pertains to a triggering event 901 as well. In this case, the triggering event is likely to be a claim against a bond or guaranty, but it may also be input from the Flagging Process (FIG. 8), into which all reports which are not first presented as pertaining to a Registered User are directed.

Prior to Company’s receipt of a triggering event or claim, a Registered User record contains a certain value in the “Experience Rating” field which is the product of a formula 900. This value grows automatically as the given Registered User builds up “Positive History” by purchasing more and more guaranties or bonds which do not result in claims. Specifically, the Experience Rating formula references each Bond Database 1301 record and Guaranty Database 1307 record related to the given Registered User Database 1308 record so that the value rendered by the formula automatically reflects the number of that user’s bonds and guaranties which have resulted in no claims.

Upon the receipt of a triggering event 901, the Company first investigates and verifies the event 902 through researching the credibility of the report, if this has not already been done (in the case of a claim having already been paid, verification at this stage is unnecessary).

Company Staff then evaluates whether the event is credible and damaging enough to merit a strike against the user’s Experience Rating 903. If not, then Staff decides whether to record the event at all 904, either making an entry in the Notes Database 910 or ending the process 909. If the event is sufficiently credible and damaging, the Staff creates 905 a new record in the Notes Database 1311, enters all information 905 pertaining to the event, and then assigns a negative value to the event and enters 905 this value in the “Negative History” field of the given Notes Database record 1311, which field is referenced in the formula which determines the Registered User’s Experience Rating value, thus resulting in a new Experience Rating 906. If the new Experience Rating value falls below a predetermined limit as a result of the new Negative History 907, then all outstanding bonds and guaranties are automatically cancelled, the Seals expired, and the given user is notified 908.

FIG. 10 depicts an example Verification/Activation Page, which serves a role in the Bond/Guaranty Verification & Coverage Activation process depicted in FIG. 11. The example depicts the Verification/Activation Page for a guaranty, but the page for a bond is similar.

In verifying that a given seller is bonded or a sale guaranteed, the buyer first views the Seal (410 or 420) being displayed by the seller 1101 and then clicks through 1102 to the verification page (FIG. 10) by clicking on the link included in the text (412 or 422) portion of the Seal (410 or 420). Viewing the verification/activation page (FIG. 10), the potential buyer evaluates whether this seller is who she claims to be or that the auction guarantee matches the auction which the potential buyer would like to bid upon and for which coverage is to be activated 1103. If there is not a match, the potential buyer may file a report of potential misappropriation of the Seal 1104. If the there is a match, the potential buyer submits 1105 the information requested in the Verification/Activation Page (see FIG. 10), which causes a new record 1106 to be created in the Bond Activations 1302 or Guaranty Activations 1312 Database. The buyer then receives an email confirming activation of coverage under the given bond or guaranty and containing a confirmation code that must be supplied in order to file a claim 1106. Alternately, an encrypted attachment (not depicted graphically) can accompany the confirmation email for security purposes.

Thereafter, if the purchase is made 1107, the transaction is undertaken between the seller and buyer. If the seller then fails to perform 1108, the buyer initiates 1109 the Claim Process (FIG. 12A).

FIG. 12A provides a flowchart overview of the Claim Process with reference to various sub-processes. Upon failure of the seller to perform 1201, the buyer must first request a refund 1202 directly from the seller. Failing to procure a refund 1203, the buyer then visits the Claims Page (HTML form hosted on Company site) to submit information pertaining to her claim 1204, including proof of her activation of protection under the bond or guaranty, certification that a refund has been requested from the seller and that the seller has denied the request, sale price, date, the nature of the defective performance, etc. Upon submission, a new record is created in the Claims Database 1304. If the information is complete 1205, the information submitted is automatically compared to the Registered User database information 1206 to determine whether the claimant currently owes the Company, e.g., if the claimant also has outstanding claims for which the Company has not been reimbursed 1211. If money is owed, the claimant must pay all balances before the claim can be processed (1214, 1215, 1216). Once balances are paid, the Company staff reviews the merit of the claim 1210. If the claim is sufficient to support payment 1209, Staff contacts the seller 1213 to request direct refund by seller to buyer. If the claim does not support payment, the staff contacts the buyer to see whether the deficiency in the claim can be corrected (1208, 1207, 1225, 1212).

Once the seller has been contacted 1213, she may refund the buyer (1217, 1218), dispute the claim 1218 or neither. A dispute initiates the Claims Dispute Resolution process 1220 detailed in FIG. 12C. If no dispute is made or if claim is upheld in dispute, the Claim Payment and Collection Process (FIG. 12B) is followed 1224. If the dispute is upheld, the claim is rejected, and the parties are notified of the result 1223.

By the time a claim reaches the process in FIG. 12B (1231), it is ready for payment. After the Company has issued payment to the buyer (by check or otherwise) 1232, the Staff contacts the seller against whom the claim was made 1233. If the seller agrees to reimburse the Company 1235, she sends payment to Company 1234 and avoids cancellation of her current bonds and guaranties. If she does not so agree 1235, then her bonds and guaranties are cancelled 1236 and the credit card which she has on file is charged for the amount due 1239 as per the Bond or Guaranty contract. If the charge is not sufficient to cover the liability, the staff contacts the seller for the remaining balance due 1240. If the seller agrees to pay it at this time 1241, she can still avoid certain complications. If the seller disputes the credit card charges 1237 or refuses to pay any excess charges 1241, then the Company notifies the ISP or auction site involved 1244, suspends seller’s account altogether 1243, and pursues legal action to collect 1246.

In all cases, the results are entered 1242 in a new record in the Notes Database 1311, including an entry in the Negative History field 1242, resulting in a newly adjusted Experience Rating.

If a claim is disputed by the seller, the Claim Dispute process depicted in FIG. 12C is followed. This process gives both the seller and buyer an opportunity to present their cases. The Company staff eventually decides whether to strike the claim or uphold it, and this result is returned to the main process depicted in FIG. 12A.

FIG. 13 depicts the core databases involved in storing and manipulating the information used in the present electronic bonding/guaranty invention. Principle relationships between records in a given database and records in another database are denoted with arrows and discussed briefly below.

Records in the Applications Database 1306 (“Database” hereinafter “DB”) comprise fields for all data submitted by a given registered user for a given application. The given application is related to a specific record in the Registered Users DB 1308 by way of a unique registered user identification number, which is assigned to each record in the Registered User DB at time of creation. As known to those skilled in the art, records are said to be “related” when the data in the related field of a given record in a given first database matches the data in the related field of a given record in a second database. Once a database relationship is properly defined, such a data matching will cause data of the two related records to be linked. Applications, when successful, result in the formation of new bonds and guaranties. Each new record in the Bonds DB 1301 and Guaranties DB 1307 is related to the record of in the Applications Database 1306 from which it spawned.

Certain identifying fields, such as email address, in the Applications Database 1306 may be related to a corresponding field, e.g., email address, in the Flagged Individuals DB 1303 so that applications submitted by undesirable applicants may be discovered prior to acceptance as per the Automated Guaranty and Bond Application review processes in FIGS. 6 and 7. Other fields in the Applications Database 1306, wherein the nature of the goods being sold is specified, may also be linked to corresponding fields in the Flagged Items DB 1305 to assist in avoiding underwriting transactions involving such items.

Records in the Registered Users DB 1308 are related to several other databases by way of the unique registered user identification number; these related databases include the Bonds DB 1301, Guaranties DB 1307, Payment History DB 1309, Archived Contact Info DB 1310, Claims DB 1304, and Notes DB 1311. Typically, the relationship is one to many: one record in the Registered User DB 1308 relates to multiple payments, multiple bonds, etc., while each payment, bond, etc., relates to only one registered user (as the Seller). Note, however, that a single record in the Notes DB 1311 may relate to multiple records in the Registered Users DB 1308. Note also that in order to file a claim, the claimant typically must have activated the protection of the bond or guaranty at the time of purchase, thereby creating a new record in the Bond Coverage Activations DB 1302 or Guaranty Coverage Activations DB 1312. At the d time of filing claim, the claimant must then become a registered user, if he or she has not already done so, thereby creating a new record in the Registered Users DB 1308. A given record in the Registered User DB 1308 may therefore relate to multiple claim records 1304 filed by a given user and, in a different relationship, multiple claims 1304 filed against that same user.

The records in Bonds 1301 and Guaranties DB’s 1312 have a one-to-many relationship to the Claims DB 1304 and Coverage Activations DB’s (1302, 1312), e.g., a single bond may produce multiple claims and activations, but a given claim or activation invokes the protection of only one bond or guaranty.

Less significant relationships are not depicted and should be apparent to one of ordinary skill in the art of data structure. Similarly, the many fields represented in each of the records of the various databases are not denoted by name or content in this document but should be apparent. Additional databases not depicted may also be employed to enhance the functionality of those depicted, according to the degree of sophistication the Company wishes to bring to bear upon the problem of accurately recording information pertaining to users, bonds and guaranties. For instance, for security purposes, the Company may wish to archive IP address information from which all bond or guaranty verification/activation click-throughs are received. Also, a Reports Database, in which a new record is created any time a report of suspicious activity is submitted to the through the Reports Page (not pictured), is contemplated.

FIGS. 14A through 14D depict flow charts detailing different revenue/money flow models through which the present invention can be readily funded and deployed for the benefit of all parties. The models are essentially self-explanatory.

FIG. 14A is that which is used in the preferred embodiment.

FIG. 14B is a promising alternative embodiment, since it provides guaranties which are free to both buyer and seller. Specifically, the cast of the quantity is paid for by advertisers, who pay for a banner ad 1002 on the Guaranty Verification and Activation page 1000. Of course, the seller must still agree to be ultimately responsible for any default on his part (1411, 1414).

FIG. 14C presents a “buyer pays” model, where the bidder activates protection if he wants it and is willing to pay for it 1422. This model may well be the most efficient, simply because the purchasing decision is placed squarely on the shoulders of the party for whose benefit the bond or guaranty coverage exists.

FIG. 14D presents a model wherein the Auctioneer handles the billing portion of the equation 1432, since the Auctioneer is presumably already billing the seller, the Auctioneer then outsources the rest of the work to Company. Alternately (not shown), the entire process can be handled by the Auctioneer providing its own bonds and guaranties and otherwise standing in the shoes of the Company.

It should be noted that different models can be mixed and matched or supplemented with other revenue models.

The present invention incorporates several security measures which are not graphically depicted. One primary risk to the Company in using the present invention comes from misappropriation of the bond or guaranty logo. Sellers who wish to avoid liability for claims made by aggrieved buyers but who wish to benefit from the appearance of being bonded or offering guaranteed auctions may attempt to pirate the company Seal and represent that they are covered when they are not. Thus, security measures include:

The Regenerating Seal. A Web browser “reads” HTML documents so as to display images when a proper reference to particular digital image, stored on a connected server, is made. The typical HTML code appears in a form similar to this: <img src=http://www.xxxx.com/image.gif>.

In the present invention, the Seal signifying a bond or guaranty includes a reference to a unique image, typically, a .jpg or .gif file, which is stored on the server of the Company. This image is that which is automatically generated for each bond or guaranty, and it contains the name, unique ID number, etc., as displayed in FIGS. 4B (411) and 4C (421). As depicted, this Seal image (411 or 421) indicates that the bond or guaranty it represents only covers purchases or bids made on a specified day.

The image (411 or 421) is regenerated each day at 12:01 am PST with the new day’s date visible therein and a new, unannounced background and color scheme. The new image then replaces the previous day’s image using the same URL or image address.

This daily image replacement allows properly referenced images to be continually renewed. Images which are not properly referenced, i.e., pirated, do not get replaced or updated. Thus, pirated images continue to display an expiration date which has already passed and a color/background scheme which is different from all active bonds and guaranties. This method does not eliminate the possibility of piracy but increases its difficulty and detectability.

Digital watermarking. Each image (411 or 421) used in a Seal is encoded so as to identify it as an image produced by and belonging to Company. Known search software can then be used to track the use of any such images containing this coding and thereby locate pirated images.

Text searching. The text (412 and 422) which appears under the Seal image (411 and 421) is an integral part of all valid Seals (410 and 420). Web text search and comparison software, such as that used by iParadigms in its plagiarism.org operations, can then be used by Company to detect any publications of this text which are not authorized.

Verification/Activation Page. The Verification/Activation process and page creates several protections. First, it puts a certain burden on purchasers to inspect that the seller is who he claims to be. Next, if a seller pirates this entire page in order to appear to be bonded or to have a valid guaranty, the page itself will appear at a URL hosted by someone other than Company, and, if it is referenced anywhere on the Web which makes it spider-able, Company text and/or image search software as described above will locate this unauthorized page. Even if the fake verification/activation page goes undetected, bidders who attempt to activate coverage will not receive a proper email confirmation from the Company, and may recognize that something suspicious is happening.

Community self-policing. As the electronic bond or guaranty becomes more familiar to the Internet purchasers, these purchasers will become more familiar with the proper appearance of the Company Seal and the Verification/Activation Page and will be able to recognize more readily when a Seal has expired or been misappropriated or when an entire Verification/Activation Page has been pirated and uploaded by someone other than Company. Thus, an easy self-policing mechanism is provided in each Seal: clicking on “Contact Us” immediately transports the user’s browser to a Web form where a report can be made.

“Click-through” tracking. Known software enables tracking of traffic from one Web location to another. The Company can employ such software to determine where click-throughs are coming from, and these click-throughs can be compared to the database of URL’s which have been authorized to display the Seal. If a given site is displaying the Seal without authority, this information will be automatically brought to the attention of Company staff.

I. Electronic Collateral Reservation Process Alternative Embodiment

FIG. 15 presents an overview of a process by which the Company’s risk can be reduced by continuously preauthorizing a credit card charge in “chain” fashion such that there is essentially never a time throughout the duration of a bond when the Company does not have a preauthorized charge against the bonded seller’s credit card in the amount of the full penal sum of a bond. Since this Electronic Collateral Reservation Process incorporates many of the processes already described above, the flowchart depicted in FIG. 15 is intended primarily to highlight only the differences in this alternative embodiment.

The user begins by completing a bond application choosing a coverage limit and specifying whether the bond should be automatically renewed upon expiration 1501. In this application, she can choose to use one credit card as the “collateral card,” which will only be charged in the event of a default by the user, and another credit card to which payment for the bond will be billed, although the same card can be used for both purposes. Provided that the application is complete and otherwise acceptable, a charge to the collateral card in the amount of the full penal sum of the requested bond will be preauthorized 1502 and a charge to the billing card in the amount of the price of the bond will be preauthorized 1502. If both preauthorizations are successful, i.e., not declined by the credit card issuer, then the bond application is accepted, the charge to the billing card finalized, and the bond contract becomes legally binding 1504. If either preauthorization fails or the bond application is insufficient on grounds described in reference to FIG. 6 or elsewhere, then the application is rejected 1503.

After a bond application has been accepted, the Company’s risk period begins. The risk period is discussed in more detail below in reference to FIGS. 16A and 16B.

At regular, specified intervals from the beginning through the end of the risk period, the Company will follow a “re-preauthorization” procedure 1512. This procedure has two basic steps: first, the existing preauthorization, initially made when the bond application was accepted, of a charge to the collateral card in the amount of the total penal sum is canceled. This step may be achieved by closing out the preauthorized charge as an actual $1 charge and then immediately voiding this $1 transaction. The second step of the re-preauthorization procedure 1512 is executed immediately thereafter: a new preauthorization of a charge to the collateral card in the amount of the full penal sum of the user’s bond is performed. The new preauthorization can also be made immediately before the existing one is canceled, if the given user’s credit limit will allow it.

This procedure 1512 allows the Company to maintain a virtually uninterrupted reservation of a certain portion of the total credit available to the collateral card account. This procedure is made necessary by the fact that preauthorizations of credit card charges usually expire within a few days of preauthorization.

Once the risk period has ended 1505, the re-preauthorization cycle discontinues 1518.

Upon the expiration of a bond 1506 for which the user has selected automatic renewal 1507, the billing card is charged 1508. If the billing card is declined 1509, a suspension notice is sent to the user 1510 indicating that the bond will be suspended for lack of payment unless payment is provided within a certain number of days. Upon payment, the bond will be reinstated.

If preauthorization of the collateral card fails 1513, the bond is suspended 1514 until such time as the user provides new, valid credit card information, at which time the bond will be reinstated 1516, provided that the bond itself has not expired. If the user fails to provide a new valid credit card 1513, then the user’s Experience Rating will be affected, and the user will not be able to purchase additional bonds until such time as the failure is remedied 1512. If preauthorization of the collateral card is successful 1513 and the risk period has not ended 1505, then the re-preauthorization 1512 cycle continues.

FIG. 16A presents a timeline tying together much of the above discussion. The Company’s risk period is that time period between the moment of approval of a bond application 1601 and the last moment at which filing of a viable, timely claim against that bond by an aggrieved buyer is possible 1605. If the Company is using the Electronic Collateral Reservation Process described in FIG. 15, it should reserve funds in the collateral card account throughout the risk period, and this reservation can be released 1606 any time after the risk period has ended 1605.

In FIG. 16A, a bond application is approved 1601, but the applicant has requested that bond coverage not become active until sometime later 1602. The applicant has also requested that the bond be automatically renewed upon expiration, and thus, in the example of a one month bond model, the bond becomes active 1602, expires at the end of one month, and then is automatically renewed immediately 1604. This automatic renewal occurs several times until finally the bonded seller requests that automatic renewal be discontinued. When the then-current month ends, the bond expires and is not renewed, and therefore the bond coverage ends 1603. The Company’s risk period, however, may not end until sometime thereafter, since claims can be filed for bonded transactions that occurred during the active life of the bond coverage for a certain period of time after bond coverage has ended 1603, as illustrated in the following FIG. 16B.

FIG. 16B depicts another scenario in timeline fashion. In this case, the bond applicant chooses that the bond become active immediately upon acceptance, and therefore the bond coverage period and the risk period begin simultaneously 1610. As per the Electronic Collateral Reservation Process, re-preauthorization of the collateral card charge occurs at regular intervals 1613 thereafter. The bonded seller then lists an auction that begins 1611 and ends 1612 during the bond coverage period. Although it is not necessary, the Company should probably require that auctions both begin and end during the bond coverage period in order for bond coverage to lie. Once the auction has ended 1612, the time period allotted for delivery of the purchased item from seller to buyer begins 1612. A purchaser may not file a claim until this delivery period has ended 1614, at which time the claim period begins 1614. The purchaser then has a certain number of days during which she can file a claim under the bond, after which time the claim period ends 1615, and no more claims can be filed against the given expired bond. Thus, in this example, where the bonded seller has run but a single auction, the Company’s risk period ends when the claim period associated with that auction ends 1615. Note that the delivery period and the claim period both extend well beyond the expiration of the bond 1616, and therefore the re-preauthorization cycle 1613 continues also. In the case of bonds which are not associated with an auction site, the bond claim period will simply extend for a fixed period of time after the end of the bond coverage period rather than being tied to any transaction.

If a claim is filed during the claim period, however, then the Company’s risk period will be extended indefinitely until the claim is resolved, and the re-preauthorization cycle will continue accordingly.

If multiple claims are made against a single bond, the Company will need to make a business decision regarding whether to charge the seller’s card the entire penal sum and divide the resulting funds amongst claimants, refunding any remainders to the card once all claims are extinguished, or to charge the value of each claim as a separate charge against the collateral card up to an aggregate sum equaling the penal sum.

II. Integrated Auction Bonding Method

The preferred embodiment as described above allows the identifying Seal of a bond to be added to any HTML page, including both the homepage of the bonded seller and auctions she uploads on a third party auction site. However, the security measures described may not be enough to prevent unauthorized uses–piracy–of the bond Seal. This problem can be partly remedied through the use of an alternative embodiment wherein the third party auction site operator, such as eBay (hereinafter, “Auctioneer”), itself serves up a condensed version of the bond Seal rather than the Seal being served by the Company’s servers. Such an approach makes use of the fact that certain parts of the HTML page in which an online auction is presented are under the exclusive control of the Auctioneer itself, as opposed to the section of content that can be manipulated by the auction site user. Thus, if the only legitimate Seals are those which are served in an “exclusive control” area, then pirated Seals will be obvious and basically pointless.

Serving of the Seal by the Auctioneer is made possible by the Integrated Auction Bonding Method disclosed in the following figures. In this alternative embodiment, a high speed data link is established between the servers of the Company and those of the Auctioneer. This link allows database replication, meaning that certain fields of records in the Company’s bond database are mirrored in a separate bond database under the control of the Auctioneer.

FIG. 17A depicts a simple portrayal of this database relationship. The Company’s databases, including the Bonds Database 1701 and other related databases 1702 discussed in this document, appear on the left. On the right are the databases of the Auctioneer, including the Mirror Bonds Database 1703 and such other databases 1704 as the Auctioneer uses in its own operations, all of which reside on the Auctioneer’s hardware. The Company’s Bonds Database 1701 is the master database from which the Mirror Bonds Database 1703 derives continually updated information. Only a few fields in the Company’s Bonds Database 1701 are replicated in that of the Auctioneer 1703, namely: (1) is the bond currently in effect; (2) what is the coverage limit of the bond; (3) what is the bonded seller’s unique auction site username or other control value/ID; and (4), if there may be large delays between updates of the information in the Mirror Bonds Database 1703, when is the bond scheduled to expire. Ideally, this last piece of information need not be stored by the Auctioneer but rather the coverage limit field would be continually updated in real-time and reduced to $0 immediately upon bond expiration. Additional fields may be stored to enhance the functionality, granularity, accuracy or speed of the system as a whole.

Note that the Company must make a business decision regarding whether to withdraw bond coverage from auctions that are already running when a bond is prematurely canceled (re-preauthorization fails, for instance).

As with other icons typically served next to the username of a seller, whenever that username appears on an auction site, such as the reward stars served next to the usernames of prolific sellers on eBay, the condensed bond Seal is called every time the bonded seller’s username appears on the Auctioneer’s site. When this call is made, the Auctioneer’s databases are queried to determine whether the given seller is bonded, and if so, what is the coverage limit of the bond. In cases where the seller is bonded, the bond Seal is served. This Seal can simply serve to demonstrate that the seller is bonded, or it can display additional information, such as the difference between the penal sum and the sum total of aggregated potential claims against the bond as determined through the Bond Margin Gauge process described in reference FIG. 18 below.

FIG. 17B shows a fragment of an example HTML page that is an auction listing on the Auctioneer’s site, which is being operated in cooperation with the Company per the Integrated Auction Bonding Method. The seller in this example has a unique username “JoeSeller” 1711 and has been awarded a user rating 1712 and an achievement star 1713 by the Auctioneer. As is typical, the user rating 1712 is a real-time updated text value, and the achievement star 1713 is an image file served next to the username 1711 of any sellers to whom it has been awarded. Next to these other icons is the Seal 1714, which demonstrates that the given seller is bonded and that his bond margin, a dynamically updated, real-time value, is $4690.00. This number is the purpose of the Bond Margin Gauge.

Each time the Seal, including the Bond Margin Gauge, is called to appear in an HTML document per request by a client computer to the Company’s server, certain information is retrieved and processed from the Auctioneer’s databases, specifically: the bonded seller’s coverage limit, the high bid in all currently running bonded auctions (including, in the case of a Dutch auction, the top X bids where X is the number of items being auctioned in the Dutch auction), and the winning bid in all closed bonded auctions for which the risk period has not expired. The sum total of all high bids in all currently running bonded auctions and all winning bids in closed auctions for which the risk period has not yet expired is subtracted from the penal sum of the seller’s bond to leave a difference which represents how much bond “headroom” is available under the seller’s bond. This number is then displayed in the Seal automatically appearing next to the seller’s username. This number is useful to potential bidders, since competing claims against the bond could reduce the availability of funds against which an aggrieved buyer could claim in the event of default.

FIG. 18 presents an example of the Bond Margin Gauge in action. On Day 1, JoeSeller (1711 in FIG. 17B) has three running auctions, two of which have met the reserve. The bonded seller’s coverage limit is $5000.00, and the sum of the three high bids is $310.00. The Bond Margin Gauge therefore reads $4690.00. On Day 2, two of the auctions have closed, one of which did not meet the reserve, auction 3. Since auction 3 has closed without a winner, the high bid in that auction no longer counts against the seller’s bond margin. The sum total of the winning bid in auction 1, which has closed, and auction 2, which is still open, is $300, and the bonded seller’s currently available margin as measured by the Bond Margin Gauge is therefore $4700. By day 4, auction 2 has also closed with a high bid of $150.00, and the Bond Margin Gauge reads $4650.00.

On Day 93, JoeSeller (1711 in FIG. 17B) lists a new auction which currently has no bids. The risk period for auction 1 has ended, and therefore the winning bid in that auction no longer counts against the seller’s bond margin. However, the risk period for auction 2 has not yet ended, and therefore the seller’s bond margin equals $4850. By day 95, the risk period for auction 2 has ended, and auction 4 has a high bid of $500, resulting in a bond margin of $4500 for the given bonded seller.

III. Bidder Payment Bonding and Deposit Accounts

To this point, the present invention disclosure has dealt primarily with the bonding of Internet merchants to protect buyers in cases of merchant default. FIG. 19 depicts an alternative embodiment of the current invention adapted for bonding bidders.

After the user has registered with the Company 1901 and her credit card or cards have been preauthorized 1902, the bidder can choose to open a deposit account 1904, specifying an amount of funds to be deposited with the Company 1905. This amount is charged to the bidder’s credit card 1905, and the bidder’s deposit account shows a credit for these funds.

It should be noted that a Bond Seal for a bonded bidder preferably appears next to the given bidder’s username, just as Bond Seals appear next to the seller’s username when a seller is bonded. The Bond Seal used to indicate that a bidder is bonded can, but does not have to include a margin counter displaying a value representing the difference between the bidder’s total coverage and the sum total of her outstanding bids. The outstanding bids include any winning bids in closed auctions wherein it is still possible for an aggrieved seller to claim against the bidder’s bond.

It is typically possible for the same auction site account to be used for both buying and selling activities, and, therefore, one type of Bond Seal appears next to the given username when that user is acting as a bidder. Another type of Bond Seal is displayed when the given user is acting as a seller, provide, of course, that the given user is covered by both an applicable merchant bond and a bidder bond.

It is to be further understood that the seller can, if required, activate the buyer’s bond upon acceptance of the buyer’s bid by linking to the online site by clicking through the Seal and following the coverage activation procedures described in greater detail above for activating coverage of the seller’s bond by the buyer.

Whether or not the bidder has elected to open a deposit account, the bidder is then given the choice between a preferred bond and a standard bond 1907. The standard bond, providing but a small amount of coverage, is free and has no set expiration date. A preferred bond must be paid for upon initiation and at periodic renewals, but the coverage limit available to the bidder is much higher. A preferred bond is handled essentially like the sellers’ bonds above via the re-preauthorization cycle (see 1512 in FIG. 15): the charge for the full penal sum is preauthorized on the collateral card 1909, the fee for the bond is charged to the billing card 1910, and re-preauthorization of the collateral card is repeated periodically thereafter 1911. If the bidder chooses a standard bond 1914, the re-preauthorization cycle is not used, but the card is checked once every few weeks to see that it remains valid 1915.

The deposit account is used to allow immediate payments to be made electronically and automatically by the Company directly to a bonded seller at the moment a bonded bidder with a deposit account wins an auction listed by the given bonded seller, provided that funds in the deposit account exceed the price of the winning bid.

FIG. 20 provides a flowchart that ties together the complex interactions of the various embodiments described above when several of these technological methods are deployed simultaneously. When an auction closes 2001 wherein the seller is bonded 2002, if the bidder is also bonded and has deposited funds in a deposit account sufficient to cover the price of the winning bid 2013, payment will be wired automatically to the seller immediately after the auction closes 2014. If no such deposit account funds are available 2013 but the bidder later pays the seller 2015 and the seller delivers 2017, then the transaction has gone well, and the Company does not get involved 2004, just as if neither the seller 2002 nor the bidder 2003 were bonded at all 2004. If a bonded seller fails to deliver 2017, then the claim process depicted in FIG. 12A is followed. In cases where the bidder is bonded 2003/2016 but fails to pay 2005/2015, the seller must file a claim against the bidder’s bond during the claim period 2006. If the bidder does not correct her default 2007, the seller must deliver the item purchased in the auction to the Company 2008. Upon satisfactory delivery, the seller will be paid by the Company 2009, and the bidder’s collateral card charged 2010, both for the amount of the bid price and for a default premium whereby the Company profits from having served as a surety for the defaulting bidder. Thereafter, the purchased item can be sent to the bidder by the Company if desired. If the bidder’s collateral card is declined 2010, then the bidder is contacted, and the Company’s chosen collection methods are employed.

Alternately (not depicted), the seller can sell the purchased item to the next highest bidder in case of default by the winning bidder, if this next highest bidder can be found, in which case the Company would reimburse the seller her transaction costs in finding another buyer and charge the defaulting bonded bidder for these costs in addition to a premium.

Another alternative provides that when sellers are listing auctions on the Auctioneer’s site, they are offered the option to allow only bonded bidders, or only bonded bidders with deposit accounts, to bid on the auction. The Auctioneer’s database will then be checked when a bidder places a bid to see whether that bidder is bonded before the bid will actually be placed.

Another option that can be offered to sellers by the Auctioneer at listing time is to allow automatic discounts–2% off the price of winning bid, for instance–for any bidders who are bonded. Some auctions already allow sellers to offer discounts to the first bidder in a given auction.

Various embodiments of the of the present invention have been described herein. It should be understood by those of ordinary skill in the art, however, that the above described embodiments of the present invention are set forth merely by way of example and should not be interpreted as limiting the scope of the present invention, which is defined by the appended claims. Many other alternative embodiments, variations and modifications of the foregoing embodiments that embrace various aspects of the present invention will also be understood upon a reading of the detailed description together with the Figures. For instance, it will be understood that features of one embodiment may be combined with features of other embodiments while other features may be omitted (or replaced) as being nonessential to the practice of the present invention.