SYSTEM AND METHOD FOR SETTLING MULITPLE PAYEES FROM A SINGLE ELECTRONIC AND/OR CHECK PAYMENT

Abstract

A system and method is disclosed that facilitates electronic payment to multiple payees from a single electronic payment transaction and/or from a multiple payee check payment. The system includes a database storing payor and payee identity, address, and bank account information and a processor that executes instructions causing the processor to initiate a multiple payee payment and/or a multiple payee check handling and clearing process including determining identity of the payor and/or receiving the payor's check information; receive identification of multiple payees; place a hold on a payor's bank/card account and/or accept multiple payee check deposit via an ATM; alert respective payees that funds are available; enable payee electronic check endorsement and/or identity verification for the respective payees; receive electronic payee endorsement and confirmation of identity and provide an endorsement file to the payor for each payee; debit the payor's account in respective amounts owed the respective payees; and disburse the respective amounts to the respective payees through a payment network.

Claims

1. A system for facilitating electronic payments of a multiple payee payment, comprising: at least one remote server establishing secure communication with an electronic payor account and a plurality of electronic payee accounts; a secure database connected to the server, the database comprising transaction records, payor account information, and payee account information; a computing device securely connected to the remote server, the computing device comprising a processor and a memory having instructions that, when executed by the processor, cause the computing device to at least: authenticate a multiple payee payment to be disbursed from the electronic payor account to at least one of the plurality of electronic payee accounts; determine a payment distribution comprising a payment to each of the electronic payee accounts, based on a value of the multiple payee payment and information stored at the secure database; and initiate payment disbursements to each of the plurality of electronic payee accounts according to the payment distribution and update the database with a new transaction record.

2. The system of claim 1, wherein the instructions that cause the computing device to authenticate the multiple payee payment comprise at least one of: placing a hold on the electronic payor account; and establishing an endorsement of the multiple payee payment by one or more payees.

3. The system of claim 1, wherein establishing the endorsement comprises receiving at least one of an electronic verification and an identification verification from each payee of the multiple payee payment.

4. The system of claim 3, wherein the identification verification is an electronic signature.

5. The system of claim 1, wherein determining the payment distribution comprises at least one of: receiving a designation at the server, from at least one authorized user associated with a payor or payee, specifying a payment amount for each of the electronic payee accounts; and receiving, at the server, a confirmation specifying the payment amount.

6. The system of claim 1, wherein determining the payment distribution comprises: processing a payment amount of the multiple payee payment; verifying endorsement of the payees; processing a redirection request of a payee, each redirection request assigning an endorsed payment amount of the payee to another payee of the multiple payee payment; and determining an updated payment amount to each payee.

7. The system of claim 1, further comprising: negotiating, by the payees, stakes of the multiple payee payment for each payee; and initiating, by at least one payee, a payment redirection request.

8. The system of claim 1, further comprising a notification system for alerting at least one of a payor and payee regarding one or more of: a payment status, an endorsement status, an account hold status, a request for information, and a debit or credit to an account.

9. The system of claim 8, wherein the notification systems sends alerts via one or more of: an email, a text message, a SMS message, a phone call, and a mobile device notification.

10. The system of claim 1, further comprising at least one of an automated clearing house (ACH) system and an electronic payment network configured to establish a secure connection with the remote server and facilitate payment disbursements to each of the plurality of electronic payee accounts according to the payment distribution.

11. The system of claim 1, wherein the secure database further comprises at least one of: multiple payee payment authentication information, payment distribution determinations, and payment disbursement records.

12. The system of claim 1, wherein the payor account information and payee account information each comprise information related to one or more of: name, address, account number, claim activities, benefits, surrender requests, and insurance policy information.

13. A method for facilitating electronic payments of a multiple payee payment, comprising: receiving, at a remote server, an electronic multiple payee payment to be disbursed from an electronic payor account to a plurality of electronic payee accounts; authenticating the multiple payee payment, the authenticating comprising verifying an electronic endorsement from each of the plurality of payees; determining a payment distribution comprising a payment to each of the electronic payee accounts, based on a value of the multiple payee payment and information stored at a secure database, wherein the database comprises transaction records, payor account information, and payee account information; initiating payment disbursements to each of the plurality of electronic payee accounts according to the payment distribution; and updating the secure database with a new transaction record.

14. The method of claim 13, wherein authenticating the multiple payee payment comprises at least one of: placing a hold on the electronic payor account; and verifying the electronic endorsement from each of the plurality of payees, the electronic endorsement being an identification verification from each payee.

15. The method of claim 13, wherein determining the payment distribution comprises at least one of: receiving a designation at the server, from at least one authorized user associated with payor or payee, specifying a payment amount for each of the electronic payee accounts; and receiving, at the server, a confirmation specifying a payment amount.

16. The method of claim 13, wherein determining the payment distribution comprises: processing a payment amount of the multiple payee payment; verifying endorsement from the payees for the endorsed payment amount; processing a redirection request of a payee, each redirection request assigning a respective payee's endorsed payment amount to another payee of the multiple payee payment; and determining an updated payment amount to each payee.

17. The method of claim 13, further comprising notifying at least one of a payor and payee regarding one or more of: a payment status, an endorsement status, an account hold status, a request for information, and a debit or credit to an account.

18. The method of claim 13, wherein the electronic multiple payee payment comprises at least one of: an image, manually-entered information, a scanned document, and information received from an populated form.

19. The method of claim 13, wherein the payor is at least one of: a financial institution, an insurance carrier, a mortgage holder, a lienholder, and a policy claimant.

20. The method of claim 13, further comprising initiating payment disbursements to each of the plurality of electronic payee accounts according to the payment distribution, and update the database with a new transaction record.

21. The method of claim 13, further comprising negotiating, by the payees, stakes of the multiple payee payment for each payee; and initiating, by at least one payee, a payment redirection request.

22. A non-transitory computer-readable medium having instructions stored thereon, that when executed by a processor, causes the processor to at least: receive an electronic multiple payee payment to be disbursed from an electronic payor account to a plurality of electronic payee accounts; authenticate the multiple payee payment by at least verifying an electronic endorsement from each of the plurality of payees; determine a payment distribution comprising a payment to each of the electronic payee accounts, based on a value of the multiple payee payment and information stored at a secure database, the database comprising transaction records, payor account information, and payee account information; and initiate payment disbursements to each of the plurality of electronic payee accounts according to the payment distribution.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0028] The above and other objects and advantages of the invention will be apparent to those skilled in the art based on the following detailed description in conjunction with the appended figures, of which:

[0029] FIG. 1 illustrates a conventional single payee payment system.

[0030] FIG. 2 illustrates a multi-payee payment system of an exemplary embodiment of the invention.

[0031] FIG. 3 illustrates a fully integrated multi-payee payment system of FIG. 2 as used to facilitate multiple payments by an insurance carrier.

[0032] FIG. 4 illustrates a fully integrated multi-payee payment system of FIG. 2 as used to facilitate multiple payments by a payor.

[0033] FIG. 5 illustrates a partially integrated third-party multi-payee payment system as used to facilitate multiple payments by an insurance carrier in the context of a conventional ACH payment system.

[0034] FIG. 6 illustrates a partially integrated third-party multi-payee payment system as used to facilitate multiple payments by a payor in the context of a conventional ACH payment system.

[0035] FIG. 7 illustrates multi-payee e-payment and multi-payee check e-payment in an exemplary embodiment.

[0036] FIG. 8 illustrates multi-payee e-payment debits and disbursements in an exemplary embodiment.

[0037] FIG. 9 illustrates fully integrated multi-payee account hold in an exemplary embodiment.

[0038] FIG. 10 illustrates multi-payee payment notification in an exemplary embodiment.

[0039] FIG. 11 illustrates multi-payee payment endorsement and authentication in an exemplary embodiment.

[0040] FIG. 12 illustrates multi-payee payment notification for insurance claims in an exemplary embodiment.

[0041] FIG. 13 illustrates an ATM multi-payee check deposit in an exemplary embodiment.

[0042] FIG. 14 illustrates a document exchange process in an exemplary embodiment.

[0043] FIG. 15 illustrates a sample hardware platform for implementing the system and method of the exemplary embodiments.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0044] Exemplary embodiments of an electronic multi-payee payment system are described below with respect to FIGS. 1-15. Those skilled in the art will appreciate that the steps described are for exemplary purposes only and are not limited to the specific process described.

[0045] FIG. 1 illustrates a conventional single payee payment system 10. As illustrated, a payor 11 uses his/her financial institution or other payment/banking network 12 to initiate an integrated money transfer to a single payee 15 through a payment system 13 such as an automated clearing house (ACH), debit or credit card network, RTP network, etc. The payment system 13 provides payment to a financial institution 14 of the payee 15. In operation, the financial institution/money transmitter 12 collects the payor's funds and processes the single payee payment through the payment or banking networks 13 and payment is provided to the single payee's bank 14. The funds are credited to the payee's account 15. In this system, if the payor 11 needs to pay other payees, the payor 11 uses his/her financial institution 12 to initiate additional transfers for each additional payee 15. In each instance, the financial institution/money transmitter 12 collects the payor's funds and processes the payment for transfer to a single payee. If it is a multiple payee payment that is also a multiple stakeholder payment, then the payment cannot be processed by the system as a paper check will have to be issued. As noted in the background section above, such conventional systems only permit a single payment to a single entity at a time and are very inefficient, particularly for businesses and individuals who routinely pay multiple payees.

[0046] FIG. 2 illustrates a multi-payee payment system of an exemplary embodiment of the invention. In the embodiment of FIG. 2, an Mroute payment system 20 in accordance with the invention processes a multi-payee payment from the financial institution 21 of payor 11 and provides the payees 25-27 the option of choosing a desired account in which to have their individual stake deposited. The Mroute payment system 20 implements the payment to multiple accounts using a NEDD (Notification, Endorsement, Debits, Disbursements) protocol as described herein to process and route funds to the financial institutions 22-24 of multiple payees 25-27. In operation, a credit is made to Payee 1 via the payee's financial institution 22, a credit is made to Payee 2 via the payee's financial institution 23, and a credit is made to Payee 3 via the payee's financial institution 27 in accordance with the processes described in more detail below.

[0047] The Mroute payment system 20 may be used as an integrated (i.e. standalone) system or may be partially integrated (i.e. works in conjunction with another payment system) in many different systems where simultaneous payment to multiple payees is desired. For example, FIG. 3 illustrates a fully integrated multi-payee payment system 20 as used to facilitate multiple payments by an insurance carrier 30. As illustrated, the insurance carrier 30 communicates with the Mroute payment system 20 to provide payment alerts and to receive endorsement files and, optionally, to exchange a proposed workflow arrangement. The insurance carrier's financial institution 31 implements core software (for integration with the Core Financial Software System used by financial institutions) 32 to tell the Mroute payment system 20 how much to debit from each payee account and for the Mroute payment system 20 to specify the amount of funds to hold. The Mroute payment system 20 processes and routes the multiple payments to the respective payees as disbursements. As shown, the payees may include the policyholder/claimant 33 that receives payment notifications and provides endorsements to the Mroute payment system 20 for the amounts disbursed to the policyholder/claimant's bank 34 using core software 35. Other payees may include a bank/mortgagee/lienholder 36 of insured property that receives payment notifications and provides endorsements to the Mroute payment system 20 for the amounts disbursed to the bank/mortgagee/lienholder's bank 37 using core software 38, as well as additional payees 39 that receive payment notifications and provide endorsements to the Mroute payment system 20 for the amounts disbursed to the payee's bank 40 using core software 41. The policyholder/claimant 33, bank/mortgagee/lienholder 36, and payee 39 may optionally develop a workflow arrangement with the Mroute payment system 20 as illustrated.

[0048] FIG. 4 more generally illustrates a fully integrated multi-payee payment system 20 as used to facilitate multiple payments by a payor. As illustrated, the payor 42 communicates with the Mroute payment system 20 to provide payment alerts and to receive endorsement files. The payor's financial institution 43 implements core software 44 to tell the Mroute payment system 20 how much to debit from each payee account and for the Mroute payment system 20 to specify the amount of funds to hold. The Mroute payment system 20 processes and routes the multiple payments to the respective payees as disbursements. As shown, the respective payees 45-47 receive payment notifications and provide endorsements to the Mroute payment system 20 for the amounts disbursed to the respective payee's banks 48-50 using respective core software 51-53. The respective payees 45-47 may optionally develop a workflow arrangement with the Mroute payment system 20 as illustrated.

[0049] FIG. 5 illustrates an embodiment of a partially integrated third-party multi-payee payment system 20 as used to facilitate multiple payments by an insurance carrier 30. In this example, the multi-payee payment system 20 is partially integrated with a conventional ACH payment system that provides ACH payment via the respective financial institutions of each party. In this example, the multi-payee payment system 20 further includes its own bank 54 for facilitating ACH payment. Also, instead of core software for facilitating communications as in FIG. 3, each financial institution 31, 34, 37, 40, and 54 in the system implements conventional ACH transfers or other conventional single payee transfer payment using ACH system 55.

[0050] FIG. 6 illustrates an embodiment of a partially integrated third-party multi-payee payment system 20 as used to facilitate multiple payments by a payor 42. This example also partially integrates the multi-payee payment system 20 with a conventional ACH payment system that provides ACH payment via the respective financial institutions of each party. In this example, the multi-payee payment system 20 further includes its own bank 54 for facilitating ACH payment. Also, instead of core software for facilitating communications as in FIG. 4, each financial institution 43, 48, 49, 50, and 54 in the system implements conventional ACH transfers or other conventional single payee transfer payment using ACH system 55.

[0051] An embodiment of the invention in a full integration standalone operation contemplates implementation of a NEDD (Notification, Endorsement, Debits, Disbursements) protocol in the Mroute payment system 20. In particular, a processing platform, preferably placed in the cloud (FIG. 15), processes software for implementing the NEDD protocol described herein whereby a payor (insurer/business entity/individual/government entity) may make a multiple payee or stakeholder electronic payment. The fully integrated Mroute payment system 20, once engaged, initiates a chain of events that is structured on a queue based architecture design, but can also be based on other design architecture. The structured events are described in more detail below with respect to FIGS. 7-14.

[0052] In the exemplary embodiments described below with respect to FIGS. 7-14, once a single electronic transaction payable to more than one payee is initiated by a preregistered user or account holder of a preregistered user, the Mroute payment system 20 initiates a multiple payee bank account hold on the payor's bank or card account. The hold allows the bank account to be debited multiple times based on the number of payees and further initiates the notification (N) part of the NEDD protocol. Notification of available funds may be sent by way of an email, SMS text, phone call, mobile device, by integrating with a payee's platform if the payee is a business, etc. Payees may then be alerted that funds are available and their endorsement verification is required to proceed.

[0053] The Mroute payment system 20 may also initiate a multiple payee check handling and clearing process. In this case, a preregistered user manually inputs payee information from a check or remotely captures with a camera or other device the fields of the check with payee names on the check. The Mroute payment system 20 captures the fields and requests name confirmation of the payees from the user and populates an email or cell phone number field for the user to input the information of each payee. Upon entry, the Mroute payment system 20 sends payment notifications to all the payees while simultaneously placing a hold on the check issuer's bank account. The information is stored in a database where each transaction is mapped to a payer and payees.

[0054] The embodiments of the invention described with respect to FIGS. 7-14 further enable each payee to electronically verify their business or individual identity if the payment is as a result of an initiated multi-payee transaction and not from a paper check instrument. Upon identity verification, the multiple payee held funds are debited by the Mroute payment system 20 and credits of different amount are made to the payees. On the other hand, if the payment was initially in the form of a multi-payee paper check, then the system will follow steps that involve sending each payee an electronic image of the check. The payees will be provided an interface to remotely input their signature endorsement to the back of the remotely captured check image. The embodiments described herein further provide the ability to accept multiple remotely captured endorsements from various payees and place it on the endorsement section (back of check) of a remotely captured check image. This is the endorsement (E) part of the NEDD protocol and it allows all the stakeholders to sign off on the payment. Once all payees have properly endorsed as per the payor's specifications, the endorsement file is stored or made available to the payor for their records. Endorsements can also be in the form of identification verification for individual or business entity payees.

[0055] In a situation where not all the payees are entitled to a portion of either an initiated or converted (from a paper check instrument) multi-payee payment, then a payment form is provided to a payee. Payment forms provide a different type of endorsement and can be custom statements provided by the payer where payee must agree to the terms and endorse. The language involves a simple payment redirection request, where a payee intends not to accept/receive any funds but redirects the total amount to other payee(s). For example, in an insurance claim where policyholders' contractors are payees on a payment, the policyholder will usually need to endorse the full payment over to the contractor. A payment form enables total funds redirection to any of the other payees.

[0056] After all endorsements are gathered, the hold on the payor's funds in their bank account is lifted and the funds are debited (D), which is the debit (D) part of the NEDD protocol. The debited funds are disbursed as specified by the payor to the payees or stakeholders. The system thus enables a single payor to specify a single electronic transaction not be designated to just a single payee as is the norm, but to be designated to multiple payees.

[0057] Unspecified multi-payee payments are payments where the initiator or payer does not specify the amounts to disburse to each payee. Upon payee notification of pending funds for collection, the system deploys a channel that allows each payee to the transaction input a desired amount as a fraction of the total payment. The payees are provided with the option to all agree to each other's desired amount. The system will then verify that the payees' desired amounts all add up to the total payment's initial amount. This feature allows for payees deciding what they each receive when a payor does not specify an exact amount to disburse to the payees. The debited funds are paid out based on a disbursement (D) arrangement as specified and agreed by the payees involved through a web interface according to an embodiment of the invention. The disbursement arrangement is the disbursement (D) part of the NEDD protocol and concludes when the funds are deposited into the various payee bank accounts as requested/required. The disbursement arrangement also can involve a customized workflow that allows the upload/exchange of documents.

[0058] A workflow arrangement is the workflow (steps) that can be involved in the disbursement arrangement, i.e., the disbursement arrangement workflow. The disbursement arrangement workflow is the required steps/documents that a payor can/will require before disbursements can occur. For example, an insurer or financial institution/lienholder will require a law firm to produce paperwork before it can get its fee after negotiating a settlement. The requested paperwork can include a contract between one or more operators of the system with their policyholder or customer that indicates the amount of such operator's fee so they know what to pay the operator from the negotiated settlement. Also, the requested paperwork may include an affidavit of lien removal to ensure the operator accepts that it has been paid in full and will not place a lien on the property. The requirements (workflow arrangement) will differ from payor to payor and can be based on their various arrangements.

[0059] In situations where a multiple payee check is in play, the system can handle and negotiate the check remotely and settle all the payees electronically. A remote multiple payee check can be done directly with the system or via ATM deposits.

[0060] Embodiments of the invention in a partial integration non-standalone operation integrate with existing 3rd party payment systems that financial institutions currently use such as ACH (automated clearing house), etc. Where the complete system is not utilized or needed by a business or individual, and partial integration may be preferred, the following steps may apply in the operation. Once a payment is initiated, a notification (N) is sent out to the various payees. The notification can be sent by any of an email, SMS text, phone call, mobile device, or by integrating with a payee's platform if they are a business. All payees are alerted that funds are available and their endorsement is required to proceed.

[0061] The invention further enables each payee to endorse (E) the electronic payment after they have received the notification, thereby allowing all stakeholders to sign off on the payment. Once all payees have properly endorsed as per the payor's specifications, the endorsement file is made available to the payor for their records. After all endorsements are gathered and forwarded, the payor's funds may then be debited (D) from their bank account through the ACH or any other electronic payment system. The debited funds may then be available for the disbursement (D) arrangement as specified and agreed to by the parties involved through a web interface. The disbursement arrangement concludes when the funds are deposited into the various payee bank accounts as requested/required. In exemplary embodiments, the disbursement arrangement can involve a customized workflow that allows the upload/exchange of documents.

[0062] In insurance claims, benefits, annuities and surrenders, fully integrated applications of the invention may apply the above-described NEDD protocol steps, but may be implemented as follows. For P/C insurance claims, once a payment is initiated according to an embodiment of the invention, it places a hold on the payout amount in the insurance carrier's designated bank account. A notification (N) is sent out to the payees including the bank/mortgagee/lienholder, policyholder/claimant, and any other additional stakeholder(s) on the insurance settlement. After the notification (N) and endorsement (E) portion is done, the hold on the insurance carrier's funds in their bank account is lifted and the funds are debited (D) from the bank account. The funds may then be sent directly to the designated bank account of the bank/mortgagee/lienholder, etc. After these steps are completed, the disbursement (D) arrangement is between the bank/mortgage comp/lienholder and the policyholder/claimant/payees. The disbursement arrangement workflow may be customized based on the requirements of the bank/mortgagee/lienholder and allows the upload of documents or contracts with the 3rd party payees.

[0063] For L/H insurance claims or surrenders, the funds are debited through the Mroute payment system 20 and deposited based on the agreed disbursement arrangement. The funds are deposited directly into the designated bank accounts of the beneficiaries.

[0064] In insurance claims, benefits, annuities and surrenders, partially integrated applications of the invention implement the following operations. For P/C insurance claims, after the notification (N) and endorsement (E) portion is done, the funds are debited (D) through 3rd party payment systems like the ACH, etc., from the insurers designated bank account and deposited directly to the designated bank account of the receiving bank/mortgage comp/lienholder. After these steps are completed, the disbursement (D) arrangement is between the bank/mortgage comp/lienholder and the policyholder/claimant/payees. The disbursement arrangement workflow can be customized based on the requirements of the bank/mortgagee/lienholder and allows the upload of documents. With the disbursement workflow, other payees/stakeholders, not the policyholder or claimant, are able to claim their share based on their portion of the payment.

[0065] For L/H insurance claims or surrenders, the funds are debited through 3rd party payment systems like the ACH, etc., and deposited based on the agreed disbursement arrangement with the disbursement workflow to the designated bank accounts of the beneficiaries.

[0066] The invention further includes a database in conjunction with a processor to gather relevant information about claims, benefits, annuities and surrenders from insurance carriers once an insurance claim, benefit, surrender request is made. The information may be accessible to the stakeholders and can include mortgagees, lienholders, policyholders, claimants, etc. The database synchronizes with the insurance carrier's database and provides real time information upon request. This eliminates risks and delays for the banks/mortgage company/lienholder as they now have access to pertinent information that will lead to a faster insurance settlement.

[0067] The system platform can also be integrated in even smaller parts. Certain operations can be implemented in mini parts. For example, an insurer may implement the complete NEDD protocol (or some aspects of it) directly with their policyholders or claimants. In such case, a disbursement and workflow arrangement can also occur directly between an insurer and multiple policyholders/claimants, and not only when banks/mortgagees/lienholders etc. are involved. The same setup may be used for banks/mortgage comps/lienholders. They can also implement only certain aspects of NEDD protocol as they see fit. For example, a bank can choose to only implement the workflow arrangement and disbursement aspects of NEDD, and the platform of the invention will accommodate them.

[0068] A software embodiment for implementing the fully integrated and partially integrated Mroute payment system 20 in accordance with the invention will now be described with respect to FIGS. 7-14.

[0069] FIG. 7 illustrates multi-payee e-payment and multi-payee check e-payment in an exemplary embodiment. As illustrated, an authorized user or initiator, who can be a preregistered user, any payer or a payee of a multi-payee e-payment, accesses the system at 60. The user/initiator may initiate a multi-payee e-payment at 62, or initiate a multi-payee check e-payment at 64. If multi-payee e-payment is initiated at 62, the payor's payment details are input into database 66 at 68. The payor's payment information such as name, payment amount, account and routing number, and credit card information is stored in the database 66, or retrieved from the database 66 if previously stored or integrated. A multi-payee account hold is placed on the payer's funds through the payment/banking network or financial institution's core system 70. On the other hand, if the user/initiator initiated multi-payee check e-payment at 64, then information from the payor's check is retrieved from a scanned or remotely captured check copy information and input into the database 66 at 72. A multi-payee account hold is placed on the payor's funds through the payment/banking network or financial Institution's core system 70.

[0070] In the case of initiation of a multi-payee e-payment, the authorized user selects two or more designated payees to proceed at 74. On the other hand, in the case of initiation of multi-payee check e-payment, the authorized user selects two or more designated payees to proceed at 76. Based on stored database information, the payor's funds from a multi-payee e-payment or a multi-payee check e-payment is either debited or placed on hold through the banking network/servers 70.

[0071] At 78, the authorized user specifies the exact amount to disburse to each payee, or else the system proceeds without specified amounts at 80. Optional payment redirection at 82 allows a payee to redirect all funds to one or more of the other payees. Next, the funds are either distributed according to a pre-set disbursement at 84, or the payees may each select a particular stake in the total payment at 86. In such case, each payee must be in agreement of each other's stake and the total agreed amounts cannot exceed the total lump sum payment from the payor. Similarly, in the case of multi-payee check e-payment, the system proceeds without specified amounts at 88. Optional payment redirection at 90 allows a payee to redirect all funds to one or more of the other payees. Next, the payees may each select a particular stake in the total payment at 92. In such case, each payee must be in agreement of each other's stake and the total agreed amounts cannot exceed the total lump sum payment from the payor.

[0072] Payers' payment request or options are mapped/linked to the payees within the database and a notification based on the payer's payout preferences is sent to all payees at 94. In a situation where a payee as authorized user initiates the check e-payment process, that payee also gets a notification. Notifications are sent through the internet or telecomm network or via onsite servers at 96. The payees receive notifications and begin the endorsement/authentication process at 98.

[0073] FIG. 8 illustrates multi-payee e-payment debits and disbursements in an exemplary embodiment. In this embodiment, multi-payee debits and disbursements are processed at 100 after retrieving information from the database 66. With full integration, the payor's funds are placed on hold at 102 and the account hold protocol is enabled. On the other hand, with partial integration, the payor's funds are debited at 104. In each case, the notification and endorsement/authentication protocol is enabled at 106 and 108 and the payor specifies various amounts from the total payment to be disbursed to the payees at 110 or 112. In other cases, the payor does not specify amounts from the total payment to be disbursed to the payees (at 114 and 116). Payees have the opportunity to choose an amount from the total and, optionally, the payee may initiate a payment redirection request that allows a payee to redirect a stake from the total payment at 118 and 120. The transaction account process allows all payees to select at 122 or 124 a stake that is equal to the total payment from the payor. The stake is confirmed at 126 or 128, and the payor is debited at 130 or the payees' disbursement begins after the transaction account is debited at 132. The system confirms all payees are in agreement with each other's stake at 134 and 136. If not in agreement, the system allows the payees to reenter a stake until all the payees are in agreement. The system confirms the total payees agreed stake is equal to the total payment from the payor, and the funds are disbursed to the respective payees at 138-148. Similarly, if the payor enters specified amounts at 110 or 112, the payor is debited at 150 or the payees' disbursement begins after the transaction account is debited at 152. The system confirms all payees are in agreement with each other's stake at 154 and 156. If not in agreement, the system allows the payees to reenter a stake until all the payees are in agreement. The system confirms the total payees agreed stake is equal to the total payment from the payor, and funds are disbursed to the respective payees at 158-168. The debits and credits are processed through the payment networks, core systems at 170, and all transaction information is stored in the database 66.

[0074] FIG. 9 illustrates fully integrated multi-payee account hold in an exemplary embodiment. As described above, the payor's account information is stored in the database 66. Once a multiple-payee e-payment is initiated, a multiple-payee account/funds hold process begins at 180. The system requests/places an account/funds hold through the payment/banking network, core system at 182. The payor's exact payment amount is placed on hold at 184, but the debits are in portions based on the amount to be disbursed to a payee. The system also creates a temporary transaction account just for the transaction at 186. The payor's funds are debited and a credit is made to the transaction account at 188. The system tags each payee with each payees' exact amount. The amount on hold is debited in portions or the transaction account is debited in portions per database input at 190.

[0075] FIG. 10 illustrates multi-payee payment notification in an exemplary embodiment. The multi-payee payment instructions are stored in database 66. Payees are simultaneously notified of payment availability per authorized user input and payment instructions at 200. FIG. 10 shows notification to three payees 202, 204, and 206. A specific payment notification is prepared for each payee based on authorized user input that has been stored in database 66. Notification is sent to the payees via existing networks 208 to their contact information stored in the database 66. Each payee receives a payment notification with web link/instructions on how to proceed to collect funds at 210, 212, and 214. The procedure to collect funds might differ from one payee to the next. At step 216, payees are directed to endorse/authenticate payment and to provide identification before disbursements are made.

[0076] FIG. 11 illustrates multi-payee payment endorsement and authentication in an exemplary embodiment. As illustrated, each payee receives a payment notification link at 220 that is tagged to the specific preprogrammed disbursement requirement/information passed through from the database 66. Payment is initiated as a multi-payee e-payment at 222 or payment is initiated as a multi-payee check e-payment at 224. Each payee's identification is individually authenticated at 226 or 228. An optional endorsement for payees is provided at 230. Upon authentication at 228, each payee is prompted to endorse a copy of the check at 232, 234, and 236. A copy of the check is provided to each payee through an interface at 238. The check image is looped through each payee interface and each payee is able to remotely affix their individual endorsement to the endorsement section on the back of the check image. The system uses a real time image that enables the copy of the check update in real time after a payee endorses. The real time check endorsement updates are visible to all the payees so each payee can see that a fellow payee has endorsed the check. A “payable to” 3.sup.rd party endorsement is also affixed to the check's endorsement section. All payees' endorsements are aligned and the check image is forwarded to the payor's bank for clearing at 239, and the transaction information is stored in the database 66.

[0077] FIG. 12 illustrates multi-payee payment notification for insurance claims in an exemplary embodiment. In this embodiment, insurance carriers 240 send claims information to the database 66. Such information includes the claim number, the policy number, claim amount, estimate, contractor's lien waiver, etc. The claims information is sent to the claims notification 242 from the database 66. There, the information is sorted and each claim is tagged by the claim number. The claims notification system 242 retains structured claims information that is ready to be accessed. As illustrated, the claims notification system 242 provides notices via web/servers, etc. at 244. Mortgage companies, financial institutions, finance companies, etc. may access the claim information directory via integration or indirectly at 246. Policyholders and/or claimants cannot access claim information via integration, only indirectly at 248.

[0078] FIG. 13 illustrates an ATM multi-payee check deposit in an exemplary embodiment. As illustrated, a payee on a multiple payee check deposits the check through the ATM at 250. The payee authenticates the bank account and slides the check into ATM at 252. The system scans the check at 254 and identifies/extracts the names of the payees using, for example, optical character recognition techniques, or requests the depositor type the payee names at 256. All payee emails are entered, including the depositor at 258. Payment notification goes out to the payees at 260, and the transaction information is stored in the database 66.

[0079] FIG. 14 illustrates a document exchange process in an exemplary embodiment. As illustrated, the payor initiates a multi-payee payment at 270. The payment is initiated with options at 272, and the payor opts for document request/exchange with payees and is able to select from the documents or forms template, customize it or upload one at 274. The payor/payee documents exchange is continuous and can span various payment cycles. All payees are linked to the documents and they are able to remotely endorse as requested, or receive revised versions at 276, 278, and 280. The documents/forms are stored in the database 66 and are forwarded to the payor at 282.

[0080] Those skilled in the art will appreciate that implementation of the methods described herein may be effected by use of a server, processor, or other computer program product. Those skilled in the art also will appreciate that the systems and methods described herein address problems with convention electronic payment systems that require only one payment to be made at a time. The system described herein provides a system and method for multi-payee debits and disbursements as well as mechanisms for authenticating and notifying the payees and providing for multi-payee endorsements, thereby addressing unaddressed issues in the art.

[0081] FIG. 15 illustrates a sample hardware platform for implementing the system and method of the exemplary embodiments. As illustrated, the payment information stored in the database 66 and the instructions for implementing the methods described herein from instruction memory 290 are provided to a processor 292 for processing the instructions and information to implement the features and methods described herein. In an exemplary embodiment, the database 66, instruction memory 290, and processor 292 provide a platform 294 available in the cloud that is made secure using conventional encryption techniques. Banking networks 70/170 described herein access the platform 294 through a direct link or a secure internet connection. Computers 296 provide interfaces for providing inputs to be processed and for receiving displays of processed outputs from platform 294. Other parties may access the platform 294 via secure internet connections via their computing devices 298.

[0082] While the present disclosure has been described in connection with the preferred aspects, as illustrated in the various figures, it is understood that other similar aspects may be used or modifications and additions may be made to the described aspects for performing the same function of the present disclosure without deviating therefrom. Therefore, the present disclosure should not be limited to any single aspect, but rather construed in breadth and scope in accordance with the appended claims. For example, the various procedures described herein may be implemented with hardware or software, or a combination of both. Thus, the methods and apparatus of the disclosed embodiments, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium. As used herein and in the claims, a computer readable medium specifically excludes a modulated signal. When the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus configured for practicing the disclosed embodiments. In addition to the specific implementations explicitly set forth herein, other aspects and implementations will be apparent to those skilled in the art from consideration of the specification disclosed herein. It is intended that the specification and illustrated implementations be considered as examples only. In addition, those skilled in the art will appreciate that the disclosed steps may be reordered, equivalent elements may be substituted for those specifically disclosed, and certain features of the present invention may be used independently of other features—all without departing from the present invention as outlined in the appended drawings and claims.