Patent Publication Number: US-9413747-B2

Title: Shutting down access to all user accounts

Description:
CROSS-REFERENCE OF RELATED APPLICATIONS 
     This application is a continuation of U.S. patent application Ser. No. 14/175,136, filed Feb. 7, 2014, which is hereby incorporated by reference in its entirety. 
    
    
     FIELD OF THE INVENTION 
     The present invention embraces a system for restricting access to a user&#39;s account via one or more account access channels. The system typically includes a processor, a memory, and an access restriction module stored in the memory. The access restriction module is typically configured to allow the user to restrict access to the account via one or more account access channels. 
     BACKGROUND 
     Over the last few years, there has been a proliferation of ways to access a user&#39;s bank account, including via a debit card, credit card, mobile wallet, online or mobile banking, or automated teller machine (ATM). That said, a need exists for users to be able restrict access to their accounts if a way of accessing their accounts becomes compromised. 
     SUMMARY 
     In one aspect, the present invention embraces a method of restricting access to a user&#39;s account via one or more account access channels. The present invention also embraces a system configured for performing one or more of the steps of the method. 
     The method typically includes: integrating a first account access channel associated with the user&#39;s account with a first access restriction procedure; receiving a request from the user to implement the first access restriction procedure; and, based on receiving the request from the user to implement the first access restriction procedure, implementing the first access restriction procedure, wherein implementing the first access restriction procedure includes restricting access to the user&#39;s account via the first account access channel. 
     In a particular embodiment, the method includes: based on receiving the request from the user to implement the first access restriction procedure, prompting the user to provide predefined authentication information; and receiving the predefined authentication information from the user; wherein implementing the first access restriction procedure is further based on receiving the predefined authentication information from the user. 
     In another particular embodiment, the method includes: integrating a second account access channel associated with the user&#39;s account with the first access restriction procedure; wherein implementing the first access restriction procedure includes restricting access to the user&#39;s account via the second account access channel. 
     In yet another particular embodiment, the method includes: integrating a second account access channel associated with the user&#39;s account with a second access restriction procedure; receiving a request from the user to implement the second access restriction procedure; and, based on receiving the request from the user to implement the second access restriction procedure, implementing the second access restriction procedure, wherein implementing the second access restriction procedure includes restricting access to the user&#39;s account via the second account access channel. 
     In yet another particular embodiment, the method includes: graphically presenting a first access restriction button to the user via an online banking interface or an automated teller machine interface; wherein receiving the request from the user to implement the first access restriction procedure includes determining that the user has engaged the first access restriction button via the online banking interface or the automated teller machine interface. 
     In yet another particular embodiment, restricting access to the user&#39;s account via the first account access channel includes disabling access to the user&#39;s account via the first account access channel. 
     In yet another particular embodiment, restricting access to the user&#39;s account via the first account access channel includes implementing an authentication procedure that requires secondary authentication before permitting access to the user&#39;s account via the first account access channel. 
     The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Having thus described embodiments of the invention in general terms, reference will now be made the accompanying drawings, wherein: 
         FIG. 1  depicts a method for restricting access to a user&#39;s account(s) via one or more account access channels in accordance with an aspect of the present invention; 
         FIG. 2  depicts a banking system and environment in accordance with an aspect of the present invention; 
         FIG. 3  schematically depicts an automated teller machine in accordance with an aspect of the present invention; 
         FIG. 4  schematically depicts a user&#39;s mobile device in accordance with an aspect of the present invention; 
         FIG. 5  schematically depicts a user&#39;s computing device in accordance with an aspect of the present invention; and 
         FIG. 6  schematically depicts a banking system in accordance with an aspect of the present invention. 
     
    
    
     DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION 
     Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein. Furthermore, when it is said herein that something is “based on” something else, it may be based on one or more other things as well. In other words, unless expressly indicated otherwise, as used herein “based on” means “based at least in part on” or “based at least partially on.” Like numbers refer to like elements throughout. 
     In some embodiments, an “entity” as used herein may be a financial institution. For the purposes of this invention, a “financial institution” may be defined as any organization, entity, or the like in the business of moving, investing, or lending money, dealing in financial instruments, or providing financial services. This may include commercial banks, thrifts, federal and state savings banks, savings and loan associations, credit unions, investment companies, insurance companies and the like. In some embodiments, the entity may allow a user to establish an account with the entity. An “account” may be the relationship that the user has with the entity. Examples of accounts include a deposit account, such as a transactional account (e.g., a banking account), a savings account, an investment account, a money market account, a time deposit, a demand deposit, a pre-paid account, a credit account, a non-monetary user profile that includes only personal information associated with the user, or the like. The account is associated with and/or maintained by an entity. In other embodiments, an “entity” may not be a financial institution. 
     As used herein, an “online banking account” is an account that is associated with one or more user accounts at a financial institution. For example, the user may have an online banking account that is associated with the user&#39;s checking account, savings account, investment account, and/or credit account at a particular financial institution. A username and password are typically associated with the online banking account and can be used by the user to gain access to the online banking account. The online banking account may be accessed by the user over a network (e.g., the Internet) via a computer device, such as a personal computer, laptop, or mobile device (e.g., a smartphone or tablet). The online banking account may be accessed by the user via a mobile or online banking website or via a mobile or online banking application. A customer may access an online banking account to view account balances, view transaction history, view statements, transfer funds, and pay bills. More than one user may have access to the same online banking account. In this regard, each user may have a different username and password. Accordingly, one or more users may have a sub-account associated with the online banking account. 
     As used herein, an “account access channel” is any way in which an account holder can access his or her account (e.g., make payments or purchases, transfer funds, pay bills, withdraw funds, deposit funds, view account balances, view transaction history, view statements, and the like). By way of example, an account access channel may be the account holder&#39;s debit card and/or any associated debit card information (e.g., card number, expiration date, account holder name, security code, and/or personal identification number (PIN)). An account access channel may be the account holder&#39;s credit card and/or any associated credit card information (e.g., account number, expiration date, account holder name, address, zip code, and/or security code). An account access channel may be the account holder&#39;s online banking account that is associated with the holder&#39;s account(s) and/or any information needed to access the online banking account, such as a username, password, and any other login or authentication information. An account access channel may be a mobile device (e.g., a laptop, personal digital assistant (PDA), cell phone, smart phone, tablet, mp3 player, or any other suitable electronic device) or other computing device (e.g., personal computer) that the account holder regularly uses to access the account (e.g., via online banking or a mobile wallet). An account access channel may be the account holder&#39;s ATM card or bank card and/or any associated card information (e.g., card number and/or PIN), which the account holder may use to access his or her account (e.g., via an ATM). An account access channel may be the account holder&#39;s checks associated with the account and associated information that could be used for an electronic check. By way of further example, an account access channel may by any information need to engage in a wire transfer or electronic funds transfer. 
     In some embodiments, the “user” may be a customer (e.g., an account holder or a person who has an account (e.g., banking account, credit account, or the like) at the entity) or potential customer (e.g., a person who has submitted an application for an account, a person who is the target of marketing materials that are distributed by the entity, a person who applies for a loan that not yet been funded). In other embodiments, the “customer” may refer to the user. 
     In one aspect, the present invention generally relates to a system for restricting access to a user&#39;s account(s) via one or more account access channels. More particularly, the user may discover that one or more account access channels have been compromised (e.g., lost or misappropriated). For example, the user may lose a debit card or mobile device. Based on such account access channel being compromised, the user may request that access to the user&#39;s account(s) via such account access channel be restricted. Based on such request, the system may prevent such account access channel from being used to access the user&#39;s account(s) or otherwise restrict access to the user&#39;s account(s). 
     Referring now to  FIG. 1 , a general process flow  100  is provided for restricting access to a user&#39;s account(s) via one or more account access channels. 
     At block  110 , the method includes integrating one or more account access channels associated with one or more user accounts with an access restriction procedure. The step of integrating the access channels with the access restriction procedure may be initiated by the user or by the entity providing the user&#39;s account(s). For example, the entity might automatically integrate issued debit cards, ATM cards, credit cards, and online banking accounts with an access restriction procedure. Alternatively, the user might initiate the step of integrating the access channels with the access restriction procedure. In this regard, the user may initiate the step of integrating the access channels with the access restriction procedure via an online banking interface or ATM interface. 
     The access restriction procedure typically defines the procedure that is implemented (e.g., upon the initiation of the user) if account access channels become compromised or if the user fears the account access channels become compromised. In this regard, the access restriction procedure typically defines the extent to which access to the one or more user accounts is restricted if the account access channels become compromised or if the user fears the account access channels become compromised. In one embodiment, the access restriction procedure, once implemented, may entirely prevent the account access channels from being used to access the user&#39;s account(s). For example, if the user losers his or her debit card, then debit card and its associated information (e.g., card number) might be blocked from being used in future transaction (e.g., in-person transactions, ATM transactions, and/or online transactions). Alternatively, the access restriction procedure may restrict access to the user&#39;s account(s) via the account access channels by requiring additional authentication information before permitting access to the user&#39;s account(s). For example, if the user fears that his or her online banking username has been compromised, then the access restriction procedure might require the user to provide, in addition to the user&#39;s online banking username and password, secondary authentication information (e.g., a PIN, biometric information, such as voice authentication, a fingerprint, and/or a retina scan, or an answer to a security question) before permitting access to the user&#39;s online banking account. By way of further example, if the user fears that his or her debit card has been compromised, then the access restriction procedure might require the user to provide, in addition to the user&#39;s PIN, secondary authentication information (e.g., zip code, biometric information, such as voice authentication, a fingerprint, and/or a retina scan, or an answer to a security question) before allowing a transaction involving the debit card to be completed. Furthermore, the access restriction procedure may initiate the replacement of the account access channels. For example, if the account access channels include a debit card or credit card, then the access restriction procedure may initiate the process for issuing a replacement debit or credit card. By way of further example, if the account access channels include the user&#39;s online banking account, then the access restriction procedure may initiate the process for issuing the user a new username and password for the user&#39;s online banking account. Each access restriction procedure may be defined by the user and/or by the entity. 
     In order to integrate the one or more account access channels with the access restriction procedure, identification information regarding one or more account access channels (e.g., information regarding the user&#39;s debit card, credit card, ATM card, mobile device, and/or online banking account) is typically received from the user or from the entity providing the user&#39;s account(s). If the account access channel is a mobile device or other computing device, the identification information may be any information sufficient to generate a device “fingerprint,” or unique signature of the device. Device identification information may be collected from a variety of sources. In some embodiments, the device identification information includes an identification code. The identification code may be but is not limited to a serial number or an item number of the device. In some embodiments, the device identification information may be associated with a chip associated with the device. The chip may be but is not limited to a subscriber identification module (SIM) card, removable hard drive, processor, microprocessor, or the like. In other embodiments, the device identification information may be associated with a removable part of the device. Removable parts include but are not limited to detachable keyboards, battery covers, cases, hardware accessories, or the like. Removable parts may contain serial numbers or part numbers. In alternative embodiments, a unique key, code, or piece of software provided by a financial institution may be downloaded onto the device. This unique key, code, or piece of software may then serve as device authentication information. In some embodiments, device identification information may need to be entered manually at the device. For example, the user may be prompted (e.g., via an online banking interface) to manually enter the device identification information (e.g., a serial number, an identification code, an International Mobile Station Equipment Identity (IMEI), a phone number, a chip, a removable part, or similar pieces of device identification information). In other embodiments, device identification information may not be based on user input received at the device. Instead, the device identification information may be automatically provided by the device. In yet another embodiment, the device may provide the information without requiring user input after receiving a request for the identification information. 
     This information regarding the account access channels is then associated with the access restriction procedure (e.g., by creating a record in memory associating the account access channels with the access restriction procedure). 
     In one embodiment, the access restriction procedure may integrated with a plurality of account access channels (e.g., all of the user&#39;s account access channels) such that if the access restriction procedure is initiated, then access to the user&#39;s account(s) from each account access channel may be restricted. In one particular embodiment, each user account may have a single access restriction procedure that is (i) linked to each of the account&#39;s access channels and (ii) configured, when initiated, to disable access to the account from each account access channel. 
     In an alternative embodiment, each user account may have a plurality of access restriction procedures, each of which may be integrated with different account access channels. For example, a user account may have a first access restriction procedure linked to the user&#39;s debit card, a second access restriction procedure linked to the user&#39;s online banking account, and a third access restriction procedure linked to the user&#39;s mobile device. The first access restriction procedure may be configured to disable access to the user&#39;s account via the debit card (e.g., prevent debit card transactions online, in a store, or at an ATM) or, alternatively, to require secondary authentication information. The first access restriction procedure may be further configured to automatically initiate the process for replacing the user&#39;s debit card. The second access restriction procedure may be configured to disable access to the user&#39;s online banking account or, alternatively, to require secondary authentication information before allowing access to the user&#39;s online banking account. The second access restriction procedure may be further configured to automatically initiate the process for replacing the user&#39;s online banking username and/or password. The third access restriction procedure may be configured to prevent access to the user&#39;s account via the mobile device. For example, using identification information from the mobile device, the mobile device may be prevented from accessing the user&#39;s account, such as by preventing the mobile device from logging into the customer&#39;s online banking account or being used as a mobile wallet. Furthermore, because the mobile device may have saved information related to the user&#39;s online banking account (e.g., the user&#39;s online banking username), the third access restriction procedure may be further configured to restrict access to the user&#39;s online banking account (e.g., by requiring secondary authentication information) from any device, not just the user&#39;s mobile device. 
     A particular mobile device may be identified by gathering device identification information from the mobile device to generate the device&#39;s “fingerprint,” or unique signature of the mobile device. Device identification information may be collected from a variety of sources. In some embodiments, the device identification information includes an identification code. The identification code may be but is not limited to a serial number or an item number of the device. In some embodiments, the device identification information may be associated with a chip associated with the mobile device. The chip may be but is not limited to a subscriber identification module (SIM) card, removable hard drive, processor, microprocessor, or the like. In other embodiments, the device identification information may be associated with a removable part of the mobile device. Removable parts include but are not limited to detachable keyboards, battery covers, cases, hardware accessories, or the like. Removable parts may contain serial numbers or part numbers. In alternative embodiments, a unique key, code, or piece of software provided by a financial institution may be downloaded onto the mobile device. This unique key, code, or piece of software may then serve as device identification information. Typically, the device identification information (e.g., a serial number, an identification code, an International Mobile Station Equipment Identity (IMEI), a phone number, a chip, a removable part, or similar pieces of device identification information) is collected from the mobile device without requiring user input. For example, the device identification information may be automatically provided by the mobile device. Alternatively, the mobile device may provide the information without requiring user input after receiving a request from a system for the identification information. In other embodiments, device identification information may be entered manually at the mobile device. For example, if the mobile device&#39;s serial number cannot be automatically located (perhaps due to interference, long range, or similar hindrance), the user may be prompted for manual entry of the serial number (or an identification code, an International Mobile Station Equipment Identity (IMEI), a phone number, a chip, a removable part, or similar pieces of device identification information). The device identification information may be stored and subsequently used to identify the mobile device. 
     In some embodiments, an access restriction procedure is configured to restrict access to a single user account (e.g., a checking account linked to a debit card). That said, in other embodiments, an access restriction procedure may be configured to restrict access to a plurality of user accounts. For example, an access restriction procedure integrated with the user&#39;s online banking account may be configured to restrict access via the online banking account to each user account (e.g., a checking account, savings account, and credit account) linked to the online banking account. 
     At block  120 , the method includes receiving a request from the user to implement an access restriction procedure. The request from the user to implement the access restriction procedure may be sent by the user via an online banking interface (e.g., via a mobile banking application, via a mobile banking website, or via an online banking website) or an ATM interface. In this regard, the online banking interface or ATM interface may present a graphical user interface (GUI) having an icon or button linked to the access restriction procedure, such that if the user engages the icon or button, then the online banking interface or ATM interface transmits the request to implement the access restriction procedure. For example, the online banking interface or ATM interface may present a red “Shut Down All Account Access” button linked to an access restriction procedure integrated with all of the user&#39;s account access channels. By way of further example, the online banking interface or ATM interface may present multiple buttons each linked to a different access restriction procedure integrated with a particular account access channel, such as a “Lost Debit Card” button linked to an access restriction procedure integrated with the user&#39;s debit card or a “Compromised Online Banking Account” button linked to an access restriction procedure integrated with the user&#39;s online banking account. 
     At block  130 , optionally, the user is prompted to provide predefined authentication information (e.g., predefined by the user or by the entity). This predefined authentication information (e.g., secondary authentication information) is typically in addition to any authentication information already provided by the user (e.g., a username and password provided to initiate an online banking session or a debit/ATM card and PIN to initiate an ATM session). The predefined authentication information may be a password, a passcode, a PIN, biometric information (e.g., voice authentication, a fingerprint, and/or a retina scan), an answer to one or more security questions, the identity of a computing device being used or in the user&#39;s possession, or any other information that can be used to authenticate the identity of the user (e.g., determine that the authentication information is associated with the user) and determine that the user has authority to access the account. In one embodiment, authentication information may include a unique intrinsic user activity, such as making a predefined motion with a user device. Using a unique intrinsic user activity for authentication is described in commonly assigned U.S. Pat. No. 8,116,453, which is hereby incorporated by reference in its entirety. 
     Next, at block  140 , the predefined authentication information is received from the user (e.g., via the online banking interface or ATM interface). 
     At block  150 , based on (i) receiving the request from the user to implement the access restriction procedure and (ii) receiving the predefined authentication information, the access restriction procedure is implemented by restricting access (e.g., disabling access or requiring secondary authentication information) to the integrated account access channels as defined by the access restriction procedure. That said, in some embodiments, the method may not require any secondary authentication information before implementing the access restriction procedure. In such embodiments, the access restriction procedure may be implemented upon receiving the request from the user to implement the access restriction procedure. 
     Once the access restriction procedure has been implemented, the system may subsequently receive an indication of a transaction via a restricted account access channel. If the access restriction procedure is configured to prevent the restricted account access channel from being used to access the user&#39;s account, then the transaction would be denied. For example, a credit card transaction may be denied, or an attempt to initiate an online banking session or ATM session may be blocked. 
     Alternatively, if the access restriction procedure is configured to require secondary authentication before permitting access to the user&#39;s account, then, based upon receiving the indication of the transaction, the user would be presented with a request to provide such secondary authentication. For example, if the user is attempting to initiate an online banking, then the user may be prompted to answer a security question. By way of further example, if the user is attempting to engage in a credit card transaction, then the user may be prompted to provide their zip code or a PIN. Thereafter, if the correct secondary authentication information is provided, then the transaction via the restricted account access channel would be permitted. That said, if correct secondary authentication information is not provided, then the transaction via the restricted account access channel is denied or blocked. 
     Once the access restriction procedure has been implemented, access may be restricted pursuant to the access restriction procedure indefinitely or for a predefined period of time. If the access restriction procedure is configured to restrict access for a predefined period of time, then the access restrictions are terminated after the predefined period of time has elapsed. If the access restriction procedure is configured to restrict access for an indefinite or a predefined period of time, the access restriction procedure might be configured to be terminated if predefined authentication information is provided (e.g., a PIN, biometric information, such as voice authentication, a fingerprint, and/or a retina scan, or an answer to one or more security questions). 
       FIG. 2  provides a block diagram illustrating a banking system  600  and environment  200 , in accordance with an embodiment of the present invention. As illustrated in  FIG. 2 , the banking environment  200  typically includes an automated teller machine  300 , a mobile device  400 , and/or a computing device  500 . The computing device may be any device that employs a processor and memory and can perform computing functions, such as a personal computer or a mobile device. As used herein, a “mobile device” is any mobile communication device, such as a cellular telecommunications device (i.e., a cell phone or mobile phone), personal digital assistant (PDA), a mobile Internet accessing device, a tablet computer, a laptop, or other mobile device. 
     The ATM  300 , mobile device  400 , and the computing device  500  are typically configured to communicate over a network  250  with a financial institution&#39;s banking system  600 . The ATM  300 , the mobile device  400 , the computing device  500 , and the financial institution&#39;s banking system  600  are each described in greater detail below with reference to  FIGS. 3-6 . The network  250  may include a local area network (LAN), a wide area network (WAN), and/or a global area network (GAN). The network  250  may provide for wireline, wireless, or a combination of wireline and wireless communication between devices in the network. In one embodiment, the network  250  includes the Internet. In one embodiment, the network  250  includes a wireless telephone network  252 . 
     In general, ATM  300 , the mobile device  400 , and/or the computing device  500  are configured to connect with the network  250  to log the user into the banking system  600 . The banking system  600  involves authentication of the user in order to access the user&#39;s account on the banking system  600 . For example, the banking system  600  is a system where the user logs into his/her account such that the user can access data that is associated with the user. For example, in one embodiment of the invention, the system  600  may allow the user to use the mobile device  400  or computing device  500  to log into the user&#39;s online banking account. In another embodiment, the system  600  may allow the user to access his or her account via the ATM  300 . Logging into the banking system  600  generally requires that the user authenticate his/her identity using a user name, a passcode, a cookie, a biometric identifier, a PIN, a private key, a token, and/or another authentication mechanism that is provided by the user to the banking system  600  via the ATM  300 , the mobile device  400 , and/or the computing device  500 . 
     The financial institution&#39;s banking system  600  is typically in network communication with other devices. In one embodiment, an application download server may be used to download online and/or mobile banking software applications that interacts with the banking system  600  to the mobile device  400  and/or computing device  500 . In some embodiments of the invention, the application download server is configured to be controlled and managed by one or more third-party data providers (not shown in  FIG. 2 ) over the network  250 . In other embodiments, the application download server is configured to be controlled and managed over the network  250  by the same entity that maintains the banking system  600 . 
     As depicted in  FIG. 3 , the ATM  300  typically includes a communication interface  310 , a processor  320 , a user interface  330 , and a memory  340  having an ATM datastore  342  and an ATM application  344  stored therein. As shown, the processor  320  is operatively connected to the communication interface  310 , the user interface  330 , and the memory  340 . 
     The communication interface  310  of the ATM may include a contactless interface  350 . In one embodiment, the contactless interface is an NFC interface. The contactless interface  350  is configured to contactlessly and/or wirelessly send and/or receive information over relatively short ranges (e.g., within four inches, within three feet, and the like). The contactless interface  350  may include a transmitter, receiver, smart card, key card, proximity card, Bluetooth® device, radio frequency identification (RFID) tag and/or reader, and/or the like. In some embodiments, the contactless interface  350  communicates information via radio, IR, and/or optical transmissions. Generally, the contactless interface  350  is configured to operate as a contactless transmitter and/or as a contactless receiver. The contactless interface  350  functions to enable transactions with users utilizing an external apparatus capable of contactless communication. Also, it will be understood that the contactless interface  350  may be embedded, built, carried, and/or otherwise supported in and/or on the ATM  300 . In some embodiments, the contactless interface  350  is not supported in and/or on the ATM  300 , but the contactless interface  350  is otherwise operatively connected to the ATM  300  (e.g., where the contactless interface  350  is a peripheral device plugged into the ATM  300 ). The contactless interface  350  of the ATM  300  is configured to contactlessly and/or wirelessly communicate information to and/or from an external device. 
     The communication interface  310  may generally also include a modem, server, transceiver, and/or other device for communicating with other devices and systems (e.g., the system  600 ) on a network. 
     The user interface  330  of the ATM  300  may include a display (e.g., a liquid crystal display, a touchscreen display, and/or the like) which is operatively coupled to the processor  320 . The user interface  330  may include any number of other devices allowing the ATM  300  to transmit/receive data to/from a user, such as a keypad, keyboard, touch-screen, touchpad, microphone, mouse, joystick, other pointer device, button, soft key, and/or other input device(s). For example, the user can use the user interface  330  to submit a request to implement the access restriction procedure (e.g., by pressing a button linked to the access restriction procedure). 
     As further illustrated in  FIG. 3 , the memory  340  may include ATM applications  344 . It will be understood that the ATM applications  344  can be executable to initiate, perform, complete, and/or facilitate one or more portions of any embodiment described and/or contemplated herein. Generally, the ATM application  344  is executable to receive transaction instructions from the user and perform typical ATM functions, as appreciated by those skilled in the art. In some embodiments, the ATM application is configured to access content, such as data stored in memory  340 , for example in the ATM datastore  342 , or a database in communication with the ATM  300  and may transfer the content to an external device (e.g., a mobile device) if the external device is configured for contactless communication. The content may include coupons, ads, offers, images, financial receipts, account-related documentation, reissued account card, new account card, prepaid cards, or the like. 
     The ATM  300  typically requires users to identify and/or authenticate themselves to the ATM  300  before the ATM  300  will initiate, perform, complete, and/or facilitate a transaction. For example, in some embodiments, the ATM  300  is configured (and/or the ATM application  244  is executable) to authenticate an ATM user based at least partially on an ATM debit card, smart card, token (e.g., USB token, etc.), username, password, PIN, biometric information, and/or one or more other credentials that the user presents to the ATM  300 . Additionally or alternatively, in some embodiments, the ATM  300  is configured to authenticate a user by using one-, two-, or multi-factor authentication. For example, in some embodiments, the ATM  300  requires two-factor authentication, such that the user must provide a valid debit card and enter the correct PIN associated with the debit card in order to authenticate the user to the ATM  300 . Alternatively, the user may be able to provide their online banking username and password for authentication. The ATM  300  may prompt the user to provide further authentication information upon the user&#39;s initiation of a request to implement an access restriction procedure. 
       FIG. 4  provides a block diagram illustrating the mobile device  400  in more detail, in accordance with embodiments of the invention. In one embodiment of the invention, the mobile device  400  is a mobile telephone. However, it should be understood, however, that a mobile telephone is merely illustrative of one type of mobile device that may benefit from, employ, or otherwise be involved with embodiments of the present invention and, therefore, should not be taken to limit the scope of embodiments of the present invention. Other types of mobile devices may include portable digital assistants (PDAs), pagers, mobile televisions, gaming devices, laptop computers, cameras, video recorders, audio/video player, radio, GPS devices, or any combination of the aforementioned. 
     The mobile device  400  typically includes a processor  410  communicably coupled to such devices as a memory  420 , user output devices  436 , user input devices  440 , a communication interface  460 , a power source  415 , a clock or other timer  450 , a camera  480 , and a positioning system device  475 . The processor  410 , and other processors described herein, typically includes circuitry for implementing communication and/or logic functions of the mobile device  400 . For example, the processor  410  may include a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and/or other support circuits. Control and signal processing functions of the mobile device  400  are allocated between these devices according to their respective capabilities. The processor  410  thus may also include the functionality to encode and interleave messages and data prior to modulation and transmission. The processor  410  can additionally include an internal data modem. Further, the processor  410  may include functionality to operate one or more software programs, which may be stored in the memory  420 . For example, the processor  410  may be capable of operating a connectivity program, such as a web browser application  422 . The web browser application  422  may then allow the mobile device  400  to transmit and receive web content, such as, for example, location-based content and/or other web page content, according to a Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and/or the like. 
     The processor  410  is typically configured to use the communication interface  460  to communicate with one or more other devices on the network  250 . In this regard, the communication interface  460  typically includes an antenna  476  operatively coupled to a transmitter  474  and a receiver  472  (together a “transceiver”). The processor  410  is typically configured to provide signals to and receive signals from the transmitter  474  and receiver  472 , respectively. The signals may include signaling information in accordance with the air interface standard of the applicable cellular system of the wireless telephone network  252 . In this regard, the mobile device  400  may be configured to operate with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the mobile device  400  may be configured to operate in accordance with any of a number of first, second, third, and/or fourth-generation communication protocols and/or the like. For example, the mobile device  400  may be configured to operate in accordance with second-generation (2G) wireless communication protocols IS-136 (time division multiple access (TDMA)), GSM (global system for mobile communication), and/or IS-95 (code division multiple access (CDMA)), or with third-generation (3G) wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA) and/or time division-synchronous CDMA (TD-SCDMA), with fourth-generation (4G) wireless communication protocols, and/or the like. The mobile device  400  may also be configured to operate in accordance with non-cellular communication mechanisms, such as via a wireless local area network (WLAN) or other communication/data networks. 
     The communication interface  460  may also include a near field communication (NFC) interface  470 . As used herein, the phrase “NFC interface” generally refers to hardware and/or software that is configured to contactlessly and/or wirelessly send and/or receive information over relatively short ranges (e.g., within four inches, within three feet, within fifteen feet, and the like). The NFC interface  470  may include a smart card, key card, proximity card, Bluetooth® device, radio frequency identification (RFID) tag and/or reader, transmitter, receiver, and/or the like. In some embodiments, the NFC interface  470  communicates information via radio, infrared (IR), and/or optical transmissions. In some embodiments, the NFC interface  470  is configured to operate as an NFC transmitter and/or as an NFC receiver (e.g., an NFC reader). Also, it will be understood that the NFC interface  470  may be embedded, built, carried, and/or otherwise supported in and/or on the mobile device  400 . In some embodiments, the NFC interface  470  is not supported in and/or on the mobile device  400 , but the NFC interface  470  is otherwise operatively connected to the mobile device  400  (e.g., where the NFC interface  470  is a peripheral device plugged into the mobile device  400 ). Other apparatuses having NFC interfaces mentioned herein may be configured similarly. In some embodiments, the NFC interface  470  of the mobile device  400  is configured to contactlessly and/or wirelessly communicate information to and/or from a corresponding NFC interface of another apparatus (e.g., an automated teller machine (ATM) or another mobile or computing device). 
     The mobile device  400  typically has a user interface that is, like other user interfaces described herein, made up of user output devices  436  and/or user input devices  440 . The user output devices  436  include a display  430  (e.g., a liquid crystal display or the like) and a speaker  432  or other audio device, which are operatively coupled to the processor  410 . The user input devices  440 , which allow the mobile device  400  to receive data from a user such as the user, may include any of a number of devices allowing the mobile device  400  to receive data from a user, such as a keypad, keyboard, touch-screen, touchpad, microphone, mouse, joystick, other pointer device, button, soft key, and/or other input device(s). The user interface may also include a camera  480 , such as a digital camera. 
     The mobile device  400  may also include a positioning system device  475  that is configured to be used by a positioning system to determine a location of the mobile device  400 . For example, the positioning system device  475  may include a GPS transceiver. In some embodiments, the positioning system device  475  is at least partially made up of the antenna  476 , transmitter  474 , and receiver  472  described above. For example, in one embodiment, triangulation of cellular signals may be used to identify the approximate location of the mobile device  400 . In other embodiments, the positioning system device  475  includes a proximity sensor or transmitter, such as an RFID tag, that can sense or be sensed by devices known to be located proximate a location to determine that the mobile device  400  is located proximate these known devices. 
     The mobile device  400  further includes a power source  415 , such as a battery, for powering various circuits and other devices that are used to operate the mobile device  400 . Embodiments of the mobile device  400  may also include a clock or other timer  450  configured to determine and, in some cases, communicate actual or relative time to the processor  410  or one or more other devices. 
     The mobile device  400  also includes a memory  420  operatively coupled to the processor  410 . As used herein, memory includes any computer readable medium (as defined herein below) configured to store data, code, or other information. The memory  420  may include volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The memory  420  may also include non-volatile memory, which can be embedded and/or may be removable. The non-volatile memory can additionally or alternatively include an electrically erasable programmable read-only memory (EEPROM), flash memory or the like. 
     The memory  420  can store any of a number of applications which include computer-executable instructions/code executed by the processor  410  to implement the functions of the mobile device  400  described herein. For example, the memory  420  may include such applications as a conventional web browser application  422  and/or a mobile banking application  421 . These applications also typically provide a graphical user interface (GUI) on the display  430  that allows the user to communicate with the mobile device  400 , the banking system  600 , and/or other devices or systems. In one embodiment of the invention, when the user decides to enroll in an online banking program, the user downloads or otherwise obtains the mobile banking system client application from the banking system  600  or from a distinct application server. In other embodiments of the invention, the user interacts with the banking system  600  via the web browser application  422  in addition to, or instead of, the mobile banking application  421 . The banking system  600  is typically configured to present a graphical user interface (e.g., through a mobile banking application or mobile banking website) that allows the user to use the mobile device  400  to control access to the user&#39;s online banking account. In this regard, the graphical user interface may include one or more buttons (e.g., “Shut Down All Account Access”) linked to one or more access restriction procedures that allow the user to request that an access restriction procedure be implemented. The mobile banking application or mobile banking website may prompt the user to provide further authentication information upon the user&#39;s initiation of a request to implement an access restriction procedure. 
     The memory  420  can also store any of a number of pieces of information, and data, used by the mobile device  400  and the applications and devices that make up the mobile device  400  or are in communication with the mobile device  400  to implement the functions of the mobile device  400  and/or the other systems described herein. For example, the memory  420  may include such data as user authentication information. 
     Referring now to  FIG. 5 , the computing device  500  also includes various features, such as a network communication interface  510 , a processing device  520 , a user interface  530 , and a memory device  550 . The network communication interface  510  includes a device that allows the personal computing device  500  to communicate over the network  250  (shown in  FIG. 2 ). In one embodiment of the invention, a network browsing application  555  provides for a user to establish network communication with the banking system  600  (shown in  FIG. 2 ) for the purpose accessing a user&#39;s online banking account. In another embodiment, an online banking application  556  allows the user of the computing device  500  to a user&#39;s online banking account. 
     As used herein, a “processing device,” such as the processing device  520 , generally refers to a device or combination of devices having circuitry used for implementing the communication and/or logic functions of a particular system. For example, a processing device  520  may include a digital signal processor device, a microprocessor device, and various analog-to-digital converters, digital-to-analog converters, and other support circuits and/or combinations of the foregoing. Control and signal processing functions of the system are allocated between these processing devices according to their respective capabilities. The processing device  520  may further include functionality to operate one or more software programs based on computer-executable program code thereof, which may be stored in a memory. As the phrase is used herein, a processing device  520  may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function. 
     As used herein, a “user interface”  530  generally includes a plurality of interface devices and/or software that allow a user to input commands and data to direct the processing device to execute instructions. For example, the user interface  530  presented in  FIG. 5  may include a graphical user interface (GUI) or an interface to input computer-executable instructions that direct the processing device  520  to carry out specific functions. In this regard, the graphical user interface may include one or more buttons linked to one or more access restriction procedures that allow the user to request that an access restriction procedure be implemented. The user interface  530  employs certain input and output devices to input data received from the user or output data to the user. These input and output devices may include a display, mouse, keyboard, button, touchpad, touch screen, microphone, speaker, LED, light, joystick, switch, buzzer, bell, and/or other user input/output device for communicating with one or more users. 
     As used herein, a “memory device”  550  generally refers to a device or combination of devices that store one or more forms of computer-readable media for storing data and/or computer-executable program code/instructions. Computer-readable media is defined in greater detail below. For example, in one embodiment, the memory device  550  includes any computer memory that provides an actual or virtual space to temporarily or permanently store data and/or commands provided to the processing device  520  when it carries out its functions described herein. 
       FIG. 6  provides a block diagram illustrating the banking system  600  in greater detail, in accordance with an embodiment of the invention. As illustrated in  FIG. 6 , in one embodiment of the invention, the banking system  600  includes a processing device  620  operatively coupled to a network communication interface  610  and a memory device  650 . In certain embodiments, the banking system  600  is operated by a financial institution, while in other embodiments, the banking system  600  is operated by an entity other than a financial institution. 
     It should be understood that the memory device  650  may include one or more databases or other data structures/repositories. The memory device  650  also includes computer-executable program code that instructs the processing device  620  to operate the network communication interface  610  to perform certain communication functions of the banking system  600  described herein. For example, in one embodiment of the banking system  600 , the memory device  650  includes, but is not limited to, a network server application  670 , an authentication application  660 , a user account data repository  680  which includes user authentication data  680  and user account information  684 , an online banking application  690  which includes a web server application  693 , a downloadable online banking client application  694 , an automated teller machine (ATM) application  695 , and other computer-executable instructions or other data. The computer-executable program code of the network server application  670 , the authentication application  660 , the online banking application  690 , or the automated teller machine (ATM) application  695  may instruct the processing device  620  to perform certain logic, data-processing, and data-storing functions of the banking system  600  described herein, as well as communication functions of the banking system  600 . In this regard, the processing device  620  is typically configured to implement one or more access restriction procedures as described herein (e.g., by restricting access to the user&#39;s account(s) via one or more account access channels). To accomplish this, the processing device  620  may deny transactions initiated by a restricted account access channel or require secondary authentication information before permitting transactions from a restricted account access channel. 
     In one embodiment, the user account data repository  680  includes user authentication data  682  and user account information  684 . The network server application  670 , the authentication application  660 , and the online banking application  690  are configured to implement user account information  684  and the user authentication data  682  (e.g., user identification information) when authenticating a user to the banking system  600 . In this regard, the user authentication data  682  may include a user&#39;s username, password, PIN number, and device identification information associated with a mobile device. The user account information  684  may include account identification information. The user account data repository  680  also typically includes information regarding each access restriction procedure associated with the user&#39;s account(s). 
     As used herein, a “communication interface” typically includes a modem, server, transceiver, and/or other device for communicating with other devices on a network, and/or a user interface for communicating with one or more users. Referring again to  FIG. 6 , the network communication interface  610  is a communication interface having one or more communication devices configured to communicate with one or more other devices on the network  250 , such as the ATM  300 , the mobile device  400 , and the computing device  500 . The processing device  620  is typically configured to use the network communication interface  610  to transmit and/or receive data and/or commands to and/or from the other devices connected to the network  250 . 
     As will be appreciated by one of skill in the art, the present invention may be embodied as a method (including, for example, a computer-implemented process, a business process, and/or any other process), apparatus (including, for example, a system, machine, device, computer program product, and/or the like), or a combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, and the like), or an embodiment combining software and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product on a computer-readable medium having computer-executable program code embodied in the medium. 
     Any suitable transitory or non-transitory computer readable medium may be utilized. The computer readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples of the computer readable medium include, but are not limited to, the following: an electrical connection having one or more wires; a tangible storage medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), or other optical or magnetic storage device. 
     In the context of this document, a computer readable medium may be any medium that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, radio frequency (RF) signals, or other mediums. 
     Computer-executable program code for carrying out operations of embodiments of the present invention may be written in an object oriented, scripted or unscripted programming language. However, the computer program code for carrying out operations of embodiments of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages. 
     Embodiments of the present invention are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and/or combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable program code portions. These computer-executable program code portions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a particular machine, such that the code portions, which execute via the processor of the computer or other programmable data processing apparatus, create mechanisms for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. 
     These computer-executable program code portions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the code portions stored in the computer readable memory produce an article of manufacture including instruction mechanisms which implement the function/act specified in the flowchart and/or block diagram block(s). 
     The computer-executable program code may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the code portions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block(s). Alternatively, computer program implemented steps or acts may be combined with operator or human implemented steps or acts in order to carry out an embodiment of the invention. 
     As the phrase is used herein, a processor may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing particular computer-executable program code embodied in computer-readable medium, and/or by having one or more application-specific circuits perform the function. 
     Embodiments of the present invention are described above with reference to flowcharts and/or block diagrams. It will be understood that steps of the processes described herein may be performed in orders different than those illustrated in the flowcharts. In other words, the processes represented by the blocks of a flowchart may, in some embodiments, be in performed in an order other that the order illustrated, may be combined or divided, or may be performed simultaneously. It will also be understood that the blocks of the block diagrams illustrated, in some embodiments, merely conceptual delineations between systems and one or more of the systems illustrated by a block in the block diagrams may be combined or share hardware and/or software with another one or more of the systems illustrated by a block in the block diagrams. Likewise, a device, system, apparatus, and/or the like may be made up of one or more devices, systems, apparatuses, and/or the like. For example, where a processor is illustrated or described herein, the processor may be made up of a plurality of microprocessors or other processing devices which may or may not be coupled to one another. Likewise, where a memory is illustrated or described herein, the memory may be made up of a plurality of memory devices which may or may not be coupled to one another. 
     To supplement the present disclosure, this application further incorporates entirely by reference the following commonly assigned patent applications: 
     
       
         
           
               
               
               
             
               
                   
               
               
                 U.S. patent application Ser. No. 
                 Title 
                 Filed On 
               
               
                   
               
             
            
               
                 14/175,639 (now published as U.S. 
                 DETERMINING USER 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 AUTHENTICATION REQUIREMENTS 
                   
               
               
                 2015/0227926) 
                 BASED ON THE CURRENT LOCATION 
                   
               
               
                   
                 OF THE USER IN COMPARISON TO A 
                   
               
               
                   
                 USERS&#39;S TRAVEL ROUTE 
                   
               
               
                 14/175,643 (now published as U.S. 
                 DETERMINING USER 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 AUTHENTICATION REQUIREMENTS 
                   
               
               
                 2015/0227727) 
                 BASED ON THE CURRENT LOCATION 
                   
               
               
                   
                 OF THE USER IN COMPARISON TO 
                   
               
               
                   
                 THE USERS&#39;S NORMAL BOUNDARY 
                   
               
               
                   
                 OF LOCATION 
                   
               
               
                 14/175,646 (now published as U.S. 
                 DETERMINING USER 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 AUTHENTICATION REQUIREMENTS 
                   
               
               
                 2015/0227728) 
                 BASED ON THE CURRENT LOCATION 
                   
               
               
                   
                 OF THE USER BEING WITHIN A 
                   
               
               
                   
                 PREDETERMINED AREA REQUIRING 
                   
               
               
                   
                 ALTERED AUTHENTICATION 
                   
               
               
                   
                 REQUIREMENTS 
                   
               
               
                 14/175,701 (now published as U.S. 
                 USER AUTHENTICATION BASED ON 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 HISTORICAL TRANSACTION DATA 
                   
               
               
                 2015/0229623) 
                   
                   
               
               
                 14/175,947 (now published as U.S. 
                 USER AUTHENTICATION BASED ON 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 HISTORICAL USER BEHAVIOR 
                   
               
               
                 2015/0229624) 
                   
                   
               
               
                 14/175,954 (now published as U.S. 
                 USER AUTHENTICATION BY GEO- 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 LOCATION AND PROXIMITY TO 
                   
               
               
                 2015/0229650) 
                 USER&#39;S CLOSE NETWORK 
                   
               
               
                 14/175,863 (now published as U.S. 
                 USER AUTHENTICATION BASED ON 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 OTHER APPLICATIONS 
                   
               
               
                 2015/0227731) 
                   
                   
               
               
                 14/175,615 (now published as U.S. 
                 USER AUTHENTICATION BASED ON 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 FOB/INDICIA SCAN 
                   
               
               
                 2015/0227726) 
                   
                   
               
               
                 14/175,688 (now published as U.S. 
                 USER AUTHENTICATION BASED ON 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 SELF-SELECTED PREFERENCES 
                   
               
               
                 2015/0227730) 
                   
                   
               
               
                 14/175,672 (now published as U.S. 
                 SELF-SELECTED USER ACCESS 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 BASED ON SPECIFIC 
                   
               
               
                 2015/0227729) 
                 AUTHENTICATION TYPES 
                   
               
               
                 14/175,146 (now published as U.S. 
                 PROVIDING AUTHENTICATION 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 USING PREVIOUSLY-VALIDATED 
                   
               
               
                 2015/0227725) 
                 AUTHENTICATION CREDENTIALS 
                   
               
               
                 14/175,652 (now published as U.S. 
                 DETERMINING AUTHENTICATION 
                 Feb. 7, 2014 
               
               
                 patent application Publication No.  
                 REQUIREMENTS ALONG A 
                   
               
               
                 2015/0227924) 
                 CONTINUUM BASED ON A CURRENT 
                   
               
               
                   
                 STATE OF THE USER AND/OR THE 
                   
               
               
                   
                 SERVICE REQUIRING 
                   
               
               
                   
                 AUTHENTICATION 
                   
               
               
                 14/175,956 (now published as U.S. 
                 SORTING MOBILE BANKING 
                 Feb. 7, 2014 
               
               
                 patent application Publication No.  
                 FUNCTIONS INTO AUTHENTICATION 
                   
               
               
                 2015/0227724) 
                 BUCKETS 
                   
               
               
                 14/175,962 (now published as U.S. 
                 AUTHENTICATION LEVEL OF 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 FUNCTION BUCKET BASED ON 
                   
               
               
                 2015/0229625) 
                 CIRCUMSTANCES 
                   
               
               
                 14/175,771 (now published as U.S. 
                 REMOTE REVOCATION OF 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 APPLICATION ACCESS BASED ON 
                   
               
               
                 2015/0227903) 
                 LOST OR MISAPPROPRIATED CARD 
                   
               
               
                 14/175,786 (now published as U.S. 
                 REVOCATION OF APPLICATION 
                 Feb. 7, 2014 
               
               
                 patent application Publication No. 
                 ACCESS BASED ON NON-CO- 
                   
               
               
                 2015/0227927) 
                 LOCATED 
               
               
                   
               
            
           
         
       
     
     While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of, and not restrictive on, the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations and modifications of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.