US20090106157A1 - Funding a Radio Frequency Device Transaction - Google Patents

Abstract

A transponder-reader payment system includes an RFID reader for interrogating a transponder and an RFID transponder device. The RFID reader receives, from the RFID transponder device, a code that is associated with a first funding source and a second funding source. The RFID reader communicates a request associated with a transaction to a payment processor. The request includes the code and the transaction is funded using the first funding source and the second funding source associated with the code. In one embodiment, the transaction is funded according to a funding account protocol associated with the code.

Description

RELATED APPLICATIONS
• This application is a continuation of U.S. patent application Ser. No. 10/876,822, entitled “TRANSMITTINGTRACK 1/TRACK 2 FORMATTED INFORMATION VIA RADIO FREQUENCY,” filed on Jun. 24, 2004, which is a continuation of U.S. patent application Ser. No. 10/318,480, entitled “SYSTEM AND METHOD FOR ASSIGNING A FUNDING SOURCE FOR A RADIO FREQUENCY IDENTIFICATION DEVICE,” filed Dec. 13, 2002 (U.S. Pat. No. 7,249,112 on Jul. 24, 2007), which is a non-provisional of U.S. Provisional Patent Application No. 60/396,577, filed Jul. 16, 2002. U.S. patent application Ser. No. 10/876,822 is also a continuation of U.S. patent application Ser. No. 10/192,488, entitled “SYSTEM AND METHOD FOR PAYMENT USING RADIO FREQUENCY IDENTIFICATION IN CONTACT AND CONTACTLESS TRANSACTIONS,” filed on Jul. 9, 2002 (issued as U.S. Pat. No. 7,239,226 on Jul. 3, 2007), which is a non-provisional of U.S. Provisional Application No. 60/304,216, filed on Jul. 10, 2001. All of the above applications are incorporated herein by reference.
FIELD OF INVENTION
• This invention generally relates to facilitating a radio frequency device transaction, and more particularly, to facilitating a financial transaction using a first funding source and a second funding source.
BACKGROUND OF THE INVENTION
• Like barcode and voice data entry, RFID is a contactless information acquisition technology. RFID systems are wireless, and are usually extremely effective in hostile environments where conventional acquisition methods fail. RFID has established itself in a wide range of markets, such as, for example, the high-speed reading of railway containers, tracking moving objects such as livestock or automobiles, and retail inventory applications. As such, RFID technology has become a primary focus in automated data collection, identification and analysis systems worldwide.
• Of late, companies are increasingly embodying RFID data acquisition technology in a fob or tag for use in completing financial transactions. A typical fob includes a transponder and is ordinarily a self-contained device which may be contained on any portable form factor. In some instances, a battery may be included with the fob to power the transponder. In which case the internal circuitry of the fob (including the transponder) may draw its operating power from the battery power source. Alternatively, the fob may exist independently of an internal power source. In this instance the internal circuitry of the fob (including the transponder) may gain its operating power directly from an RF interrogation signal. U.S. Pat. No. 5,053,774 issued to Schuermann describes a typical transponder RF interrogation system which may be found in the prior art. The Schuermann patent describes in general the powering technology surrounding conventional transponder structures. U.S. Pat. No. 4,739,328 discusses a method by which a conventional transponder may respond to a RF interrogation signal. Other typical modulation techniques which may be used include, for example, ISO/IEC 14443 and the like.
• In the conventional fob powering technologies used, the fob is typically activated upon presenting the fob in an interrogation signal. In this regard, the fob may be activated irrespective of whether the user desires such activation. Inadvertent presentation of the fob may result in initiation and completion of an unwanted transaction. Thus, a fob system is needed which allows the fob user to control activation of the fob to limit transactions being undesirably completed.
• One of the more visible uses of the RFID technology is found in the introduction of Exxon/Mobil's Speedpass® and Shell's EasyPay® products. These products use transponders placed in a fob or tag which enables automatic identification of the user when the fob is presented at a Point of Sale (POS) device. Fob identification data is typically passed to a third party server database, where the identification data is referenced to a customer (e.g., user) credit or debit account. In an exemplary processing method, the server seeks authorization for the transaction by passing the transaction and account data to an authorizing entity. Once authorization is received by the server, clearance is sent to the point of sale device for completion of the transaction. In this way, the conventional transaction processing method involves an indirect path which causes undue overhead due to the use of the third-party server.
• A need exists for a transaction authorization system which allows fob transactions to be authorized while eliminating the cost associated with using third-party servers.
• In addition, conventional fobs are limited in that they must be used in proximity to the Point of Sale device. That is, for fob activation, conventional fobs must be positioned within the area of transmission cast by the RF interrogation signal. More particularly, conventional fobs are not affective for use in situations where the user wishes to conduct a transaction at a point of interaction such as a computer interface.
• Therefore, a need exists for a fob embodying RFID acquisition technology, which is capable of use at a point of interaction device and which is additionally capable of facilitating transactions via a computer interface connected to a network (e.g., the Internet).
• Existing transponder-reader payment systems are also limited in that the conventional fob used in the systems is only responsive to one interrogation signal. Where multiple interrogation signals are used, the fob is only responsive to the interrogation signal to which it is configured. Thus, if the RFID reader of the system provides only an interrogation signal to which the fob is incompatible, the fob will not be properly activated.
• Therefore, a need exists for a fob which is responsive to more than one interrogation signal.
• Existing transponder-reader payment systems are additionally limited in that the payment systems are typically linked to a funding source associated with the transponder which includes a predetermined spending limit. Thus no flexibility is provided in instances where the payment is requested which exceeds the predetermined spending limit. This is typically true since traditional methods for processing a requested transaction involve comparing the transaction to the spending limit or to an amount stored in a preloaded value data file prior to providing transaction authorization to a merchant.
• Thus, a system is needed which processes transponder-reader payment requests irrespective of the spending limit assigned to an associated transponder-reader payment system funding source.
• Further, traditional transponder-reader systems do not permit the user to manage the system user account data. This is extremely problematic where the user wishes to change a transponder-reader system funding source to a source which provides more available spending room, or where changes are made to user's status (e.g., change in address, phone number, email, etc.) for which the transponder-reader account provider wishes to readily update the user's account.
• Thus a need exists for a transponder-reader system which will allow the user limited access to the transponder-reader account for managing account data.
• Further still, existing transponder-reader systems do not permit means for automatically incenting the use of the fob associated with the system as opposed to the credit or charge card associated with the fob. That is, conventional transponder-reader systems do not provide a means for encouraging usage of the transponder reader system by encouraging use of the fob product since the present systems do not distinguish between usage of a system transponder and a charge or credit card account associated with the transponder.
• Consequently, a need exists for a transponder-reader system which is capable of determining when a system transponder is used, and incenting such usage.
• Still further, present systems are limited in that the systems are unable to track credit or charge card usage and fob usage for a single funding source. For example, in typical prior art systems, a fob may be linked to a specified funding source (e.g., American Express, MasterCard, Visa, etc.) which may be used to provide funds for satisfaction of a transaction request. The funding source may additionally have a consumer credit or charge card which may be associated with the fob and which may be used for contact transactions. Where the credit or charge card is used, a statement reporting the card usage is provided to the card user. However, the reporting statement does not include a reporting of the fob product usage. Thus, a fob user is unable to chart, analyze or compare fob usage to the usage of the associated card. This is especially problematic where the funding source is used by more than one entity (e.g., spouses, multiple company personnel, etc.) where one entity may use the fob and a separate entity may use the card associated with the fob.
• Thus, a need exists for a transponder-reader payment system which would permit reporting of the fob usage and the credit card usage in a single file.
SUMMARY OF THE INVENTION
• Described herein is a system and method for using RFID technology to initiate and complete financial transactions. The transponder-reader payment system described herein may include an RFID reader operable to provide a RF interrogation signal for powering a transponder system, receiving a transponder system RF signal, and providing transponder system account data relative to the transponder system RF signal. The transponder-reader payment system may include an RFID protocol/sequence controller in electrical communication with one or more interrogators for providing an interrogation signal to a transponder, an RFID authentication circuit for authenticating the signal received from the transponder, a serial or parallel interface for interfacing with a point of interaction device, and an USB or serial interface for use in personalizing the RFID reader and/or the transponder. The transponder-reader payment system may further include a fob including one or more transponders (e.g., modules) responsive to one or more interrogation signals and for providing an authentication signal for verifying that the transponder and/or the RFID reader are authorized to operate within the transponder reader payment system. In this way, the fob may be responsive to multiple interrogation signals provided at different frequencies. Further, the fob may include a USB or serial interface for use with a computer network or with the RFID reader.
• In one embodiment, the RFID reader receives, from the RFID transponder device, a code that is associated with a first funding source and a second funding source. The RFID reader communicates a request associated with a transaction to a payment processor. The request includes the code and the transaction is funded using the first funding source and the second funding source associated with the code. In one embodiment, the transaction is funded according to a funding account protocol associated with the code.
• The RFID system and method according to the present invention may include an RFID transponder device which may be embodied in a fob, tag, card or any other form factor (e.g., wristwatch, keychain, cell phone, etc.), which may be capable of being presented for interrogation. In that regard, although the transponder is described herein as embodied in a fob, the invention is not so limited. The system may further include an RFID reader configured to send a standing RFID recognition signal which may be transmitted from the RFID reader via radio frequency (or electromagnetic) propagation. The fob may be placed within proximity to the RFID reader such that the RFID signal may interrogate the fob and initialize fob identification procedures.
• In one exemplary embodiment, as a part of the identification process, the fob and the RFID reader may engage in mutual authentication. The RFID reader may identify the fob as including an authorized system transponder for receiving encrypted information and storing the information on the fob memory. Similarly, the fob, upon interrogation by the RFID reader, may identify the RFID reader as authorized to 25 receive the encrypted and stored information. Where the RFID reader and the fob successfully mutually authenticate, the fob may transmit to the RFID reader certain information identifying the transaction account or accounts to which the fob is associated. The RFID reader may receive the information and forward the information to facilitate the completion of a transaction. In one exemplary embodiment, the RFID reader may forward the information to a point of interaction device (e.g., POS or computer interface) for transaction completion. The mutual authorization process disclosed herein aids in ensuring fob transponder-reader payment system security.
• In another exemplary embodiment, the fob according to the present invention, includes means for completing transactions via a computer interface. The fob may be connected to the computer using a USB or serial interface fob account information may be transferred to the computer for use in completing a transaction via a network (e.g., the Internet). In yet another exemplary embodiment of the present invention, a system is provided which incents usage of the transponder-reader system transponder (e.g., fob). The system distinguishes between the usage of a fob and the usage of a charge or credit card sharing the same funding source as the fob. Where the fob is used, the system may provide reward points to the user based on criteria predetermined by the issuer. Additionally, where a preloaded fob system is used, the present invention recognizes when the associated fob preloaded value data file is loaded or reloaded with funds. The invention then may provide reward points based on the criteria associated with the loading or reloading action. Further, the system according to this invention may incent patronage of a merchant. In this case, the system may receive a fob transaction request and incent the fob user based on a marker or other identifier correlated with the merchant. The marker may be included in the transaction identification, in a merchant identification provided with the transaction, or a combination of both.
• In still another exemplary embodiment of the invention, a system is disclosed which enables the user to manage the account associated with the fob. The user is provided limited access to all or a portion of the fob account information stored on the account provider database for updating, for example, demographic information, account funding source, funding account protocol and/or account restrictions (e.g., spending limits, personal identification number, etc.). Access to all or a portion of the account may be provided to the user telephonically or via a network (e.g., online).
• 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 a further exemplary embodiment, the present invention provides methods for processing a transaction request whereby the amount of the transaction request may be approved prior to requesting funding from the funding source and/or verifying that the amount for completing the transaction is available. In this way, the transaction may be approved provided the transaction and/or account meets certain predetermined authorization criteria. Once the criteria is met, the transaction is authorized and authorization is provided to the requesting agent (e.g., merchant). In one instance the payment for the transaction is requested from the funding source simultaneously to, or immediately following, the providing of the authorization to the merchant.
• In another instance the payment for transactions is requested at a time period later than when the authorization is provided to the merchant. These features and other advantages of the system and method, as well as the structure and operation of various exemplary embodiments of the system and method, are described below.
BRIEF DESCRIPTION OF THE DRAWINGS
• The accompanying drawings, wherein like numerals depict like elements, illustrate exemplary embodiments of the present invention, and together with the description, serve to explain the principles of the invention. In the drawings:
• FIG. 1A illustrates an exemplary RFID-based system in accordance with the present invention, wherein exemplary components used for fob transaction completion are depicted;
• FIG. 1B illustrates an exemplary personalization system in accordance with the present invention;
• FIG. 2 is a schematic illustration of an exemplary fob in accordance with the present invention;
• FIG. 3 is a schematic illustration of an exemplary RFID reader in accordance with the present invention;
• FIG. 4 is an exemplary flow diagram of an exemplary authentication process in accordance with the present invention;
• FIG. 5 is an exemplary flow diagram of an exemplary decision process for a protocol/sequence controller in accordance with the present invention;
• FIGS. 6A-B are an exemplary flow diagram of a fob personalization process in accordance with the present invention;
• FIGS. 7A-B are an exemplary flow diagram of an RFID reader personalization process in accordance with the present invention;
• FIG. 8 is a flow diagram of an exemplary payment/transaction process in accordance with the present invention;
• FIG. 9 is another schematic illustration of an exemplary fob in accordance with the present invention;
• FIG. 10 is a depiction of an exemplary preloaded fob payment/transaction process in accordance with the present invention;
• FIG. 11B is a depiction of an exemplary preloaded fob account reload process in accordance with the present invention;
• FIG. 12 is a depiction of an exemplary Direct Link payment/transaction process in accordance with the present invention;
• FIG. 13 is a depiction of another exemplary payment/transaction process in accordance with the present invention; and
• FIG. 14 is an exemplary flow diagram of a funding protocol for use by the fob account provider in satisfying a transaction request.
DETAILED DESCRIPTION
• The present invention may be described herein in terms of functional block components, screen shots, optional selections and various processing steps. Such functional blocks may be realized by any number of hardware and/or software components configured to perform to 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 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, extensible markup language (XML), JavaCard and MULTOS 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 the like. For a basic introduction on cryptography, review a text written by Bruce Schneier entitled “Applied Cryptography: Protocols, Algorithms, and Source Code in C,” published by John Wiley & Sons (second edition, 1996), herein incorporated by reference.
• In addition, many applications of the present invention could be formulated. The exemplary network disclosed herein 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 network (ITN).
• Where required, the system user may interact with the system via any input device such as, a keypad, keyboard, mouse, kiosk, personal digital assistant, handheld computer (e.g., Palm Pilot®, Blackberry®, cellular phone and/or the like. Similarly, the invention could be used in conjunction with any type of personal computer, network computer, work station, minicomputer, mainframe, or the like running any operating system such as any version of Windows, Windows NT, Windows 2000, Windows 98, Windows 95, MacOS, OS/2, BeOS, Linux, UNIX, Solaris or the like. Moreover, although the invention may frequently be described as being implemented with TCP/IP communications protocol, it should be understood that the invention could also be implemented using SNA, IPX, Appletalk, IPte, NetBIOS, OSI or any number of communications protocols. Moreover, the system contemplates, the use, sale, or distribution of any goods, services or information over any network having similar functionality described herein.
• FIG. 1A illustrates an exemplaryRFID transaction system100A in accordance with the present invention, wherein exemplary components for use in completing a fob transaction are depicted. In general, the operation ofsystem100A may begin whenfob102 is presented for payment, and is interrogated byRFID reader104 or, alternatively,interface134.Fob102 andRFID reader104 may then engage in mutual authentication after which thetransponder102 may provide the transponder identification and/or account identifier to theRFID reader104 which may further provide the information to themerchant system130POS device110.
• System100A may include afob102 having atransponder114 and anRFID reader104 in RF communication withfob102. Although the present invention is described with respect to afob102, the invention is not to be so limited. Indeed, system100 may include any device having a transponder which is configured to communicate with anRFID reader104 via RF communication. Typical devices may include, for example, a key ring, tag, card, cell phone, wristwatch or any such form capable of being presented for interrogation.
• TheRFID reader104 may be configured to communicate using an RFIDinternal antenna106. Alternatively,RFID reader104 may include anexternal antenna108 for communications withfob102, where the external antenna may be made remote to theRFID reader104 using a suitable cable and/ordata link120.RFID reader104 may be further in communication with amerchant system130 via adata link122. Thesystem100A may include a transaction completion system including a point of interaction device such as, for example, a merchant point of sale (POS)device110 or a computer interface (e.g., user interface)134. In one exemplary embodiment the transaction completion system may include amerchant system130 including thePOS device110 in communication with an RFID reader104 (via data link122). As described more fully below, the transaction completion system may include theuser interface134 connected to anetwork136 and to the transponder via aUSB connector132.
• Although the point of interaction device is described herein with respect to a merchant point of sale (POS) device, the invention is not to be so limited. Indeed, a merchant POS device is used herein by way of example, and the point of interaction device may be any device capable of receiving fob account data. In this regard, the POS may be any point of interaction device enabling the user to complete a transaction using afob102.POS device110 may be in further communication with a customer interface118 (via data link128) for entering at least a customer identity verification information. In addition,POS device110 may be in communication with a merchant host network112 (via data link124) for processing any transaction request. In this arrangement, information provided byRFID reader104 is provided to thePOS device110 ofmerchant system130 viadata link122. ThePOS device110 may receive the information (and alternatively may receive any identity verifying information fromcustomer interface118 via data link128) and provide the information tohost system112 for processing.
• A variety of conventional communications media and protocols may be used fordata links120,122,124, and128. For example,data links120,122,124, and128 may be an Internet Service Provider (ISP) configured to facilitate communications over a local loop as is typically used in connection with standard modem communication, cable modem, dish networks, ISDN, Digital Subscriber Lines (DSL), or any wireless communication media. In addition, themerchant system130 including thePOS device110 andhost network112 may reside on a local area network which interfaces to a remote network (not shown) for remote authorization of an intended transaction. Themerchant system130 may communicate with the remote network via a leased line, such as a T1, D3 line, or the like. Such communications lines are described in a variety of texts, such as, “Understanding Data Communications,” by Gilbert Held, which is incorporated herein by reference.
• An account number, as used herein, may include any identifier for an account (e.g., credit, charge debit, checking, savings, reward, loyalty, or the like) which may be maintained by a transaction account provider (e.g., payment authorization center) and which may be used to complete a financial transaction. A typical account number (e.g., account data) may be correlated to a credit or debit account, loyalty account, or rewards account maintained and serviced by such entities as American Express®, Visa® and/or MasterCard® or the like. For ease in understanding, the present invention may be described with respect to a credit account. However, it should be noted that the invention is not so limited and other accounts permitting an exchange of goods and services for an account data value is contemplated to be within the scope of the present invention.
• In addition, the account number (e.g., account data) may be associated with 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, digital certificate, biometric data, and/or other identification indicia. The account number may be optionally located on a rewards card, charge card, credit card, debit card, prepaid card, telephone card, smart card, magnetic stripe card, bar code card, and/or the like. The account number may be distributed and stored in any form of plastic, electronic, magnetic, and/or optical device capable of transmitting or downloading data 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 American Express®. Each company's credit card numbers comply with that company's standardized format such that the company using a sixteen-digit format will generally use four spaced sets of numbers, as represented by the number “0000 0000 0000 0000”. In a typical example, 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. The account number stored asTrack 1 andTrack 2 data as defined in ISO/IEC 7813, and further may be made unique tofob102. In one exemplary embodiment, the account number may include a unique fob serial number and user identification number, as well as specific application applets. The account number may be stored infob102 inside adatabase214, as described more fully below.Database214 may be configured to store multiple account numbers issued to thefob102 user by the same or different account providing institutions. Where the account data corresponds to a loyalty or rewards account, thedatabase214 may be configured to store the attendant loyalty or rewards points data.
• FIG. 2 illustrates a block diagram of the many functional blocks of anexemplary fob102 in accordance with the present invention.Fob102 may be anRFID fob102 which may be presented by the user to facilitate an exchange of funds or points, etc., for receipt of goods or services. As described herein, by way of example, thefob102 may be an RFID fob which may be presented for facilitating payment for goods and/or services.
• Fob102 may include anantenna202 for receiving an interrogation signal fromRFID reader104 via antenna106 (or alternatively, via external antenna108).Fob antenna202 may be in communication with atransponder114. In one exemplary embodiment,transponder114 may be a 13.56 MHz transponder compliant with the ISO/IEC 14443 standard, andantenna202 may be of the 13 MHz variety. Thetransponder114 may be in communication with a transponder compatible modulator/demodulator206 configured to receive the signal fromtransponder114 and configured to modulate the signal into a format readable by any later connected circuitry. Further, modulator/demodulator206 may be configured to format (e.g., demodulate) a signal received from the later connected circuitry in a format compatible withtransponder114 for transmitting toRFID reader104 viaantenna202. For example, wheretransponder114 is of the 13.56 MHz variety, modulator/demodulator206 may be ISO/IEC 14443-2 compliant.
• Modulator/demodulator206 may be coupled to a protocol/sequence controller208 for facilitating control of the authentication of the signal provided byRFID reader104, and for facilitating control of the sending of thefob102 account number. In this regard, protocol/sequence controller208 may be any suitable digital or logic driven circuitry capable of facilitating determination of the sequence of operation for thefob102 inner-circuitry. For example, protocol/sequence controller208 may be configured to determine whether the signal provided by theRFID reader104 is authenticated, and thereby providing to theRFID reader104 the account number stored onfob102.
• Protocol/sequence controller208 may be further in communication withauthentication circuitry210 for facilitating authentication of the signal provided byRFID reader104. Authentication circuitry may be further in communication with a non-volatilesecure memory database212.Secure memory database212 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.Database212 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.Database212 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 preferably 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 controller208 for data analysis and used for management and control purposes, as well as security purposes. Authentication circuitry may authenticate the signal provided byRFID reader104 by association of the RFID signal to authentication keys stored ondatabase212. Encryption circuitry may use keys stored ondatabase212 to perform encryption and/or decryption of signals sent to or from theRFID reader104.
• In addition, protocol/sequence controller208 may be in communication with adatabase214 for storing at least afob102 account data, and aunique fob102 identification code. Protocol/sequence controller208 may be configured to retrieve the account number fromdatabase214 as desired.Database214 may be of the same configuration asdatabase212 described above. The fob account data and/or unique fob identification code stored ondatabase214 may be encrypted prior to storage. Thus, where protocol/sequence controller208 retrieves the account data, and or unique fob identification code fromdatabase214, the account number may be encrypted when being provided toRFID reader104. Further, the data stored ondatabase214 may include, for example, an unencryptedunique fob102 identification code, a user identification,Track 1 and 2 data, as well as specific application applets.Fob102 may be configured to respond to multiple interrogation frequency transmissions provided byRFID reader104. That is, as described more fully below,RFID reader104 may provide more than one RF interrogation signal. In this case,fob102 may be configured to respond to the multiple frequencies by including infob102 one or more additional RF signal receiving/transmittingunits226. RF signal receiving/transmittingunit226 may include anantenna218 andtransponder220 where theantenna218 andtransponder220 are compatible with at least one of the additional RF signals provided byRFID reader104. For example, in one exemplary embodiment,fob102 may include a 134KHz antenna218 configured to communicate with a 134KHz transponder220. In this exemplary configuration, an ISO/IEC 14443-2 compliant modulator/demodulator may not be required. Instead, the 134 KHz transponder may be configured to communicate directly with the protocol/sequence controller208 for transmission and receipt of authentication and account number signals as described above.
• In another embodiment,fob102 may further include a universal serial bus (USB)connector132 for interfacingfob102 to auser interface134.User interface134 may be further in communication with aPOS device110 via anetwork136.Network136 may be the Internet, an intranet, or the like as is described above with respect tonetwork112. Further, theuser interface134 may be similar in construction to any conventional input devices and/or computing systems aforementioned for permitting the system user to interact with the system. In one exemplary embodiment,fob102 may be configured to facilitate online Internet payments. AUSB converter222 may be in communication with a USB connector232 for facilitating the transfer of information between the modulator/demodulator206 andUSB connector132. Alternatively,USB converter222 may be in communication with protocol/sequence controller208 to facilitate the transfer of information between protocol/sequence controller208 andUSB connector132.
• Wherefob102 includes aUSB connector132,fob102 may be in communication with, for example, a USB port onuser interface134. The information retrieved fromfob102 may be compatible with credit card and/or smart card technology enabling usage of interactive applications on the Internet. No RFID reader may be required in this embodiment since the connection toPOS device110 may be made using a USB port onuser interface134 and anetwork136.
• Fob102 may include means for enabling activation of the fob by the user. In one exemplary embodiment, a switch230 which may be operated by the user of thefob102. The switch230 onfob102 may be used to selectively or inclusively activate thefob102 for particular uses. In this context, the term “selectively” may mean that the switch230 enables the user to place thefob102 in a particular operational mode. For example, the user may place thefob102 in a mode for enabling purchase of a good or of a service using a selected account number. Alternatively, the fob may be placed in a mode as such that the fob account number is provided by USB port132 (or serial port) only and thefob transponder114 is disabled. In addition, the term “inclusively” may mean that thefob102 is placed in an operational mode permitting thefob102 to be responsive to the RF interrogation and interrogation via theUSB connector132. In one particular embodiment, the switch230 may remain in an OFF position ensuring that one or more applications or accounts associated with thefob102 are non-reactive to any commands issued byRFID reader104. As used herein, the OFF position may be termed the “normal” position of the activation switch230, although other normal positions are contemplated.
• In another exemplary embodiment, when the switch230 is moved from the OFF position, thefob102 may be deemed activated by the user. That is, the switch230 may activate internal circuitry infob102 for permitting the fob to be responsive to RF signals (e.g., commands from RFID reader104). In this way, switch230 may facilitate control of the active and inactive states of thefob102. Such control increases the system security by preventing inadvertent or illegal use of thefob102.
• In one exemplary embodiment, switch230 may be a simple mechanical device in communication with circuitry which may electrically prevent the fob from being powered by an RFID reader. That is, when switch230 is in its normal position, switch230 may provide a short to thefob102 internal circuitry, preventingfob102 from being responsive to interrogation by RF or via the USB connector230. In this arrangement, the switch230 may be, for example, a “normally closed” (NC) configured switch, which may be electrically connected to theantenna202 at the interface of theantenna202 and thetransponder114. The switch230 may be depressed, which may open the switch230 fully activating theantenna202.
• In yet another exemplary embodiment, thefob102 may include a biometric sensor and biometric membrane configured to operate as switch230 and activate thefob102 when provided biometric signal from thefob102 user. Such biometric signal may be the digital reading of a fingerprint, thumbprint, or the like. Typically, where biometric circuitry is used, the biometric circuitry may be powered by an internal voltage source (e.g., battery). In this case, the switch may not be a simple mechanical device, but a switch which is powered. In yet another exemplary embodiment, switch230 may be battery powered though no biometric circuitry is present in thefob102.
• In yet another embodiment, the switch230 may be a logic switch. Where switch230 is a logic switch the switch230 control software may be read from thesequence controller208 to selectively control the activation of thevarious fob102 components.
• FIG. 3 illustrates an exemplary block diagram of anRFID reader104 in accordance with an exemplary embodiment of the present invention.RFID reader104 includes, for example, anantenna106 coupled to aRF module302, which is further coupled to acontrol module304. In addition,RFID reader104 may include anantenna108 positioned remotely from theRFID reader104 and coupled toRFID reader104 via asuitable cable120, or other wire or wireless connection.
• RF module302 andantenna106 may be suitably configured to facilitate communication withfob102. Wherefob102 is formatted to receive a signal at a particular RF frequency,RF module302 may be configured to provide an interrogation signal at that same frequency. For example, in one exemplary embodiment,fob102 may be configured to respond to an interrogation signal of about 13.56 MHz. In this case,RFID antenna106 may be 13 MHz and may be configured to transmit an interrogation signal of about 13.56 MHz. That is,fob102 may be configured to include a first and second RF module (e.g., transponder) where the first module may operate using a 134 kHz frequency and the second RF module may operate using a 13.56 MHz frequency. TheRFID reader104 may include two receivers which may operate using the 134 kHz frequency, the 13.56 MHz frequency or both. When thereader104 is operating at 134 kHz frequency, only operation with the 134 kHz module on thefob102 may be possible. When thereader104 is operating at the 13.56 MHz frequency, only operation with the 13.56 MHz module on thefob102 may be possible. Where thereader104 supports both a 134 kHz frequency and a 13.56 MHz RF module, thefob102 may receive both signals from thereader104. In this case, thefob102 may be configured to prioritize selection of the one or the other frequency and reject the remaining frequency. Alternatively, thereader104 may receive signals at both frequencies from the fob upon interrogation. In this case, thereader104 may be configured to prioritize selection of one or the other frequency and reject the remaining frequency.
• Further, protocol/sequence controller314 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 thefob102 user that the transaction is initiated (e.g., fob is being interrogated), the fob is valid (e.g., fob is authenticated), transaction is being processed, (e.g., fob 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 thefob102 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 thefob102 is being interrogated, the transaction status, or the like.
• RFID antenna106 may be in communication with atransponder306 for transmitting an interrogation signal and receiving at least one of an authentication request signal and/or an account data fromfob102.Transponder306 may be of similar description astransponder114 ofFIG. 2. In particular,transponder306 may be configured to send and/or receive RF signals in a format compatible withantenna202 in similar manner as was described with respect tofob transponder114. For example, wheretransponder306 is 13.56 MHz RF ratedantenna202 may be 13.56 MHz compatible. Similarly, wheretransponder306 is ISO/IEC 14443 rated,antenna106 may be ISO/IEC 14443 compatible.
• RF module302 may include, for example,transponder306 in communication withauthentication circuitry308 which may be in communication with asecure database310.Authentication circuitry308 anddatabase310 may be of similar description and operation as described with respect toauthentication circuitry210 andsecure memory database212 ofFIG. 2. For example,database310 may store data corresponding to thefob102 which are authorized to transact business over system100.Database310 may additionally storeRFID reader104 identifying information for providing to fob102 for use in authenticating whetherRFID reader104 is authorized to be provided the fob account number stored onfob database214.
• Authentication circuitry308 may be of similar description and operation asauthentication circuitry210. That is,authentication circuitry308 may be configured to authenticate the signal provided byfob102 in similar manner thatauthentication circuitry210 may be configured to authenticate the signal provided byRFID reader104. As is described more fully below,fob102 andRFID reader104 engage in mutual authentication. In this context, “mutual authentication” may mean that operation of the system100 may not take place untilfob102 authenticates the signal fromRFID reader104, andRFID reader104 authenticates the signal fromfob102.
• FIG. 4 is a flowchart of an exemplary authentication process in accordance with the present invention. The authentication process is depicted as one-sided. That is, the flowchart depicts the process of theRFID reader104 authenticating thefob102, although similar steps may be followed in the instance that fob102 authenticatesRFID reader104.
• As noted,database212 may store security keys for encrypting or decrypting signals received fromRFID reader104. In an exemplary authentication process, whereRFID reader104 is authenticatingfob102,RFID reader104 may provide an interrogation signal to fob102 (step402). The interrogation signal may include a random code generated by the RFIDreader authentication circuit210, which is provided to thefob102 and which is encrypted using an unique encryption key corresponding to thefob102 unique identification code. For example, the protocol/sequence controller314 may provide a command to activate theauthentication circuitry308.Authentication circuitry308 may provide from database310 a fob interrogation signal including a random number as a part of the authentication code generated for each authentication signal. The authentication code may be an alphanumeric code which is recognizable (e.g., readable) by theRFID reader104 and thefob102. The authentication code may be provided to thefob102 via theRFID RF interface306 and antenna106 (or alternatively antenna108).
• Fob102 receives the interrogation signal (step404). The interrogation signal including the authorization code may be received at theRF interface114 viaantenna202. Once thefob102 is activated, the interrogation signal including the authorization code may be provided to the modulator/demodulator circuit206 where the signal may be demodulated prior to providing the signal to protocol/sequence controller208. Protocol/sequence controller208 may recognize the interrogation signal as a request for authentication of thefob102, and provide the authentication code toauthentication circuit210. Thefob102 may then encrypt the authentication code (step406). In particular, encryption may be done byauthentication circuit210, which may receive the authentication code and encrypt the code prior to providing the encrypted authentication code to protocol/sequence controller208.Fob102 may then provide the encrypted authentication code to the RFID reader104 (step408). That is, the encrypted authentication code may be provided to theRFID reader104 via modulator/demodulator circuit206, RF interface114 (e.g., transponder114) andantenna202.
• RFID reader104 may then receive the encrypted authentication code and decryption it (step410). That is, the encrypted authentication code may be received atantenna106 andRF interface306 and may be provided toauthentication circuit308.Authentication circuit308 may be provided a security authentication key (e.g., transponder system decryption key) fromdatabase310. The authentication circuit may use the authentication key to decrypt (e.g., unlock) the encrypted authorization code. The authentication key may be provided to the authentication circuit based on thefob102 unique identification code. For example, the encrypted authentication code may be provided along with theunique fob102 identification code. The authentication circuit may receive thefob102 unique identification code and retrieve from the database310 a transponder system decryption key correlative to theunique fob102 identification code for use in decrypting the encrypted authentication code.
• Once the authentication code is decrypted, the decrypted authentication code is compared to the authentication code provided by theRFID reader104 at step402 (step412) to verify its authenticity. If the decrypted authorization code is not readable (e.g., recognizable) by theauthentication circuit308, thefob102 is deemed to be unauthorized (e.g., unverified) (step416) and the operation of system100 is terminated (step418). Contrarily, if the decrypted authorization code is recognizable (e.g., verified) by thefob102, the decrypted authorization code is deemed to be authenticated (step412), and the transaction is allowed to proceed (step414). In one particular embodiment, the proceeding transaction may mean that thefob102 may authenticate theRFID reader104 prior to theRFID reader104authenticating fob102, although, it should be apparent that theRFID reader104 may authenticate thefob102 prior to thefob102 authenticating theRFID reader104.
• It should be noted that in an exemplary verification process, theauthorization circuit308 may determine whether the unlocked authorization code is identical to the authorization code provided instep402. If the codes are not identical then thefob102 is not authorized to access system100. Although, the verification process is described with respect to identicality, identicality is not required. For example,authentication circuit308 may verify the decrypted code through any protocol, steps, or process for determining whether the decrypted code corresponds to an authorizedfob102.
• Authentication circuitry308 may additionally be in communication with a protocol/sequence controller314 of similar operation and description as protocol/sequence controller208 ofFIG. 2. That is, protocol/sequence device controller314 may be configured to determine the order of operation of theRFID reader104 components. For example,FIG. 5 illustrates and exemplary decision process under which protocol/sequence controller314 may operate. Protocol/sequence controller314 may command the different components ofRFID reader104 based on whether afob102 is present (step502). For example, if afob102 is not present, then protocol/sequence controller314 may command theRFID reader104 to provide an uninterrupted interrogation signal (step504). That is, the protocol/sequence controller may command theauthentication circuit308 to provide an uninterrupted interrogation signal until the presence of afob102 is realized. If afob102 is present, the protocol/sequence controller314 may command theRFID reader104 to authenticate the fob102 (step506).
• As noted above, authentication may mean that the protocol/sequence controller314 may command theauthentication circuit308 to providefob102 with an authorization code. If a response is received fromfob102, protocol/sequence controller may determine if the response is a response to theRFID reader104 provided authentication code, or if the response is a signal requiring authentication (step508). If the signal requires authentication, then the protocol/sequence controller314 may activate the authentication circuit as described above (step506). On the other hand, if thefob102 signal is a response to the provided authentication code, then the protocol/sequence controller314 may command theRFID reader104 to retrieve the appropriate security key for enabling recognition of the signal (step510). That is, the protocol/sequence controller314 may command theauthentication circuit308 to retrieve from database310 a security key (e.g., transponder system decryption key), unlock the signal, and compare the signal to the signal provided by theRFID reader104 in the authentication process (e.g., step506). If the signal is recognized, the protocol/sequence controller314 may determine that thefob102 is authorized to access the system100. If the signal is not recognized, then thefob102 is considered not authorized. In which case, the protocol/sequence controller314 may command the RFID controller to interrogate for authorized fobs (step504).
• Once the protocol/sequence controller determines that thefob102 is authorized, the protocol/sequence controller314 may seek to determine if additional signals are being sent by fob102 (step514). If no additional signal is provided byfob102, then the protocol/sequence controller314 may provide all the components ofRFID reader104 to remain idle until such time as a signal is provided (step516). Contrarily, where anadditional fob102 signal is provided, the protocol/sequence controller314 may determine if thefob102 is requesting access to the merchant point of sale terminal110 (e.g., POS device) or if thefob102 is attempting to interrogate theRFID reader104 for return (e.g., mutual) authorization (step518). Where thefob102 is requesting access to a merchant point ofsale terminal110, the protocol/sequence controller314 may command theRFID reader104 to open communications with the point of sale terminal110 (step524). In particular, the protocol/sequence controller314 may command the point of saleterminal communications interface312 to become active, permitting transfer of data between theRFID reader104 and the merchant point ofsale terminal110.
• On the other hand, if the protocol/sequence controller determines that thefob102 signal is a mutual interrogation signal, then the protocol/sequence controller may command theRFID reader104 to encrypt the signal (step520). The protocol/sequence controller314 may command theencryption authentication circuit318 to retrieve fromdatabase320 the appropriate encryption key in response to thefob102 mutual interrogation signal. The protocol/sequence controller314 may then command theRFID reader104 to provide the encrypted mutual interrogation signal to thefob102. The protocol/sequence controller314 may command theauthentication circuit318 to provide an encrypted mutual interrogation signal for thefob102 to mutually authenticate.Fob102 may then receive the encrypted mutual interrogation signal and retrieve fromauthentication circuitry212 an RFID reader decryption key.
• Although an exemplary decision process of protocol/sequence controller314 is described, it should be understood that a similar decision process may be undertaken by protocol/sequence controller208 in controlling the components offob102. Indeed, as described above, protocol/sequence controller314 may have similar operation and design as protocol/sequence controller208. In addition, to the above, protocol/sequence controllers208 and314 may incorporate in the decision process appropriate commands for enabling USB interfaces222 and316, when the corresponding device is so connected.
• Encryption/decryption component318 may be further in communication with a secureaccount number database320 which stores the security keys necessary for decrypting the encrypted fob account number. Upon appropriate request from protocol/sequence controller314, encryption/decryption component (e.g., circuitry318) may retrieve the appropriate security key, decrypt the fob account number and forward the decrypted account number toprotocol sequence controller314 in any format readable by any later connectedPOS device110. In one exemplary embodiment, the account number may be forwarded in a conventional magnetic stripe format compatible with the ISO/IEC 7813 standard. Upon receiving the account number in magnetic stripe format, protocol/sequence controller314 may forward the account number toPOS device110 via acommunications interface312 and data link122, as best shown inFIG. 1.POS device110 may receive the decrypted account number and forward the magnetic stripe formatted account number to amerchant network112 for processing under the merchant's business as usual standard. In this way, the present invention eliminates the need of a third-party server. Further, where thePOS device110 receives a response from network112 (e.g., transaction authorized or denied), protocol/sequence controller314 may provide the network response to theRF module302 for optically and/or audibly communicating the response to thefob102 user.
• RFID reader104 may additionally include aUSB interface316, in communication with the protocol/sequence controller314. In one embodiment, the USB interface may be a RS22 serial data interface. Alternatively, theRFID reader104 may include a serial interface such as, for example, a RS232 interface in communication with the protocol/sequence controller314. TheUSB connector316 may be in communication with a personalization system116 (shown inFIG. 1B) for initializingRFID reader104 to system100 application parameters. That is, prior to operation of system100,RFID reader104 may be in communication withpersonalization system116 for populatingdatabase310 with a listing of security keys belonging to authorizedfobs102, and for populatingdatabase320 with the security keys to decrypt thefob102 account numbers placing the account numbers in ISO/IEC 7813 format. In this way,RFID reader104 may be populated with a unique identifier (e.g., serial number) which may be used byfob authentication circuitry210 to determine ifRFID reader104 is authorized to receive afob102 encrypted account number.
• FIG. 1B illustrates anexemplary personalization system100B, in accordance with the present invention. In general,typical personalization system100B may be any system for initializing theRFID reader104 and fob102 for use insystem100A. With reference toFIG. 1B, the similar personalization process forfob102 may be illustrated. For example,personalization system116 may be in communication withfob102 via RF ISO 14443interface114 for populatingfob database212 with the security keys for facilitating authentication of theunique RFID reader104 identifier. In addition,personalization system116 may populate on database212 aunique fob102 identifier for use byRFID reader104 in determining whetherfob102 is authorized to access system100.Personalization system116 may populate (e.g., inject) theencrypted fob102 account number intofob database214 for later providing to an authenticatedRFID reader104.
• In one exemplary embodiment,personalization system116 may include any standard computing system as described above. For example,personalization system116 may include a standard personal computer containing a hardware security module operable using any conventional graphic user interface. Prior to populating the security key information account number and unique identifying information into thefob102 orRFID reader104, the hardware security module may authenticate thefob102 andRFID reader104 to verify that the components are authorized to receive the secure information.
• FIGS. 6A-B illustrate an exemplary flowchart of a personalization procedure which may be used to personalizefob102 and/orRFID reader104. Although the following description discusses mainly personalization offob102,RFID reader104 may be personalized using a similar process. The personalization process, which occurs between thepersonalization system116 and the device to be personalized (e.g.,fob102 or RFID reader104), may begin, for example atstep602. Mutual authentication may occur between thepersonalization system116 and the device to be authenticated in much the same manner as was described above with regard tofob102 mutually authenticating withRFID reader104. That is,personalization system116 may transmit apersonalization system116 identifier to the device to be authenticated which is compared by thedevice authentication circuitry210,308 against personalization system identifiers stored in thedevice database212,310. Where a match does not occur (step604), the personalization process may be aborted (step612). Where a match occurs (step604), the personalization system may prepare a personalization file to be provided to the device to be personalized (step606). If the personalization system is operated manually, the personalization file may be entered into thepersonalization system116 using any suitable system interface such as, for example, a keyboard (step606). Where thepersonalization system116 operator elects to delay the preparation of the personalization files, thesystem116 may abort the personalization process (step610). In this context, the personalization file may include theunique fob102 orRFID reader104 identifier, security key for loading intodatabase212 and310, and/or security keys for decrypting a fob account number which may be loaded indatabase320.
• Fob102 may be personalized by direct connection to thepersonalization system116 via RF ISO/IEC 14443interface114, or thefob102 may be personalized usingRFID reader104.Personalization system116 andRFID reader104 may engage in mutual authentication andRFID reader104 may be configured to transmit the fob personalization file to fob102 via RF. Once thefob102 is presented to RFID reader104 (steps608,614) for personalization,fob102 andRFID reader104 may engage in mutual authentication (step614). Where thefob102 is not presented to theRFID reader104 for personalization, the personalization process may be aborted (step610).
• If thefob102 is detected, thepersonalization system116 may create as a part of the personalization file, a unique identifier for providing to the fob102 (step616). The identifier is unique in that one identifier may be given only to a single fob. That is, no other fob may have that same identifier. The fob may then be configured and loaded with that identifier (step618).
• Theencrypted fob102 account number may be populated intofob102 in the same manner as is described with respect to thefob102 unique identifier. That is,personalization system116 may pre-encrypt the account data (step640) and inject the encrypted account into fob database214 (step622). The encrypted account data may be loaded (e.g., injected) into thefob102 usingRFID reader104 as discussed above.
• Once the personalization file is populated into thefob102, the populated information is irreversibly locked to prevent alteration, unauthorized reading and/or unauthorized access (step624).Personalization system116 may then create a log of the personalization file information for later access and analysis by thepersonalization system116 user (step626).
• It should be noted that in the event the personalization process is compromised or interrupted (step628), thepersonalization system116 may send a security alert to the user (step630) and the personalization process may be aborted (step612). On the other hand, where no such compromising or interruption exists, thepersonalization system116 may be prepared to begin initialization on a second device to be personalized (step632).
• FIGS. 7A-B illustrate another exemplary embodiment of a personalization process which may be used to personalizeRFID reader104.RFID reader104 may be in communication with apersonalization system116 via an RFID reader USB connection316 (step702). Once connected,personalization system116 may establish communications with theRFID reader104 andRFID reader104 may providepersonalization system116 anyRFID reader104 identification data presently stored on the RFID reader104 (step704). In accordance withstep708, where theRFID reader104 is being personalized for the first time (step706) theRFID reader104 and thepersonalization system116 may engage in mutual authentication as described above with respect toFIGS. 6A-B. After the mutual authentication is complete,personalization system116 may verify thatRFID reader104 is properly manufactured or configured to operate within system100. The verification may include evaluating the operation of theRFID reader104 by determining if the RFID reader will accept predetermined default settings. That is, thepersonalization system116 may then provide the RFID reader104 a set of default settings (step708) and determine if theRFID reader104 accepts those settings (step712). IfRFID reader104 does not accept the default settings,personalization system116 may abort the personalization process (step714).
• If thepersonalization system116 determines that the personalization process is not the first personalization process undertaken by the RFID reader104 (step706),personalization system116 andRFID reader104 may engage in a mutual authentication process using the existing security keys already stored on RFID reader104 (step710). If authentication is unsuccessful (step712), thepersonalization system116 may abort the personalization process (step714).
• Where thepersonalization system116 and theRFID reader104 successfully mutually authenticate, thepersonalization system116 may update theRFID reader104 security keys (step716). Updating the security keys may take place at any time as determined by a system100 manager. The updating may take place as part of a routine maintenance or merely to install current security key data. The updating may be performed by downloading firmware into RFID reader104 (step718). In the event that thepersonalization system116 determines instep706 that theRFID reader104 is undergoing an initial personalization, the firmware may be loaded into theRFID reader104 for the first time. In this context, “firmware” may include any file which enables theRFID reader102 to operate under system100 guidelines. For example, such guidelines may be directed toward the operation of RFID reader protocol/sequence controller314.
• Personalization system116 may then determine if the personalization keys (e.g., security keys, decryption keys, RFID identifier) need to be updated or if theRFID reader104 needs to have an initial installation of the personalization keys (step720). If so, thenpersonalization system116 may download the personalization keys as appropriate (step722).
• Personalization system116 may then check theRFID reader104 to determine if thefob102 identifiers and corresponding security keys should be updated or initially loaded (step724). If no updating is necessary thepersonalization system116 may end the personalization procedure (step732). Contrarily, if thepersonalization system116 determines that thefob102 identifiers and corresponding keys need to be updated or installed, thepersonalization system116 may download the information onto RFID reader104 (step726). The information (e.g., fob security keys and identifiers) may be downloaded in an encrypted format and theRFID reader104 may store the information in theRFID reader database310 as appropriate (step728). Thepersonalization system116 may then create or update a status log cataloging for later use and analysis by thepersonalization system116 user (step730). Upon updating the status log, the personalization process may be terminated (step732).
• It should be noted that, in some instances it may be necessary to repersonalize the RFID reader in similar manner as described above. In that instance, the personalization process described inFIGS. 7A and 7B may be repeated.
• FIG. 8 illustrates an exemplary flow diagram for the operation ofsystem100A. The operation may be understood with reference toFIG. 1A, which depicts the elements ofsystem100A which may be used in an exemplary transaction. The process is initiated when a customer desires to present afob102 for payment (step802). Upon presentation of thefob102, the merchant initiates the RF payment procedure via an RFID reader104 (step804). In particular, the RFID reader sends out an interrogation signal to scan for the presence of fob102 (step806). The RF signal may be provided via theRFID reader antenna106 or optionally via anexternal antenna108. The customer then may present thefob102 for payment (step808) and thefob102 is activated by the RF interrogation signal provided.
• Thefob102 and theRFID reader104 may then engage in mutual authentication (step810). Where the mutual authentication is unsuccessful, an error message may be provided to the customer via the RFID optical and/or audible indicator (step814) and the transaction may be aborted (step816). Where the mutual authentication is successful (step814), theRFID reader104 may provide the customer with an appropriate optical and/or audible message (e.g., “transaction processing” or “wait”) (step818). The fob protocol/sequence controller208 may then retrieve fromdatabase214 an encrypted fob account number and provide the encrypted account number to the RFID reader104 (step820).
• TheRFID reader104 may then decrypt the account number and convert the account number into magnetic stripe (ISO/IEC 7813) format (step822) and provide the unencrypted account number to the merchant system130 (step828). In particular, the account number may be provided to thePOS110 device for transmission to themerchant network112 for processing. Exemplary processing methods according to the present invention are discussed with respect toFIGS. 10-13, shown below. Upon processing, thePOS device110 may then send an optical and/or audible transaction status message to the RFID reader104 (step830) for communication to the customer (step832).
• The methods for processing the transactions may include one of several formats as required by the fob issuer. For example, one processing method may include processing the transaction under a preloaded fob format wherein a payment value (e.g., monetary value, reward points value, barter points value, etc.) may be preloaded into an preloaded value account or data file prior to permitting usage of the fob. In this way, the user may be permitted to set aside a payment amount for transactions for goods and services using the fob. During processing of the transaction, approval of the transaction may involve comparing the transaction amount to the amount stored (or remaining) in the preloaded value data file. Comparison may be made by a preloaded value processing system wherein the preloaded value processing system may compare the transaction amount to be processed to the preload value data file. Where the transaction amount exceeds the amount stored in the preloaded value account, the preloaded value processing system may deny authorization for completion of the transaction. Contrarily, where the transaction amount does not exceed the amount stored in the preloaded value data file account the preloaded value processing system may provide for authorization of the transaction.
• An exemplary preloadedvalue processing system1000 is shown with respect toFIG. 10. Preloadedvalue processing system1000 may include afob102 including atransponder114, which is in communication with amerchant system130 via anRFID reader104 or acomputer interface134 as is described with respect toFIG. 1A. The merchant system may be in communication with anissuer system1010, where theissuer system1010 may be maintained by any entity (e.g., financial institution, American Express, Visa and/or MasterCard, etc.) which permits thefob102 user to store a preload value in a preloaded value account (e.g., data file) maintained on anissuer database1012 of similar construction asdatabase212. Theissuer system1000 may further include one or more process servers for processing a fob transaction. As shown, a POS device110 (included in merchant system130) may be in communication with an issuer account server (IAS)1014 for receiving the fob account information fromPOS device110.IAS1014 may be in further communication with a preloaded value authorization server (PLAS)1016 for processing transactions involving a preloaded value fob. ThePLAS1016 may be in further communication with anissuer database1012 for retrieving funds from the preloaded value data file (not shown) which are necessary for satisfying the preloaded fob or merchant transaction request.
• As used herein, the term “issuer” or “account provider” may refer to any entity facilitating payment of a transaction using a fob, and which included systems permitting payment using at least one of a preloaded and non-preloaded fob. Typical issuers maybe American Express, MasterCard, Visa, Discover, and the like. In the preloaded value processing context, an exchange value (e.g., money, rewards points, barter points, etc.) may be stored in a preloaded value data file for use in completing a requested transaction. The exchange value may not be stored on the fob itself. Further, the preloaded value data file may be debited the amount of the transaction requiring the preloaded value data file to be replenished. As described more fully below, the preloaded value system platform may be used to complete “direct link” transactions. In which case, the preloaded value account may function as a place holder, perpetually storing a zero value.
• The preloaded value data file may be any conventional data file configuration for storing a value (e.g., monetary, rewards points, barter points, etc.) which may be exchanged for goods or services. In that regard, the preloaded value data file may have any configuration as determined by theissuer system1010.
• In exemplary operation, a fob identifying information (e.g., account number or fob marker) may be provided to thePOS device110 in similar manner as was discussed with respect toFIG. 1A. That is, thefob102 may be presented to themerchant system130 via anRFID reader104 or acomputer interface134, which may provide the fob identifying information inTrack 1 orTrack 2 format. APOS device110 included in themerchant system130 may receive thefob102 identifying information and provide thefob102 identifying information along with the transaction identifying information (e.g., amount, quantity, merchant identification, etc.) to theissuer system1010 for authorization. Themerchant system130 may additionally include a merchant system marker or identifier for indicating a merchant system identity. Themerchant system130 may combine thefob102 identifying information, the merchant identifying information, or the transaction identifying information, or any combination thereof, into a merchant transaction request for providing to theissuer system1010.
• TheIAS1014 may receive the transaction and fob identifying information (or merchant transaction request) and recognize that the transaction is being requested relative to a preloaded value account associated with a preloaded fob. That is, theIAS1014 may recognize that the user has presented apreloaded fob102 for payment. Recognition of thefob102 as a preloaded fob may mean that the fob identifying information includes a marker or identifier indicating that the fob is associated with a preloaded value data file. Upon recognition of the marker, theIAS1014 may forward transaction and fob identifying information to thePLAS1016 for processing.PLAS1016 may compare the transaction amount to the value stored or remaining in the preloaded value to determine if authorization should be granted or denied. Where the transaction amount exceeds the value stored in the preloaded value data file thePLAS1016 may forward a transaction denied message to theIAS1014 for providing to themerchant system130. Alternatively, where the transaction amount is less than or equal to the value stored in the preload value data file thePLAS1016 may deduct from the preloaded value data file the necessary amount for satisfaction of the transaction.
• As noted above, in one exemplary embodiment of the present invention, thePLAS1016 may provide a transaction denied message to theIAS1014 where the amount stored in the preloaded value account is less than required for satisfying the merchant or fob transaction request. In this instance, where the preloaded value falls below a predetermined minimum level (e.g., minimum depletion level), it may be necessary for the fob user to reload the preloaded value data file. Reloading of the preloaded value account may take place manually (e.g., by the fob user telephonically or online) or may take place automatically when the value stored in the preloaded value data file is depleted to a predefined level. Where the reloading is done automatically, reloading may occur under rules established by the fob issuer or owner. For example, reloading may occur at preselected time limits, when the reserve is below a predetermined amount, until a maximum number of reloads in a predetermined time period has occurred or until a maximum reload amount is reached in a predetermined time period.
• FIG. 11B depicts an exemplary preloading and reloading processes which may be performed in accordance with the present invention. The preloading and reloading processes may be preformed using one or more servers (e.g., PLAS1016) in communication with afunding source1104. Although the processes are demonstrated using aPLAS1016, it is contemplated that any server for establishing and managing data files may be used. However, to facilitate further understanding of the invention, the preloading and reloading aspects of the invention are described with reference toPLAS1016.
• PLAS1016 may be used to establish on the server or on a database (e.g., database1012) a preloaded value account (e.g., data file) (1106). The preload value account may be funded or maintained by a fob issuer which may establish a credit, charge, debit, rewards value account, etc. in connection with a charge or credit card (e.g., Visa, MasterCard, American Express, Discover, etc.), debit or direct debit authorization (DDA) system.
• The preloaded value account may be established to at least a predetermined minimum preload amount or value (e.g., minimum preload level) as determined by the account provider and/or the fob user or owner. In this context, the predetermined minimum value (e.g., minimum preload value) required to establish the preloaded value account may vary with respect to a particular fob user. The preloaded value account may be loaded (e.g., preloaded or reloaded) from funds received from one of a funding source account1104 (American Express, Visa, MasterCard, Discover, etc.). That is, thePLAS1016 may communicate with thefunding source1104 to obtain funds or value for loading or reloading the preloaded value account (1108).
• FIG. 11B shows and exemplary reloading process in accordance with the invention. During operation, a consumer may present to amerchant system130 theprepaid fob102 for purchasing goods or services (1110). The preloaded value account is then depleted the value amount paid to themerchant system130. The process for purchasing goods may be repeated until the value stored in the preloaded value account equals or is less than a minimum level balance (e.g., minimum depletion level). The minimum depletion level may be predetermined by the fob user or fob issuer, and may be the minimum value permitted to be stored in the preloaded value account before the file is to be reloaded.
• Once the preloaded value data is depleted such that the minimum depletion level is reached, thePLAS1016 may trigger an automatic reload to reload the preloaded value account from funds retrieved from the funding source1104 (1112). The amount of funds retrieved may be sufficient for loading the preloaded value account to the minimum amount described above or to some other predetermined reload value. In one exemplary embodiment, thePLAS1016 may trigger automatic reloading where a predetermined minimum depletion level (e.g., “minimum level balance”) is reached. That is, the preloaded value account may not be entirely depleted to zero value before automatic reloading occurs. In this instance, thePLAS1016 may charge the funding necessary for automatic reloading against the available funds atfunding source1104. In another exemplary embodiment the automatic reloading may occur where the transaction exceeds the amount stored in or remaining in the preloaded value account. In this way, the preloaded value account may be restored to an amount necessary for completion of the transaction. For example, where automatic reloading restores the preloaded value account to a value suitable for transaction completion, the preloaded value account may be automatically reloaded prior to processing the transaction.
• In another exemplary embodiment, automatic reloading may occur based on different user or issuer automatic reload criteria. Other automatic reload criteria may include, but are not limited to, reloading until a defined maximum load amount in a defined time period is reached, reloading at a selected reoccurring time interval (e.g., once a month), reloading as permitted until a defined maximum number of reloads in a specified time period is reached, or reloading until a defined maximum reload amount is reached in a specified time period, etc. In some instances, reloading may be done manually, such as, for example, when the fob user contacts the issuer telephonically or via user interface to provide a specified funding criteria for use in reloading the preloaded value account.
• In yet another exemplary embodiment, the preloaded value transaction processing system may permit approval of a transaction where the transaction value exceeds the preloaded value amount stored in the preloaded value account. That is, the preloaded fob may be used for purchases exceeding the preloaded value amount provided that the charge submitted by the merchant is less than or equal to the maximum reload amount permitted plus the amount stored on the card at the time the charge is submitted.
• In another exemplary embodiment, the preloaded value system may approve transactions based on a particular merchants transaction processing protocol. Where the issuer has reviewed and/or approved a merchant's transaction processing method, the system may take the method in consideration in determining whether to approve a merchant's transaction request. For example, a merchant's transaction processing method may include the merchant submitting transaction requests which exceed the preloaded value amount, but the actual charge may be less than or equal to the preloaded value amount. Under this transaction processing method a merchant, such as, for example, a gasoline merchant, may seek pre-approval of an anticipated gasoline fueling amount. Neither the consumer nor the merchant may know the final value of the purchase, especially, for example, where the consumer decides to fill his automobile gas tank or purchase non-fuel items. Thus, the merchant may submit a transaction request which may be higher than the final amount of the transaction. In this instance, the preloaded value transaction processing system may still be configured to approve the transaction request. The processing system may recognize that a transaction came from a particular merchant and institute a predetermined approval protocol correlative to that merchant, since the approval protocol may include information that the merchant is sending a transaction request exceeding the actual charge.
• The transaction processing system may use any one of the acceptable techniques for identifying merchants, such as recognition of the merchant ID, or a marker appended to the transaction, etc. The processing system may correlate the merchant ID with a merchant protocol for requesting a transaction approval of an amount greater than the preloaded value (or reload value), and approve the merchant request accordingly.
• In accordance with an alternate exemplary embodiment of a preloadedvalue processing system1000, upon receiving the transaction request from theIAS1014, thePLAS1016 may evaluate the transaction request based upon several risk criteria established by the issuer. If all the criteria are successfully met, then thePLAS1016 may send authorization of the transaction (e.g., “transaction granted”) to theIAS1014 for providing to themerchant system130. Simultaneous with or subsequent to, providing the transaction authorization to theIAS1014, thePLAS1016 may seek satisfaction of the transaction from the fob value account maintained on theaccount provider database1012. The transaction request may be provided to theIAS1014 for processing. That is, theIAS1014 may seek to deduct the transaction value from the balance of the amount stored in the preloaded value account.
• FIG. 12 depicts an exemplary embodiment of another transaction processing system (“direct link” system)1200 in accordance with the present invention. More particularly,FIG. 12 depicts adirect link system1200 which may be used to process a merchant transaction request. In this context, a direct link system may be any system which facilitates satisfaction of a transaction request using a fob or other presentable medium (credit card, charge card, debit card, etc.) directly linked to an account which stores an exchange value (e.g., money, credit or charge, or rewards points, etc.). In this instance, the preloaded value account may not be preloaded as described above. Further, the preloaded value account may be linked to a contact product such as a credit, debit, and/or DDA card, and the like, which may be presented for payment of goods and services. In this regard, the fob (here called “direct link fob”) and the card are associated with the same funding source and the user or merchant may seek satisfaction of a transaction from the funding source independent of whether the direct link fob or card is used.
• In the exemplarydirect link system1200, thedirect link fob102 user may not establish a preloaded value account with value. Instead, the preloaded value account may perpetually store a zero value or thefob102 may be associated with a fob transaction account which may be used to provide payment to the merchant for goods and services where the account may be a credit, debit, loyalty account or the like.
• In accordance with an exemplary embodiment of the invention, a transaction request associated with adirect link fob102 may be processed using the preloaded value transaction system processing described above. However, as noted, in this instance the preloaded value account is used as a place holder storing a zero value. A transaction account containing a transaction account value which is associated with the direct link fob is treated as the funding source for satisfying direct link transactions. In this instance, the transaction may be satisfied according to a fob user or issuer predefined protocol or criteria.
• As shown, themerchant system130 may be in communication with anissuer system1010 for receiving a merchant transaction request. More particularly, thePOS device110 may be in communication with an issuer server, such as, for example, an issuer account server (IAS)1014 for receiving the merchant and/or transaction identifying information.IAS1014 may be in further communication with aPLAS1016 for processing the merchant transaction request. In some instances thePLAS1016 may be in further communication with asecond IAS1202, although asecond IAS1202 may not be required where one or more of the existing servers may perform the functions ofIAS1202 described below. However, theIAS1202 is included herein to simplify the understanding the operation of this exemplary embodiment.
• In exemplary operation ofsystem1200, the direct link fob identifying information (e.g., fob identifier or account number) may be provided to thePOS device110 in similar manner as was discussed with respect toFIG. 1A. That is, thedirect link fob102 may be presented to themerchant system130 via anRFID reader104 or acomputer interface134, which may provide thedirect link fob102 identifying information inTrack 1 orTrack 2 format. APOS device110 included in themerchant system130 may receive thedirect link fob102 identifying information and provide thedirect link fob102 identifying information along with the transaction identifying information (e.g., amount, quantity, merchant identification, etc.) to theissuer system1010 for authorization.
• TheIAS1014 may receive the transaction and fob identifying information and recognize that the transaction as being requested relative to adirect link fob102. Recognition of thedirect link fob102 in this instance may mean that thedirect link fob102 identifying information includes a marker or identifier indicating that the fob is associated with a zero value preloaded value account. Upon recognition of the marker, theIAS1014 may forward the transaction and fob identifying information toPLAS1016 for processing.
• In similar manner as was described with respect to the operation of the preloaded value processing system ofFIG. 10, thePLAS1016 may evaluate the transaction request based upon several risk criteria established by the issuer. Exemplary risk criteria may include, but are not limited to, consideration of transaction amount limits for a specified time period, fob user usage history, fund or reserve limits, pre-determined re-funding rules, user defined limits, etc. If all the criteria are successfully met, then thePLAS1016 may send authorization of the transaction (e.g., “transaction granted”) to theIAS1014 for providing to themerchant system130. The transaction authorization may be provided to themerchant system130 based on evaluation of the risk criteria and not upon the value present in preloaded value account or direct link transaction account storing value relative to the direct link fob.
• After providing the transaction authorization to theIAS1014, thePLAS1016 may seek authorization of the transaction against the direct link fob account (e.g., transaction account) which is maintained on theissuer database1012, and which is funded by value received from afunding source1104. The authorization request may be provided to theIAS1202 for approval which may retrieve the necessary value from the direct link fob account. For example, where the direct link fob account is a charge or credit account, thePLAS1016 may request authorization from thesecond IAS1202 and theIAS1202 may assess the transaction amount against the direct link fob account ondatabase1012. TheIAS1202 may seek to record the amount of the transaction in the direct link fob usage history data file for payment at the end of a billing cycle (e.g., charge account), or the amount may be recorded on the fob direct link fob usage data file for payment at a date later than the end of the billing cycle (e.g., credit account).
• In an alternative operation thePLAS1016 may assess the transaction amount against the direct link fob account, without use of asecond IAS1202. Whether the transaction is processed using asecond IAS1202, it is to be understood that value may not be immediately transferred to the merchant system from the direct link fob account for satisfying the transaction. Instead, the direct link fob issuer guarantees satisfaction of the merchant transaction request until the necessary value is retrieved from the direct link fob account at the end of the billing cycle or later.
• In yet another exemplarytransaction processing system1300 depicted inFIG. 13, themerchant system130 may provide a batch file containing multiple fob transaction requests to be processed to aprocess server1302 where the multiple fob transactions may include both preloaded value and direct link transaction request. Thesystem1300 may include aprocess server1302 which distinguished between preloaded value and direct link transaction requests. That is,process server1302 may be used for separating the fob transactions which are associated with a preloaded fob account and those that are not associated with a preloaded fob account, as discussed more fully below. Theprocess server1302 may further be in communication with anIAS1014 for seeking settlement of the transaction. TheIAS1014 may process the transaction request in accordance with the direct link transaction process or the preloaded value transaction platform described above.
• In exemplary operation ofsystem1300, theprocess server1302 may receive the settlement file and create sub-files of transaction requests relative to the type of fob used in the transaction (e.g., preloaded fob, and direct link fob associated with a charge or credit account). Theprocess server1302 may create a first fob transaction file for merchant payables and a second fob transaction file for accounts receivable to be forwarded to theIAS1014 for processing. Where the sub-file includes merchant payable, theprocess server1302 may provide funds to the merchant for payment of the transaction, where the funds provided may be equivalent to the transaction amount minus discount revenues. The funds may be retrieved from the funding source for providing to the merchant. Alternatively, theprocess server1302 may create a second fob transaction file for accounts receivable payments and forwarded the second fob transaction file to theIAS1014.IAS1014 may then process the transaction request according to the processes described inFIGS. 10 and 12. That is, theIAS1014 may distinguish the preloaded fob transaction requests from those associated with the direct link fob and process the transactions accordingly.
• Considering the operation of the various transaction processing systems described above, it can be seen that the transaction processing systems described may distinguish when a preloaded fob is used, when a card associated with a fob is used, or when an account associated with a preloaded fob is reloaded. In that regard, the present invention may be used to reward points depending on the nature of the fob usage. The points (e.g., loyalty points) may be stored in a points or rewards account maintained on the issuer database (e.g., database1012). The rewards points may then later be redeemed from the rewards account for exchange for goods and services as desired by the fob user.
• As noted, in one instance, points may be provided when the fob is used as opposed to when the card associated with the fob is used. For example, theIAS1014 may recognize that a fob is being used and award points (e.g., loyalty points) to the rewards account assigned to the fob user or associated with the fob. The loyalty points may be awarded based on any criteria as determined by the fob issuer. Exemplary rewarding criteria may include rewarding points for, for example, frequency of fob usage, amount of individual purchase using the fob, or the total amount of purchases in a given time period.
• Where the fob is associated with a preloaded value account such as that described with respect toFIG. 10, points may be awarded for account reloading. That is,IAS1014 may place award points in the rewards account relative to the amount loaded or reloaded as required. Further theIAS1014 may place reward points in the rewards account relative to usage of the fob at a particular merchant or for a particular transaction.
• It should be noted that the transaction account associated with thefob102 may include a usage restriction, such as, for example, a per purchase spending limit, a time of day use, a day of week use, certain merchant use and/or the like, wherein an additional verification is required when using the fob outside of the restriction. The restrictions may be personally assigned by thefob102 user, or the account provider. For example, in one exemplary embodiment, the account may be established such that purchases above $X (i.e., the spending limit) must be verified by the customer. Such verification may be provided using a suitable personal identification number (PIN) which may be recognized by theRFID reader104 or a payment authorization center (not shown) as being unique to thefob102 holder (e.g., customer) and thecorrelative fob102 transaction account number. Where the requested purchase is above the established per purchase spending limit, the customer may be required to provide, for example, a PIN, biometric sample and/or similar secondary verification to complete the transaction.
• Where a verification PIN is used as secondary verification the verification PIN may be checked for accuracy against a corroborating PIN which correlates to thefob102 transaction account number. The corroborating PIN may be stored locally (e.g., on thefob102, or on the RFID reader104) or may be stored on a database (not shown) at the payment authorization center. The payment authorization center database may be any database maintained and operated by thefob102 transaction account provider.
• The verification PIN may be provided to thePOS device110 using a conventional merchant (e.g., POS)PIN key pad118 in communication with thePOS device110 as shown inFIG. 1, or an RFID keypad in communication with theRFID reader104. PIN keypad may be in communication with the POS device110 (or alternatively, RFID reader104) using any conventional data link described above. Upon receiving the verification PIN, theRFID reader104 may seek to match the PIN to the corroborating PIN stored on theRFID reader104 atdatabase310 or320. Alternatively, the verification PIN may be provided to a payment authorization center to determine whether the PIN matches the PIN stored on the payment authorization center database which correlates to thefob102 account. If a match is made, the purchase may no longer be restricted, and the transaction may be allowed to be completed.
• In an alternate embodiment, verification of purchases exceeding the established spending limit may involve biometrics circuitry included infob102.FIG. 9 is a schematic block diagram of anexemplary fob102 whereinfob102 includes abiometric security system902.Biometric security system902 may include abiometric sensor904 for sensing the fingerprint of thefob102 user. Thebiometric sensor902 may be in communication with a sensor interface/driver906 for receiving the sensor fingerprint and activating the operation offob102. In communication with thebiometric sensor904 andsensor interface906 may be abattery903 for providing the necessary power for operation of the biometric security system components.
• In one exemplary application of thefob102 including thebiometric security system902, the customer may place his finger on the biometric sensor to initiate the mutual authentication process between thefob102 and theRFID reader104, or to provide secondary verification of the user's identity. The sensor fingerprint may be digitized and compared against a digitized fingerprint stored in a database (e.g., security database212) included onfob102. Such comparison step may be controlled by protocol/sequence controller208 and may be validated byauthentication circuit210. Where such verification is made, the mutual authentication betweenfob102 andRFID reader104 may begin, and the transaction may proceed accordingly. Alternatively, the comparison may be made with a digitized fingerprint stored on a database maintained by thefob102 transaction account provider system (not shown). The digitized fingerprint may be verified in much the same way as is described above with respect to the PIN.
• In one exemplary application of thefob102 including thebiometric security system902, thesystem902 may be used to authorize a purchase exceeding the established per purchase spending limit. In this case, where the customer's intended purchase exceeds the spending limit, the customer may be asked to provide assurance that the purchase is authorized. Accordingly, the customer may provide such verification by placing his finger over thebiometric sensor904. Thebiometric sensor904 may then digitize the fingerprint and provide the digitized fingerprint for verification as described above. Once verified,fob102 may provide a transaction authorized signal to RF transponder202 (or alternatively to transponder220) for forwarding toRFID reader104.RFID reader104 may then provide the transaction authorized signal to thePOS device110 in similar manner as is done with convention PIN driven systems and thePOS device110 may process the transaction under the merchant's business as usual standard.
• 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.).
• With reference toFIG. 1A, the fob user may connect thefob102 to acomputer interface134 via theUSB interface132. The fob user may then use thecomputer interface134 to access the fob user data file via thenetwork136. In particular, thenetwork136 may be in communication with an issuer system (e.g. system1010 ofFIG. 10) and may be provided limited access to an issuer server (e.g., server1014) for managing the fob. Theissuer server1014 may be in communication with an issuer system database (e.g.,1012) 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 theissuer system1010 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 theissuer database1012 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 (e.g. IAS1014) 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 offunding sources1104 described above. In this regard, thedatabase1012 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 thefob102 and when the value is retrieved from a funding source (or multiple funding sources) to complete a transaction.
• FIG. 14 depicts anexemplary funding protocol1400 which may be identified by the fob user. As shown, the funding protocol may be initiated when thefob102 is presented for payment (step1402). Thefob102 may be presented to anRFID reader104. TheRFID reader104 or thecomputer interface134 may provide an account number to themerchant system130 and themerchant system130 may seek satisfaction of a transaction request from an issuer system1010 (step1404).
• Thefob102 user may indicate via thedatabase1012 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, theissuer server1014 may switch the funding source associated with thefob102 from a primary funding source to a secondary funding source (step1408). In this regard, the server may retrieve value from the sub-data file associated with the secondary funding source. Theserver1014 may additionally determine whether the spending limit for the secondary funding source has been reached or exceeded (step1410). 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 (step1414). The funds may then be transferred to themerchant system130 under any business as usual standard (step1416), completing the merchant's transaction request.
• In some instances, the funding may be switched from the primary funding source to the secondary funding source (step1408), and the spending limit for the secondary funding source is reached or exceeded (step1410). In which case, theissuer server1014 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 (step1412). The combination of funds may be retrieved using any formula determined by the fob user or fob account issuer (step1430), and the funds may be transferred to themerchant system1014, 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 (step1432). In which case, the server may determine if the spending limit for the tertiary funding source has been reached or exceeded (step1436). If the funds are exceeded, the merchant request may be terminated and a “transaction denied” message may be forwarded to the merchant system130 (step1434).
• Where a merchant transaction request is not flagged (step1406), in one embodiment, theissuer server1014 may not switch from a primary funding source to a secondary funding source. Instead, theissuer server1014 may determine whether the spending limit on the primary source is reached or exceeded (step1420). 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 (step1422) and transferred to themerchant system130 under business as usual standards (step1424).
• Contrarily, where the spending limit on the primary funding source is reached or exceeded (step1420), in one embodiment, theissuer server1014 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 (step1426). 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 (step1430). The funds may then be transferred to themerchant system130 under business as usual standards (step1424).
• 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 (step1428). 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 (step1434).
• On the other hand, should the funding source be switched from a primary funding source to a secondary funding source, theserver1014 may determine whether the spending limit for the secondary funding source is reached or exceeded (step1440). 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 themerchant system130 under business as usual standards (step1434). 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 (step1442) and transferred to the merchant system130 (step1424), satisfying the transaction request.
• The preceding detailed description of exemplary embodiments of the invention makes reference to the accompanying drawings, which show the exemplary embodiment by way of illustration. While these exemplary embodiments 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. 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. Further, the present invention may be practiced using one or more servers, as necessary. Thus, the preceding detailed description is presented for purposes of illustration only and not of limitation, and the scope of the invention is defined by the preceding description, and with respect to the attached claims.

Claims (30)

1. A method, comprising:

receiving a code from a radio frequency (RF) transponder device, wherein the code is associated with a first funding source and a second funding source; and

communicating a request to a payment processor, wherein the request is associated with a transaction and comprises the code, and wherein the transaction is funded from the first funding source and the second funding source.

2. The method ofclaim 1, wherein the transaction is funded according to a funding account protocol associated with the code.

3. The method ofclaim 2, wherein the funding account protocol comprises a predetermined formula.

4. The method ofclaim 2, wherein the funding account protocol involves the first funding source and the second funding source.

5. The method ofclaim 2, wherein the funding account protocol comprises receiving funds from the second funding source in response to a first funding source value associated with the first funding source being less than a minimum depletion value associated with the first funding source.

6. The method ofclaim 2, wherein the funding account protocol comprises receiving funds from at least one of the first funding source or the second funding source according to a formula determined at least partially by at least one of: a merchant system, a payment processor system, an RF reader, a transaction processing system, a transponder device user, the RF transponder device, a loyalty points system, a first funding source system, or a second funding source system.

7. The method ofclaim 2, wherein the funding account protocol comprises receiving funds from at least one of the first funding source or the second funding source in accordance with at least one of: an amount associated with the transaction, a merchant type associated with the transaction, a first funding source value, a second funding source value, or a date of the request.

8. The method ofclaim 2, wherein the funding account protocol is stored on at least one of: a merchant system, a payment processor system, an RF reader, the RF transponder device, a transaction processing system, a first funding source system, or a second funding source system.

9. The method ofclaim 1, wherein communicating the request comprises communicating with at least one of a merchant system, a point of sale device, a payment transaction processor, a first funding source system, or a second funding source system.

10. The method ofclaim 1, further comprising:

encrypting, with a reader authentication key, a reader authentication signal received from the RF transponder device to create an encrypted reader authentication signal;

transmitting the encrypted reader authentication signal and an RF device authentication signal to the RF transponder device;

decrypting, with an RF device authentication key, an encrypted transponder authentication signal received from the RF transponder device to create a decrypted transponder authentication signal; and,

authenticating the RF transponder device in response to the decrypted transponder authentication signal matching the transponder device authentication signal.

11. A computer-readable medium having stored thereon a plurality of instructions, the plurality of instructions comprising:

instructions for receiving a code from a radio frequency (RF) transponder device, wherein the code is associated with a first funding source and a second funding source; and

instructions for communicating a request to a payment processor, wherein the request comprises the code, and wherein the request is funded from the first funding source and the second funding source.

12. A radio frequency (RF) reader, comprising:

a first communication device for receiving a code from an RF transponder device, wherein the code is associated with a first funding source and a second funding source; and

a second communication device for communicating a request to a payment processor, wherein the request comprises the code, and wherein the request is funded from the first funding source and the second funding source.

13. The RF reader ofclaim 12, wherein the first communication device and the second communication device are the same device.

14. A method, comprising

receiving a code associated with a radio frequency (RF) transponder device, wherein the code is associated with a first funding source and a second funding source; and,

processing a request, wherein the request is funded from at least one of the first funding source and the second funding source.

15. The method ofclaim 14, wherein the receiving comprises receiving from at least one of a radio frequency (RF) reader in communication with the RF transponder device, a merchant system in communication with the RF reader, or a point-of-sale (POS) device in communication with at least one of the RF transponder device or the RF reader.

16. The method ofclaim 14, further comprising communicating with a first funding source system and a second funding source system.

17. The method ofclaim 14, wherein the code is further associated with a third funding source and wherein the request is funded from the first funding source, the second funding source and the third funding source.

18. The method ofclaim 14, wherein the code is further associated with a funding account protocol associated with the first funding source and the second funding source.

19. The method ofclaim 18, further comprising funding the request according to the funding account protocol.

20. The method ofclaim 18, further comprising receiving an update funding account protocol request from at least one of a user, a user system, a personalization system, a payment processor, a merchant system, a loyalty points system, a first funding source system, or a second funding source system.

21. The method ofclaim 20, further comprising updating the funding account protocol according to the update funding account protocol request.

22. A method, comprising:

transmitting a code to a radio frequency (RF) reader, wherein the RF reader sends a request to a payment processor, and wherein the request is associated with a transaction and comprises the code, and wherein the code is associated with a first funding source and a second funding source, and wherein a request is funded from the first funding source and the second funding source.

23. The method ofclaim 21, further comprising:

encrypting, with a transponder device authentication key, a transponder device authentication signal received from the RF reader to create an encrypted transponder device authentication signal;

transmitting the encrypted transponder device authentication signal to the RF reader for authentication of a transponder device by the RF reader;

decrypting, with a reader authentication key, an encrypted reader authentication signal received from the RF reader to create a decrypted reader authentication signal;

authenticating the RF reader in response to the decrypted reader authentication signal matching a reader authentication signal transmitted from the transponder device to the RF reader;

24. A radio frequency (RF) transponder device, comprising:

a code associated with a first funding source and a second funding source;

a transponder device communication interface for transmitting the code to an RF reader, wherein the RF reader sends a request to a payment processor, and wherein the request is associated with a transaction and comprises the code, and wherein the code is associated with a first funding source and a second funding source, and wherein a request is funded from the first funding source and the second funding source.

25. The transponder device ofclaim 24, wherein the RF reader is in communication with at least one of: a merchant system, a point of sale device, a payment processor system, a loyalty points system, a payment processor, a first funding source system or the second funding source system.

26. The transponder device ofclaim 24, wherein the request is funded according to a funding account protocol associated with the code, the first funding source and the second funding source.

27. The transponder device ofclaim 24, further comprising:

means for encrypting, with a transponder device authentication key, a transponder device authentication signal received from the RF reader to create an encrypted transponder device authentication signal;

means for transmitting the encrypted transponder device authentication signal to the RF reader for authentication of the transponder device by the RF reader;

means for decrypting, with a reader authentication key, an encrypted reader authentication signal received from the RF reader to create a decrypted reader authentication signal; and

means for authenticating the RF reader in response to the decrypted reader authentication signal matching a reader authentication signal transmitted from the RF reader to the transponder device.

means for activating the transponder device communications interface in response to the decrypted reader authentication signal matching the reader authentication signal.

28. The transponder device ofclaim 27, further comprising:

means for encrypting the code with a code key to create an encrypted code, wherein the transponder device communication interface is further configured to transmit the encrypted code to the RF reader.

29. The transponder device ofclaim 28, wherein at least one of the transponder device authentication key, the reader authentication key, or the code key is a security key unique to at least one of the transponder device and the reader.

30. The transponder device ofclaim 28, wherein the transponder device authentication key, the reader authentication key, and the code key are the same key.

Images