Buttons for person to person payments

Abstract

According to the invention, a process for facilitating payment between a buyer and a seller with an online money transfer performed over a wide area network is disclosed. In one step, login information relevant to a vending site is received. The login information is associated with the seller. Listings at the vending site associated with the seller are automatically determined. A number of snippets of HTML code are generated for the listings, wherein each snippet includes a link. One of the plurality of snippets is automatically inserted into each of the listings. Activation of the link points a web browser to a payment enabler that can transfer money from the buyer to the seller.

Description

BACKGROUND OF THE INVENTION

[0001] The invention relates generally to person-to-person money transfers, and more particularly facilitating money transfers related to listings at vending sites.

[0002] One party may wish to transfer money to herself, a counter party, or vice versa, for any of a variety of reasons. For example, a payor may wish to give the money to the payee as a gift, or the payee may receive payment for an auction item sold to the payor. If the receiving party to the transfer is a merchant with a merchant credit card account, payment is received in the conventional way. Person-to-person payments apply to situations where the receiver of the payment does not have access to a merchant credit card account. For example, the payee in a person-to-person transaction may be a merchant of goods without the ability to accept credit card payments directly because a merchant credit card account is lacking.

[0003] Until recently for person-to-person payments, payors typically complete such payments via cash, check or money order because the payee does not have the ability to receive money electronically. Electronic payment methods are generally available to merchants, such as credit cards and bank account debits through electronic fund transactions, however, the payor may not have access to these methods for whatever reason. For example, these electronic payment methods for merchants may require purchasing hardware and/or software to support accepting payment.

[0004] Auction sites, such as eBay™, provide action services that often involve parties without access to merchant account for accepting payment. Today, these parties often rely upon online money transfer systems. Often a button is inserted into auctions that the payor may activate to link to the online money transfer system. This button may embed a user identifier for the payee that is passed to the online money transfer system when the payor activates the link. The user identifier is used in one example to inform the online money transfer system who referred the payor.

[0005] There are web sites that will auto-insert information into auction listings for various purposes. For example, an online money transfer system may insert buttons into all the auction listings for a particular user. The user provides the web site with a user name and password for the auction site and the web site finds all the active auction listings. A button is inserted into each active listing associated with the user.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The present invention is described in conjunction with the appended figures:

[0007] FIG. 1 is a block diagram of an embodiment of an online money transfer system that is interfaced to a payor and payee;

[0008] FIG. 2 is a block diagram of another embodiment of an online money transfer system;

[0009] FIG. 3 is a block diagram of an embodiment of a payment enabler;

[0010] FIG. 4 is a block diagram of an embodiment of a vending site;

[0011] FIG. 5 is a flow diagram of an embodiment of a process for adding snippets to listings on the vending site;

[0012] FIG. 6 is a flow diagram of an embodiment of a process for a buyer paying for goods and/or services in the listing; and

[0013] FIG. 7 is a flow diagram of an embodiment of a process for automatically inserting snippets in listings.

[0014] In the appended figures, similar components and/or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

DESCRIPTION OF THE SPECIFIC EMBODIMENTS

[0015] The ensuing description provides preferred exemplary embodiment(s) only, and is not intended to limit the scope, applicability or configuration of the invention. Rather, the ensuing description of the preferred exemplary embodiment(s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment of the invention. It being understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth in the appended claims.

[0016] The present invention facilitates online money transfers between payors and payees that use vending sites. Types of vending sites include auction sites, classified advertising sites, and other on-line sites that facilitate person-to-person sales. When a party does not have access to a merchant account for accepting payment, they often rely upon a payment enabler to allow the money transfer in these person-to-person sales. In various embodiments, the process of interacting with the payment enabler is facilitated with a snippet that may have a link and a button graphic associated therewith. These snippets allow the payor or purchaser to reduce the information manually entered into the payment enabler. A metalink tool will add the snippet to all current and/or future listings at one or more vending sites.

[0017] Referring first to FIG. 1, a block diagram of an embodiment of an on-line purchase system 100 is shown. Included in the system 100 are a vending web site 140, an online money transfer system 190, a sender 110, and a receiver 130. Respective computers 120 interface the sender 110 and receiver 130 to the Internet 150 or other wide area network such that they can interact with the vending site 140 and the money transfer system 190. Money handlers 160, a payment enabler 170 and user interfaces 180 make up the money transfer system 190.

[0018] The vending site 140 is a web site coupled to the Internet 150 and may include servers and other computers as is well known in the art. The sender 110 points their browser to the vending site 140 to choose a purchase listing associated with the receiver 130. These listings could be classified advertisements, electronic advertisements or auctions. As is the case with some auctions, a listing may not be paid for until a period specified in the auction has expired. Although this embodiment shows the vending site 140 being separate from the money transfer system 190, other embodiments could combine these into the same location or spread portions of either among any number of locations.

[0019] The transfer system 190 works in concert with the vending site 140 to help pay the selling party. It is noted that vending sites 140 do not typically support the insertion of buttons directly, but have certain features meant for manual manipulation that allow automation of the process by the payment enabler 170. When the purchaser wants to pay the selling party, the purchaser or payor interacts with the money transfer system 190 to get money sent to the selling party or payee. To initiate sending money, the payor may contact the payment enabler 170 directly, may click a button in the listing or may respond to a button or link in a money request. Money handlers 160 are used to payin money for the buyer 110 or payout money for the seller 130. The user interfaces 180 provide a variety of ways for the sender and receiver 110, 130 to interact with the transfer system 190.

[0020] With reference to FIG. 2, a block diagram of an embodiment of an online money transfer system 190 is shown. The money transfer system 190 can be used for a variety of purposes, such as sending checks, sending greeting cards, sending payments for goods or services, or other situations where the receiver 130 may not have a merchant account for accepting electronic payment. In this embodiment, six handlers 160 and five user interfaces 180 are shown. Other embodiments could have more or less handlers 160 and interfaces 180. Each of the handlers 160 allows a sender or receiver 110, 130 to add and/or remove money from the payment enabler 170. Normally, the receiver 130 can choose the handler 160, but in some circumstances, the sender 110 can choose the handler 160. For example, the sender may specify a particular gift certificate handler 160-6 that only allows the certificate to be used at a particular store for merchandise and/or services. The user interfaces 180 allow interaction with the payment enabler 170 to transfer money to and from a stored value fund.

[0021] The promotion handler 160-1 allows adding and removing money in a form other than legal tender or negotiable instrument. Examples include airline mileage programs, prepaid phone cards. For example, a user could use money in their stored value fund to purchase airline miles with an airline mileage handler 160-1. A conversion rate would be applied to convert the money to mileage credit. The promotion handler 160-1 may need special information from the payment enabler 170, such as the user's promotion account number, etc. Some of the interfaces 180 used to gain access to the payment enabler 170 could be used to also gain access to the vending site 140 to allow selecting a listing where a computer 120 may not be readily available to the sender 110.

[0022] The credit and debit card handlers 160-2, 160-3 behave largely the same. Both can be used to add money into the payment enabler 170. In other embodiments, these handlers 160-2, 160-3 can also be used to remove money from the payment enabler 170 also, for example, to purchase a prepaid credit/debit card, to pay down a balance on a credit card, or to add credit to a bank account associated with a debit card. To use these handlers 160-2, 160-3, the payment enabler 170 stores the information for receiving money from credit or debit cards in the conventional way, such as the account number, expiration date, name, and/or PIN. Similar information may be used when paying-out money to a credit/debit card.

[0023] The bank handler 160-4 allows electronic funds transfer (EFT) of money to a bank account of the user. The user enters the account number and routing information into the payment enabler 170 with a user interface 180 to facilitate adding and removing of money from the payment enabler with this handler 160-4. In one embodiment, an automated teller machine (ATM) could incorporate the bank handler 160-4 along with an ATM interface 180-1 to allow adding and removing funds along with interfacing with the payment enabler 170. Another embodiment uses a bank handler 160-4 branch location as a retail interface 180-4 for interacting with the payment enabler 170. Some embodiments could wire money into a bank account of the user instead of an EFT.

[0024] The retail handler 160-5 typically corresponds to a retail location 500 or storefront that may wire money, print money orders and/or cash checks. Money may be sent to the retail handler 160-5, whereafter the user is issued cash or a negotiable instrument for that money. Money can be added to the system 100 by the retail handler 160-5 also. For example, the user may give cash to the clerk at the retail location 500 who enters a credit into the payment enabler. The user could further specify to the clerk a receiver who should get the money. A retail interface 180-4 at the retail location 500 or bricks and mortar location is used by the clerk to indicate to the payment enabler 170 that the money has been received from or by the user. Through an retail handler 160-5 a sender 110 could use the online money transfer system 100 without any knowledge of computers or without any debit/credit card or bank account.

[0025] Gift certificates are dispensed through one or more gift certificate handlers 160-6. The gift certificate can be limited to merchandise and/or services from a single store or a group of stores. In some cases, the gift certificate is used only online by entering a code provided to the receiver or could be printed for use in a bricks and mortar store. Cash equivalents such as FlooZ™, formerly available from Flooz.com, could also be provided to the receiver 130. For example, a listing on the vending site 140 may specify that the compensation should be in the form of a particular gift certificate.

[0026] As briefly discussed above, the ATM interface 180-1 allows interaction with the payment enabler 170. The user may 110, 130 or may not have an affiliation with the ATM that is used to interface with the payment enabler 170. Under this circumstance, the owner of the ATM may charge the user a fee for this service. The user 110, 130 can receive cash or deposit cash if the ATM is coupled to a bank handler 160-4. In any event, the ATM interface 180-1 can be used to interface with the payment enabler 170 in the same way a user 110, 130 may interact through a web browser and computer 120 with the payment enabler 170. If the ATM has a magnetic stripe or smart card reader, this could be used by to avoid entering credit or debit card information manually for the payment enabler 170.

[0027] A kiosk interface 180-2 allows a user to interact with the payment enabler 170, but typically does not allow adding or removing cash. The kiosk interface 180-2 may be a browser terminal available for general use. Some embodiments may include a check or money order printer for removing money from the system 100. The kiosk interface 180-2 could be in a retail location 500 and linked to the other systems in the retail location 500 such that a payout could be provided by other systems in the retail location 500.

[0028] An Internet interface 180-3 is typically implemented through a web browser. The browser downloads web pages from the payment enabler 170. This browser may reside on the computer 120 of the sender or receiver 110,130. Some embodiments could host the Internet interface on a portable device such as a wireless phone or personal digital assistant (PDA). The Internet interface 180-3 may also be used by the ATM, kiosk and retail interfaces 180-1, 180-2, 180-4 in whole or in part. The Internet interface 180-3 uses encryption for the link to the payment enabler 170 in some embodiments.

[0029] The retail interface 180-4 allows for specialized interaction by a clerk at the retail location 500. Clerks typically have special training and offer enhanced services over most interfaces 180 and handlers 160. The clerk can move money between senders 110 and receivers 130 at the direction of the user. Also, the clerk can pay-in and pay-out money from the transfer system 100 for any user. The retail interface 180-4 allows an clerk to act on behalf of the user when manipulating the user's account. For security, the user's password or PIN may be entered during this manipulation. Further, the clerk may verify the identity of the receiver 130 before disbursing the any money from the transfer system 190. In one embodiment, a test question is provided by the sender 110 that the receiver 130 must answer before the electronic gift is paid-out.

[0030] Interaction with the payment enabler 170 may also be performed over a telephone 140 interfaced to the plain-old telephone system (POTS) 155. The phone interface 180-5 provides voice prompts and recognizes the user's touch-tone or speech recognized input. Enhanced interaction with the phone interface 180-5 could be provided with wireless phones having wireless access protocol (WAP) and/or browser graphical user interfaces (GUIs).

[0031] Referring to FIG. 3, a block diagram of an embodiment of a payment enabler 170 is shown. The transfer of money between handlers 160, stored value funds and users 110, 130 is controlled by the payment enabler 170. The payment enabler 170 may be implemented on one or more computers in one or more locations where the various computers communicate over a network. Included in the payment enabler 170 are a payment controller 304, handler interfaces 308, a billing function 312, a messaging function 316, an enabler interface 320, a user database 324, a payment conversion function 328, an exchange rate database 332, and a metalink tool 336.

[0032] The payment controller 304 manages operation of the payment enabler 170. The handlers 160 and interfaces 180 along with user information and money conversion tasks are all choreographed by the payment controller 304. The payment controller 304 is interconnected to the other portions of the payment enabler 170 by one or more networks.

[0033] The payment conversion function 328 allows converting between disparate forms of money as it is transferred through the transfer system 190. An exchange rate database 332 holds conversion factors that allow determining the proper weight to give one form of money with respect to the others. In one example, the payment conversion function 328 may convert money in U.S. dollars to money in European Union Euros. In another example, a user may convert money into airline miles at the rate of eight miles for every dollar for a promotion handler 160-1. The exchange rate database 332 is updated with conversion rates as often as practical using conventional methods. The conversion rate may accommodate a percentage service fee for the exchange, or instead of a conversion rate, a flat fee could be charged.

[0034] A billing function 312 monitors and charges for the services of the payment enabler 170. There may be charges when transferring money, converting money, sending electronic gifts, printing and mailing negotiable instruments, using kiosks, ATMs or retail locations, inserting snippets into listings on vending sites 140, etc. These charges are normally deducted from a transfer, but other embodiments could charge monthly fees or use based fees. Some embodiments could recover a fee from the handler 160. For example, a fee could be charged to the gift certificate target store instead of charging the sender 110. The different types of handlers 160 may have different fees associated with them. For example, a credit card may have a three percent charge, but a bank transfer may only have a one percent charge. The sender and/or the receiver can be charged to transfer money between themselves. Further, a charge from the money transfer could be funneled back to the vending site 140 to pay for the listing. The transfer in or out of the system 100 may incur a separate charge. The billing function 312 may issue invoices for some users.

[0035] There are handler interfaces 308 to support the various handlers 160. Each of these interfaces 308 may support a single handler 160 or a group of handlers. For example, a single interface may perform EFT both to and from all bank handlers 160. When money is sent to or received from a handler 160, the appropriate handler interface 308 passes the money and transfer information to the payment controller. In some embodiments, the cost of the transfer to or from the handler is reported by the handler interface 308 such that the billing function could recover those costs as a fee to the buyer 110 or seller 130.

[0036] Information for the users of the system 100 is stored in the user database 324. This information includes an address book of other users, money credit in the stored value fund, past money transfer information, account number, e-mail addresses, contact information, vending site login information, snippet information and preferences, customized snippet messages, handler interface information, handler preference information, etc. The money credit is stored in a trust account for the benefit of the user according to the entry in the user database 324 corresponding to that user and interest may or may not be paid on that money credit.

[0037] Money is a credit amount stored as a database entry corresponding to the user in the user database 324. The database entry corresponds to a stored value fund for that user that can be supplemented by transferring-in credit or reduced by transferring-out credit. The money or credit is transferred between users by updating the database entries for the users involved in the transfer. Money could be in any currency or be anything of monetary value, for example, airline mileage, promotional program points, gift certificate credit, commodities such as gold, etc.

[0038] Some embodiments may not used stored value funds. In these embodiments, money transfers to the receiver 130 pass directly to the money handler 160 specified by the receiver 130. The receiver has the option of having the money transfer once it clears or immediately. Where the transfer is immediate, transfers that fail could be absorbed by either the receiver 130 or the payment enabler 170 if insurance is purchased.

[0039] The enabler interface 320 is used by the various interfaces 180 to interact with the user. The enabler interface 320 produces the form web pages and informational web pages to allow the user to create and maintain their account, transfer money, select electronic gifts, configure vending site snippets, and learn to use the system 100. The appropriate user interface 180 formats and processes the enabler interface information according to the device used to interface with the payment enabler 170. For example, the Internet interface 180-3 takes the information from the enabler interface 320 and formats into hypertext mark-up language (HTML) appropriate for the computer 120 of the user.

[0040] A messaging function 316 is used with some configurations to notify the user of certain events. Requests for money are sent by the messaging function 316 along with acknowledgment and billing messages. These messages could be accessed using a web browser, an e-mail program, an instant messaging program, a pager, a WAP enabled device, etc. In some embodiments, the messaging function 316 may issue printed bills for users. The messaging function 316 is also used to communicate with retail locations 500 and with the eCard site 140. Some embodiments use the metalink tool 336 to formulate a money request to the buyer 110 after a listing matures at the vending site.

[0041] The metalink tool 336 manages formulation of snippets, automated insertion of those snippets at the vending site, gathering information about the listing, and formulating money requests for a listing. Electronic listings, such as classified ads and auctions, are managed by the metalink tool 336 for the benefit of a seller 130. Goods or services offered in a listing can be paid for using the payment enabler 170.

[0042] The metalink tool 336 gathers information on each listing from the seller 130, the vending site 140, the buyer 110, and any information stored in the user database 324 in the past. Information gathered and stored in the user database 324 for each listing could include a shipper selection, shipping insurance cost information, an address for the seller, tax information, an item description, a reference number, a payment enabler category, a purchase price, a phone number for the seller, a close date for the listing, and a quantity of items in the listing. After the listing closes, information such as the address of the buyer, the e-mail address of the buyer, the shipping selection, the insurance selection, a purchase order number, special handling instructions, and other information could be added to the user database 324.

[0043] In a listing, the seller 130 often whishes to indicate the forms of payment accepted. A branded graphic or button can accomplish this. By way of the enabler interface 320, the seller 130 interacts with the metalink tool 336 to insert a snippet of HTML code that references a graphic for display. This graphic can be made into a button by including a link or a universal resource identifier (URI) that is loaded into the browser when the graphic is clicked upon. The metalink tool 336 stores login information for any number of vending sites associated with each seller 130 in the user database 324. The login information allows the metalink tool 336 to automatically insert the snippet into the current listings of the seller 130 and/or all future listings of the seller 130. Some embodiments just list the HTML code of the snippet in a web page that the seller 130 can cut and paste into a listing. In some cases, the snippet may include a custom message from the seller 130 that is either visible all the time or only when the cursor hovers over the graphic.

[0044] The link can include information about the listing to make the process of sending money to the seller 130 easier. In one embodiment, a code unique to that listing is inserted into the link. That code is used to query the user database 324 for information on the listing. Another embodiment includes fields in the link that hold some or all of the information relevant to the listing.

[0045] Here is an example of a snippet that might be automatically inserted or manually pasted into a listing: <form name=“frmMZSubmit” method=“POST” action=“http://fdcdevwevl/HSPaymeSignon.asp”><input type=“hidden” name=“hdnMZUserID” value=“3181”><input type=“hidden” name=“hdnAmount” value=“34”><input type=“hidden” name=“hdnSubject” value=“ParkieBaby”><input type=“hidden” name=“hdnReferenceNumber” value=“223453389”><tr><td colspan=“2” align=“center”><input type=“impage” name=“imgSubmit” src=“http://www.moneyzap.com/images/logo_lg.gif”></td></tr></form>. Specified in this snippet are the payment enabler user identifier for the seller 130, the purchase price of $34, the subject of the listing of “ParkieBaby,” the reference number for the listing of “223453389,” a link back to the payment enabler 170, and a graphic for the button. Although this embodiment uses HTML and scripts, any combination of web languages could be used such as ActiveX™, Java™, scripting languages, etc. Other embodiments could embed more information in the link that is provided to the payment enabler 170 when the link is presented as is known in the art.

[0046] The metalink tool 336 can track the listing to determine when it has matured for sale. For example, an auction may have a closing date while a classified ad is mature so long as the item is not sold. When a listing matures, the metalink tool automatically gathers the sale price, the buyer 110, the e-mail address of the buyer, the shipping amount, a listing description, a reference identifier used by the vending site, and any other information available from the vending site 140. Some embodiments automatically compose a message with an embedded snippet that is sent to the buyer 130 soliciting money from the payment enabler. The seller can customize the contents of this message in one embodiment.

[0047] With reference to FIG. 4, a block diagram of an embodiment of a vending site 140 is shown. The vending site 140 works in concert with the money transfer system 190 to allow paying the seller for whatever is offered in the listing at the vending site 140. The vending site includes a site controller 404, a web interface 408, a user database 416, and a listing database 412.

[0048] The site controller 404 manages the functions of the vending site 140. The web interface 408 allows interaction with information in the listing database 412 and user database 416. Both the sender and receiver 110, 130 interact with the web interface 408 to browse listings or enter listings. Any account information on the sender and receiver 110, 130 is stored in the user database 416. The listing database 416 stores the listings of the sellers 130.

[0049] The site controller 404 allows adding information to listings, determining contact information for a buyer, and searching for listings of a particular seller. These functions are typically meant for manual interaction through the web interface 408. The metalink tool uses these functions in an automated way to extract the information relating to transferring money. In some embodiments, the vending site 140 may have special interfaces designed for automated interaction with software robots gathering information.

[0050] Referring next to FIG. 5, a flow diagram of an embodiment of a process 500 for adding snippets to listings on the vending site is shown. The depicted portion of the process begins in step 504 where the seller 130 logs into the payment enabler 170 with a user interface 180. In step 508, a graphic is chosen that will act as a button when coupled with a link. A determination is made in step 510 as to whether the snippet will be manually or automatically inserted in listings. In this embodiment, manual insertion is done one listing at a time, but automatic insertion is done for all listings. In automatic mode, some embodiments could query the vending systems to present a column of listings that the seller 130 could select individual listings to receive the snippet.

[0051] Where a single snippet for manual insertion is selected in step 510, processing continues to step 512-1 where a web page is presented to the seller 130 for entry of information that is associated with the listing. These fields could include specification of shipping options, shipping insurance cost information, an address for the seller, tax information, an item description, a reference number, a payment enabler category, a purchase price, a phone number for the seller, a close date for the listing, and a quantity of items in the listing. Some fields, such as the purchase price may be left blank. In step 516-1, the seller 130 can enter a special message that is presented beneath the snippet or as the cursor passes over the graphic. For example, this message could say “Multiple Items Shipped at No Extra Cost” or some other message.

[0052] In step 520, the information is processed to produce a snippet. The snippet includes fields that will be used when presenting the details of the transaction to the buyer 110 for approval. The snippet is manually cut from the web page of the payment enabler 170 for pasting into the vending site in steps 528 and 532. In some cases, the seller 130 may modify the fields in the snippet. Whatever ends up in those fields is presented to the buyer in a pre-populated money transfer window when the purchase process begins.

[0053] Referring back to step 510 and the case where automatic insertion is selected, processing proceeds to step 512-2 where a potentially different set of optional fields are presented to the seller 130. With automatic snippet insertion, there are potentially many listings that are updated so fields unique to a particular listing are not entered in step 512-2. Information that is entered includes specification of shipping options, shipping insurance cost information, an address for the seller, tax information, and a phone number for the seller. Some of these fields may be pre-populated with information from the user database 324, which would allow modification by the seller 130. Most of the remaining information can be mined from the vending site 140 by the metalink tool 336. Any special instructions are entered in step 516-2. These instructions are visible in all the listings where snippets are inserted.

[0054] In step 536, login information is provided to the metalink tool 336 for all the vending sites 140 that have listings needing snippets. This login information is stored in the user database 324 for next time. They seller can enter individual listings by their identifier for each vending site 140 or can specify a global insertion for all listings associated with the login information in step 540. Some embodiments search the vending sites 140 for listings and present a web page that shows the listings and allows selection of individual listings, all listings on a particular vending site or all listings on all vending sites. In step 544, the metalink tool 336 inserts buttons into the listings specified in step 540.

[0055] With reference to FIG. 6, a flow diagram of an embodiment of a process 600 for a buyer 110 paying for goods and/or services in the listing is shown. The depicted portion of the process begins in step 604 where the listing matures. With classified advertisements, the listing matures once it appears on the vending site 140. But with most auctions, the buyer is not determined until the close of the auction period at which time the listing matures. In some embodiments, a classified advertisement can become stale when the listing is already sold or after some time period. In those circumstances, the metalink tool 336 could change the graphic to indicate unavailability or could contact the vending site 140 to remove the listing.

[0056] Once the listing has matured, the graphic for the button reflects in step 608 that payment can be made now to purchase the goods and/or services in the listing. In step 610, the metalink tool 336 gathers information about the closed listing such as final price, buyer user identifier, buyer e-mail address, etc. for storage in the user database 324. If the buyer user identifer for that vending site 140 is found in the user database, additional information can be determined for the transaction. There are three options for proceeding with payment from step 612, namely, the payor manually goes to the payment enabler, the payor uses the button to go to the payment enabler, or the payee sends a money request to the payee.

[0057] Where an automated request from the buyer 110 for money is prepared, processing continues from step 612 to step 620 where a money request message is sent to the buyer 110. In this embodiment, an e-mail message is formulated and sent, but other embodiments could use a message on a web page, an instant message, a pager message, a wireless phone message, or other electronic message to request the money. The message includes a link to the payment enabler in a snippet. The snippet has embedded information relating to the transaction, such as a shipper selection, shipping insurance cost information, an address for the seller, tax information, an item description, a reference number, a vending site identifier, a payment enabler category, a purchase price, a phone number for the seller, a close date for the listing, a quantity of items in the listing, a buyer user identifier, a buyer e-mail address, a buyer address, and/or an account number of the buyer for the payment enabler. Alternative embodiments may instead include a code that references the transaction information stored in the user database 324 such that in either case it is available to pre-populate forms for sending money.

[0058] In most cases, the payor activates the link in the snippet to direct their web browser to the payment enabler 170 and to reference transaction information. In some cases, however, the payor 110 will manually point their browser to the payment enabler 170 without the benefit of the information embedded in the snippet. In step 628, the information from the snippet and/or user database is used to pre-populate information fields for the money transfer. Things that typically are used in a person-to-person money transfer include information on the seller, on the transaction and on the buyer. Certain information available may be shielded from the buyer 110 or seller 130 to protect privacy.

[0059] In step 632, a web page is formulated to allow the authorization of sending money to the payee. All fields are populated with any gathered information, but some fields may be modifiable, such as the shipping information, money handler information, insurance for the shipping, the quantity, any special instructions to the seller, etc. Any fields that are missing information are populated by the buyer 110 in step 636. Some non-essential fields may be left blank by the buyer 110. In step 640, electronic notification is sent to the seller that payment has been received. The payment is transferred in step 644 from the money handler of the buyer to the stored value account of the seller.

[0060] As mentioned above, it is possible for the buyer to manually browse to the payment enabler 170 without using the link in the snippet by proceeding from step 612 directly to step 632. Under this circumstance, the payment enabler does not know the listing being paid for. In one embodiment, the buyer sends money to the seller in the traditional way. In another embodiment, the buyer enters a vending site and listing identifier so that information stored in the user database 324 is used to pre-populate forms. In any event, processing continues through steps 632 , 636, 640 and 644 as with the embodiment where a money request is sent to the buyer discussed above.

[0061] A third alternative from step 612 involves the buyer activating the button in the snippet on the vending site 140. After maturing, the button in the listing can be activated in step 624 as in the money request embodiment discussed above. From step 624 and beyond processing proceeds as in that money request embodiment.

[0062] Referring next to FIG. 7, a flow diagram of an embodiment 544 of a subroutine for automatically inserting snippets in listings is shown. In this embodiment, the seller 130 has chosen automatic insertion of snippets for specific listings or all listings on a one-time basis or for all listings going forward. In step 702, a determination as to whether there are only specified listing(s) or a search for listings should be done. If a search is specified, it is performed in step 704. That search can be performed on one or more vending sites 140.

[0063] Regardless of how the listings are found, information is gathered in step 708 about those listings. Information such as the type of listing, any closing date, the subject of the listing, the quantity, and any other information is gathered. The gathered information is stored in the user database 324 in step 712. For each listing found, a customized snippet is formulated in step 716. Those snippets are inserted in their respective listings in step 720. If a one-time insertion is requested, processing from step 724 ends until another request is made by the seller 130. If the seller specifies perpetual insertion, processing goes from step 724 to step 728 to wait for the next insertion cycle. In this embodiment, the insertion process is run once a day to look for and insert snippets in new listings. Other embodiments may use other periods or could have the period be specified by the seller 130.

[0064] While the principles of the invention have been described above in connection with specific apparatuses and methods, it is to be clearly understood that this description is made only by way of example and not as limitation on the scope of the invention.

Claims

1. A method for facilitating payment between a buyer and a seller with an online money transfer performed over a wide area network, the method comprising steps of: receiving login information relevant to a vending site, wherein the login information is associated with the seller; automatically determining listings at the vending site associated with the seller; generating a plurality of snippets of HTML code for the listings, wherein each snippet includes a link; and automatically inserting one of the plurality of snippets into each of the listings, wherein activating the link points a web browser to a payment enabler that can transfer money from the buyer to the seller.

2. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 1, wherein one of the plurality of snippets indicates a graphic associated with the snippet and information unique to the seller and a listing including the snippet.

3. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 1, further comprising steps of: determining the listing has matured, whereby the purchaser is fixed; and changing a button graphic displayed by the snippet to reflect the listing is available to the buyer.

4. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 1, further comprising steps of: determining one of the plurality of listings has matured, whereby the buyer is fixed; automatically determining an electronic address of the purchaser; and automatically sending a message to the electronic address of the purchaser.

5. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 4, wherein the message includes at least one of a web page, an instant message, an e-mail message, a pager message, and a wireless phone message.

6. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 4, further comprising a step of automatically determining a purchase price from the vending site.

7. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 4, wherein the message includes a snippet that points to the payment enabler and includes information relating to a listing associated with that snippet.

8. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 1, further comprising a step of determining from the vending site at least one of: a purchase price, a shipping amount, a listing description, a reference identifier used by the vending site, and an e-mail address of the buyer.

9. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 1, further comprising a step of receiving selection of a button graphic for display by the snippet.

10. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 1, further comprising steps of: receiving authorization from the buyer to debit a money handler associated with the buyer; and adding a credit in a stored value account of the seller as a result of the receiving authorization step.

11. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 1, further comprising a step of receiving at least two of a shipper selection, shipping insurance cost information, an address for the seller, tax information, an item description, a reference number, a payment enabler category, a purchase price, a phone number for the seller, a close date for the listing, and a quantity of items in the listing.

12. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 1, further comprising a step of receiving from the seller a message that is embedded in the plurality of snippets for display as part of each listing.

13. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the wide area network as recited in claim 1, further comprising a step of receiving login information relevant to a plurality of vending sites, wherein the login information for each of the plurality of vending sites is associated with the seller.

14. A method for facilitating payment between a buyer and a seller with an online money transfer performed over a computer network, the method comprising steps of: receiving login information relevant to a vending site, wherein the login information is associated with the seller; determining a listing at the vending site associated with the seller; generating a snippet of code for the listing, wherein the snippet includes a link that addresses a payment enabler; determining the listing has matured, whereby the buyer is fixed; determining an electronic address of the buyer; and automatically sending a message to the electronic address of the buyer.

15. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 14, further comprising a step of automatically inserting the snippet into the listings.

16. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 14, wherein the snippet indicates a graphic associated with the snippet and an information unique to the seller and the listing including the snippet.

17. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 14, wherein the message includes at least one of a web page, an instant message, an e-mail message, a pager message, and a wireless phone message.

18. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 14, further comprising a step of automatically determining a purchase price from the vending site.

19. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 14, wherein the message includes the link that points to the payment enabler and includes information relating to the listing.

20. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 14, further comprising steps of: receiving authorization from the buyer to debit a money handler associated with the buyer; and adding a credit in a stored value accoun t of the seller as a result of the receiving authorization step.

21. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 14, further comprising a step of receiving from the seller a unique message that is embedded in the plurality of snippets for display as part of each listing.

22. A method for facilitating payment between a buyer and a seller with an online money transfer performed over a computer network, the method comprising steps of: receiving login information relevant to a vending site, wherein the login information is associated with the seller; determining a listing at the vending site associated with the seller; generating a snippet of code for the listing, wherein the snippet comprises: a link that points to a payment enabler, and a message formulated by the seller for display to the buyer; and inserting the snippet into the listing.

23. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 22, further comprising steps of: determining the listing has matured, whereby the buyer is fixed; automatically determining an electronic address of the buyer; and automatically sending a message to the electronic address of the buyer.

24. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 23, further comprising a step of automatically determining a purchase price from the vending site.

25. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 22, further comprising a step of determining from the vending site at least one of: a purchase price, a shipping amount, a listing description, a reference identifier used by the vending site, and an e-mail address of the buyer.

26. The method for facilitating payment between the buyer and the seller with the online money transfer performed over the computer network as recited in claim 22, further comprising steps of: receiving authorization from the buyer to debit a money handler associated with the buyer; and adding a credit in a stored value account of the buyer as a result of the receiving authorization step.