The present invention relates in general to portable proximity consumer devices used in wireless payment transactions, and in particular to various embodiments of portable proximity consumer devices, such as credit and debit contactless smart cards, that use secured account numbers for wireless financial transactions.
Generally, portable proximity consumer devices such as contactless smart cards are designed to provide the consumer with a way to engage in purchase transactions by wirelessly connecting the portable proximity consumer devices directly with the merchant's point of sales device, for instance using radio frequency (RF) or infrared (IR) signals. For example, contactless smart cards allow a consumer to store and transmit financial data and other personal data to a merchant device which uses it to effect a payment during a purchase transaction.
Because portable proximity consumer devices operate without requiring direct connection to the accepting device, portable proximity consumer devices are expected to gain popularity over other types of devices that require physical contact and/or physical connections to communicate with other devices and systems. Illustratively, contactless smart cards may be used to replace regular credit cards, as they need not be in contact with a transaction reader device to be operated. Regular credit cards having magnetic stripes and contact smart cards must come in contact with a reader.
Portable proximity consumer devices may wirelessly exchange data with a proximity device reader from a distance, as long as the user is in wireless range of the proximity device reader. Unfortunately, due to the wireless nature of the portable proximity consumer devices, it is possible that proximity device reader may be used for surreptitious interrogation of the portable proximity consumer device by intercepting the portable proximity electronic device's communications. In addition, it is conceivable that a proximity accepting device may be developed or modified to enhance its power and sensitivity and thereby increase its ability to interrogate with and intercept signals from the portable proximity consumer devices from a greater distance than specified in standards used for portable proximity consumer devices.
Theft of sensitive information using wireless interrogation or interception of communications from portable proximity consumer devices is a major concern for consumers and businesses alike. Unfortunately, given the sophistication of the wireless interrogation equipment and the nature of wireless signals, it is easy for wireless interrogation to occur at virtually any time and place. Once the victim of the wireless interrogation discovers that they had sensitive information stolen, it is often too late to discover where the theft took place. The victim must then deal with the consequences and hassle of correcting the unauthorized access and possible uses of the information.
In response to such risk, many payment service providers have instigated safeguards for protecting purchases from fraudulent attacks, for example, by employing encryption technologies to encrypt the primary account number and other data associated with account transactions. Encryption generally involves encrypting transaction data on one end of a transmission with a key, and then regenerating the original transaction data by decrypting the encrypted data received with the same key on the other end of the transmission. While encryption technologies have proven to be highly effective in preventing information theft, implementing or upgrading to the latest encryption technology often requires upgrades by the end user's of payment processing systems. Due to the cost, time, and risk of potential business interruption (e.g., loss of sales), many merchants, for example, resist making necessary upgrades to their procedures and systems to implement such safeguards. Therefore, such safeguards have had limited success as they are generally expensive to implement, can be overcome, and have not been fully accepted by the credit card industry, merchants, payment processors, etc.
Therefore, what is needed is a cost effective device and method that integrates easily with exiting payment processing systems and prevents an unauthorized user from using data wirelessly interrogated or intercepted from a portable proximity consumer devices.
Embodiments of the present invention provide an apparatus and method for conducting financial transactions using secured account numbers from portable proximity consumer devices.
Embodiments of the invention include the use of “secured account numbers”. These may include “ghost” account numbers. A ghost account number can be one that is related to a person's real account number.
In one embodiment, the present invention provides a method including receiving an authorization request message which includes a secured account number. The secured account number is associated with a real account number. In this embodiment, the authorization request message originates from a transaction that results from a wireless based interaction between a portable proximity consumer devices including a wireless communication module and a memory pre-loaded with the secured account number and a proximity reader device including a second wireless communication module. The secured account number is wirelessly transmitted from the portable proximity consumer device to the proximity reader device. The secured account number may then be transmitted to a server computer operated by an acquirer, payment processing system, and/or issuer. After the secured account number is received by the server computer, the real account number is determined. Once the real account number is determined, the issuer, for example, may proceed with its usual transaction authorization methods and processes. The issuer may then send an authorization response message back to the proximity reader device to inform the consumer that the transaction is or is not authorized.
In another embodiment, the present invention provides a portable proximity consumer device for performing contactless transactions. The portable proximity consumer device includes a first antenna, a first memory including a secured account number coupled to the first antenna, and a second memory wherein the second memory comprising a real account number, wherein the real account number is associated with the secured account number.
In another embodiment, the present invention provides a system for performing payment transactions. The system includes a payment processing system capable of converting a secured account number to a user's real account number. In response to the payment processing system receiving a transaction authorization request comprising the secured account number, the payment processing system determines the user's real account number associated with the secured account number, and verifies that the transaction authorization request was associated with a wireless payment transaction.
These and other embodiments of the invention are described in further detail below.
Embodiments of the invention are directed to the use of a secured account number preloaded onto a portable proximity consumer device. Portable proximity consumer devices may be any portable consumer device such as a contactless smart debit/credit card, contact chip enabled debit/credit card, a PDA, mobile phone, and the like, capable of wireless transmission of a secured account number, in lieu of a user's primary account number (PAN) or a user's real account number. As described herein, the term “proximate” may be used interchangeably with terms such as contactless relating to transactions wirelessly communicated between devices proximate to one another.
Secured account numbers may include “ghost” account numbers. In one embodiment, a ghost account number can be one that is related to a person's real account number. The secured account number may be considered an account number capable of resembling a user's real account number (e.g., a real PAN). For example, if a user's real account number contains nineteen digits, the secured account number may also contain nineteen digits. It is contemplated that the secured account number may be of any length as long as it resembles a real account number, such as a credit card number, debit card number, gift card number, and the like. For example, the secured account number may resemble a gift card number that is twenty one digits in length, when the user's real account number is nineteen digits long. The secured account number may also be a static number. The term “static” means that the secured account number does not have to change between transactions, but may change when the user changes accounts, the user's real account number expires, the portable proximity consumer device is lost or stolen, etc. The secured account number may also be described using terms such as bogus, fake, decoy, substitute, and the like, which signify an alphanumeric sequence that is used in place of a user's real account number to perform transactions.
In embodiments of the invention, the secured account number may be preloaded into a first memory in a portable proximity consumer device, while the user's real account number is stored in a second memory in the portable proximity consumer device. The first and second memories may use different data storage technologies. For example, the first memory may include a memory chip, and the second memory may be in the form of a magnetic stripe.
The portable proximity consumer device can operate in a variety of wireless transmission modes such as a contactless mode or an infrared mode, RF mode (i.e., Radio Frequency), and the like, and optionally may be operated in a contact mode such as through a hardwired communication interface. The secured account number is used in wireless transactions. The user's regular account number is used and transmitted when the portable proximity consumer device is used in a contact mode, or when the consumer performs a direct entry transaction (e.g., entering a real account number onto a Web form to purchase goods on the Internet).
Put another way, the secured account number is not used for contact transactions or direct entry transactions. For example, in a non-wireless transaction, when the secured account number is entered onto a Web form via an Internet merchant portal, the transaction will not be unauthorized. This is useful if someone (e.g., a thief) surreptitiously intercepts the secured account number during a contactless purchase transaction and obtains the secured account number. Because the secured account number is configured to resemble a real account number, it will deceive the unauthorized user into believing that it is an operable account number. However, if the unauthorized user enters the secured account number onto a Web form to conduct a transaction, the transaction is not authorized by the issuer, unless, for example, the issuer is using the transaction as a means to catch the unauthorized user. Furthermore, the secured account number is configured such that unauthorized users may not retrieve the real account number for use in fraudulent transactions, without access to a database configured to keep the real account number secret from unauthorized access. As will be explained in further detail below, this is advantageous as it can make it easier to detect an unauthorized transaction and discover potential fraud. In addition, the secured account number does not provide sufficient information to route the transaction to the appropriate issuer since the secured account does not provide a valid transaction path number (e.g., bank identification number). Thus, the present invention creates multiple challenges to prevent the transaction that the thief tries to conduct from being authorized.
The portable proximity consumer devices according to embodiments of the invention can be used with authorized wireless interrogation devices (e.g., authorized proximity reader devices) that can also have wireless communication and transmission modules (e.g., receiver, transceiver, etc.). Such authorized interrogation devices may be present at point-of-sale (POS) reader devices, ATM (automatic teller machines), and the like. Such interrogation devices are well known in the art. The portable proximity consumer devices according to embodiments of the invention may operate with any number of such authorized wireless interrogation devices using a variety of operating standards. For example, such a standard may be the Europay-Mastercard-Visa (EMV) standard started by a working group created in 1993 by the world's three main payment organizations: EUROPAY (EPI), MASTERCARD (MCI) and VISA.
As noted above and below, an exemplary portable proximity consumer device may include a memory such as a memory chip and/or a microprocessor. Either may be operationally coupled to the communication and/or transmission modules in the portable proximity consumer device. The memory could be in the form of a memory chip or could be wired logic. The information in the memory may include information such as a user's bank account information, secured account number, credit or debit account number information, account balance information, consumer information, etc.
In some embodiments, during a process for authorizing an electronic payment transaction, the secured account number is wirelessly transmitted from a portable proximity consumer device to the proximity reader device performing the transaction, such as for instance, a contactless smart card transaction reader device. The secured account number is then transmitted from the contactless smart card transaction reader device at a merchant, to the merchant's acquirer, to a payment processing system, and then to the issuer. In one embodiment, one or more computational apparatuses at any one of these entities may be used to convert the secured account number into the user's real account number so that the issuer can respond to a submitted authorization request message.
In embodiments of the invention, an authorization request message for a transaction is created after a consumer purchases a good or service at a POS reader device using a portable proximity consumer device such as a credit or debit card. The authorization request message may be sent from the POS reader device located at a merchant to the merchant's acquirer, to a payment processing system, and then to an issuer.
A “merchant” in embodiments of the invention can have any suitable characteristics. A merchant may include entities such as corporations, sole proprietorships, non-profit organizations, or a specific group of such entities. Examples of merchants include restaurants, theaters, gasoline and fuel stores, grocery stores, clothing retailers, department stores, etc. The merchant has one or more POS reader devices that can interact with the portable proximity consumer devices. Any suitable POS reader device may be used including card readers as described herein. The card readers may include any suitable contact or proximity mode of operation. For example, exemplary card readers can include RF (radio frequency) antennas, magnetic stripe readers, etc. to interact with the portable proximity consumer devices.
An “acquirer” is typically a business entity, e.g., a commercial bank that has a business relationship with a particular merchant. An “issuer” is typically a business entity (e.g., a bank) that issues a portable proximity consumer device such as a credit or debit card to a consumer. Some entities such as American Express perform both issuer and acquirer functions. Embodiments of the invention encompass such single entity issuer-acquirers.
An “authorization request message” can include a request for authorization to conduct an electronic payment transaction or some other type of activity. It may include one or more of an account holder's payment account number, currency code, sale amount, merchant transaction stamp, acceptor city, acceptor state/country, POS transaction number, POS transaction type, etc. Optionally, an authorization request message may be protected using a secure encryption method—e.g., 128-bit SSL or equivalent-in order to prevent data from being compromised. In other embodiments, an “authorization request message” may include a request for permission to enter a predetermined location (e.g., as used for wireless access badges).
Typically, an electronic payment transaction is authorized if the consumer conducting the transaction has sufficient funds or credit to conduct the transaction. Conversely, if there are insufficient funds or credit in the consumer's account, or if the consumer's portable proximity consumer device is on a blacklist (e.g., it is indicated as stolen), then an electronic payment transaction may not be authorized (e.g., declined).
The transaction processing system 100 also includes a proximity reader device 110 capable of wirelessly receiving secured account numbers, and an optional contact reader 114, capable of receiving real account numbers from a portable proximity consumer device 102 such as a credit or debit smart card. The proximity reader device 110 and/or the contact reader 114 can be located at the merchant 112, or may be simply operated by the merchant 112.
The portable proximity consumer device 102 according to embodiments of the invention may be in any suitable form. For example, the portable proximity consumer device 102 can be hand-held and compact so that it can fit into a consumer's wallet and/or pocket (e.g., pocket-sized). For example, the portable proximity consumer device 102 may include smart cards, ordinary credit or debit cards (with a magnetic stripe and without a microprocessor), a keychain device, key Fob, etc. Other examples of contactless portable proximity consumer devices 102 include cellular phones, personal digital assistants (PDAs), pagers, payment cards, security cards, access cards, smart media, transponders, and the like. Such portable proximity consumer devices 102 can have one or more antennas 106 coupled to wireless transmission devices that can transmit and/or receive signals and data through a wireless communication medium.
The payment processing system 120 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. An exemplary payment processing system 120 may include VisaNet™. Payment processing systems such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, includes a single message system (SMS) that automatically authorizes and provides enough information to automatically clear and settle a financial transaction, and/or a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system, which performs clearing and settlement services.
The payment processing system 120 may include a server computer. A server computer 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 system 120 may use any suitable wired or wireless network, including the Internet.
In one embodiment, the proximity reader device 110 is capable of wirelessly receiving a secured account number from a portable proximity consumer device 102. For example, as illustrated in
The secured account number may be derived from the user's real account number using any suitable algorithm. For example, one exemplary algorithm multiplies the first twelve numbers of the user's real card number by two and then takes the last digit of the new number, e.g., 1234 5678 9012 1214, to convert the user's real account number to a secured account number, e.g. 2468 0246 8024 1214. In this example, the algorithm may leave a single digit in each digit location. As illustrated above, when the number five is multiplied by two, the algorithm drops the resultant one of the “10” to leave the zero. Of course, other algorithms may be used. Any such algorithms preferably leave the last four digits of the real account number unaltered. Typical credit card receipts mask the first series of numbers of a user's account number, but exposes the last four digits. By not altering the last four digits, the consumer does not know whether a secured account number or the real account number is used in a particular transaction. This is advantageous, as it avoids confusion on the part of the consumer and may deter fraudulent activities related to the retrieval of receipts.
The resultant secured account number may be stored in a database along with the real account number in a lookup table with other corresponding secured and real account numbers. The database may be accessible to the acquirer 116, payment processing system 120, and/or the issuer 130. The database is preferably accessible to at least one of the payment processing system 120 and/or the issuer 130, since the issuer 130 authorizes or does not authorize the user's transaction.
The secured account numbers may be preloaded into the user's portable proximity consumer device 102. The one or more algorithms may be used at any time, e.g., prior to manufacturing, during the manufacturing, or during processing of the consumer portable proximity device 102, to generate the secured account numbers. For example, the algorithm may be used when generating real account numbers, during production of the portable proximity consumer device 102, during account number activation, or when preparing to preload the secured account numbers into the portable proximity consumer devices 102, etc.
It is desirable to “preload” the secured account number into a memory in the portable proximity consumer device 102. As noted above, encryption techniques are known. However, such encryption techniques require the use of lengthy computer programs that need to be stored on the portable proximity consumer device. Such lengthy computer programs occupy valuable space in the memory of the portable proximity consumer device 102. By using a preloaded secured account number that resembles a real account number, a relatively small amount of space is used in the memory of the portable proximity consumer device 102. Additionally, the software and the hardware associated with the proximity reader device 110 and/or the contact card reader 114 need not be altered since the secured account number has the same form as the real account number.
In one operational embodiment, during a consumer purchase transaction, an authorization request message including a secured account number is wirelessly transmitted from the portable proximity consumer device 102 to the proximity reader device 110. For example, a consumer can purchase an article of clothing with a contactless smart card. The authorization request message including the secured account number and a POS transaction type identifier (indicative that the transaction was a wireless type of proximity transaction,) is received by the merchant 112 and is transmitted to the acquirer 116. The acquirer 116 then transmits, among other information, the authorization request message including the secured account number, POS transaction type identifier to the payment processing system 120 for processing thereof.
In one embodiment, the POS transaction type identifier may be an alphanumeric indicator, symbol, and the like. It may indicate that transaction that was conducted was a proximity financial transaction, and was not a contact-type transaction. For example, the POS transaction type identifier may be a conventional number used in the credit card industry such as “POS entry code 91”, or could be a modified version of a standard indicator such as a modified international standards organization (ISO) indicator. After a server computer at the payment processing system 120 receives the authorization request message, the payment processing system 120 identifies the transmitted account number as a secured account number and uses the POS transaction type identifier to identify the transaction as a wireless transaction. If the secured account number is valid and if the transaction is identified as a wireless transaction, then the payment processing system 120 converts the secured account number to the user's real account number. The real account number is then transmitted to the issuer 130 for payment authorization.
The real account number includes the real account number's BIN (bank identification number) so the transaction processing system 120 knows which particular issuer is supposed to receive the authorization request message. Generally, a BIN corresponds to the first six digits of the user's real account number (e.g., a credit or debit account number). These first six digits identify which network the portable proximity consumer device 102 is associated with as well as which issuer 130 issued the portable proximity consumer device 102. If the transaction is authorized by the issuer 130, the payment processing system 120 transmits an authorization response message along with the secured account number (or real account number) back to the acquirer 116. The acquirer 116 sends the authorization response message to the merchant 112. A printer (not shown) at the merchant 112 may then print a receipt showing only the last four digits of the secured account number, e.g., ***********1214. As noted above, since the last four digits are the same for both the secured account number and the user's real account number, the user is unaware of any account number differences between the secured account number and the user's real account number. While four digits are illustrated, one skilled in the art will recognize that any alphanumeric indicator, symbol, or indicia, common to both the secured account number and the user's real account number may be used within the scope of the present invention. For example, in some embodiments, the secured account number and the real account number may have two or more common numbers.
Two software engines are illustrated in
When a secured account number is received by the secured account engine 122, the secured account engine 122 converts the secured account number to the user's real account number. In one embodiment, the secured account engine 122 compares the secured account number to a plurality of secured account numbers to find the user's real account number (e.g., in a lookup table). Alternatively, one or more algorithms may be operated to convert the secured account number to the user's real account number. A suitable algorithm may be the reverse program of the algorithm used to convert the real account number to the secured account number (as described above).
If the payment processing system 120 receives an authorization request message including a secured account number that does not have the transaction type identifier (e.g., POS 91), or other indicator, indicating a proximity transaction, then the optional fraud detection engine 124 may be capable of one or more proactive and non-proactive responses. For example, one non-proactive response is simply to deny the transaction. An authorization response message may be sent from the issuer 130 to the merchant 112 that indicates that the transaction is not authorized. One example of a proactive response is to alert legal authorities that a fraudulent activity is taking place. In one embodiment, when the secured account number is received by the payment processing system 120 without the POS proximity transaction indicator, then the issuer 130 is notified. The issuer 130 checks the user's real account for unusual activity (e.g., large purchases when a consumer usually does not make large purchases). If unusual activity is detected, then the payment processing system 120 and/or the issuer 130 may suspend the secured account number until verification is made that the secured account number was not stolen. In this case, the use of the secured account number and/or the real account number can be temporarily suspended pending an investigation. If it is determined that the user's secured account number was obtained and used by an unauthorized person, then the payment processing system 120 may reissue a new portable proximity consumer device to the real user. For example, similar to conventional procedures for lost or stolen account numbers, part of the verification process may be for the payment processing system 120 to issue an alert to the merchant 112 to keep the portable proximity consumer device 102, or to have the user contact the issuer 130 to verify the unauthorized transaction.
The wireless communication module 206 may be designed to receive wireless interrogation signals and transmit communication signals to the proximity reader device 110 via the wireless transmission module 106. Any number of wireless portable consumer devices well known in the art may be used to accomplish the reception and transmission of data between the proximity reader device 110 and the portable proximity consumer device 102. For example, the wireless communication module 206 may be formed from a wireless receiver in combination with a wireless transmitter. The wireless communication module 206 may use any viable communication link such as ISO 14443, Bluetooth, 802.11x, cellular network, RF, and the like. In other words, virtually any wireless transceiver system that is sized accordingly and capable of communicating with contactless reader 110 may be used.
The first memory 210 can be a non-volatile or volatile memory such as a random access memory that has sufficient space to hold the necessary programming and data structures of the invention. While first memory 210 is shown as a single entity, it should be understood that first memory 210 may in fact comprise a plurality of modules, and that first memory 210 may exist at multiple levels, from high speed registers and caches to lower speed but larger direct random access memory (DRAM) chips. In one embodiment, first memory 210 may include a secured account program 212 and secured account number storage 214. The secured account program 212 may use any one of a number of different programming languages. For example, the program code can be written in PLC code (e.g., ladder logic), a higher-level language such as C, C++, Java, or a number of other languages. While secured account program 212 may be a standalone program, it is contemplated that secured account program 212 may be combined with other programs.
The secured account program 212 when executed on CPU 202, provides a secured account number to the proximity reader device 110 from the secured account number storage 214. In one embodiment, the secured account program 212 is configured to retrieve a secured account number from the secured account storage 214. The secured account program 212 instructs the CPU 202 to wirelessly transmit the secured account number, among other data such as available credit, user data, and the like, to the proximity reader device 110 via the wireless communication module 206.
In one embodiment, data processing circuit 104 may optionally include a second memory 220. The second memory 220 is capable of storing the user's real account number in a real account number storage 222. Preferably, in the case were data processing circuit 104 stores both the secured account number and the user's real account number, the user's real account number is accessible only via a physical contact connection. For example, the user's real account number may be accessed via an electrical connection with data processing circuit 104. In an alternate embodiment, similar to conventional credit/debit cards the user's real account number may be encoded onto the magnetic stripe 108. In this configuration, the user's real account number is accessible using conventional contact readers 114 capable of reading magnetic stripes.
In preferred embodiments, the first and second memories use different data storage technologies. For example, the first and second memories may be selected from optical, magnetic, or electronic storage media, and may be different. For example, the first memory may be use an electronic storage medium (e.g., a memory chip), while the second memory may use a magnetic storage medium (e.g., a magnetic stripe 108).
At step 308, the secured account number is converted to the user's real account number. For example, as described above, when a secured account number is received by the payment processing system 120, a secured account engine 122 converts the secured account number to the user's real account number. In one embodiment, the secured account engine 122 may search a database of secured account numbers to find the user's real account number. Alternatively, a conversion algorithm may be used to convert the secured account number to the user's real account number.
If the real account number is not found, at step 309, the method 300 proceeds to step 316 and, for example, issues a transaction invalid protocol to the payment processing system 120. For example, if the real account number is not found, the payment processing system 120 may alert the issuer 130, the acquirer 116, and/or the merchant 112 that the transaction is not authorized. Conceivably, after attempting to use the contactless authorization, the user, being unaware of the secured account number, may reattempt the transaction using the user's real account number via entry by an operator or by using a contact reader 114.
At step 310, if the secured account number is valid, the authorization request message including the user's real account number, the merchant ID, the POS transaction type, and the purchase amount along with other transaction data to the issuer 130. For example, the payment processing system 120 may transmit the user's real account number, the secured account number, and the POS transaction type, along with other transaction data to the issuer 130. At step 312 if the transaction is not authorized, e.g. the user does not have sufficient credit for the purchase, the method 300 proceeds to step 316. However, if the transaction is authorized, e.g., the issuer 130 has authorized the transaction, the method 300 proceeds to step 313. Then at step 313, an authorization response message is sent to the merchant 112 informing the merchant 112 and the user whether or not the transaction is authorized. At step 314, the transaction is cleared and settled using conventional procedures. For example, at the end of the day, a normal clearing and settlement process can take place at step 314. At step 318 the method 300 ends.
The method shown in
Any of the above described steps may be embodied as computer code on a computer readable medium. The computer readable medium may reside on one or more computational apparatuses and may use any suitable data storage technology.
The present invention can be implemented in the form of control logic in software or hardware or a combination of both. The control logic may be stored in an information storage medium as a plurality of instructions adapted to direct an information processing device to perform a set of steps disclosed in embodiment of the present invention. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the present invention.
The above description is illustrative but 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.
A recitation of “a”, “an” or “the” is intended to mean “one or more” 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.
This application is a continuation of U.S. patent application Ser. No. 16/368,262, filed on Mar. 28, 2019, which is a continuation of U.S. patent application Ser. No. 14/275,718 filed May 12, 2014, which is a divisional of U.S. patent application Ser. No. 11/398,887 filed Apr. 5, 2006, which claims priority to U.S. Provisional Patent Application No. 60/714,635 filed Sep. 6, 2005, the entireties of which are hereby incorporated by reference for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
3594727 | Barun | Jul 1971 | A |
5163098 | Dahbura | Nov 1992 | A |
5276311 | Hennige | Jan 1994 | A |
5280527 | Gullman et al. | Jan 1994 | A |
5585787 | Wallerstein | Dec 1996 | A |
5613012 | Hoffman et al. | Mar 1997 | A |
5781438 | Lee et al. | Jul 1998 | A |
5877482 | Reilly | Mar 1999 | A |
5883810 | Franklin et al. | Mar 1999 | A |
5930767 | Reber et al. | Jul 1999 | A |
5953710 | Fleming | Sep 1999 | A |
5955961 | Wallerstein | Sep 1999 | A |
5956699 | Wong et al. | Sep 1999 | A |
5988497 | Wallace | Nov 1999 | A |
6000832 | Franklin et al. | Dec 1999 | A |
6014635 | Harris et al. | Jan 2000 | A |
6024286 | Bradley et al. | Feb 2000 | A |
6044360 | Picciallo | Mar 2000 | A |
6076073 | Pieterse et al. | Jun 2000 | A |
6163771 | Walker et al. | Dec 2000 | A |
6227447 | Campisano | May 2001 | B1 |
6236981 | Hill | May 2001 | B1 |
6267292 | Walker et al. | 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 et al. | Jul 2002 | B1 |
6453301 | Niwa | Sep 2002 | B1 |
6592044 | Wong et al. | Jul 2003 | B1 |
6636833 | Flitcroft et al. | Oct 2003 | B1 |
6748367 | Lee | Jun 2004 | B1 |
6805287 | Bishop et al. | Oct 2004 | B2 |
6805288 | Routhenstein et al. | Oct 2004 | B2 |
6857566 | Wankmueller | Feb 2005 | B2 |
6879965 | Fung et al. | Apr 2005 | B2 |
6891953 | DeMello et al. | May 2005 | B1 |
6901387 | Wells et al. | May 2005 | B2 |
6931382 | Laage et al. | Aug 2005 | B2 |
6938019 | Uzo | Aug 2005 | B1 |
6941285 | Sarcanin | Sep 2005 | B2 |
6980670 | Hoffman et al. | Dec 2005 | B1 |
6990470 | Hogan et al. | Jan 2006 | B2 |
6991157 | Bishop et al. | Jan 2006 | B2 |
7051929 | Li | May 2006 | B2 |
7069249 | Stolfo et al. | Jun 2006 | B2 |
7103576 | Mann, III et al. | Sep 2006 | B2 |
7113930 | Eccles et al. | Sep 2006 | B2 |
7136835 | Flitcroft et al. | Nov 2006 | B1 |
7177835 | Walker et al. | Feb 2007 | B1 |
7177848 | Hogan et al. | Feb 2007 | B2 |
7194437 | Britto et al. | Mar 2007 | B1 |
7209561 | Shankar et al. | Apr 2007 | B1 |
7264154 | Harris | Sep 2007 | B2 |
7280975 | Donner | Oct 2007 | B1 |
7287692 | Patel et al. | Oct 2007 | B1 |
7292999 | Hobson et al. | Nov 2007 | B2 |
7350230 | Forrest | Mar 2008 | B2 |
7353382 | Labrou et al. | Apr 2008 | B2 |
7379919 | Hogan et al. | May 2008 | B2 |
7386517 | Donner | Jun 2008 | B1 |
RE40444 | Linehan | Jul 2008 | E |
7415443 | Hobson et al. | Aug 2008 | B2 |
7444676 | Asghari-Kamrani et al. | Oct 2008 | B1 |
7469151 | Khan et al. | Dec 2008 | B2 |
7529934 | Fujisawa et al. | May 2009 | B2 |
7548889 | Bhambri et al. | Jun 2009 | B2 |
7567934 | Flitcroft et al. | Jul 2009 | B2 |
7567936 | Peckover et al. | Jul 2009 | B1 |
7571139 | Giordano et al. | Aug 2009 | B1 |
7571142 | Flitcroft et al. | Aug 2009 | B1 |
7580898 | Brown et al. | Aug 2009 | B2 |
7584153 | Brown et al. | Sep 2009 | B2 |
7593896 | Flitcroft et al. | Sep 2009 | B1 |
7606560 | Labrou et al. | Oct 2009 | B2 |
7627531 | Breck et al. | Dec 2009 | B2 |
7627895 | Gifford et al. | Dec 2009 | B2 |
7650314 | Saunders | Jan 2010 | B1 |
7685037 | Reiners et al. | Mar 2010 | B2 |
7702578 | Fung et al. | Apr 2010 | B2 |
7707120 | Dominguez et al. | Apr 2010 | B2 |
7712655 | Wong | May 2010 | B2 |
7734527 | Uzo | Jun 2010 | B2 |
7735733 | Kranzley | Jun 2010 | B2 |
7753265 | Harris | Jul 2010 | B2 |
7770789 | Oder, II et al. | Aug 2010 | B2 |
7784685 | Hopkins, III | Aug 2010 | B1 |
7793851 | Mullen | Sep 2010 | B2 |
7801826 | Labrou et al. | Sep 2010 | B2 |
7805376 | Smith | Sep 2010 | B2 |
7805378 | Berardi et al. | Sep 2010 | B2 |
7818264 | Hammad | Oct 2010 | B2 |
7828220 | Mullen | Nov 2010 | B2 |
7835960 | Breck et al. | Nov 2010 | B2 |
7841523 | Oder, II et al. | Nov 2010 | B2 |
7841539 | Hewton | Nov 2010 | B2 |
7844550 | Walker et al. | Nov 2010 | B2 |
7848980 | Carlson | Dec 2010 | B2 |
7849020 | Johnson | Dec 2010 | B2 |
7853529 | Walker et al. | Dec 2010 | B1 |
7853995 | Chow et al. | Dec 2010 | B2 |
7865414 | Fung et al. | Jan 2011 | B2 |
7873579 | Hobson et al. | Jan 2011 | B2 |
7873580 | Hobson et al. | Jan 2011 | B2 |
7890393 | Talbert et al. | Feb 2011 | B2 |
7891563 | Oder, II et al. | Feb 2011 | B2 |
7896238 | Fein et al. | 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 et al. | May 2011 | B2 |
7954705 | Mullen | Jun 2011 | B2 |
7959076 | Hopkins, III | Jun 2011 | B1 |
7996288 | Stolfo | Aug 2011 | B1 |
8025223 | Saunders et al. | Sep 2011 | B2 |
8046256 | Chien et al. | Oct 2011 | B2 |
8060448 | Jones | Nov 2011 | B2 |
8060449 | Zhu | Nov 2011 | B1 |
8074877 | Mullen et al. | Dec 2011 | B2 |
8074879 | Harris | Dec 2011 | B2 |
8082210 | Hansen et al. | Dec 2011 | B2 |
8095113 | Kean et al. | Jan 2012 | B2 |
8104679 | Brown | Jan 2012 | B2 |
RE43157 | Bishop et al. | Feb 2012 | E |
8109436 | Hopkins, III | Feb 2012 | B1 |
8121942 | Carlson et al. | Feb 2012 | B2 |
8121956 | Carlson et al. | Feb 2012 | B2 |
8126449 | Beenau et al. | Feb 2012 | B2 |
8132723 | Hogg et al. | Mar 2012 | B2 |
8171525 | Pelly et al. | May 2012 | B1 |
8175973 | Davis et al. | May 2012 | B2 |
8190523 | Patterson | May 2012 | B2 |
8196813 | Vadhri | Jun 2012 | B2 |
8205791 | Randazza et al. | Jun 2012 | B2 |
8219489 | Patterson | Jul 2012 | B2 |
8224702 | Mengerink et al. | Jul 2012 | B2 |
8225385 | Chow et al. | Jul 2012 | B2 |
8229852 | Carlson | Jul 2012 | B2 |
8265993 | Chien et al. | Sep 2012 | B2 |
8280777 | Mengerink et al. | Oct 2012 | B2 |
8281991 | Wentker et al. | Oct 2012 | B2 |
8328095 | Oder, II et al. | 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 et al. | Mar 2013 | B2 |
8401539 | Beenau et al. | Mar 2013 | B2 |
8401898 | Chien et al. | Mar 2013 | B2 |
8402555 | Grecia | Mar 2013 | B2 |
8403211 | Brooks et al. | Mar 2013 | B2 |
8412623 | Moon et al. | Apr 2013 | B2 |
8412837 | Emigh et al. | Apr 2013 | B1 |
8417642 | Oren | Apr 2013 | B2 |
8433116 | Butler et al. | Apr 2013 | B2 |
8447699 | Batada et al. | May 2013 | B2 |
8453223 | Svigals et al. | May 2013 | B2 |
8453925 | Fisher et al. | Jun 2013 | B2 |
8458487 | Palgon et al. | Jun 2013 | B1 |
8484134 | Hobson et al. | Jul 2013 | B2 |
8485437 | Mullen et al. | Jul 2013 | B2 |
8494959 | Hathaway et al. | Jul 2013 | B2 |
8498908 | Mengerink et al. | Jul 2013 | B2 |
8504475 | Brand et al. | Aug 2013 | B2 |
8504478 | Saunders et al. | Aug 2013 | B2 |
8510816 | Quach et al. | Aug 2013 | B2 |
8528067 | Hurry et al. | Sep 2013 | B2 |
8533860 | Grecia | Sep 2013 | B1 |
8538845 | Liberty | Sep 2013 | B2 |
8555079 | Shablygin et al. | Oct 2013 | B2 |
8566168 | Bierbaum et al. | Oct 2013 | B1 |
8567670 | Stanfield et al. | Oct 2013 | B2 |
8571939 | Lindsey et al. | Oct 2013 | B2 |
8577336 | Mechaley, Jr. | Nov 2013 | B2 |
8577803 | Chatterjee et al. | Nov 2013 | B2 |
8577813 | Weiss | Nov 2013 | B2 |
8578176 | Mattsson | Nov 2013 | B2 |
8583494 | Fisher | Nov 2013 | B2 |
8584251 | McGuire et al. | Nov 2013 | B2 |
8589237 | Fisher | Nov 2013 | B2 |
8589271 | Evans | Nov 2013 | B2 |
8589291 | Carlson et al. | Nov 2013 | B2 |
8595098 | Starai et al. | Nov 2013 | B2 |
8595812 | Bomar et al. | Nov 2013 | B2 |
8595850 | Spies et al. | Nov 2013 | B2 |
8606638 | Dragt | Dec 2013 | B2 |
8606700 | Carlson et al. | Dec 2013 | B2 |
8606720 | Baker et al. | Dec 2013 | B1 |
8615468 | Varadarajan | Dec 2013 | B2 |
8620754 | Fisher | Dec 2013 | B2 |
8635157 | Smith et al. | Jan 2014 | B2 |
8646059 | Von Behren et al. | Feb 2014 | B1 |
8651374 | Brabson et al. | Feb 2014 | B2 |
8656180 | Shablygin et al. | Feb 2014 | B2 |
8751391 | Freund | Jun 2014 | B2 |
8751642 | Vargas et al. | 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 |
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 |
9646303 | Karpenko et al. | May 2017 | B2 |
9680942 | Dimmick | Jun 2017 | B2 |
10289999 | Gauthier et al. | May 2019 | B2 |
20010029485 | Brody et al. | Oct 2001 | A1 |
20010034720 | Armes | Oct 2001 | A1 |
20010054003 | Chien et al. | Dec 2001 | A1 |
20020007320 | Hogan et al. | Jan 2002 | A1 |
20020016749 | Borecki et al. | Feb 2002 | A1 |
20020029193 | Ranjan et al. | Mar 2002 | A1 |
20020035548 | Hogan et al. | Mar 2002 | A1 |
20020062249 | Iannacci | May 2002 | A1 |
20020073045 | Rubin et al. | Jun 2002 | A1 |
20020116341 | Hogan et al. | Aug 2002 | A1 |
20020133467 | Hobson et al. | Sep 2002 | A1 |
20020138445 | Laage et al. | Sep 2002 | A1 |
20020147913 | Lun Yip | Oct 2002 | A1 |
20020169720 | Wilson et al. | Nov 2002 | A1 |
20030028481 | Flitcroft et al. | Feb 2003 | A1 |
20030046237 | Uberti | Mar 2003 | A1 |
20030101134 | Liu et al. | May 2003 | A1 |
20030130955 | Hawthorne | Jul 2003 | A1 |
20030191709 | Elston et al. | Oct 2003 | A1 |
20030191945 | Keech | Oct 2003 | A1 |
20030208767 | Williamson et al. | Nov 2003 | A1 |
20030220876 | Burger et al. | Nov 2003 | A1 |
20040010462 | Moon et al. | Jan 2004 | A1 |
20040050928 | Bishop et al. | Mar 2004 | A1 |
20040059682 | Hasumi et al. | Mar 2004 | A1 |
20040068472 | Sahota et al. | Apr 2004 | A1 |
20040078328 | Talbert | Apr 2004 | A1 |
20040093281 | Silverstein et al. | May 2004 | A1 |
20040139008 | Mascavage, III | Jul 2004 | A1 |
20040139044 | Rehwald | Jul 2004 | A1 |
20040143532 | Lee | Jul 2004 | A1 |
20040158532 | Breck et al. | Aug 2004 | A1 |
20040210449 | Breck et al. | Oct 2004 | A1 |
20040210498 | Freund | Oct 2004 | A1 |
20040232225 | Bishop et al. | Nov 2004 | A1 |
20040236632 | Maritzen | Nov 2004 | A1 |
20040250068 | Fujisawa et al. | Dec 2004 | A1 |
20040260646 | Berardi et al. | Dec 2004 | A1 |
20050033686 | Peart et al. | Feb 2005 | A1 |
20050033689 | Bonalle | Feb 2005 | A1 |
20050037735 | Coutts | Feb 2005 | A1 |
20050038736 | Saunders | Feb 2005 | A1 |
20050080730 | Sorrentino | Apr 2005 | A1 |
20050108178 | York | May 2005 | A1 |
20050119978 | Ates | Jun 2005 | A1 |
20050127164 | Wankmueller | Jun 2005 | A1 |
20050177496 | Blagg et al. | Aug 2005 | A1 |
20050197945 | Harper | Sep 2005 | A1 |
20050199709 | Linlor | Sep 2005 | A1 |
20050246293 | Ong | Nov 2005 | A1 |
20050269401 | Spitzer et al. | Dec 2005 | A1 |
20050269402 | Spitzer et al. | Dec 2005 | A1 |
20060105742 | Kim et al. | May 2006 | A1 |
20060169767 | Moulton et al. | Aug 2006 | A1 |
20060213972 | Kelley et al. | Sep 2006 | A1 |
20060235795 | Johnson et al. | Oct 2006 | A1 |
20060237528 | Bishop et al. | Oct 2006 | A1 |
20060278704 | Saunders et al. | Dec 2006 | A1 |
20070055630 | Gauthier | Mar 2007 | A1 |
20070107044 | Yuen et al. | May 2007 | A1 |
20070129955 | Dalmia et al. | Jun 2007 | A1 |
20070136193 | Starr | Jun 2007 | A1 |
20070136211 | Brown et al. | Jun 2007 | A1 |
20070170247 | Friedman | Jul 2007 | A1 |
20070179885 | Bird et al. | Aug 2007 | A1 |
20070208671 | Brown et al. | Sep 2007 | A1 |
20070245414 | Chan et al. | Oct 2007 | A1 |
20070288377 | Shaked | Dec 2007 | A1 |
20070291995 | Rivera | Dec 2007 | A1 |
20080015988 | Brown et al. | Jan 2008 | A1 |
20080029607 | Mullen | Feb 2008 | A1 |
20080035738 | Mullen | Feb 2008 | A1 |
20080052226 | Agarwal et al. | Feb 2008 | A1 |
20080054068 | Mullen | Mar 2008 | A1 |
20080054079 | Mullen | Mar 2008 | A1 |
20080054081 | Mullen | Mar 2008 | A1 |
20080065554 | Hogan et al. | Mar 2008 | A1 |
20080065555 | Mullen | Mar 2008 | A1 |
20080201264 | Brown et al. | Aug 2008 | A1 |
20080201265 | Hewton | Aug 2008 | A1 |
20080228646 | Myers et al. | Sep 2008 | A1 |
20080243702 | Hart et al. | Oct 2008 | A1 |
20080245855 | Fein et al. | Oct 2008 | A1 |
20080245861 | Fein et al. | Oct 2008 | A1 |
20080283591 | Oder, II et al. | Nov 2008 | A1 |
20080302869 | Mullen | Dec 2008 | A1 |
20080302876 | Mullen | Dec 2008 | A1 |
20080313264 | Pestoni | Dec 2008 | A1 |
20090006262 | Brown et al. | Jan 2009 | A1 |
20090010488 | Matsuoka et al. | Jan 2009 | A1 |
20090037333 | Flitcroft et al. | Feb 2009 | A1 |
20090037388 | Cooper et al. | Feb 2009 | A1 |
20090043702 | Bennett | Feb 2009 | A1 |
20090048971 | Hathaway et al. | Feb 2009 | A1 |
20090106112 | Dalmia et al. | Apr 2009 | A1 |
20090106160 | Skowronek | Apr 2009 | A1 |
20090134217 | Flitcroft et al. | May 2009 | A1 |
20090157555 | Biffle et al. | Jun 2009 | A1 |
20090159673 | Mullen et al. | Jun 2009 | A1 |
20090159700 | Mullen et al. | Jun 2009 | A1 |
20090159707 | Mullen et al. | Jun 2009 | A1 |
20090173782 | Muscato | Jul 2009 | A1 |
20090198618 | Chan | Aug 2009 | A1 |
20090200371 | Kean et al. | Aug 2009 | A1 |
20090248583 | Chhabra | Oct 2009 | A1 |
20090276347 | Kargman | Nov 2009 | A1 |
20090281948 | Carlson | Nov 2009 | A1 |
20090294527 | Brabson et al. | Dec 2009 | A1 |
20090307139 | Mardikar et al. | Dec 2009 | A1 |
20090308921 | Mullen | Dec 2009 | A1 |
20090327131 | Beenau et al. | Dec 2009 | A1 |
20100008535 | Abulafia et al. | Jan 2010 | A1 |
20100082467 | Carlson | Apr 2010 | A1 |
20100088237 | Wankmueller | Apr 2010 | A1 |
20100094755 | Kloster | Apr 2010 | A1 |
20100100454 | Sines | Apr 2010 | A1 |
20100106644 | Annan et al. | Apr 2010 | A1 |
20100120408 | Beenau et al. | 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 et al. | Jul 2010 | A1 |
20100211505 | Saunders et al. | Aug 2010 | A1 |
20100223186 | Hogan et al. | Sep 2010 | A1 |
20100228668 | Hogan et al. | Sep 2010 | A1 |
20100235284 | Moore | Sep 2010 | A1 |
20100258620 | Torreyson et al. | Oct 2010 | A1 |
20100291904 | Musfeldt et al. | Nov 2010 | A1 |
20100299267 | Faith et al. | Nov 2010 | A1 |
20100306076 | Taveau et al. | Dec 2010 | A1 |
20100325041 | Berardi et al. | Dec 2010 | A1 |
20110010292 | Giordano et al. | Jan 2011 | A1 |
20110016047 | Wu et al. | Jan 2011 | A1 |
20110016320 | Bergsten et al. | Jan 2011 | A1 |
20110040640 | Erikson | Feb 2011 | A1 |
20110047076 | Carlson et al. | Feb 2011 | A1 |
20110083018 | Kesanupalli et al. | Apr 2011 | A1 |
20110087596 | Dorsey | Apr 2011 | A1 |
20110093397 | Carlson et al. | Apr 2011 | A1 |
20110125597 | Oder, II et al. | May 2011 | A1 |
20110153437 | Archer et al. | Jun 2011 | A1 |
20110153498 | Makhotin et al. | Jun 2011 | A1 |
20110154466 | Harper et al. | Jun 2011 | A1 |
20110161233 | Tieken | Jun 2011 | A1 |
20110178926 | Lindelsee et al. | Jul 2011 | A1 |
20110191244 | Dai | Aug 2011 | A1 |
20110238511 | Park et al. | Sep 2011 | A1 |
20110238573 | Varadarajan | 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 et al. | Nov 2011 | A1 |
20110276381 | Mullen et al. | Nov 2011 | A1 |
20110276424 | Mullen | Nov 2011 | A1 |
20110276425 | Mullen | Nov 2011 | A1 |
20110295745 | White et al. | Dec 2011 | A1 |
20110302081 | Saunders et al. | Dec 2011 | A1 |
20120023567 | Hammad | Jan 2012 | A1 |
20120028609 | Hruska | Feb 2012 | A1 |
20120030047 | Fuentes et al. | Feb 2012 | A1 |
20120035998 | Chien et al. | Feb 2012 | A1 |
20120041881 | Basu et al. | Feb 2012 | A1 |
20120047237 | Arvidsson et al. | Feb 2012 | A1 |
20120066078 | Kingston et al. | Mar 2012 | A1 |
20120072350 | Goldthwaite et al. | Mar 2012 | A1 |
20120078735 | Bauer et al. | Mar 2012 | A1 |
20120078798 | Downing et al. | Mar 2012 | A1 |
20120078799 | Jackson et al. | Mar 2012 | A1 |
20120095852 | Bauer et al. | Apr 2012 | A1 |
20120095865 | Doherty et al. | Apr 2012 | A1 |
20120116902 | Cardina et al. | May 2012 | A1 |
20120123882 | Carlson et al. | May 2012 | A1 |
20120123940 | Killian et al. | May 2012 | A1 |
20120129514 | Beenau et al. | May 2012 | A1 |
20120143754 | Patel | Jun 2012 | A1 |
20120143767 | Abadir | Jun 2012 | A1 |
20120143772 | Abadir | Jun 2012 | A1 |
20120158580 | Eram et al. | Jun 2012 | A1 |
20120158593 | Garfinkle et al. | Jun 2012 | A1 |
20120173431 | Ritchie et al. | Jul 2012 | A1 |
20120185386 | Salama et al. | Jul 2012 | A1 |
20120197807 | Schlesser et al. | Aug 2012 | A1 |
20120203664 | Torossian et al. | Aug 2012 | A1 |
20120203666 | Torossian et al. | Aug 2012 | A1 |
20120215688 | Musser et al. | 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 et al. | Sep 2012 | A1 |
20120246079 | Wilson et al. | Sep 2012 | A1 |
20120265631 | Cronic et al. | Oct 2012 | A1 |
20120271770 | Harris et al. | Oct 2012 | A1 |
20120297446 | Webb et al. | Nov 2012 | A1 |
20120300932 | Cambridge et al. | Nov 2012 | A1 |
20120303503 | Cambridge et al. | Nov 2012 | A1 |
20120303961 | Kean et al. | Nov 2012 | A1 |
20120304273 | Bailey et al. | Nov 2012 | A1 |
20120310725 | Chien et al. | Dec 2012 | A1 |
20120310831 | Harris et al. | Dec 2012 | A1 |
20120316992 | Oborne | Dec 2012 | A1 |
20120317035 | Royyuru et al. | Dec 2012 | A1 |
20120317036 | Bower et al. | Dec 2012 | A1 |
20130017784 | Fisher | Jan 2013 | A1 |
20130018757 | Anderson et al. | Jan 2013 | A1 |
20130019098 | Gupta et al. | Jan 2013 | A1 |
20130031006 | McCullagh et al. | Jan 2013 | A1 |
20130054337 | Brendell et al. | Feb 2013 | A1 |
20130054466 | Muscato | Feb 2013 | A1 |
20130054474 | Yeager | Feb 2013 | A1 |
20130081122 | Svigals et al. | Mar 2013 | A1 |
20130091028 | Oder (“J.D.”), II et al. | Apr 2013 | A1 |
20130110658 | Lyman et al. | May 2013 | A1 |
20130111599 | Gargiulo | May 2013 | A1 |
20130117185 | Collison et al. | 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 et al. | Jun 2013 | A1 |
20130145148 | Shablygin et al. | Jun 2013 | A1 |
20130145172 | Shablygin et al. | Jun 2013 | A1 |
20130159178 | Colon et al. | Jun 2013 | A1 |
20130159184 | Thaw | Jun 2013 | A1 |
20130166402 | Parento et al. | Jun 2013 | A1 |
20130166456 | Zhang et al. | Jun 2013 | A1 |
20130173736 | Krzeminski et al. | Jul 2013 | A1 |
20130185202 | Goldthwaite et al. | Jul 2013 | A1 |
20130191227 | Pasa et al. | Jul 2013 | A1 |
20130191286 | Cronic et al. | Jul 2013 | A1 |
20130191289 | Cronic et al. | 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 et al. | Aug 2013 | A1 |
20130212007 | Mattsson et al. | Aug 2013 | A1 |
20130212017 | Bangia | Aug 2013 | A1 |
20130212019 | Mattsson et al. | Aug 2013 | A1 |
20130212024 | Mattsson et al. | Aug 2013 | A1 |
20130212026 | Powell et al. | Aug 2013 | A1 |
20130212666 | Mattsson et al. | Aug 2013 | A1 |
20130218698 | Moon et al. | Aug 2013 | A1 |
20130218769 | Pourfallah et al. | Aug 2013 | A1 |
20130226799 | Raj | Aug 2013 | A1 |
20130226802 | Hammad et al. | 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 | Said | Sep 2013 | A1 |
20130254052 | Royyuru et al. | Sep 2013 | A1 |
20130254102 | Royyuru | Sep 2013 | A1 |
20130254117 | Von Mueller et al. | Sep 2013 | A1 |
20130262296 | Thomas et al. | Oct 2013 | A1 |
20130262302 | Lettow et al. | Oct 2013 | A1 |
20130262315 | Hruska | Oct 2013 | A1 |
20130262316 | Hruska | Oct 2013 | A1 |
20130262317 | Collinge et al. | Oct 2013 | A1 |
20130275300 | Killian et al. | Oct 2013 | A1 |
20130275307 | Khan | Oct 2013 | A1 |
20130275308 | Paraskeva et al. | Oct 2013 | A1 |
20130282502 | Jooste | Oct 2013 | A1 |
20130282575 | Mullen et al. | Oct 2013 | A1 |
20130282588 | Hruska | Oct 2013 | A1 |
20130297501 | Monk et al. | Nov 2013 | A1 |
20130297504 | Nwokolo et al. | Nov 2013 | A1 |
20130297508 | Belamant | Nov 2013 | A1 |
20130304649 | Cronic et al. | Nov 2013 | A1 |
20130308778 | Fosmark et al. | Nov 2013 | A1 |
20130311382 | Fosmark et al. | Nov 2013 | A1 |
20130317982 | Mengerink et al. | Nov 2013 | A1 |
20130332344 | Weber | Dec 2013 | A1 |
20130339253 | Sincai | Dec 2013 | A1 |
20130346305 | Mendes et al. | Dec 2013 | A1 |
20130346314 | Mogollon et al. | Dec 2013 | A1 |
20140007213 | Sanin et al. | 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 |
20140032419 | Anderson | Jan 2014 | A1 |
20140040137 | Carlson et al. | Feb 2014 | A1 |
20140040139 | Brudnicki et al. | Feb 2014 | A1 |
20140040144 | Plomske et al. | Feb 2014 | A1 |
20140040145 | Ozvat et al. | Feb 2014 | A1 |
20140040148 | Ozvat et al. | Feb 2014 | A1 |
20140040628 | Fort et al. | Feb 2014 | A1 |
20140041018 | Bomar et al. | Feb 2014 | A1 |
20140046843 | Liscia | Feb 2014 | A1 |
20140046853 | Spies et al. | Feb 2014 | A1 |
20140047551 | Nagasundaram et al. | Feb 2014 | A1 |
20140052532 | Tsai et al. | Feb 2014 | A1 |
20140052620 | Rogers et al. | Feb 2014 | A1 |
20140052637 | Jooste et al. | 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 |
20140249945 | Gauthier et al. | Sep 2014 | A1 |
20140258113 | Gauthier et al. | Sep 2014 | A1 |
20140294701 | Dai et al. | Oct 2014 | A1 |
20140297534 | Patterson | Oct 2014 | A1 |
20140310183 | Weber | Oct 2014 | A1 |
20140324690 | Allen et al. | 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 |
20150081544 | Schulz et al. | Mar 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 |
20150278799 | Palanisamy | Oct 2015 | A1 |
20150287037 | Salmon et al. | Oct 2015 | A1 |
20150312038 | Palanisamy | Oct 2015 | A1 |
20150319158 | Kumnick | Nov 2015 | A1 |
20150324736 | Sheets et al. | Nov 2015 | A1 |
20150332262 | Lingappa | Nov 2015 | A1 |
20150356560 | Shastry et al. | Dec 2015 | A1 |
20150363781 | Badenhorst | Dec 2015 | A1 |
20160028550 | Gaddam et al. | Jan 2016 | A1 |
20160036790 | Shastry et al. | Feb 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 |
20160092874 | O'Regan et al. | Mar 2016 | A1 |
20160103675 | Aabye et al. | Apr 2016 | A1 |
20160119296 | Laxminarayanan et al. | Apr 2016 | A1 |
20160132878 | O'Regan et al. | May 2016 | A1 |
20160140545 | Flurscheim et al. | May 2016 | A1 |
20160148197 | Dimmick | May 2016 | A1 |
20160148212 | Dimmick | May 2016 | A1 |
20160171479 | Prakash et al. | Jun 2016 | A1 |
20160173483 | Wong et al. | Jun 2016 | A1 |
20160197725 | Hammad | Jul 2016 | A1 |
20160210628 | McGuire | Jul 2016 | A1 |
20160217461 | Gaddam et al. | Jul 2016 | A1 |
20160218875 | Le Saint et al. | Jul 2016 | A1 |
20160224976 | Basu et al. | Aug 2016 | A1 |
20160224977 | Sabba et al. | Aug 2016 | A1 |
20160232527 | Patterson | Aug 2016 | A1 |
20160239842 | Cash et al. | Aug 2016 | A1 |
20160269391 | Gaddam et al. | Sep 2016 | A1 |
20160308995 | Youdale et al. | Oct 2016 | A1 |
20170046696 | Powell et al. | Feb 2017 | A1 |
20170076288 | Awasthi | Mar 2017 | A1 |
20170103387 | Weber | Apr 2017 | A1 |
20170109745 | Al-Bedaiwi et al. | Apr 2017 | A1 |
20170148013 | Rajurkar et al. | May 2017 | A1 |
20170163617 | Laxminarayanan et al. | Jun 2017 | A1 |
20170163629 | Law et al. | Jun 2017 | A1 |
20170186001 | Reed et al. | Jun 2017 | A1 |
20170200156 | Karpenko et al. | Jul 2017 | A1 |
20170200165 | Laxminarayanan et al. | Jul 2017 | A1 |
20170201520 | Chandoor et al. | Jul 2017 | A1 |
20170220818 | Nagasundaram et al. | Aug 2017 | A1 |
20170221054 | Flurscheim et al. | Aug 2017 | A1 |
20170221056 | Karpenko et al. | Aug 2017 | A1 |
20170228723 | Taylor et al. | Aug 2017 | A1 |
20170236113 | Chitalia et al. | Aug 2017 | A1 |
20170293914 | Girish et al. | Oct 2017 | A1 |
20170295155 | Wong | Oct 2017 | A1 |
20170364903 | Lopez | Dec 2017 | A1 |
20170373852 | Cassin et al. | Dec 2017 | A1 |
20180006821 | Kinagi | Jan 2018 | A1 |
20180075081 | Chipman | Mar 2018 | A1 |
20180247303 | Raj et al. | Aug 2018 | A1 |
20180262334 | Hammad | Sep 2018 | A1 |
20180268399 | Spector et al. | Sep 2018 | A1 |
20180268405 | Lopez | Sep 2018 | A1 |
20180285875 | Law et al. | Oct 2018 | A1 |
20180324184 | Kaja et al. | Nov 2018 | A1 |
20180324584 | Lopez | Nov 2018 | A1 |
20190020478 | Girish et al. | Jan 2019 | A1 |
20190066069 | Faith et al. | Feb 2019 | A1 |
Number | Date | Country |
---|---|---|
2006287606 | Sep 2011 | AU |
PI06156657 | Mar 2019 | BR |
2621358 | Feb 2017 | CA |
1549977 | Nov 2004 | CN |
1028401 | Aug 2000 | EP |
2156397 | Feb 2010 | EP |
269725 | Nov 2015 | IN |
2005118224 | May 2005 | JP |
2005520269 | Jul 2005 | JP |
5199095 | Feb 2013 | JP |
2013050968 | Mar 2013 | JP |
5519754 | Apr 2014 | JP |
101379710 | Mar 2014 | KR |
285539 | Apr 2011 | MX |
2259587 | Aug 2005 | RU |
2004109577 | Aug 2005 | RU |
2419872 | May 2011 | RU |
0014648 | Mar 2000 | WO |
0135304 | May 2001 | WO |
0173580 | Oct 2001 | WO |
0135304 | May 2002 | WO |
03019445 | Mar 2003 | WO |
03081832 | Oct 2003 | WO |
2004006064 | Jan 2004 | WO |
2004042536 | May 2004 | WO |
2004051585 | Jun 2004 | WO |
2005001751 | Jan 2005 | WO |
2006113834 | Oct 2006 | WO |
2007030480 | Jun 2007 | 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 |
WO-2013155627 | Oct 2013 | WO |
2013179271 | Dec 2013 | WO |
Entry |
---|
“How it Works”, Speedpass, Available Online at: http://speedpass.com/how/index.jsp, Accessed from Internet on Oct. 6, 2005, 1 page. |
“How it Works Technology”, Speedpass, Available Online at: http://speedpass.com/how/technology.jsp, Accessed from Internet on Oct. 6, 2005, 1 page. |
“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”, USPTO Patent Trial and Appeal Board, IPR 2016-00600, Feb. 17, 2016, 65 pages. |
“Questions & Answers Safety & Security”, Speedpass, Available Online at: http://speedpass.com/faqs/category.jsp?categoryiD=3, Accessed from Internet on Oct. 6, 2005, 1 page. |
U.S. Appl. No. 11/398,887 , “Advisory Action”, dated May 8, 2012, 3 pages. |
U.S. Appl. No. 11/398,887 , “Final Office Action”, dated Dec. 22, 2011, 23 pages. |
U.S. Appl. No. 11/398,887 , “Non-Final Office Action”, dated Jan. 28, 2010, 13 pages. |
U.S. Appl. No. 11/398,887 , “Non-Final Office Action”, dated May 8, 2013, 13 pages. |
U.S. Appl. No. 11/398,887 , “Non-Final Office Action”, dated Jun. 22, 2010, 16 pages. |
U.S. Appl. No. 11/398,887 , “Non-Final Office Action”, dated Apr. 28, 2011, 19 pages. |
U.S. Appl. No. 11/398,887 , “Non-Final Office Action”, dated Jun. 16, 2009, 20 pages. |
U.S. Appl. No. 11/398,887 , “Non-Final Office Action”, dated Nov. 13, 2008, 22 pages. |
U.S. Appl. No. 11/398,887 , “Non-Final Office Action”, dated Jan. 24, 2011, 7 pages. |
U.S. Appl. No. 11/398,887 , “Notice of Allowance”, dated Feb. 14, 2014, 12 pages. |
U.S. Appl. No. 14/275,715 , “Final Office Action”, dated May 15, 2018, 13 pages. |
U.S. Appl. No. 14/275,715 , “Final Office Action”, dated Aug. 7, 2015, 24 pages. |
U.S. Appl. No. 14/275,715 , “Final Office Action”, dated Jun. 10, 2019, 8 pages. |
U.S. Appl. No. 14/275,715 , “Non-Final Office Action”, dated Jan. 14, 2015, 16 pages. |
U.S. Appl. No. 14/275,715 , “Non-Final Office Action”, dated Jun. 2, 2017, 20 pages. |
U.S. Appl. No. 14/275,715 , “Non-Final Office Action”, dated Dec. 19, 2016, 25 pages. |
U.S. Appl. No. 14/275,715 , “Non-Final Office Action”, dated Feb. 21, 2019, 6 pages. |
U.S. Appl. No. 14/275,718 , “Final Office Action”, dated Nov. 14, 2017, 10 pages. |
U.S. Appl. No. 14/275,718 , “Non Final Office Action”, dated Mar. 27, 2017, 18 pages. |
U.S. Appl. No. 14/275,718 , “Notice of Allowance”, dated Dec. 28, 2018, 10 pages. |
U.S. Appl. No. 14/275,718 , “Supplemental Notice of Allowance”, dated Mar. 20, 2019, 2 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, 90 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, 62 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 No.”, Self-Cleaning Token Valut, filed Sep. 14, 2016, 52 pages. |
U.S. Appl. No. 15/462,658 , “U.S. Patent Application No.”, Replacing Token on a Multi-Token User Device, filed Mar. 17, 2017, 58 pages. |
U.S. Appl. No. 15/585,077 , “U.S. Patent Application No.”, System and Method Using Interaction Token, filed May 2, 2017, 36 pages. |
U.S. Appl. No. 15/956,991 , “U.S. Patent Application No.”, Mobile Tokenization Hub, filed Apr. 19, 2018, 118 pages. |
U.S. Appl. No. 15/977,921 , “U.S. Patent Application No.”, Integration of Verification Tokens With Mobile Communication Devices, filed May 11, 2018, 112 pages. |
U.S. Appl. No. 16/287,244 , “U.S. Patent Application No.”, Payment Channel Returning Limited Use Proxy Dynamic Value, filed Feb. 27, 2019, 32 pages. |
U.S. Appl. No. 16/302,054 , “U.S. Patent Application No.”, Methods of Distributing Tokens and Managing Token Relationships, filed Nov. 15, 2018, 62 pages. |
U.S. Appl. No. 16/311,144 , “U.S. Patent Application No.”, Encryption Key Exchange Process Using Access Device, filed Dec. 18, 2018, 61 pages. |
U.S. Appl. No. 16/368,262 , “Non-Final Office Action”, dated Jun. 5, 2020, 8 pages. |
U.S. Appl. No. 16/368,262 , “Notice of Allowance”, dated Oct. 9, 2020, 8 pages. |
U.S. Appl. No. 61/738,832 , “U.S. Provisional Application No.”, Management of Sensitive Data, filed Dec. 18, 2012, 22 pages. |
U.S. Appl. No. 61/751,763 , “U.S. Provisional Application No.”, Payments Bridge, filed Jan. 11, 2013, 64 pages. |
U.S. Appl. No. 61/879,632 , “U.S. Provisional Application No.”, Systems and Methods for Managing Mobile Cardholder Verification Methods, filed Sep. 18, 2013, 24 pages. |
U.S. Appl. No. 61/892,407 , “U.S. Provisional Application No.”, Issuer Over-The-Air Update Method and System, filed Oct. 17, 2013, 28 pages. |
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, 67 pages. |
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, 51 pages. |
U.S. Appl. No. 62/000,288 , “U.S. Provisional Application No.”, Payment System Canonical Address Format, filed May 19, 2014, 58 pages. |
U.S. Appl. No. 62/003,717 , “U.S. Provisional Application No.”, Mobile Merchant Application, filed May 28, 2014, 58 pages. |
U.S. Appl. No. 62/024,426 , “U.S. Provisional Application No.”, Secure Transactions Using Mobile Devices, filed Jul. 14, 2014, 102 pages. |
U.S. Appl. No. 62/037,033 , “U.S. Provisional Application No.”, Sharing Payment Token, filed Aug. 13, 2014, 36 pages. |
U.S. Appl. No. 62/038,174 , “U.S. Provisional Application No.”, Customized Payment Gateway, filed Aug. 15, 2014, 42 pages. |
U.S. Appl. No. 62/042,050 , “U.S. Provisional Application No.”, Payment Device Authentication and Authorization System, filed Aug. 26, 2014, 120 pages. |
U.S. Appl. No. 62/053,736 , “U.S. Provisional Application No.”, Completing Transactions Without a User Payment Device, filed Sep. 22, 2014, 31 pages. |
U.S. Appl. No. 62/054,346 , “U.S. Provisional Application No.”, Mirrored Token Vault, filed Sep. 23, 2014, 38 pages. |
U.S. Appl. No. 62/103,522 , “U.S. Provisional Application No.”, Methods and Systems for Wallet Provider Provisioning, filed Jan. 14, 2015, 39 pages. |
U.S. Appl. No. 62/108,403 , “U.S. Provisional Application No.”, Wearables With NFC HCE, filed Jan. 27, 2015, 32 pages. |
U.S. Appl. No. 62/117,291 , “U.S. Provisional Application No.”, Token and Cryptogram Using Transaction Specific Information, filed Feb. 17, 2015, 25 pages. |
U.S. Appl. No. 62/128,709 , “U.S. Provisional Application No.”, Tokenizing Transaction Amounts, filed Mar. 5, 2015, 30 pages. |
AU2006287606 , “Notice of Acceptance”, dated May 26, 2011, 3 pages. |
BRPI0615665-7 , “Notice of Allowance”, dated Jan. 2, 2019, 3 pages. |
BRPI0615665-7 , “Office Action”, dated Mar. 27, 2018, 9 pages. |
CA2.621.358 , “Notice of Allowance”, dated Jul. 21, 2016, 1 page. |
CA2,621,358 , “Office Action”, dated Jan. 10, 2013, 2 pages. |
CA2.621.358 , “Office Action”, dated Aug. 13, 2015, 3 pages. |
CA2.621.358 , “Office Action”, dated Mar. 19, 2014, 3 pages. |
CN200680041246.7 , “Office Action”, dated Sep. 13, 2013, 14 pages. |
CN200680041246.7 , “Office Action”, dated Sep. 13, 2010, 18 pages. |
CN200680041246.7 , “Office Action”, dated Dec. 30, 2013, 19 pages. |
CN200680041246.7 , “Office Action”, dated Jan. 30, 2012, 19 pages. |
CN200680041246.7 , “Office Action Response”, dated May 12, 2012, 15 pages. |
Edward et al., “Universal Electronic Payment Apparatuses, Methods and Systems”, WIPO/Thomson, 6/3K/3, Sep. 27, 2011, 2 pages. |
IN1693/CHENP/2008 , “Examination Report”, dated Aug. 3, 2015, 8 pages. |
IN1693/CHENP/2008 , “First Examination Report”, dated Aug. 26, 2014, 3 pages. |
JP2008-530147 , “Notice of Allowance”, dated Jan. 8, 2013, 3 pages. |
JP2008-530147 , “Office Action”, dated Oct. 23, 2012. |
JP2008-530147 , “Office Action”, dated Feb. 21, 2012, 15 pages. |
JP2008-530147 , “Office Action”, dated Jun. 12, 2012, 7 pages. |
JP2008-530147 , “Office Action Response”, dated May 21, 2012, 14 pages. |
JP2012-227388 , “Notice of Decision to Grant”, dated Mar. 4, 2014, 4 pages. |
JP2012-227388 , “Office Action”, dated Jul. 23, 2013, 12 pages. |
JP2012-227388 , “Office Action”, dated Nov. 12, 2013, 2 pages. |
Judson , “Encryption Switch Processing”, WIPO/Thompson; 6/3K/5, Nov. 5, 2009, 1 page. |
KR10-2008-7008119 , “Office Action”, dated Mar. 29, 2013, 4 pages. |
KR10-2008-7008119 , “Office Action”, dated Sep. 10, 2013, 6 Pages. |
KR2008-7008119 , “Notice of Allowance”, dated Dec. 30, 2013, 3 pages. |
Lyle , “Merchant-Consumer Bridging Platform Apparatuses, Methods and Systems”, WIPO/Thomson; 6/3K/4, (Item 2 from file:349), Feb. 5, 2011, 1 page. |
MX/A/2008/003108 , “Office Action”, dated Nov. 10, 2010, 3 pages. |
PCT/US2006/034612 , “International Search Report and Written Opinion”, dated Apr. 30, 2007, 10 pages. |
RU2008113214 , “Notice of Decision to Grant”, dated Dec. 1, 2010, 5 pages. |
RU2008113214 , “Office Action”, dated Aug. 31, 2010, 10 pages. |
Number | Date | Country | |
---|---|---|---|
20210133733 A1 | May 2021 | US |
Number | Date | Country | |
---|---|---|---|
60714635 | Sep 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11398887 | Apr 2006 | US |
Child | 14275718 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16368262 | Mar 2019 | US |
Child | 17145919 | US | |
Parent | 14275718 | May 2014 | US |
Child | 16368262 | US |