Abstract:
A method and system for payments for mobile phone payments with a disabling feature is disclosed. The method includes activating a mobile phone containing contactless payment systems, and having a timeout feature disable the contactless payment systems after a set period of time.

Description:
CROSS-REFERENCES TO RELATED APPLICATIONS 
       [0001]    This patent application is a non-provisional of and claims priority to U.S. provisional patent application No. 60/884,212, filed on Jan. 9, 2007 and U.S. provisional patent application No. 60/884,290, filed on Jan. 10, 2007, both of which are herein incorporated by reference in their entirety for all purposes. 
         [0002]    This application is also related to U.S. patent application Ser. No. ______, entitled “Contactless Transaction” (Attorney Docket No. 16222U-038310US), filed on the same day as the present application, and is also related to U.S. patent application Ser. No. ______, entitled “Mobile Payment Management” (Attorney Docket No. 16222U-038320US), filed on the same day as the present application, and is also related to U.S. patent application Ser. No. ______, entitled “Mobile Phone Payment Process including Threshold Indicator” (Attorney Docket No. 16222U-038340US), filed on the same day as the present application. These applications are herein incorporated by reference in their entirety for all purposes. 
     
    
     BACKGROUND 
       [0003]    With advancements in technology, contactless payment systems such as contactless cards have begun to proliferate as a means for conducting transactions. Contactless payment cards can communicate with contactless readers in point of sale (POS) devices or contactless readers, when they are close together. 
         [0004]    Usage of a contactless card requires a consumer to carry the contactless card, of course. This results in additional items carried by already overloaded consumers. Another problem with a contactless payment card is that, since it only needs to be proximate to a contactless reader to read data from it, it is possible that an unauthorized person might use an unauthorized reader to “sniff” data from the contactless card when the contactless card is not being used in a transaction. 
         [0005]    Embodiments of the invention address these and other problems, individually and collectively. 
       BRIEF SUMMARY 
       [0006]    Embodiments of the invention are directed to improved mobile phone payment systems and methods with a disabling feature. 
         [0007]    One embodiment of the invention is directed to a method. The method comprises entering a predetermined timeout time into a mobile phone, where the mobile phone comprises a contactless element that is configured to be read by a contactless reader in an access device. The method also includes executing a mobile payment application associated with the mobile phone, and disabling the mobile payment application after the predetermined timeout time has elapsed. 
         [0008]    Another embodiment of the invention is directed to a computer readable medium comprising code for allowing a contactless element in a mobile phone to communicate with a contactless reader in an access device, code for entering a predetermined timeout time, code for executing a mobile payment application associated with the mobile phone, and code for disabling the mobile payment application after the predetermined timeout time has elapsed. 
         [0009]    Another embodiment of the invention is directed to a method comprising transmitting data related to a mobile payment application to a mobile phone comprising a contactless element, wherein the data comprises a timer for a predetermined timeout time such that the mobile payment application is disabled after the predetermined timeout time has elapsed. 
         [0010]    These and other embodiments of the invention are described in further detail below. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0011]      FIG. 1  shows a block diagram of a system according to an embodiment of the invention. 
           [0012]      FIG. 2  shows a block diagram of a mobile phone according to an embodiment of the invention. 
           [0013]      FIG. 3  shows a block diagram of an access device according to an embodiment of the invention. 
           [0014]      FIG. 4  shows a flowchart illustrating the various display screens of a mobile phone during a method according to an embodiment of the invention. 
           [0015]      FIG. 5  shows a flowchart illustrating a method according to an embodiment of the invention. 
           [0016]      FIG. 6  shows a flowchart illustrating of a method according to an embodiment of the invention. 
           [0017]      FIG. 7  shows a flowchart illustrating the various display screens of a mobile phone during a method according to an embodiment of the invention. 
       
    
    
     DETAILED DESCRIPTION 
       [0018]    I. Mobile Transaction Systems 
         [0019]    The environment is ripe for the development of payment and payment-related services in the mobile phone ecosystem. Consumer demand for all-purpose multi-functional mobile phones is increasing. Technology that supports a mobile payments infrastructure is emerging (i.e., contactless payment acceptance infrastructure, Near field communication (NFC)-enabled mobile phones, and robust mobile networks). There is increasing collaboration between wireless and financial services. The mobile phone has the potential to enhance the security and convenience of using a payment product as well as introduce payment products to parts of the world that don&#39;t currently have a support infrastructure for traditional payment products. 
         [0020]    Embodiments of the invention are directed towards the use of a mobile telephone, or mobile phone, as a contactless payment device. The mobile phone can contain a mobile payment application that is a software application that stores payment details, such as a credit card number and related information. When consumers wish to make a purchase from a merchant, they can place their mobile phones in proximity to an access device associated with the merchant. The mobile payment application may then send the payment details to the access device over a wireless connection. From there the transaction may progress similarly to the progression of a purchase with a traditional credit card. 
         [0021]    To make a payment using a mobile phone, the mobile payment application stored on the phone is executed so that the payment can be made with the mobile phone. In certain embodiments of the invention, there can be two modes of operation of the mobile phone relating to execution. 
         [0022]    In a first mode of operation according to an embodiment of the invention, the consumer, or user, sets the mobile phone application as “always on.” In this mode of operation, the mobile payment application on the phone is always in an execution mode when the mobile phone is powered on. To make a payment, the consumer can place the mobile phone close to an access device such as a POS terminal with a contactless reader, and payment information (e.g., account information) will be transmitted from the mobile phone to the contactless reader (and therefore the POS terminal). Whenever the mobile phone is powered on, the mobile payment application can automatically execute. To deactivate the mobile payment application, the consumer can manually deactivate it by changing settings on the mobile phone. In this first mode, the mobile payment application is always active, and as such, payment information can be transmitted anytime the phone is located near an access device. 
         [0023]    The second mode of operation, according to embodiments of the invention, can help prevent the accidental transmittal of information as can occur in the first mode. In the second mode of operation, the user can manually select the mobile phone application each time before making a purchase. In this method, the mobile phone normally resides in the “idle” state, such that it does not transmit any payment information to an access device, even when placed in proximity to one. To conduct a transaction, the consumer can execute the mobile payment application on the mobile phone by selecting it, typically by using a shortcut key on the phone or by navigating to a menu system on the display of the mobile phone and by selecting an appropriate menu item. Once the mobile payment application is active, the mobile phone will transmit payment information when placed in proximity with an access device. 
         [0024]    In this method of execution of the mobile phone application, the application remains active until a transaction has occurred. Once a transaction has occurred, the mobile phone can go back to the idle state. However, there may be occasions when the consumer activates the mobile payment application, but then does not intend to continue with a payment transaction. On such occasions, the mobile payment application would still remain active, and could unintentionally transmit payment information to an unauthorized contactless reader. To prevent this, the consumer can manually disable the mobile phone application, thereby returning the mobile phone to the idle state. Still, there are times when the user may forget to do so, leaving the mobile payment application active. 
         [0025]    In preferred embodiments of the invention, the mobile phone comprises a predetermined timeout time. Using this feature, the mobile phone can automatically disable the mobile payment application after a set amount of time (the predetermined timeout time) has elapsed. In certain implementations, a countdown timer on the mobile phone will start to count down from the predetermined timeout time once the mobile payment application has been executed. If a payment transaction with the phone takes place, the phone will reset back to the idle state after the payment transaction is completed, and the timer will likewise reset and stop counting. If no payment transaction occurs within the predetermined timeout time, then after the predetermined timeout time, the mobile payment application on the phone will automatically disable so that contactless payments cannot be made. The mobile phone can return to the idle state. When this happens, the timer will stop counting and be reset back to the predetermined timeout time, to be used when the mobile payment application is next activated. 
         [0026]    If the predetermined timeout time elapses and therefore the mobile payment application deactivates, then no payment information will be sent even in the event the mobile phone is placed near an access device. The phone can remain in the idle state until the user again activates the mobile payment application. If the user activates a mobile payment application to make a payment transaction, but then the user waits longer than the predetermined timeout time to conduct the transaction, then the mobile phone will not be able to conduct the payment transaction when it is placed next to an access device. In this case, the consumer can activate the payment application again, and can then present the phone to the access device again (within the predetermined time), in order to conduct and complete the transaction. In embodiments of the invention, the duration of the predetermined timeout time may be set by the user, or may be set by another entity such as the mobile phone carrier or the financial institution associated with the payment information stored on the mobile payment application. 
         [0027]    In certain embodiments, the mobile phone may contain more than one mobile payment application or mobile payment application instance. In these embodiments, the mobile phone can contain a plurality of mobile payment applications or instances. Each of the plurality of mobile payment applications or instances can be associated with different payment details. In some implementations, each mobile payment application or instance on a mobile phone is associated with a specific issuer, and each may contain different payment information, and may be associated with different issuer specific payment services. For example, a single mobile phone may contain three instances of a mobile payment application. The first instance may contain credit card information relating to a Bank A credit card. The second instance may contain information relating to a Bank B credit card. The third instance may contain information relating to a debit card associated with a checking account with a Bank C. The consumer can select the payment service of Bank A, Bank B, or Bank C to make a payment using the corresponding account. 
         [0028]    In certain embodiments, a consumer can set one of the issuer-specific payment services as a default. The default payment service will then be used for payment transactions conducted using the phone, barring further action by the consumer. In the above example, using the mobile phone, the consumer may choose the first issuer specific payment service as the default mobile payment application. When the consumer uses the mobile phone in a payment transaction, the default mobile payment application associated with the selected payment service will be used. The consumer may change the default payment service at a later date. Also, in some embodiments, the consumer can select an issuer specific payment service to be a default service for a predetermined number (e.g., one) of transactions. 
         [0029]    Also, in some embodiments, each payment service can be associated with its own predetermined timeout time. Also, the duration of timeout times can vary according to issuer or consumer preference. 
         [0030]    Specific embodiments of the invention can be described with reference to  FIGS. 1-7 . 
         [0031]      FIG. 1  shows a system according to an embodiment of the invention. Other systems according to embodiments of the invention may include fewer or more components than are specifically shown in  FIG. 1 . 
         [0032]      FIG. 1  shows a consumer  30 , a mobile phone  32 , an access device  18 , a merchant  22 , a payment processing network  40 , and an issuer  42 , in operative communication with each other. The merchant  22  and issuer  42  can communicate through the payment processing network  40 . As used herein, an “issuer” is typically a business entity (e.g., a bank) which maintains financial accounts for the consumer and often issues a portable consumer device such as a credit or debit card to the consumer. In embodiments of the invention, the issuer  42  has issued a mobile payment application to the consumer  30 . The mobile payment application will be used with the mobile phone  32 . When the consumer  30  wishes to conduct a payment transaction with the merchant  22 , she will (if needed) activate the mobile payment application on the mobile phone (as more fully explained below), and position the mobile phone  32  near the access device  18  so that the two devices communicate wirelessly. The access device  18  can read the payment data from the mobile phone  32 , and provide that data to the merchant  22 . The merchant  22  can contact the issuer  42  associated with the payment account through the payment processing network  40 , to receive either an authorization or a denial for the transaction. 
         [0033]    The payment processing network  40  may have a server computer  44 , as well as a database  48 . The server computer  44  is typically a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a web server. 
         [0034]    The payment processing network  40  may comprise or use a payment processing network such as VisaNet™. The payment processing network  40  and any communication network that communicates with the payment processing network  40  may use any other suitable wired or wireless network, including the Internet. The payment processing network  40  may be adapted to process ordinary debit or credit card transactions. 
         [0035]    The server computer  44  may comprise or be associated with a computer readable medium comprising code for receiving information regarding a payment account, and then determining the issuer associated with that payment account. The computer readable medium may also comprise code for using the payment account information to route any authorization request message to the appropriate issuer  42 . 
         [0036]    For simplicity of illustration, one mobile phone  32 , one access device  18 , one merchant  22 , and one issuer  42  are shown. However, it is understood that in embodiments of the invention, there can be multiple mobile phones, access devices, merchants, issuers, as well as server computers, databases, accounts, etc. 
         [0037]    An exemplary mobile phone  32  may comprise a computer readable medium and a body as shown in  FIG. 2 . ( FIG. 2  shows a number of components, and the mobile phones according to embodiments of the invention may comprise any suitable combination or subset of such components.) The computer readable medium  32 ( b ) may be present within the body  32 ( h ), or may be detachable from it. The body  32 ( h ) may be in the form a plastic substrate, housing, or other structure. The computer readable medium  32 ( b ) may be a memory that stores data and may be in any suitable form including a magnetic stripe, a memory chip, etc. The memory preferably stores information such as payment account information, which may comprise financial information, transit information (e.g., as in a subway or train pass), access information (e.g., as in access badges), etc. Financial information may include information such as bank account information, bank identification number (BIN), credit or debit card number information, account balance information, expiration date, consumer information such as name, date of birth, etc. Any of this information may be transmitted by the mobile phone  32 . 
         [0038]    In some embodiments information in the memory may also be in the form of data tracks that are traditionally associated with credits cards. Such tracks include Track 1 and Track 2. Track 1 (“International Air Transport Association”) stores more information than Track 2, and contains the cardholder&#39;s name as well as account number and other discretionary data. This track is sometimes used by the airlines when securing reservations with a credit card. Track 2 (“American Banking Association”) is currently most commonly used. This is the track that is read by ATMs and credit card checkers. The ABA (American Banking Association) designed the specifications of this track and all world banks must abide by it. It contains the cardholder&#39;s account, encrypted PIN, plus other discretionary data. 
         [0039]    The mobile phone  32  may further include a contactless element  32 ( g ), which is typically implemented in the form of a semiconductor chip (or other data storage element) with an associated wireless transfer (e.g., data transmission) element, such as an antenna. Contactless element  32 ( g ) is associated with (e.g., embedded within) mobile phone  32  and data or control instructions may be applied to contactless element  32 ( g ) by the processor  32 ( c ). 
         [0040]    Contactless element  32 ( g ) is capable of transferring and receiving data using a near field communications (“NFC”) capability (or near field communications medium) typically in accordance with a standardized protocol or data transfer mechanism (e.g., ISO 14443/NFC). Near field communications capability is a short-range communications capability, such as RFID, Bluetooth™, infra-red, or other data transfer capability that can be used to exchange data between the mobile phone  32  and an interrogation device such as an access device. The access device should have a contactless reader that can read the contactless element  32 ( g ). Thus, the mobile phone  32  is capable of communicating and transferring data and/or control instructions via both cellular network and near field communications capability. 
         [0041]    The mobile phone  32  may also include a processor  32 ( c ) (e.g., a microprocessor) for processing the functions of the mobile phone  32  and a display  32 ( d ) to allow a consumer to see phone numbers and other information and messages. The mobile phone  32  may further include input elements  32 ( e ) to allow a consumer to input information into the phone, a speaker  32 ( f ) to allow the consumer to hear voice communication, music, etc., and a microphone  32 ( i ) to allow the consumer to transmit her voice through the mobile phone  32 . The mobile phone  32  may also include an antenna  32 ( a ) for wireless data transfer (e.g., data transmission over a wireless network). 
         [0042]    The mobile phone  32  may contain a plurality of copies, or instances, of the mobile payment application. Code for the plurality of mobile payment applications may reside on computer readable medium  32 ( b ) of the mobile phone  32 . Computer readable medium  32 ( b ) may also comprise code relating to a timer that automatically deactivates any mobile payment applications after a predetermined timeout time has elapsed, code for displaying the timer in the mobile phone display, code for executing the mobile payment applications on the mobile phone, and code for allowing contactless element to communicate with the contactless reader in an access device. In certain embodiments, the mobile payment application is a J2ME/MIDP 2.0 application (MIDlet). Mobile Information Device Profile (MIDP) is the specification published for the use of Java on embedded devices such as mobile phones. Each mobile payment application instance can be customized and configured for a specific issuer. The data for the mobile payment application can be transmitted by being provisioned over-the-air (OTA), installed, activated, and configured according to the issuer&#39;s specifications on the mobile phone during service activation. Once configured an application instance may appear as an entry in the phone&#39;s main menu folder for mobile payments and other financial applications. In some embodiments, there can be more than one application instance on the menu based on the number of instances of the mobile payment application that have been activated and configured on the mobile phone. 
         [0043]      FIG. 3  shows a block diagram showing basic components that may reside in a contactless reader or POS terminal such as access device  18 . An exemplary access device  18  may comprise a processor  18 ( a )- 1 , a computer readable medium  18 ( a )- 2 , a keypad  18 ( a )- 3 , a mobile phone reader  18 ( a )- 4 , an output device  18 ( a )- 5 , and a network interface  18 ( a )- 6 , which can all be operatively coupled to the processor  18 ( a )- 1 . Exemplary mobile phone readers can include RF (radio frequency) antennas that interact with the mobile phone  32  through near field communications. Suitable output devices may include displays and audio output devices. Exemplary computer readable media may include one or more memory chips, disk drives, etc. The network interface  18 ( a )- 6  may allow the access device  18  to send and receive messages from the merchant  22 , payment processing network  40 , and/or the issuer  42 . 
         [0044]    In order to conduct purchase transactions using the components in  FIGS. 1-3 , the mobile phone  32  and mobile payment application is first configured. Then, the mobile phone  32  can be used to conduct payment transactions. These procedures are explained in detail below. 
         [0045]    II. Configuring the Mobile Phone 
         [0046]    Once the mobile payment application has been provisioned and installed on a mobile phone, it is configured to allow payment transactions to be conducted using the phone. As described above, more than one mobile payment application or instance may be installed on the mobile phone. For such cases, each application or instance may be individually configured if desired or configured in the same way. 
         [0047]      FIG. 5  shows the steps taken to configure a mobile payment application on a mobile phone according to an embodiment of the invention, along with screen shots of what the display of the mobile phone may show during certain steps. In  FIG. 5 , steps located below Mobile Handset  412  are the steps that may be performed by the mobile payment application, and the steps located under Consumer  410  are the steps that may be performed by the user of the handset. 
         [0048]    A payment service can first be activated on the phone. Once the mobile phone has received a message saying the selected payment application has successfully been installed and there is service activation (step  414  and screen shot  418 ), the application can be launched as in step  416 . Once launched, the mobile payment application checks its own configuration to determine if any user modifications are possible. If no configuration modifications are allowed, then the process jumps to step  448 , the configuration is complete, the display screen  450  is shown, and the mobile payment application is ready for use as in step  446 . 
         [0049]    If configuration options are allowed, the mobile payment application can allow the consumer to accept the default configuration option or modify some or all of the configuration options. In step  422 , the application checks if a password is mandatory. If so, the user is prompted to enter a password in step  420 . The requirements for the password may vary. In one implementation, the password may be required to consist of between 4 and 8 letters or numbers. Screen shot  424  shows what the display screen of the mobile phone will look like during step  420 . 
         [0050]    Next, the application checks to see if there are any other issuer specific software platforms installed on the mobile phone in step  426 . If there are other platforms installed, the consumer is prompted to choose whether the currently configurable platform is the default application in step  424  and as shown in screen shot  428 . If the currently configured platform is not chosen as the default (i.e., another instance is the default), then the configuration process is completed as in step  448 . 
         [0051]    If there are no other platforms installed, or if the currently configured platform is set as the default platform, the mobile payment application then checks to see if the mode of operation can be configured to be always on in step  432 . If it can be so configured, the application prompts the user to set the application as either always on or in manual activation mode in step  430  and as shown in screen shot  434 . The “always on” feature may alternatively be predetermined and not configurable by the user, as shown in step  436 . In either case, if the platform is set to be always on, the phone can be configured to display an indicator alerting the user as such in step  435 . 
         [0052]    If the consumer has the option to configure the mode of operation of the platform, the user can choose to not set the application associated with the platform as always on, but can choose to require manual activation prior to each purchase. If that configuration is chosen, the mobile payment application can check to see if a predetermined timeout time is configurable  442 . If so, the application may prompt the user to enter the duration of the predetermined timeout time into the mobile phone in step  440  and as shown in screen shot  438 . As can be seen from screen shot  438 , in that implementation, the default predetermined timeout time can be 90 seconds. In other implementations the predetermined timeout time can be for other durations, such as 30 seconds, 60 seconds, 100 seconds, etc. If the duration is configurable by the user, the user may be allowed choose any number of seconds, from 00-99, as shown in screen shot  438 . 
         [0053]    Alternatively, the predetermined timeout time may not be configurable by the user, as shown in step  442 . In that implementation, the predetermined timeout time is entered into the mobile phone when the mobile payment application is provisioned and installed. The duration of the predetermined timeout time may be chosen by the issuer associated with the mobile payment application, the mobile carrier, an organization associated with the payment processing network, or some other institution. Furthermore, after the mobile payment application has been fully configured, the duration of the predetermined timeout time may be changed by the appropriate party such as the issuer or organization associated with the payment processing network. A signal can be received by the mobile phone OTA (such as through the wireless network) that reconfigures the mobile payment application and adjusts the duration of the predetermined timeout time. 
         [0054]    If the predetermined timeout time is not configurable, the phone can be configured to remove an indicator alerting the user that the mobile payment application is currently active from its display in step  444 . Such indicator only needs to be displayed while the mobile payment application is active. Upon completion of the configuration process (step  448 ), the phone becomes ready to use in step  446  and displays screen shot  450 . At that point, a completion message is sent by the phone in step  452 , and it may be sent through the wireless network  408  to be received by the payment processing network and the issuer, to alert the institutions of the activation of a new mobile payment application. 
         [0055]    III. Using the Mobile Phone 
         [0056]    Once the mobile payment application has been configured, it may be used in payment transactions.  FIG. 4  shows a progression of screen shots of the display of a mobile phone that is being used in a payment transaction. In this embodiment, the mobile payment application associated with the mobile phone is set to a manual activation mode of operation (i.e., the user will need to select the application prior to using the mobile phone in a transaction). In screen shot  51 , the user (i.e., the consumer) is shown executing the mobile payment application. In screen shot  52 , the pay functionality of the mobile payment application is selected. Once selected, the application shows that it is ready to engage in a payment transaction in screen shot  53 . The consumer brings the mobile phone in proximity to the access device (or “waves” the mobile phone at the access device) in step  54  to effect the payment transaction. Once the payment transaction is completed, the mobile phone display shows a confirmation in screen shot  55 . 
         [0057]      FIG. 6  shows a flowchart illustrating the various steps of conducting a transaction according to an embodiment of the transaction. At step  500 , the mobile phone (i.e., the mobile handset  32 ) is in the idle state. In order to execute the mobile payment application in order to conduct a payment transaction, the user (i.e., the consumer  30 ) has two options in certain embodiments. In first option, the user can select a shortcut key as in step  502 , such as a programmable “soft key” located on the phone, which directly executes the mobile payment application. In the second option, the user goes through the menu system of the phone to select the application, as in step  504 . In certain embodiments, step  504  can further comprise entering a password into the mobile phone application, in order to authenticate the consumer  30  and prevent fraud. This results in the mobile payment application being executed and the mobile phone becoming ready to effect a transaction, as shown in steps  506  and  508 . The mobile phone can then in step  510  display a message indicating that is ready to conduct a payment transaction. 
         [0058]    At step  512 , the mobile phone is ready to conduct the transaction. Step  512  is when a timer associated with the mobile phone begins counting down from the predetermined timeout time. Should no payment transaction occur before the predetermined timeout time elapses, the mobile payment application is disabled in step  528 , and the mobile phone returns to the main application page on the mobile phone display in step  530 . At this point, if the consumer  30  still wishes to conduct a payment transaction, she reselects the mobile payment application either in step  502  or step  504 . However, in certain embodiments, after the mobile payment application has been deactivated due to a predetermined timeout time elapsing, a password will not need to be entered into the mobile payment application, even if originally required. This is because the consumer has already been authenticated by entering the password the first time, and necessitating further password inputs may discourage the consumer from making purchases. 
         [0059]    If the phone is presented to an access device (e.g., a POS terminal) within the predetermined timeout time, a payment transaction will be conducted. The access device, which is a POS terminal  462  in this embodiment, is ready in step  516 , and the phone is presented to the contactless reader element  18 ( a )- 4  associated with POS terminal  18  in step  514 . This allows the mobile phone  32  and the POS terminal  18  to communicate through near field communications, such that the payment application can transmit payment information to the merchant  22  through the POS terminal  18 . The POS terminal will process the transaction in step  522 , and the merchant  22  can complete the sale in step  524 . The merchant  22  may provide a receipt to the consumer in step  526 . Also, once the phone  412  is presented to the POS terminal in step  520 , the mobile phone  32  can detect that a payment transaction has occurred, and can display the payment completion page to the user in step  518 . Once the payment completion page is displayed, the mobile payment application is deactivated in step  528 , and the mobile phone returns to the main application page on the mobile phone display in step  530 . 
         [0060]      FIG. 7  shows a progression of screen shots of the display of a mobile phone  32  that is being used in the steps of  FIG. 6 . In screen shot  550 , the mobile payment application has been executed and the pay functionality of the mobile payment application is selected. Once selected, the application shows that it is ready to engage in a payment transaction in screen shot  552 . The consumer brings the mobile phone in proximity to the access device (or “waves” the mobile phone at the access device) in step  554  to effect the payment transaction. Once the payment transaction is effected, the access device will beep to show a successful payment transaction in step  556 , and the mobile phone display shows a confirmation in screen shot  55 . 
         [0061]    Embodiments of the invention have a number of advantages. Mobile phones are ubiquitous, so adding payment functionality to them greatly expands the market for contactless payment devices. At the same time, the use of a timeout feature allows the phone to have full contactless card functionality, while removing limitations. Many potential users are hesitant to adopt contactless payment systems as they may unintentionally effect payment transactions merely by passing nearby access devices. With a timeout feature, this concern is minimized. Furthermore, the use of multiple instances of a mobile payment application on a mobile phone allows for the use of a variety of cards on a single phone. Combined with the timeout feature, the plurality of mobile payment applications allows a user to replace many payment cards with a single mobile phone without concern over accidental or surreptitious transmittal of any of the payment information. 
         [0062]    It should be understood that the present invention as described above can be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software. 
         [0063]    Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network. 
         [0064]    The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents. 
         [0065]    One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention. 
         [0066]    A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary.