# US 8,571,980 B1 · System, method and computer program product for transferring money > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,571,980 B1 - Document ID: US8571980B1 - Status: Granted - Kind: B1 - Application number: 11/444,930 - Filed: 2006-05-31 - Granted: 2013-10-29 - Earliest claimed: 2005-06-01 - Assignees: Stragent, LLC - Applicants: Susan Greenwood - Inventors: Susan Greenwood - Web page: https://patentgrep.com/patent/US8571980B1 ## CPC - G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems - G06Q 20/325: {using wireless networks} - G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract A system, method and computer program product are provided for transferring money. In use, requests from a plurality of senders are received utilizing a network. Each request is utilized for transferring money from a first account associated with a corresponding sender to a single second account associated with the receiver. In addition, a queue of the requests is displayed to the receiver. Further, the money is transferred to the single second account. The first account and the single second account are each associated with at least one first entity independent from a second entity that receives the requests and displays the queue of such requests. ## Claims ### Claim 1 A computer program product embodied on a non-transitory computer readable medium, comprising: computer code for creating a sender transfer service account for each of a plurality of senders utilizing a network, the sender transfer service account being created for a particular one of the senders by: receiving a sender password, receiving sender transfer service account information, receiving one or more actual sender bank account numbers including routing information and account information, the one or more actual sender bank account numbers associated with at least one first entity independent from a second entity associated with the sender transfer service account, causing a verification in connection with at least one aspect of the sender transfer service account by requiring the particular sender to verify a unique code intended for the particular sender, and storing the sender password, the sender transfer service account information, and the one or more actual sender bank account numbers in association with the sender transfer service account; computer code for creating a receiver transfer service account associated with the second entity for a receiver utilizing the network, by: receiving a receiver password, receiving receiver transfer service account information, receiving one or more actual receiver bank account numbers including routing information and account information, the one or more actual receiver bank account numbers associated with the at least one first entity independent from the second entity that is associated with the receiver transfer service account, causing a verification in connection with at least one aspect of the receiver transfer service account by requiring the receiver to verify a unique code intended for the receiver, and storing the receiver password, the receiver transfer service account information, and the one or more actual receiver bank account numbers in association with the receiver transfer service account; computer code for receiving a request to transfer money in connection with the one or more actual sender bank account numbers of the particular sender and an actual receiver bank account number of a receiver, where the request to transfer money is administered, at least in part, by the second entity without requiring disclosure of the one or more actual sender bank account numbers to the receiver and without requiring disclosure of the actual receiver bank account number to the particular sender, by: logging in the particular sender utilizing the sender password, receiving receiver transfer service account information that does not include the actual receiver bank account number, receiving a monetary amount to be transferred from the one or more actual sender bank account numbers of the particular sender to the actual receiver bank account number of the receiver, and receiving a selection of at least one of the one or more actual sender bank account numbers of the particular sender; computer code for sending an alert to the receiver utilizing at least one of an e-mail alert or a phone alert; computer code for receiving requests from the senders including the particular sender utilizing the network, each request for transferring money from a first account associated with a corresponding sender to a second account associated with the receiver; computer code for allowing acceptance of the request to transfer money in connection with the one or more actual sender bank account numbers of the particular sender and the actual receiver bank account number of the receiver, where the acceptance of the request is administered, at least in part, by the second entity without requiring disclosure of the one or more actual sender bank account numbers to the receiver and without requiring disclosure of the actual receiver bank account number to the particular sender, by: logging in the receiver utilizing the receiver password, displaying a queue of the requests to the receiver, the requests including the display of the request from the particular sender including the sender transfer service account information and the monetary amount, receiving a selection of the request from the particular sender, and receiving a selection of at least one of the one or more actual receiver bank account numbers of the receiver, and causing a direct transfer of the money to an account associated with the one or more actual receiver bank account numbers of the receiver; wherein the computer program product is operable such that the first account and the second account are each associated with the at least one first entity independent from the second entity, where the second entity performs the receiving the request and the displaying the queue associated with the computer code for receiving and displaying. ### Claim 2 A system, comprising: at least one computer with software installed thereon configured for: creating a sender transfer service account for each of a plurality of senders utilizing a network, the sender transfer service account being created for a particular one of the senders by: receiving a sender password, receiving sender transfer service account information, receiving one or more actual sender bank account numbers including routing information and account information, causing a verification in connection with at least one aspect of the sender transfer service account by requiring the particular sender to verify a unique code intended for the particular sender, and storing the sender password, the sender transfer service account information, and the one or more actual sender bank account numbers in association with the sender transfer service account; creating a receiver transfer service account associated with a second entity for a receiver utilizing the network, by: receiving a receiver password, receiving receiver transfer service account information, receiving one or more actual receiver bank account numbers including routing information and account information, the one or more actual receiver bank account numbers associated with at least one first entity independent from the second entity that is associated with the sender transfer service account and the receiver transfer service account, causing a verification in connection with at least one aspect of the receiver transfer service account by requiring the receiver to verify a unique code intended for the receiver, and storing the receiver password, the receiver transfer service account information, and the one or more actual receiver bank account numbers in association with the receiver transfer service account; receiving a request to transfer money in connection with the one or more actual sender bank account numbers of the particular sender and an actual receiver bank account number of a receiver, where the request to transfer money is administered, at least in part, by the second entity without requiring disclosure of the one or more actual sender bank account numbers to the receiver and without requiring disclosure of the actual receiver bank account number to the particular sender, by: logging in the particular sender utilizing the sender password, receiving at least a portion of the receiver transfer service account information that does not include the actual receiver bank account number, receiving a monetary amount to be transferred from the one or more actual sender bank account numbers of the particular sender to the actual receiver bank account number of the receiver, and receiving a selection of at least one of the one or more actual sender bank account numbers of the particular sender; sending an alert to the receiver utilizing at least one of an e-mail alert or a phone alert; and allowing acceptance of the request to transfer money in connection with the one or more actual sender bank account numbers of the particular sender and the actual receiver bank account number of the receiver, where the acceptance of the request is administered, at least in part, by the second entity without requiring disclosure of the one or more actual sender bank account numbers to the receiver and without requiring disclosure of the actual receiver bank account number to the particular sender, by: logging in the receiver utilizing the receiver password, displaying a queue of requests to the receiver, the requests including the request to transfer money of the particular sender, the displaying including a display of the sender transfer service account information and the monetary amount, receiving a selection of the request to transfer money of the particular sender, and receiving a selection of at least one of the one or more actual receiver bank account numbers of the receiver; wherein the system is operable such that the money is capable of being directly transferred to a bank account associated with the one or more actual receiver bank account numbers of the receiver, without requiring disclosure of the one or more actual sender ban account numbers to the receiver and without requiring disclosure of the actual receiver bank account number to the particular sender. ### Claim 3 (depends on 1) The computer program product of claim 1, wherein the receiver is selected from a group consisting of an individual, a business, and a government entity. ### Claim 4 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the requests are displayed in the queue with information selected from a group consisting of a name of the sender, an address of the sender, an amount of the money, a timestamp, and a message. ### Claim 5 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the requests are displayed in the queue with information including a name of the sender, an address of the sender, an amount of the money, a timestamp, and a message. ### Claim 6 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the requests are displayed in the queue with information including at least a name of the sender, and an amount of the money. ### Claim 7 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the requests are displayed in the queue with information including at least a name of the sender, an amount of the money, a timestamp, and a message. ### Claim 8 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that a plurality of queues are displayed which are each assigned a unique identifier. ### Claim 9 (depends on 1) The computer program product of claim 1, wherein each request includes a pseudo account identifier associated with the receiver. ### Claim 10 (depends on 9) The computer program product of claim 9, wherein the pseudo account identifier is not an e-mail address associated with the receiver. ### Claim 11 (depends on 9) The computer program product of claim 9, wherein the pseudo account identifier is an e-mail address associated with the receiver. ### Claim 12 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the requests are displayed in a plurality of queues. ### Claim 13 (depends on 12) The computer program product of claim 12, wherein each queue in the plurality of queues is associated with a single pseudo account identifier. ### Claim 14 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the transfer is completed in response to an acceptance received from the receiver utilizing the network. ### Claim 15 (depends on 14) The computer program product of claim 14, wherein the computer program product is operable such that at least one request is dismissed after a predetermined amount of time without receiving the acceptance. ### Claim 16 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the transfer is carried out automatically. ### Claim 17 (depends on 1) The computer program product of claim 1, and further comprising computer code for attaching a document to the request. ### Claim 18 (depends on 1) The computer program product of claim 1, and further comprising computer code for logging in the receiver utilizing receiver login data. ### Claim 19 (depends on 18) The computer program product of claim 18, wherein a single set of the receiver login data is associated with a plurality of accounts associated with the receiver. ### Claim 20 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that a status of each of the requests is displayed, the status including a pending status. ### Claim 21 (depends on 1) The computer program product of claim 1, wherein displaying the queue of the requests to the receiver includes displaying at least one request made by an anonymous sender. ### Claim 22 (depends on 1) The computer program product of claim 1, wherein displaying the queue of the requests to the receiver includes displaying a gift icon in association with at least one request. ### Claim 23 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that at least one of the requests is automatically initiated. ### Claim 24 (depends on 1) The computer program product of claim 1, wherein the first account associated with the sender and the second account associated with the receiver are each associated with a different entity. ### Claim 25 (depends on 1) The computer program product of claim 1, wherein the first account associated with the sender and the second account associated with the receiver are each associated with a same entity. ### Claim 26 (depends on 1) The computer program product of claim 1, wherein the at least one first entity is separate from the second entity. ### Claim 27 (depends on 1) The computer program product of claim 1, wherein the second entity includes an entity that processes the requests. ### Claim 28 (depends on 1) The computer program product of claim 1, wherein the second entity includes an external entity. ### Claim 29 (depends on 1) The computer program product of claim 1, wherein at least one of the at least one first entity includes a business entity. ### Claim 30 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the queue of the requests is displayed utilizing a single interface. ### Claim 31 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the queue of the requests is displayed utilizing a list. ### Claim 32 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the queue of the requests includes a historical queue of requests. ### Claim 33 (depends on 1) The computer program product of claim 1, wherein the computer program product is operable such that the queue of the requests includes a queue of the requests with each request displayed with an associated status. ### Claim 34 (depends on 1) The computer program product of claim 1, and further comprising: computer code for displaying a selection mechanism from which at least one sender is capable of selecting a name of the receiver from a list of saved names in connection with at least one request. ### Claim 35 (depends on 1) The computer program product of claim 1, and further comprising: computer code for initiating a communication from the receiver to at least one of the senders via an interface that displays an associated request. ### Claim 36 (depends on 35) The computer program product of claim 35, and further comprising: computer code for initiating a response to the communication from the at least one sender to the receiver via another interface that displays the communication and information corresponding with the associated request. ### Claim 37 (depends on 1) The computer program product of claim 1, and further comprising: computer code for initiating a communication from the receiver to at least one of the senders via a web interface that displays at least one request. ### Claim 38 (depends on 37) The computer program product of claim 37, and further comprising: computer code for initiating a response to the communication from the at least one sender to the receiver via another interface that displays the communication and request information. ### Claim 39 (depends on 1) The computer program product of claim 1, wherein the computer code for receiving, the computer code for displaying, and the computer code for transferring are associated with a web application executed utilizing at least one server having at least one processor. ### Claim 40 (depends on 2) The system of claim 2, wherein the receiver is an individual. ### Claim 41 (depends on 2) The system of claim 2, wherein the system is operable such that the requests are displayed in the queue with information including at least a name or address of the sender, an amount of the money, and a message. ### Claim 42 (depends on 2) The system of claim 2, wherein the system is operable such that the requests are displayed in the queue with information including at least one of a name of the sender, an address of the sender, an amount of the money, a timestamp, or a message. ### Claim 43 (depends on 2) The system of claim 2, wherein the system is operable such that the requests are displayed in the queue with information including at least a name of the sender, and an amount of the money. ### Claim 44 (depends on 2) The system of claim 2, wherein the system is operable such that the requests are displayed in the queue with information including at least a name of the sender, an amount of the money, a timestamp, and a message. ### Claim 45 (depends on 2) The system of claim 2, wherein the system is operable such that a plurality of queues is displayed which are each assigned a unique identifier. ### Claim 46 (depends on 2) The system of claim 2, wherein each request includes an identifier associated with the receiver. ### Claim 47 (depends on 46) The system of claim 46, wherein the identifier serves multiple purposes for the receiver. ### Claim 48 (depends on 46) The system of claim 46, wherein the identifier is an e-mail address associated with the receiver. ### Claim 49 (depends on 2) The system of claim 2, wherein the system is operable such that the requests are displayed in a plurality of queues. ### Claim 50 (depends on 49) The system of claim 49, wherein each queue in the plurality of queues is associated with a single pseudo account identifier. ### Claim 51 (depends on 2) The system of claim 2, wherein a plurality of pseudo account identifiers correspond with the single second account associated with the receiver. ### Claim 52 (depends on 2) The system of claim 2, wherein the system is operable such that the transfer is completed in response to an acceptance received from the receiver utilizing the network. ### Claim 53 (depends on 52) The system of claim 52, wherein the system is operable such that the request is dismissed after a predetermined amount of time without receiving the acceptance. ### Claim 54 (depends on 2) The system of claim 2, wherein the system is operable such that the transfer is carried out automatically without an acceptance received from the receiver in response to a corresponding request. ### Claim 55 (depends on 2) The system of claim 2, wherein the system is operable such that the transfer is carried out utilizing an automated clearinghouse. ### Claim 56 (depends on 2) The system of claim 2, and further comprising logic for logging in the receiver utilizing receiver login data. ### Claim 57 (depends on 56) The system of claim 56, wherein a single set of the receiver login data is associated with a plurality of accounts associated with the receiver. ### Claim 58 (depends on 56) The system of claim 56, wherein a single set of the receiver login data is associated with a plurality of queues. ### Claim 59 (depends on 2) The system of claim 2, wherein the system is operable such that the money is transferred directly from the first account to the second account without passing through one or more intermediate accounts. ### Claim 60 (depends on 2) The system of claim 2, and further comprising logic for logging in the sender utilizing sender login data. ### Claim 61 (depends on 2) The system of claim 2, wherein the system is operable such that a status of each of the requests is displayed, the status including a pending status. ### Claim 62 (depends on 2) The system of claim 2, wherein displaying the queue of the requests to the receiver includes displaying at least one request made by an anonymous sender. ### Claim 63 (depends on 2) The system of claim 2, wherein displaying the queue of the requests to the receiver includes displaying a gift icon in association with at least one request. ### Claim 64 (depends on 2) The system of claim 2, wherein the system is operable such that at least one of the requests is automatically initiated. ### Claim 65 (depends on 2) The system of claim 2, wherein the at least one first entity is separate from the second entity. ### Claim 66 (depends on 2) The system of claim 2, wherein the second entity includes an entity that processes the requests. ### Claim 67 (depends on 2) The system of claim 2, wherein the second entity includes an external entity. ### Claim 68 (depends on 2) The system of claim 2, wherein the second entity includes a business entity. ### Claim 69 (depends on 2) The system of claim 2, wherein the system is operable such that the queue of the requests is displayed utilizing a single interface. ### Claim 70 (depends on 2) The system of claim 2, wherein the system is operable such that the queue of the requests is displayed utilizing a list. ### Claim 71 (depends on 2) The system of claim 2, wherein the system is operable such that the queue of the requests includes a historical queue of requests. ### Claim 72 (depends on 2) The system of claim 2, wherein the system is operable such that the queue of the requests includes a queue of the requests with each request displayed with an associated status. ### Claim 73 (depends on 2) The system of claim 2, and further comprising: logic for displaying a selector from which at least one sender is capable of selecting a name of the receiver from a list of saved names in connection with a corresponding request. ### Claim 74 (depends on 2) The system of claim 2, and further comprising: logic for logging in at least one sender utilizing a sender identifier and a sender personal identifier; logic for, after logging in the at least one sender, receiving, from the at least one sender, a receiver identifier and a monetary amount; logic for displaying a confirmation interface including the receiver identifier and the monetary amount; logic for receiving, from the at least one sender, a confirmation via the confirmation interface; logic, after receiving the confirmation, initiating communication of a message to the receiver; logic for, after initiating the communication of the message to the receiver, logging in the receiver utilizing a receiver identifier and a receiver personal identifier; and logic for, after logging in the receiver, completing the transferring. ### Claim 75 (depends on 74) The system of claim 74, and further comprising: logic for displaying a selection mechanism from which at least one sender is capable of selecting a name of the receiver from a list of saved names in connection with at least one request. ### Claim 76 (depends on 74) The system of claim 74, wherein the system is operable such that a pseudo account identifier is received with the receiver identifier and the monetary amount. ### Claim 77 (depends on 2) The system of claim 2, and further comprising: logic for initiating a communication from the receiver to at least one of the senders via an interface that displays the queue of the requests. ### Claim 78 (depends on 77) The system of claim 77, and further comprising: logic for initiating a response to the communication from the at least one sender to the receiver via another interface that displays the communication and information associated with an associated request. ### Claim 79 (depends on 2) The system of claim 2, and further comprising: logic for initiating a communication from the receiver to at least one of the senders via a web interface that displays the queue of the requests. ### Claim 80 (depends on 79) The system of claim 79, and further comprising: logic for initiating a response to the communication from the at least one sender to the receiver via another web interface that displays the communication and information corresponding with an associated request. ### Claim 81 (depends on 2) The system of claim 2, wherein the system is operable such that a plurality of the requests is simultaneously displayed in the queue. ### Claim 82 (depends on 2) The system of claim 2, wherein the transferring includes initiation of a transfer. ### Claim 83 (depends on 2) The system of claim 2, wherein the transferring includes completion of a transfer. ### Claim 84 (depends on 2) The system of claim 2, and further comprising logic for providing a first graphical user interface for logging in, a second graphical user interface for creating a user account that utilizes a identifier, a third graphical user interface for configuring the user account, a fourth graphical user interface for initiating the transferring, a fifth graphical user interface for confirming a money transfer, a sixth graphical user interface for displaying a list of money transfers, a seventh graphical user interface for displaying a history of money transfers, an eighth graphical user interface for registering a monetary account for use in association with the user account, and a ninth graphical user interface for reporting information associated with multiple user accounts of multiple registered users. ### Claim 85 (depends on 2) The system of claim 2, wherein the queue is one of a plurality of hierarchical queues including at least one master queue and a plurality of sub-queues. ### Claim 86 (depends on 2) The system of claim 2, wherein the system is operable such that a particular request expires unless accepted within a predetermined time. ### Claim 87 (depends on 2) The system of claim 2, wherein the system is operable such that the sender transfer service account information includes at least one of an address, a name, or an identifier. ### Claim 88 (depends on 2) The system of claim 2, wherein the system is operable such that the receiver transfer service account information includes a pseudo account identifier. ### Claim 89 (depends on 2) The system of claim 2, wherein the system is operable such that the unique code includes a unique transaction code. ### Claim 90 (depends on 2) The system of claim 2, wherein the system is operable such that the at least one aspect includes the one or more actual sender bank account numbers. ### Claim 91 (depends on 2) The system of claim 2, wherein the system is operable such that the phone alert includes a SMS message. ### Claim 92 (depends on 2) The system of claim 2, wherein the system is operable such that the transfer of money from the one or more actual sender bank account numbers of the particular sender is directly sent to the actual receiver bank account number of the receiver. ### Claim 93 (depends on 2) The system of claim 2, wherein the system is operable such that the receiver transfer service account information includes a pseudo account identifier, for being used by the sender to request the transfer of money by receiving the pseudo account identifier from the sender and utilizing the pseudo account identifier to communicate information about the request to transfer money to the receiver. ### Claim 94 (depends on 2) The system of claim 2, wherein the system is operable such that the receiver transfer service account information includes a pseudo account identifier including an e-mail address, for being used by the sender to request the transfer of money by receiving the pseudo account identifier from the sender and utilizing the pseudo account identifier to communicate information about the request to transfer money to the receiver. ### Claim 95 A computer program product embodied on a non-transitory computer readable medium, comprising: code for creating a sender transfer service account for each of a plurality of senders utilizing a network, the sender transfer service account being created for a particular one of the senders by: receiving a sender password, receiving sender transfer service account information, receiving one or more actual sender bank account numbers including routing information and account information, verifying at least one aspect of the sender transfer service account by prompting feedback from the particular sender, and storing the sender password, the sender transfer service account information, and the one or more actual sender bank account numbers in association with the sender transfer service account; code for creating a receiver transfer service account associated with a second entity for a receiver utilizing the network, by: receiving a receiver password, receiving receiver transfer service account information, receiving one or more actual receiver bank account numbers including routing information and account information, the one or more actual receiver bank account numbers associated with at least one first entity independent from a second entity that is associated with the sender transfer service account and the receiver transfer service account, verifying at least one aspect of the receiver transfer service account by prompting feedback from the receiver, and storing the receiver password, the receiver transfer service account information, and the one or more actual receiver bank account numbers in association with the receiver transfer service account; code for receiving a request to transfer money in connection with the one or more actual sender bank account numbers of the particular sender and an actual receiver bank account number of a receiver, without requiring disclosure of the one or more actual sender bank account numbers to the receiver and without requiring disclosure of the actual receiver bank account number to the particular sender, by: logging in the particular sender utilizing the sender password, receiving at least a portion of the receiver transfer service account information, receiving a monetary amount to be transferred from the one or more actual sender bank account numbers of the particular sender to the actual receiver bank account number of the receiver, and receiving a selection of at least one of the one or more actual sender bank account numbers of the particular sender; code for sending an alert to the receiver utilizing at least one of an e-mail alert or a phone alert; and code for allowing acceptance of the request to transfer money in connection with the one or more actual sender bank account numbers of the particular sender and the actual receiver bank account number of the receiver, without requiring disclosure of the one or more actual sender bank account numbers to the receiver and without requiring disclosure of the actual receiver bank account number to the particular sender, by: logging in the receiver utilizing the receiver password, displaying a queue of requests to the receiver, the requests including the request to transfer money of the particular sender, the displaying including display of the sender transfer service account information and the monetary amount, receiving a selection of the request to transfer money of the particular sender, and receiving a selection of at least one of the one or more actual receiver bank account numbers of the receiver; wherein the computer program product is operable such that the money is capable of being transferred to a bank account associated with the one or more actual receiver bank account numbers of the receiver directly, bank account-to-bank account, without requiring disclosure of the one or more actual sender bank account numbers to the receiver and without requiring disclosure of the actual receiver bank account number to the particular sender. ### Claim 96 (depends on 95) The computer program product of claim 95, wherein the computer program product is operable such that the receiver transfer service account information includes a pseudo account identifier, for being used by the sender to request the transfer of money by receiving the pseudo account identifier from the sender and utilizing the pseudo account identifier to communicate information about the request to transfer money to the receiver. ### Claim 97 (depends on 95) The computer program product of claim 95, wherein the computer program product is operable such that the receiver transfer service account information includes a pseudo account identifier including an e-mail address, for being used by the sender to request the transfer of money by receiving the pseudo account identifier from the sender and utilizing the pseudo account identifier to communicate information about the request to transfer money to the receiver. ### Claim 98 A computer program product embodied on a non-transitory computer readable medium, comprising: code for creating a first account for a first entity utilizing a network, by: receiving a first password, receiving first account information, identifying one or more actual first bank account numbers including routing information and account information, and storing the first password, the first account information, and the one or more actual first bank account numbers in association with the first account; code for verifying at least one aspect in connection with the first account by requesting feedback from the first entity; code for creating a second account for a second entity utilizing the network, by: receiving a second password, receiving second account information, identifying one or more actual second bank account numbers including routing information and account information, and storing the second password, the second account information, and the one or more actual second bank account numbers in association with the second account; code for verifying at least one aspect in connection with the second account by requesting feedback from the second entity; code for receiving a first request to transfer money in connection with at least one of the one or more actual first bank account numbers of the first entity and a receiver, without requiring disclosure of the at least one of the one or more actual first bank account numbers to the receiver and without requiring disclosure of an actual receiver bank account number of the receiver to the first entity, by: logging in the first entity utilizing the first password, receiving receiver information, receiving a first monetary amount to be transferred from the at least one of the one or more actual first bank account numbers of the first entity to the actual receiver bank account number of the receiver, and receiving a selection of the at least one of the one or more actual first bank account numbers of the first entity; code for causing an alert to be sent to the receiver utilizing at least one of an e- mail alert or a phone alert; and code for allowing acceptance of a second request to transfer money in connection with an actual sender bank account number of a sender and the second entity, without requiring disclosure of the actual sender bank account number to the second entity and without requiring disclosure of at least one of the one or more actual second bank account numbers of the second entity to the sender, by: logging in the second entity utilizing the second password, displaying a queue of one or more requests to the second entity, the one or more requests including the second request to transfer money of the sender, the displaying including display of a second monetary amount, receiving a selection in connection with the second request to transfer money of the sender, and receiving a selection of the at least one of the one or more actual second bank account numbers of the second entity; wherein the computer program product is operable such that money is capable of being transferred directly from a first entity bank account associated with the at least one of the one or more actual first bank account numbers of the first entity to a receiver bank account associated with the actual receiver bank account number of the receiver, without requiring disclosure of the at least one of the one or more actual first bank account numbers to the receiver and without requiring disclosure of the actual receiver bank account number to the first entity; wherein the computer program product is further operable such that money is capable of being transferred directly to a second entity bank account associated with the at least one of the one or more actual second bank account numbers of the second entity from a sender bank account associated with the actual sender bank account number of the sender, without requiring disclosure of the actual sender bank account number to the second entity and without requiring disclosure of the at least one of the one or more actual second bank account numbers to the sender. ### Claim 99 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the receiver information includes a pseudo account identifier which is used in connection with communication with the receiver regarding the first request to transfer money. ### Claim 100 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the receiver information includes a pseudo account identifier including an e-mail address, which is used in connection with communication with the receiver regarding the first request to transfer money. ### Claim 101 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the first account and the second account are associated with a same entity. ### Claim 102 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the first account, the second account, the receiver bank account, the sender bank, the first entity bank account, and the second entity bank account are associated with a same entity. ### Claim 103 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the at least one aspect is of the first account. ### Claim 104 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the receiver information includes information associated with a receiver account. ### Claim 105 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the actual first or second bank account numbers are associated with at least one first particular entity independent from a second particular entity that receives the first request to transfer money or allows acceptance of the second request to transfer money. ### Claim 106 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the actual first and second bank account numbers are associated with at least one first particular entity independent from a second particular entity that receives the first request to transfer money and allows acceptance of the second request to transfer money. ### Claim 107 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the actual first or second bank account numbers are associated with at least one first particular entity independent from a second particular entity that administers, at least in part, the receipt of the first request to transfer money or allowance of the acceptance of the second request to transfer money. ### Claim 108 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the actual first and second bank account numbers are associated with at least one first particular entity independent from a second particular entity that administers, at least in part, the receipt of the first request to transfer money or allowance of the acceptance of the second request to transfer money. ### Claim 109 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the first entity is the sender, and the second entity is the receiver. ### Claim 110 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the queue is displayed utilizing a list. ### Claim 111 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the queue includes a historical queue of requests. ### Claim 112 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the queue includes a list of the requests with each request displayed with an associated status. ### Claim 113 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the queue is one of a plurality of hierarchical queues including at least one master queue and a plurality of sub-queues. ### Claim 114 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the one or more requests are displayed in the queue with information including a name of the sender, an address of the sender, a timestamp, and a message. ### Claim 115 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that a plurality of queues are displayed which are each assigned a unique identifier. ### Claim 116 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the receiving the selection of the at least one of the one or more actual first bank account numbers of the first entity includes a selection of at least one of a plurality of displayed actual first bank account numbers which are registered by the first entity. ### Claim 117 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the receiving the selection of the at least one of the one or more actual second bank account numbers of the second entity includes a selection of at least one of a plurality of displayed actual second bank account numbers which are registered by the second entity. ### Claim 118 (depends on 98) The computer program product of claim 98, wherein the computer program product is further operable such that, in response to the first request to transfer money, money is transferred to the receiver bank account without passing through one or more intermediate accounts utilizing an automated clearinghouse (ACH); and, in response to the second request to transfer money, money is transferred from the sender bank account without passing through one or more intermediate accounts utilizing the ACH. ### Claim 119 (depends on 98) The computer program product of claim 98, wherein the computer program product is operable such that the actual first and second bank account numbers are associated with at least one first particular entity independent from a second particular entity that receives the first request to transfer money and allows acceptance of the second request to transfer money, and the one or more actual second bank account numbers includes a single second bank account number.