Account permanence

Information

  • Patent Grant
  • 10733604
  • Patent Number
    10,733,604
  • Date Filed
    Thursday, August 2, 2018
    5 years ago
  • Date Issued
    Tuesday, August 4, 2020
    3 years ago
  • Inventors
  • Original Assignees
  • Examiners
    • Sterrett; Jonathan G
    Agents
    • Kilpatrick Townsend & Stockton LLP
Abstract
A system and method for using derived account identifiers. The derived account identifiers are associated with a single permanent account identifier. Each derived account identifier is associated with a communication channel or portable consumer device.
Description
BACKGROUND

Transaction cards, such as credit cards, are used to conduct transactions such as payment transactions. A card can be presented in person in order to conduct a transaction (a “card present” transaction). The card can contain an account number. The account number could also be recited over the phone for mail order purchases (a “card not present” transaction). Now, with the rise of cellular telephones, the Internet, and various other communication channels and technologies, account numbers can be used in a number of different ways.


The ubiquity of card transactions and the ease with which they can be made using technology (including in card not present transactions) has led to increased opportunities for fraud. Once fraud has been discovered, the account in question may be suspended and the consumer is issued a new account. The technology does not exist, however, for issuing a replacement account and the means enabling the user to use the replacement account immediately. Instead, the issuance process may take some time, and during this period the consumer cannot use the account over any channel. For example, if a consumer's credit card number is stolen during a card not present transaction, for instance through the use of keylogging software illegally installed on the consumer's computer terminal, the consumer can use the credit card number neither in future card present nor card not present transactions.


Some cards have further identifying features, such as “verification values” or “card security codes,” Verification values are 3- or 4-digit numbers that are printed on the face of a credit card. A verification value is often used in “card not present” transactions. If the verification value and the consumer's account number is stolen, then a thief may use this information to conduct purchases in card not present transactions, for instance transactions made through the Internet or by telephone.


Better methods to secure against fraud are desirable. Embodiments of the invention address these and other problems, individually and collectively.


BRIEF SUMMARY

Embodiments of the invention include assigning a single permanent account to a consumer, and having the consumer use derived account identifiers associated with a particular payment mechanism that the consumer is using. If one payment mechanism is compromised, other payment mechanisms are not compromised.


One embodiment of the invention is directed to a method comprising creating a plurality of derived account identifiers, wherein each derived account identifier is derived from a single permanent account identifier associated with a consumer, and wherein each derived account identifier is associated with a different payment mechanism; and providing the plurality of derived account identifiers to the consumer.


Another embodiment of the invention is directed to a computer readable medium comprising code for creating a plurality of derived account identifiers, wherein each derived account identifier is derived from a single permanent account identifier associated with a consumer, and wherein each derived account identifier is associated with a different payment mechanism; and code for providing the plurality of derived account identifiers to the consumer.


Another embodiment of the invention is directed to a method comprising using a first derived account identifier in a first transaction; using a second derived account identifier in a second transaction; wherein each of the first and second derived account identifiers is associated with a different payment mechanism, and wherein each of the plurality of derived account identifiers is derived from a single permanent account identifier.


Another embodiment of the invention is directed to a plurality of portable consumer devices comprising a first portable consumer device comprising a first derived account identifier; and a second portable consumer device comprising a second derived account identifier, wherein the first and second derived account identifiers are derived from a single permanent account identifier.


Another embodiment of the invention is directed to a method comprising receiving an authorization request message comprising a derived account identifier, wherein the first derived account identifier is associated with a specific payment mechanism, and wherein the derived account identifier is associated with a single permanent account identifier; determining the single permanent account identifier associated with the derived account identifier; and forwarding the authorization request message to an issuer using the single permanent account identifier.


Another embodiment of the invention is directed to a computer readable medium comprising code for receiving an authorization request message comprising a derived account identifier, wherein the derived account identifier is associated with a specific payment mechanism, and wherein the derived account identifier is associated with a single permanent account identifier; code for determining the single permanent account identifier associated with the derived account identifier; and code for forwarding the authorization request message to an issuer using the single permanent account identifier.


These and other embodiments of the invention are described in further detail below with reference to the drawings and the Detailed Description.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of a system according to an embodiment of the invention.



FIG. 2 is a block diagram of a portable consumer device that can be in the form of a phone.



FIG. 3 is a block diagram of a portable consumer device in the form of a payment card.



FIG. 4 is a block diagram of an access device according to an embodiment of the invention.



FIG. 5 is a diagram showing the relationship between a permanent account and derived accounts according to an embodiment of the invention.



FIG. 6 is a flowchart illustrating a method according to an embodiment of the invention.



FIG. 7 is a flowchart illustrating a method according to an embodiment of the invention.





DETAILED DESCRIPTION

Embodiments of the invention can be used in a transaction environment that contains multiple payment mechanisms. As used herein, a “payment mechanism” can mean the agency or means by which a transaction is produced or is accomplished. Payment mechanism may include all various communication channels and portable consumer devices. A transaction can occur over any payment mechanism, Examples of various payment mechanisms may include transactions over the Internet, transactions using a payment card such as a credit card, transactions conducted over a telephone, and the like.


A “communication channel” is a subcategory of payment mechanism, and may include various ways of conducting a transaction using different components and/or communication paths. Examples of various communication channels include a channel including an access device or point-of-sale (POS) terminal (such as with a credit card), a merchant, an acquirer associated with the merchant, a payment processing organization, and an issuer; a channel associated with payment over the Internet; a channel associated with cellular telephone network (e.g., where payment is made via a cellular phone), etc.


A “portable consumer device” is a subcategory of payment mechanism, and may include a specific device that is being used to conduct a payment transaction. “Portable consumer devices” may include key fobs, payment cards, wireless phones, etc. A more detailed description of portable consumer devices is provided below.


In a conventional process, an issuer would issue a consumer a payment card such as a credit card. It would have an account number, an expiration date and a CVV2 value associated with it. The account number, the expiration date, and the CVV2 value would be used for both card present and card not present transactions. It may also be used with the consumer's cellular phone if the consumer's cellular phone is used to conduct payment transactions.


In embodiments of the invention, a consumer is assigned a single permanent account identifier for an account. In certain embodiments, this identifier is not directly used to conduct transactions between the customer and merchants. It can be a permanent identifier the consumer can use to reference the consumer's account. When purchase transactions are conducted, the consumer can use derived account identifiers. Each payment mechanism that is used by the consumer can have its own, separate, derived account identifier. The derived account identifiers can be associated with the single permanent account identifier, but they may be different.


As used herein, a derived account identifier may be an account identifier that is associated with the single permanent account identifier. The derived account identifier may be associated to the single permanent account identifier through a look up table, by means of sharing certain characteristics, by means of manipulating the single permanent account identifier through mathematical or other formulas to create the derived account identifiers, or by other suitable means. In some embodiments, the permanent account identifier may include a permanent account number that does not change (e.g., 1234567812345678). Derived account identifiers may include one or more pieces of information associated with the permanent account identifier. For example, an exemplary first derived account identifier may include the permanent account number, a first expiration date, and a first verification value. An exemplary second derived account identifier may include the permanent account number, a second expiration date, and a second verification value.


In embodiments of the invention, consumers use each derived account identifier only in coordination with the associated payment mechanism. For example, a consumer may have a single permanent account identifier for a permanent account, and two derived account identifiers: a first one for use with a credit card (the credit card being an instance of a portable consumer device), and a second one for any “card not present” transactions, such as for making purchases over the Internet (the Internet being a communication channel). When the consumer uses the credit card for in-person purchases, such as at a POS terminal, the first derived account identifier on the card is used, and is linked to the permanent account so that any purchases made are debited from the permanent account. Likewise, when shopping over the Internet, the consumer can make purchases from Internet based stores by providing the second derived account identifier to the Internet based stores, Any purchases made in this fashion are debited from the permanent account.


In certain embodiments, each derived account identifier is intended to act much as typical card information currently does. As such, each derived account identifier can be used for multiple transactions or purchases, with different merchants. After each commerce transaction, the account associated with the single permanent account identifier can be adjusted to reflect the transactions. For example, purchases made using a first derived account identifier and a second account identifier can be added together so that a consumer sees only one monthly statement for purchases made using those account identifiers. In this fashion, the consumer may need to maintain only a single account that is linked to the single permanent account identifier, while having the security of using multiple derived account identifiers. Each derived account can expire at some pre-defined time and date, but typically that expiration date is at least several months from the issue date of the derived account identifier. The number of commerce transactions that each derived account is usable for is only limited by the expiration date, and the amount of money or credit limit in the consumer's account.


In embodiments of the invention, if a derived account identifier is intercepted during use and then used in a fraudulent manner, that derived account identifier can be cancelled and a replacement derived account identifier can be issued. The replacement derived account identifier can be associated with the same portable consumer device or communication channel as the cancelled identifier. In this way, the customer can continue making purchases using the channels that have not been compromised, even while waiting for the replacement derived account identifier.


Specific embodiments of the invention can be described with reference to FIGS. 1-7.



FIG. 1 shows a system according to an embodiment of the invention. Other systems according to embodiments of the invention may include fewer or more components than are specifically shown in FIG. 1.



FIG. 1 shows an access device 18, an acquirer 30, a payment processing network 40, and an issuer 42, in operative communication with each other. The acquirer 30 and issuer 42 can communicate through the payment processing network 40. A mobile gateway 38 may also be in communication with the issuer 42 via the payment processing network 40. A computer 60 (e.g., a personal computer) may also be in communication with the issuer 42 via the payment processing network 40.


The acquirer 30 may be a bank that is associated with the access device 18, and the issuer 42 may issue the first and second portable consumer devices 14, 32 to the consumer.


As used herein, an “acquirer” is typically a business entity, e.g., a commercial bank that has a business relationship with a particular merchant or other entity. An “issuer” is typically a business entity (e.g., a bank) which issues a portable consumer device such as a credit or debit card to a consumer. Some entities can perform both issuer and acquirer functions. Embodiments of the invention encompass such single entity issuer-acquirers.


The payment processing network 40 may have a server computer 44, as well as a database 48, The server computer 44 is typically a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a web server.


The payment processing network 40 may comprise or use a payment processing network such as VisaNet™. The payment processing network 40 and any communication network that communicates with the payment processing network 40 may use any other suitable wired or wireless network, including the Internet. The payment processing network 40 may be adapted to process ordinary debit or credit card transactions.


The server computer 44 may comprise or be associated with a computer readable medium comprising code for receiving a derived account identifier, and then determining the single permanent account identifier from the derived account identifier. The computer readable medium may also comprise code for using the single permanent account to route any authorization request message to the appropriate issuer 42.


For simplicity of illustration, one access device 18, one acquirer 30, and one issuer 42 are shown. However, it is understood that in embodiments of the invention, there can be multiple access devices, acquirers, issuers, as well as server computers, databases, accounts, etc.


An exemplary portable consumer device 32′ in the form of a phone may comprise a computer readable medium and a body as shown in FIG. 2. (FIG. 2 shows a number of components, and the portable consumer devices according to embodiments of the invention may comprise any suitable combination or subset of such components.) The computer readable medium 32(b) may be present within the body 32(h), or may be detachable from it. The body 32(h) may be in the form a plastic substrate, housing, or other structure. The computer readable medium 32(b) may be a memory that stores data and may be in any suitable form including a magnetic stripe, a memory chip, etc. The memory preferably stores information such as financial information, transit information (e.g., as in a subway or train pass), access information (e.g., as in access badges), etc. Financial information may include information such as bank account information, bank identification number (BIN), credit or debit card number information, account balance information, expiration date, consumer information such as name, date of birth, etc. Any of this information may be transmitted by the portable consumer device 32′.


In some embodiments, and regardless of the type of portable consumer device that is used, information in the memory may also be in the form of data tracks that are traditionally associated with credits cards. Such tracks include Track 1 and Track 2. Track 1 (“International Air Transport Association”) stores more information than Track 2, and contains the cardholder's name as well as account number and other discretionary data. This track is sometimes used by the airlines when securing reservations with a credit card. Track 2 (“American Banking Association”) is currently most commonly used. This is the track that is read by ATMs and credit card checkers. The ABA (American Banking Association) designed the specifications of this track and all world banks must abide by it. It contains the cardholder's account, encrypted PIN, plus other discretionary data.


The portable consumer device 32′ may further include a contactless element 32(g), which is typically implemented in the form of a semiconductor chip (or other data storage element) with an associated wireless transfer (e.g., data transmission) element, such as an antenna. Contactless element 32(g) is associated with (e.g., embedded within) portable consumer device 32′ and data or control instructions transmitted via a radio or cellular network may be applied to contactless element 32(g) by means of a contactless element interface (not shown). The contactless element interface functions to permit the exchange of data and/or control instructions between the mobile device circuitry (and hence the radio or cellular network) and an optional contactless element 32(g).


Contactless element 32(g) is capable of transferring and receiving data using a near field communications (“NFC”) capability (or near field communications medium) typically in accordance with a standardized protocol or data transfer mechanism (e.g., ISO 14443/NFC). Near field communications capability is a short-range communications capability, such as RFID, Bluetooth™, infra-red, or other data transfer capability that can be used to exchange data between the portable consumer device 32′ and an interrogation device. Thus, the portable consumer device 32′ is capable of communicating and transferring data and/or control instructions via both cellular network and near field communications capability.


The portable consumer device 32′ may also include a processor 32(c) (e.g., a microprocessor) for processing the functions of the portable consumer device 32′ and a display 32(d) to allow a consumer to see phone numbers and other information and messages. The portable consumer device 32′ may further include input elements 32(e) to allow a consumer to input information into the device, a speaker 32(f) to allow the consumer to hear voice communication, music, etc., and a microphone 32(i) to allow the consumer to transmit her voice through the portable consumer device 32′. The portable consumer device 32′ may also include an antenna 32(a) for wireless data transfer (e.g., data transmission).


If the portable consumer device is in the form of a debit, credit, or smartcard, the portable consumer device may also optionally have features such as magnetic strips. Such devices can operate in either a contact or contactless mode.


An example of a portable consumer device 32″ in the form of a card is shown in FIG. 3. FIG. 3 shows a plastic substrate 32(m). A contactless element 32(o) for interfacing with an access device 34 may be present on or embedded within the plastic substrate 32(m). Consumer information 32(p) such as an account number, expiration date, a verification value, and consumer name may be printed or embossed on the card. Also, a magnetic stripe 32(n) may also be on the plastic substrate 32(m).


As shown in FIG. 3, the portable consumer device 32″ may include both a magnetic stripe 32(n) and a contactless element 32(o). In other embodiments, both the magnetic stripe 32(n) and the contactless element 32(o) may be in the portable consumer device 32″. In other embodiments, either the magnetic stripe 32(n) or the contactless element 32(o) may be present in the portable consumer device 32″.



FIG. 4 shows a block diagram showing basic components that may reside in a POS terminal such as access device 18. An exemplary access device 18 may comprise a processor 18(a)-1, a computer readable medium 18(a)-2, a keypad 18(a)-3, a portable consumer device reader 18(a)-4, an output device 18(a)-5, and a network interface 18(a)-6, which can all be operatively coupled to the processor 18(a)-1. Exemplary portable consumer device readers can include RF (radio frequency) antennas, magnetic stripe readers, etc. that interact with the portable consumer device 32, Suitable output devices may include displays and audio output devices. Exemplary computer readable media may include one or more memory chips, disk drives, etc. The network interface 18(a)-6 may allow the access device 18 to send and receive messages from the acquirer 30, payment processing network 40, and/or the issuer 42.


Referring to FIG. 1, according to certain embodiments, each communications channel may be associated with a different derived account identifier. For example, a consumer may have three separate derived account identifiers, one each for a separate communications channel. The consumer may have a first derived account identifier for use with first communications channel 52. In this embodiment, the first communications channel 52 includes the path that is formed by access device 18, and acquirer 30. This communications channel is for purchases made in person. It comprises using a first portable consumer device 14, such as a credit card. First portable consumer device 14 will contain the first derived account identifier, and can be used for transactions in person, such as making purchases at a store.


The consumer may also have a second derived account identifier for use with second derived communications channel 53. In this embodiment, second communications channel 53 includes the path that is formed by mobile gateway 38. This communications channel is for purchases made with an electronic device such as second portable consumer device 32, which may be a cell phone. Second portable consumer device 32 can contain the second derived account identifier, and can be used for transactions.


The consumer may also have a third derived account identifier for use with third communications channel 62. In this embodiment, third communications channel comprises the Internet. This communications channel is for purchases made with devices (such as user computer 60) that are connected to the Internet. User computer 60 may contain the third derived account identifier in a memory storage, or the third derived account identifier may be input into user computer 60 separately for each transaction.


In the above embodiment, each derived account identifier can only be used with its associated channel (i.e., first derived account identifier can only be used with first communications channel 52, second derived account identifier can only be used with second communications channel 53, and third derived account identifier can only be used with third communications channel 62). As in the above example, if the consumer is at a store, this comprises first communications channel 52. As such, if she wishes to make a purchase, she would use first portable consumer device 14 (in this example, a credit card) containing the first derived account identifier, for that purchase. Likewise, if she wishes to make a purchase over the Internet (third communications channel 62), she would use the third derived account identifier.


In the above embodiment, if the first derived account identifier on the first portable consumer device 14 is used in an Internet transaction (i.e., over communication channel 62), that transaction can be rejected by the payment processing network 40 or the issuer 42. Likewise, even if the third derived account identifier is stolen by fraudulent actors while being used in an Internet transaction, it is unusable in any other channel, Commonly in fraud situations, the fraudulent actors will take stolen credit card information and create a physical card to use for in-person situations. In embodiments of the invention however, the third derived account identifier cannot be used in-person (i.e., it cannot be used with communication channel 52), and so any such transactions can be refused, preventing fraudulent purchases.


Referring to FIG. 1, according to other embodiments, each portable consumer device may be associated with a different derived account identifier derived from a single permanent account identifier associated with the consumer. For example, the first portable consumer device 14 may be a credit card and the second portable consumer device 32 may be a key-fob, and each may be associated with a separate derived account identifier.


In this example, the first portable consumer device 14 and the second portable consumer device 32 may be associated with first and second derived account identifiers. The first and second account identifiers may be derived from a single permanent account identifier associated with the consumer. Therefore in this example, the credit card 14 may contain or be associated with the first derived account identifier, and the key-fob 32 may contain or be associated with the second derived account identifier. In this embodiment, for the consumer to consummate a transaction, she must use a portable consumer device that contains the correct derived account identifier (i.e., the identifier that is associated with the portable device being used).


In alternative embodiments, several communication channels may share the same derived account identifiers and/or portable consumer devices. In one implementation, in FIG. 1, third communication channel 62 may be associated with a first derived account identifier, and the first and second communication channels 52 and 53 may be associated with a second derived account identifier. For example, third communication channel 62 may be for transactions that take place over the Internet. Using this third communication channel 62, the consumer inputs the first derived account identifier when making purchases. First and second communication channels 52 and 53 may be for transactions using a first portable consumer device 14 (such as a credit card) and a second portable consumer device 32 (such as a cellular telephone), respectively. Both the first portable consumer device 14 and the second portable consumer device 32 may contain the same second derived account identifier in this example.


Embodiments of the invention contemplate that different communication channels and portable consumer devices may contain various combinations of derived account identifiers as may be desirable. In other embodiments, a communication channel or portable consumer device may be associated with more than a single derived account identifier. For example, a consumer may be given several derived account identifiers, all for use in Internet transactions. Or the consumer may be provided with several credit cards, each containing a different derived account identifier. The amount of derived account identifiers provided to a consumer, and to which portable consumer devices and communication channels they are associated with, can vary depending on the needs of the issuer, the consumer, or the payment processing network.



FIG. 5 shows the relationship between derived account identifiers and a single permanent account identifier according to an embodiment of the invention, and how the derived account identifiers are created from the single permanent account identifier. This process of derivation is according to a preferred embodiment of the invention. Permanent account identifier 51 may include a base account number 50, which in this implementation is the numeral string 0123456789. The derived account identifiers in this example, each comprise three parts. First derived account identifier 51(a) comprises a first account number 50(a), which may be the same as the base account number 50, a first verification value 54(a), and a first expiration date 55(a). Second derived account identifier 51(b) comprises a second account number 50(b), which may be the same as the base account number 50, a second verification value 54(b), and a second expiration date 55(b). In this embodiment, the base account numbers 50(a) and 50(b) of the first and second derived account identifiers 51(a), 51(b) are identical to the base account number 50 of the permanent account identifier 51. What has been varied is the other parts of the derived account identifiers 51(a), 51(b), namely the verification values (54(a) and 54(b)) and the expiration dates (55(a) and 55(b)). The parts of the derived identifiers may be assigned by the issuer or an organization associated with the payment processing network, once the base number 50 of the permanent account identifier 51 has been assigned. By way of example, expiration date 55(a) may be October, 2009, and expiration date 55(b) may be February 2010. Verification value 54(a) may be the number 012, and verification value 54(b) may be the number 789.


Each of the derived account identifiers is associated with its own communication channel or portable consumer device. Derived account identifier 51(a) can be associated with first communication channel 52, and derived account identifier 51(b) can be associated with second communication channel 62. Both 52 and 62 may be any type of channel. For example, as with FIG. 1, first communication channel 52 may be a channel for in person transactions, and second communications channel 62 may be for transactions that take place over the Internet. Transactions over communication channel 52 may be performed using a portable consumer device 14, such as a credit card. For transactions over this first communication channel 52, first account number 50(a) can be the same as the base account number 50, and the first verification value 51(a) and first expiration date 54(a) are printed on the portable consumer device 14. When the consumer wishes to make a transaction over the second communications channel 62, she can use the second derived account identifier 51(b), In this case, she can use base account number 50(b) as the credit card number that is requested by an Internet store, and enter the second verification value 54(b) and the second expiration date 55(b) onto any website forms, to make a purchase over the Internet.


Assigning each derived account identifier with a unique expiration date and verification value, while keeping the same base number as the single permanent account identifier, is a simple yet novel way to create many unique derived account identifiers that can all be associated with the single permanent account identifier. A credit card number with a missing or incorrect expiration date may not be accepted for use in purchase transactions. As such, even if one derived account identifier is discovered and used in fraudulent transactions, any other related derived account identifiers are not compromised.


In the embodiments discussed above, the derived account numbers and the base account number are the same. In other embodiments, the derived account numbers may be different than the base account number. In such embodiments, the derivation of derived account numbers from the permanent account identifier may occur using any other suitable process. The process of derivation can include combining numbers and letters together without alteration, manipulating numbers using a mathematical formula, etc. For example, a permanent account identifier such as 1234567812345678 may be altered to three different derived account identifiers by multiplying the permanent identifier by 3, 6, and 9, respectively and taking the 16 rightmost digits. The three derived numbers could be used for three different payment mechanisms that the consumer might use (e.g., a first one including a POS terminal, a second one using a mobile gateway, and a third one using an Internet connection.


In one exemplary embodiment, the payment processing network 40 may generate the single permanent account identifier and corresponding derived account identifiers. In this case, the derived account identifiers would be provided to the issuer 42. In another embodiment, issuer 42 may generate the single permanent account identifier and the derived account identifiers. The derived account identifiers would then be communicated to the payment processing network 40. In a further embodiment, issuer 42 may generate the single permanent account identifier and provide it to payment processing network 40. Payment processing network 40 would then create the associated derived account identifiers from the provided single permanent account identifier.


A method of performing an embodiment of the invention is detailed in FIG. 6. In step 202, an issuer or an organization associated with a payment processing network can generate a permanent account identifier, and assign the permanent account identifier to a consumer. This permanent account identifier may be used to reference the consumer's account with the issuer or organization. For example, the consumer may open up a credit card account with an issuer such as a bank. The bank will then generate a permanent account identifier and use that as the credit card account number. Then in step 204, the issuer or organization will generate, from the permanent account identifier, a plurality of different derived account identifiers for each of the communication channels and/or portable consumer devices that a consumer might use. These identifiers then will be provided to the consumer.


The derived account identifiers that have been generated are then associated with separate communication channels or portable consumer devices. For example, as explained above, a first derived account identifier can be assigned to a first portable consumer device, a second derived account identifier can be assigned to a second portable consumer device, and a third derived account identifier can be assigned for the consumer to use when the consumer uses a computer in a “card not present” type of transaction.


Each derived account identifier can then be used in conjunction with its associated communication channel or portable consumer device. The consumer can use any of the derived account identifiers that she was provided for commerce transactions, as seen in step 206 and as shown above.


The issuer or organization can monitor to see if any of the derived account identifiers have expired or been compromised. This is shown in step 208. If that answer is “No”, i.e. none of the derived account identifiers have expired or been compromised, the consumer may keep using all of them as in step 206, If that answer is “Yes”, i.e. a derived account identifier has expired or has been compromised, then the expired or compromised identifier may be cancelled and made unusable by the consumer. The issuer or organization can create a replacement derived account identifier to replace the cancelled ones in step 210, and associate them with the communication channels or portable consumer devices that had previously been associated with the cancelled derived account identifiers. Once this happens, the consumer may use the new derived account identifier in place of the cancelled one, as in step 206.


The method of using the invention according to one embodiment is shown in FIG. 7. The reference numbers used below refer to the steps in FIG. 7, and the components in FIG. 1. In this embodiment, a consumer has been assigned a single permanent account identifier, and has been provided with a plurality of derived account identifiers. Each derived account identifier is associated with a specific type or category of communication channel or portable consumer device. In step 302, the consumer can use a first portable consumer device 14 at a merchant that has a POS terminal (which is an example of access device 18), The first portable consumer device 14 may be in the form of a card. The first portable consumer device is associated with a first derived account identifier. The POS terminal can generate an authorization request message in step 304, which includes information in the first derived account identifier. It is then sent to the acquirer 30, and then to the payment processing network 40. A server computer 44 in the payment processing network 40 can then use a lookup table or the like in a database 48 to identify the single permanent account identifier associated with the first derived account identifier in Step 306. The single permanent account identifier may include the correct BIN or bank identification number for the issuer 42. In step 308, the payment processing network 40 then sends the authorization request message to the appropriate issuer 42.


Then, in step 310, the issuer 42 determines whether or not the transaction is authorized. The issuer 42 may authorize the transaction if there is sufficient credit and/or funds in the consumer's account. The issuer 42 may not authorize the transaction if there is insufficient credit or funds.


The issuer 42 then generates an authorization response message that is sent back to the POS terminal via the payment processing network 40, in step 312. During this step, the payment processing network 40 may convert the single permanent account identifier back to the first derived account identifier information. The authorization response message is received by the POS terminal, which can inform the consumer as to whether or not the transaction has been approved.


After the transaction is approved, a normal clearing and settlement process can take place, in step 314.


Then, the consumer may conduct a second transaction, at a POS terminal in step 316 using a second portable consumer device The second portable consumer device used in the second transaction can be associated with a second derived account identifier. For example, the second portable consumer device may be in the form of a wireless phone with a contactless communication element. The second transaction may be conducted with a second portable consumer device (and a second derived account identifier that is associated with the second portable consumer device). The POS terminal for the second transaction may be a different terminal from the one in the first transaction, or it may be the same terminal. The process for this second transaction is substantially similar to the process in the first transaction. In step 318, the POS terminal sends an authorization message that includes the derived account identifier used in the second transaction, to the payment processing network 40. The payment processing network determines the permanent account identifier in step 320, and forwards the authorization request message to the issuer 42 in step 322. The issuer 42 determines if the transaction is authorized in step 324, using the same criteria as in step 310.


The issuer 42 then generates an authorization response message that is sent back to the POS terminal via the payment processing network 40, in step 326. The authorization response message may include the derived account identifier used in the second transaction. It is then received by the POS terminal, which can inform the consumer as to whether or not the transaction has been approved. Clearing and settlement then takes place in step 328. Further transactions can subsequently be conducted using the same derived account identifier, or other derived account identifiers in the same manner (e.g., using an authorization request message) as described above in steps 302-328.


Embodiments of the invention have a number of advantages. For example, the permanent account number associated with the consumer is not exposed out in the open at any time in some embodiments. Further, even if one derived account identifier is compromised, the single permanent account identifier and the other derived account identifiers are not compromised. Also, this invention improves the ability of issuers to retain its holders (e.g., cardholders). In certain embodiments, the single permanent account identifier is not required to have an expiration date, and it is possible to keep the consumer associated with the account for life. Further, in embodiments of the invention, even if a derived account identifier associated with one channel or portable consumer device is cancelled, other account identifiers associated with other channels or devices may be used. Thus, the cancellation of one derived account identifier does not mean that all account identifiers become inactive.


Embodiments of the invention are not limited to the above-described embodiments. For example, although separate functional blocks are shown for an issuer, payment processing system, and acquirer, some entities perform all of these functions and may be included in embodiments of invention.


It should be understood that the present invention as described above can be implemented in the form of control logic using computer software in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art can know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software


Any of the software components or functions described in this application, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.


The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.


One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention.


A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary, A recitation of “she” is meant to be gender neutral, and may be read as “he” or “she”, unless specifically indicated to the contrary.


All patents, patent applications, publications, and descriptions mentioned above are herein incorporated by reference in their entirety for all purposes. None is admitted to be prior art.

Claims
  • 1. A method comprising: receiving, by a computer, a first authorization request message for a first transaction comprising a first derived account identifier from an access device, the first derived account identifier being one of a plurality of derived account identifiers associated with different payment mechanisms, wherein the first derived account identifier is associated with a permanent account identifier, wherein the first derived account identifier can only be used with a first payment mechanism;determining, by the computer and during the first transaction, that the first derived account identifier is being used with the first payment mechanism and not with another type of payment mechanism;in response to determining that the first derived account identifier is being used with the first payment mechanism, accessing, by the computer, a database of derived and permanent account identifiers to identify the permanent account identifier associated with the first derived account identifier;exchanging, by the computer, the first derived account identifier in the first authorization request message with the permanent account identifier in the first authorization request message;forwarding, by the computer and during the first transaction, the first authorization request message including the permanent account identifier to an issuer for approval;receiving, by the computer, a second authorization request message for a second transaction comprising a second derived account identifier from a mobile phone, the second derived account identifier being one of a plurality of derived account identifiers associated with different payment mechanisms, wherein the second derived account identifier is associated with the permanent account identifier, wherein the second derived account identifier can only be used with a second payment mechanism;determining, by the computer and during the second transaction, that the second derived account identifier is being used with the second payment mechanism and not with another type of payment mechanism;in response to determining that the second derived account identifier is being used with the second payment mechanism, accessing, by the computer, the database of derived and permanent account identifiers to identify the permanent account identifier associated with the second derived account identifier;exchanging, by the computer, the second derived account identifier in the second authorization request message with the permanent account identifier in the second authorization request message; andforwarding, by the computer and during the second transaction, the second authorization request message including the permanent account identifier to the issuer for approval.
  • 2. The method of claim 1, wherein the computer is in a payment processing network located between a plurality of acquirers and issuers.
  • 3. The method of claim 1, wherein the access device receives the first derived account identifier from a payment card which stores the first derived account identifier.
  • 4. The method of claim 1, wherein the first and second derived account identifiers are formed by mathematically altering the permanent account identifier.
  • 5. The method of claim 1, wherein the access device is a point of sale terminal.
  • 6. The method of claim 1, the mobile phone is a cellular phone.
  • 7. The method of claim 1, wherein the first authorization request message is received from the access device via an acquirer.
  • 8. The method of claim 1, wherein the mobile phone comprises a contactless element.
  • 9. The method of claim 1, further comprising: receiving an authorization response message comprising the permanent account identifier from the issuer;modifying the authorization response message to replace the permanent account identifier with the first derived account identifier; andtransmitting the modified authorization response message to the access device.
  • 10. The method of claim 9, wherein the authorization response message is a first authorization response message, and the modified authorization response message is a first modified authorization response message, and the method further comprises: receiving a second authorization response message comprising the permanent account identifier from the issuer;modifying the second authorization response message to replace the permanent account identifier with the second derived account identifier; andtransmitting the modified second authorization response message to the mobile phone.
  • 11. A computer comprising: a processor; anda computer readable medium, the computer readable medium comprising code, executable by the processor, for implementing a method comprising:receiving, by the computer, a first authorization request message for a first transaction comprising a first derived account identifier from an access device, the first derived account identifier being one of a plurality of derived account identifiers associated with different payment mechanisms, wherein the first derived account identifier is associated with a permanent account identifier, wherein the first derived account identifier can only be used with a first payment mechanism;determining, by the computer and during the first transaction, that the first derived account identifier is being used with the first payment mechanism and not with another type of payment mechanism;in response to determining that the first derived account identifier is being used with the first payment mechanism, accessing, by the computer, a database of derived and permanent account identifiers to identify the permanent account identifier associated with the first derived account identifier;exchanging, by the computer, the first derived account identifier in the first authorization request message with the permanent account identifier in the first authorization request message;forwarding, by the computer and during the first transaction, the first authorization request message including the permanent account identifier to an issuer for approval;receiving, by the computer, a second authorization request message for a second transaction comprising a second derived account identifier from a mobile phone, the second derived account identifier being one of a plurality of derived account identifiers associated with different payment mechanisms, wherein the second derived account identifier is associated with the permanent account identifier, wherein the second derived account identifier can only be used with a second payment mechanism;determining, by the computer and during the second transaction, that the second derived account identifier is being used with the second payment mechanism and not with another type of payment mechanism;in response to determining that the second derived account identifier is being used with the second payment mechanism, accessing, by the computer, the database of derived and permanent account identifiers to identify the permanent account identifier associated with the second derived account identifier;exchanging, by the computer, the second derived account identifier in the second authorization request message with the permanent account identifier in the second authorization request message; andforwarding, by the computer and during the second transaction, the second authorization request message including the permanent account identifier to the issuer for approval.
  • 12. The computer of claim 11, wherein the computer is in a payment processing network located between a plurality of acquirers and issuers.
  • 13. The computer of claim 11, wherein the access device receives the first derived account identifier from a payment card which stores the first derived account identifier.
  • 14. The computer of claim 11, wherein the first and second derived account identifiers are formed by mathematically altering the permanent account identifier.
  • 15. The computer of claim 11, wherein the access device is a point of sale terminal.
  • 16. The computer of claim 11, the mobile phone is a cellular phone.
  • 17. The computer of claim 11, wherein the first authorization request message is received from the access device via an acquirer.
  • 18. The computer of claim 11, wherein the mobile phone comprises a contactless element.
  • 19. The computer of claim 11, wherein the method further comprises: receiving an authorization response message comprising the permanent account identifier from the issuer;modifying the authorization response message to replace the permanent account identifier with the first derived account identifier; andtransmitting the modified authorization response message to the access device.
  • 20. The computer of claim 19, wherein the authorization response message is a first authorization response message, and the modified authorization response message is a first modified authorization response message, and the method further comprises: receiving a second authorization response message comprising the permanent account identifier from the issuer;modifying the second authorization response message to replace the permanent account identifier with the second derived account identifier; andtransmitting the modified second authorization response message to the mobile phone.
CROSS-REFERENCES TO RELATED APPLICATIONS

This patent application is a continuation application of U.S. patent application Ser. No. 14/306,017, filed on Jun. 16, 2014, which is a continuation application of U.S. patent application Ser. No. 13/460,293, filed on Apr. 30, 2012, now U.S. Pat. No. 8,793,186, which is a continuation of and claims priority to U.S. patent application Ser. No. 13/072,436, filed on Mar. 25, 2011, now U.S. Pat. No. 8,190,523, issued on May 29, 2012, which is a continuation of and claims priority to U.S. patent application Ser. No. 12/205,069, filed on Sep. 5, 2008, now U.S. Pat. No. 7,937,324, issued May 3, 2011, which claims priority to U.S. Provisional Patent Application No. 60/972,088, filed on Sep. 13, 2007, each of which are herein incorporated by reference in their entirety for all purposes.

US Referenced Citations (543)
Number Name Date Kind
5365046 Haymann Nov 1994 A
5613012 Hoffman Mar 1997 A
5781438 Lee Jul 1998 A
5883810 Franklin Mar 1999 A
5953710 Fleming Sep 1999 A
5956699 Wong Sep 1999 A
6000832 Franklin Dec 1999 A
6014635 Harris Jan 2000 A
6044360 Picciallo Mar 2000 A
6163771 Walker Dec 2000 A
6227447 Campisano May 2001 B1
6236981 Hill May 2001 B1
6267292 Walker Jul 2001 B1
6327578 Linehan Dec 2001 B1
6341724 Campisano Jan 2002 B2
6385596 Wiser et al. May 2002 B1
6422462 Cohen Jul 2002 B1
6425523 Shem Ur Jul 2002 B1
6592044 Wong Jul 2003 B1
6636833 Flitcroft Oct 2003 B1
6748367 Lee Jun 2004 B1
6805287 Bishop Oct 2004 B2
6879965 Fung Apr 2005 B2
6891953 Demello et al. May 2005 B1
6901387 Wells May 2005 B2
6931382 Laage Aug 2005 B2
6938019 Uzo Aug 2005 B1
6941285 Sarcanin Sep 2005 B2
6980670 Hoffman Dec 2005 B1
6990470 Hogan Jan 2006 B2
6991157 Bishop Jan 2006 B2
7051929 Li May 2006 B2
7069249 Stolfo Jun 2006 B2
7103576 Mann, III Sep 2006 B2
7113930 Eccles Sep 2006 B2
7136835 Flitcroft Nov 2006 B1
7177835 Walker Feb 2007 B1
7177848 Hogan Feb 2007 B2
7194437 Britto Mar 2007 B1
7209561 Shankar et al. Apr 2007 B1
7264154 Harris Sep 2007 B2
7287692 Patel Oct 2007 B1
7292999 Hobson Nov 2007 B2
7350230 Forrest Mar 2008 B2
7353382 Labrou Apr 2008 B2
7379919 Hogan May 2008 B2
7380710 Brown Jun 2008 B2
RE40444 Linehan Jul 2008 E
7415443 Hobson Aug 2008 B2
7444676 Asghari-Kamrani Oct 2008 B1
7469151 Khan Dec 2008 B2
7548889 Bhambri Jun 2009 B2
7567934 Flitcroft Jul 2009 B2
7567936 Peckover Jul 2009 B1
7571139 Giordano Aug 2009 B1
7571142 Flitcroft Aug 2009 B1
7580898 Brown Aug 2009 B2
7584153 Brown Sep 2009 B2
7593896 Flitcroft Sep 2009 B1
7606560 Labrou Oct 2009 B2
7627531 Breck Dec 2009 B2
7627895 Gifford Dec 2009 B2
7650314 Saunders Jan 2010 B1
7685037 Reiners Mar 2010 B2
7702578 Fung Apr 2010 B2
7707120 Dominguez Apr 2010 B2
7712655 Wong May 2010 B2
7734527 Uzo Jun 2010 B2
7753265 Harris Jul 2010 B2
7770789 Oder, II Aug 2010 B2
7784685 Hopkins, III Aug 2010 B1
7793851 Mullen Sep 2010 B2
7801826 Labrou Sep 2010 B2
7805376 Smith Sep 2010 B2
7805378 Berardi Sep 2010 B2
7818264 Hammad Oct 2010 B2
7828220 Mullen Nov 2010 B2
7835960 Breck Nov 2010 B2
7841523 Oder, II Nov 2010 B2
7841539 Hewton Nov 2010 B2
7844550 Walker Nov 2010 B2
7848980 Carlson Dec 2010 B2
7849020 Johnson Dec 2010 B2
7853529 Walker Dec 2010 B1
7853995 Chow Dec 2010 B2
7865414 Fung Jan 2011 B2
7873579 Hobson Jan 2011 B2
7873580 Hobson Jan 2011 B2
7890393 Talbert Feb 2011 B2
7891563 Oder, II Feb 2011 B2
7896238 Fein Mar 2011 B2
7908216 Davis et al. Mar 2011 B1
7922082 Muscato Apr 2011 B2
7931195 Mullen Apr 2011 B2
7937324 Patterson May 2011 B2
7938318 Fein May 2011 B2
7954705 Mullen Jun 2011 B2
7959076 Hopkins, III Jun 2011 B1
7996288 Stolfo Aug 2011 B1
8025223 Saunders Sep 2011 B2
8046256 Chien Oct 2011 B2
8060448 Jones Nov 2011 B2
8060449 Zhu Nov 2011 B1
8074877 Mullen Dec 2011 B2
8074879 Harris Dec 2011 B2
8082210 Hansen Dec 2011 B2
8095113 Kean Jan 2012 B2
8104679 Brown Jan 2012 B2
RE43157 Bishop Feb 2012 E
8109436 Hopkins, III Feb 2012 B1
8121942 Carlson Feb 2012 B2
8121956 Carlson Feb 2012 B2
8126449 Beenau Feb 2012 B2
8171525 Pelly May 2012 B1
8175973 Davis et al. May 2012 B2
8190523 Patterson May 2012 B2
8196813 Vadhri Jun 2012 B2
8205791 Randazza Jun 2012 B2
8219489 Patterson Jul 2012 B2
8224702 Mengerink Jul 2012 B2
8225385 Chow Jul 2012 B2
8229852 Carlson Jul 2012 B2
8265993 Chien Sep 2012 B2
8280777 Mengerink Oct 2012 B2
8281991 Wentker et al. Oct 2012 B2
8328095 Oder, II Dec 2012 B2
8336088 Raj et al. Dec 2012 B2
8346666 Lindelsee et al. Jan 2013 B2
8376225 Hopkins, III Feb 2013 B1
8380177 Laracey Feb 2013 B2
8387873 Saunders Mar 2013 B2
8401539 Beenau Mar 2013 B2
8401898 Chien Mar 2013 B2
8402555 Grecia Mar 2013 B2
8403211 Brooks Mar 2013 B2
8412623 Moon Apr 2013 B2
8412837 Emigh Apr 2013 B1
8417642 Oren Apr 2013 B2
8433116 Davis et al. Apr 2013 B2
8447699 Batada May 2013 B2
8453223 Svigals May 2013 B2
8453925 Fisher Jun 2013 B2
8458487 Palgon Jun 2013 B1
8484134 Hobson Jul 2013 B2
8485437 Mullen Jul 2013 B2
8494959 Hathaway Jul 2013 B2
8498908 Mengerink Jul 2013 B2
8504475 Brand et al. Aug 2013 B2
8504478 Saunders Aug 2013 B2
8510816 Quach Aug 2013 B2
8533860 Grecia Sep 2013 B1
8538845 Liberty Sep 2013 B2
8555079 Shablygin Oct 2013 B2
8566168 Bierbaum Oct 2013 B1
8567670 Stanfield Oct 2013 B2
8571939 Lindsey Oct 2013 B2
8577336 Mechaley, Jr. Nov 2013 B2
8577803 Chatterjee Nov 2013 B2
8577813 Weiss Nov 2013 B2
8578176 Mattsson Nov 2013 B2
8583494 Fisher Nov 2013 B2
8584251 McGuire Nov 2013 B2
8589237 Fisher Nov 2013 B2
8589271 Evans Nov 2013 B2
8589291 Carlson Nov 2013 B2
8595098 Starai Nov 2013 B2
8595812 Bomar Nov 2013 B2
8595850 Spies Nov 2013 B2
8606638 Dragt Dec 2013 B2
8606700 Carlson Dec 2013 B2
8606720 Baker Dec 2013 B1
8615468 Varadarajan Dec 2013 B2
8620754 Fisher Dec 2013 B2
8635157 Smith Jan 2014 B2
8646059 Von Behren Feb 2014 B1
8651374 Brabson Feb 2014 B2
8656180 Shablygin Feb 2014 B2
8751391 Freund Jun 2014 B2
8762263 Gauthier et al. Jun 2014 B2
8793186 Patterson Jul 2014 B2
8838982 Carlson et al. Sep 2014 B2
8856539 Weiss Oct 2014 B2
8887308 Grecia Nov 2014 B2
9065643 Hurry et al. Jun 2015 B2
9070129 Sheets et al. Jun 2015 B2
9100826 Weiss Aug 2015 B2
9160741 Wentker et al. Oct 2015 B2
9219708 Anati Dec 2015 B2
9229964 Stevelinck Jan 2016 B2
9245267 Singh Jan 2016 B2
9249241 Dai et al. Feb 2016 B2
9256871 Anderson et al. Feb 2016 B2
9280765 Hammad Mar 2016 B2
9530137 Weiss Dec 2016 B2
20010029485 Brody Oct 2001 A1
20010034702 Mockett et al. Oct 2001 A1
20010034717 Whitworth Oct 2001 A1
20010034720 Armes Oct 2001 A1
20010054003 Chien Dec 2001 A1
20020007320 Hogan Jan 2002 A1
20020016749 Borecki Feb 2002 A1
20020029193 Ranjan Mar 2002 A1
20020035548 Hogan Mar 2002 A1
20020046092 Ostroff Apr 2002 A1
20020073045 Rubin Jun 2002 A1
20020116341 Hogan Aug 2002 A1
20020133467 Hobson Sep 2002 A1
20020147913 Lun Yip Oct 2002 A1
20020169719 Dively Nov 2002 A1
20030023552 Kight et al. Jan 2003 A1
20030028481 Flitcroft Feb 2003 A1
20030080183 Rajasekaran et al. May 2003 A1
20030130955 Hawthorne Jul 2003 A1
20030191709 Elston Oct 2003 A1
20030191945 Keech Oct 2003 A1
20040010462 Moon Jan 2004 A1
20040050928 Bishop Mar 2004 A1
20040059682 Hasumi Mar 2004 A1
20040093281 Silverstein May 2004 A1
20040139008 Mascavage Jul 2004 A1
20040143532 Lee Jul 2004 A1
20040158532 Breck Aug 2004 A1
20040210449 Breck Oct 2004 A1
20040210498 Freund Oct 2004 A1
20040232225 Bishop Nov 2004 A1
20040260646 Berardi Dec 2004 A1
20050035192 Bonalle Feb 2005 A1
20050037735 Coutts Feb 2005 A1
20050080730 Sorrentino Apr 2005 A1
20050108178 York May 2005 A1
20050199709 Linlor Sep 2005 A1
20050246293 Ong Nov 2005 A1
20050269401 Spitzer Dec 2005 A1
20050269402 Spitzer Dec 2005 A1
20060122931 Walker Jun 2006 A1
20060124756 Brown Jun 2006 A1
20060235795 Johnson Oct 2006 A1
20060237528 Bishop Oct 2006 A1
20060278704 Saunders Dec 2006 A1
20070107044 Yuen May 2007 A1
20070129955 Dalmia Jun 2007 A1
20070136193 Starr Jun 2007 A1
20070136211 Brown Jun 2007 A1
20070170247 Friedman Jul 2007 A1
20070179885 Bird Aug 2007 A1
20070208671 Brown Sep 2007 A1
20070245414 Chan Oct 2007 A1
20070288377 Shaked Dec 2007 A1
20070291995 Rivera Dec 2007 A1
20070299742 Williams Dec 2007 A1
20080015988 Brown Jan 2008 A1
20080029607 Mullen Feb 2008 A1
20080035738 Mullen Feb 2008 A1
20080052226 Agarwal Feb 2008 A1
20080054068 Mullen Mar 2008 A1
20080054079 Mullen Mar 2008 A1
20080054081 Mullen Mar 2008 A1
20080059605 Shalev Mar 2008 A1
20080065554 Hogan Mar 2008 A1
20080065555 Mullen Mar 2008 A1
20080201264 Brown Aug 2008 A1
20080201265 Hewton Aug 2008 A1
20080228646 Myers Sep 2008 A1
20080243702 Hart Oct 2008 A1
20080245855 Fein Oct 2008 A1
20080245861 Fein Oct 2008 A1
20080263645 Renter Oct 2008 A1
20080283591 Oder, II Nov 2008 A1
20080302869 Mullen Dec 2008 A1
20080302876 Mullen Dec 2008 A1
20080313264 Pestoni Dec 2008 A1
20090006262 Brown Jan 2009 A1
20090010488 Matsuoka Jan 2009 A1
20090030845 Hurry Jan 2009 A1
20090037333 Flitcroft Feb 2009 A1
20090037388 Cooper et al. Feb 2009 A1
20090043702 Bennett Feb 2009 A1
20090048971 Hathaway Feb 2009 A1
20090106112 Dalmia Apr 2009 A1
20090106160 Skowronek Apr 2009 A1
20090134217 Flitcroft May 2009 A1
20090157555 Biffle Jun 2009 A1
20090159673 Mullen Jun 2009 A1
20090159700 Mullen Jun 2009 A1
20090159707 Mullen Jun 2009 A1
20090173782 Muscato Jul 2009 A1
20090200371 Kean Aug 2009 A1
20090248583 Chhabra Oct 2009 A1
20090276347 Kargman Nov 2009 A1
20090281948 Carlson Nov 2009 A1
20090294527 Brabson Dec 2009 A1
20090307139 Mardikar Dec 2009 A1
20090308921 Mullen Dec 2009 A1
20090327131 Beenau Dec 2009 A1
20100008535 Abulafia Jan 2010 A1
20100088237 Wankmueller Apr 2010 A1
20100094755 Kloster Apr 2010 A1
20100106644 Annan Apr 2010 A1
20100120408 Beenau May 2010 A1
20100133334 Vadhri Jun 2010 A1
20100138347 Chen Jun 2010 A1
20100145860 Pelegero Jun 2010 A1
20100161433 White Jun 2010 A1
20100185545 Royyuru Jul 2010 A1
20100211505 Saunders Aug 2010 A1
20100223186 Hogan Sep 2010 A1
20100228668 Hogan Sep 2010 A1
20100235284 Moore Sep 2010 A1
20100258620 Torreyson Oct 2010 A1
20100291904 Musfeldt Nov 2010 A1
20100299267 Faith et al. Nov 2010 A1
20100306076 Taveau Dec 2010 A1
20100325041 Berardi Dec 2010 A1
20110010292 Giordano Jan 2011 A1
20110016047 Wu Jan 2011 A1
20110016320 Bergsten Jan 2011 A1
20110040640 Erikson Feb 2011 A1
20110047076 Carlson et al. Feb 2011 A1
20110083018 Kesanupalli Apr 2011 A1
20110087596 Dorsey Apr 2011 A1
20110093397 Carlson Apr 2011 A1
20110125597 Oder, II May 2011 A1
20110153437 Archer Jun 2011 A1
20110153498 Makhotin et al. Jun 2011 A1
20110154466 Harper Jun 2011 A1
20110161233 Tieken Jun 2011 A1
20110178926 Lindelsee et al. Jul 2011 A1
20110191244 Dai Aug 2011 A1
20110238511 Park Sep 2011 A1
20110238573 Varadarajan Sep 2011 A1
20110238576 Patterson Sep 2011 A1
20110246317 Coppinger Oct 2011 A1
20110258111 Raj et al. Oct 2011 A1
20110272471 Mullen Nov 2011 A1
20110272478 Mullen Nov 2011 A1
20110276380 Mullen Nov 2011 A1
20110276381 Mullen Nov 2011 A1
20110276424 Mullen Nov 2011 A1
20110276425 Mullen Nov 2011 A1
20110295745 White Dec 2011 A1
20110302081 Saunders Dec 2011 A1
20120023567 Hammad Jan 2012 A1
20120028609 Hruska Feb 2012 A1
20120030047 Fuentes et al. Feb 2012 A1
20120035998 Chien Feb 2012 A1
20120041881 Basu Feb 2012 A1
20120047237 Arvidsson Feb 2012 A1
20120066078 Kingston Mar 2012 A1
20120072350 Goldthwaite Mar 2012 A1
20120078735 Bauer Mar 2012 A1
20120078798 Downing Mar 2012 A1
20120078799 Jackson Mar 2012 A1
20120095852 Bauer Apr 2012 A1
20120095865 Doherty Apr 2012 A1
20120116902 Cardina May 2012 A1
20120123882 Carlson May 2012 A1
20120123940 Killian May 2012 A1
20120129514 Beenau May 2012 A1
20120143767 Abadir Jun 2012 A1
20120143772 Abadir Jun 2012 A1
20120158580 Eram Jun 2012 A1
20120158593 Garfinkle Jun 2012 A1
20120173431 Ritchie Jul 2012 A1
20120185386 Salama Jul 2012 A1
20120197807 Schlesser Aug 2012 A1
20120203664 Torossian Aug 2012 A1
20120203666 Torossian Aug 2012 A1
20120215688 Musser Aug 2012 A1
20120215696 Salonen Aug 2012 A1
20120221421 Hammad Aug 2012 A1
20120226582 Hammad Sep 2012 A1
20120231844 Coppinger Sep 2012 A1
20120233004 Bercaw Sep 2012 A1
20120246070 Vadhri Sep 2012 A1
20120246071 Jain Sep 2012 A1
20120246079 Wilson et al. Sep 2012 A1
20120265631 Cronic Oct 2012 A1
20120271770 Harris Oct 2012 A1
20120278238 Patterson Nov 2012 A1
20120297446 Webb Nov 2012 A1
20120300932 Cambridge Nov 2012 A1
20120303503 Cambridge Nov 2012 A1
20120303961 Kean Nov 2012 A1
20120304273 Bailey Nov 2012 A1
20120310725 Chien Dec 2012 A1
20120310831 Harris Dec 2012 A1
20120316992 Oborne Dec 2012 A1
20120317035 Royyuru Dec 2012 A1
20120317036 Bower Dec 2012 A1
20130017784 Fisher Jan 2013 A1
20130018757 Anderson et al. Jan 2013 A1
20130019098 Gupta Jan 2013 A1
20130031006 McCullagh et al. Jan 2013 A1
20130054337 Brendell Feb 2013 A1
20130054466 Muscato Feb 2013 A1
20130054474 Yeager Feb 2013 A1
20130081122 Svigals Mar 2013 A1
20130091028 Oder, II Apr 2013 A1
20130110658 Lyman May 2013 A1
20130111599 Gargiulo May 2013 A1
20130117185 Collison May 2013 A1
20130124290 Fisher May 2013 A1
20130124291 Fisher May 2013 A1
20130124364 Mittal May 2013 A1
20130138525 Bercaw May 2013 A1
20130144888 Faith Jun 2013 A1
20130145148 Shablygin Jun 2013 A1
20130145172 Shablygin Jun 2013 A1
20130159178 Colon Jun 2013 A1
20130159184 Thaw Jun 2013 A1
20130166402 Parento Jun 2013 A1
20130166456 Zhang Jun 2013 A1
20130173736 Krzeminski Jul 2013 A1
20130185202 Goldthwaite Jul 2013 A1
20130191286 Cronic Jul 2013 A1
20130191289 Cronic Jul 2013 A1
20130198071 Jurss Aug 2013 A1
20130198080 Anderson et al. Aug 2013 A1
20130200146 Moghadam Aug 2013 A1
20130204787 Dubois Aug 2013 A1
20130204793 Kerridge Aug 2013 A1
20130212007 Mattsson Aug 2013 A1
20130212017 Bangia Aug 2013 A1
20130212019 Mattsson Aug 2013 A1
20130212024 Mattsson Aug 2013 A1
20130212026 Powell et al. Aug 2013 A1
20130212666 Mattsson Aug 2013 A1
20130218698 Moon Aug 2013 A1
20130218769 Pourfallah et al. Aug 2013 A1
20130226799 Raj Aug 2013 A1
20130226813 Voltz Aug 2013 A1
20130246199 Carlson Sep 2013 A1
20130246202 Tobin Sep 2013 A1
20130246203 Laracey Sep 2013 A1
20130246258 Dessert Sep 2013 A1
20130246259 Dessert Sep 2013 A1
20130246261 Purves et al. Sep 2013 A1
20130246267 Tobin Sep 2013 A1
20130254028 Salci Sep 2013 A1
20130254052 Royyuru Sep 2013 A1
20130254102 Royyuru Sep 2013 A1
20130254117 Von Mueller Sep 2013 A1
20130262296 Thomas Oct 2013 A1
20130262302 Lettow Oct 2013 A1
20130262315 Hruska Oct 2013 A1
20130262316 Hruska Oct 2013 A1
20130262317 Collinge Oct 2013 A1
20130275300 Killian Oct 2013 A1
20130275307 Khan Oct 2013 A1
20130275308 Paraskeva Oct 2013 A1
20130282502 Jooste Oct 2013 A1
20130282575 Mullen Oct 2013 A1
20130282588 Hruska Oct 2013 A1
20130297501 Monk et al. Nov 2013 A1
20130297504 Nwokolo Nov 2013 A1
20130297508 Belamant Nov 2013 A1
20130304649 Cronic Nov 2013 A1
20130308778 Fosmark Nov 2013 A1
20130311382 Fosmark Nov 2013 A1
20130317982 Mengerink Nov 2013 A1
20130332344 Weber Dec 2013 A1
20130339253 Sincai Dec 2013 A1
20130346314 Mogollon Dec 2013 A1
20140007213 Sanin Jan 2014 A1
20140013106 Redpath Jan 2014 A1
20140013114 Redpath Jan 2014 A1
20140013452 Aissi et al. Jan 2014 A1
20140019352 Shrivastava Jan 2014 A1
20140025581 Calman Jan 2014 A1
20140025585 Calman Jan 2014 A1
20140025958 Calman Jan 2014 A1
20140032417 Mattsson Jan 2014 A1
20140032418 Weber Jan 2014 A1
20140040137 Carlson Feb 2014 A1
20140040139 Brudnicki Feb 2014 A1
20140040144 Plomske Feb 2014 A1
20140040145 Ozvat Feb 2014 A1
20140040148 Ozvat Feb 2014 A1
20140040628 Fort Feb 2014 A1
20140041018 Bomar Feb 2014 A1
20140046853 Spies Feb 2014 A1
20140047551 Nagasundaram et al. Feb 2014 A1
20140052532 Tsai Feb 2014 A1
20140052620 Rogers Feb 2014 A1
20140052637 Jooste Feb 2014 A1
20140068706 Aissi Mar 2014 A1
20140074637 Hammad Mar 2014 A1
20140108172 Weber et al. Apr 2014 A1
20140114857 Griggs et al. Apr 2014 A1
20140143137 Carlson May 2014 A1
20140164243 Aabye et al. Jun 2014 A1
20140188586 Carpenter et al. Jul 2014 A1
20140294701 Dai et al. Oct 2014 A1
20140297534 Patterson Oct 2014 A1
20140310183 Weber Oct 2014 A1
20140330721 Wang Nov 2014 A1
20140330722 Laxminarayanan et al. Nov 2014 A1
20140331265 Mozell et al. Nov 2014 A1
20140337236 Wong et al. Nov 2014 A1
20140344153 Raj et al. Nov 2014 A1
20140372308 Sheets Dec 2014 A1
20150019443 Sheets et al. Jan 2015 A1
20150032625 Dill et al. Jan 2015 A1
20150032626 Dill et al. Jan 2015 A1
20150032627 Dill et al. Jan 2015 A1
20150046338 Laxminarayanan et al. Feb 2015 A1
20150046339 Wong et al. Feb 2015 A1
20150052064 Karpenko et al. Feb 2015 A1
20150088756 Makhotin et al. Mar 2015 A1
20150106239 Gaddam et al. Apr 2015 A1
20150112870 Nagasundaram et al. Apr 2015 A1
20150112871 Kumnick Apr 2015 A1
20150120472 Aabye et al. Apr 2015 A1
20150127529 Makhotin et al. May 2015 A1
20150127547 Powell et al. May 2015 A1
20150140960 Powell et al. May 2015 A1
20150142673 Nelsen et al. May 2015 A1
20150161597 Subramanian et al. Jun 2015 A1
20150178724 Ngo et al. Jun 2015 A1
20150180836 Wong et al. Jun 2015 A1
20150186864 Jones et al. Jul 2015 A1
20150193222 Pirzadeh et al. Jul 2015 A1
20150195133 Sheets et al. Jul 2015 A1
20150199679 Palanisamy et al. Jul 2015 A1
20150199689 Kumnick et al. Jul 2015 A1
20150220917 Aabye et al. Aug 2015 A1
20150269566 Gaddam et al. Sep 2015 A1
20150312038 Palanisamy Oct 2015 A1
20150319158 Kumnick Nov 2015 A1
20150332262 Lingappa Nov 2015 A1
20150356560 Shastry et al. Dec 2015 A1
20160028550 Gaddam et al. Jan 2016 A1
20160042263 Gaddam et al. Feb 2016 A1
20160065370 Le Saint et al. Mar 2016 A1
20160092696 Guglani et al. Mar 2016 A1
20160092872 Prakash et al. Mar 2016 A1
20160103675 Aabye et al. Apr 2016 A1
20160119296 Laxminarayanan et al. Apr 2016 A1
20160224976 Basu et al. Aug 2016 A1
20170046696 Powell et al. Feb 2017 A1
20170103387 Weber Apr 2017 A1
20170220818 Nagasundaram et al. Aug 2017 A1
20170228723 Taylor et al. Aug 2017 A1
Foreign Referenced Citations (16)
Number Date Country
2008298750 Apr 2014 AU
2156397 Feb 2010 EP
2001035304 May 2001 WO
2001035304 May 2001 WO
2004042536 May 2004 WO
2006113834 Oct 2006 WO
2009032523 Mar 2009 WO
2010078522 Jul 2010 WO
2012068078 May 2012 WO
2012098556 Jul 2012 WO
2012142370 Oct 2012 WO
2012167941 Dec 2012 WO
2013048538 Apr 2013 WO
2013056104 Apr 2013 WO
2013119914 Aug 2013 WO
2013179271 Dec 2013 WO
Non-Patent Literature Citations (37)
Entry
Examination Report dated Jun. 21, 2012 in Australian Patent Application No. 2008298750, 4 pages.
“Petition for Inter Partes Review of U.S. Pat. No. 8,533,860 Challenging Claims 1-30 Under 35 U.S.C. § 312 and 37 C.F.R. § 42.104”, Before the USPTO Patent Trial and Appeal Board, IPR 2016-00600, Feb. 17, 2016, 65 pages.
U.S. Appl. No. 13/072,436 , “Notice of Allowance”, dated Jan. 31, 2012, 16 pages.
U.S. Appl. No. 13/460,293 , “Non Final Office Action”, dated Dec. 11, 2013, 9 pages.
U.S. Appl. No. 13/460,293 , “Notice of Allowance”, dated Mar. 26, 2014, 5 pages.
U.S. Appl. No. 14/600,523 , “U.S. Patent Application No.”, Secure Payment Processing using Authorization Request, filed Jan. 20, 2015, 42 pages.
U.S. Appl. No. 14/952,444 , “U.S. Patent Application No.”, Tokenization Request Via Access Device, filed Nov. 25, 2015, 78 pages.
U.S. Appl. No. 14/952,514 , “U.S. Patent Application No.”, Systems Communications with Non-sensitive Identifiers, filed Nov. 25, 2015, 72 pages.
U.S. Appl. No. 14/955,716 , “U.S. Patent Application No.”, Provisioning Platform for Machine-to-Machine Devices, filed Dec. 1, 2015, 61 pages.
U.S. Appl. No. 14/966,948 , “U.S. Patent Application No.”, Automated Access Data Provisioning, filed Dec. 11, 2015, 52 pages.
U.S. Appl. No. 15/004,705 , “U.S. Patent Application No.”, Cloud-based Transactions with Magnetic Secure Transmission, filed Jan. 22, 2016, 161 pages.
U.S. Appl. No. 15/008,388 , “U.S. Patent Application No.”, Methods for Secure Credential Provisioning, filed Jan. 27, 2016, 89 pages.
U.S. Appl. No. 15/011,366 , “U.S. Patent Application No.”, Token Check Offline, filed Jan. 29, 2016, 60 pages.
U.S. Appl. No. 15/019,157 , “U.S. Patent Application No.”, Token Processing Utilizing Multiple Authorizations, filed Feb. 9, 2016, 63 pages.
U.S. Appl. No. 15/041,495 , “U.S. Patent Application No.”, Peer Forward Authorization of Digital Requests, filed Feb. 11, 2016, 63 pages.
U.S. Appl. No. 15/265,282 , “U.S. Patent Application”, Self-Cleaning Token Vault, filed Sep. 14, 2016.
U.S. Appl. No. 15/462,658 , “U.S. Patent Application”, Replacing Token on a Multi-Token User Device, filed Mar. 17, 2017, 58 pages.
U.S. Appl. No. 61/738,832 , “U.S. Provisional Application No”, Management of Sensitive Data, filed Dec. 18, 2012.
U.S. Appl. No. 61/751,763 , “U.S. Provisional Application No”, Payments Bridge, filed Jan. 11, 2013.
U.S. Appl. No. 61/879,362 , “U.S. Provisional Application No.”, Systems and Methods for Managing Mobile Cardholder Verification Methods, filed Sep. 18, 2013.
U.S. Appl. No. 61/892,407 , “U.S. Provisional Application No”, Issuer Over-The-Air Update Method and System, filed Oct. 17, 2013.
U.S. Appl. No. 61/894,749 , “U.S. Provisional Application No”, Methods and Systems for Authentication and Issuance of Tokens in a Secure Environment, filed Oct. 23, 2013.
U.S. Appl. No. 61/926,236 , “U.S. Provisional Application No”, Methods and Systems for Provisioning Mobile Devices With Payment Credentials and Payment Token Identifiers, filed Jan. 10, 2014.
U.S. Appl. No. 62/000,288 , “U.S. Provisional Application No”, Payment System Canonical Address Format, filed May 19, 2014.
U.S. Appl. No. 62/003,717 , “U.S. Provisional Application No”, Mobile Merchant Application, filed May 28, 2014.
U.S. Appl. No. 62/024,426 , “U.S. Provisional Application No”, Secure Transactions Using Mobile Devices, filed Jul. 14,2014.
U.S. Appl. No. 62/037,033 , “U.S. Provisional Application No”, Sharing Payment Token, filed Aug. 13, 2014.
U.S. Appl. No. 62/038,174 , “U.S. Provisional Application No”, Customized Payment Gateway, filed Aug. 15, 2014.
U.S. Appl. No. 62/042,050 , “U.S. Provisional Application No”, Payment Device Authentication and Authorization System, filed Aug. 26, 2014.
U.S. Appl. No. 62/053,736 , “U.S. Provisional Application No”, Completing Transactions Without a User Payment Device, filed Sep. 22, 2014.
U.S. Appl. No. 62/054,346 , “U.S. Provisional Application No”, Mirrored Token Vault, filed Sep. 23, 2014.
U.S. Appl. No. 62/103,522 , “U.S. Provisional Application No”, Methods and Systems for Wallet Provider Provisioning, filed Jan. 14, 2015.
U.S. Appl. No. 62/108,403 , “U.S. Provisional Application No”, Wearables With NFC HCE, filed Jan. 27, 2015.
U.S. Appl. No. 62/117,291 , “U.S. Provisional Application No”, Token and Cryptogram Using Transaction Specific Information, filed Feb. 17, 2015.
U.S. Appl. No. 62/128,709 , “U.S. Provisional Application No.”, Tokenizing Transaction Amounts, filed Mar. 5, 2015, 30 pages.
AU2008298750 , “Office Action Response”, filed Jan. 29, 2013, 20 pages.
Levi et al., “The prevention of cheque and credit card fraud—CiteSeerX”, Crime Prevention Unit Paper No. 26, 1991, pp. 1-57.
Related Publications (1)
Number Date Country
20190073667 A1 Mar 2019 US
Provisional Applications (1)
Number Date Country
60972088 Sep 2007 US
Continuations (4)
Number Date Country
Parent 14306017 Jun 2014 US
Child 16053699 US
Parent 13460293 Apr 2012 US
Child 14306017 US
Parent 13072436 Mar 2011 US
Child 13460293 US
Parent 12205069 Sep 2008 US
Child 13072436 US