Patent Document

RELATED APPLICATIONS 
     This application is a Continuation-in-Part application of U.S. application Ser. No. 09/630,595 filed Aug. 1, 2000, which is incorporated herein by reference in its entirety. 
     This application also claims priority to provisional U.S. application Ser. No. 60/774,192 filed Feb. 17, 2006, which is incorporated herein by reference in its entirety. 
    
    
     FIELD OF THE INVENTION 
     The systems and methods of the invention relate to keeping check of financial transactions using a register portion, in conjunction with performing authentication of the transaction. 
     BACKGROUND OF THE INVENTION 
     Standard credit cards and other transaction accounts have a Primary Account Number (PAN) which is typically the  16  digit number on the card. In the case of accounts having multiple cards, (e.g., a credit card having PAN xxxx xxxx xxxx xxxx with husband and wife each having a card), each of the multiple cards is the same. However, authentication processing may be complicated by both a husband and wife (or any other multiplicity of persons) using multiple cards off one PAN. 
     The invention addresses the above problem, as well as other problems, that exist in known technology. 
     SUMMARY OF THE INVENTION 
     Systems and methods are provided that keep check of financial transactions by maintaining a count of the financial transactions using a register portion, in conjunction with performing authentication further to inputting transaction data from a data-bearing record that is stored in a device. The system may include a communication portion that inputs transaction data received from the data bearing record, the transaction data including an input transaction count value and an input device differentiator number; and a processing portion that processes the transaction data. The processing portion may include (1) a memory portion that stores stored data; (2) a device identification portion that identifies the device based on the device differentiator number and an account number, the account number being derived from the transaction data; (3) a register portion that maintains a count of financial transactions so as to provide a current transaction count value associated with the input device differentiator number for the account number, the register portion maintaining current transaction count values for respective device differentiator numbers, which device differentiator numbers are associated with the account number; and (4) an authentication portion that performs authentication processing based on a comparison process that utilizes the current transaction count value and the input transaction count value, the authentication portion generating an authentication result, the authentication portion outputting the authentication result. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The invention can be more fully understood by reading the following detailed description together with the accompanying drawings, in which like reference indicators are used to designate like elements, and in which: 
         FIG. 1  illustrates an overall transaction architecture according to one embodiment of the invention; 
         FIG. 2  illustrates an overall architecture of the invention according to a second embodiment of the invention; 
         FIG. 3  illustrates an activation architecture for the initiation of user accounts according to the invention; 
         FIG. 4  illustrates a flowchart of transaction processing according to the invention; 
         FIG. 5  is a diagram showing a validation process utilizing a respective device differentiator number (DDN), assigned to each card, in accordance with one embodiment of the invention; 
         FIG. 6  is block diagram showing further details of the transaction server  200  in accordance with one embodiment of the invention; 
         FIG. 7  is a flow chart showing further aspects of transaction processing in accordance with one embodiment of the invention; and 
         FIG. 8  is diagram showing use of multiple device differentiator numbers with one PAN in accordance with one embodiment of the invention. 
     
    
    
     DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS 
     Hereinafter, aspects of methods and systems in accordance with various embodiments of the invention will be described. As used herein, any term in the singular may be interpreted to be in the plural, and alternatively, any term in the plural may be interpreted to be in the singular. 
     Features of various embodiments of the invention are described herein. The invention relates to utilization of a payment device in a transaction processing system. The payment device may be any of a variety of devices. The invention relates to identification of the particular payment device used in a transaction and processing associated with such identification. For example, the payment device may be a credit card, a smart card, RFID card, other funds card, a special device for effecting internet purchases, a program operating on a computer system, a key FOB, a device with a bar code, a phone, a device in a keychain, a processing component in an personal music device and/or any other payment device that is used by a user to effect a transaction. For example, the payment device may be a software applet running on the user&#39;s computer, which allows access to the user&#39;s account. Further, the particular payment device may utilize a variety of technologies to interface with other portions of the transaction processing system. Such interface used by the payment device may include magnetic stripe technology, wireless technology and/or a computer network, for example. For example, as described below in accordance with one embodiment, the invention might utilize RF or RFID technology as an interface between the payment device and the other transaction processing system components. Accordingly, various embodiments of the invention may utilize a variety of systems with differing architecture. 
     Accordingly, the invention is directed to providing differentiation between such multiple payment devices in the field. In short, any device might be utilized to function as a payment device so long as such device provides information needed to process a transaction, or so long as a customer can transmit the information using the device. However, it is appreciated that the architecture of the transaction processing system, including the payment devices, should preferably be sustained on a global network, i.e., to support global capabilities. 
     In accordance with one embodiment of the invention, hereinafter features of the invention relating to credit card processing will be described. In running a transaction for a credit card, for example, the card reader typically reads (1) the PAN, (2) expiration date of the card, and (3) discretionary data, for example. All of such information may be read using any suitable reader. The discretionary data may include an ATC (Automatic Transaction Counter) which increments for each new transaction. When the cardholder runs a new transaction, the ATC is read and then compared to an ATC value, when an ATC value is maintained by the authentication platform of the card processor, i.e., when a counter is maintained. If respective derived values, i.e., values derived from the ATC values, do not match, then the transaction is denied. This processing prevents fraud by a person who somehow reads (or otherwise acquires) the PAN and expiration data. Accordingly, the person attempting the transaction needs the ATC counter to run a transaction. 
     A problem in the “multiple cards per PAN” scenario is that each card will have a different ATC (Automatic Transaction Counter) count. For example, the husband may have an ATC value of  10  transactions on his card, and the wife has an ATC value of  25  transactions on her card. Both cards are tied to the same PAN account. If the card processor has an ATC value of 25 (the wife&#39;s value) for the shared PAN, and the husband uses his card which has an ATC of 10, obviously the husband&#39;s transaction will not go through. The problem is how does the processor in the authentication platform distinguish between the different cards for the PAN? One solution is to issue a different PAN for each payment device that is issued, e.g. one PAN for each credit card. However, this approach would result in an excessive and effectively unmanageable number of PANs. Also, such an arrangement would not allow a user to have multiple payment devices associated with a single PAN, which is often desired. Accordingly, the one PAN for each payment device is not a workable solution. 
     In accordance with embodiments of the invention, the solution is to give each separate card (or other payment device) its own unique number or some other indicia. Such unique number might be characterized as a Card Sequence Number (CSN) or a Device Differentiator Number (DDN), for example. As used herein, such number (or other indicia) will be referred to as a “Device Differentiator Number (DDN)”. 
     For example, let&#39;s assume the account (PAN) has 4 purchase devices: (1) a first credit card , (2) a second credit card, (3) a first RFID key fob, and (4) a second RFID key fob. Each of the 4 devices is given its own DDN. Each then maintains its own ATC count, and the card processor also maintains an ATC count for each separate DDN. The card processor can not only keep track of which ATC count each device is on, but can also glean substantial information by telling which particular payment device was used to effect which particular transaction. 
     It is appreciated that while various embodiments of the invention set forth herein include an ATC (Automatic Transaction Counter), e.g., the DDN is used in conjunction with the ATC, such is not needed. Thus, in practice of embodiments of the invention, it is not needed that a particular device utilize, or have, an ATC. For example, in embodiments, a particular device may not use an ATC, but only the DDN as described herein. Thus, the processing of the DDN may or may not be performed in conjunction with (or alongside) the processing of an ATC. As should be appreciated, the utilization of the DDN alone, i.e., without an ATC, lends itself to a wide variety of benefits. 
       FIG. 1  shows one architecture, in accordance with an embodiment of the invention.  FIG. 1  illustrates an overall point of sale architecture that includes a transponder  102  which communicates via an RF link  104  to a receiver  106 . The transponder  102  may be or include any of several known electromagnetically coupled devices, generally activated by proximity to an RF-enabled receiving unit, such as receiver  106 . Transponder  102  may, for instance, contain an electromagnetic coil antenna for inductive coupling to receiver  106 , thereby being energized with small but sufficient electric current to activate embedded electronics within the transponder  102 . Those electronics may include memory such as CMOS memory, logic gates, filters for isolating discrete transmission frequencies and other elements known in the art. In one embodiment, transponder  102  may be programmable and able to receive updated programmable instructions via RF link  104 , as well as to have electronic memory erased or updated during transactions. Receiver  106  may include an electromagnetic antenna to couple with transponder  102 , generally within the range of a few feet of the device. 
     In the embodiment illustrated in  FIG. 1 , the receiver  106  is connected to a point of sale (POS) device  108  for conducting a commercial or other transaction. For instance, the point of sale device  108  may be or include any of several commercially known electronic cash registers or related transaction processing equipment, such as point of sale terminals manufactured by Sharp Corp. or others. In one embodiment of the invention, transponder  102  may be embedded within a personal article for convenience, aesthetic and affinity purposes. In that regard, the invention might be integrated in one implementation within a fully functional watch. Embedding in other personal articles, such as key chains, pagers, clothing or other items is also possible. In the operation of the invention, a user who has subscribed to the account system of the invention may approach the receiver  106  at the point of sale device  108  to initiate and complete a purchase or other transaction, such as at a restaurant or grocery market checkout line, or other points of sale. In the embodiment illustrated in  FIG. 1 , transponder  102  contains an encoded transponder ID  110 , which may for instance be a 5-digit number or other identifying information. In this embodiment, transponder  102  may also store an account table  112  directly recording account information for the subscribed user of the transponder  102 . The account table  112  may be or include, for example, an account number and other information for a debit account, a cash account, a credit card account, special premises account for internal use such as by employees, or other account information associated with users of the system. The account information in the account table may also include a device differentiator number and an automatic transaction counter (ATC) value. 
     In the implementation of this embodiment of the invention, receiver  106  is configured to receive the account table  112  and apply an amount being executed at the point of sale device  108  to the account reflected within the account table  112 . For instance, a patron who has subscribed to an account according to the system of the invention may approach receiver  106  in a restaurant line and wave a watch or other article containing transponder  102  in proximity of the receiver  106 . When transponder  102  comes within range of receiver  106 , transponder  102  may be inductively coupled to the coils of an electromagnetic antenna within receiver  106  inducing electrical energy within transponder  102 , to establish the RF link  104  with the receiver  106 . Upon activation of transponder  102  and radiation of transponder ID  110  to the receiver  106 , the receiver  106  may respond with an acknowledge signal to the transponder  102 . The point of sale device  108  may indicate on a display screen or otherwise that a transaction is ready to be commenced. Once the point of sale device  108  generates total amount due for the transaction, the receiver  106  may interrogate transponder  102  to obtain account table information from account table  112  for application to the sale. 
     For instance, if a patron has purchased a meal in a restaurant line at point of sale device  108 , the total purchase price may be validated for completion of the transaction. Conversely, if the amount of the transaction cannot be validated, the point of sale device  108  may indicate “cash required” or another message that transponder validation or authorization has failed. If the transaction amount is validated, receiver  106  enters the transaction amount and transmits the revised account table  112  information over the RF link  104  to the transponder  102 . A transaction completion signal may be emitted by receiver  106 , which in one embodiment may turn off or decouple the transponder  102  via RF link  104 . 
     In terms of new accounts registration as illustrated in  FIG. 3 , in the invention a network-based activation architecture may be advantageously employed. As shown in the figure, a new user may access a client work station  118  connected via communications link  120  to a registration server  122 . The communications link  120  may be, include or access any one or more of, for instance, the Internet, an intranet, a PAN (Personal Area Network), a LAN (Local Area Network), a WAN (Wide Area Network) or a MAN (Metropolitan Area Network), a frame relay connection, an Advanced Intelligent Network (AIN) connection, a synchronous optical network (SONET) connection, a digital T1, T3 or E1 line, Digital Data Service (DDS) connection, DSL (Digital Subscriber Line) connection, an Ethernet connection, an ISDN (Integrated Services Digital Network) line, a dial-up port such as a V.90, V.34 or V.34bis analog modem connection, a cable modem, an ATM (Asynchronous Transfer Mode) connection, or FDDN (Fiber Distributed Data Networks) or CDDI (Copper Distributed Data Interface) connections. Communications link  120  may furthermore be, include or access any one or more of a WAP (Wireless Application Protocol) link, a GPRS (General Packet Radio Service) link, a GSM (Global System for Mobile Communication) link, a CDMA (Code Division Multiple Access) or TDMA (Time Division Multiple Access) link such as a cellular phone channel, a GPS (Global Positioning System) link, CDPD (cellular digital packet data), a RIM (Research in Motion, Limited) duplex paging type device, a Bluetooth radio link, or an IEEE 1802.11-based radio frequency link. Communications link  120  may yet further be, include or access any one or more of an RS-232 serial connection, an IEEE-1394 (Firewire) connection, an IrDA (infrared) port, a SCSI (Small Computer Serial Interface) connection, a USB (Universal Serial Bus) connection or other wired or wireless, digital or analog interface or connection. 
     The registration server  122  may be or include, for instance, a workstation running the Microsoft Windows™ NT™, Windows™ 2000, Unix, Linux, Xenix, IBM AIX, Hewlett-Packard UX, Novell Netware™, sun Microsystems Solaris™, OS/2™, BeOS™, Mach, Apache, OpenStep™ or other operating system or platform. 
     The registration server  122  may communicate with client workstation  118  to receive preassigned information related to transponder  102 , such as transponder ID  110  which may be printed by sticker on a watch or other article housing the device, for entry into a database  126  within registration server  122  and the setting up of an account. The account may illustratively include or be more than one type of account  124   a  . . .  124   n , such as cash accounts, debit accounts, credit card accounts, special purpose vending accounts, telephone card accounts, or others. The registration server  122  may validate the transponder ID  110 , and interrogate a new subscriber at client work station  118  to identify or select which one or more of accounts  124   a  . . .  124   n  the user wishes to associate with the transponder  102 . 
     For instance, the registration  122  may accept a preexisting credit card number for registration with the transponder  102  and execution of future transactions. Once new account information is established, the registration server  122  may communicate via network connection to receiver  106  to update subscriber registration tables within the database  126 , receiver  106 , point of sale device  108  or other associated hardware to authorize transactions at the point of sale. The paperwork, delay, possibility for error and other drawbacks of paper-based back end account registration is thereby avoided. 
     A second illustrative embodiment of the invention is shown in  FIG. 2 , generally involving a processing architecture similar to that of  FIG. 1 . In this embodiment, a transponder  102  again communicates via RF link  104  with receiver  106  to effectuate point of sale or other transactions. However, in the embodiment of  FIG. 2  a portion or all of account table  112  or other information stored in transponder  102  in the first embodiment may be offloaded to economize on the necessary electronics, power consumption and other properties of transponder  102 . In the embodiment illustrated in  FIG. 2 , the point of sale device  108  is additionally connected to a transaction server  200  via communications link  114 , for the purpose of authorizing in whole or in part transactions presented for payment using transponder  102 . Communications link  114  may be, include or access communications resources similar to communications link  120 . 
     In this embodiment, part or all of the information of account table  112  may be stored in hard disk or other storage  230  of transaction server  200 . Transaction initiation begins in the same manner as the embodiment illustrated in  FIG. 1 , however, after acknowledgments are exchanged between point of sale device  108  and transponder  102  and a transaction is set up, the point of sale device  108  may communicate with transaction server  200  to validate a transaction amount or other information against account information stored in the transaction server  200 . 
     While this implementation involves additional hardware and communications link  114 , if transaction server  200  is co-located with the point of sale device  108 , such as in a restaurant or retail outlet, communication delays may be minimal. Furthermore if the transaction server  200  is dedicated to processing transactions only at the site of point of sale device  108  or closely grouped facilities, processing burdens may be comparatively modest. In another embodiment of the invention, transaction server  200  may communicate with remote credit file databases or other information resources before authorizing or completing a transaction initiated over RF link  104  at receiver  106 , when circumstances may permit some execution delay to be acceptable. 
     Alternatively, in another embodiment of the invention the point of sale device  108  may perform a preliminary authorization for transactions presented at the receiver  106 , to collect and temporarily store transactions, for instance over2 or 3 hour periods, for batch processing remotely via transaction server  200 . Since the majority of transactions typically reconcile without difficulty, this implementation permits more-immediate completion while still checking on account validations at frequent intervals. 
     Overall transaction processing is illustrated in the flowchart of  FIG. 4 . In step  402 , processing begins. In step  404 , the receiver  106  is presented with transponder  102  within range of electromagnetic coupling, such as inductive coupling. In step  406 , transponder  102  is activated, for instance by inductive energization of its circuitry. In step  408  transponder  102  may communicate transponder ID  110 , which the receiver  106  acknowledges with an acknowledge signal over RF link  104  in step  410 . 
     In step  412 , transaction information is input from the transponder. After step  412 , the process passes to step  413 . 
     In step  413 , an end of transaction signal is sent to transponder  102 . Then, in step  414 , transponder  102  decouples from the receiver  106 . 
     In step  415 , transaction table  112  or other account information may be interrogated to determine whether account parameters permit the pending transaction at the point of sale device  108 , i.e., a validation process is performed on the transaction. If the transaction is not validated, then in step  416  a “cash required” or other message is signaled at point of sale device  108 , and processing proceeds to step  424  whole processing ends. 
     If the account to be applied to the pending transaction is validated at step  414 , in step  418 , the point of sale device  108  and receiver  106  communicate with transponder  102  to indicate transaction acceptance, and modify information within account table  112  if appropriate. In step  424 , processing ends. 
     The foregoing description of the system and method for transponder-activated transactions is illustrative, and variations in configuration and implementation will occur to persons skilled in the art. For instance, while transponder  102  has been described as electromagnetically coupling with the receiver  106 , or other types of detection and coupling could be used. For instance, an infrared device, a biometrically enabled or other device may be presented to corresponding detecting apparatus at the point of sale. Similarly, transponder  102  may contain or store other types or forms of information other than transponder ID  110  and account table  112 . 
     In general, in implementation of the various embodiments of the invention, any type of arrangement may be used to transmit information from the payment device to an transaction processing system. For example, an RF or RFID interface may be used as described herein, as well as any other suitable wireless interface might be used. Other interface arrangements that might be used to communicate information between the payment device and the transaction processing system include a bar code reader, a magnetic stripe reader, a hologram reader, any other visual identifier and associated reader, a key entry device, the Internet or any other computer network, any point of sale (POS) device and/or a phone network or any other communication network or arrangement, for example. 
     Hereinafter, further details of the architecture and processing of the transaction server  200  will be described in accordance with embodiments of the invention. In particular, aspects of processing by the transaction server  200  relating to the device differentiator number (DDN) will be described. For example, each transponder  102  may be associated with a particular device differentiator number. 
     As described herein, the transaction server  200  performs authorization processing for transactions presented for payment using transponder  102 . This authorization is performed at the transaction server  200 .  FIG. 6  is a block diagram showing further details of the transaction server  200  in accordance with one embodiment of the invention. 
     As shown in  FIG. 6 , the transaction server  200  includes a processing portion  210 . The processing portion  210  performs a variety of processing in the transaction server  200 . For example, such processing is related to authorization of a requested transaction and/or monitoring of transactions, for example. The transaction server  200  further includes a memory portion  230 . The memory portion  230  may be in the form of a computer readable medium. The memory portion  230  stores a wide variety of data needed in operation of the transaction server  200 . Such data may relate to accounts of customers, aggregated data and/or behavior information, for example. 
     The processing portion  210  includes a number of processing components. Specifically, the processing portion  210  includes a device identification portion  212 , a register portion  214  and an authentication portion  216 , as well as a monitoring portion  220 . 
     The various processing performed by the components in the processing portion  210  are discussed further below. However, in summary, the device identification portion  212  identifies the device that is associated with a particular requested transaction. The register portion register portion  214  in turn identifies the transaction count value for the particular requested transaction. The authentication portion  216  works in conjunction with the device identification portion  212  and the authentication portion  216  to effect the authentication of the requested transaction. The processing portion  210  also includes the monitoring portion  220 . The monitoring portion  220  analyzes data acquired (from the various transactions that are processed by the transaction server  200 ) for a variety of purposes. For example, the monitoring portion  220  analyzes the data to identify behavior and to prevent fraud. 
     Hereinafter, further aspects of the invention will be described relating to the use of device differentiator numbers and transaction count values, as well as the associated processing of the transaction server. 
     Transactions processed by the system of  FIG. 1  are typically associated with a transaction account. As described herein, transaction accounts have a Primary Account Number (PAN) which is typically the  16  digit number on the card. In the case of accounts having multiple payment devices, (e.g., credit cards having PAN xxxx xxxx xxxx xxxx with husband and wife each having a respective card), each of the multiple cards is the same. However, authentication processing may be complicated by both a husband and wife (or any other multiplicity of persons) using multiple cards off one PAN. Illustratively, this is true in the situation where a counter is utilized to authenticate transactions associated with the card. 
     This also becomes a problem in the context of RFID (Radio Frequency IDentification) based cards like the Chase Blink Card, i.e., the Chase card with Blink. The Blink Card is one embodiment of the transponder  102  of  FIG. 1 . The Blink Card has a magnetic stripe for magnetic stripe processing, as well as an RFID chip for RFID based processing (where one just waves the card past an RFID capable reader). For those RFID based transactions, for example, the card reader (e.g. the receiver  106  of  FIG. 1 ) reads (1) the PAN, (2) expiration date, and (3) discretionary data. All of (1)-(3) are read using the RFID reader off the RFID chip. 
     The discretionary data may include an ATC (Automatic Transaction Counter) which increments for each new transaction. When the cardholder runs a new RFID transaction, the ATC is read and then compared to an ATC value maintained by the card processor (e.g. JP Morgan Chase&#39;s authentication platform). If the derived values do not match, then the transaction is denied. This prevents fraud by a person who somehow reads (or otherwise acquires) the PAN and expiration data. 
     The problem is that in the multiple cards per PAN scenario, each card will have a different ATC count as those cards are used differently. For example, the husband may have an ATC value of 10 on the husband&#39;s card (as a result of making 10 transactions), and the wife has an ATC value of 25 on her card (as a result of making 25 transactions). Both cards are tied to the same PAN account. If the card processor has an ATC value of 25 (my wife&#39;s value) for our PAN, and I use my card which has an ATC of 10, obviously my transaction will not go through. The problem is how does the processor distinguish between the different cards for the PAN? In accordance with embodiments of the invention, the solution is to give each separate card its own device differentiator number (DDN), e.g., let&#39;s assume the account (PAN) has 4 purchase devices: (1) a first Blink card, (2) a second Blink card, (3) a first RFID key fob, and (4) a second RFID key fob. Each of the 4 devices is given its own DDN. Each then maintains its own ATC count, and the card processor also maintains an ATC count for each separate DDN. For example, each DDN may be stored on several bytes on the card and can be a value between 1-9, for example, to allow up to 9 different cards/fobs (or other devices) for the single PAN. It could be just 3 bits, which would allow up to 8 different values for 8 different cards/fobs or other devices. However, any suitable storage medium might be used (of any suitable size) to store the device differentiator number (DDN). For example, more than 9 values might be needed or desired, i.e., any number of values may be provided for, as desired. In general, any suitable number might be used to differentiate a particular payment device. For example, a numbering scheme might be used to uniquely identify the particular payment device, as well as to reflect that the particular payment device is a member of a family of payment devices. For example, the number of payment devices associated with a particular PAN might be reflected in the device differentiator number. 
     In one embodiment, the discretionary data ( 3 ) that is read off the card according to the invention includes (a) the DDN value, and (b) the ATC value. As a result, the authentication platform (based on the DDN) can identify which device was used to run the transaction. In particular, in the transaction server  200  of  FIG. 6 , the device identification portion  212  performs this identification. Accordingly, the authentication platform, and specifically the register portion  214  of  FIG. 6 , will know which ATC value that particular device is on (since the authentication platform retains the last counter it saw from that particular device, for example). In accordance with embodiments of the invention, the device differentiator number (DDN) (assigned to each separate payment device) might be characterized as a static portion, whereas the ATC is the dynamic portion. Once the transaction count value is known for the particular device, based on the device differentiator number, the authentication portion  216  performs authentication processing to determine if the requested transaction should be approved. 
     The solution to the ATC/multiple cards problem provided by the invention has various other significant benefits. One benefit is that the Digital Authentication Code (DAC) security mechanism can be used. 
     When the cardholder uses the card in its RFID mode, a DAC may be utilized and is computed by using a card-specific encryption key to compute a code result based on the ATC value read off the card, and a challenge value issued by the RFID card reader. (The computation of the DAC, which is similar to a hash or message authentication code, may also factor in the PAN and expiration date.) The DAC concept is described in U.S. Pat. No. 6,857,566 and U.S. Publication No. 2005/0121512 (continuation of the &#39;566 patent), both assigned to MasterCard and incorporated herein by reference in their entirety. However, since the DAC works off the ATC value of a particular card or device, utilization of the DAC has been problematic in the multiple users/one PAN situation. However, with each card having its own device differentiator number (DDN) in accord with the invention, the authentication platform can discern between different cards or devices, for example. Accordingly, the authentication platform can determine the parameters upon which the DAC was computed, and in particular, the ATC that was used to compute the DAC. It is of course appreciated that DAC processing, or DAC related processing, is certainly not needed in practice of the invention. Rather, any of a variety of authentication processing might be used. 
     Other benefits of the invention flow from utilization of a respective DDN (assigned to each card/device), and the resulting ability to identify which device effected which transaction. A variety of these benefits may be provided in conjunction with using, or processing, the ATC. For example, through use of a DDN assigned to each separate payment device, the monitoring portion  220  of the transaction server  200  can track statistics on purchasing behavior of each separate cardholder (me versus my wife). In this manner, the device differentiator number (DDN) allows the monitoring portion  220  to granulate purchasing trends amongst various persons having the same PAN. 
     The DDN can further be used for Point of Sale (POS) loyalty purposes. Even though a husband and wife have the same PAN (i.e., plastic number), the monitoring portion  220  can tell that the wife consistently shops at TIFFANY&amp;Co. (versus other comparables), but that the husband shops at a variety of comparable stores. This in turn may allow for more effective target marketing. 
     Utilization of the device differentiator number (DDN) can be used in fraud analysis by the monitoring portion  220 . For example, if a husband and wife are respectively shopping in New York and LA, the card processor can distinguish between the two cards and legitimatize the transactions. 
     Utilization of the device differentiator number (DDN) can assist in channel specific authorization, i.e., by the authentication platform (the authentication portion  216 ) being able to tell which device ran the transaction. For example, a particular PAN might be associated with two payment devices, (1) a credit card with CVV and (2) a cell phone. The authentication portion  216  might be presented with an Internet transaction in which a CVV was presented to the on-line merchant. However, the authentication platform can ascertain whether the transaction was effected by the credit card or the cell phone. If by the cell phone, the authentication platform will know the transaction is fraudulent, i.e., since the cell phone has no CVV associated with it. 
     Further, a particular payment device may indeed have two device differentiator numbers (DDNs). For example, the Blink Card noted herein may have a DDN associated with the magnetic stripe and a DDN associated with RFID chip. As a result, the card processor (JP Morgan Chase) can tell which part of the Blink Card was used in which transaction. This allows various analysis helpful for marketing purposes, e.g., a determination that the RFID part of the Blink card is extensively used for some transactions. 
       FIG. 5  is a diagram showing a validation process utilizing a respective device differentiator number (DDN), assigned to each card, in accordance with one embodiment of the invention. As shown, both husband and wife (Husband Smith and Wife Smith) have their own physical card. Both cards have the same PAN. However, both cards have their own individual device differentiator number (DDN). The diagram illustrates the wife using her card in a transaction, as shown in step  1 . After step  1 , the process of  FIG. 5  passes to step  2 . 
     In step  2 , information is transmitted to the authentication platform including (1) the PAN, (2) expiration date, and (3) discretionary data. The discretionary data includes an automatic transaction counter (ATC) and a device differentiator number (DDN). 
     After step  2 , the process passes to step  3 . In step  3 , the authentication platform receives the transmitted information (1)-(3) and performs processing to authenticate the transaction. Specifically, the authentication platform first identifies which payment device (card H or card W) was used based on the device differentiator number (DDN), i.e., in this case, the authentication platform determines that card W was used. The authentication platform then determines what count (automatic transaction counter) that particular device is on and performs authentication processing based on that particular count. The process then ends with the authentication determination being transmitted back to the merchant, for example. 
     As described herein, a variety of processing and/or analysis can be performed using the device differentiator number (DDN), in addition to the authentication of the transaction. As an alternative to ATC (Automatic Transaction Counter), other authentication techniques may of course be used, e.g. such as time based authentication. However, the device differentiator number (DDN) described herein may well be used in the situation where the device differentiator number (DDN) is not needed for authentication, i.e., for the various other benefits as described herein. 
     As described in various embodiments herein, a device differentiator number is used to identify a particular payment device in the field. In such embodiments, further features may be implemented that apply particular rules to the authorization processing associated with a payment device. 
     In accordance with one embodiment of the invention, different rules may be applied to different devices associated with a particular PAN. Use of a particular payment device associated with a PAN may thus be controlled vis-a-vis another payment device associated with the same PAN. For example, the rules may limit which device may be used at which merchant or which type of merchant. Thus, a primary user of a first payment device associated with a PAN may have unlimited use of the PAN. However, the rules associated with a second payment device (provided to an assistant of the primary user) might only allow the assistant to shop at office supply stores, for example. This processing controlling which payment device may be used at which merchants may work off of existing merchant category codes (MCCs), for example, i.e., to determine at which store a customer is shopping. The rules associated with various payment devices (which are associated with the same PAN) may be varied as desired. Rules may hold for all the payment devices associated with a particular PAN, or alternatively, particular rules may apply to only some of the payment devices associated with a particular PAN. 
     In accordance with one embodiment of the invention, the rules associated with respective payment devices may differentially control the time of day that the particular payment device is usable. Further, the rules may control the amount of funds that are drawn using a particular payment device. For example, an assistant of the main cardholder is only allowed to spend $500 per day. 
     As described herein, the rules associated with a particular device may provide channel control. That is, a particular device may only be usable via a particular channel or channels. Accordingly, a transaction is denied if a request for the transaction comes through on a channel on which the particular device cannot operate. For example, if a Blink enabled device submits a request via an Internet channel, the rules might dictate for the transaction processing system to decline that transaction (the assumption being that the transaction is fraudulent). The rules controlling the channel control may be varied as desired. 
     Related to the channel control, in accordance with one embodiment of the invention, an alert system may be used in conjunction with excessive denials associated with the channel control. That is, the transaction processing system may watch for a high rate of denials on a particular channel. Such a high rate of failure may be indicative that indeed such requested transactions are not fraudulent. For example, a new technology might have come on-line which allows a particular payment device to operate on a channel that was previously not possible. The authentication system might then be adjusted to legitimize such transactions. 
     In accordance with embodiments of the invention, trend tracking is provided to track use of a particular payment device. For example, a user might always have used a payment device on a particular channel. Accordingly, the transaction processing system may be provided to identify a change in the normal channel used by a payment device. Any of a wide variety of other trend tracking capabilities may be utilized based on the capability to distinguish between different payment devices. 
     Further, an alert system may be used that tracks a particular payment device for particular criteria. The particular criteria to trigger the alert, as well as the manner in which the alert is reported out, may be varied as desired. For example, if a child spends more than $50 in a day (using the child&#39;s payment device), the parent might be alerted via a cell phone call. Alternatively, the parent might be suitably alerted if the child shops at a particular type of merchant, e.g. a liquor store. 
       FIG. 7  is a flow chart showing further aspects of transaction processing in accordance with one embodiment of the invention. In particular,  FIG. 7  shows aspects of channel monitoring in accordance with one embodiment of the invention. As shown, the process starts in step  700  and passes to step  710 . In step  710 , in this example, the card information is read via a magnetic stripe. In step  720  the card information (including the DDN) is input into the transaction processing system. 
     In step  730  the particular channel that the request came in on is determined. Further, the process determines if such channel is irregular for that particular payment device. If it is indeed an irregular channel, an alert is initiated. The alert might be in the form of a call to the customer home number. For example, if the transaction request was for an Internet purchase (and the submitted DDN is associated with a device that cannot do Internet transactions), then an alert would be initiated. 
     After step  730 , the process passes to step  740 . In step  740 , if the channel is irregular, the process determines if there are an excessive number of denials on a particular channel. If yes, the process considers adjusting the denial criteria. That is, it might be the case that new technology has come to market that provides use of a device on a new channel, i.e., a channel which was not previously usable by the particular device. By monitoring excessive denials on a particular channel and/or for a particular device type, the use of such new technology by a customer might be identified, and the system adjusted appropriately. 
     After step  740  of  FIG. 7 , the process passes to step  750 . In step  750 , the process determines, based on the particular payment device used (as identified by the DDN), whether the transaction satisfies any rules associated with that particular payment device. Then, in step  760 , the process determines, based on the particular payment device used, whether the transaction triggers any alerts associated with that particular payment device. For example, the DDN might be associated with the daughter&#39;s credit card, and once a dollar amount is attained, an alert is sent to the parent&#39;s. In step  770 , the process grants or denies the transaction based on whether criteria are satisfied, i.e., is the request authorized 
     Hereinafter, further aspects of embodiments will be described. As described herein, discretionary data may include an ATC (Automatic Transaction Counter) which increments for each new transaction. It is appreciated that the ATC of a particular payment device may be inadvertently incremented so as to be out of synchrony with the transaction processing system (and the authentication performed thereby). For example, a payment device may be inadvertently read or energized so as to inadvertently increment the ATC of such payment device. Accordingly, the transaction processing system may be provided with a processing capability to accommodate such inadvertent incrementation of the ATC. For example, if an ATC value for a transaction is not valid, the transaction processing system might look ahead, i.e., increment, several values to determine if such ATC values might result in validation of the transaction. 
     In summary of aspects of the invention, and in explanation of yet further features,  FIG. 8  is diagram showing use of multiple device differentiator numbers with one PAN in accordance with one embodiment of the invention. 
     As illustrated in  FIG. 8 , one PAN  802  is associated with a plurality of devices ( 810 - 818 ), i.e., any of the devices ( 810 - 818 ) may be used by the customer (or the customer&#39;s family) to access funds in the PAN account. This association is accomplished using a respective device differentiator number for each device ( 810 - 818 ). In requesting a transaction, the device differentiator number (associated with the particular device used) is sent to the authenticating entity along with the ATC (Automatic Transaction Counter) for the particular device. Typically, the PAN is also forwarded with a transaction request. As described in detail above, based on the PAN and the DDN submitted, the authenticating entity determines whether the ATC (also submitted) is valid. Accordingly, in accordance with one embodiment of the invention, any of a wide variety of devices may be used so long as such devices may provide the ATC, the DDN and the PAN values (or information by which the ATC, the DDN and the PAN are derivable). However, as described herein, devices that do not use an ATC may also be utilized, i.e., so as to realize the various benefits associated with use of a DDN, without an ATC. 
     For example, as described above, typically, the PAN is also forwarded with a transaction request. However, this may not always be the case. For example, the PAN might be somehow suitably derived from other information contained in the request. For example, a single PAN might be associated with a particular phone number, and thus derivable by the authenticating entity based on the phone number as described, for example, in U.S. Pat. 7,103,576 (U.S. patent application Ser. No. 09/956,997). Accordingly, the features described in U.S. Pat. No. 7,103,576 may be used in conjunction with the features described herein. 
       FIG. 8  shows illustrative devices which might be used in the practice of the invention. For example, the DDN  0001 I is associated with the internet browser  810  of the customer&#39;s computer. That is, when the customer (or a member of the customer&#39;s family) submits a transaction using the browser  810 , the ATC, the DDN and the PAN is submitted in some suitable manner, such as by the user typing in such information and/or through use of a cookie on the customer&#39;s computer, for example. Alternatively, the customer might use a password protected applet  811  on the same physical computer to submit a transaction request associated with the DDN  002 I. Each of these are considered a “device” having an associated device differentiator number (DDN), i.e., so the authenticating entity can determine which device was used. In turn, the authenticating entity can separately track (and separately report in a statement to the customer) transaction activity associated with the two devices  810 ,  811 ). 
       FIG. 8  also shows that the wife&#39;s credit card  812  is associated with the DDN  003 ; the husband&#39;s credit card  813  is associated with the DDN  004 ; the son&#39;s credit card  814  is associated with the DDN  005 ; and the son&#39;s key fob  815  is associated with the DDN  006 . Thus, the authenticating entity can distinguish between purchases made by these respective devices. 
     Further,  FIG. 8  shows that transactions may be submitted using the wife&#39;s cell phone, via devices  816  and  817 . For example, the DDN  007  may be verbally conveyed by the wife in a telephone call, the PAN identified from the incoming cell phone number, and the ATC conveyed by the output of a suitable tone. The physical phone might also contain an RFID device, which is associated with a separate DDN ( 008 ). 
     Lastly, the DDN  009  is shown as associated with a dog&#39;s RFID device. Such device might be used when the dog is placed in a kennel, for example. The user could drop off and pick up the dog without ever dealing with any sign-in sheet or other administrative matter. Rather, the dog&#39;s presence would be tracked via interface with the RFID device  818 . 
     It is appreciated that a wide variety of devices may be used. Each device may be associated with its own DDN. For example, an RFID device (with DDN) might be provided to interact with a gasoline filling station, such as an automobile, boat or personal watercraft filling station. 
       FIG. 8  also illustrates, as described above, that particular rules might be associated with particular DDNs, i.e., particular devices associated with the particular DDNs. For example, as shown, a rule set might be applied to the DDNs  005  and  006  to limit spending activity of a son. 
       FIG. 8  also shows that the form of the DDN may vary as desired. For example, the DDN  001 I denotes, for example, that such DDN is associated with a device that is expected to effect Internet transactions. The dog&#39;s RFID device  818 , on the other hand, is not expected to effect Internet transactions. Thus, an Internet transaction submitted using the PAN  802  with the DDN  009  would be flagged as potentially fraudulent. 
     In accordance with one embodiment of the invention, a customer may be provided with the ability to vary the rules associated with some or all of the DDNs associated with their PAN. In one embodiment, the user might vary the rules based on rule level. For example, all the devices (DDNs) of the customer personally might be considered to be at a first level. On the other hand, all the devices of the customer&#39;s son might be considered to be at a second level. Accordingly, the customer might collectively vary the rules at either the first or second level. For example, at the second level, the customer might collectively change all the son&#39;s devices (as identified by the authenticating entity using the DDNs) to have a maximum per day limit of $100 versus $50. 
     In accordance with one embodiment of the invention, the ability to uniquely identify a particular payment device (based on information submitted in the transaction request) allows the ability to segregate purchases associated with a particular PAN based on which payment device effected the particular purchase. That is, in a typical situation, several payment devices will be associated with a single PAN. The primary account holder (or a representative thereof) will typically receive a monthly statement of all the transactions associated with the particular PAN. The invention allows segregation of the transactions (in a statement) based on which payment device effected the transaction. This segregation may be performed in a variety of ways as desired. For example, all the transactions associated with all the primary account holders payment devices may be set out in one listing, while the transactions effected by the children&#39;s payment devices may be set out in a separate listing. The particular arrangement may be varied as desired. For example, if electronically viewed (such as over the Internet) various view options may be provided as desired. The various views may segregate the transactions (based on which payment device effected the transaction) in any manner desired. The user would then be provided suitable options to select which view the user wishes to review. 
     It will be readily understood by those persons skilled in the art that the present invention is susceptible to broad utility and application. Many embodiments and adaptations of the present invention other than those herein described, as well as many variations, modifications and equivalent arrangements, will be apparent from or reasonably suggested by the present invention and foregoing description thereof, without departing from the substance or scope of the invention. 
     Accordingly, while the present invention has been described here in detail in relation to its exemplary embodiments, it is to be understood that this disclosure is only illustrative and exemplary of the present invention and is made to provide an enabling disclosure of the invention. Accordingly, the foregoing disclosure is not intended to be construed or to limit the present invention or otherwise to exclude any other such embodiments, adaptations, variations, modifications and equivalent arrangements.

Technology Category: g