Web-based payment system and method

A payment processing method comprises receiving at a host computer system payment information from a client computer, wherein the payment information relates to a payment from a consumer. The method further comprises verifying at least a portion of the payment information and storing at least a portion of the payment information in a database. The method further comprises transmitting a first electronic file comprising at least a portion of the payment information to a financial institution, thereby initiating processing of the payment and transmitting a second electronic file comprises at least a portion of the payment information to a client computing system. The method also comprises responding to a request for historical information by transmitting to a user computer system a third electronic file comprising at least a portion of the payment information.

BACKGROUND OF THE INVENTION

This invention relates generally to the field of financial transactions. This invention relates more particularly to systems and methods for collecting payment information from consumers and processing payments through electronic funds transfers.

Merchants often provide products and/or services to consumers in return for a promise to pay in the future. However, consumers sometimes do not fulfill their obligation and a certain portion of a merchant's accounts receivable goes unpaid. In attempting to collect on its accounts receivable, a merchant typically weighs the cost of further efforts to collect from a consumer against the amount owned by the consumer and the likelihood that the additional efforts will be successful.

Electronic funds transfers provide a convenient method for collecting money from consumers. For example, if a merchant engages a collector to obtain payment from a consumer, the collector may contact the consumer by phone and obtain payment account information and receive permission from the consumer to process a transaction. However, a consumer attempting to avoid an obligation may provide false or inaccurate information to the collector. Further, unbeknownst to the collector, the consumer may have avoided this or similar obligations in the past, also by providing false information. Thus, systems and methods are needed that provide instant verification of payment account information and compile historical payment information that may be used to detect efforts to circumvent payment of debts. Such systems and methods generally also would make debt collection more efficient.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention thus provide a payment processing system having a host computer system configured to receive payment information via a network from a client computer, a data storage arrangement configured to store the payment information, and a settlement engine. The settlement engine is configured to receive payment information from the host computer system, initiate payment processing by transmitting a file comprising at least a portion of the payment information to a first financial institution, and transmit a message to a client computing system. The message includes at least a portion of the payment information. The settlement engine may be configured to receive payment information from the data storage arrangement. The host computer system may be configured to respond to requests for historical payment information by transmitting an electronic file to a user computer. The electronic file may include payment information. The electronic file may include payment information from a particular consumer covering a specified period of time. The electronic file may include payment information to a particular client covering a specified period of time.

In another embodiment, a payment processing method includes receiving at a host computer system payment information from a client computer. The payment information relates to a payment from a consumer. The method also includes verifying at least a portion of the payment information, storing at least a portion of the payment information in a database, transmitting a first electronic file comprising at least a portion of the payment information to a financial institution, thereby initiating processing of the payment, transmitting a second electronic file comprises at least a portion of the payment information to a client computing system, and responding to a request for historical information by transmitting to a user computer system a third electronic file comprising at least a portion of the payment information.

The method also may include initiating an electronic transfer of funds to a client's financial institution representing the payment. The method also may include receiving an electronic transfer of funds from a consumer's financial institution representing the payment. The electronic transfer of funds to a client's financial institution may be initiated prior to receipt of the electronic transfer of funds from a consumer's financial institution. The method also may include receiving an electronic message comprising a rejection of the payment from a consumer's financial institution. The method also may include initiating an electronic withdrawal of funds from the client's financial institution. The method also may include transmitting to the client computing system a fourth electronic file that includes revised payment information. The third electronic file also may include payment information from a particular consumer covering a specified period of time. The third electronic file may include payment information to a particular client covering a specified period of time. The first electronic file may include additional payment information from a least one additional customer. The first electronic file may include information representing a rejection of an attempt to withdraw funds from a consumer's financial institution.

The payment information may include a checking account of the consumer from which the payment is to be made. The payment information may include a credit card account of the consumer from which the payment is to be made. The payment information may include a debit card account of the consumer from which the payment is to be made. The step of verifying at least a portion of the payment information may include contacting the client's computer system to obtain information relating to the payment information. The step of verifying at least a portion of the payment information may include consulting an electronic file provided by a client to obtain information relating to the payment information. The step of verifying at least a portion of the payment information may include using an algorithm specified by a client to evaluate at least a portion of the payment information. The step of using an algorithm specified by a client to evaluate at least a portion of the payment information may include checking the arrangement of numbers in an account number of the payment information. The step of verifying at least a portion of the payment information may include consulting a third party service to verify an ABA routing number of the payment information. The third party service may be provided by Thompson Financials.

DETAILED DESCRIPTION OF THE INVENTION

The present invention provides a payment processing system that may be accessed and used via the Internet or other network. The system provides the capability for servicing a number of clients simultaneously. Historical information is compiled, which assists the process of collecting from consumers. Built in verification processes further simplify the process of collecting from consumers and frustrate attempts by consumers to provide false or inaccurate information.

According to the present invention, an operator of a payment processing system provides access to its clients or their representatives via a network, such as the Internet. Clients may include retailers, banks, utility companies, or other such merchants that routinely provide merchandise or services to consumers on credit. The clients may use the system to provide a convenient method for their consumers to pay their debts, or the clients may use the system particularly for collecting on past due accounts. In either case the clients or third parties, such as collectors, acting on behalf of the clients, attempt to contact a consumer with an outstanding account balance. (Hereinafter, the term “collector” will be understood to refer to a person employed by a client working exclusively for the client, or a person not directly employed by a client but working on the client's behalf. A collector also may work for a number of different clients.) Collectors typically contact consumers by telephone, although different methods for contacting consumers is certainly possible. Once the collector is in contact with the consumer, the collector may obtain payment information from the consumer.

Payment information may include a checking account number and a bank identification number, such as an ABA (American Banking Association) number or Routing and Transit number. Additionally or alternatively, the payment information could include a credit card number or other account number that allows non-signatory payment authorization (e.g., telephone authorization). Other payment information may include the consumer's name and address, the client's name and address, a payment date, and the like. The collector assimilates the payment information by entering it into data fields of display screens transmitted by a host computer system to a computer used by the collector. The display screens may comprise web pages, and the collector may use a web browser to view the pages and interact with the host computer system that generates the web pages. As the data is entered, for example, as each data field is completed or as a page of data is completed, the data is transmitted to the host computer system.

As the host computer system receives the payment information, the host computer system may verify some or all of the information. Thus, if a consumer provides the collector with false, misleading, or inaccurate information, the collector may request correct information while still in contact with the consumer. Because some consumers having past due accounts may be notoriously difficult to contact, the present invention is particularly useful to clients because it may help to avoid needless repetition. For example, a collector having the means of the present invention to verify payment information in real time does not have to repeatedly contact the consumer to get revised information. If the consumer is providing incorrect information, in many cases, the collector knows right away. Further, being able to verify information also allows the collector to assess whether the consumer is truly attempting to satisfy an obligation. If a consumer continues to provide useless payment information, then the client is sooner able to transfer a past due account to the next stage of collections. Thus, the present invention may significantly reduce the amount of time wasted attempting to contact delinquent consumers and then re-contacting those consumers over the course of weeks or months attempting to get reliable payment information, only to eventually find out that the account must be written off. Of course, the verification process of the present invention also streamlines collection from paying clients who mistakenly provide inaccurate payment information.

In addition to verifying the validity of account numbers, balances, and the like, the present invention also may evaluate a consumer's payment history. For example, because the present invention stores historical payment information relating to consumers, a collector may be able to view a consumer's history with respect to NSF checks. As with a paper check, a checking account debit via an electronic funds transfer also may result in a return due to insufficient funds being in the consumer's checking account to cover the amount of the payment. Thus, if the consumer accumulates a history of NSF checks, collectors may be required to collect from consumers using other means, such as credit cards, or obtain a supervisor's approval.

Once acceptable payment information is received, the present invention initiates an electronic funds transfer to collect the funds from the consumer's bank and deposit the funds in a client's bank. Transfers may involve the federal funds network, the ACH (Automated Clearing House) network, or other acceptable electronic funds transfer system. Further, the present invention may include processes for complying with various federal and state laws regulating electronic funds transfers, particularly telephone-authorized transfers. For example, the present invention may cause a confirmation letter to be printed and sent to a consumer following an authorization by the consumer to transfer money from the consumer's checking account.

In addition to initiating the electronic funds transfer, the present invention also may be configured to transmit payment information directly to a client's accounting system. This further simplifies the collection process for clients. In some embodiments, operators of the present invention may transfer funds to the client's bank even before the operator receives the funds from the consumer's bank. Of course, the operator may need to withdraw the funds from the client's bank if the operator does not eventually receive payment from the consumer's bank. However, according to the present invention, transfers among financial institutions may be consolidated, thus lowering the cost to complete the transactions.

Many additional features are included in some embodiments of the present invention. For example, the present invention provides collectors the ability to schedule future payments, and to modify or cancel, pending payments. Also, the present invention provides authorized users with the ability to view historical information relating to certain clients and consumers. Further, operators of systems according to the present invention may customize various features to suit the needs of their clients, and different clients may have different features.

Having described the present invention generally, attention is directed toFIG. 1, which illustrates one possible embodiment of a system according to the present invention. However, those skilled in the art will realize a number of possible configurations for systems according to the present invention that differ from the system ofFIG. 1. Thus, the system ofFIG. 1should be considered a non-limiting example.

FIG. 1illustrates a web-based payment system100according to the present invention. The system100includes a host computer system102. The host computer system102may be, for example, a server computer, a personal computer, a workstation, or other suitable computing device. The host computer system102includes application software that programs the host computer system102to perform one or more methods according to the present invention. For example, application software resident on the host computer system102may program the host computer system102to act as a web site server.

The system100also includes a first network104. The network104may be the Internet, an intranet, a wide area network (WAN), a local area network (LAN), a virtual private network, any combination of the foregoing, or the like. Through the network104, collectors106may access the host computer system102.

The collectors106act on behalf of clients to collect funds from consumers108. Collectors106may be employed by clients as employees or contract agents, for example. Collectors106, particularly contract collectors, may work for multiple clients simultaneously. The clients may be merchants, financial institutions, or other entities owed money by consumers. Thus the clients of the web-based payment system operator are creditors of the consumers/debtors from whom payment is sought.

A collector106may access the host computer system102using any suitable computing device. The network connection may be a wired connection or a wireless connection, as is known in the art. Also as is known in the art, the host computer system102may transmit electronic files comprising web pages to be displayed on a display screen for viewing by the collector106. The collector106then may enter data into data fields on the web pages and transmit the data back to the host computer system102. This process will be explained further hereinafter.

Collectors106may contact consumers108through, for example, a telephone network109, or the like. If a collector106is successful obtaining payment information from a consumer108, then the collector106enters the payment information into appropriate data fields of the web pages. The payment information may include, for example, an ABA routing number, an account number, name and address information, a payment amount, and the like. Once entered, the information is transmitted to the host computer system102.

Once payment information is received, the host computer system102may store the information in a suitable storage arrangement associated with the host computer system102, such as a database110. The information is then used by a settlement engine111to initiate the necessary transactions among the appropriate accounts. The settlement engine111may be a separate computing device from the host computer system102. The two computing devices may be co-located, or may be connected from different locations via a network. In some embodiments, the settlement engine111comprises software residing on the host computer system102that programs it to perform functions according to the present invention. For example, through a second network112, the settlement engine111may send an electronic file comprising the transaction information to a financial institution114associated with the operator of the system100. The operator's financial institution114or ODFI (Originating Depository Financial Institution) may be any of a number of financial institutions, such as a bank, a savings & loan, or the like. The second network112may be any appropriate communications network. In some embodiments, the second network112is the ACH network.

The ODFI114, through the federal funds network, obtains the funds from a consumer's bank116, and deposits the funds into a client's bank118. The process of transferring funds through the federal funds network is well known. However, in some embodiments of the present invention, the operator may deposit funds relating to a transaction into the client's bank118before the operator receives the funds from the consumer's bank116. Thereafter, it may become necessary for the operator to reverse such transactions. For example, if a consumer does not have the necessary funds, the operator may be required to withdraw the funds from a client's bank118.

The settlement engine111also may send transaction information to a client's computing system120. This allows the client to properly account for the funds collected and allocate the funds to the appropriate consumer's account.

The system100also includes a third network122through which access terminals124may interface with the host computer system102. The access terminals124may be any suitable computing device. They may reside at one or more operator sites, client sites, collector sites, or the like. Appropriate security features may prevent access by unauthorized users, or allow various levels of access to authorized users. The access terminals124may be used to generate reports from the system100, to perform maintenance on the system100, and to accomplish other functions related to the present invention. The third network122may be any suitable communications network, such as those previously described. In some embodiments, the first, second, and third networks104,112,122, may comprise the same network.

Having describe a web-based payment system100according to the present invention, a method of performing web-based payments according to the present invention will be described.FIG. 2Aillustrates such a method200. The method200begins at operation202when the host computer system102receives a request, such as from a collector106, to access the system. In response, at operation204, the host computer system102transmits a file comprising a Login display screen300ofFIG. 3. The Login display screen300includes a Login ID data field302, a Password data field304, a Login button306, and a Reset button308.

As mentioned previously, the login procedure may include security features that prevent unauthorized access, and/or provide various levels of user access. For example, the web address (i.e., URL) may be unique to each client, and only pre-authorized IP addresses may be allowed to access the URL. Other examples are possible.

At operation206, the host computer system102receives the login information. Depending on the login information, the host computer system102may allow or deny access. If access is allowed, depending on the user identified by the login information, the host computer system102may transmit a Payment Search display screen400(FIG. 4) or a Select a Company display screen500(FIG. 5). For example, if a collector works on behalf of many different creditors, the collector then may be required to select one of the creditors from a dropdown menu502ofFIG. 5to indicate which client the collector is currently working for. In this case, the host computer system102transmits the select company page500at operation208and receives a selection at operation210. If the collector works on behalf of only one client, then operations208and210may not be necessary. In either case, once a client is identified, the Payment Search display screen400is transmitted by the host computer system102at operation212. The Payment Search display screen400identifies the name402of the client.

At operation214, the host computer system102receives a selection from a collector (or other user). For example, using a button on the Payment Search display screen400, a collector may elect to initiate a new payment at operation216(New button404), schedule a future payment at operation218(Future button406), modify or delete a pending payment at operation220(Pending button408), or view a history of processed payments at operation222(History button410). Additionally, a collector or other user may: logout by selecting a Logout button412at operation224; select a different company using the Select a Company button414at operation226; return from another display screen to the Payment Search display screen400by selecting the Payments button416at operation228; search for payments or other information by selecting the Search button418at operation230; print reports by selecting the Reports button420at operation232; create, view, or update administrative features by selecting the Administration button422at operation234; obtain help by selecting the Help button424at operation236; and/or log back into the system (for example if logged off due to time out) by selecting the Login button426at operation238. As mentioned previously, security features may be used to control access to the function described above. Further, many of these functions may be available from other display screens. Some of the functions may require the collector to enter a consumer account number in an Account Number field428.

If the collector or other user selects the Logout button412, the host computer system102may transmit a Logout display screen600(FIG. 6) at operation224to be displayed at the collector's or other user's computing device. The Logout display screen600also may appear in response to the collector being logged off due to a timeout, for example, which may occur after a predetermined period of inactivity.

FIG. 2Billustrates the Initiate a New Payment operation216in greater detail, according to some embodiments of the present invention. As mentioned previously, some of the selections from the Payment Search display screen400may require entering a consumer account number in the Account Number field428. Thus, at operation250the host computer system102verifies the consumer account number. If the account number if not valid, the host computer system102may transmit an invalid account display screen, such as the Supervisor Authorization display screen700ofFIG. 7. Depending upon the reason for invalidity, it may be possible to continue with the process of initiating a new payment.

An account number may be verified in any of several ways. For example, the host computer system102may transmit account information to the client's computing system for verification. In other embodiments, a file may be sent to a third party site related to the client. In still other embodiments, the client periodically may supply files containing valid and/or invalid account numbers that the host computer system102stores and uses to verify accounts prior to processing payments. Further still, client-defined algorithms may be used to verify account numbers. Many other examples are possible.

Once an account number is validated or approved, the host computer system102may transmit an Initiate a New Payment display screen800(FIG. 8) at operation252. At this point, it may be the case that a collector, such as a client customer service representative, has contacted a consumer/debtor and obtained authorization to initiate a payment from the consumer to the client/creditor. Thus, the Initiate a New Payment display screen800includes a number of data fields to be completed to initiate the transaction. The data fields include: Name802and Address804, ABA Routing Number806; Account Number808; and Payment Amount810data fields.

In some embodiments, some of the data fields may be pre-populated with information relating to the consumer and/or client. For example, a Pay to the Order Of field812may be pre-filled with the client's name. In other embodiments, information may be returned to the host computer system102upon verification of the account number. The consumer's Name and Address field802,804may be completed in this way. In some embodiments, information may come from a client's computing system120. The information may have been supplied previously, or the information may be obtained real time from the client's computing system120, or a third party computing system related to the client. In still other embodiments, information may be obtained from history files associated with the host computer system102, having been stored previously, for example, at the database110. Payment information may be supplied in this manner. For example, if the consumer previously paid by credit card, the consumer's credit card number may appear in the Account Number field808, although some of the digits may be masked. In yet other embodiments, other information may be supplied in response to the entry of certain information, for example, supplying the city and state from a database upon the entry of a zip code. Other embodiments are possible, including any combination of the foregoing.

The ABA Routing Number field806and the Account Number field808may comprise a MICR line814, similar to those found on a paper check. As this information is entered by the user, verification systems may be used to verify account numbers, account balances, account status, and the like. For example, a service, such as that provided by Thompson Financials, may be used to verify a bank name once the consumer supplies an ABA routing number. Further, credit card accounts may be verified and/or debited as the information is entered by the user. In any of the foregoing examples, warning screens may be used to provide the user with information relating to the success or failure of attempts to charge and/or verify accounts and account information. Verification of payment information is shown as operation254.

In some embodiments, consumers are changed a fee for payments made according to the present invention. In other embodiments, no fee is charged. In still other embodiments, a drop down menu812may be used to selectively waive a fee. Embodiments that include an ability to waive a fee also may include a data filed or drop-down menu for selecting or providing a reason for waiving a fee. Further to such embodiments, fee waivers may require supervisor approval, in which case additional display screens may be included for requesting and receiving supervisor approval for fee waivers.

A collector may add additional payments from the same consumer by selecting an Add Payments button814, abort the transaction by selecting a Cancel button816, or initiate the payment according to the information in Initiate a New Payment display screen800by selecting a Continue button818. If the collector selects the Add Payments button814, shown as operation256, an Additional Payments display screen900(FIGS. 9A and 9B) is displayed, which has data fields similar to the ones discussed above for including additional payment information.

Selecting the Continue button820causes a New Payment Confirmation display screen1000(FIG. 10) to be displayed at operation260. The New Payment Confirmation display screen1000includes a Payment Information Confirmation section1002, a Confirm button1004, a Modify button1006, and a Cancel button1008. A user, such as a client CSR, may confirm the transaction by selecting the Confirm button1004at operation262, in which case a New Payment Final Confirmation display screen1100(FIG. 11) is displayed at operation264. Selecting the Modify button1006causes the Initiate a New Payment display screen800(FIG. 8) to be redisplayed, or the Additional Payments display screen900(FIGS. 9A and 9B), if multiple payments are being confirmed. This allows the user to modify any incorrect information. Selecting the Cancel button1008aborts the transaction. The New Payment Final Confirmation display screen1100(FIG. 11), includes a Payment Summary area1102and a Return to Main Menu button1104. Selecting the Return to Main Menu button1104causes the Payment Search display screen400(FIG. 4) to be displayed, from which additional payments or other functions may be selected. Selecting the Confirm button1004also causes the payment information to be stored at operation266and initiates a Process Transaction operation at operation268.

The Process Transaction operation268is illustrated in greater detail inFIG. 2C. The operation may take place immediately upon confirmation of the transaction, or may be performed as part of a batch process, having been consolidated with other, potentially related transactions. At operation270transaction information is sent to a client computer system120. This operation may result in transaction information being posted directly to consumers' accounts at the client computer system. At operation272transaction information is sent to the system operator's ODFI. The ODFI may be, for example, the operator's bank. In some embodiments, the ODFI transfers funds to the client's financial institution at operation274even before the ODFI receives funds from the consumer's financial institution. The ODFI initiates an electronic funds transfer through the Federal Funds Network, or similar electronic funds transfer network, at operation276by sending transaction information to the consumer's financial institution. This operation276may involve first sending the transaction information to a clearing bank, depending on the procedures used by the electronic funds network being used.

In some circumstances, funds are later received through the funds network from the consumer's financial institution at operation278. However, in some circumstances, the consumer's financial institution rejects the transaction at operation280, for example, because the consumer has stopped payment, does not have the funds in his account, or the like. In these instances, the ODFI requests a return of funds from the client's bank at operation282, and sends an adjustment to the consumer's account in the client's computer system at operation284. In either of the above cases, the payment information is revised accordingly and saved at operation286.

As mentioned previously, according to embodiments of the present invention, several transactions may be consolidated prior to initiating transactions through the funds network. This reduces the charges associated with processing such transactions. For example, a number of payments may have been processed for a particular client in a given processing period. During the same period, one or more payments processed in previous periods may have been rejected by consumers' financial institutions. In such cases, the funds deposited (or withdrawn) from the client's financial institution may represent the net result of the two. This process further reduces the transaction processing costs.

Attention is redirected to the Payment Search display screen400ofFIG. 4for a discussion of other selection alternatives. The schedule a Future Payment button406causes a Schedule a Future Payment display screen1200(FIG. 12) to be displayed. From the Schedule a Future Payment display screen400, a user may enter future payment information using data fields similar to the data fields of the Initiate a New Payment display screen800(FIG. 8). However, the Schedule a Future Payment display screen1200includes a date field1220for scheduling the data for the future payment to be processed. An Add more Payments button1214functions similarly to the Add More Payments button814(FIG. 8), causing an Add Additional Future Payments display screen1300, (FIGS. 13A and 13B) to be displayed. A Future Payment Confirmation display screen1400(FIG. 14) and a Future Payment Final Confirmation display screen1500(FIG. 15) function similarly to analogous display screens in the Initiate a New Payment process.

Selecting the Pending button418ofFIG. 4causes the host computer system102to return a Pending Payments display screen1600ofFIG. 16for the consumer account identified in the Account Number data filed428of the Payment Search display screen400. The Pending Payments display screen1600includes a list of pending transactions1602relating to the consumer's account. A transaction may be selected using radio buttons1604. Once selected, a collector or other user may modify the transaction by selecting a Modify Selected Payment button1606, or delete the transaction by selecting the Delete Selected Payment button1608.

Selecting the Delete Selected Payment button1606causes the host computer system102to return the Delete Payment Confirmation display screen1700ofFIG. 17. Deletion is confirmed by selecting the Confirm Payment Deletion button1702. In some embodiments, supervisor approval may be required to delete the transaction. In such embodiments, which may be customized according to the requirements of particular clients, the Supervisor Approval to Delete Payment display screen1800may be returned by the host computer system102upon selection of the Confirm Payment Deletion button1702. A supervisor then may enter his supervisor login into a Supervisor Login data field1802and select a Continue with Delete Payment button1804to approve the deletion. Alternatively, the supervisor may select a Cancel Request button1806to abort the transaction deletion. Once a transaction deletion is confirmed, a Delete Payment Final Confirmation display screen1900ofFIG. 19is returned by the host computer system102.

A pending transaction may be modified by selecting the transaction from the list of pending transactions1602(FIG. 16) and selecting the Modify Selected Payment button1606. In response, the host computer system102returns the Modify A Pending Payment display screen2000ofFIG. 20. The display screen2000includes a number of editable data fields containing the payment information relating to the selected transaction. A collector or other user may edit the information accordingly and transmit the changes to the host computer system102by selecting a Continue button2002. In some embodiments, information may be masked for security purposes, such as the bank account number in the Bank Account # data field2004. Further, in still other embodiments certain payment information may not be editable for a pending payment. In this example, the fee2006is not editable. Other such examples are possible. The collector may abort the modifications by selecting a Cancel button2008.

Upon selection of the Continue button2002, the host computer system102returns a Modify a Pending Payment Verification display screen2100ofFIG. 21. The display screen2100includes the modified information for review prior to final confirmation. The information may be confirmed by selecting the Confirm button2102. The transaction may be modified by selecting a Modify button2104, which returns the user to the Modify A Pending Payment display screen2000ofFIG. 20. The modification may be aborted by selecting a Cancel button2106.

Selection of the History button410ofFIG. 4causes the host computer system102to return a Payment History display screen2200ofFIG. 22for the consumer account identified in the Account Number data filed428of the Payment Search display screen400. The display screen2200includes a list of transactions2202relating to the consumer. The list may include all transactions ever processed relating to the consumer, or may include only those transactions going back a predetermined period of time. The operator may customize the period of time to suite the needs of particular clients. Further, the information displayed in the list2002may be customized for clients by the operator. In some embodiments, the user may obtain more detailed information relating to a transaction by selecting, or “drilling-down” on the transaction. The user may return to the Payment Search display screen400by selecting a Return to Main Menu button2004.

Selecting the Search button418causes the host computer system to return a Payment Search display screen2300ofFIG. 23. Pending and historical payments may be searched using may different criteria. Payments may be searched by entering a consumer's account number in an Account Number field2302. The search may be limited further by entering a date range into Activity Date fields From2304and To2306. Additionally or alternatively, payments may be searched by entering a specific transaction confirmation number in a Transaction Confirmation Number data field2308. Selecting a Search button2308causes the host computer system102to return transactions matching the specified criteria. Selecting a Cancel button2310aborts the search.

Selecting the Reports button420causes the host computer system102to return a Reports display screen2400. Many different types of reports may be provided, and the types of reports may be customized by the operator to satisfy the needs of particular clients. Each report may include data range fields2402to limit the reports to specified periods of time. The fields may default to particular dates, depending upon the particular field. Filtering capability also may be provided by selecting a filter from a drop down menu2404to further limit a report to particular transactions. Filters may include, for example, Login ID, Payee, Payment Type, and the like. Selecting a View button causes the corresponding report to be returned by the host computer system102. In the returned reports, hyperlinks may allow the user to drill-down into more detailed information summarized in the report. A Completed Transactions report may include the total number and dollar value of transactions processed and the number of transactions returned. A Pending/Future-dated Transactions report may include the total number and amount of transactions pending for a particular day or date range. A Deleted transactions report may include the total number and amount of transactions deleted on a particular day or within a date range. A Returned Items report may include the total number and amount of returned transactions for a particular day or date range. Additional filters in for this report may include a reason for return. A Fee Waive for Date Range report may include total consumer fees collected and waived, sorted by collector or user, for a specific data range. A Fee Waive by Reason Waived report may include the total number and dollar amount of consumer fees waived by waive reason. Additional filters for this report may include a reason code. Many other reports are possible.

Selecting the Administration button422causes the host computer system102to return an Administration display screen2500ofFIG. 25. The ability to change administrative features may be customized according to the requirement of particular clients. Thus, a Super User Login data field2502and Super User Password data field2504may be provided for security purposes. Authorized users may accomplish a number of administrative functions, including: updating and viewing user information by selecting a Update/View Users button2514; create new users by selecting a Create New User button2506; and edit group relationships by selecting the Edit Group Relationships button2508. Many other administrative functions are possible.

Having described several embodiments, it will be recognized by those of skill in the art that various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the invention. Additionally, a number of well known processes and elements have not been described in order to avoid unnecessarily obscuring the present invention. For example, those skilled in the art know how to arrange computers into a network and enable communication among the computers. Additionally, those skilled in the art will realize that the present invention may: display information in languages other than English; provide clients the option to specify expiration periods for security and other information; process payments using forms of payments other than credit cards and bank accounts; provide reports of information according to client specifications; filter specified information from reports; and conform to particular state laws relating to the processing of payments and the fees that may be charged for doing so. Accordingly, the above description should not be taken as limiting the scope of the invention, which is defined in the following claims.