US20130238488A1 - System and method for transferring funds - Google Patents

Abstract

A computer-implemented payment processing system includes an account information directory comprising a database of registered users of a payment network, at least one of the registered users having a plurality of public identifiers associated therewith that are stored in the account information directory, at least one of the plurality of public identifiers being useable by the user to send funds to other users and to receive funds from the other users; and a rules engine accessible to the user by way of a computer network, the rules engine being accessible by the user to separately configure attributes of the plurality of public identifiers.

Description

PRIORITY CLAIM
• This application claims priority to U.S. Patent Application Ser. No. 61/607,882, entitled “SYSTEM AND METHOD FOR TRANSFERRING FUNDS,” filed Mar. 7, 2012.
BACKGROUND
• Embodiments of the present invention relate generally to the field of transferring funds. In particular, they relate to systems and methods for generating and maintaining a payment network.
• Payments made between individuals are often made with cash or checks. Payments for items and services purchased from businesses are often also made with cash or checks, and are also often made using credit cards or debit cards. While these payment mechanisms have worked well, enhanced systems and methods of facilitating such payments would be desirable.
SUMMARY
• According to an example embodiment, a computer-implemented payment processing method comprises receiving a fund transfer request identifying a recipient by a public identifier, determining a private identifier for the receiver based on the public identifier, and transmitting a transfer message via a computer network to cause funds to be transferred from a sender to the recipient. The fund transfer request is received via a computer network. The message is generated using the private identifier.
• According to another example embodiment, a computer-implemented payment processing system comprises an account information directory and a rules engine. The account information directory comprises a database of registered users. At least one of the registered users is associated with a plurality of public tokens that are stored in the account information directory. The plurality of tokens are useable by the user to send funds to other users and to receive funds from the other users. The rules engine is accessible to the user by way of a computer network to configure attributes of the plurality of public tokens.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a schematic diagram of a fund transfer system in which a sender and a recipient use different banking institutions according to an example embodiment.
• FIG. 2 is a schematic diagram of token management logic that may manage tokens for fund transfer requests according to an example embodiment.
• FIG. 3A is a process in which a fund transfer request results in the funds being received by a registered or unregistered recipient according to an example embodiment.
• FIG. 3B is a process in which a fund transfer request results in the funds being received by a registered or unregistered recipient according to an example embodiment.
• FIG. 4 is a screen shot of a web page that may be presented to a user to configure user preferences and manage connections with other users.
• FIG. 5 is a screen shot of a web page that may be presented to a user to configure notification settings.
• FIG. 6 is a screen shot of a web page that may be presented to a user to send money to a recipient.
DETAILED DESCRIPTION
• Referring toFIG. 1, a fund transfer system100 that implements a payment network is shown. The fund transfer system100 may be utilized by senders to send funds to recipients and by recipients to receive the funds. The fund transfer system100 may facilitate the transfer of funds from senders to receivers without either party disclosing any financial account information to each other. The senders and recipients may be individuals or business entities. In the example embodiment, the sender uses a bank account as the source of funds. In other embodiments, the sender may use credit cards, debit cards, business credit cards or check cards as the source of funds. The fund transfer system100 may be used for both intrabank transfers (i.e., transfers in which the sender and the recipient both have accounts at the same bank and the funds are transferred between the accounts within the same bank) and interbank transfers (i.e., transfers in which the sender and the recipient have accounts at different banks and the funds are transferred between the accounts at different banks)
• The fund transfer system100 may include, among other systems, asender computer system110, abank computer system120, arecipient computer system130, abank computer system150, a paymentservice computer system160, and an automated clearinghouse computer system170. Each of the above described systems may communicate through anetwork140, which may include one or more of the Internet, Cellular network, Wi-Fi, Wi-Max, a proprietary banking network, and so on. InFIG. 1 and throughout the remaining description, for sake of providing an example, it is assumed that the sender performs a funds transfer from an account maintained by thebank computer system120 and the receiver receives the funds using an account maintained by thebank computer system150. Hence, thecomputer system120 is sometimes referred to herein as the sender bank computer system and thecomputer system150 is sometimes referred to herein as the receiver bank computer system. It will be appreciated of course that any given bank computer system may operate in different capacities in the context of different fund transfer transactions. Additionally, while the examples provided herein are primarily in the context of a sender requesting a funds transfer to a recipient, it will also be appreciated that a recipient may request a funds transfer from a sender.
• Thesender computer system110 may be used by an individual user (e.g., a business owner or employee, a consumer, and so on) to create transactions and interact with banking functions provided through an online banking area of a website provided by the senderbank computer system120 or through a website provided by apayment service160. Thesender computer system110 may, for example, comprise a user computer (e.g., desktop or laptop computer), a cellular telephone, smart phone, a mobile handheld wireless e-mail device, a personal digital assistant, a portable gaming device, or other suitable device. Thesender computer system110 may also comprise one or more servers each with one or more processors configured to execute instructions stored in memory. For example, such an arrangement may be utilized if the sender is a merchant or other business.
• Thesender computer system110 may comprisenetwork interface logic112, adisplay device114, aninput device116, andclient application118.Network interface logic112 may include, for example, program logic that connects thesender computer system110 to thenetwork140. As described in greater detail below, for example, thesender computer system110 may receive and display screens on thedisplay device114 including account information, transaction instructions, and so on. In an example embodiment, such screens may be used to request a username and password information. Such screens may also be used to prompt the user to provide information regarding the amount of the funds and the identity of the merchant or individual that is to receive the funds. Such information may comprise, for example, a name, an address, a phone number, an e-mail address, a selection of a recipient from an electronic directory, and/or other information. Such screens may also include screens displaying information regarding past transactions. Such screens are-presented to the user via thedisplay device114. Theinput device116 may be used to permit the user to initiate account access and to facilitate receiving fund transfer request information from the user.
• Theclient application118 may comprise program logic (i.e., stored executable instructions) configured to implement at least some of the functions described herein. As will be appreciated, the level of functionality that resides on thesender computer system110 as compared to other components of the fund transfer system100 may vary depending on the implementation. Theclient application118 may simply be a web browser (e.g., Internet Explorer®, Mozilla Firefox®, Chrome®, Safari®, and so on) configured to receive and display web pages received from thebanking computer system120. The client application may also comprise a mobile web browser, text message (SMS) interface, a dedicated application, or other program suitable for sending and receiving information over thenetwork140.
• Thebank computer system120 is operated by a bank institution that maintains accounts held by customers, such as demand deposit accounts, credit card accounts, home mortgage loans, student loans, and so on. Thebank computer system120 may, for example, comprise one or more servers each with one or more processors configured to execute instructions stored in memory, send and receive data stored in memory, and perform other operations to implement the operations described herein associated with logic or processes shown inFIGS. 1-6.
• Thebank computer system120 may includenetwork interface logic122,account processing logic124, anaccount database126, and aninformation directory128. Thenetwork interface logic122 may include, for example, program logic that connects thebank computer system120 to thenetwork140. Thenetwork interface logic122 may facilitate secure communications between the bank and the sender and/or the recipient. Thenetwork interface logic122 may also facilitate communication with other entities, such as other banks, settlement systems, and so on. Thenetwork interface logic122 may include user interface program logic configured to generate and present web pages to users accessing thebank computer system120 over thenetwork140.
• Theaccount processing logic124 performs account processing to process transactions in connection with the account(s) of the account holder, such as account credits and debits to checking and savings accounts, credits and debits to home mortgage and home equity accounts, credits and debits to student loan accounts, and so on. Thus, whenever funds are transferred into or out of an account of an account holder (e.g., a sender or recipient of funds), theaccount processing logic124 reflects an appropriate debit or credit in theaccount database126, which stores account information (e.g., transactions, information about the account holder, and so on) for accounts that are maintained by the bank on behalf of its customers. Theaccount processing logic124 may also process fund transfer requests to transfer funds from a sender using thesender computer system110 to a recipient using therecipient computer system130.
• Theinformation directory128 may be used when an identifier other than a bank account/routing number is used (e.g. an e-mail address, phone number, Universal Payment Identification Code (UPIC), randomly generated number, and so on) to identify a recipient of a funds transfer. Theinformation directory128 may be a database that is maintained to allow the financial institution to convert/correlate the recipient's cell phone number (or e-mail address, or other identifier) to a bank account number/routing number of the recipient's bank account. This arrangement allows the sender to uniquely identify the recipient (e.g., with an e-mail address or other identifier), without necessarily having private/personal information regarding the recipient (i.e., the recipient's bank account/routing number).
• Users may register their information with theinformation directory128 prior to any financial transaction. A user may be added to theinformation directory128 upon registering for the fund transfer system100 through thebank computer system120. Upon registration, a new entry may be created for the newly registered user in a database that implements theinformation directory128. The user may provide one or more identifiers (e.g., phone numbers, e-mail addresses, and so on) that the user may share with other individuals with whom the user interacts (for example, in the same way that people selectively or freely share phone numbers and e-mail addresses with other individuals for purposes of communicating with such other individuals). Herein, such identifiers are referred to as “public identifiers” or “public tokens.” (The terms “identifier” and “token” are used interchangeably herein to refer to a code (e.g., an e-mail address, a phone number, a user generated or system generated character string, etc.) that identifies a user.) Theinformation directory128 may also generate or otherwise associate an identifier that is securely maintained and that is used to identify the user in theinformation directory128. Herein, such identifiers are referred to as “private identifiers.” The private identifier may, for example, be a unique ID of the database entry for the user in theinformation directory128. While the private identifier is known by theinformation directory128, it need not be known by the user with whom it is associated or by other users. However, it may be known by banks and other entities that are members of the payment network implemented by the funds transfer system100. In addition to the public identifier(s) (e.g., phone numbers, e-mail addresses, and so on) and the private identifier (e.g., database UID), other information may also be stored in the database entry, such as account information (account numbers, routing numbers, etc.) for accounts held by the user at the bank and user preferences. At least some of this information may be populated automatically, e.g., if the user registers for the fund transfer system100 during a secure on line banking session on thebank computer system120.
• Additionally, the database entry for each user may also store a registry of other users connected to that user. That is, for each user, a registry may be stored that includes a listing of each other user with whom the user has an established connection. Such connection may be established, for example, the first time that the user sends or receives funds from the other user. A connection may also be established by way of a user interface that permits a user to add connections with other users through a lookup service in theinformation directory128 and/or another information directory. An example of such a user interface is discussed below in connection withFIG. 4. The users may include not only users that are registered in the payment network implemented by the fund transfer system100, but also other affiliated payment networks, as discussed in greater detail below. For each user in the registry, additional information may be stored, such as their unique ID and/or other information. As another example, the information for the other users may be stored in separate database entries in theinformation directory128.
• In various embodiments, a plurality of information directories may exist, each directory maintained by a different institution or entity. For example, users that maintain accounts at the bank associated withbank computer system120 may register throughbank computer system120, users that maintain accounts at the bank associated withbank computer system150 may register throughbank computer system150, and so on for other users that maintain accounts at other entities. Such entities may also include non-bank entities (e.g., payment processing companies, credit agencies, credit card network providers, and so on), and users may also register through such non-bank entities.
• In addition to the public and private identifiers that have already been described herein, additional identifiers may also be used. For example, such additional identifiers may be handled with varying levels of security. As another example, variations of existing public identifiers may be used to implement special purpose public tokens, public tokens with customized functionality, and so on, as discussed in greater detail below.
• Thetoken management logic129 manages tokens. For example, thetoken management logic129 may be configured to register tokens, authenticate tokens, generate tokens and so on. The token managelogic129 may also facilitate identification of the recipient when a token is not recognized. Thetoken management logic129 may also be used to customize attributes of tokens, such that particular accounts are used, particular methods of notification are used, and so on. Thetoken management logic129 is discussed in greater detail below in connection withFIG. 2.
• Therecipient computer system130 may be configured in generally the same manner as the other computer systems described herein. For example, if the fund recipient is an individual, thecomputer system130 may be a mobile device, such as a cellular phone, smart phone, mobile handheld wireless e-mail device, personal digital assistant, portable gaming device, a desktop computer or other suitable device. Thecomputer system130 may also comprise one or more servers each with one or more processors configured to execute instructions stored in memory. For example, such an arrangement may be utilized if the recipient is a merchant or other business.
• In one embodiment (e.g., where the recipient is a bricks-and-mortar merchant), therecipient computer system130 may include point of sale devices (e.g., cash register systems) that are equipped to electronically obtain public token information from customers. For example, the cash register systems may be equipped with a near field communication (NFC) reader device that is capable of reading a public token (e.g., cell phone number) from an NFC equipped cell phone. As another example, the cell phone may include an application that is configured to generate a bar code or other image on a display screen that contains the public token, and the cash register system may be equipped with a bar code reader configured to read the bar code. Therecipient computer system130 may then request payment from the sender via the funds transfer system100 using the public token obtained at the point of sale.
• The recipientbank computer system150 may be configured in a similar manner as the senderbank computer system120. Thus, thebank computer system150 comprisesnetwork interface logic152,account processing logic154,account database156, andinformation directory158 corresponding to thenetwork interface logic122,account processing logic124,account database126 andinformation directory128 of thebank computer system120.
• The paymentservice computer system160 may be associated with a payment service that is configured to facilitate interbank fund transfers, e.g., a payment service provided by a non-bank entity as previously mentioned. The payment service may, for example, be an entity that is formed as a joint venture between banks and/or other entities that send and receive funds using the fund transfer system100. As another example, the payment service may be a third party vendor. As another example, the payment service may be a web portal provided for an online community of individuals where such individuals obtain user names/login IDs or otherwise become registered members. The individuals may, for example, use the web portal to interact with each other and/or to interact with a service provided by the online community. Examples of online communities include MSN®, iPhone® users, Facebook®, LinkedIn°, and so on. The payment service may, for example, be an additional service that is offered by the web portal to the members of the online community. As another example, the payment service may be provided by one of the banks, i.e., such that the bank performs both the operations described herein as being performed by thebank computer system120/150 and the operations described herein as being performed by the paymentservice computer system160.
• Herein, the banks associated withcomputer systems120 and150 are assumed to be “member banks” That is, the banks associated withcomputer systems120 and150 are assumed to follow established protocols for transferring funds using the fund transfer system100. For example, in the context of a payment service that is created as a joint venture, the member banks may include at least the banks that are part owners of the joint venture, as well as potentially other banks While two member banks are shown inFIG. 1, it will be appreciated that there may be additional member banks. Additionally, as previously indicated, non-bank entities may also be members. The payment service may also be used by senders and recipients that have bank accounts at non-member banks, for example, by permitting such users to register directly with the paymentservice computer system160. Hence, users do not need to be customers of any particular bank in order to be able to use the fund transfer system100.
• The paymentservice computer system160 may, for example, comprise one or more servers each with one or more processors configured to execute instructions stored in memory, send and receive data stored in memory, and perform other operations to implement the operations described herein associated with logic or processes shown inFIGS. 1-6. The paymentservice computer system160 includesnetwork interface logic162 and aninformation directory168. Although not specifically shown, it will be appreciated that the paymentservice computer system160 may include account processing logic and an account database in the same or similar manner to theaccount processing logic124,155 and theaccount databases126,156. Thenetwork interface logic162 may include user interface program logic configured to generate and present web pages to users accessing the paymentservice computer system160 over thenetwork140.
• Theinformation directory168 may be used when an identifier other than a bank account/routing number is used (e.g. an e-mail address, phone number, Universal Payment Identification Code (UPIC), randomly generated number, and so on). As described above in connection with theinformation directory128 and158, theinformation directory168 is a database that is maintained to allow the payment service to convert/correlate the recipient's cell phone number (or e-mail address, or other token) to a bank account number/routing number of the recipient's bank account for users that registered through the paymentcomputer service system160. This arrangement allows the sender to uniquely identify the recipient (e.g., with an e-mail address or other identifier), without necessarily having private/personal information regarding the recipient (i.e., the recipient's bank account/routing number).
• Users including senders and recipients may register their information with theinformation directory168 in advance, e.g., where such users do not bank or have accounts with any of the other member entities. Additionally, the paymentservice computer system160 may be configured such that users that only wish to send funds may do so without registering. For example, the payment servicecomputer service system160 may be configured to generate web pages that receive credit card information from a sender to complete a transaction each time a sender wishes to send funds, without requiring that the sender ever register with the payment servicecomputer service system160.
• As will be appreciated, the information that is stored in theinformation directory168 may vary depending on the implementation, including the extent to which information is also stored in theinformation directories128 and158. For example, in one embodiment, when a user registers at the bank computer system120 (or at thebank computer system150, or at the computer system of another member entity), information may be stored in both theinformation directory128 and theinformation directory158. Theinformation directory128 may store a complete identification of the user's bank accounts and other information collected during registration. Conversely, theinformation directory168 may store a reduced amount of information, such as the registered public token(s), the financial institution with it is associated, and the private token (e.g., unique ID) associated with each token. More detailed bank account number/routing number, or other sensitive information need not be stored at theinformation directory168. In another embodiment, instead of using a paymentservice computer system160 to maintain theinformation directory168, such information may be stored entirely in theinformation directories128,158 maintained by individual member banks As will also be appreciated, the extent to which transaction details are tracked and maintained in theaccount processing logic124,154 as compared to the extent to which transaction details are tracked and maintained by the paymentservice computer system160 may vary depending on the implementation.
• The Automatic Clearing House (ACH)system170 is used to transmit funds to and from bank accounts of the senders and recipients. As is known, the ACH Network is a nationwide batch oriented electronic funds transfer system which provides for interbank clearing of electronic payments for participating depository financial institutions. An ACH entry may start with an account holder (known as the Receiver in ACH terminology) authorizing an Originator (e.g., a person or a company) to issue ACH debit or credit to an account. Depending on the ACH transaction, the Originator must receive authorization from the Receiver. In accordance with the rules and regulations of ACH, no financial institution may issue an ACH transaction (whether it is debit or credit) towards an account without prior authorization from the Receiver. Once authorization is received, the Originator then creates an ACH entry to be given to an Originating Depository Financial Institution (ODFI), which may be any financial institution that does ACH origination. This ACH entry is then sent to an ACH Operator (i.e., central clearing facilities through which financial institutions transmit or receive ACH entries, e.g., the Federal Reserve or the Electronic Payments Network) and is passed on to the Receiving Depository Financial Institution (RDFI), where the Receiver's account is issued either a credit or debit, depending on the ACH transaction. The RDFI may, however, reject the ACH transaction and return it to the ODFI with the appropriate reason, such as that there were insufficient funds in the account or that the account holder indicated that the transaction was unauthorized. An RDFI has a prescribed amount of time in which to perform returns (e.g., two to sixty days from the receipt of the ACH transaction). An ODFI receiving a return of an ACH entry may re-present the ACH entry two more times, or up to three total times, for settlement. Again, the RDFI may reject the transaction, after which the ODFI may no longer represent the transaction via ACH. The above description of ACH system is one in use currently, the embodiments of the current invention will continue to function similarly even if some methods and steps in the ACH system are modified.
• Referring toFIG. 2,FIG. 2 shows thetoken management logic169 in greater detail. As shown inFIG. 2, thetoken management logic169 includessponsor identification logic182,registration logic184,token authentication logic186,rules engine188, andtoken generation logic190. Although thetoken management logic169 is shown, it will be appreciated that thetoken management logic129 and159 may be configured in the same or similar manner.
• Thesponsor identification logic182 may be configured to identify a sponsor of a token. For example, if the sender uses a token to identify a recipient that is unrecognized at theinformation directory129 of the sender bank computer system120 (i.e., because the recipient is not a customer of the sender bank), thesponsor identification logic182 may be configured to receive the token from the senderbank computer system120 and access theinformation directory168 to provide an identification of the unique ID and financial institution associated with that token.
• As will be appreciated, the extent to which thebank computer systems120,150 have sponsor identification logic that operates in the same manner as thesponsor identification logic182 may depend, in part, on the extent to which the information is stored in theinformation directory168 as compared to the extent to which information is also stored in theinformation directories128 and158. In various embodiments, greater or lesser degrees of reliance may be placed on theinformation directory168 to perform user identification functions in a centralized fashion in connection with the transfer of funds between entities. Herein, for sake providing an example, it is assumed that theinformation directory168 is used to perform user identification functions in a centralized fashion in connection with the transfer of funds between entities. In such embodiments, it may be possible to avoid replicating all the functions of thesponsor identification logic182 and thebank computer systems120,150.
• In one embodiment, the payment network implemented by the fund transfer system100 is configured to interact with other affiliated payment networks (e.g., PayPal, CashEdge, and so on). In such an arrangement, if the token provided by the senderbank computer system120 is not recognized in theinformation directory168, thesponsor identification logic182 is configured to transmit inquiries to the other affiliated payment networks (e.g., in a predetermined sequence) to determine if the token is recognized at any of the other affiliated payment networks. If the recipient is registered with another payment network, then the funds may be transferred to the recipient by routing the funds through the other payment network. In an embodiment where a user lookup service is provided by theinformation directory168, the look up service may operate in the same manner to identify users registered at remote entities. Information may also be stored in theinformation directory168 identifying the payment network determined to be associated with that token, thereby facilitating additional funds transfers to that token in the future. Hence, in such an arrangement, funds may be pushed to a recipient that is not registered with the payment system implemented by the funds transfer system100 but rather that is registered with another payment system. Additionally, such funds may be pushed to the recipient without the sender having to know or be concerned about whether the recipient is registered with the payment system implemented by the funds transfer system100.
• Theregistration logic184 is configured to facilitate the process of registering new users. For example, in the preceding discussion, if the token is not recognized at theinformation directory168, and is not registered at any other affiliated payment network, then the registration logic may be configured to send the recipient an e-mail or other communication inviting the recipient to register with the payment network. Such an e-mail may include a link to the website provided by the paymentservice computer system160. Theregistration logic184 may be configured to generate web pages for presentation to the user at the website to facilitate the registration process. If, based on information provided by the user when registering at the website, it is determined that the user is a customer of one of the member entities, then the user may be forwarded to the website of the member entity to complete the registration process. As will be appreciated, theregistration logic184 may also present web pages to the user in other scenarios (e.g., where the user has arrived at the website as a result of a search engine query, where the user has arrived at the website via another website (e.g., such as an online community website or merchant website), and so on). Theregistration logic184 may create new database entries in theinformation directory168 responsive to inputs received from the user.
• Thetoken authentication logic186 is configured to authenticate tokens. For example, when a user registers a new token, thetoken authentication logic186 may be configured to confirm that the user is associated with that token (e.g., that the user who is attempting to register a cell phone number as a token is indeed the owner of that cell phone number). (Herein, the term “own” in the context of telephone numbers refers to the telephone number being assigned to one particular user as opposed to being assigned to other users, and is not being used to refer to ownership as between the user and the phone carrier that provides the telephone number to the user. The term is used analogously in the context of e-mail addresses.) As another example, when a user attempts to register a new e-mail address, theauthentication logic186 may perform an authentication operation such as sending the user an e-mail at the new e-mail address. The e-mail may, for example, contain a link that must be accessed by the user in order to successfully complete the registration process.
• Additionally, thetoken authentication logic186 may be configured to perform authentication operations on previously-registered tokens. For example, a user that registers a cell phone number may ultimately switch cell phone numbers and/or cell phone carriers. Thetoken authentication logic186 may be configured to process disconnect directories that are published by cell phone carriers and that list cell phone numbers that have been disconnected by that carrier. For example, if a registered cell phone number is listed as having been disconnected, thetoken authentication logic186 may send an e-mail to the user at a registered e-mail address to determine whether the cell phone number is no longer a valid token for that user or whether the user has merely changed cell phone carriers but has retained the cell phone number.
• Thetoken authentication logic186 may also be configured to send follow up communications to the user trying to use a token to send/receive money from another user if there is uncertainty regarding whether the other user is correct owner of the token. For example, thetoken authentication logic186 may be configured to notify the sender that such uncertainty exists, request that the sender provide confirm information that was provided regarding the recipient, provide additional information regarding the recipient, and so on. For example, if a user attempts to send funds using the token jsmith@abc-company.com, an e-mail may be sent to the user if there is uncertainty whether ownership of the token jsmith@abc-company.com has changed (e.g., due to a change in employees at ABC Company). Theauthentication logic186 may also be configured to access other networks or online communities (e.g., Facebook, LinkedIn, etc.) to obtain additional information that may be used to authenticate the token. Thetoken authentication logic186 may also be configured to track the changing public tokens by date and time of use and the date and time that a particular recipient ceases to use a particular public token.
• Hence, theregistration logic182 and theauthentication logic184 cooperate to facilitate the registration of tokens and to ensure that the tokens are associated with their correct owners. In one embodiment, the entity that registers a token is responsible for warranting the validity of the registration. For example, if the recipient bank registers a token 415-555-1234, and subsequently accepts a payment to the user that registered the token 415-555-1234, then the recipient bank is responsible for refunding money to the sender if the user that registered the token 415-555-1234 is not actually the owner of that cell phone number at the time of the funds transfer (e.g., because the previous owner changed cell phone numbers, and the new owner is on a different payment network). Hence, the recipient bank undertakes responsibility for correctly authenticating the user at the time of registration and for routinely processing disconnect directories to ensure that the authentication remains valid.
• In one embodiment, the warranty (and/or limited access to the information directory168) may be provided as a service to third parties. For example, an on line retailer that is refunding money to a customer may wish to verify that a token previously provided by the customer (e.g., “415-555-1234”) remains accurate. If funds are refunded to the customer at the “415-555-1234” token, but the customer no longer owns that token, then the payment service would be responsible for refunding the funds to the correct customer. The fee charged for the service may, for example, be based on the dollar value of liability accepted by the payment service for providing incorrect information. As another example, a service may be provided in which a per token fee is charged for identifying a user based on a token and/or for identifying a token (e.g., e-mail address, cell phone number, etc.) based on an identification of a user.
• Therules engine188 is configured to permit users to configure different attributes for different tokens. The attributes may be specified in rules that are configured based on user specified preferences. In various embodiments, therules engine188 may provide a user with default settings that are used until the user decides to customize the rules. For example, therules engine188 may be used to configure the manner in which funds are directed to various accounts held by the user at the bank (e.g., to forward at least a portion of the funds or transfer funds into a particular type of account), and so on. As another example, the funds may be split between a plurality of accounts according to the rules specified by the user, e.g., the funds may also be transferred into at least one of a retirement account, savings account, PayPal® account, or a certificate of deposit. As another example, portion of the received funds may be forwarded to a different user that is registered with the payment network. As another example, therules engine188 may be used to configure the manner in which a notification is sent to a recipient informing the recipient that a fund transfer request has been made by a sender. For example, according to one embodiment, the rules may be configured to specify the channel(s) by which notifications are sent (e-mail, text message, voicemail, and so on), the e-mail account(s) and/or phone number(s) to which notifications are sent, and so on. As another example, if the fund transfer amount is greater than a threshold value, the user may receive an automated telephone call instead of an e-mail message or may receive an e-mail/telephone call instead of no message. As another example, if the fund transfer request originated from a particular sender, then the user may specify the mode of the notification (e.g., e-mail, voicemail, or text message). As another example, therules engine188 may be used to configure the payment channel used to send funds to a recipient (e.g., ACH transfer, credit card network, PayPal network, printed and mailed check, and so on). As another example, therules engine188 may be used to configure the speed with which funds are transferred to the recipient (e.g., instantaneous, same day, overnight, 2-day payment, and so on). As another example, therules engine188 may be used to configure transaction limits (e.g., to ensure that no more than $500 can be charged to a particular token during a predetermined time period such as one day, one week, one month, etc.).
• Thetoken generation logic190 may be configured to generate additional public tokens for a user. Thetoken generation logic190 may cooperate with therules engine188 to create different tokens that are configured with different attributes. For example, a business may wish to use different individual tokens depending on whom within the business is responsible for processing a particular transaction. For example, a recipient that is a landlord that owns several apartment buildings may wish to create different tokens for each apartment building. For example, the additional tokens may be based on user provided alphanumeric character strings, may be system generated based on pseudo random character strings, or may be generated in another fashion. For example, if the landlord recipient already uses an e-mail address as a public token (e.g., landlord@mail.com), the additional public tokens may be variants of the public token already used by the recipient (e.g., landlord@mail.com/building1, landlord@mail.com/building2, landlord@mail.com/building3 and so on). Such tokens may then be configured with different attributes usingrules engine188. For example, if each of the different buildings has a different building manager, then an e-mail may be sent to an e-mail address of the respective building manager for a particular apartment building when a tenant of that apartment building pays rent.
• As another example, the landlord recipient may provide each tenant with a different public token for use by the tenants to pay rent. Again, for example, the additional tokens may be variants of the public token already used by the recipient (e.g., landlord@mail.com/unit101, landlord@mail.com/unit102, landlord@mail.com/unit103 and so on). Thebank computer system150 may then receive funds from each tenant and all the funds may be transferred to one or more accounts belonging to the landlord. Theaccount processing logic154 may be configured to generate a report showing the funds received in connection with each token (thereby showing, for example, which tenants have paid in a given month and which tenants have not paid in a given month). Tokens may also be programmed with additional information, for example, the amount of the expected monthly payment. Theaccount processing logic154 may then be configured to compare the amount actually received with the expected monthly payment to ensure that the tenant has paid completely and to track overall account status of the tenant.
• As another example, a recipient may also configure single use tokens. For example, a recipient may be organizing an event in which other users are expected to financially contribute to the event. The recipient may then configure a token (e.g., johnsmith@mail.com/moms-birthday-party) which may be provided to the other users. Theaccount processing logic154 may then generate a report showing the funds that have been received from various ones of the other users in connection with that token.
• As another example, senders may also configure different tokens. For example, a sender may use a first token as their default token (e.g., johnsmith@mail.com), and create additional special purpose tokens where payment is to be made from other accounts (e.g., johnsmith@mail.com/collegesavings to make a tuition payment from a college savings fund).
• As another example, as previously indicated, theinformation directories128,158,168 may provide a lookup service that may be used by users to establish connections with other users. In such an embodiment, users may be able to configure aspects of their tokens that are displayed to other users. For example, if an individual is operating a business under another name (e.g., Joseph Smith DBA “Joe's Lawn Service”), it may be desirable to permit the user to configure the token such that the business name is displayed to other users, even though the name on the account is actually the individual's name. In this manner, it will be easier for customers of the business to establish a connection with the business.
• Referring toFIGS. 3A and 3B,FIGS. 3A and 3B illustrate a process in which the funds may be received by a registered or unregistered recipient according to an example embodiment. InFIGS. 3A and 3B, a fund transfer message is received from a sender at the senderbank computer system120 and propagates to the recipient bank computer system, where it causes funds to be deposited in to the account of a recipient. Specifically, atstep301 inFIG. 3A, the senderbank computer system120 receives a fund transfer request from a sender which identifies the recipient using a token. Atstep311, thebank computer system120 searches theinformation directory128 to determine whether the token is associated with a user that is registered with the sender bank (i.e., a transfer within the same bank). If the token is associated with a user registered with the sender bank then, atstep313, the recipient's account information is retrieved from theinformation directory128. Subsequently, atstep315, the funds are transferred to the recipient's account. The funds may be transferred to the recipient's financial account based on preferences of the sender and the recipient, as discussed in greater detail below in connection withFIGS. 4 to 6.
• If, atstep311, the recipient is not registered with the sender bank, then the process proceeds to step321. Atstep321, thebank computer system120 transmits an inquiry to the paymentservice computer system160, and it is determined if the token is associated with a user that is registered at another member entity of the payment network implemented by the funds transfer system100. For example, if it is the first time that the sender has transferred funds to this particular recipient, then thebank computer system120 may transfer the public token of the recipient as provided by the sender. In this scenario, thesponsor identification logic182 may perform a search of theinformation directory168 to determine if the token is associated with a user that is registered with another member entity. If the public token is located in the directory, then the paymentservice computer system160 may return the unique ID associated with the public token along with an identification of the financial institution or other member entity with which it is associated to the senderbank computer system120. The senderbank computer system120 may then create another registry entry for the sender, and store the public token and the unique ID of the recipient as part of the registry entry. The senderbank computer system120 may also prompt the sender to provide other information about the recipient (e.g., a nickname or other name by which the sender wishes to identify the recipient).
• As another example, if the sender has transferred funds to this recipient previously, then thebank computer system120 may transfer the unique ID of the recipient to the paymentservice computer system160. In this scenario, thesponsor identification logic182 may use the unique ID as an index to the database that implements theinformation directory168 to locate the recipient in theinformation directory168. Assuming the unique ID is still valid and is still located in theinformation directory168, then the paymentservice computer system160 may return the financial institution or other member entity with which it is associated to the senderbank computer system120. As another example, if the sender has transferred funds to this recipient previously, then thebank computer system120 identifies the member entity with which it is associated based on the unique ID itself (e.g., where the unique ID is embedded with information that identifies the financial institution). Atstep323, the sender's registry is updated to include an entry for the recipient, including the unique identifier of the recipient. At step,325 the funds are transferred to the member entity (e.g., the recipient bank in the example ofFIG. 1) for deposit along with the unique ID of the recipient. Based on the unique ID, theinformation directory158 may be accessed by the recipientbank computer system150 to identify the account number of the recipient. The funds may then be deposited in the bank account of the recipient.
• If, atstep321, the recipient is not a user that is registered at another member entity of the payment network implemented by the funds transfer system100, then the process proceeds to step331 illustrated inFIG. 3B. Atstep331, thesponsor identification logic182 of the paymentservice computer system160 transmits inquiries to other payment networks (e.g., PayPal®, Star, Blink, Interlink, Plus, etc.), and it is determined if the token is associated with a user that is registered at another payment network. For example, thesponsor identification logic182 may transmit an inquiry to a first payment network to inquire whether the recipient is registered at that payment network. If not, thesponsor identification logic182 may continue to transmitting additional inquiries to other affiliated payment networks until the payment network at which the recipient has registered an account is identified. Atstep333, if the recipient is registered with another payment network, information may also be stored in theinformation directory168 identifying the payment network determined to be associated with that token, thereby facilitating additional funds transfers to that token in the future. Next, at step335 the funds may be transferred to the recipient by routing the funds through the other payment network. Hence, in such an arrangement, funds may be pushed to a recipient that is not registered with the payment system implemented by the funds transfer system100 without the sender having to know or be concerned about whether the recipient is registered with the payment system implemented by the funds transfer system100.
• If, after the search of other payment networks is completed, no other payment network is identified at which the recipient is registered, then the recipient is presumed to not be a registered user of any payment network. Accordingly, atstep341, an invitation is sent to the recipient to invite the recipient to join the payment network. For example, if the token used by the sender is an e-mail address, then an e-mail is sent to the recipient informing that another user is attempting to transfer funds to the recipient and inviting the recipient to join the payment network. A link in the e-mail may, for example, deliver the recipient to the website provided by thebank computer system120. As another example, if the token used by the sender is a cell phone number, the recipient may be sent a text message containing a URL inviting the recipient to join the payment network. As will be appreciated, the recipient may be sent such an invitation in other situations, e.g., if the recipient is not a registered user of the payment network implemented by the funds transfer system100, even if the user is a registered user of another payment network.
• Atstep343, the recipient may be prompted to provide account information. Atstep351, based on the account information, it may be determined whether the user is a customer of one of the member entities. For example, a bank routing number for a demand deposit account may be used to determine whether the user is a customer of one of the member entities. If the recipient is a customer of a member entity, then atstep353 the recipient may be transferred to the member entity for registration (e.g., the recipient bank in the example ofFIG. 1). A unique ID is associated with the recipient in theinformation directory159 of the recipientbank computer system150 and in theinformation directory168 of the paymentservice computer system160. Atstep355, the sender's registry is updated to include the recipient, including the unique identifier of the recipient. Atstep357, the funds are transferred to the recipient.
• If the recipient is not a customer of a member entity, then atstep363 the recipient is registered by the paymentservice computer system160. Atstep365, the sender's registry is updated to include an entry for the recipient, including the unique identifier of the recipient. Atstep367, the funds are transferred to the recipient. As will be appreciated, if the recipient has customized fund transfer preferences, the fund transfer will be processed by therules engine188 according to the recipient preferences. Examples of token customization to reflect such preferences were previously described above in connection withrules engine188 andtoken generation logic190.
• FIG. 4 is a screen shot of aweb page400 that may be provided to a user when the user selects a preferences tab. Theweb page400 may be used to configure preferences in connection with thetoken management logic129,159 or169 (depending on where the user registered for the payment network).Web page400 includes a plurality of fields including a defaultnotification settings field401, a manageconnections field411, and a managerecipients field431. The default notification settings field401 presents the user with information regarding the current default notification settings for a funds transfer event. As shown in the screen shot inFIG. 4, notification settings field401 may include settings to specify a telephone number to which automated telephone call notifications or text message notifications should be sent (field403) and an e-mail address to which e-mail notifications should be sent (field405). The user may also be permitted to specify the name on the account (field407) as it should appear to other users when the other users receive a funds transfer notification. The information specified infield407 may also be used in other situations, for example, when others user are searching for connections through a lookup service ininformation directory128,156,168. The user may configure therules engine188 to notify the user regarding transactions based on the user preferences received from the user prior to the occurrence of the transactions. If the user fails to configure customized notification settings, default notification settings may be used. In various embodiments, a user may choose different/custom notification settings for each token that the user has registered.
• In the example shown inFIG. 4, the telephone number that may receive a call, text message or voice message, upon the occurrence of a predetermined event is 949-555-7878. Additionally, the e-mail address that may be used to notify the user that a fund transfer has occurred from or to the user's accounts is pat@mail.com. The user may choose to be notified by e-mail or telephone or both.
• Thetoken field413 may display a particular token that the user has registered or is in the process of registering. Thestatus field415 may display whether the token has been verified/unverified or is active/inactive. The receivingmoney field417 is derived in part on the information in the status field and indicating whether a particular token is currently available for sending/receiving money. For example, for the inactive phone number (i.e., 650-555-5555), the user may send/receive funds using this token for connections established prior to the token becoming inactive. However, the user cannot establish new connections with other users based on this token. For example, this may be a mobile number that was previously owned by the user. Because a unique ID serves as the basis for funds transfers after a connection has been established, previously established connections are still valid (because they are based on the unique ID and not the mobile number), however, new connections are not permitted to be established (because another user may now be using the token).
• Theaccount number field419 may display the type of account and a partial account number of an account that is associated with the token infield413. Hence, funds sent/received using the token specified infield413 are withdrawn from/deposited to the account specified infield419. If an account number is not associated with the e-mail address or the mobile number infield413, then theaccount number field419 may display a message such as “account is not specified.” Thenotification field421 may indicate whether the default notification settings specified in field701 are to be used for notifications or whether other/customized settings are to be used.
• Actions field423 may include various links that allow the user to take various actions. For example, links may include, edit, remove, and verify. If the status of a token is verified, then the edit field allows the user to edit attributes of the token as specified in therules engine188. For example, the accounts and notification preferences (fields719 and721) may be edited in greater detail. If the account number is verified, then the remove link may also be displayed. if the account is unverified or inactive, a verify link that sends an e-mail or a SMS and displays a verification code may be displayed. An edit and remove link may also be displayed for unverified or in active e-mail or telephone numbers. The user may also add new tokens using new connections link425.
• As will be apparent fromfields401 and411, separate payment and notification channels may be used for funds transfers. For example, for the 415-555-4001 token, the payment channel occurs through the 415-555-4001 token, however, the notification channel occurs through the 949-555-7878 and pat@mail.com tokens. Additionally, if the user decides to set a custom notification channel for the 415-555-4001 token, the user can do so without disrupting connections that have already been established using the 415-555-4001 token. Disrupting one channel (e.g., by changing the token) does not impact the other channel.
• The manageconnections field431 allows a user to perform various functions related to managing the user's connections with other users.Field431 shows a registry of connections that have been established by a user. Withinfield431 various information may be displayed regarding each other user, for example, name (field433), nickname (field435), e-mail/mobile (field437), status (field439), and actions (field441) and a link that allows a user to addnew recipients443. Although not specifically shown, it will be appreciated that a unique ID may also be stored for each of the users in the registry shown infield431. As previously indicated, the unique ID need not be known by the user and is maintained more secure.
• Thename field433 may be the name of the recipient as it appears on the account associated with the other user (e.g., as specified by the other user). Thenickname field435 may be a nickname assigned to the other user (e.g., as specified by the user). The e-mail/mobile field437 may display the public tokens that are being used by the recipient. Thestatus field437 may display whether a permanent connection has been established for a particular contact. Actions field441 may be determined based on the status field. For example, if a link has been established, then theactions field441 may display a link that allows a user to send money to the recipient. If a link has not been established, then the actions field may display a send money link, but theactions field441 may also display a view details link. The view details link may display another screen to the user where the user may provide further details to establish a connection with a recipient. Other actions that may be displayed are edit and remove. Edit may allow the user to edit each field discussed above and remove may allow a user to remove a recipient and related information from the user's registry. Alink443 may be used to add additional users to the registry, e.g., via a search ofinformation directories128,158 and/or168.
• In an example embodiment, the manageconnections field431 may present a message to the user that informs the user when another user is no longer the owner of a token. The message may include a link that allows the user to update the token information. In other embodiments, if the other user's information has changed, then the message presented by the manageconnections field431 may allow the user to update the outdated information.
• FIG. 5 is a screen shot of a form that allows a user to update default or custom notification settings. InFIG. 5, the user is provided with a list of e-mail addresses associated with the user's account. The user may use a checkbox to indicate which e-mail address should receive a notification. For example, the user in the screen shot shown inFIG. 5 has chosen e-mail address “psmith@google.com” by placing acheck mark505 in the appropriate field. In other embodiments, a user may choose multiple e-mail addresses instead of choosing a single e-mail address. Also shown on the screen shot are telephone numbers associated with the user accounts. The user may use acheck mark509 to select a phone number that receives a notification. In other embodiments, the user may choose multiple telephone numbers and multiple e-mail addresses for notification. Alink511 may allow the user to add e-mail addresses or telephone numbers to the account information maintained by the bank. In one embodiment, the user may select the link and the user may be automatically taken to a web portal provided by a banking institution. The user may click onsave button513 to save the notification changes implemented by the user.
• FIG. 6 shows a screen shot of aweb page600 that may be presented to a user when the user selects the send money tab. Theweb page600 may include a sendmoney field601 that the user may fill out to send money to a chosen recipient. Theweb page600 may include a display ofvarious payment channels619 that are available to the user. Theweb page600 may also include afield630 showing details regarding recent transactions that are pending, returned or completed.
• The sendmoney form601 may prompt the user to choose a recipient from a pull downmenu603. The list of recipients presented usingmenu603 may be populated using the list of recipients contained infield431 discussed inFIG. 4. The list ofrecipients menu603 may contain the names of users that the user has sent funds to or received funds from in the past or that have been added in another manner. In one embodiment, the recipients may be identified by the nicknames assigned to each recipient. Since the nicknames may be directly correlated with the unique ID within thetoken management logic129, the account information may be derived from the nicknames via the unique ID. Hence, as previously indicated, the connection between the two users is not disrupted when a cell phone number or e-mail address becomes obsolete. After choosing the recipient, the user may choose an account from which funds will be sent to the recipient using a drop downmenu605. The drop down menu may be pre-populated with a list of all accounts that are held by the user. The user may enter a dollar amount that the user would like to transfer to the recipient in theamount field607. The user's name may be presented with anoptional field description609 that will allow the user to ascertain that the payment was for a particular product or service provided by the recipient. Another field may be auto populated with the user's name as the sender of the funds. Anickname field611 is also displayed if the recipient knows the user by a name that is different than the user's name as it appears on the user's account. The sendmoney form601 also displays links that allow the user to addrecipients615, managerecipients617 and thecurrent notification preference613.
• The payment channels form619 presented to the user may allow the user to choose various payment channels such as, credit card, ACH or PayPal®. Also displayed with each payment channel may be the funds available torecipient field623. For example, the credit card method may make the funds available to the recipient within 2-days of processing the send request. However, the user may be charged a fee as indicated byfield625, for example, $5.00. In other examples, a user may choose ACH infield621, however the funds may be available to the recipient in 4 days with no fee. Other payment channels, such as PayPal®, Star, Blink, Interlink, and Plus may also be presented to the user.
• Field630 shows a few of the most recent transactions that the user has performed. Additional recent transactions may be displayed via selection of a link to view more transfers and/or by selecting the transfer activity tab.Field630 may display various fields that include information regarding the transactions. For example, such fields may include a date sentfield633, fromaccount field635,recipient field637,amount field639,description field641,status field643 andactions field645. The date sentfield633 lists the date when the user initiated the send request. The fromaccount field635 may display the type of account (i.e. checking, savings, or money market) and a partial account number. Therecipient field637 may display the full name of the recipient. Theamount field639 displays the dollar amount sent to the recipient. Thedescription field641 displays the description that was entered by the user while processing the request. Thestatus field643 may inform the user whether the fund transfer is pending, returned or not processed, or has been completed. The actions field645 may display a link that allows a user to view more details regarding the current status of the fund transfer.
• The embodiments of the present invention have been described with reference to drawings. The drawings illustrate certain details of specific embodiments that implement the systems and methods and programs of the present invention. However, describing the invention with drawings should not be construed as imposing on the invention any limitations that may be present in the drawings. The present invention contemplates methods, systems and program products on any machine-readable media for accomplishing its operations. The embodiments of the present invention may be implemented using an existing computer processor, or by a special purpose computer processor incorporated for this or another purpose or by a hardwired system.
• As noted above, embodiments within the scope of the present invention include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium which can be used to store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
• Embodiments of the present invention have been described in the general context of method steps which may be implemented in one embodiment by a program product including machine-executable instructions, such as program code, for example in the form of program modules executed by machines in networked environments. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Machine-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.
• As previously indicated, embodiments of the present invention may be practiced in a networked environment using logical connections to one or more remote computers having processors. Those skilled in the art will appreciate that such network computing environments may encompass many types of computers, including personal computers, hand held devices, multi processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and so on. Embodiments of the invention may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
• An exemplary system for implementing the overall system or portions of the invention might include a general purpose computing computers in the form of computers, including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. The system memory may include read only memory (ROM) and random access memory (RAM). The computer may also include a magnetic hard disk drive for reading from and writing to a magnetic hard disk, a magnetic disk drive for reading from or writing to a removable magnetic disk, and an optical disk drive for reading from or writing to a removable optical disk such as a CD ROM or other optical media. The drives and their associated machine-readable media provide nonvolatile storage of machine-executable instructions, data structures, program modules and other data for the computer. It should also be noted that the word “terminal” as used herein is intended to encompass computer input and output devices. Input devices, as described herein, include a keyboard, a keypad, a mouse, joystick or other input devices performing a similar function. The output devices, as described herein, include a computer monitor, printer, facsimile machine, or other output devices performing a similar function.
• It should be noted that although the diagrams herein may show a specific order and composition of method steps, it is understood that the order of these steps may differ from what is depicted. For example, two or more steps may be performed concurrently or with partial concurrence. Also, some method steps that are performed as discrete steps may be combined, steps being performed as a combined step may be separated into discrete steps, the sequence of certain processes may be reversed or otherwise varied, and the nature or number of discrete processes may be altered or varied. The order or sequence of any element or apparatus may be varied or substituted according to alternative embodiments. Accordingly, all such modifications are intended to be included within the scope of the present invention as defined in the appended claims. Such variations will depend on the software and hardware systems chosen and on designer choice. It is understood that all such variations are within the scope of the invention. Likewise, software and web implementations of the present invention could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps. The foregoing description of embodiments of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. The embodiments were chosen and described in order to explain the principals of the invention and its practical application to enable one skilled in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. Other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangement of the embodiments without departing from the scope of the present invention as expressed in the appended claims.

Claims (22)

1. A computer-implemented payment processing system comprising:

an account information directory comprising a database of registered users of a payment network, at least one of the registered users having a plurality of public identifiers associated therewith that are stored in the account information directory, at least one of the plurality of public identifiers being useable by the user to send funds to other users and to receive funds from the other users; and

a rules engine accessible to the user by way of a computer network, the rules engine being accessible by the user to separately configure attributes of the plurality of public identifiers.

2. The system ofclaim 1, wherein the rules engine is accessible by the user to configure a rule that controls a manner in which a notification is sent to the user informing the user that a funds transfer request has been received from a sender.

3. The system ofclaim 2, wherein the rule specifies a channel by which notifications are sent, the channel selected from the group consisting of e-mail, text message, and voicemail, and wherein the rules engine is further configured to permit the user to specify at least one of an e-mail address and a telephone number to which the notifications are sent.

4. The system ofclaim 2, wherein the rule specifies a channel in which a notification is sent when the funds transfer amount is greater than a threshold value, the channel selected from the group consisting of e-mail, text message, and voicemail.

5. The system ofclaim 2, wherein the rule specifies a channel in which a notification is sent when the funds transfer request originates from a particular sender, the channel selected from the group consisting of e-mail, text message, and voicemail.

6. The system ofclaim 1, wherein the rules engine is configured to permit the user to configure a payment channel to be used.

7. The system ofclaim 6, wherein the payment channel is selected from the group consisting of Automatic Clearing House (“ACH”) transfer, credit card network, PayPal network, and printed and mailed check.

8. The system ofclaim 1, wherein the rules engine is accessible by the user to define an account associated with one of the plurality of public identifiers, the account being a demand deposit account held by the user at a financial institution, wherein funds transfers received using the one of the plurality of public identifiers are deposited to the account.

9. The system ofclaim 8, wherein the demand deposit account is a first demand deposit account and the financial institution is a first financial institution, wherein the funds are received from a sender having a second demand deposit account at a second financial institution, and wherein the funds are received by the first financial institution directly from the second financial institution via an interbank electronic payment clearing system.

10. The system ofclaim 9, wherein the first and second financial institutions are first and second banks.

11. The system ofclaim 1, wherein the rules engine is accessible by the user to configure a manner in which received funds are split between a plurality of accounts held by the user at a financial institution.

12. The system ofclaim 1, wherein the rules engine is accessible by the user to configure a manner in which received funds are forwarded to another user that is registered with the payment network.

13. The system ofclaim 1, wherein the rules engine is configured to permit the user to configure the speed with which funds are transferred from the user to a recipient, wherein the speed is selected from the group consisting of immediate, same day, overnight, and 2-day payment.

14. The system ofclaim 1, wherein the rules engine is configured to permit the user to configure a transaction limit for outgoing funds transfers, such that an outgoing funds transfer having a dollar value in excess of the transaction limit is not permitted.

15. The system ofclaim 1, wherein the rules engine is configured to permit the user to configure a transaction limit, such that outgoing funds transfers having an aggregate dollar value within a predetermined time period in excess of the transaction limit are not permitted.

16. The system ofclaim 1, wherein the rules engine is configured to permit users to configure aspects of the plurality of public identifiers that are displayed to other users.

17. The system ofclaim 16, wherein the aspects that are configured include a name of the user.

18. A computer-implemented data processing system, comprising:

a computer system including a processor and computer readable storage media, the computer readable storage media having instructions stored therein that when executed by the computer system configure the computer system to:

process funds transfers between a user and a plurality of other users, each of the funds transfers being initiated by the user or by one of the plurality of other users, the funds transfers using a plurality of public identifiers to identify the user; and

provide a graphical user interface to the user, the graphical user interface comprising at least one display screen, the at least one display screen comprising an identifier management field useable by the user to separately manage attributes of different public identifiers from the plurality of public identifiers; and

an account information directory implemented in a data storage system, the account information directory maintaining registration information for the user, the registration information including the plurality of public identifiers and account number information.

19. The system ofclaim 18, wherein the at least one display screen includes a field that displays a link to modify a source account.

20. The system ofclaim 18, wherein the at least one display screen includes a field that displays an indicator reflecting whether one of the plurality of public identifiers is active.

21. The system ofclaim 18, wherein the at least one display screen includes a field that displays a list of the plurality of public identifiers.

22. A computer-implemented payment processing method comprising:

storing, by a computer system, information regarding a recipient in an account information directory, the account information directory being implemented in a data storage system, the information including a plurality of public identifiers identifying the recipient;

receiving, by the computer system, a funds transfer request identifying the recipient by one of the plurality of public identifiers, the funds transfer request being received via a computer network;

determining, by the computer system, a private identifier for the recipient based on the received public identifier;

transmitting, by the computer system, a funds transfer message via the computer network to cause funds to be transferred from a sender to the recipient, the funds transfer message being generated using the private identifier; and

providing a graphical user interface to the recipient, the graphical user interface comprising at least one display screen, the at least one display screen comprising an identifier management field useable by the recipient to separately manage attributes of different public identifiers from the plurality of public identifiers.

Images