This application relates generally to information security. More specifically, this application relates to methods and systems using information security to transfer funds to deposit accounts.
There are a number of instances in which parties wish to deposit funds directly to other's accounts. In some of these instances, the parties are trusted parties, in which case a holder of the account may provide those parties with the primary account number for the deposit account and identify the financial institution where it is held. This is often done, for example, with employers who arrange for direct deposit of employee paychecks and similar applications.
In other instances, however, the parties are not trusted parties, and the holder of the account is understandably reluctant to disclose his account information. This may occur, for example, in the context of refunds to be made by parties in certain commercial transactions, in the context of electronic commercial transactions, and in a variety of other applications. Traditionally, the account holder must choose between refusing to disclose his account information, in which case the convenience of a direct deposit is forgone, or to accept an unknown level of risk that such personal financial information will be used improperly. Because of the high level of discomfort many individuals have with such disclosure, particularly with parties who are not known to be trustworthy, a very large number of potential direct-deposit transactions have simply not been made; they have instead been substituted with much less convenient and less timely alternatives, such as through preparation and mailing of checks or other negotiable instruments.
There is accordingly a general need in the art for improved methods and systems that permit deposits to be made directly into deposit accounts while ensuring the security and confidentiality of private account information.
Embodiments of the invention thus provide methods and systems that permit the deposit of funds in a deposit account without disclosing private account information to a party who may be initiating the deposit. Embodiments of the invention make use of a nonpublic mapping for a plurality of deposit accounts from indirect identifications of those accounts to direct identifications of those accounts. Thus, the initiating party may supply the indirect identification at one node of a financial-services network, with the mapping being used to supply the financial institution that maintains the account with the direct identification.
Thus, in a first set of embodiments, a method is provided for depositing funds in a deposit account. A request to credit a specified amount to the deposit account is received at a node of a financial-services network that comprises a plurality of interconnected nodes. The request includes an indirect identification of the deposit account. A direct identification of the deposit account is determined from the indirect identification and from a nonpublic mapping of a plurality of respective indirect identifications to respective direct identifications of respective deposit accounts. An instruction is issued to credit the deposit account with the specified amount in accordance with the determined direct identification.
Different architectures for the financial-services network may be supported. For example, in some such embodiments, the financial-services network comprises a hub node and a plurality of ordinary nodes, each of which is in direct communication with the hub node. In some instances, the request may be received at the hub node. In other embodiments, each of the plurality of the interconnected nodes is in direct communication with a second plurality of the interconnected nodes. The financial-services network may also be provided in communication with other financial-services networks. For instance, in one embodiment, receiving the request may comprise receiving the request as routed from a second financial-services network that comprises a second plurality of interconnected nodes. Alternatively, issuing the instruction to credit the deposit account may comprise transmitting the instruction for routing over a second financial-services network that comprises a second plurality of interconnected nodes. In some cases, at least some of the nodes may have automated teller machines (“ATMs”), in which case the financial-services network comprises an ATM network.
The nonpublic mapping may be maintained in one embodiment at the node at which the request is received. In another embodiment, the nonpublic mapping may comprise a plurality of nonpublic mappings of respective indirect identifications to respective direct identifications of respective deposit accounts. Each such nonpublic mapping may be maintained at a different node comprised by the financial-services network. At least part of the nonpublic mapping may be encrypted. In some instances, the request may further include an identification of a financial institution that maintains the deposit account. Issuing the instruction to credit the deposit account may then comprise transmitting the instruction for routing to a node comprised by the financial institution. In other instances, the node at which the request is received may be comprised by a financial institution that maintains the deposit account.
Examples of indirect identifications that may be used in embodiments of the invention include a name of a holder of the deposit account, a name of a relative of the holder of the deposit account, a date meaningful to the holder of the deposit account, and a truncated portion of a numerical identifier of the holder of the deposit account. Examples of the direct identification include a primary account number for the deposit account and perhaps also a routing number identifying a financial institution that maintains the deposit account.
The methods of the present invention may also be embodied in a computer-readable storage medium having a computer-readable program embodied therein for directing operation of a computational device comprised by a node of the financial-services network. The computational device includes an input device, a communications system, a processor, and a storage device. The computer-readable program includes instructions for operating the computational device to deposit funds in a deposit account in accordance with the embodiments described above.
A further understanding of the nature and advantages of the present invention may be realized by reference to the remaining portions of the specification and the drawings wherein like reference numerals are used throughout the several drawings to refer to similar components. In some instances, a sublabel is associated with a reference numeral and follows a hyphen to denote one of multiple similar components. When reference is made to a reference numeral without specification to an existing sublabel, it is intended to refer to all such multiple similar components.
Embodiments of the invention provide methods and systems for depositing funds in deposit accounts without compromising the security and confidentiality of private account information. Such deposits may be made using embodiments of the invention even by those other than a “holder” of the account, which is intended to refer herein to any person having rights to make withdrawals from the account. As used herein, a “deposit account” is intended to refer to any financial account to which funds may be deposited for the benefit of the account holder. The term is intended to encompass both time-deposit accounts and transaction accounts. Examples of deposit accounts thus includes checking accounts, savings accounts, demand-deposit accounts, certificate accounts, share accounts, money-market mutual-fund accounts, negotiable withdrawal order accounts, and the like.
The capability of making deposits in this way is provided in part by drawing a distinction between “indirect information” and “direct information” that may be used to identify deposit accounts. In particular, direct information is intended to refer to a unique identifier of the deposit account that is used by a financial institution that maintains the account in identifying that account. This direct information is usually shared by the financial institution with the account holder, and may sometimes be shared with third parties by the account holder, but is generally otherwise viewed as private information between the financial institution and account holder. Merely by way of example, such direct information could comprise a primary account number (“PAN”) used by the financial institution in identifying the account. In some instances, the direct information might also include a routing or transit number used to identify the financial institution itself.
In contrast, indirect information is intended to refer to any information that is not direct information and may be used, such as described herein, to identify the deposit account. In some instances, such indirect information may identify the account holder, from which the financial institution is able to identify the account. Usually, the indirect information that is used in embodiments of the invention enjoys an intermediate level of confidentiality, not being readily available publicly to third parties but not being viewed by the account holder as as sensitive as the direct information. For example, in some embodiments the indirect information comprises a name of a relative of the holder, such as a mother's or grandmother's maiden name. In other embodiments, the indirect information comprises a date meaningful to the holder, such as a birth date, birth date of a child or other relative, anniversary date, and the like. In still other embodiments, the indirect information comprises a truncated portion of a numerical identifier of the holder, such as the last four digits of a Social Security Number, and the like.
According to embodiments of the invention, a nonpublic mapping is provided between the indirect information and the direct information that may be applied at a node within a financial-services network. The invention is not restricted to a particular architecture for the network and, indeed,
In
In some embodiments, communications may be provided among a plurality of financial-services networks, such as illustrated schematically in
An illustration is provided in
In the illustration, the conversion of the indirect identification to the direct identification is effected at the hub node 312, but may more generally take place at any node. The network node at which such conversion takes place may reflect an accommodation of competing concerns, and the point at which this accommodation is made may differ in different embodiments. For example, as is evident from the description that follows, the amount of information that need be maintained by the conversion node is greater if the conversion takes place closer in the network to the node 308 where the indirect information is received. At the same time, however, current financial-services networks are generally equipped for transmission of the direct information but not for the indirect information; fewer modifications are needed to such existing network infrastructures if the conversion takes place closer in the network to the node 316 where the deposit is to be effected.
An example of a data record that may be provided by the party 304 to node 308 is shown at block 332 in
At node 312, the indirect identification in the data record is compared with a nonpublic mapping 336 that defines a relationship between a plurality of indirect identifications to direct identifications of respective deposit accounts. The security and confidentiality of the direct identification is maintained at least in part through the nonpublic character of the mapping. In some cases, additional security may also be provided through a variety of mechanisms, such as by encrypting all or a portion of the mapping, periodically changing what qualifies as indirect identifications, and the like. Also, while the exemplary mapping shows only a single indirect identification for each deposit account, in other embodiments multiple indirect identifications may be provided in the mapping for some or all of the deposit accounts. Such multiple indirect identifications permit different parties 304 to use different indirect identifications to identify the same deposit account, which may be useful in cases where the account holder wishes to exercise greater selective discretion over which information to disclose to such parties 304.
In the illustrated example, the mapping 336 associates combinations of holder birth dates and mother's maiden names with account numbers, which thereby correspond to the direct identifications of deposit accounts. Thus, a processor at node 312 uses the mapping information to generate an instruction 340 to credit the deposit account with the specified amount, identifying the deposit account with the direct identification. This instruction is transmitted through the remainder of the network until it is delivered to the node 316 comprised by the financial institution 324. While
Also, while the configuration shown in
It is noted that access to the mapping is generally used only where a request made for a deposit to an account. Other types of transactions are typically prevented from being executed only with the indirect information, requiring instead that the direct information be provided by the individual attempting to initiate the transaction. For example, a withdrawal from an account, a transfer of funds from an account, and the like will normally require that the individual provide the direct information. This precludes an individual from withdrawing funds from another's account simply based on relatively insecure indirect information.
Methods for depositing funds in a deposit account are thus summarized for a variety of embodiments with the flow diagram shown in
In many instances, it will be verified that funds are available to support the deposit, as indicated at block 416. For example, the party may need to provide cash, his own account number to be debited, an approved credit instrument, or similar funds support to a teller, automated device, or other person or device in order to support the deposit request. Execution of the deposit request may be denied in the event the party is unable to supply the necessary funds. At block 420, the party additionally supplies the indirect identification of the deposit account and perhaps also the identity of the financial institution so that the financial network may route a request to credit the deposit account to the conversion node, as indicated at block 424. The conversion node is the node at which the direct identification of the deposit account is determined at block 428 with the nonpublic mapping as described above.
The conversion node thus performs at least three functions in embodiments of the invention. It receives the request to credit the deposit account, it determines the direct identification from the nonpublic mapping, and it issues the instruction to credit the deposit account. In instances where the request originates in another financial-services network, its receipt at the conversion node may be direct from the other network or may be routed through one or more intermediate nodes in the origination-node network, the conversion-node network, or even in intermediate networks. In the event that the conversion node is comprised by the financial institution that maintains the deposit account, issuing the instruction to credit the deposit account may be performed directly by that financial institution to perform the credit. In other instances, the credit instruction may be routed from the conversion node to a node that is comprised by the financial institution, as indicated at block 432. The financial-institution node may also be located in a different financial network than the conversion node, in which case the routing may include internetwork transmissions.
Once the credit instruction is received by the financial institution by being received at a node comprised by the financial institution, the direct identification of the deposit account may be used to identify where to deposit the funds. The specified amount is accordingly credited to the deposit account as indicated at block 436.
Each of the nodes comprised by the financial-services network may include a computational device equipped to implement the appropriate communications to transfer the requests and instructions through the network as described above. In addition, those computational devices may be equipped in different ways to process transactions. For instance, one such computational device may comprise an ATM, which includes both structural components and programming instructions to enable it to accept deposits, process withdrawals, transfer funds, and the like. In other cases, the computational device may comprise a teller-station terminal equipped to accept data and processing instructions to record transactions executed by a teller. In still other cases, the computational device may comprise an Internet gateway having connections and processing instructions to transmit financial-transaction information securely. Some of the nodes may also comprise computational devices whose function is completely internal to network and that are not equipped for external interactions.
A general structure for such computational devices is provided with a schematic illustration in
The computational device 500 also comprises software elements, shown as being currently located within working memory 520, including an operating system 524 and other code 522, such as a program designed to implement methods of the invention. It will be apparent to those skilled in the art that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.
Thus, having described several embodiments, it will be recognized by those of skill in the art that various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the invention. Accordingly, the above description should not be taken as limiting the scope of the invention, which is defined in the following claims.