Patent Publication Number: US-2018039973-A1

Title: Radio frequency transactions using a plurality of accounts

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of U.S. application Ser. No. 11/164,352, filed on Nov. 18, 2005, which is a continuation-in-part and claims priority to U.S. patent application Ser. No. 10/711,720, now U.S. Pat. No. 7,996,324, titled “SYSTEMS AND METHODS FOR MANAGING MULTIPLE ACCOUNTS ON A RF TRANSACTION DEVICE USING SECONDARY IDENTIFICATION INDICIA,” filed Sep. 30, 2004. The &#39;720 application itself claims priority to U.S. Provisional Application No. 60/507,803, filed Sep. 30, 2003. This application is also a continuation-in-part of and claims priority to U.S. patent application Ser. No. 10/340,352, now U.S. Pat. No. 7,889,052, entitled “SYSTEM AND METHOD FOR INCENTING PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed Jan. 10, 2003 (which itself claims priority to U.S. Provisional Patent Application No. 60/396,577, filed Jul. 16, 2002), and is also a continuation-in-part and claims priority to U.S. patent application Ser. No. 10/192,488, now U.S. Pat. No. 7,239,226, entitled “SYSTEM AND METHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed on Jul. 9, 2002 (which itself claims priority to U.S. Provisional Patent Application No. 60/304,216, filed Jul. 10, 2001. All of the above-listed applications are incorporated herein by reference. 
    
    
     FIELD OF INVENTION 
     The present invention generally relates to payment systems, and more particularly, to systems and methods for facilitating the payments using non-traditional payment devices. 
     BACKGROUND OF INVENTION 
     In general, financial transaction devices that are capable of managing multiple accounts, are typically designed to access only those accounts managed by the same issuer. For example, the same issuer provides both the credit card and the wholesale purchase club account to the user. As such, the issuer providing both accounts generally establishes its own application tenant storage format and management protocol related to the accounts. The established format and protocol is ordinarily different from any format or protocol used by other unrelated issuers, which provides the issuer increased control over access to the account data. Because of the differing unique protocols/formats amongst issuers, multiple issuers typically provide a transaction device corresponding to an account offered by the issuer, where the data for accessing the account is stored in that issuer&#39;s protocol/format. Thus, a user wishing to access multiple accounts managed by different issuers, must ordinarily carry at least one transaction device per issuer. Carrying multiple transaction devices can be inconvenient in that the instruments may be more easily misplaced, lost or stolen, preventing the user from accessing the account. 
     Another disadvantage of conventional methods of managing multiple accounts, which is related to the different issuer formats/protocols, is that, since conventional financial transaction devices typically only store application tenant information related to one issuer, the information may not be recognized by a second issuer distinct from the first. That is, the user of the financial transaction device typically is only able to use the financial transaction device at locations identified by the issuer of the transaction card. The financial transaction device may not be used at any other locations, since the locations not identified by the user will not recognize the application tenant information which is typically stored on the instrument in an issuer determined format. As such, in order to access multiple accounts managed by different issuers using different formats/protocols, the user must typically carry multiple cards, as noted above. 
     Further still, with the expansion and permeation of technology, more and more users typically carry multiple transaction devices and technological devices. For example, a user may carry 4-5 transaction devices, a cell phone, a PDA, a handheld device, and a laptop. When a user, for example, goes to the coffee shop, it is desirable for the user to use one device for both his purchase and his technological needs. Thus, a need exists for a technological device that can perform both transactions. 
     SUMMARY OF INVENTION 
     The present invention includes systems and methods for facilitating transactions using non-traditional devices. A method of the present invention includes the steps of forming a transaction request at a non-traditional device, and communicating the transaction request to a reader. In one embodiment, the non-traditional device may be configured with a transponder or other RF operable device. In another embodiment, the non-traditional device may be configured with an RFID protocol, such as a protocol in ISO8583 format. In yet another embodiment, the non-traditional device may be configured to facilitate transactions using a random number, an authentication tag, a counter, or an encrypted payload. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       A more complete understanding of the present invention may be derived by referring to the detailed description and claims when considered in connection with the Figures, wherein like reference numbers refer to similar elements throughout the Figures, and: 
         FIG. 1  illustrates a general overview of an exemplary data set management method in accordance with an exemplary embodiment of the present invention; 
         FIG. 2  illustrates a block diagram overview of an exemplary data set management system in accordance with an exemplary embodiment of the present invention; 
         FIG. 3  illustrates a more detailed exemplary data set management method in accordance with an exemplary embodiment of the present invention; 
         FIG. 4  illustrates an exemplary data set management method for adding data sets in accordance with an exemplary embodiment of the present invention; 
         FIG. 5  illustrates an exemplary data set management method for deleting data sets in accordance with an exemplary embodiment of the present invention; 
         FIG. 6  illustrates an exemplary method for user-self-management of data sets in accordance with an exemplary embodiment of the present invention; 
         FIG. 7  illustrates an exemplary method for issuer management of data sets in accordance with the present invention; 
         FIG. 8  illustrates an exemplary data set selection method for use in completing a transaction; 
         FIG. 9  illustrates a block diagram of an exemplary transaction device for use with the present invention; 
         FIG. 10  illustrates a block diagram of an exemplary Radio Frequency Identification (RFID) reader for use with the present invention; 
         FIG. 11  depicts an exemplary screen shot providing a system user with a listing of transaction account numbers stored on an transaction device that is available for completing a transaction, in accordance with the present invention; 
         FIG. 12  depicts an exemplary screen shot providing a system user the opportunity to allocate a portion of the transaction to be satisfied to a user selected transaction account number, in accordance with the present invention; 
         FIG. 13  depicts an exemplary screen shot providing a system user the opportunity to identify a portion of a transaction request to be satisfied by a user selected transaction account number, in accordance with the present invention; 
         FIG. 14  depicts a subsequent listing of transaction accounts stored on the transaction device, which are available for transaction completion, in accordance with the present invention; 
         FIG. 15  depicts an exemplary method for selecting one of a multiple transaction accounts for transaction completion, in accordance with the present invention; 
         FIG. 16  illustrates an exemplary non-traditional payment processing device in accordance with the present invention; 
         FIG. 17  illustrates an exemplary method for using non-traditional devices to facilitate RF transactions; and 
         FIG. 18  depicts an exemplary method for using an additional authentication factor with a non-traditional device; 
         FIG. 19  depicts an exemplary funding protocol which may be identified by the fob user. 
     
    
    
     DETAILED DESCRIPTION 
     While the exemplary embodiments herein are described in sufficient detail to enable those skilled in the art to practice the invention, it should be understood that other embodiments may be realized and that logical and mechanical changes may be made without departing from the spirit and scope of the invention. Thus, the following detailed description is presented for purposes of illustration only and not of limitation. 
     The present invention improves upon prior art contactless cards and includes novel systems and methods for securing the use of contactless cards in the payment process from end-to-end, (meaning from the time it is used to the time it is accepted by the acquirer), or any portion thereof. Embodiments of the invention generally include security solutions for contactless transaction systems, the use of PINs, substantially securely accessing multiple card products in one device, and/or emulating a magnetic stripe card and cellular phones without substantially compromising security. The invention also includes new security methods which minimize the risks associated with this air interface. In one embodiment, consumer payment information is transmitted using RF technology, so the information can often be accessed without having physical procession of the payment device (e.g., card or fob). 
     More particularly, exemplary embodiments reduce or eliminate account fraud for RF devices by substantially securing the data contained on the device. The invention incorporates transaction card account payment security from a RF device with a POS device instead of (or in addition to) using an identifier that identifies where to find the correct transaction card account number from the merchant system, outside the POS and using a separate network (not one of the standard financial networks). While the invention and RF devices may include new POS terminals to read the RF signal and transmit it to facilitate authorization and submission, the increased consumer convenience and security should translate into greater use of the fob. Moreover, the POS terminals for the RF devices often include a failure rate less than magnetic-stripe devices, as there is little or no mechanical interaction between the card and the reader (no swiping), thereby resulting in less ongoing cost and maintenance of the POS devices. As used herein, the terms secure, valid, authorized, authenticated, etc. (including similar terms and various forms of the terms) may include full, partial or substantial security, validation, authorization, authentication, etc. 
     An exemplary aspect of the present invention includes the RF device storing substantially “in-the-clear” account data (such as the account number and its expiration date), an encryption key and a counter. The RF devices are typically manufactured with the account number, encryption key and the beginning counter set in them. The RF device at a minimum contains a simple processor chip capable of incrementing a counter and producing an authentication tag. RF devices with greater capabilities (like contactless smart cards) can be used, but are simply an extension of the present invention discussed herein. 
     In an exemplary embodiment, and which is substantially secure for this particular scheme, both the RF device and reader include an authentication tag with the transaction request. When the RF device comes into range of a merchant&#39;s RF reader, the reader sends a random number or ‘nonce’ to the RF device. The RF device uses the random number (from the RF reader), its counter, and its account number to produce an authentication tag (Message Authentication Code) using its encryption key. The account data, counter, random number and authentication tag is then returned to the RF reader by the RF device as a transaction request. Once the request has been sent to the RF reader, the RF device increments its counter by the designated value. For a basic introduction to cryptography, please review a text written by Bruce Schneider which is entitled “Applied Cryptography: Protocols, Algorithms, and Source Code In C,” published by John Wiley &amp; Sons (second edition, 1996), which is hereby incorporated by reference. 
     The invention contemplates various ways to update the counter. The simplest approach is to increment the counter by some value. That value can be obvious (e.g., 1) or something more obscure such as 47 (a number or algorithm which may be different for each account or account range). The key is that the counter is something that can be anticipated by the acquirer as it authenticates the transaction request. Another method to obscure the value is to not have the starting value equal to 0 or 1. Rather, it may be seeded with a specific value (which also may vary by account or account range) and incremented. Finally, the counter may be a random number produced by some algorithm that is based on an initial seed that is produced by the RF device and is also known by the issuer. This is similar to a hidden secret known only to the device and the issuer. 
     The RE reader then utilizes the transaction request and creates a second authentication tag using the RF reader&#39;s encryption key. The RF reader converts the transaction request into a form recognized and used by its corresponding POS device (typically this will be using the format described by ISO 8583), including the two authentication tags, the RF device counter, and the RF reader random number. The extra data may be stored anywhere on the submission record. The POS device uses its existing payment infrastructure and network to send a message/request to the acquirer for the account for authorization of the transaction processing. 
     The acquirer routes the authorization request to the account issuer. The account issuer&#39;s authorization process substantially recognizes the type of request and substantially verifies the authentication tags from both the RF device and the RF reader. This approach provides better security of the request by verifying not only the RF device, but also verifying that the authorization request originated from a legitimate RF reader. Because the backend server verifies the authentication tags using the same encryption key, the correct encryption key for the RFID and the RF reader should be known by that same server. Whereas the encryption key may change for the different accounts that are used at any RF reader, the encryption key for the reader should be the same. The encryption key may be the same for all the RFIDs containing accounts in a particular number range, or it may be unique for each account. The incoming account number is used to identify the encryption key that is then used to calculate or recalculate, construct or reconstruct the authentication tag using the account number, random number and/or counter from the RF device. If the same authentication tag value is produced, the RF device tag is authentic and considered valid. 
     The authentication tag for the RF reader is processed in a similar manner. The encryption key associated with the RF reader based on the POS identifier from the incoming request is identified and used to rehash the incoming account number, random number, counter, and/or RF device authentication tag. If the same or substantially the same authentication tag value is produced, the RF reader tag is authentic and considered valid. 
     Once the authentication tags have been verified, the issuer validates the counter from the account. Depending on the method used to increment the counter, the acquirer may identify the expected counter value that it will match to the incoming counter value. Any unexpected or reused value may indicate a likely misuse of the RFID or a fraudulent replay of a previous RFID transaction request transmission. To account for undelivered or missing requests, the acquirer may allow for acceptable gaps in the counter value, but reused values may always be rejected. 
     If either authentication tag or the counter is found to be fully or partially invalid, the authorization request may be rejected. If they are found to be valid, the actual account number is submitted for payment authorization, using the normal process. The authorization response is then returned to the merchant. If the payment is authorized the merchant submits the request through its existing submissions infrastructure and network for settlement. 
     Another exemplary embodiment that may differ from the first RF device includes an authentication tag for the transaction request and the RF reader is not authenticated. A similar RF device process is used, but when the transaction request is sent to the RF reader, the reader simply converts the request into a form recognized and usable by the POS device. The issuer then verifies the authentication tag of the RF device. 
     In yet another exemplary embodiment the RF reader includes an authentication tag for the transaction request. In this embodiment, when the RFID is read by the RF reader, the account data and counter is provided to the RF reader. The RF reader uses its encryption key to create an authentication tag for the transaction request. The acquirer then verifies the authentication tag using the encryption key associated with the POS device. In this approach, the security of the account relies on the integrity of the POS device, while simplifying the process (the RFID does not increment a counter) and content (no encryption key) of the account. However, the RFID transmission is vulnerable to eavesdropping. This particular scheme does not necessarily encrypt the account data, but leaves it in the clear. The security is from the authentication tag(s), the nonce and counter that is used and verified by the issuer. Moreover, it helps to insure that the transaction request came from a credible source (e.g., the account and/or the POS device). However, unless the issuer enforces that the account number on the RF device can only originate from a RF associated POS device, this in and of itself may not be adequate to secure the account completely, since the payment information is communicated in the clear, the account number may be captured and faked in any normal online payment. However, by restricting these accounts to be used only through the RF payment channel, the appropriate controls may be enforced. 
     In another exemplary embodiment, more than one account or one number is stored on the RF device. Two kinds of account numbers, a routing number and transaction account number housed on the RF device may exist. The routing number may be an account number that cannot be used for payment, and that designates to which issuing bank the transaction request should be directed for authorization and submission (using the Industry routing currently used within the existing payment network). The encrypted account data from the RF device is included in the request and describes the actual account data (number and expiration date) to be used for the transaction processing. 
     In an alternate embodiment, the RF reader activates a RF device and sends a random number to the RF device. The RF device uses its encryption key to create an authentication tag using the routing number, the random number from the RF reader, the counter from the RF device, and/or the encrypted account data. The RF device then returns the routing number as the account number known by the RF reader and merchant, the counter, the encrypted account from the RF device, the random number provided by the RF reader and/or the authentication tag to the RF reader as a transaction request. 
     The RF reader converts this request into a form recognizable by a POS device and forwards the transaction request to its POS device. In an exemplary embodiment, the request may be in the ISO 8583 format. The POS device then forwards the request to the associated acquirer using the existing infrastructure and network based on the routing number provided. The POS device uses the standard 8583 protocol in a new, unique way, by placing the encrypted payload from the RFID, in this case containing the account number, into the Cryptogram field in the authorization request. The acquirer may forward the authorization to the issuing bank (if different). The issuing bank recognizes the type of request, and verifies the authentication tag and the counter for the request (as described previously). Since the routing number is defined as the account number on the ISO 8583 request it can be used by the issuing bank to locate the encryption key used to create the authentication tag for the RF device. If either the authentication tag or counter verification fails, the request is rejected and returned to the merchant. If both prove to be valid, the payload is decrypted using the encryption key used for the payload, again using a key that is retrieved based on the routing number. The encryption payload key and encryption key to create the authentication tag may be different keys. The decrypted transaction account number is processed using the authorization system. The authorization may be returned using business as usual procedures over the 8583 protocol. If the authorization is approved, the merchant submits the transaction request, the 8583 protocol is again used. The routing number may be used to route the submission to the acquiring bank for merchant payment. The encrypted payload from the RFID, may be included in the Cryptogram field in the submission request. When the issuing bank receives the transaction request, the account number in the Cryptogram field is decrypted using the secret encryption key associated with the routing number. The account member can then be billed based on the decrypted account number ID. 
     In still another exemplary embodiment, the invention uses more than one transaction account number on the RF device. As noted, there are two kinds of account numbers, a routing number and multiple transaction account numbers housed on the RF device. In this embodiment, the routing number may be an account number that cannot be used for payment, but that designates to which issuer the transaction request should be directed for authorization and submission (using the industry routing currently used within the existing payment network). The encrypted account data from the RF device may be included in the request and describes the actual account data (e.g., number and expiration date) to be used for the payment. 
     In one exemplary variation of this aspect, the system uses a paired list of routing and encrypted account data. The routing and encrypted account number to be used for the transaction request may be determined from the current value of the counter, so that the routing number and the encrypted account number are both unique for the transaction. When the RF device is activated when passed within range of a RF reader, the RF device increments the counter and uses the counter as an index to select the routing number and encrypted account number to include in the transaction request. These account numbers and the counter are then used with the random number from the RF reader, the counter and the encryption key to produce the authentication tag for the transaction request. There can be a single encryption key that is used for each of the encrypted account numbers on the RF device or each encrypted account may have its own encryption key that is used. 
     A PIN can also be used with the RF device for identification and authentication. If there are multiple accounts contained on the RF device, instead of relying on the counter and an algorithm to determine which should be used, a PIN provided by the accountholder may be used. When the RF device is presented to the RF reader, the accountholder may be prompted to enter a PIN. The PIN may simply authenticate the user to use the account. But when there are multiple accounts, the entered PIN may be used to identify which account should be used within the transaction request. This would allow the RF device to contain different account numbers for different types of account products, such as, for example, credit and charge cards. As an example, data related to two accounts may exist on the RF device representing a charge and credit card, each associated with a unique PIN. When the RF device is presented, the accountholder may decide which card and/or account should be used for the payment through the PIN entered. The entered PIN would be returned to the RF device and used to identify which card and/or account will be used. If the PIN for the charge card is used, that card account is used in the transaction request that is provided back to the RF reader. A counter valve may still be important for the purpose of building the authentication tag for the transaction request. Although this approach includes a RF device with greater processing capabilities, it extends the security of the account numbers imbedded on the card by requiring an explicit authentication of the account by the accountholder before the payment can be requested. 
     Another embodiment may include a single routing number associated with a RFID, but multiple encrypted account numbers. As the counter is incremented, the counter is used as an index to pull the next encrypted account number from protected memory on the RFID to be transmitted to the reader, using the already described random number, counter and/or authentication tag. 
     Since the RF device typically corresponds to only one actual account from the issuer the list of encrypted accounts on the RFID may correspond to a series of fa&gt;&gt;;ade account numbers that are linked to the single account number on a centralized server. Because the fa&gt;&gt;;ade numbers have limited use, it also possible to transmit them to the reader ‘in the clear’, without significantly impacting fraud rates. The fa&gt;&gt;;ade or blinded account numbers may be supported through a single-use account number or proxy account number (e.g., Private Payments) system, which identifies the underlying account number to be used for the transaction request. As the routing and encrypted account data is selected (by either the RF device or reader), it may be placed into the transaction request and forwarded to the POS device and the acquirer for authorization. Once the request has been authenticated (as described previously using the authentication tag and the RF device counter), the account where the charge will be applied may be authorized. The routing number is used to identify the encryption key to be used to decrypt the account data within the transaction request from the transaction request. The authorization system may recognize that the account is not a usable account number, but a fa&gt;&gt;;ade/blinded account. The authorization system may request a Private Payments system to identify the actual account number. The actual account number may be returned from Private Payments for authorization and the response may be returned to the requestor. For more information on Private Payment systems, see U.S. patent application Ser. No. 09/800,461, filed Mar. 7, 2001, and titled “SYSTEM FOR FACILITATING A TRANSACTION,” and U.S. patent application Ser. No. 10/905,078, filed Dec. 14, 2004, and titled “METHOD AND SYSTEM FOR FACILITATING A TRANSACTION USING A TRANSPONDER,” both of which are hereby incorporated by reference. 
     This embodiment may minimize risk by limiting the exposure of any account during any one transaction since the actual account may change from request to request. Although this appears to limit the life span of the RF device to the number of items included in the list, the counter may be reset once the limit of the list has been exceeded. Even though there are 10 items in the list, following the 10 requests, the counter may be offset (not reset because that would reduce the ability to properly verify misuse) so that the list of accounts may be used and reused. As discussed previously, the accounts may also be selected from the list randomly using an algorithm known only to the card and the acquirer. In this case, the account used cannot be anticipated without knowing the algorithm. Thus, the list may never really expire, instead its use may not follow a basic pattern. Finally, there may not be a one to one correlation between the counter and the encrypted account number returned, for example, an encrypted account number may be changed every 10 increments of the counter, increasing fraud potential insignificantly. 
     There may be two variables that may be changed to create other embodiments of the invention, namely, what is used to select the account data and where the account data is selected. Instead of using the counter from the RF device to identify what account data to use, the list may use a date range to define the effective period when each individual routing and encrypted account data would be used. Being date sensitive may limit the long-term use of this account to what is contained on the card. Once the last item in the list has been used, then the account may no longer be used. Instead of the RF device selecting the account data, the entire list may be sent to the RF reader and the reader may make the selection using either the counter or the date range. 
     Another exemplary embodiment of the invention may include a combination of the previous two, one routing account number and a list of encrypted account data. Which instance of the encrypted account data is used may be determined as described previously using the counter, random identifier, or an associated date range by either the RF device or RF reader. Whereas the routing number in the earlier descriptions represents how the data will be authenticated by the acquirer, this approach may include a unique routing number for each RF device. So as requests are made for a specific RF device for a specific counter, the corresponding account data from the list may be used for the transaction request. 
     Because the merchant knows the routing number, but not the payment account number when the actual account number is in the encrypted payload, disputes may be an issue. One way to solve this problem is to allow credits, that is refunds from the merchant, to be processed using the routing number. In this embodiment, only transaction requests from the merchant, in which the merchant attempts to use the routing number for payment may be rejected. 
     In another embodiment, during the authorization step, the issuing bank may return the actual payment credit card number in the response. This would result in the merchant knowing the ‘real’ credit card number, without the credit card number having ever been transmitted in the clear from the RFID. The merchant may then submit the ‘real’ credit card number with the transaction request, simplifying disputes. 
     Another exemplary embodiment extends the invention to include other encrypted data in the datagram sent in the 8583 protocols. The first example of this use may be to provide the customer&#39;s name on the payment receipt. For privacy reasons, the customer name may not be transmitted in the clear to the reader. In a unique usage of the 8583 protocol, the name may be protected without requiring decryption on the reader. The customer name may include an encrypted payload from the RFID, along with the account number. The RF reader may have no knowledge of the contents of the encrypted payload on the RFID and simply move this information into the cryptogram field in the authorization request. The acquirer may forward the authorization to the issuing bank (if different). At the issuing bank, the routing number would be used to determine the encryption key and use it to decrypt the payload from the RFID. The account number may be used as described previously for authorization. The decrypted name may be returned to the reader in the authorization request (if approved). The POS device would then use the name returned from the issuer to print on the customer&#39;s receipt. 
     The present invention also provides a system and method for a RF operable transaction device configured to manage multiple data sets (e.g., “application tenants”) of differing formats associated with a plurality of distinct transaction account issuers. In this context, an “application tenant” may include all or any portion of any data sets which are substantially correlated to an account issuer, which the issuer may additionally use to substantially identify an instrument user or related account. For example, where the account issuer provides application tenant information, the application tenant may include, inter alia, a membership identifier associated with a user enrolled in an issuer provided transaction account program, and all related subsets of data stored on the transaction device. Where multiple application tenants are referred to herein, each tenant may constitute its own distinct data set, independent of any other application tenant data sets. For example, each application tenant may include a unique membership identifier and all associated subsets of data. Alternatively, an application tenant may include a membership identifier and an application for processing all data owned by an issuer. Thus, the data set or subset may include the processing application. Moreover, differing formats, as discussed herein, include differences in all or any portion of the formats. As such, “application tenant” and “distinct data set,” and data set “owner” and account “issuer” may be used interchangeably herein. 
     In addition, it should be noted that although the present invention is described with respect to a financial transaction device, the invention is not so limited. The invention is suitable for any instrument capable of storing distinct data sets which may be provided by multiple distinct account issuers where the distinct data sets may be formatted one different from another. The account may be, for example, a calling card, a loyalty, debit, credit, incentive, direct debit, savings, financial, membership account or the like. While the information provided by the account issuers may be described as being “owned” by the issuers, the issuers or their designees may simply be a manager of the account. 
     The present invention may be described herein in terms of functional block components, optional selections and/or various processing steps. It should be appreciated that such functional blocks may be realized by any number of hardware and/or software components configured to perform the specified functions. For example, the present invention may employ various integrated circuit components (e.g., memory elements, processing elements, logic elements, look-up tables, and/or the like), which may carry out a variety of functions under the control of one or more microprocessors or other control devices. Similarly, the software elements of the present invention may be implemented with any programming or scripting language such as C, C++, Java, COBOL, assembler, PERL, Visual Basic, SQL Stored Procedures, extensible markup language (XML), with the various algorithms being implemented with any combination of data structures, objects, processes, routines or other programming elements. Further, it should be noted that the present invention may employ any number of conventional techniques for data transmission, signaling, data processing, network control, and/or the like. For a basic introduction of cryptography and network security, the following may be helpful references: (1) “Applied Cryptography: Protocols, Algorithms, And Source Code In C,” by Bruce Schneier, published by John Wiley &amp; Sons (second edition 1996); (2)·ava Cryptography” by Jonathan Knudson, published by O&#39;Reilly &amp; Associates (1998); and (3) “Cryptography and Network Security: Principles and Practice” by Mayiam Stalling, published by Prentice Hall; all of which are hereby incorporated by reference. 
     As used herein, the terms “user,” “end user,” consumer,” “customer” or “participant” may be used interchangeably with each other, and each shall mean any person, entity, machine, hardware, software and/or business. Furthermore, the terms “business” or “merchant” may be used interchangeably with each other and shall mean any person, entity, machine, hardware, software or business. Further still, the merchant may be any person, entity, software and/or hardware that is a provider, broker and/or any other entity in the distribution chain of goods or services. For example, the merchant may be a ticket/event agency (e.g., Ticketmaster, Telecharge, Clear Channel, brokers, agents). 
     The systems and/or components of the systems discussed herein may also include one or more host servers or other computing systems including a processor configured to process digital data, a memory coupled to the processor for storing digital data, an input digitizer coupled to the processor for inputting digital data, an application program stored in the memory and accessible by the processor for directing processing of digital data by the processor, a display coupled to the processor and memory for displaying information derived from digital data processed by the processor and a plurality of databases, the databases including client data, merchant data, financial institution data and/or like data that may be used in association with the present invention. As those skilled in the art may appreciate, the user interface for each system described herein may typically include an operating system (e.g., Windows NT, 95/98/2000, Linux, Solaris, etc.) as well as various conventional support software and drivers typically associated with computers. The user computer and other systems described herein can be in a home or business environment with access to a network. In an exemplary embodiment, access is through the Internet through a commercially-available web-browser software package. 
     Communication between various elements of the present invention is accomplished through any suitable communication means, such as, for example, a telephone network, intranet, Internet, point-of-sale device (point-of-sale device, personal digital assistant, cellular phone, kiosk, etc.), online communications, off-line communications, wireless communications, and/or the like. One skilled in the art may also appreciate that, for security reasons, any databases, systems, or components of the present invention may consist of any combination of databases or components at a single location or at multiple locations, wherein each database or system includes any of various suitable security features, such as firewalls, access codes, encryption, decryption, compression, decompression, and/or the like. 
     The systems may be suitably coupled to the network via data links. A variety of conventional communications media and protocols may be used for data links. For example, a connection to an Internet Service Provider (ISP) over the local loop as is typically used in connection with standard modem communication, cable modem, Dish networks, ISDN, Digital Subscriber Line (DSL), or various wireless communication methods. The merchant system might also reside within a local area network (LAN) that interfaces to the network via a leased line (T1, D3, etc.). Such communication methods are well known in the art and are covered in a variety of standard texts. See, e.g., Gilbert Held, “Understanding Data Communications” (1196), hereby incorporated by reference. 
     The computing units may be connected with each other via a data communication network. The network may be a public network and assumed to be insecure and open to eavesdroppers. In the illustrated implementation, the network may be embodied as the Internet. In this context, the computers may or may not be connected to the Internet at all times. For instance, the customer computer may employ a modem to occasionally connect to the Internet, whereas the bank computing center might maintain a permanent connection to the Internet. Specific information related to the protocols, standards, and application software utilized in connection with the Internet may not be discussed herein. For further information regarding such details, see, for example, Dilip Naik, “Internet Standards and Protocols” (1998);·ava 2 Complete,” various authors (Sybex 1999); Deborah Ray and Eric Ray, “Mastering HTML 4.0” (1997); Loshin, “TCP/IP Clearly Explained” (1997). All of these texts are hereby incorporated by reference. 
     It may be appreciated that many applications of the present invention may be formulated. One skilled in the art may appreciate that a network may include any system for exchanging data or transacting business, such as the Internet, an intranet, an extranet, WAN, LAN, satellite communications, and/or the like. It is noted that the network may be implemented as other types of networks, such as an interactive television (ITV) network. The users may interact with the system via any input device such as a keyboard, mouse, kiosk, personal digital assistant, handheld computer (e.g., Palm Pilot®), cellular phone and/or the like. Similarly, the invention may be used in conjunction with any type of personal computer, network computer, workstation, minicomputer, mainframe, or the like running any operating system such as any version of Windows, Windows NT, Windows2000, Windows 98, Windows 95, MacOS, OS/2, BeOS, Linux, UNIX, Solaris or the like. Moreover, although the invention is frequently described herein as being implemented with TCP/IP communications protocols, it may be readily understood that the invention may also be implemented using IPX, Appletalk, IP-6, NetBIOS, OSI or any number of existing or future protocols. Moreover, the present invention contemplates the use, sale or distribution of any goods, services or information over any network having similar functionality described herein. 
     In accordance with various embodiments of the invention, the Internet Information Server, Microsoft Transaction Server, and Microsoft SQL Server, are used in conjunction with the Microsoft operating system, Microsoft NT web server software, a Microsoft SQL database system, and a Microsoft Commerce Server. Additionally, components such as Access or SQL Server, Oracle, Sybase, Informix MySQL, Interbase, etc., may be used to provide an ADO-compliant database management system. The term “webpage” as it is used herein is not meant to limit the type of documents and applications that might be used to interact with the user. For example, a typical website might include, in addition to standard HTML documents, various forms, Java applets, Javascript, active server pages (ASP), common gateway interface scripts (CGI), extensible markup language (XML), dynamic HTML, cascading style sheets (CSS), helper applications, plug-ins, and/or the like. 
     The financial transaction device (e.g., smart card, magnetic stripe card, bar code card, optical card, biometric device, radio frequency fob or transponder and/or the like) may communicate to the merchant, information from one or more data sets associated with the financial transaction device. In one example, membership data and credit card data associated with an account or card may be transmitted using any conventional protocol for transmission and/or retrieval of information from an account or associated transaction card (e.g., credit, debit, loyalty, etc.). In one exemplary embodiment, the transaction device may be configured to communicate via RF signals. As such, the data contained on the instrument may be communicated via radio frequency signals. 
     A financial transaction device may include one or more physical devices used in carrying out various financial transactions. For example, a financial transaction device may include a rewards card, charge card, credit card, debit card, prepaid card, telephone card, smart card, magnetic stripe card, radio frequency card/transponder and/or the like. In yet another exemplary embodiment of the present invention, a financial transaction device may be an electronic coupon, voucher, and/or other such instrument. 
     The financial transaction device in accordance with this invention may be used to pay for acquisitions, obtain access, provide identification, pay an amount, receive payment, redeem reward points and/or the like. In the radio frequency (“RF”) embodiments of the transaction device, instrument to instrument transactions may also be performed. See, for example, Sony&#39;s “Near Field Communication” (“NFC”) emerging standard which is touted as operating on 13.56 MHz and allowing the transfer of any kind of data between NFC enabled devices and across a distance of up to twenty centimeters. See also, Bluetooth chaotic network configurations; described in more detail at http://www.palowireless.com/infotooth/whatis.asp, which is incorporated herein by reference. Furthermore, data on a first RF device may be transmitted directly or indirectly to another RF device to create a copy of all or part of the original device. 
     Furthermore, financial transaction device as described herein may be associated with various applications which allow the financial transaction devices to participate in various programs, such as, for example, loyalty programs. A loyalty program may include one or more loyalty accounts. Exemplary loyalty programs include frequent flyer miles, on-line points earned from viewing or purchasing products or websites on-line and programs associated with diner&#39;s cards, credit cards, debit cards, hotel cards, calling cards, and/or the like. Generally, the user is both the owner of the transaction card account and the participant in the loyalty program; however, this association is not necessary. For example, a participant in a loyalty program may gift loyalty points to a user who pays for a purchase with his own transaction account, but uses the gifted loyalty points instead of paying the monetary value. 
     Further still, a “code,” “account,” “account number,” “identifier,” “loyalty number” or “membership identifier,” as used herein, includes any device, code, or other identifier/indicia suitably configured to allow the consumer to interact or communicate with the system, such as, for example, authorization/access code, personal identification number (PIN), Internet code, other identification code, and/or the like that is optionally located on a rewards card, charge card, credit card, debit card, prepaid card, telephone card, smart card, magnetic stripe card, bar code card, radio frequency card and/or the like. The account number may be distributed and stored in any form of plastic, electronic, magnetic, radio frequency, audio and/or optical device capable of transmitting or downloading data from itself to a second device. A customer account number may be, for example, a sixteen-digit credit card number, although each credit provider has its own numbering system, such as the fifteen-digit numbering system used by an exemplary loyalty system. Each company&#39;s credit card numbers comply with that company&#39;s standardized format such that the company using a sixteen-digit format may generally use four spaced sets of numbers, as represented by the number “0000 0000 0000 0000”. The first five to seven digits are reserved for processing purposes and identify the issuing bank, card type and etc. In this example, the last sixteenth digit is used as a sum check for the sixteen-digit number. The intermediary eight-to-ten digits are used to uniquely identify the customer. In addition, loyalty account numbers of various types may be used. 
     Further yet, the “transaction information” in accordance with this invention may include the nature or amount of transaction, as well as, a merchant, user, and/or issuer identifier, security codes, or routing numbers, and the like. In various exemplary embodiments of the present invention, one or more transaction accounts may be used to satisfy or complete a transaction. For example, the transaction may be only partially completed using the transaction account(s) correlating to the application tenant information stored on the transaction device with the balance of the transaction being completed using other sources. Cash may be used to complete part of a transaction and the transaction account associated with a user and the transaction device, may be used to satisfy the balance of the transaction. Alternatively, the user may identify which transaction account, or combination of transaction accounts, stored on the transaction device the user desires to complete the transaction. Any known or new methods and/or systems configured to manipulate the transaction account in accordance with the invention may be used. 
     In various exemplary embodiments, the financial transaction device may be embodied in form factors other than, for example, a card-like structure. As already mentioned, the financial transaction device may comprise an RF transponder, a speed pass, store discount card, or other similar device. Furthermore, the financial transaction device may be physically configured to have any decorative or fanciful shape including key chains, jewelry and/or the like. The financial transaction device may furthermore be associated with coupons. A typical RF device which may be used by the present invention is disclosed in U.S. application Ser. No. 10/192,488, entitled “System And Method For Payment Using Radio Frequency Identification In Contact And Contactless Transactions,” and its progeny, which are all commonly assigned, and which are all incorporated herein by reference. 
     As used herein, the term “data set” may include any set of information and/or the like which may be used, for example, in completing a transaction. For example, data sets may include information related to credit cards, debit cards, membership clubs, loyalty programs, speed pass accounts, rental car memberships, frequent flyer programs, coupons, tickets and/or the like. This information may include membership identifiers, account number(s), personal information, balances, past transaction details, account issuer routing number, cookies, identifiers, security codes, and/or any other information. The data set may additionally include an issuer defined management process for determining which subsets of data are to be provided to an issuer or merchant. In some instances, a data set may be associated with one or more account numbers corresponding to accounts maintained by the account issuer. 
     The various data sets associated with a financial transaction device may either be stored on the financial transaction device itself or remotely. In one exemplary embodiment, the financial transaction device itself is configured to store at least two data sets. In other exemplary embodiments, data sets may be stored in one or more databases and the data sets are affiliated with the financial transaction device. For example, a central database on the instrument may store multiple distinct data sets correlated with a unique issuer. The data sets stored on the remote database may be stored thereon, in such a manner as to mimic the corresponding data sets stored on the transaction device. The multiple distinct data sets may be accessed, for example, by a merchant system, whether stored on the transaction device or remote database stand alone device, and/or a computer user interface, via a network. In this example, the financial transaction device may include one or more user identifiers (e.g., membership identifiers), which may be used to provide access to a subset of data included on the financial transaction device. 
     Various information and data are described herein as being “stored.” In this context, “stored” may mean that the information is kept on a database. In accordance with the invention, a database may be any type of database, such as relational, hierarchical, object-oriented, and/or the like. Common database products that may be used to implement the databases include DB2 by IBM (White Plains, N.Y.), any of the database products available from Oracle Corporation (Redwood Shores, Calif.), Microsoft Access or MSSQL by Microsoft Corporation (Redmond, Wash.), or any other database product. Databases may be organized in any suitable manner, including as data tables or lookup tables. Association of certain data may be accomplished through any data association technique known and practiced in the art. For example, the association may be accomplished either manually or automatically. Association techniques include common techniques such as using a key field in the tables to speed searches, sequential searches through all the tables and files, and sorting records in the file according to a known order to simplify lookup. 
     Although all data sets associated with a particular financial transaction device may be owned by the same owner, it is contemplated that in general, some of the data sets stored on the financial transaction device have different owners. Furthermore, the storage of data sets is configured to facilitate independent storage and management of the data sets on the financial transaction device. Further still, the data sets may be stored in distinct differing formats provided by the distinct issuer or data set owner (also called “issuer,” herein). The owners of data sets may include different individuals, entities, businesses, corporations, software, hardware, and/or the like. However, one skilled in the art will appreciate that the owners may also include different divisions or affiliates of the same corporation or entity. 
     A data set may contain any type of information stored in digital format. For example, a data set may include account numbers, programs/applications, scripts, cookies, instruments for accessing other data sets, and/or any other information. 
     As discussed above, many issuers of existing financial transaction devices utilize predetermined formats for account numbers, data and/or applications stored in association with the financial transaction device. Similarly, the data storage media associated with these financial transaction devices are typically configured to accommodate specific predetermined data formats. Thus, since the data format associated with a first issuer is often different from a data format of a second issuer, storage of multiple distinct data of differing formats on a single device provides complications for conventional systems. This is true since, each issuer typically maintains an account processing system that uses a processing protocol different from other issuers, and the information stored on the transaction card relative to the issuer must be formatted accordingly. As such, to ensure the security and integrity of the issuer-owned data, the loading of data on a transaction device is typically performed by an issuer or a third-party provider who typically uploads all related and similarly formatted data sets onto the transaction device. However, since the third party may typically only be authorized by the issuer to load issuer-owned data of similar format onto an issuer-provided transaction device, including differently formatted data sets on a single transaction device by the third party is often not permitted. More particularly, independent owners of data sets are often reluctant to conform their data set formats to a “standard format” because of the security advantages of maintaining a separate, distinct, often secreted format. 
     In contrast, and in accordance with an exemplary embodiment of the present invention, the format of the information stored in the present invention may vary from one data set to another. That is, the present invention permits the data to be stored on the financial transaction device in any format, and more particularly, in any format recognizable by the data owner/transaction device issuer. Thus, as noted, each data set may be used for a very wide variety of purposes including storage of applications, raw data, cookies, coupons, membership data, account balances, loyalty information, and/or the like. 
     In accordance with one aspect of the present invention, any suitable data storage technique may be utilized to store data without a standard format. Data sets may be stored using any suitable technique, including, for example, storing individual files using an ISO/IEC 7816-4 file structure; implementing a domain whereby a dedicated file is selected that exposes one or more elementary files containing one or more data sets; using data sets stored in individual files using a hierarchical filing system; data sets stored as records in a single file (including compression, SQL accessible, hashed via one or more keys, numeric, alphabetical by first tuple, etc.); block of binary (BLOB); stored as ungrouped data elements encoded using ISO/IEC 7816-6 data elements; stored as ungrouped data elements encoded using ISO/IEC Abstract Syntax Notation (ASN.1) as in ISO/IEC 8824 and 8825; and/or other proprietary techniques that may include fractal compression methods, image compression methods, etc. 
     In one exemplary embodiment, the ability to store a wide variety of information in different formats is facilitated by storing the information as a Block of Binary (BLOB). Thus, any binary information can be stored in a storage space associated with a data set. As discussed above, the binary information may be stored on the financial transaction device or external to but affiliated with the financial transaction device. The BLOB method may store data sets as ungrouped data elements formatted as a block of binary via a fixed memory offset using either fixed storage allocation, circular queue techniques, or best practices with respect to memory management (e.g., paged memory, memory recently used, etc.). By using BLOB methods, the ability to store various data sets that have different formats facilitates the storage of data associated with the financial transaction device by multiple and unrelated owners of the data sets. For example, a first data set which may be stored may be provided by a first issuer, a second data set which may be stored may be provided by an unrelated second issuer, and yet a third data set which may be stored, may be provided by a third issuer unrelated to the first and second issuers. Each of these three exemplary data sets may contain different information that is stored using different data storage formats and/or techniques. Further, each data set may contain subsets of data which also may be distinct from other subsets. 
     Even further, where the invention contemplates the use of a self-service user interaction device. In this context, the self-service user interaction device may be any device suitable for interacting with a transaction device, and receiving information from the transaction device user and providing the information to a merchant, account issuer, account manager, data set owner, merchant point of sale, and the like. For example, the self-service user interaction device may be a stand alone read write device, self-service kiosk, merchant point of sale, read/write device, and the like. In one example, the self-service user interaction device may be configured to communicate information to and from the transaction device and to manipulate the data sets stored thereon. The self-service interaction device may be in communication with the various components of the invention using any communications protocol. 
     In general, systems and methods disclosed herein, are configured to facilitate the management of multiple distinct data sets associated with a financial transaction device. Management of data sets may include such steps as adding, augmenting, updating and/or deleting data sets associated with the financial transaction device. Such manipulations of the data may occur without replacing or reissuing the financial transaction device. With reference to  FIG. 1 , an exemplary method  100  according to the present invention is shown. Method  100  may include issuing a financial transaction device issued to a transaction device user (step  110 ), enrolling multiple data set owners in a multiple account on a transaction device program (step  112 ), and managing data sets associated with the financial transaction device (step  120 ). In managing the data, the method  100  may determine, for example, whether the data should be added to a data set (step  130 ), modified (step  140 ) or deleted (step  150 ), as described more fully below. Once the data is appropriately managed, the financial transaction device user may present the data contained on the instrument to a merchant system for completion of a transaction. The system may be further configured such that, during an exemplary transaction, data sets associated with the financial transaction device may be managed. For example, the user may be prompted (e.g., on a screen, by electronic voice, by a store clerk, by a signal and/or the like) as to the possibility of adding, for example, a loyalty account to the same financial transaction device and the user may also be presented with terms and/or conditions in a similar or different manner. The user may be prompted at any time during the transaction, but in an exemplary embodiment, the user is prompted at the completion of the transaction. If the user accepts the invitation to add data to the financial transaction device, a new data set may be added (step  130 ) and/or an existing data set is updated (step  140 ). For example, if data is to be updated, the stand alone may locate appropriate data to be updated on the transaction device, and make the updates (“modifications”) in accordance with data owner instructions. If the data is to be added, the stand alone device may be configured to provide any account information (e.g., account identifier, security code, data owner routing number, etc.) to the transaction device for storage thereon. The stand alone may locate an appropriate database location on transaction device for storing the added data. The stand alone device facilitates storage of the data in a distinct location on the transaction device database, where the data is stored independently of any other data. In an exemplary embodiment of the invention, the data is added to a database location on the transaction device which reserved for independently storing all data owned by a particular data set owner. Alternatively, the data may be stored in a distinct location on the transaction device, which is a separate location than is used to store any other data set. Further still, the data set is stored in accordance with any storage protocol permitting the data to be stored and retrieved independently of other data. The adding and updating of the data may be verified by the issuer, prior to making the modifications. If verified, all databases containing the data set to be updated or a mirror image of the data set to be updated, are modified in accordance with the user or issuer provided instructions, and/or the issuer defined data storage protocol or format. 
     In one exemplary embodiment, multiple account issuers may be enrolled in a multiple account management program using a financial transaction device in accordance with the invention (step  112 ). For example, permission for adding account issuer-owned data may be obtained from the data set owner. The data set owner may then be requested to provide account information to be stored on a transaction device. The data set owner may then provide account information relative to a distinct user account for loading onto the transaction device in accordance with the present invention. The issuers may be enrolled prior to issuance of the instrument or the issuers may be enrolled after issuance. By enrolling in the management program, the issuer may provide authorization for including the issuer-owned data on the financial transaction device. The issuer-owned data may be included (e.g., added, deleted, modified, augmented, etc.) on the transaction device using a stand alone interaction device, merchant system, or user personal computer interface upon presentment of the transaction device to the stand alone interaction device  290  (step  114 ). The stand alone interaction device may manipulate the issuer-owned data while preserving a format recognizable by an issuer account management system. For example, the stand alone device may identify the appropriate header or trailer associated with the data and add, delete or modify the data accordingly. The stand alone may manipulate the data using any manipulation instruction or protocol as provided by the data set owner so that the resulting manipulated data is in a format recognizable by the data set owner system. In this way, the stand alone device may manipulate the data while maintaining the data set owner&#39;s format. Alternatively, the interaction device may store the issuer-owned data on the transaction device in any format, provided that the issuer-owned data is provided to the issuer system (or to merchant system) in an issuer system (or merchant system) recognizable format. 
     It should be noted, that the financial transaction device may be issued with or without one or more data sets stored thereon. The financial transaction device may be issued using various techniques and practices now known or hereinafter developed wherein an instrument is prepared (e.g., embossed and/or loaded with data) and made available to a user for effecting transactions. Although the present invention may contemplate managing data sets (step  120 ) before issuing a financial transaction device (step  110 ), in various exemplary embodiments, by way of illustration, the data sets are described herein as being managed (step  120 ) after issuance (step  11   0 ). 
     At any time after issuance (step  110 ) of the financial transaction device, the financial transaction device may be used in a commercial transaction. In one exemplary embodiment of the present invention, a user communicates with a merchant, indicates a desire to participate in a issuer provided consumer program. The user may communicate with the merchant by, for example, presenting the transaction device to the merchant and indicting a desire to complete a transaction. The user may indicate his desire to complete a transaction using any conventional process used by the merchant. The user may further indicate that the user wished to complete the transaction using the financial transaction device. 
     During completion of the transaction, the user may present the financial transaction device to a merchant system. The financial transaction device is configured to communicate with the merchant, using any conventional method for facilitating a transaction over a network. 
     As stated above, in various embodiments of the present invention, the data can be stored without regard to a common format. However, in one exemplary embodiment of the present invention, the data set (e.g., BLOB) may be annotated in a standard manner when provided for manipulating the data onto the financial transaction device. The annotation may comprise a short header, trailer, or other appropriate indicator related to each data set that is configured to convey information useful in managing the various data sets. For example, the annotation may be called a “condition header,” “header,” “trailer,” or “status,” herein, and may comprise an indication of the status of the data set or may include an identifier correlated to a specific issuer or owner of the data. In one example, the first three bytes of each data set BLOB may be configured or configurable to indicate the status of that particular data set (e.g., LOADED, INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED). Subsequent bytes of data may be used to indicate for example, the identity of the issuer, user, transaction/membership account identifier or the like. Each of these condition annotations are further discussed herein. 
     The data set annotation may also be used for other types of status information as well as various other purposes. For example, the data set annotation may include security information establishing access levels. The access levels may, for example, be configured to permit only certain individuals, levels of employees, companies, or other entities to access data sets, or to permit access to specific data sets based on the transaction, merchant, issuer, user or the like. Furthermore, the security information may restrict/permit only certain actions such as accessing, modifying, and/or deleting data sets. In one example, the data set annotation indicates that only the data set owner or the user are permitted to delete a data set, various identified merchants are permitted to access the data set for reading, and others are altogether excluded from accessing the data set. However, other access restriction parameters may also be used allowing various entities to access a data set with various permission levels as appropriate. 
     The data, including the header or trailer may be received from a data set owner via any communication method described herein. The header or trailer may be appended to a data set to be modified, added or deleted, to indicate the action to be taken relative to the data set. The data set owner may provide the to a stand alone interaction device configured to add, delete, modify, or augment the data in accordance with the header or trailer. As such, in one exemplary embodiment, the header or trailer is not stored on the transaction device along with the associated issuer-owned data but instead the appropriate action may be taken by providing to the transaction device user at the stand alone device, the appropriate option for the action to be taken. However, the present invention contemplates a data storage arrangement wherein the header or trailer, or header or trailer history, of the data is stored on the transaction device in relation to the appropriate data. 
     In various exemplary embodiments, the steps of adding, deleting, augmenting and/or modifying data sets may be repeated. For example, first, second, and additional data sets may be added (step  130 ) to the financial transaction device in any order. In one exemplary embodiment of the present invention, the first data set is owned by a first data set owner (i.e., first issuer) and the second data set is owned by a second data set owner (i.e., second issuer). Furthermore, the system may include replacing a first data set with a subsequent data set by deleting a data set (step  150 ), then adding a data set (step  130 ). 
     With reference now to  FIG. 2 , in one exemplary embodiment of the present invention, a data set management system (“management system”)  200  comprises a merchant system  220 , various issuer systems  230 , and a financial transaction device  240 . Management system  200  may further be accessed by a user  201  on a self-service interaction device, such as, for example, user computer  250  or via a transaction device such as, for example, kiosk  270 , stand alone interaction device  290 , automated teller, or the like. In these examples, communications between user computer  250  or kiosk  270  and merchant system  220  or issuer systems  230  may take place via, for example, a network  260 . In various embodiments, merchant system  220 , user computer  250  and/or kiosk  270  are configured to communicate with financial transaction device  240 . For example, communication with financial transaction device  240  may be facilitated by a point-of-read/write device  280 , such as a merchant point of sale, merchant RFID reader, computer interface, or the like, configured to receive information provided by financial transaction device  240 . 
     In general, merchant system  220  is configured to interact with a user  201  attempting to complete a transaction, and to communicate transaction data to one or more of issuer systems  230 . Issuer systems  230  are configured to interact with financial transaction device  240  to receive and/or exchange data facilitating a transaction. Merchant system  220  may be operated, controlled and/or facilitated by any merchant that accepts payment via a transaction device. 
     Merchant system  220  is configured to facilitate interaction with user  201 , which may be any person, entity, software and/or hardware. User  201  may communicate with the merchant in person (e.g., at the box office), or electronically (e.g., from a user computer  250  via network  260 ). During the interaction, the merchant may offer goods and/or services to user  201 . The merchant may also offer user  201  the option of completing the transaction using a financial transaction device. The merchant system may provide the options to user  201  using interactive user interface, suitable website or other Internet-based graphical user interface that is accessible by users. 
     Each user  201  may be equipped with a computing system to facilitate online commerce transactions. For example, user  201  may have a computing unit in the form of a personal computer (e.g., user computer  250 ), although other types of computing units may be used including laptops, notebooks, hand held computers, set-top boxes, and/or the like. Merchant system  220  may have a computing unit  222  implemented in the form of a computer-server, although other implementations are possible. Issuer system  230  may have a computing center such as a main frame computer. However, the issuer computing center may be implemented in other forms, such as a mini-computer, a PC server, a network set of computers, or the like. 
     Issuer system  230  may be configured to manipulate a transaction account associated with the corresponding issuer-owned data stored on transaction device  240  (or database  282 , discussed below) in accordance with a related transaction. For example, issuer system  230  may receive “transaction information” and manipulate an account status or balance in accordance with the information received. In accordance with the transaction amount, issuer system  230  may, for example, diminish a value available for completing a transaction associated with the account, or issuer system  230  may alter the information relative to the account user (e.g., demographics, personal information, etc.). 
     It should be noted that issuer systems  230  may also be configured to interact with financial transaction device  240 , directly or indirectly via database  282  or stand alone interaction device  290 , to individually manage data sets on financial transaction device  240 . For example, issuer systems  230  may manage data sets on database  282 . In some embodiments, the data sets on database  282  may then be stored on financial transaction device  240  when the transaction device is presented. In other embodiments, issuer systems  230  may store data set information within their own systems which may communicate with the financial transaction device via user computer  250 , kiosk  270 , or merchant system  220 . In such embodiments, issuer system  230  may be configured to push the data set to financial transaction device  240  via the stand alone interaction device  290 , or merchant system  220 , kiosk  270 , interaction device  290  or computer  250  which may be configured to pull such information from issuer system  230 . 
     In addition, the data may be manipulated using, for example, a stand alone interaction device  290  configured to communicate with at least one of issuer systems  230  which may or may not be configured to communicate with a merchant system  220 . Interaction device  290  may communicate with issuer systems  230  using any of the aforementioned communication protocols, techniques and data links. The communication between the stand alone interaction device  290  and issuer system  230  may be facilitated by a network  260 . In an exemplary embodiment, network  260  may be secure against unauthorized eavesdropping. 
     Interaction device  290  may provide instructions to issuer systems  230  for requesting receipt of issuer-owned data, such as for example, account data, user member identification data, member demographic data, or the like, which the issuer wishes to store on financial transaction device  240 . Interaction device  290  may communicate with issuer systems  230  using an issuer recognizable communications protocol, language, methods of communication and the like, for providing and receiving data. In one exemplary embodiment, issuer-owned data is received by interaction device  290  from issuer systems  230 , and stored onto financial transaction device  240 . The data may be stored or manipulated in accordance with the issuer provided instructions, protocol, storage format, header or trailers received by the interaction device from issuer systems  230 . The issuer-owned data may be stored on financial transaction device  240  in any format recognizable by a merchant system  220 , and further recognizable by issuer system  230 . In one exemplary embodiment, the issuer-owned data is stored using a issuer system  230  format which may be later formatted in merchant system  220  recognizable protocol when provided to merchant system  220 . In one embodiment, the issuer-owned information is stored on financial transaction device  240  in the identical format with which it was provided by issuer system  230 . In that regard, interaction device  290  may be any device configured to receive issuer-owned data from an issuer system  230 , and write the data to a database, such as, for example, a database on transaction device  240  or database  282 . Further, as described more fully below, the issuer-owned information may also be provided by issuer system  230  to a remote database  282  where the information is stored such that it mirrors the corresponding information stored on transaction device  240 . 
     Interaction device  290  may be initialized prior to use. For example, interaction device  290  may be any system which may be initialized (“configured”) to communicate with a merchant system  220 . Where the interaction device is not initialized prior to attempting communications with merchant system  220  or transaction device  240 , interaction device  290  may be initialized at merchant system  220  location. Interaction device  290  may be initialized using any conventional method for configuring device communication protocol. 
     As noted, in accordance with the invention a transaction device is provided which permits the storage and presentment of at least one of a plurality of data sets for completing a transaction. The data sets may be stored on the transaction device itself, or on a remote database, as described below. The data sets stored with regard to the transaction device may be modified, deleted, added or augmented, as required by the issuer or the user. For example, as owner of the data, an issuer may modify a data set at the issuer&#39;s discretion. The issuer may modify the data, data subsets, member identifier and/or applications or data sets associated with its transaction account program. Such modifications may be completed or substantially completed in substantially real-time or at a later date, for example, when the transaction device is next presented. 
     In a typical example of issuer modification of the data sets, one or more data sets may be modified by issuer system  230  directly via issuer systems  230 , upon presentment of financial transaction device  240  to the system  230 . That is, user  201  may present the card to issuer system  230 , and issuer system  230  may modify the issuer data stored thereon, using any issuer defined protocol. Alternatively, the modifications, or instructions for modification, may be initiated at issuer system  230 , and provided to network  260 . The modifications and/or modification instructions may additionally be provided to a suitable device configured to communicate with transaction device  240 , receive information regarding the data stored on transaction device  240 , and to write or overwrite the information contained on transaction device  240 . For example, as noted, interaction device  290  is a suitable interaction device which may be used to provide information to transaction device  240  to modify the information stored thereon. Interaction device  290  may be any device capable of receiving data management instructions from issuer systems  230  and for updating the data stored on transaction device  240 , in accordance with the instructions received. In this regard, interaction device  290  may include any electronic components, databases, processors, servers and the like which may be used to modify the data stored on transaction device  240  using any suitable data modification protocol as is found in the art. In an exemplary embodiment, the interaction device is configured to modify the data on the transaction device in accordance with a data owner defined protocol. 
     In one exemplary embodiment, interaction device  290 , may be configured to modify the transaction device&#39;s  240  issuer-owned data when transaction device  240  is initially configured, prior to providing transaction device  240  to user  201 . Interaction device  290  may additionally be configured to modify the issuer data on transaction device  240  when transaction device  240  is next presented, for example, to the stand alone interaction device  290 . In this regard, interaction device  290  may receive from multiple distinct issuer systems  230 , via network  260 , the issuer provided modifications/instructions and may update transaction device  240  in real-time or substantially real-time. The modifications may be provided to interaction device  290  for storage and later use when transaction device  240  is next presented. Alternatively, interaction device  290  may be configured to retrieve the instructions from issuer system  230  when transaction device  240  is next presented to device  290 . Further, where other devices, such as, for example, a kiosk  270 , merchant point-of-sale device, or the like, are likewise configured to modify the issuer data on transaction device  240 , the invention contemplates that the real-time or substantially real-time modifications noted above may be made using those devices in similar manner as is described with interaction device  290 . 
     Alternatively, the device to which transaction device  240  may be presented, may not be equipped for updating or modifying the data stored on transaction device  240 . For example, merchant system  220  may be any conventional merchant system which communicates to an issuer system  230 , and which permits a user  201  to complete a financial transaction, but which is not configured to modify the issuer data contained on transaction device  240 . In general, conventional merchant systems are not configured to write or overwrite data included on the payment devices presented to the merchant system for processing. That is, merchant system  220  may include little or no additional software to participate in an online transaction supported by network  260 . Management of the data sets on transaction device  240  may be performed independent of the operation of merchant system  220  (e.g., via issuer system  230  or interaction device  290 ). As such, the present invention may require no retrofitting of merchant system  220 , to accommodate system  200  operation. Thus, where merchant system  220  is not configured to modify the data on transaction device  240 , such modifications may be made as described above with respect to modifications being made at interaction device  290  or by the issuer at issuer system  230 . 
     Merchant system  220 , kiosk  270 , interaction device  290 , may include additional means for permitting the transaction device user  201  to self-manage the data stored on transaction device  240 . In this case, the systems  220 ,  270 , and  290  may include an additional user interface for use by user  201  to identify the modification action to be taken. Where the systems  220 ,  270 , and  290  are configured to communicate with transaction device  240  and to modify the data thereon, the modifications may be completed or substantially completed in real-time or substantially real-time. For example, user  201  may present transaction device  240  to one of the systems  220 ,  270 , or  290 , provide instructions to the system  220 ,  270 , or  290  for modifying the data on transaction device  240 . The instructions may include, for example, “ADD,” “DELETE,” MODIFY,” and the system  220 ,  270 , or  290  may modify the data stored on transaction device  240  in accordance therewith. The modifications may be made on the instrument in real-time or substantially real-time, for example, prior to permitting transaction device  240  to be used by user  201 . Alternatively, the modifications or instructions for modification may be provided by user  201  to merchant system  220  or kiosk  270 , and merchant system  220  or kiosk  270  may further provide the modifications/instructions to network  260  for use in later modifying the data. For example, the modifications/instructions may be provided by system  220  or  270  to issuer system  230  managed by the issuer owning the data to be modified. Issuer system  230  may provide the modifications to, for example, interaction device  290 , for updating transaction device  240  when next presented. The modifications/instructions may additionally be provided from network  260  to a remote database, where the modifications/instructions corresponding to the transaction device and the issuer may be additionally stored (i.e., database  282 , described below). In one exemplary embodiment, the modifications/instructions may be stored at issuer system  230 , until such time as transaction device  240  is next presented to a device configured to modify the data on the instrument. Once presented, the modifications/instructions may be provided to the device (e.g., computer  250 , interaction device  290 , etc.) for modifying transaction device  240  data. 
     In another exemplary embodiment, user  201  may self-manage the data sets by, for example, modifying the data sets using a conventional computer system  250 , which may be in communication with network  260 . Computer system  250  may or may not be configured to interact with financial transaction device  240 . Where computer system  250  is not configured to interact with transaction device  240 , user  201  may provide modifications or instructions to issuer system  230  for later use in modifying the corresponding transaction device  240  data, for example, when transaction device  240  is next presented in similar manner as described above. Where computer  250  is configured to interact with financial transaction device  240  to modify the data stored thereon, user  201  may provide modifications/instructions to computer  250  for modifying the data on the financial instrument in real-time or substantially real-time. That is, computer  250  may be configured to interact with, read, add, delete, and/or modify the data sets on transaction device  240 . Consequently, computer  250  may receive modifications/instructions from user  201  and perform the modifications accordingly, and may modify the data in real-time or substantially real-time. Computer  250  may additionally be configured to receive authorization of the modifications/instructions from issuer system  230  prior to making user  201  requested changes. In one exemplary arrangement, user  201  may provide the modifications/instructions via network  260  which may be additionally provided to issuer system  230 . Issuer system  230  may receive user  201  modifications/instructions and verify whether the identified updates are available to user  201  or if the identified updates are valid. If the identified updates are authorized, issuer system  230  may update a data storage area associated with transaction device  240 . For example, issuer system  230  may update an issuer database (not shown) containing data corresponding to the issuer-owned data associated with transaction device  240 . Alternatively, issuer system  230  may provide modifications/instructions to a database positioned remotely to issuer system  230  for use in modifying the data stored thereon, which is associated to the transaction device  230 . As such, in accordance with the present invention, user  201  may self-manage the data via, for example, user computer  250 , a kiosk  270 , a merchant system  220 , and/or a stand alone interaction device  290 . 
     In one exemplary method of self-management, user  201  logs onto a website via user computer  250 , or onto a stand alone device, such as, for example, interaction device  290  or kiosk  270 , and selects options for configuring data sets on a financial transaction device  240 . The changes may be transmitted to transaction device  240  via a instrument reader/writer device  280  configured to communicate the data to transaction device  240 . In this context, the reader/writer device  280  may be any conventional transaction device reader or writer. 
     As noted, modifications to the data stored on financial transaction device  240  may be made in real-time or substantially real-time when transaction device  240  is presented to interaction device  290 , or to a reader/writer device  280 . However, as noted, various embodiments of the invention include a remote database  282  in communication with an issuer system  230  via network  260 . Remote database  282  may additionally be in communication with one of user computer  250 , kiosk  270 , merchant system  220  and/or interaction device  290 , for variously receiving modifications or instructions for performing modifications to the data stored thereon. In addition, database  282  may contain a data storage area which “mirrors” the data stored on transaction device  240 . In this context “mirrored” or “mirror” may mean that the data is stored on database  282  in substantially identical configuration and format as stored on transaction device  240 . As such, the present invention may be configured to permit modifications made to transaction device  240  data to be mimicked on corresponding data locations on database  282 . For example, user  201  may self-manage the data on database  282  via a user interface in communication with database  282  via network  260 . In one exemplary embodiment, user  201  may communicate with a “website” which is used to manage database  282 , wherein database  282  is a database including unique locations for storing the issuer provided data and data sets correlative to the data and data sets stored on transaction device  240 . The website may include an account management application which permits user  201  to select which user accounts to add, delete, or modify with respect to transaction device  240 . That is, user  201  may provide unique identifying information to user computer  250  which may be recognized by the system (e.g., issuer system  230  or remote system managing database  282 ) managing database  282 , thereby permitting user  201  to access the data corresponding to the unique identifying information stored on database  282 . Further, prior to permitting modifications to database  282 , the issuer owning the data may require authorization that such modifications may be performed. Further still, the present invention contemplates that database  282  may be self-managed by user  201  in similar manner, where merchant system  220 , kiosk  270  and/or interaction device  290  are configured to provide modifications/instructions to issuer systems  230  and database  282 . 
     In another exemplary embodiment, database  282  serves as a temporary or redundant storage space for data sets. Thus, a “mirror image” of the data sets currently on financial transaction device  240  may be maintained and/or updated at appropriate intervals for facilitating replacement of, for example, a damaged financial transaction device  240 . As such, database  282  may be used, for example, for verifying the validity or accuracy of the information stored on transaction device  240 . Also, changes to one or more data sets may be stored to database  282  pending an opportunity to update financial transaction device  240 . In various embodiments, such updating may take place in both directions similar to hot sync technology. 
     As noted, in some exemplary embodiments of the invention, authorization must be obtained from issuer systems  230  prior to making any modifications to the data contained on transaction device  240  or database  282 . Authorization may be obtained by requesting the authorization during the modification process. Authorization may be given where user  201  provides the more appropriate security information, which is verified by issuer system  230 . The security information may be, for example, a security code granting access to the issuer-owned data on transaction device  240  or database  282 . For example, a point-of-sale (POS) machine may be configured to allow the input of a code, or an answer to a prompt which is provided to and verified by issuer system  230 . Once verified the modification requested may be made to the data contained on financial transaction device  240 . 
     It should be noted that the authorization code may be used to permit user  201  to select which issuer provided data to utilize for completion of a transaction. For example, a point-of-sale device (POI) device may be programmed to search financial transaction device  240  for a data set containing a particular club membership data set, or to locate all available data sets for providing to user  201  display available data sets to user  201 , thereby permitting user  201  to select which data set to use to complete a transaction. If no data set is found, the POS device may alert user  201  or prompt the merchant to alert user  201  of the possibility of adding issuer-owned data to financial transaction device  240 . A positive response to this alert may cause the POS device to add an issuer data set to transaction device  240 . 
     It is noted that user  201  may already be a member of a membership program managed by an issuer system  230  in which case the associated user  201  membership data may be assigned to user  201  for inclusion on transaction device  240 . As such, user  201  may be permitted to add the membership data set to transaction device  240 . Alternatively, the user may become a member by selecting to add the membership information to financial transaction device  240 , using the interactive device  290 . In some embodiments, changes made to the data sets stored on transaction device  240  may be updated to financial transaction device  240  in real-time or substantially real-time, where the device  290  is in communication with transaction device  240 . Or the changes may be made the next time user  201  presents financial transaction device  240  to stand alone interaction device  290  or to a kiosk  270 , merchant system  220 , or the like. 
     In another exemplary embodiment of the present invention, merchant system  220 , kiosk  270 , and/or user computer  250  may be configured to interact with financial transaction device  240  via a read/write device  280 . Read/write device  280  may be any device configured to communicate with financial transaction  240 . In one embodiment, read/write device  280  is configured to read and write to financial transaction device  240 . For example, read/write device  280  may be a point-of-sale magnetic card reader/writer. In another example, where transaction device  240  includes a RF transmitter/receiver for communicating with system  200 , read/write device  280  may include a mating transponder configured to receive and transmit issuer-owned data. Read/write device  280  may be configured to select data sets for use by a merchant using any suitable selection technique including but not limited to proprietary commands or command sequences or use of ISO/IEC 7816-4 application selection sequences (e.g., GET command). 
     In one exemplary embodiment, management of data sets is facilitated by annotating the data set with a status indicator (e.g., condition header); (e.g., LOADED, INITIALIZED, READY, BLOCKED, REMOVABLE or DELETED). 
     In this regard, a data set may have a LOADED status when the information related to that data set has been stored in association with financial transaction device  240 , but remains dormant. For example, a credit card account may have been added to financial transaction device  240  that has not yet been activated. In some instances, the loaded data set needs to be further configured before it is ready to be used. For example, the data set may be modified to include a particular branch in a chain of franchise stores, the identification of a user&#39;s  201  primary care physician, or to reflect a user&#39;s  201  selection of a platinum membership status. In another example, a loyalty program may be added in association with a financial transaction device  240 , and the data set marked LOADED. In another example, user  201  may interact with a kiosk  270  or the like to input personal information and configure the loyalty program data set. Once such a data set has been configured, it may be annotated with an INITIALIZED status. 
     The status of a data set may be set as READY when the data set is ready to be utilized. For example, user  201  may enter a secret code to indicate that user  201  is ready to use the data set. In one example, the data set may be marked as READY when that data set is first accessed to perform a transaction. It will be noted that in accordance with other embodiments of the present invention, the status of a data set may be set at READY the moment it is loaded to financial transaction device  240 . Furthermore, it is possible to change the status between READY, LOADED, and INITIALIZED, under appropriate circumstances. Thus, the data sets may be managed through any one or more of these states and in various orders. 
     It may also be desirable to prevent use of a data set and/or the associated functionality for a period of time. Thus, the status indicator may be set to BLOCKED. The setting of the status indicator to BLOCKED may, for example, disable the use of the data set. In one exemplary embodiment, an appropriately configured financial transaction device reader is configured to recognize the BLOCKED status indicator when accessing the data set and to prevent use of that data set example. 
     In addition, for various reasons, user  201  may desire to remove a data set from a transaction card  240 . User  201  may, for example, desire to use the available space on the transaction card  240  for other data sets, or may remove the data set for security reasons. Furthermore, circumstances may arise where the owner of the data set desires to remove the data set from one or more transaction devices  240 , such as when a coupon expires. In these instances, the data set may be marked as REMOVABLE. Under these circumstances, the memory associated with the data set is available to receive information associated with future added data sets, but for the moment retains the old data set. A REMOVABLE data set may again be made READY under various configurations. 
     The REMOVABLE data set may subsequently be removed from financial transaction device  240  and marked DELETED. A DELETED status indicator may be used to indicate that a portion of financial transaction device  240  is available to store one or more data sets. It is noted that data sets may be directly deleted without going through the step of making the data set REMOVABLE. In one example, a data set may be removed from financial transaction device  240  if the security of the account associated with the data set is compromised (e.g., stolen password). Furthermore, as appropriate, the status of data sets may be changed to different states. Under appropriate circumstances one or more of any of the six status indicators LOADED, INITIALIZED, READY, BLOCKED, REMOVABLE, or DELETED or other suitable status indicators may be used to annotate a BLOB or other similar data set. 
     Although the data sets described herein may be managed without status indicators, nevertheless, such status indicators facilitate management of data. For example, regardless of a first data set owner&#39;s ability to interpret the information stored in a data set owned by another party, the first owner may interpret the status indicator to determine whether the data set is LOADED, DELETED, or the like. The determination that a data set is DELETED facilitates the addition of new data sets by independent owners without overwriting other data sets on financial transaction device  240 . In addition, the use of tags or status indicators may facilitate the use of global rules, which may simplify operations and/or commands. Status indicators may also enhance interoperability between data sets. Nevertheless, a data set owner may chose not to use a status indicator even if the opportunity is available. 
     Managing of the data sets (step  120 ) may include one or more of the following exemplary steps: add, update, modify, replace, verify, delete and/or the like. More particularly,  FIG. 3  illustrates a general overview of an exemplary data set management method  300  comprising the steps of: loading a data set (step  310 ), initializing a data set (step  320 ), verifying availability of data set (step  330 ), and deleting a data set (step  340 ). In this manner, a data set may be added to a financial transaction device  240  and utilized until it is deleted. The adding and deleting steps are described in further detail with reference to  FIGS. 4 and 5 . Furthermore, the ability to update, modify, replace and/or delete a data set may be subject to security requirements. 
     In one embodiment, the various processes may include user  201  facilitating the input of information into a data management system to cause the data set to be loaded. The information may be inputted via keypad, magnetic stripe, smart card, electronic pointer, touchpad and/or the like, into a user computer  250 , POS terminal, kiosk  270 , ATM terminal and/or directly into merchant system  220  via a similar terminal or computer associated with merchant server  222 . The information may be transmitted via any network  260  discussed herein to merchant system  220  or issuer systems  230 . In another embodiment, the merchant may enter the information into an issuer system  230  on behalf to user  201 . This may occur, for example, when user  201  and/or issuer system  230  authorizes the management of data sets on financial transaction device  240  over a telephone and the service representative inputs the information. In this embodiment, transaction device  240  may be updated at the next presentment opportunity such as when user  201  attempts to compete a transaction using transaction device  240 . 
     Any suitable procedures may be utilized to determine whether a data set is currently ready for use and available (step  330 ). In one example, when a financial transaction device  240  is presented, the availability of the data set is verified by checking whether the data set has been corrupted or blocked (step  332 ), or deleted (step  333 ). For example, the data set may be checked to determine if the data set has been accessed or altered without permission (“corrupted”) or if the data set exists or has been removed from transaction device  240  (“deleted”). The check may be performed using any suitable protocol or comparing data. If the answer to these questions is no, then the data set is available and ready for use (step  334 ). If the data is corrupted or blocked, subroutines may be used to attempt to retry reading the data (step  336 ). If the data set is marked deleted or removable, subroutines will prevent access to the data set (step  335 ) and remove the data set (step  340 ). For example, a suitable subroutine may place a DELETE “marker” on the data set which prevents the data from being transmitted during completion of a transaction. The data set may then be marked for deletion and deleted from transaction device  240  at the next presentment of the device. In similar manner, where the data set is corrupted, a CORRUPTED marker may be appended to the data set and the data set is prevented from being transmitted during completion of a transaction. The marker may be a header or trailer as discussed herein. 
     Various methods may be used to add a data set to a financial transaction device  240  or to replace a data set on a financial transaction device  240 .  FIG. 4  illustrates an exemplary method of adding a data set to a financial transaction device  240 , including the general steps of presenting financial transaction device  240  (step  410 ), verifying the addition of the data set to financial transaction device  240  (step  420 ), placing the data set in a temporary holding area (step  430 ), and adding the data set (step  440 ). 
     More particularly, user  201  presents financial transaction device  240  (step  41  to a interaction device  280  configured to communicate with transaction device  240 . User  201  may present financial transaction device  240  at a point of purchase or to an interaction device  280  or kiosk  270 . For example, user  201  may wave the RF transaction device  240  in front of a POS machine in a retail store, which is configured to receive data from the device  240 . Alternatively, user  201  may present financial transaction device  240  at a self-service location such as a kiosk  270  in a mall. Moreover, user  201  may present financial transaction device  240  to a peripheral device associated with a personal computer, or the like. 
     User  201  is then given the opportunity to add a data set to transaction device  240 . For example, interaction device  280  may detect the absence of a particular data set on transaction device  240  by searching transaction device  240  data base and comparing the existing data sets to the data set to be added. If the data set to be added is not found on the data base, user  201  may be prompted to confirm the addition of this data set to transaction device  240  (step  420 ). The user may be prompted via an interactive user interface displaying the option to add the data set. In one example, when user  201  presents a financial transaction device  240  to a merchant, the card reader detects the absence of a loyalty data set and provides a message on a display to user  201  or the store clerk indicating that the loyalty data set can be added if desired. User  201  may answer in the negative and complete the purchase using typical transaction methods (step  425 ). Alternatively, if user  201  provides an affirmative response, the algorithm may prepare a data set for communication with financial transaction device  240  (step  430 ). The process may determine whether the data set (or information that may be used to create the data set) exists in some form or on some device other than on financial transaction device  240  (step  432 ). Determining whether a data set exists may involve querying an issuer system  230 , database  282 , or the like. For example, issuer system  230  may compare the data set to other data sets issuer system  230  has assigned to a particular user  201 . If the data set is not assigned to a particular user, then issuer system  230  may determine that the data set is available for adding to transaction device  240 . Determining whether a data set exists may also take place when a store clerk verbally asks (or a screen prompts) user  201  to present another card containing the information. For example, the data set may exist on a movie rental card and stored in magnetic stripe form, bar code, and/or the like. 
     If the data set exists in an accessible form, the data set may be captured (step  436 ). In this example, user  201  may present the movie rental card and the data read from the movie rental card may then be stored in a data set associated with financial transaction device  240 . For example, user  201  may desire to add a shopping loyalty card to the user&#39;s  201  financial transaction device  240 . User  201  may swipe, scan or otherwise present the loyalty card such that the data set from the loyalty card is captured. The system may be further configured such that the merchant, kiosk  270 , or computer system may access an issuer system  230  to obtain information for creating the data set. Thus, if user  201  does not have the movie rental card on the user&#39;s  201  person, the system  230  may prompt the clerk to request identifying/security information and to access the user&#39;s  201  account and therefore facilitate adding a movie rental data set associated with the user&#39;s  201  transaction device  240 . Any other suitable methods of capturing data sets may also be used. 
     If the data set does not exist, a new data set may be created (step  434 ) for inclusion on transaction device  240 . Creation of the data set may, for example, involve filling out an application, providing name and address, creating an account, and/or the like. In either event, the pre-existing or newly created data set is temporarily held in a storage area (e.g., database  282 , local memory or the like) for transfer to transaction device  240  (step  438 ). Additional data sets may be prepared for transmittal to transaction device  240  (step  439 ). 
     In this exemplary embodiment, transaction device  240  is presented again to read/write device  280  (step  442 ). Read/write device  280  is configured to attempt to transfer the data set(s) to transaction device  240  (step  444 ). For example, existing read/write device  280  may be configured with software and/or hardware upgrades to transmit data to transaction device  240 . In one exemplary embodiment, if the data sets were not transferred correctly, the process may try the transfer again. In another exemplary embodiment, data sets are added one at a time or all together. Thus, user  201  may pass a card through a card reader/writer one or more times during the addition process. The transaction may be completed (step  425 ) using the new data set or another selected method of payment. The same steps may be used in a self-service embodiment, however, in one embodiment, no financial transaction takes place along with the addition of data sets. It should also be noted that under appropriate circumstances, user  201  may add data sets at a point of purchase without actually completing a purchase. 
     In various exemplary embodiments, user  201  and/or the owner of the data set may manage the data set (i.e., steps  432 - 439 ) in advance of presenting transaction device  240 . For example, user  201  on user computer  250  may choose to add or delete data sets via a website configured for management of data sets. In another example, an issuer system  230  may add functionality to an account and may desire to update the data set associated with that account. In either example, data sets that have been prepared in advance, may be ready for transmission upon presentment of transaction device  240 . The transmission of the data sets may be transparent to user  201 . For example, user  201  may present transaction device  240  (step  442 ) to complete a purchase and the waiting data sets may automatically be added to the user&#39;s  201  card (step  440 ). 
     Similar steps may be taken to replace or update data sets with new information. For example, user  201  at a point of sale may be informed of an upgrade in functionality associated with an account or other data set. Following similar steps as discussed with reference to  FIG. 4 , the existing data set on transaction device  240  is replaced with a new data set. Moreover, depending on permission rights and/or hierarchies in place, if any, an existing data set may be replaced with an unrelated data set. Other methods of adding and replacing data sets may also be used to manage data sets on a transaction device  240 . 
     Furthermore, data sets may be deleted using any suitable techniques. For example,  FIG. 5  illustrates an exemplary data set deletion method  500 . User  201  presents transaction device  240  at a point of purchase, self-service location, or the like (step  510 ). The POS device may be configured to facilitate user  201  providing input regarding deletion of a data set (step  520 ). For example, the POS device may ask user  201 , via a test screen, whether user  201  desires to manage the data sets on transaction device  240 . Through a series of menus and/or questions, user  201  may identify data sets that user  201  desires to delete. 
     Furthermore, the POS device may be configured to interrogate a database  282  or specific issuer systems  230  to determine whether the deletion of a data set has been requested earlier. If user  201  requests deletion of one or more data sets, the data sets are then identified (step  530 ). It will be noted that step  530  may occur concurrently with step  520  or user  201  may request deletion of a specific account at this step. In other embodiments, accounts may be deleted per predefined rules or policies, and/or the like. Upon presenting transaction device  240  again, the identified data set(s) are removed from transaction device  240  (steps  540  and  550 ). Other methods of deleting data sets may also be used to manage data sets on a transaction device  240 . 
     In an exemplary embodiment, management of the data sets may further include selecting preferences for use of the data sets. For example, user  201  may indicate a desire to use data set A, associated with a low interest rate credit card, as a first option, but to use data set B, associated with a higher interest rate credit card when data set A is not available. In another example, one data set may be used for purchases of gas while another data set may be used for purchasing travel tickets. The consumer data set preferences may be stored on transaction device  240  as a data set. In this example, when the card is presented, all available data sets are read and the card reader device determines which data sets are to be used based in part on the preferences stored on the card, which preferences may be updated from time to time. 
     In one exemplary embodiment of the present invention, transaction device  240  is a RF device configured to transmit and receive information via RF frequency. The RF transaction device  240  may be embodied in any form factor allowing presentment of transaction device  240  for payment. Typical form factors may include a watch, card, FOB, or the like. For ease in understanding, the RF transaction device may be referred to, herein, as a “FOB.” 
     The FOB may be configured to communicate via a radio frequency transponder to the merchant systems or account systems. In yet another embodiment, the FOB may be configured to comprise two or more antennae that are both configured to send and receive information and the FOB may be responsive to different RF frequencies. In this exemplary embodiment, each antenna may be configured to communicate using a particular protocol and/or frequency. Thus, the FOB may be configured to communicate with two or more interaction devices  280  that each communicate with the FOB using different transmission frequencies. For more information on dual antenna fobs, see U.S. patent application Ser. No. 10/192,488, filed Jul. 9, 2002, by inventors Michael J. Berardi, et al., and entitled “System and Method for Payment Using Radio Frequency Identification in Contact and Contactless Transactions” and its progeny, which are hereby incorporated by reference. 
     As noted, the data associated with transaction device  240  may be modified by user  201  and/or by issuer system  230 .  FIGS. 6 and 7  respectively, depict exemplary methods for user  201  and issuer system  230  data management. For example, with respect to user  201  self-management, issuer system  230  may provide user  201  with a transaction device  240  (step  602 ). Transaction device  240  may be provided with pre-stored issuer-owned data, or transaction device  240  may be configured to permit user  201  to add the data at a later date. User  201  may the present transaction device  240  to read/write device  280  for initiating the self-management process (step  604 ). The read/write device  280  may then read the data on transaction device  240 , and provide the data to an interaction device  290  for displaying to user  201  (step  606 ). Alternatively, interaction device  290  may provide user  201  a list of available data to be added to transaction device  240 . 
     User  201  may then be permitted to identify which data user  201  wishes to modify (step  608 ). Identification of the data may include providing the data with a trailer or header indicating the action to be taken (e.g., add, delete, augment, overwrite, etc.). The header and an indicator of the data to be modified may then be provided to issuer system  230  (step  610 ) for verification as to whether such desired modifications are available to user  201  (step  612 ). If the desired modifications are not available, the modifications will not be made and user  201  is notified accordingly (step  614 ). User  201  may then be permitted to identify whether other data is to be modified (step  616 ). If so (step  608 ), interaction device  290  may provide a request for modification to the issuer system  203  (step  610 ) and the verification process is repeated. 
     Alternatively, where issuer system  230  verifies that the modifications may be made (step  612 ), interaction device  290  may make the modifications to the appropriate data on transaction device  240  (step  618 ). Additionally, where the system  200  includes a remote database  282  for storing a mirror image of the data contained on transaction device  240  (step  620 ), interaction device  290 , or issuer system  230 , may facilitate modification of the remote database  282  (step  622 ). User  201  may then be permitted to select other data sets to modify (step  616 ), in similar manner as was described above. 
     In either case, where the modifications are complete, user  201  may then present transaction device  240  to a merchant for use in completing a transaction. 
       FIG. 7  depicts an exemplary method wherein issuer system  230  manages the data contained on transaction device  240 . For example, the issuer may identify on issuer system  230  which data sets are to be modified (step  702 ). The modifications may then be made to the corresponding data set stored on issuer system  230  (step  704 ). Where the system  200  includes a remote database  282 , issuer system  230  may provide the modifications/instructions to database  282  for updating database  282  accordingly (step  706 ). 
     In addition, issuer system  230  may query as to whether issuer system  230  is in possession of transaction device  240  for making the modifications to the data set on transaction device  240  in real-time or substantially real-time (step  708 ). If so, the modifications are made accordingly (step  710 ) and transaction device  240  may then be provided to user  201  for use in completing a transaction using the distinct data sets modified (step  712 ). 
     Where issuer system  230  is not in possession of transaction device  240  at the time the issuer determines that modifications to the data on transaction device  240  are to be made (step  708 ), the modifications may be made on issuer system  230  (step  704 ), and may be placed in queue, for uploading to transaction device  240  when it is next presented to issuer system  230  or to an appropriate read/write device  280  (step  714 ). When transaction device  240  is presented thusly (step  716 ), issuer system  230  may be notified that transaction device  240  is available for modifying, and issuer system  230  may then provide the instructions for modification (e.g., modified data including headers) to the appropriate read/write device  280  for modifying transaction device  240  (step  718 ). Transaction device  240  may then be provided to user  201  for use in completing a transaction (step  712 ). 
     As noted, transaction device  240  may include multiple data sets which correspond to distinct issuer systems  230 , and which may be used to complete a transaction. User  201  may be permitted to choose which data set to use for transaction completion.  FIG. 8  illustrates an exemplary method by which user  201  may choose which of the data sets to use to complete a transaction. For example, user  201  may present transaction device  240  to a merchant system  220  for use in completing a transaction (step  802 ). Merchant system  220  may then read the data stored on transaction device  240  and report to user  201  all distinct data sets which may be used to complete a transaction ( 804 ). User  201  may then select the appropriate data set (step  806 ) and the transaction is completed accordingly (step  808 ). 
     It should be noted that completion of a transaction may be performed under any business as usual standard employed by the merchant and/or issuer system  230 . For example, merchant server  222  may be configured to communicate transaction data to the appropriate issuer system  230 , in real-time or substantially real-time, or by using batch processing at the end of each day. Any suitable means for delivering the transaction data to issuer systems  230  may be used. In one exemplary embodiment of the present invention, the transaction data may be delivered to issuer system  230  via a network  260 . Issuer system  230  may receive the transaction information and process the transaction under issuer defined protocol independent of any other protocol used by other issuers to process a transaction. Issuer system  230  may receive the transaction data and provide the merchant with the appropriate satisfaction for the transaction. 
     In one embodiment, the invention permits the system user  201  to present transaction device  240  containing multiple distinct data sets, and to select a particular data set for transaction completion. User  201  may select a particular data set using any form of secondary identification, such as, for example, a personal identification number (PIN), biometric identifier, voice recognition technology, retinal recognition technology, or the like. The secondary identifier may be provided to the merchant point-of-sale device  275 , kiosk  270 , read/write device  280 , or the like, for transaction completion. In yet another embodiment, the transponder, transponder-reader, and/or transponder-reader system are configured with a biometric security system that may be used for providing biometrics as a secondary form of identification. The biometric security system may include a transponder and a reader communicating with the system. The biometric security system also may include a biometric sensor that detects biometric samples and a device for verifying biometric samples. The biometric security system may be configured with one or more biometric scanners, processors and/or systems. A biometric system may include one or more technologies, or any portion thereof, such as, for example, recognition of a biometric. As used herein, a biometric may include a user&#39;s voice, fingerprint, facial, ear, signature, vascular patterns, DNA sampling, hand geometry, sound, olfactory, keystroke/typing, iris, retinal or any other biometric relating to recognition based upon any body part, function, system, attribute and/or other characteristic, or any portion thereof. For an explanation of systems and methods for providing a secondary form of identification for transaction completion, please see U.S. patent application Ser. No. 10/708,822, titled “SYSTEM FOR BIOMETRIC SECURITY USING A FOB,” filed Mar. 26, 2004; U.S. patent application Ser. No. 10/708,823, titled “METHOD FOR BIOMETRIC SECURITY USING A TRANSPONDER,” filed Mar. 26, 2004; U.S. patent application Ser. No. 10/708,824, titled “Method for Biometric Security using a Transponder-Reader,” filed Mar. 26, 2004; all of which are herein incorporated by reference. 
     To facilitate understanding of the invention, the multiple data sets contained on transaction device  240  are discussed with reference to distinct transaction account numbers associated with corresponding transaction accounts maintained by distinct issuer systems  230 . Each one of the multiple transaction account numbers, or a plurality of the transaction account numbers, may be correlated to a single issuer system  230 . However, for ease in understanding, the invention is discussed with reference to a first data set correlating to a first issuer system  230 , and a second data set correlated to a second issuer system  230 . 
     In one typical example, the transaction numbers (e.g., data set) are added to transaction device  240  as discussed above. As previously noted, each transaction number is ordinarily stored on transaction device  240  distinct from the other transaction numbers stored thereon. The transaction account numbers may include a routing number, transit number, bank identification number (BIN), or the like, which is used to identify issuer system  230  that maintains the transaction account corresponding to the transaction account number. The transaction account number may additionally include a user account number, which is used by issuer system  230  to identify the transaction account to be used to complete the transaction. In one exemplary embodiment, issuer system  230  stores the user account number on the issuer system database correlative to the transaction account in such manner that issuer system  230  may retrieve the transaction account for transaction completion by, for example, referencing the user account number. 
     In yet another exemplary embodiment of the invention, a system is provided whereby the user is permitted to select one or more funding sources for use in satisfying a merchant request. The user may switch funding sources manually by, for example, contacting the fob account provider and indicating that. a particular funding source is desired. The user may contact the provider or any other third party that can facilitate changing the funding source via any means known in the art such as, for example, telephone, voice response, internet, cell phone, modem, email, webpage submission and/or any other electronic, optical or digital methods for communication. In this way, the user is permitted to change funding sources from a primary funding source to a secondary funding source. In this context, a “primary” funding source may be the funding source which the account provider may primarily use to retrieve funds and satisfy all or a portion of a merchant transaction request. A “secondary” funding source may be any alternate funding source from which value may be retrieved for satisfying all or a portion of a transaction request. It should be noted that primary and secondary are used herein to illustrate that more than one funding source may be chosen by the user for association with the fob, and that any number of sources may be selected. 
     In addition, the fob user may provide the fob account provider with a funding protocol for use in determining which funding source to use. For example, the fob user may designate that for a particular merchant, type of merchant or type of transaction, a selected funding source is to be automatically used. In this way, the fob user is assured that particular transactions will be satisfied (e.g., completed) using an identified funding source and/or the fob account provider may send all similar transactions to an identified funding source, thereby facilitating tracking of the similar transactions. 
     The funding protocol may additionally include guidelines for automatically changing to a secondary funding source when the requested transaction amount meets or exceeds the available value of the primary funding source. That is, the funding protocol indicates to the account provider that the funds for satisfying the merchant request should be retrieved from a secondary funding source when the value in the primary funding source is insufficient for completing the transaction. Alternatively, the funding protocol may indicate to the account provider that the transaction should be completed using value from both the primary and secondary funding sources. The amount retrieved from the primary and secondary funding sources may be based on a calculated formula defined by the fob user or fob issuer. In a typical example, where a particular transaction or merchant is identified by the account provider (e.g., by use of the markers described above), the account provider may seek to retrieve a percentage of the value needed from the primary funding source with the balance of the transaction retrieved from the secondary funding source. Alternatively, the value in the primary funding source may be depleted prior to retrieving the balance of the requested transaction from the secondary funding source. 
     In accordance with another exemplary embodiment of the invention, the fob user is provided limited access to a fob user data file maintained on an issuer system for managing the fob usage and fob user information. The fob user may access the fob user data file to change, for example, demographic information (e.g., fob user address, phone number, email address, etc.), the funding source (e.g., credit account, charge account, rewards account, barter account, etc.) associated with the fob, view the transaction history, etc. In addition, the fob user may be permitted to load or reload the account or alter automatic reload parameters (e.g., amount to reload, period for reloading, etc.).The fob user may access the fob user data file via the network. In particular, the network may be in communication with an issuer system and may be provided limited access to an issuer server for managing the fob. The issuer server may be in communication with an issuer system database which stores the information to be managed relative to the user fob user data file. The changes made to the fob user data file by the fob user may be made in real-time, after a brief delay, or after an extended delay. In one instance, changes may be stored in a batch changes file on the issuer database for later batch processing. 
     The fob user may be provided limited access to all or a portion of the issuer system to define a funding protocol for use in satisfying a transaction request. The fob user may be permitted access to all or a portion of the issuer database for defining the protocol for determining the funding source to be used for a particular transaction. The user may contact the provider or any other third party that can facilitate changing the funding source via any means known in the art such as, for example, telephone, voice response, internet, cell phone, modem, email, webpage submission and/or any other electronic, optical or digital methods for communication. The fob user may be permitted to select one or more particular funding source for use with the fob depending on the conditions of the transaction request. For example, the funding protocol may indicate to the issuer (e.g., account provider) server that a particular funding source is to be used for an identified class of transactions or for a particular merchant. The funding protocol may take into account the requirements as determined by a particular funding source, or the relative risk level (e.g., high risk, medium risk, low risk, or the like) in determining which funding source or combination of sources are to be used to satisfy a transaction request. Alternatively, the funding protocol may indicate that a combination of sources may be used to satisfy a transaction request. In this arrangement, the primary, secondary, tertiary funding sources may have similar descriptions as any one of funding sources described above. In this regard, the database may include sub-data files corresponding to one or more funding sources, where the sub-data files may funded from value received from the multiple funding sources. For example, a primary sub-data file may include value received from a primary funding source and a secondary sub-data file may include value received from a secondary funding source. Alternatively, the invention may include multiple databases (not shown) for uniquely storing the funds received from, for example, a primary and secondary funding source. Further, although the invention is described with respect to primary and secondary funding source, it is to be understood that any number n of funding sources for providing value to n sub-data files is contemplated, and that the terms primary and secondary are used herein by way of example. In one exemplary embodiment, where multiple funding sources are used to satisfy a transaction, the invention may require authentication from one or more of the funding sources that the transaction is authorized. Thus, an authorization may take place upon presentment of the fob and when the value is retrieved from a funding source (or multiple funding sources) to complete a transaction. 
       FIG. 19  (FIG. 14 of U.S. Pat. No. 7,249,112) depicts an exemplary funding protocol  1900  which may be identified by the fob user. As shown, the funding protocol may be initiated when the fob is presented for payment (step  1902 ). The fob may be presented to a RFID reader. The RFID reader may provide an account number to the merchant system  220  and the merchant system  220  may seek satisfaction of a transaction request from an issuer system  230  (step  1904 ). 
     The fob user may indicate via the database that a particular merchant or class of transactions is to be flagged or marked for satisfaction using a particular funding source. The merchant or class of transactions may be flagged in similar manner as is discussed above. That is, the fob user defined protocol may provide for a particular merchant, type of merchant, or class of transactions to be marked and identified by the account provider for specified treatment, as described more fully below. 
     If a merchant (or transaction) is flagged, the issuer server may switch the funding source associated with the fob from a primary funding source to a secondary funding source (step 1408 of &#39;480). In this regard, the server may retrieve value from the sub-data file associated with the secondary funding source. The server may additionally determine whether the spending limit for the secondary funding source has been reached or exceeded (step 1410 of &#39;480). If the spending limit for the secondary funding sources is not exceeded, then the server may retrieve the appropriate value for satisfying a transaction request from the secondary funding source (step 1414 of &#39;480). The funds may then be transferred to the merchant system under any business as usual standard (step 1416 of &#39;480), completing the merchant&#39;s transaction request. 
     In some instances, the funding may be switched from the primary funding source to the secondary funding source (step 1408 of &#39;480), and the spending limit for the secondary funding source is reached or exceeded (step 1410 of &#39;480). In which case, the issuer server may determine whether the fob user has indicated that the merchant transaction request is to be satisfied using funds retrieved from a combination of funds received from the sub-data files associated with the primary and secondary funding sources (step 1412 of &#39;480). The combination of funds may be retrieved using any formula determined by the fob user or fob account issuer (step 1430 of &#39;480), and the funds may be transferred to the merchant system, satisfying the merchant transaction request. 
     In another embodiment, the server may determine if a switch is to be made to yet a tertiary funding source (step 1432 of &#39;480). In which case, the server may determine if the spending limit for the tertiary funding source has been reached or exceeded (step 1436 of &#39;480). If the funds are exceeded, the merchant request may be terminated and a transaction denied” message may be forwarded to the merchant system (step 1434 of &#39;480). 
     Where a merchant transaction request is not flagged (step 1406 of &#39;480), in one embodiment, the issuer server may not switch from a primary funding source to a secondary funding source. Instead, the issuer server may determine whether the spending limit on the primary source is reached or exceeded (step 1420 of &#39;480). If the spending limit on the primary source is not exceeded, then the appropriate funds for satisfying the merchant request may be retrieved from the primary funding source sub-data file (step 1422 of &#39;480) and transferred to the merchant system under business as usual standards (step 1424 of &#39;480). 
     Contrarily, where the spending limit on the primary funding source is reached or exceeded (step 1420 of &#39;480), in one embodiment, the issuer server may determine whether to combine funds retrieved from sub-data files associated with the primary funding source and a secondary funding source to satisfy the merchant transaction request (step 1426 of &#39;480). If the primary and secondary funding sources are to be combined, funds may be retrieved from the multiple funding sub-data files using any formula as determined by the fob user or fob account issuer (step 1430 of &#39;480). The funds may then be transferred to the merchant system under business as usual standards (step 1424 of &#39;480). 
     If the funds from the primary and secondary funding sources are not to be combined, the server may determine whether to switch from a primary funding source to a secondary funding source (step 1428 of &#39;480). If no switch is to be made and the transaction request exceeds the primary funding source limit, then the transaction request may be terminated and a “transaction denied” may be provided to the merchant under business as usual standards (step 1434 of &#39;480). 
     On the other hand, should the funding source be switched from a primary funding source to a secondary funding source, the server may determine whether the spending limit for the secondary funding source is reached or exceeded (step 1440 of &#39;480). If the spending limit for the secondary funding source is reached or exceeded, then the transaction may be terminated and a “transaction denied” message may be provided to the merchant system under business as usual standards (step 1434 of &#39;480). If the spending limit for the secondary funding source is not reached or exceeded, the appropriate funds for satisfying the transaction request may be retrieved from the sub-data file associated with the secondary funding source (step 1442 of &#39;480) and transferred to the merchant system (step 1424 of &#39;480), satisfying the transaction request. 
     The transaction account may be maintained on issuer system  230  in an issuer system database (not shown). In conventional methods for transaction completion, when a system user  201  requests completion of a transaction, user  201  may present transaction device  240  to a merchant system POS  275 . Transaction device  240  may provide the transaction account number to merchant system  220 , and the merchant system may forward a request for transaction authorization (e.g., merchant transaction request) to issuer system  230 . Merchant system  220  provides the merchant transaction request over a network (e.g., network  260 ) to issuer system  230  corresponding to the routing number included in the transaction account number. When issuer system  230  receives a transaction request from a merchant system  220 , issuer system  230  ordinarily retrieves the transaction account corresponding to the user account number from the issuer system database, and processes the transaction request under the issuer system&#39;s business as usual standards. 
     In some conventional transaction processing methods, issuer system  230  may require user  201  to provide a secondary form of identification prior to authorizing a transaction. For example, issuer system  230  may receive a transaction request from a merchant system  220 , and return instructions to merchant system  220  to prompt user  201  to provide a PIN. Merchant system POS  275  may require user  201  to provide the PIN prior to further processing the transaction request. User  201  may provide the PIN to merchant system  220  using, for example, a conventional keypad as is commonly used in the industry for such purposes. Once the PIN is provided to merchant system  220 , merchant system  220  may provide the PIN and any other information used to identify user  201  to issuer system  230  for PIN verification. 
     The conventional PIN verification process performed by issuer system  230  may include comparing the PIN to a PIN stored in the issuer system database with reference to the user&#39;s account number. If the PIN provided by user  201  matches the PIN stored correlative to the user account number on issuer system  230 , then issuer system  230  may authorize completion of the merchant&#39;s transaction request. Otherwise, issuer system  230  may deny transaction authorization. 
     Notably, issuer system  230  may use any issuer defined protocol to compare the provided PIN to the PIN stored in the issuer database. For example, the PIN may be manipulated by issuer system  230  using any suitable algorithm or any additional information obtained from merchant system  220 , user  201 , or the issuer system database, and the results of the manipulation may be analyzed, or verified against any other information stored on the issuer system database. As such, the method by which issuer system  230  verifies the PIN is not limited. Any issuer system  230  defined method may be suitably employed. 
     In other conventional transaction processing systems, the PIN may be verified by merchant system  220 . Merchant system  220  may receive the transaction account number from transaction device  240  upon initiation of a transaction by user  201 . Merchant system  220  may receive the transaction account number and recognize that user  201  may need to provide a PIN to merchant system  220  for verification prior to completion of the transaction. Merchant system  220  may provide user  201  with a request for the PIN, or with notification that a PIN is required to complete the transaction. User  201  may then provide the PIN to merchant system  220  using, for example, a conventional keypad. Merchant system  220  may receive the PIN from user  201  and provide the PIN to transaction device  240 . According to this PIN verification method, the transaction device database includes a user PIN against which transaction device  240  may compare the PIN provided by user  201  via merchant system  220 . If the PIN provided by user  201  matches the PIN stored in the transaction device database, the merchant system may then forward the merchant&#39;s transaction request to issuer system  230  for completion. Otherwise, merchant system  220  may deny the transaction. 
       FIG. 9  illustrates a block diagram of an exemplary transaction device  240  in accordance with the invention. Transaction device  240  may be a RFID transaction device  240  which may be presented by the user to facilitate an exchange of funds or points, etc., for receipt of goods or services. Transaction device  240  discussed herein may also be a “pervasive computing device,” which may include a traditionally non-computerized device that is embedded with a computing unit. Examples can include watches, Internet enabled kitchen appliances, restaurant tables embedded with RF readers, wallets or purses with imbedded transponders, etc. 
     Transaction device  240  may include an antenna  902  for receiving an interrogation signal from RFID reader  265  via antenna  1002  (or alternatively, via external antenna  1026 ). Transaction device antenna  902  may be in communication with a transponder  914 . In one exemplary embodiment, transponder  914  may be a 13.56 MHz transponder compliant with the ISO/IEC 14443 standard, and antenna  902  may be of the 13 MHz variety. The transponder  914  may be in communication with a transponder compatible modulator/demodulator  906  configured to receive the signal from transponder  914  and configured to modulate the signal into a format readable by any later connected circuitry. Further, modulator/demodulator  906  may be configured to format (e.g., demodulate) a signal received from the later connected circuitry in a format compatible with transponder  914  for transmitting to RFID reader  265  via antenna  902 . For example, where transponder  914  is of the 13.56 MHz variety, modulator/demodulator  906  may be ISO/IEC 14443-2 compliant. 
     Modulator/demodulator  906  may be coupled to a protocol/sequence controller  908  for facilitating control of the authentication of the signal provided by RFID reader  265 , and for facilitating control of the sending of transaction device  240  account number. In this regard, protocol/sequence controller  908  may be any suitable digital or logic driven circuitry capable of facilitating determination of the sequence of operation for transaction device  240  inner-circuitry. For example, protocol/sequence controller  908  may be configured to determine whether the signal provided by the RFID reader  265  is authenticated, and thereby providing to the RFID reader  265  the account number stored on transaction device  240 . 
     Protocol/sequence controller  908  may be further in communication with authentication circuitry  910  for facilitating authentication of the signal provided by RFID reader  265 . Authentication circuitry  910  may be further in communication with a non-volatile secure memory database  912 . Secure memory database  912  may be any suitable elementary file system such as that defined by ISO/IEC 7816-4 or any other elementary file system allowing a lookup of data to be interpreted by the application on the chip. Database  912  may be any type of database or file system such as simple flat file or a hierarchical file structure such as defined by ISO/IEC 7816 standard. Database  912  may be organized in any suitable manner, including as data tables or lookup tables. Association of certain data may be accomplished through any data association technique known and practiced in the art. For example, the association may be accomplished either manually or automatically. Automatic association techniques may include, for example, a database search, a database merge, GREP, AGREP, SQL, and/or the like. The association step may be accomplished by a database merge function, for example, using a “key field” in each of the manufacturer and retailer data tables. A “key field” partitions the database according to the high-level class of objects defined by the key field. For example, a certain class may be designated as a key field in both the first data table and the second data table, and the two data tables may then be merged on the basis of the class data in the key field. In this embodiment, the data corresponding to the key field in each of the merged data tables is in an exemplary embodiment the same. However, data tables having similar, though not identical, data in the key fields may also be merged by using AGREP, for example. 
     The data may be used by protocol/sequence controller  908  for data analysis and used for management and control purposes, as well as security purposes. Authentication circuitry  910  may authenticate the signal provided by RFID reader  265  by association of the RFID signal to authentication keys stored on database  912 . Encryption circuitry may use keys stored on database  912  to perform encryption and/or decryption of signals sent to or from the RFID reader  265 . 
     In addition, protocol/sequence controller  908  may be in communication with a database  916  for storing at least transaction device  240  account data, and a unique transaction device  240  identification code. Protocol/sequence controller  908  may be configured to retrieve the account number from database  916  as desired. Database  916  may be of the same configuration as database  912  described above. The transaction device account data and/or unique transaction device identification code stored on database  916  may be encrypted prior to storage. Thus, where protocol/sequence controller  908  retrieves the account data, and or unique transaction device identification code from database  916 , the account number may be encrypted when being provided to RFID reader  265 . Further, the data stored on database  916  may include, for example, an unencrypted unique transaction device  240  identification code, a user identification, Track 1 and 2 data, as well as specific application applets. 
       FIG. 10  illustrates an exemplary block diagram of a RFID reader  265  in accordance with an exemplary embodiment. RFID reader  265  includes, for example, an antenna  1002  coupled to a RF module  1022 , which is further coupled to a control module 
     In addition, RFID reader  265  may include an antenna  1026  positioned remotely from the RFID reader  265  and coupled to RFID reader  265  via a suitable cable  1028 , or other wire or wireless connection. 
     RF module  1022  and antenna  1002  may be suitably configured to facilitate communication with transaction device  240 . Where transaction device  240  is formatted to receive a signal at a particular RF frequency, RF module  1022  may be configured to provide an interrogation signal at that same frequency. For example, in one exemplary embodiment, transaction device  240  may be configured to respond to an interrogation signal of about 13.56 MHz. In this case, RFID antenna  1002  may be 13 MHz and may be configured to transmit an interrogation signal of about 13.56 MHz. 
     Further, protocol/sequence controller  1014  may include an optional feedback function for notifying the user of the status of a particular transaction. For example, the optional feedback may be in the form of an LED, LED screen and/or other visual display which is configured to light up or display a static, scrolling, flashing and/or other message and/or signal to inform transaction device  240  user or any other third party that the transaction is initiated (e.g., transaction device is being interrogated), the transaction device is valid (e.g., transaction device is authenticated), transaction is being processed, (e.g., transaction device account number is being read by RFID reader) and/or the transaction is accepted or denied (e.g., transaction approved or disapproved). Such an optional feedback may or may not be accompanied by an audible indicator (or may present the audible indicator singly) for informing transaction device  240  user of the transaction status. The audible feedback may be a simple tone, multiple tones, musical indicator, and/or voice indicator configured to signify when transaction device  240  is being interrogated, the transaction status, or the like. 
     RFID antenna  1002  may be in communication with a transponder  1006  for transmitting an interrogation signal and receiving at least one of an authentication request signal and/or an account data from transaction device  240 . Transponder  1006  may be of similar description as transponder  914  of  FIG. 9 . In particular, transponder  1006  may be configured to send and/or receive RF signals in a format compatible with antenna  902  in similar manner as was described with respect to transaction device transponder  914 . For example, where transponder  1006  is 13.56 MHz RF rated antenna  902  may be 13.56 MHz compatible. Similarly, where transponder  1006  is ISO/IEC 14443 rated, antenna  1002  may be ISO/IEC 14443 compatible. 
     RF module  1022  may include, for example, transponder  1006  in communication with authentication circuitry  1008  which may be in communication with a secure database  1010 . Authentication circuitry  1008  and database  1010  may be of similar description and operation as described with respect to authentication circuitry  910  and secure memory database  912  of  FIG. 9 . For example, database  1010  may store data corresponding to transaction device  240  which are authorized to transact business over system  200 . Database  1010  may additionally store RFID reader  265  identifying information for providing to transaction device  240  for use in authenticating whether RFID reader  265  is authorized to be provided the transaction device account number stored on transaction device database  916 . 
     Authentication circuitry  1008  may be of similar description and operation as authentication circuitry  910 . That is, authentication circuitry  1008  may be configured to authenticate the signal provided by transaction device  240  in similar manner that authentication circuitry  910  may be configured to authenticate the signal provided by RFID reader  265 . In one exemplary embodiment, transaction device  240  and RFID reader  265  engage in mutual authentication. In this context, “mutual authentication” may mean that operation of the system  200  may not take place until transaction device  240  authenticates the signal from RFID reader  265 , and RFID reader  265  authenticates the signal from transaction device  240 . For a detailed explanation of a suitable transaction processing method and mutual authentication process for use with the invention, see, for example, U.S. patent application Ser. No. 10/192,488, titled “SYSTEM AND METHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed Jul. 9, 2002, and U.S. patent application Ser. No. 10/340,352, titled “System and Method for Incenting Payment Using Radio Frequency Identification In Contact and Contactless Transactions,” filed Jan. 10, 2003, both incorporated herein by reference. 
     Transaction device  240  may provide reader  265  with transaction device data for use in authenticating a transaction request at issuer system  230 . For example, transaction device  240  may include a counter or random number generator (not shown) which may be provided to the issuer system for use in transaction device  240 , reader  265 , or transaction verification. The issuer system  240  may receive the counter or random number for use in determining whether to authorize the transaction. Suitable methods for using a counter or random number generator are disclosed in, for example, U.S. patent application Ser. No. 10/708,547, titled “SYSTEM AND METHOD FOR SECURING RF TRANSACTIONS USING A RADIO FREQUENCY IDENTIFICATION DEVICE INCLUDING A RANDOM NUMBER GENERATOR,” filed Mar. 10, 2004, and U.S. patent application Ser. No. 10/708,545, titled “SYSTEM AND METHOD FOR SECURING RF TRANSACTIONS USING A RADIO FREQUENCY IDENTIFICATION DEVICE INCLUDING A TRANSACTIONS COUNTER,” filed Mar. 10, 2004, both incorporated herein by reference. 
     In accordance with the present invention, transaction device  240  may include multiple transaction account numbers stored on RFID transaction device database  912  (or secure memory  916 ). Each transaction account numbers stored thereon may be associated with a distinct PIN for use by merchant system  220  or issuer system  230  in verifying or authorizing a transaction. For example, a first transaction account number (e.g., first data set) may be associated with a first PIN on issuer system  230  or on the transaction device database  912 ,  916 , and a second transaction account number (e.g., second data set) may be associated with a second PIN on issuer system  230  or on the transaction device database  912 ,  916 , where the first transaction account number is distinct and different from the second transaction account number and the first PIN is distinct and different from the second PIN. 
     Upon presentment of transaction device  240  to reader  265  for transaction completion, transaction device  240  may provide reader  265  with information relative to the multiple transaction account numbers contained in the transaction device database  912 ,  916 . Reader  265  may then inform user  201  that multiple transaction accounts are available on the transaction device database  912 ,  916  for use in transaction completion. Reader  265  may notify user  201  audibly, for example, by reciting specific information relative to each transaction account number. For example, reader  265  may audibly notify user  201  that a particular transaction account number is one issued by a particular issuer system  230 . Reader  265  may request that user  201  select at least one of the transaction accounts contained on the database  912 ,  916  for use in transaction completion. 
     In another exemplary embodiment, reader  265  (or merchant system  220 ) may be configured to provide to user  201  a listing of the multiple transaction accounts contained on database  912 . In this exemplary embodiment, reader  265  (or merchant system  220 ) may be equipped with a display screen (not shown) for displaying the multiple accounts to user  201 .  FIG. 11  depicts an exemplary screen shot  1100  of a display screen that may be presented to user  201  for transaction account selection. Screen shot  1100  may include a listing of transaction account numbers  1102 - 1108 , which may correspond to the transaction account numbers (e.g., data sets) stored on the transaction device database  912 , 916 . For example, transaction account number  1102  corresponds to a first transaction account number (e.g., “American Express Card ending in 4235”); transaction account number  1104  corresponds to a second transaction account number (e.g., “Federal Bank VISA Card ending in 3637”); transaction account number  1106  corresponds to a third transaction account number (e.g., “Johnson Department Store Card ending in 1234”); and transaction account number  1108  corresponds to a fourth transaction account number (e.g., “Mother Bell Phone Card ending in 0012”). 
     User  201  may then be permitted to select which one of the transaction account numbers to use in completing the transaction. For example, user  201  may be prompted by a message  1112  to provide a PIN corresponding to the transaction account number selected. The PIN may be provided to merchant system  220  via a keypad, touch screen, or the like. The PIN may then be verified in accordance with any method described above. If the PIN is verified, the transaction may be completed under business as usual standards. Otherwise, completion of the transaction is denied. 
     In another exemplary embodiment, user  201  may be permitted to select a transaction account number from the screen. User  201  may be permitted to select a particular transaction account number by providing transaction account identifying information to merchant system  220 . For example, where the screen is a touch sensitive screen, user  201  may select a particular transaction account by touching the appropriate transaction account on the screen  1100 , or by providing transaction account identifying information to the screen in accordance with the message  1110  provided by to user  201 . In some instances, user  201  may select a particular transaction account by providing merchant system  220  with a PIN which correlates with the selected transaction account. As such, issuer system  230  or merchant system  220  may verify whether a PIN is required to complete the transaction using the transaction number selected. The PIN may be verified under any merchant system  220  or issuer system  230  defined protocols. If a PIN is required, then user  201  may be prompted to provide the required PIN to the keypad prior to completing the transaction. If the system user does not provide a PIN, or alternatively provides an incorrect PIN, merchant system  220  or issuer system  230  may terminate the transaction request. 
     In yet another embodiment of the invention, user  201  may be permitted to select more than one of the transaction account numbers contained on the transaction device database for transaction completion. User  201  may be permitted to allocate portions of the transaction request to multiple transaction account numbers for transaction satisfaction. For example,  FIG. 12  depicts a second screen shot  1200  that reader  265  may provide to user  201  subsequent to the selection of a particular transaction account number. For example, user  201  may elect to use a first transaction account number  1102  for full satisfaction of the transaction request. The screen shot  1200  may provide a message  1202  prompting user  201  to identify whether the selected account is to be used for full satisfaction of the transaction request. If so, then merchant system  220  may process the transaction request under business as usual standards using the first transaction account number  1102 . Merchant system  220  may provide the first transaction account number  1102  to issuer system  230  for verification and transaction authorization. 
     If user  201  elects to allocate portions of the transaction request to multiple transaction account numbers for transaction satisfaction, reader  265  or merchant system  220  may permit user  201  to identify the portion of the transaction request to allocate to a particular transaction account number. For example, user  201  may desire to allocate 35% of the transaction to a first transaction account number  1102  and 65% to a second transaction account number. In this instance, at the screen shot  1200 , user  201  may select a first transaction account number, and indicate that the first transaction account number is not to be used for full satisfaction of the transaction request. Reader  265  or merchant system  220  may then provide user  201  with a screen shot permitting user  201  to indicate which portion of the transaction request to allocate to the first transaction number. User  201  may indicate which portion to allocate by, for example, providing the key pad with information identifying the allocated portion. In the example illustrated in  FIG. 13 , user  201  is prompted by message  1302  to provide what percentage of the transaction request is to be allocated to a first transaction account number  1102 . As shown, screen shot  1300  indicates that 35% of the transaction is to be allocated to the first transaction account number  1102 . Once user  201  indicates the portion, reader  265  or merchant system  220  may return user  201  to a subsequent listing of the available transaction account numbers for use in completing the transaction. The subsequent listing of available transaction account numbers may include all of the transaction account numbers contained on the transaction device database  912 ,  916 , or only those transaction account numbers not yet selected by user  201 . Alternatively, the subsequent listing may include notification of which transaction account number user  201  has previously selected. As shown in  FIG. 14 , a screen shot  1400  may include the subsequent listing which may additionally include the relevant information pertaining to the allocation made to the first transaction account number  1102  by user  201 . For example, screen shot  1400  may include the selected first transaction account number  1102  and the corresponding amount  1402  allocated thereto. User  201  may be permitted to select additional transaction account numbers from the subsequent listing for allocation of portions of the transaction request, or for use in satisfying the balance of the transaction request. For example, user  201  may be provided a message  1404  requiring user  201  to select additional accounts for use in transaction completion. User  201  may be required to select additional transaction account numbers from the subsequent list until the totality of the transaction is satisfied. User  201  may be provided screen shots shown in  FIGS. 11-14  and the process repeated until the appropriate portions, or all portions, of the transaction request are fully satisfied. 
       FIG. 15  illustrates an exemplary method for selecting from amongst the multiple transaction account numbers contained on the transaction device database  912 ,  916 . The method begins with user  201  presenting the multiple accounts transaction device  240  for completion of a transaction (step  1502 ). In presenting transaction device  240 , user  201  may place the transaction device within the interrogation zone of a RFID reader  265 . Reader  265  interrogates the transaction device and transaction device  240  and reader  265  may engage in mutual authentication (step  1504 ). Once transaction device  240  and reader  265  successfully mutually authenticate, transaction device  240  is provides reader  265  with transaction account information contained in the transaction device database  912 ,  916 . For detailed description of a suitable interrogation and mutual authentication process for use with the invention, please refer to U.S. patent application Ser. No. 10/192,488, incorporated by reference above. 
     Upon successful interrogation and authentication, transaction device  240  provides reader  265  with the multiple transaction account numbers stored on the transaction device database  912 ,  916  (step  1506 ). In one example, the transaction device protocol/sequence controller  908  sends a signal to database  912 ,  916  and the database  912 ,  916  provides the multiple transaction account numbers to the protocol/sequence controller  908 . The protocol sequence controller  908  may receive the multiple transaction account numbers and provides the multiple transaction account numbers to modulator/demodulator  906 , which in turn provides the multiple transaction account numbers to transaction device transponder  914 . Transponder  914  may provide the multiple transaction account numbers to transaction device antenna  902 , and antenna  902  may provide the multiple transaction account numbers to reader  265 , via reader antenna  1002  (or optional external antenna  1026 ). 
     Reader  265  may receive the transaction account numbers (step  1508 ) and provide notice to user  201  that multiple transaction account numbers are present on transaction device  240  that are available for use in completing a transaction request (step  1510 ). Reader  265  may receive the transaction account numbers at reader transponder  1006  via reader antenna  1002 . Transponder  1006  may additionally provide the multiple account numbers to a reader or merchant display screen (not shown) for use in displaying the transaction account numbers to user  201 . For example, the reader protocol sequence controller  1014  may provide a signal to the reader communications interface  1012 , which commands the interface  1012  to receive the multiple transaction account numbers and provide the multiple transaction account numbers to the display screen. 
     Reader  265  may then prompt user  201  to select at least one of the multiple transaction account numbers for use in transaction completion (step  1516 ). For example, the reader or merchant display screen may provide user  201  with a screen shot, such as, for example, screen shot  1100  shown in  FIG. 11 . The screen shot  1100  may include a listing of the multiple transaction account numbers contained on the transaction device database  912 ,  916 , which are available for use in transaction completion. The screen shot  1100  may be configured to permit user  201  to select one of the transaction account numbers, and the screen may provide the transaction account number to reader  265  or merchant system  220  for processing (step  1518 ). 
     In some instances, the account issuer  230  that provides the transaction account number to user  201  may require user  201  to provide a PIN prior to permitting use of the transaction account number for transaction completion (step  1520 ). In this case, display screen may be configured to prompt user  201  to provide the appropriate PIN for verification by reader  265 , merchant system  220 , or issuer system  230 , in any manner discussed above (step  1522 ). User  201  may provide the PIN (step  1   524 ) and the PIN may be verified under merchant system  220  or issuer system  230  defined verification protocol (step  1526 ). If the PIN is not verified (step  1526 ), then merchant system  220  may terminate the transaction request (step  1528 ). 
     In some instances, issuer system  230  corresponding to the selected transaction account number may not require a PIN for a particular transaction account number to be used for transaction completion (step  1520 ). In which case, the transaction account number is processed and the transaction completed under the merchant system&#39;s business as usual protocol. For example, merchant system  220  may provide a request for satisfaction of a transaction request to issuer system  230 , and issuer system  230  may evaluate the transaction request for transaction completion. 
     Alternatively, as illustrated in  FIG. 12 , the display screen may be configured to permit user  201  to select more than one of the multiple transaction account numbers contained on transaction device  240  for transaction completion. For example, where transaction device  240  includes multiple transaction account numbers, user  201  may allocate portions of the transaction request to the transaction account numbers for satisfaction in accordance with that portion. User  201  may elect to fully allocate the whole of the transaction request to a single transaction account number, or to separate the transaction request amongst multiple transaction account numbers (step  1530 ). If user  201  elects to allocate the transaction to only one of the transaction account numbers, the transaction request in process under the merchant system&#39;s business as usual standards (step  1532 ). For example, merchant system  220  receives the transaction account number and provides the transaction account number to the corresponding issuer system  230  by referencing issuer system  230  routing number included in the selected transaction account number. Typical methods of routing a transaction request to an issuer system  230  based on a routing number are well known and will not be discussed herein for brevity. 
     In another exemplary embodiment, user  201  may elect to allocate only a portion of the transaction request to a selected transaction account number (step  1530 ). In which case, the display screen may be configured to prompt user  201  to identify the portion of the transaction request to be allocated to the selected transaction account number. For example, display screen  1300 , shown in  FIG. 13 , illustrates a typical prompt for use in identifying which portion of a transaction to allocate to a particular transaction account number. User  201  may identify a portion of the transaction request to be allocated (step  1536 ) and merchant system  220  may process the allocated portion of the transaction request in accordance with the transaction account number selected and the merchant system business as usual standards, as discussed above (step  1538 ). That is, the portion of the transaction request to be allocated to the transaction account number is forwarded to issuer system  230  corresponding to the routing number contained in the selected transaction account number. 
     User  201  may elect to satisfy the balance of the transaction request using one or more of the remaining transaction account numbers contained on the multiple transaction account device database  912 ,  916 . In which case, reader  265  and the merchant system may provide user  201  with a subsequent list of transaction account numbers available for transaction completion and user  201  may select one or more of the transaction account numbers to satisfy the balance of the transaction request. In which case, steps  1516 - 1538  may be repeated until the transaction is wholly satisfied. 
     It should be appreciated that the particular implementations shown and described herein are illustrative of the invention and its best mode and are not intended to otherwise limit the scope of the present invention in any way. Indeed, for the sake of brevity, conventional data networking, application development and other functional aspects of the systems (and components of the individual operating components of the systems) may not be described in detail herein. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical data set management system. 
     As may be appreciated by one of ordinary skill in the art, the present invention may be embodied as a method, a data processing system, a device for data processing, and/or a computer program product. Accordingly, the present invention may take the form of an entirely software embodiment, an entirely hardware embodiment, or an embodiment combining aspects of both software and hardware. Furthermore, the present invention may take the form of a computer program product on a computer-readable storage medium having computer-readable program code means embodied in the storage medium. Any suitable computer-readable storage medium may be utilized, including hard disks, CD-ROM, optical storage devices, magnetic storage devices, and/or the like. 
     These computer program instructions 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 instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart block or blocks. The computer program instructions 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 instructions which execute on the computer or other programmable apparatus include steps for implementing the functions specified in the flowchart block or blocks. 
     It should be noted that although the present invention is discussed with respect to Internet Service Providers, and systems and networks which may communicate via a leased line (T1, D3, TCP/IP etc.), the invention is not so limited. The present invention contemplates conventional protocol, networks and systems which support a wide range of data transfer. For example, in accordance with this invention, a transaction may be completed using telephone lines connecting long distance carrier systems. In this instance, the issuer-owned data which may be included on transaction device  240  using any of the methods discussed herein, may be an account number which corresponds to long distance calling time such as may be done with a conventional calling card. 
     Where transaction device  240  is loaded with several distinct data sets, each corresponding to a distinct data set owner operating on distinct and non-compatible communications network, the user of transaction device  240  may use the instrument to complete long distance calls on each of the distinct communications network, independently of the other. This is especially useful for transaction device  240  user who may travel to different locations, where the different locations support different long distance communications network. In this exemplary embodiment, the present invention enables a user to anticipate which communications network is available in many different travel destinations, and include the corresponding mating data set on transaction device  240  prior to beginning travel. In this way, transaction device  240  user may be prepared to use transaction device  240  as a long distance calling card irrespective of his anticipated travel destination. 
     Non-traditional payment processing devices  1600  may include, for example, cell phones, pervasive computing devices, palm pilots, Blackberry® handhelds, and other devices which may be enabled to participate in standard transactions with merchants, issuers, and/or any other third parties. With reference to  FIG. 16 , an exemplary non-traditional payment processing device  1600  is depicted. Non-traditional payment device  1600  may be configured, for example, as a cell-phone  1605  device. Cell phone  1605  may be configured with an RFID transponder  1602  in the phone casing or in any other part of the phone or phone accessories. In another embodiment, cell phone  1605  may be configured with one or more RFID-enabling protocols that allow cell phone  1605  to have RFID capabilities. 
     Device  1600  may have various transaction information encrypted in a payload on device  1600 . For example, the encrypted payload may contain one or more routing numbers associated with device  1600  to facilitate locating an issuing bank. In addition, the encrypted payload may include a phone number and/or other identifier, financial information, account data, and the like. 
     In another embodiment, non-traditional device  1600  may be issued by a transaction account issuer (e.g., American Express®, banks, etc.) or a non-traditional issuer, such as, for example, a telephone company, wireless company, appliance manufacturer, or the like. Non-traditional device  1   600  may be configured to participate in standard merchant-processing networks in a way similar to traditional transaction devices  240 , described herein. Further, non-traditional device  1600  may be configured to use a safe wireless payment protocol and/or to be billed by the telephone company and/or other non-traditional issuer. 
     Non-traditional devices  1600  may be configured to communicate transaction information and/or may be used to facilitate RF transactions. For example, with reference to an exemplary method illustrated in  FIG. 17 , non-traditional device  1600  may be configured to communicate with RFID reader  265  via RF transponder  1602  (step  1701 ). RFID reader  265  may respond to non-traditional device  1600  by communicating to RF transponder  1602  a random number (step  1703 ). Device  1600  may be configured to use the random number to produce an authentication tag using RF transponder  1602  (step  1705 ). Device  1600  may then form a transaction request comprising the authentication tag, device  1600  identifier, and/or device  1600  counter, transaction information and the like (step  1707 ). Device  1600  may be configured to facilitate communicating the transaction request to RFID reader  265  (step  1709 ). RFID reader  265  may be configured to convert the transaction request into a form that may be read by merchant system POS  275  (step  1711 ). In one exemplary embodiment, RFID reader  265  may format the transaction request in the ISO 8583 format. However, RFID reader  265  may be configured to convert the transaction into any format known in the art. 
     Once RFID reader  265  converts the transaction request, RFID reader  265  may forward the request to merchant system POS  275  (step  1713 ). Merchant system POS  275  may be configured to communicate with RFID reader  265  via any network and/or data link described herein. Merchant system POS  275  may then be configured to forward the transaction request to the acquirer as an authorization request (step  1715 ). POS  275  may be configured to forward the authorization request to the acquirer using any payment infrastructure and/or network. In one embodiment, merchant system POS  275  may be configured to forward the transaction request to the associated acquirer using an existing charge card payment infrastructure and network that are based on the routing number provided to device  1600 . In another embodiment, the merchant and/or POS  275  may use the standard 8583 protocol to submit the transaction request to the issuer/acquirer. The merchant and/or POS  275  may also place the encrypted payload from device  1600  into the cryptogram field in the authorization request to forward to the acquirer. 
     The acquirer may forward the authorization request to the issuing bank (if different than the acquirer) (step  1717 ). If the acquirer is the same as the issuing bank and/or after the authorization has been sent to the issuing bank, the issuing bank may recognize the type of authorization request, and it may verify the authentication tag, the counter and/or any other transaction information that is part of the request (step  1719 ). 
     Since the routing number may be defined as the account number on the ISO 8583 authorization request, the issuing bank may use the routing number to locate the encryption key used to create the authentication tag for device  1600  (step  1721 ). That is, when the issuing bank receives the authorization request, it may use the account number/routing number in the Cryptogram field to facilitate decryption using the secret encryption key associated with the routing number. If the issuing bank cannot verify the authentication tag and/or the counter, the issuing bank may reject the request and return it to the merchant (step  1723 ). If the issuing bank can verify both the authentication tag and/or the counter, the authorization may be approved (step  1725 ). The accountholder may then be billed based on the decrypted account number ID (step  1727 ). 
     The transaction account number and phone number of non-traditional cell phone  1605  may typically be linked or associated. The transaction account number and phone number may also be provided and/or serviced by different organizations. In one embodiment, cell phone  1605  may be managed completely by the carrier, while the transaction account number may be supported completely by the account issuer. That is, even if the account issuer does not issue a physical transaction device, the issuer may issue the transaction account number that is imbedded in cell phone  1605 . Because the accountholder may be the same as the phone holder, the account issuer may bill the accountholder directly and/or the issuing bank may bill the phone carrier for all payments made using cell phone  1605  device. The term “phone carrier,” as used herein, may refer to any traditional and/or wireless phone carrier, such as, for example, AT&amp;T, MCI, Sprint, Cingular, Nextel, Verizon, and the like. 
     It may then be the responsibility of the phone carrier to individually bill the different phone holders/accountholders for the payment. Since the phone carriers bill by using a customer identification number (which may be the phone number), the phone number associated with the account number used in the payment may be identifiable and usable by the phone carrier. In one embodiment, the phone carrier may use the phone number in the payment transaction so that the phone number may be explicitly defined as part of the transaction and in the transaction request. In another embodiment, the phone carrier may identify the account number associated with the phone number in order to complete a billing (if the carrier knows what account is included in the phone at any given time). 
     There may be multiple benefits to an exemplary embodiment in which the account issuer bills the phone carrier. For example, the benefit to the phone carrier may be that the phone carrier can provide a wireless payment process that integrates with the carrier&#39;s existing payment systems. Further, phone carrier billing and settlement may simplify the payment process involving the merchant, and it may limit the amount of payment changes at the merchant&#39;s location that result from reader upgrades. In another exemplary embodiment, the phone carrier may receive a portion of the fees (discount, interchange, network, etc.) that are assessed to the merchant for the transaction. This may provide increased revenue for the phone carriers. In one embodiment, the account issuer may bill the phone carrier periodically (e.g., daily, weekly, monthly) for all activity since the previous period. If the issuer bills the phone carrier, settlement may occur through a direct payment to the account issuer by the phone carrier. However, the account issuer and the phone carrier may also settle the transaction accounts at any other period of time and/or per any other requirements. 
     In yet another embodiment in accordance with the present invention, and with reference to an exemplary method depicted in  FIG. 18 , a method  1800  for using an additional authentication factor may be used by non-traditional device  1600  before the account data is actually provided to RFID reader  265 . This additional authentication factor may be used because non-traditional devices  1600 , such as cell phone device  1605 , may be configured with greater processing capacity than traditional RF devices. Additional authentication factors may include secondary identifiers, such as, for example, PINs, biometrics, and other identifiers. For simplicity, the term “PIN” may be used herein to refer to any secondary identifiers identified herein. 
     For example, when cell phone&#39;s  1605  transponder  1602  is activated by RFID reader  265  (step  1801 ), transponder  1602  may be configured to facilitate prompting the user to enter a PIN for the account data (step  1803 ). For example, RFID reader  265  may prompt the user for a PIN, cell phone  1605  may prompt the user for a PIN, and/or any other interface communicating with the system may prompt the user for a PIN. Cell phone  1605  may then use this data to produce a first authentication tag (step  1805 ). However, cell phone  1605  may be configured to not include the authentication tag in the payment request to RFID reader  265  (step  1807 ). The acquirer may then identify the PIN for the transaction device (step  1809 ) and may use this PIN to generate a second authentication tag (step  1811 ). Acquirer and/or reader  265  may compare the first and second authentication tags (step  1813 ). If the tags do not match, the authentication fails and the request is returned to the merchant as rejected (step  1817 ). If the tags do match, the authentication succeeds and the transaction may continue (step  1815 ). 
     The invention contemplates additional and/or alternative uses of the authentication information. For example, in one embodiment the acquirer and/or reader  265  may store the PIN to be validated in the encrypted cryptogram, so that the PIN number is not broadcast to the rest of the payment system. In another embodiment, non-traditional device  1600  may be configured to include the cell phone  1605  number (or the unique identifier for non-cell phone devices) as a variable in the authentication tag. Since there is an explicit relationship between non-traditional device  1600  and the account number, an additional authentication step may include a device identifier itself (either the phone number or some other unique identifier). This may help to insure that the account is only being used in conjunction with the device. 
     The invention further contemplates the involvement of one or more additional parties in the transaction process, such as, for example, the parent device (cell phone  1605 ) carrier (i.e., the phone carrier). Although a transaction may not use the parent device carrier&#39;s infrastructure (because the transaction uses RF reader  265  attached to an existing POS device), the parent carrier may still be important to the use of non-traditional device  1600 . For example, in one embodiment, the account, counter and encryption key are not manufactured into cell phone  1605 , but instead may be loaded at any time by the parent device carrier (similarly to the way a phone number can be changed). Similarly, the phone carrier may associate the account number with a specific phone number. In another embodiment, the phone carrier may be the real owner of an account (and responsible party) and the phone holder may be considered an additional accountholder. 
     In another exemplary embodiment the invention may include a third party in the normal payment transaction/relationship. For example, in an exemplary embodiment using cell phone  1605  configured with an imbedded transponder  1602 , the merchant may receive a transaction request from cell phone  1605  and may forward it to the acquirer for authorization. If approved, the request may then be submitted to the acquirer and the acquirer may pay the merchant. The acquirer may then provide (and settle) the request to the account issuer who may then bill the transaction to the accountholder. 
     In yet another embodiment, the phone carrier may be a distinct party that may involved in one or more aspects of the payment and/or settlement process. For example, the account issuer may route each transaction to the phone carrier for authorization as well as billing. In this embodiment, the account issuer may serve as an extended acquirer and may be reimbursed for the settlement with the acquirer where the payment originated. For each transaction, the phone carrier may pay the account issuer less whatever fees that it will receive for the transaction. 
     In the foregoing specification, the invention has been described with reference to specific embodiments. However, it may be appreciated that various modifications and changes can be made without departing from the scope of the present invention. For example, alternate authentication and verification methods are required by the account issuer system may be employed. The issuer system may require the transaction device to include random number generators, counters, authentication tags, or the like for transaction device, reader, or transaction verification. Additionally, the notifications to the user discussed herein may be visual, audible, or any other suitable notification method capable of conveying to the user that multiple transaction accounts are available for transaction completion. Further, the processing method described herein may be modified so as to permit the selection of a data set from the transaction device using a PIN, where each data set is assigned a PIN, and the user uses the PIN to identify which data set to select for transaction completion. Further still, the user may audibly or physically (e.g., touch screen, input data in touch pad or key pad) select which data set to use. As such, the specification and figures are to be regarded in an illustrative manner applicable irrespective of the data processing protocol used by a data set owner, rather than a restrictive one, and all such modifications are intended to be included within the scope of present invention. Accordingly, the scope of the invention should be determined by the appended claims and their legal equivalents, rather than by the examples given above. For example, the steps recited in any of the method or process claims may be executed in any order and are not limited to the order presented. 
     Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of any or all the claims. As used herein, the terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, no element described herein is required for the practice of the invention unless expressly described as “essential” or “critical.”