Patent Grant
11720893
A transaction is typically authorized by a user at the time the transaction is requested from a resource provider. For example, a cardholder may authorize a purchase at a point of sale. The user's sensitive information, such as a primary account number (PAN), access number, or PIN number, may be communicated by a device utilized to conduct the transaction (e.g., a credit card, a mobile device, a communication device, a security device, etc.). However, users may not want to share their sensitive information with resource providers due to security concerns.
Therefore, a secure and efficient method is needed to provide more users with the capability to conduct transactions using their devices, while keeping their sensitive information hidden from resource providers. This may reduce risk both of fraud by the resource provider, as well as interception and misuse of the sensitive information by reducing the number of parties to which the sensitive information is communicated. Embodiments of the invention address this and other problems, individually and collectively.
According to some embodiments of the invention, systems and methods are provided that allow consumers to use their communication devices to perform transactions, without requiring the use of a contactless element or specialized hardware at the resource provider. To complete a transaction, a resource provider may electronically generate a code representing transaction data (e.g., resource provider data, location data, transaction amount, etc.) and display it on an access device, for example. The code may be, for example, a QR code. A user may scan the code with his or her communication device using a camera associated with the communication device, for example. The code may be interpreted by an application on the communication device and the transaction data may be displayed to the user in one embodiment. The user may request and receive a token at the communication device corresponding to sensitive information selected to perform the transaction. The user may then provide the token and the transaction data via the communication device to an application provider computer, which may facilitate completion of the transaction between the user and the resource provider using the transaction data and the token, as described further herein.
According some embodiments of the invention, a method of performing a transaction between a user and a resource provider is provided. The method comprises scanning, at a communication device of the user, a code displayed by an access device associated with the resource provider. The method further comprises determining, by the communication device, transaction data associated with the code. The method further comprises initiating, by the communication device, requesting a token corresponding to sensitive information of the user by providing the transaction data to a server computer to complete the transaction. In embodiments of the invention, “initiating requesting” may include requesting, by the communication device, the token (or other data). It may also include sending, by the communication device, a communication to another computer such as a remote server computer, which causes the remote server computer to request the token (or other data).
Embodiments of the invention are further directed to a communication device comprising a processor and a memory or computer-readable medium. The memory can comprise code, executable by the processor, for implementing the above method described herein.
According to some embodiments of the invention, a method is provided. The method comprises receiving, by an application provider computer, transaction data from a communication device. The transaction data was obtained by the communication device from an access device in a transaction. The method further comprises transmitting, by the application provider computer, a token request for a token to a token server. The method further comprises receiving, by the application provider computer, the token. The token is used to complete the transaction.
According to some embodiments of the invention, a method of performing a transaction between a user and a resource provider is provided. According to the method, transaction data comprising a transaction type indicator is received from a communication device, wherein at least some of the transaction data is received from an access device. The transaction data is analyzed, and it is determined that the transaction type indicator is one of a plurality of transaction type indicators associated with a plurality of different transaction types. Transaction processing is then initiated according to the transaction type indicator.
Embodiments of the invention are further directed to a server computer comprising a processor and a non-transitory computer readable medium. The computer readable medium can comprise code, executable by the processor, for implementing any of the methods described herein.
These and other embodiments of the invention are described in further detail below.
Embodiments of the present invention relate to systems and methods that allow users to use their communication devices to perform transactions (e.g., payment transactions, access transactions, etc.). To complete a transaction, a resource provider electronically generates a code representing transaction data and displays it on an access device. The user scans the code with his or her communication device using a camera associated with the communication device, for example. The code is interpreted by an application on the communication device. The user may request and receive a token at the communication device corresponding to sensitive information selected to perform the transaction (e.g., a primary account number). The user may then provide the token and the transaction data via the communication device to a server computer, which may facilitate completion of the transaction between the user and the resource provider using the transaction data and the token, as described further herein.
Before discussing specific embodiments and examples, some descriptions of terms used herein are provided below.
An “access device” may be any suitable device that provides access to a remote system. An access device may also be used for communicating with a resource provider computer, a transaction processing computer, an authentication computer, or any other suitable system. An access device may generally be located in any suitable location, such as at the location of a resource provider or merchant. An access device may be in any suitable form. Some examples of access devices include POS or point of sale devices (e.g., POS terminals), cellular phones, PDAs, personal computers (PCs), tablet PCs, hand-held specialized readers, set-top boxes, electronic cash registers (ECRs), automated teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, terminals, and the like. An access device may use any suitable contact or contactless mode of operation to send or receive data from, or associated with, a user communication device. In some embodiments, where an access device may comprise a POS terminal, any suitable POS terminal may be used and may include a reader, a processor, and a computer-readable medium. A reader may include any suitable contact or contactless mode of operation. For example, exemplary card readers can include radio frequency (RF) antennas, optical scanners, bar code readers, or magnetic stripe readers to interact with a payment device and/or mobile device. Other examples of access devices include devices (e.g., locks, gates, access control boxes, etc.) that control physical access to locations (e.g., venues, transit stations, homes, offices, buildings, etc.), as well as software devices that control access to data or information.
An “acquirer” may typically be a business entity (e.g., a commercial bank) that has a business relationship with a particular merchant or other entity. Some entities can perform both issuer and acquirer functions. Some embodiments may encompass such single entity issuer-acquirers. An acquirer may operate an acquirer computer, which can also be generically referred to as a “transport computer”.
An “authorization request message” may be an electronic message that is sent to a payment processing network and/or an issuer of a payment card to request authorization for a transaction. An authorization request message according to some embodiments may comply with (International Organization of Standardization) ISO 8583, which is a standard for systems that exchange electronic transaction information associated with a payment made by a consumer using a payment device or payment account. The authorization request message may include an issuer account identifier that may be associated with a payment device or payment account. An authorization request message may also comprise additional data elements corresponding to “identification information” including, by way of example only: a service code, a CVV (card verification value), a dCW (dynamic card verification value), an expiration date, etc. . . . An authorization request message may also comprise “transaction information,” such as any information associated with a current transaction, such as the transaction amount, merchant identifier, merchant location, etc., as well as any other information that may be utilized in determining whether to identify and/or authorize a transaction.
An “authorization response message” may be an electronic message reply to an authorization request message generated by an issuing financial institution or a payment processing network. The authorization response message may include, by way of example only, one or more of the following status indicators: Approval—transaction was approved; Decline—transaction was not approved; or Call Center—response pending more information, merchant must call the toll-free authorization phone number. The authorization response message may also include an authorization code, which may be a code that a credit card issuing bank returns in response to an authorization request message in an electronic message (either directly or through the payment processing network) to the merchant's access device (e.g. POS equipment) that indicates approval of the transaction. The code may serve as proof of authorization. As noted above, in some embodiments, a payment processing network may generate or forward the authorization response message to the merchant.
An “authorizing entity” may be an entity that authorizes a request. Examples of an authorizing entity may be an issuer, a governmental agency, a document repository, an access administrator, etc.
A “code” may be any system of words, letters, numbers, figures, and/or other symbols substituted for data. Exemplary codes include barcodes, QR codes, SKUs, etc.
A “communication device” may comprise any suitable electronic device that may be operated by a user, which may also provide remote communication capabilities to a network. Examples of remote communication capabilities include using a mobile phone (wireless) network, wireless data network (e.g., 3G, 4G or similar networks), Wi-Fi, Wi-Max, or any other communication medium that may provide access to a network such as the Internet or a private network. Examples of communication devices include mobile phones (e.g., cellular phones), PDAs, tablet computers, net books, laptop computers, personal music players, handheld specialized readers, watches, fitness bands, ankle bracelets, rings, earrings, etc., as well as automobiles with remote communication capabilities. A communication device may comprise any suitable hardware and software for performing such functions, and may also include multiple devices or components (e.g., when a device has remote access to a network by tethering to another device—i.e., using the other device as a modem—both devices taken together may be considered a single communication device).
A “consumer” may include an individual or a user that operates a communication device to conduct a transaction on an account or otherwise manage an account.
A “digital wallet” can include an electronic application or device that allows an individual to conduct electronic commerce transactions. A digital wallet may store user profile information, payment credentials, bank account information, one or more digital wallet identifiers, and/or the like, and can be used in a variety of transactions, such as but not limited to eCommerce, social networks, money transfer/personal payments, mobile commerce, proximity payments, gaming, and/or the like for retail purchases, digital goods purchases, utility payments, purchasing games or gaming credits from gaming websites or systems, transferring funds between users, and/or the like. A digital wallet may be designed to streamline the purchase and payment process. A digital wallet may allow the user to load one or more payment cards onto the digital wallet so as to make a payment without having to enter an account number or present a physical card. A digital wallet may also store transaction records (e.g., electronic receipts).
An “issuer” may typically refer to a business entity (e.g., a bank) that maintains an account for a user. An issuer may also issue payment credentials stored on communication devices.
“Provisioning” may include a process of providing data for use. For example, provisioning may include providing, delivering, or enabling a token on a communication device. Provisioning may be completed by any entity within or external to the transaction system. For example, in some embodiments, tokens may be provisioned by an issuer or a transaction processing network onto a mobile device. The provisioned tokens may have corresponding token data stored and maintained in a token vault or token registry. In some embodiments, a token vault or token registry may generate a token that may then be provisioned or delivered to a device.
A “resource provider” may be an entity that can provide a resource such as goods, services, information, and/or access. Examples of a resource provider include merchants, access devices, secure data access points, etc. A “merchant” may typically be an entity that engages in transactions and can sell goods or services, or provide access to goods or services.
A “server computer” may include 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 server computer may be coupled to a database and may include any hardware, software, other logic, or combination of the preceding for servicing the requests from one or more client computers. The server computer may comprise one or more computational apparatuses and may use any of a variety of computing structures, arrangements, and compilations for servicing the requests from one or more client computers.
A “service provider” or “application provider” may be an entity that can provide a service or application. An example of a service provider is a digital wallet provider.
A “token” may include a substitute identifier for some information. For example, a payment token may include an identifier for a payment account that is a substitute for an account identifier, such as a primary account number (PAN). For instance, a token may include a series of alphanumeric characters that may be used as a substitute for an original account identifier. For example, a token “4900 0000 0000 0001” may be used in place of a PAN “4147 0900 0000 1234.” In some embodiments, a token may be “format preserving” and may have a numeric format that conforms to the account identifiers used in existing payment processing networks (e.g., ISO 8583 financial transaction message format). In some embodiments, a token may be used in place of a PAN to initiate, authorize, settle or resolve a payment transaction. The token may also be used to represent the original credential in other systems where the original credential would typically be provided. In some embodiments, a token value may be generated such that the recovery of the original PAN or other account identifier from the token value may not be computationally derived. Further, in some embodiments, the token format may be configured to allow the entity receiving the token to identify it as a token and recognize the entity that issued the token.
“Tokenization” is a process by which sensitive data is replaced with substitute data. For example, a real account identifier (e.g., a primary account number (PAN)) may be tokenized by replacing the real account identifier with a substitute number that may be associated with the real account identifier. Further, tokenization can be applied to any other information to substitute the underlying information with a token. “Token exchange” or “de-tokenization” is a process of restoring the data that was substituted during tokenization. For example, a token exchange may include replacing a payment token with its associated primary account number (PAN). Further, de-tokenization or token exchange may be applied to any other information to retrieve the substituted information from a token. In some embodiments, token exchange can be achieved via a transactional message, such as an ISO message, an application programming interface (API), or another type of web interface (e.g., web request).
“Transaction data” may comprise any data associated with or indicative of a transaction between a resource provider (e.g., a merchant) and a user (e.g., a consumer). For example, transaction data may include resource provider data (e.g., resource provider ID, card acceptor ID, etc.), user data location data, transaction details (e.g., transaction ID, transaction amount, etc.).
A “transaction processing computer” may include a network of one or more devices that can process and route transaction request messages. An exemplary transaction processing computer may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, transaction scoring services, and clearing and settlement services. An exemplary transaction processing system may include VisaNet™. Transaction processing systems such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, may include a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system which performs clearing and settlement services.
The code may be received by the communication device 10 from the access device 20 at step S110A. The code may have been previously generated by access device 20 or may have been generated in real time by access device 20. The code may be static (i.e., the same for multiple transactions) or dynamic (i.e., different for different transactions). The code may be displayed electronically by the access device 20, or may be printed on a piece of paper or otherwise displayed in a non-electronic fashion to the communication device 10. The communication device 10 may scan the code using a camera or any other visual detection device incorporated into or associated with the communication device 10, for example. In other embodiments, the code may be data that is transmitted wirelessly (e.g., through NFC, Bluetooth, infrared, etc.) from the access device 20 to the communication device 10.
The code may encode transaction data, including resource provider data such as a resource provider identifier and card acceptor identifier, location data associated with the access device 20 and/or the resource provider computer 25, transaction details such as a transaction amount, an identifier associated with the transport computer 50, an application identifier (AID), combinations thereof, and/or the like. In some embodiments, some of this transaction data, such as the transaction amount, may be omitted, as described further herein. In some embodiments, the code may be a QR code, a barcode, or any other code that may be used to represent data. In the embodiment shown in
The code may be interpreted (or decoded) by communication device 10 (e.g., through an application) to extract the underlying transaction data. In some embodiments, the communication device 10 may display the transaction data upon interpreting (or decoding) the code. In some embodiments, the communication device 10 may allow the user to confirm the transaction data upon interpreting the code.
In some embodiments, a transaction amount (e.g., a purchase amount, an amount of access to provide, what to provide access to, etc.) may not be provided in the code. Thus, a transaction amount may not be included in the transaction data extracted from the code. In these embodiments, the user may enter the transaction amount into the communication device 10 after scanning the code.
In some embodiments, the communication device 10 may display a list of sensitive information that may be used to complete the transactions (e.g., a list of primary account numbers (PANs), payment devices, passwords, PINs, etc.), and allow the user to select one or more pieces of sensitive information from the list. The communication device 10 may also generate, request or retrieve a token reference identifier corresponding to the sensitive information. A mapping between the token reference identifier and a token representing the sensitive information may be stored by the token server 30, as described further herein.
At step S115A, the communication device 10 may initiate the transaction and also initiated a request for a token by transmitting the transaction data, including the transaction amount and the token reference identifier, to an application provider computer 40. At step S120A, the application provider computer 40 may send the token reference identifier to the token server 30 to request the token corresponding to the token reference identifier, as well as to request a verification value associated with the sensitive information (e.g., a card verification number (CVN) associated with a selected payment device). At step S125A, the token server 30 may return the token (including any accompanying data) and the verification value to the application provider computer 40.
The application provider computer 40 may generate a unique transaction identifier (e.g., a UUID) corresponding to the transaction. At step S130A, the application provider computer 40 may transmit the token, transaction amount, transaction identifier, and/or other transaction data to a gateway computer 45. At step S137A, the application provider computer 40 may transmit the transaction identifier to the communication device 10 for display to the user.
At step S135A, the gateway computer 45 determines the proper transport computer 50 from the transaction data (e.g., through an identifier associated with the transport computer 50), and routes the token, transaction amount, transaction identifier, and/or other transaction data to the transport computer 50. The transport computer 50 may be, for example, an acquirer associated with the resource provider computer 25. At step S140A, the transport computer 50 may generate an authorization request message using the token data, the verification value, the transaction amount, and/or other transaction data, and route the authorization request message to the transaction processing computer 60.
At step S145A, the transaction processing computer 60 may transmit the token and any other token-related data to the token server 30. The token server 30 may identify the sensitive information associated with the token (e.g., through a mapping or look-up table, by applying an algorithm to the token, and/or through any other means). At step S150A, the token server 30 may return the sensitive information to the transaction processing computer 60 to process the transaction using the sensitive information.
The transaction processing computer 60 may modify the authorization request message to include the sensitive information (e.g., a PAN) instead of the token, and transmit the modified authorization request message to the authorizing entity computer 70. The authorizing entity computer 70 may determine whether to authorize or decline the transaction. For example, the authorizing entity computer 70 may determine whether the sensitive information is correct, whether the verification value is correct, whether the user is authorized to use the sensitive information, whether the transaction amount is available (e.g., whether there are sufficient funds for a payment transaction, whether the requested amount of access is authorized, etc.), combinations thereof, and/or the like.
At step S160A, the authorizing entity computer 70 returns its authorization decision via an authorization response message to the transaction processing computer 60. The authorization response message may include the sensitive information; thus, the transaction processing computer 60 may replace the sensitive information with the token in the authorization response message. At step S165A, the transaction processing computer 60 may route the modified authorization response message to the transport computer 50.
The transport computer 50 may extract the resource provider identifier from the authorization response message, then route the authorization response message to the appropriate resource provider computer 25 at step S170A. The resource provider computer 25 may provide at least the authorization decision and the transaction identifier to the access device 20. The access device 20 may match the transaction identifier received at step S175A to the transaction identifier received by the communication device 10 at step S137A in order to determine whether to complete the transaction with the communication device 10. In some embodiments, the user of the communication device 10 may then be provided with a receipt or other proof of completion of the transaction. A clearing and settlement process may occur at the end of the day or at any other suitable time after completion of the transaction.
In some embodiments, the transaction processing computer 60 is not needed and the token server 30 and the transport computer 50 may communicate directly with the authorizing entity computer 70.
At step S120B, the application provider computer 40 may send the token reference identifier and the transaction data to the token server 30, as well as request a verification value associated with the sensitive information (e.g., a CVN associated with a selected payment device). At step S125B, the token server 30 may transmit the token (including any accompanying data), the verification value, and the transaction data directly to the gateway computer 45, without passing through the application provider computer 40.
At step S130B, gateway computer 45 sends a notification to application provider computer 40 that the token and any accompanying data was received from the token server 30, and that the transaction will continue processing. The application provider computer 40 may generate a unique transaction identifier (e.g., a UUID) corresponding to the transaction. At step S137B, the application provider computer 40 may transmit the transaction identifier to the communication device 10 for display to the user. Steps 135B to 175B may continue as described above with respect to steps 135A to 175A of
At step S210, the user of the communication device 10 may open an application to use the communication device 10 to scan the code. The code may be interpreted (or decoded) by communication device 10 (e.g., through an application) to extract the underlying transaction data. The communication device 10 may display a list of sensitive information that may be used to complete the transactions (e.g., a list of primary account numbers (PANs), payment devices, passwords, PINs, etc.), and allow the user to select one or more pieces of sensitive information from the list. The communication device 10 may generate, request or retrieve a token reference identifier corresponding to the sensitive information. A mapping between the token reference identifier and a token representing the sensitive information may be stored by the token server 30, as described further herein.
At step S215, the communication device 10 may transmit the transaction data, including the token reference identifier, to an application provider computer 40. At step S220, the application provider computer 40 sends the token reference identifier and transaction data (including the transaction identifier) to the gateway computer 45. The application provider computer 40 may know the proper gateway computer 45 to which to route the token reference identifier from one or more elements of the transaction data.
At step S225, the gateway computer 45 may send the token reference identifier to the token server 30 to request the token corresponding to the token reference identifier, as well as to request a verification value associated with the sensitive information (e.g., a card verification number (CVN) associated with a selected payment device). At step S230, the token server 30 may return the token (including any accompanying data) and the verification value to the gateway computer 45. In the embodiment of
Before, after, or in parallel with steps S215-S230, at step S235, the access device 20 may generate an authorization request message for the transaction using the transaction data (including the transaction identifier) and a “dummy token”, and forward the authorization request message to the resource provider computer 25. The “dummy token” may be formatted like a token and/or as a normal PAN, but does not contain sensitive information. In other words, the “dummy token” may be used in the authorization request message as a placeholder in order for the authorization to be processed as described herein, without using a real token. At step S240, the resource provider computer 25 may forward the authorization request message to the transport computer 50.
The transport computer 50 may transmit the authorization request message (or transaction data from the authorization request message) to the gateway computer 45 at step S245. The gateway computer 45 may match the transaction data received from the transport computer 50 to the transaction data received at step S220, as well as to the token and verification value received at step S230 (e.g., using the transaction identifier). At step S250, the gateway computer 45 may send the token and verification value (and any accompanying token data) to the transport computer 50.
The transport computer 50 may modify the authorization request message to include the token and verification value instead of the “dummy token”. Steps S255 to S280 may proceed as described with respect to steps S140A to S175A of
The embodiments shown and described with respect to
The transaction data may further include a transaction type, such as a flag or indicator indicating how the transaction will be processed (e.g., whether to use a card verification number (CVN), a TAVV, an original credit transaction (OCT), etc.). The transaction data may be analyzed to determine that the transaction type indicator is one of a plurality of transaction type indicators associated with a plurality of different transaction types. Transaction processing may be initiated according to the transaction type indicator. In this embodiment, the transaction type indicator indicates that a CVN transaction will be used in the transaction.
In the embodiment of
At step S330, the application on the communication device 10 may communicate with a token server 30 to request a token and a CVN associated with sensitive information selected by the user to perform the transaction. At step S335, the token server 30 may provision the token and CVN to the communication device 10. At step S340, the application on the communication device 10 may encrypt the transaction data, as well as the token and CVN, and provide it to an application provider computer 40. The application provider computer 40 may be the provider of the application on the communication device, such as a digital wallet provider.
At step S350, the application provider computer 40 may decrypt the encrypted transaction data and the token and CVN, and may then validate the transaction data (e.g., checking to see that the location of the merchant is one that would be expected). After validation, it may re-encrypt the transaction data, the token, and the CVN and route the encrypted data for the transaction (including the token and the CVN) to the access device 20, which may decrypt the data upon receipt. In some embodiments, the communication device 10 and the application provider computer 40 may share one pair of encryption keys (e.g., symmetric encryption keys), while the application provider computer 40 and the access device 20 may share another pair of encryption keys (e.g., a different pair of symmetric encryption keys).
Authorization processes may be conducted, after the transaction data including the token and the CVN are received by the access device 20. For example, at step S360, the access device 20 may construct an authorization request message with the token, CVN, transaction amount, and any other suitable authorization data and submit it to a resource provider computer 25. At step S365, the resource provider computer 25 may transmit the authorization request message to a transport computer 50 (e.g., an acquirer). At step S370, the transport computer 50 may forward the authorization request message to a transaction processing computer 60. At step S372, the transaction processing computer 60 may request the sensitive information (e.g., PAN) associated with the token (i.e., detokenization) from the token server 30, and receive the sensitive information at step S374. At step S376, the transaction processing computer 60 may replace the token with the sensitive information in the authorization request message, and forward the authorization request message to an authorizing entity computer 70 (e.g., an issuer) for authorization.
At step S380, the authorizing entity computer 70 may send an authorization response message (i.e., denying or allowing the transaction based on available funds, proper CVN, etc.) to the transaction processing computer 60, which may forward the authorization response message to the transport computer 50 at step S382. The transport computer 50 may forward the authorization response message to the resource provider computer 25 at step S383. The resource provider computer 25 may forward the authorization response message (or some indication of authorization) to the access device at step S384. In one embodiment, the user of the communication device 10 may then be provided with a receipt or other proof of completion of the transaction. A clearing and settlement process may occur at the end of the day or at any other suitable time after completion of the transaction.
At step S450, the application provider computer 40 may decrypt the encrypted transaction data, the token, and the CVN, and validate the decrypted data. The application provider computer 40 may route the token and CVN to the token server 30 for detokenization. At step S455, the token server 30 may locate the sensitive information associated with the token, and provide the sensitive information to the application provider computer 40. At step S460, the application provider computer 40 may encrypt the transaction data, and may route the encrypted transaction data and sensitive information for the transaction (including the PAN) to a transport computer 50. The transport computer 50 may decrypt the transaction data and the sensitive information. The transport computer 50 may generate an authorization request message with this information and may transmit it to the authorizing entity computer 70 via the transaction processing computer 60 in steps S470 and S475. The authorizing entity computer 70 may then generate an authorization response message. In steps S480 and S482, the authorization response message may be transmitted to the transport computer 50 via the transaction processing computer 60.
The transport computer 50 may forward the authorization response message to the application provider computer 40 at step S484. At step S490, the application provider computer 40 may provide the authorization response message to the resource provider computer 25. At step S492, the resource provider computer 25 may provide the authorization response message (or some indication of authorization) to the access device 20. In one embodiment, the user of the communication device 10 may then be provided with a receipt or other proof of completion of the transaction. A clearing and settlement process may occur at the end of the day or at any other suitable time after completion of the transaction.
The application provider computer 40 may either (A) route encrypted authorization data for the transaction (including transaction data and the sensitive information) to a transport computer 50 at step 565B, which may then decrypt the transaction data and the sensitive information, then generate an authorization request message including the transaction data and the sensitive information. The authorization request message may then be routed to the transaction processing computer 60 at step S570 (indicated by the dotted line path). Or, the application provider computer 40 may (B) route encrypted transaction data for the transaction and the sensitive information directly to the transaction processing computer 60 at step S665A (indicated by the dashed line path), which may then decrypt the encrypted transaction data and the sensitive information, and generate an authorization request message. In either embodiment, the transaction processing computer 60 may forward the authorization request message to an authorizing entity computer 70 for authorization at step S575. Steps S580 to S592 may proceed as described above with respect to steps S480 to S492 of
At step S640, the application on the communication device may encrypt the transaction data, as well as the token, and provide it to a joint application provider computer/authorizing entity computer 80. The application provider computer/authorizing entity computer 80 may be both the provider of the application on the communication device and the issuer of the payment device associated with the token. Although described herein as being a joint entity, it is contemplated that in other embodiments, the application provider computer and the authorizing entity computer may be separate. Further, it is contemplated that any of the embodiments described herein may be implemented with either a joint or separate application provider computer and authorizing entity computer.
At step S650, the application provider computer/authorizing entity computer 80 may decrypt the transaction data and the token, and may validate the transaction data. It may then route the token to the token server 30 for detokenization. At step S655, the token server 30 may locate the sensitive information associated with the token, and provide the sensitive information to the application provider computer/authorizing entity computer 80. At step S660, the application provider computer/authorizing entity computer 80 may route the OCT transaction data to the transaction processing computer 60. At step S665, the transaction processing computer 60 may forward the OCT transaction data to the transport computer 50. The transport computer 50 may formulate an OCT response that is sent to the transaction processing computer 60 at step S670, and to the application provider computer/authorizing entity computer 80 at step S675. At step S680, the transport computer 50 may further provide the OCT response to the resource provider computer 25. At step S685, the resource provider computer 25 may provide the OCT response to the access device 20, and the OCT transaction may be complete. In one embodiment, the user of the communication device 10 may then be provided with a receipt or other proof of completion of the transaction. A clearing and settlement process may occur at the end of the day or at any other suitable time after completion of the transaction.
At step S740, the application on the communication device 10 may communicate with a token server 30 to request a token associated with sensitive information of the user selected by the user to perform the transaction. The communication device 10 may further provide the token server 30 with at least some of the transaction data in order for the token server 30 to be able to uniquely identify the underlying transaction. For example, the communication device 10 may provide the token server 30 with a transaction identifier.
At step S750, the resource provider computer 25 may send a request for the token associated with the communication device 10 in order to complete the transaction. This may be done substantially contemporaneously with steps S730 and/or S740. The request may include identifying transaction data, such as the transaction identifier previously provided by the communication device 10, for example. At step S755, the token server 30 may retrieve the token associated with the identifying transaction data, and provide it to the resource provider computer 25. Although shown as being in direct communication with the token server 30, it is contemplated that an application provider computer 40 may act as a middleman between the resource provider computer 25 and the token server 30 in one embodiment.
Authorization processes may then conducted. For example, at step S760, the resource provider computer 25 may construct an authorization request message with the token and the transaction data and submit it to a transport computer 50. The transport computer 50 may forward the authorization request message to a transaction processing computer 60 at step S762. At step S764, the transaction processing computer 60 may request the sensitive information associated with the token from the token server 30, and receive it at step S764. At step S768, the transaction processing computer 60 may replace the token with the PAN in the authorization request message, and forward it to an authorizing entity computer 70 for authorization.
At step S770, the authorizing entity computer 70 may send an authorization response message (i.e., denying or allowing the transaction based on available funds, etc.) to the transaction processing computer 60, which may forward the authorization response message to the transport computer 50 at step S772. The transport computer 50 may forward the authorization response message to the resource provider computer 25 at step S773. At step S774, the resource provider computer 25 may forward the authorization response message to the access device 20 at step S774. In one embodiment, the user of the communication device 10 may then be provided with a receipt or other proof of completion of the transaction. A clearing and settlement process may occur at the end of the day or at any other suitable time after completion of the transaction.
For simplicity of illustration, a certain number of components are shown in
Processor 805 can be implemented as one or more integrated circuits (e.g., one or more single core or multicore microprocessors and/or microcontrollers), and is used to control the operation of communication device 800. Processor 805 can execute a variety of programs in response to program code or computer-readable code stored in memory 802, and can maintain multiple concurrently executing programs or processes. Communications subsystem 809 may include one or more RF transceivers and/or connectors that can be used by portable communication device 800 to communicate with other devices and/or to connect with external networks. User interface 806 can include any combination of input and output elements to allow a user to interact with and invoke the functionalities of communication device 800. In some embodiments, user interface 806 may include a component such as display 807 that can be used for both input and output functions.
Memory 802 can be implemented using any combination of any number of non-volatile memories (e.g., flash memory) and volatile memories (e.g., DRAM, SRAM), or any other non-transitory storage medium, or a combination thereof media. Memory 802 may store an operating system (OS) 814 and an application environment 810 where one or more applications reside including application 812 to be executed by processor 805.
Application 812 can be an application that uses, accesses, and/or stores sensitive information or tokens when executed by the processor 805. For example, application 812 can be a wallet or payment application that uses a token to conduct transactions via communication device 800. In some embodiments, access to application 812 by a user can be protected by user authentication data such as a password, passcode, PIN, etc. For example, when a user attempts to launch or execute application 812, the user may be requested to enter valid user authentication data before the user can access application 812. Application 812 may include a download manager 818, a cryptography module 814, and a code determination module 816. In some embodiments, one or more of these components can be provided by another application or component that is not part of application 812.
Download manager 818 can be configured to provide functionalities to communicate with an application provider associated with application 812 to download information via the application provider. Download manager 818 may request or otherwise manage the acquisition and/or storage of sensitive information and/or tokens. For example, download manager 818 may request and obtain sensitive information or token via the application provider associated with application 812, and stored the sensitive information or token in sensitive information data store 816. In some embodiments, the sensitive information or token provided by the application provider can be received in an encrypted form. For example, the sensitive information or token can be encrypted with a session key generated by a token server. Download manager 818 may also receive, from the application provider, the session key in an encrypted form, and store the encrypted session key in a sensitive information data store.
Cryptography module 814 may provide cryptographic functionalities for application 812. For example, cryptography module 814 may implement and perform encryption/decryption operations for application 812 using encryption algorithms such as DES, AES, TDES/TDEA, or the like, and/or hash functions such as SHA, or the like. For example, when application 812 accesses data stores within memory 802 to retrieve and use sensitive information or tokens stored therein (e.g., to conduct a transaction), application 816 may invoke cryptography module 814 to decrypt the session key that is used to encrypt the stored sensitive information or token, and then decrypt the sensitive information or token using the decrypted session key. The decrypted sensitive information or token can then be used by application 812. Code determination module 816 may interpret or translate codes scanned by camera 808 into transaction data, as described further herein.
Processor 901 may include one or more microprocessors to execute program components for performing the token request functions 930 of application provider computer 900. Network interface 902 can be configured to connect to one or more communication networks to allow application provider computer 900 to communicate with other entities such as a communication device operated by a user, a token server computer, etc. Computer readable medium 906 may include any combination of one or more volatile and/or non-volatile memories, for example, RAM, DRAM, SRAM, ROM, flash, or any other suitable memory components. Computer readable medium 906 may store code executable by the processor 901 for implementing some or all of the token request functions 930 of application provider computer 900. For example, computer readable medium 906 may include code implementing a registration module 910 and a token request module 908. In some embodiments, application provider computer 900 may also include a hardware security module (HSM) 920 to implemented a cryptography engine 922.
Registration module 910 may, in conjunction with processor 901, register users with application provider computer 900. For example, a user can be registered with the application provider by providing registration module 910 with user identifying information to identify the user, device information such as a device identifier associated with the user's communication device on which an application associated with the application provider is installed, account information such as an account identifier associated with the user's account, etc. In some embodiments, a user may set up user authentication data (e.g., password, passcode, PIN, etc.) via registration module 910. The user authentication data can be used by application provider computer 900 to authenticate the user when the application on the user's communication device communicates with application provider computer 900. Registration module 910 may also allow a user to change or update the user authentication data. The registration information can be stored in a database 903. In some embodiments, the registration process can be carried out when the user first downloads the application for installation on the user's communication device, or when the user first launches and executes the application.
Token request module 908 is configured to, in conjunction with the processor 901, facilitate requests for sensitive information or tokens received from the application installed on a user's communication device. In some embodiments, upon receiving a request from the application on the user's communication device, token request module 908 may authenticate the user and/or the communication device by verifying the user authentication data and device identifier of the communication device against the previously registered information stored in database 903. Token request module 908 may then, in conjunction with processor 901, request the sensitive information or token from a token server for use on the communication device. When token request module 908 receives the sensitive information or token from the token server, token request module 908 may send the sensitive information or token to the application executing on the communication device. In some embodiments, token request module 908 may also, in conjunction with processor 901, track which sensitive information or token is provided to a particular communication device by storing this information in user database 903. Thus, user database 903 may include a mapping between a communication device and the sensitive information or token provisioned to that communication device.
Cryptography engine 922 may provide cryptographic functionalities for application provider computer 900. In some embodiments, cryptography engine 922 can be implemented in HSM 920, which is a specialized hardware component used to perform cryptographic operations and manage cryptographic keys. Cryptography engine 922 may, in conjunction with processor 901, implement and perform encryption/decryption operations for application provider computer 900 using encryption algorithms such as such as AES, DES, TDES/TDEA, or other suitable encryption algorithms using cryptographic keys of any length (e.g., 56-bit, 128-bit, 169-bit, 192-bit, 256-bit, etc.). In some embodiments, cryptography engine 922 can also, in conjunction with processor 901, perform hash calculations using hash functions such as secure hash algorithm (SHA), or the like. For example, when application provider computer 900 receives a session key used for encrypting sensitive information or token from a token server, application provider computer 900 may invoke cryptography engine 922 to encrypt the session key, such that session key can be provided to the application on the communication device in an encrypted form. In some embodiments, the session key can be encrypted using a hash value that is computed over the user authentication data associated with the user requesting the sensitive information or token.
Processor 1001 may include one or more microprocessors to execute program components for performing the token management functions 1030 of token server computer 1000. Network interface 1002 may be configured to connect to one or more communication networks to allow token server computer 1000 to communicate with other entities such as a communication device operated by a user, an application provider computer or a token request computer, merchant computer, acquirer computer, transaction processing network computer, issuer computer, etc. Computer readable medium 1006 may include any combination of one or more volatile and/or non-volatile memories, for example, RAM, DRAM, SRAM, ROM, flash, or any other suitable memory components. Computer readable medium 1006 may store code executable by the processor 1001 for implementing some or all of the token management functions 1030 of token server computer 1000 described herein. For example, computer readable medium 1006 may include a requestor registration module 1008, a user registration module 1010, a token generator 1012, a verification and authentication module 1014, a token exchange and routing module 1016, and a token life-cycle management module 1018.
Requestor registration module 1008 may, in conjunction with processor 1001, register a token requestor entity (e.g., application provider) with the token registry 1004, and to generate a token requestor identifier (ID) for the registered entity. Each registered entity can use their respective token requestor ID as part of a token service request to facilitate identification and validation of the entity. In some embodiments, a token requestor entity may provide token requestor information to the requestor registration module 808 such as an entity name, contact information, an entity type (e.g., merchant, wallet provider, payment service provider, issuer, payment enabler, acquirer, etc.). In some embodiments in which the token is transaction related, the token requestor information may also include token presentment modes (e.g., scan, contactless, e-commerce, etc.), token type (e.g., static/dynamic, payment/non-payment), integration and connectivity parameters, and services subscribed (e.g., token request, authentication and verification, life-cycle management, etc.) and any other relevant information for the onboarding process.
User registration module 1010 may, in conjunction with processor 1001, perform registration of users and accounts of the users. In some embodiments, token server computer 1000 may allow authorized entities to register consumer accounts (e.g., payment or financial accounts) with the network token system on behalf of the users. For example, a registered token requestor may provide a token requestor ID (e.g., received at the time of registration from the requestor registration module 1008), an account identifier or other sensitive information or sensitive information identifier for which a token can substitute, a consumer name and contact information, device identifier of the consumer's communication device, a token type, and any other relevant information for individual account registration or bulk account registration. In some embodiments, user registration module 1010 may, in conjunction with processor 1001, store the account details and sensitive information in token registry 1004 for all successful activation and registration requests. In some embodiment, an authorized entity may also unregister users and accounts by providing the necessary information to token server computer 1000.
Token generation module 1012 can be configured to, in conjunction with processor 1001, generate a token or retrieve sensitive information in response to processing a request for a token or sensitive information from a token requestor (e.g., an application provider), in conjunction with processor 1001. Further, token generation module 1012 can be configured with the processor 1001 to generate verification values, such as CVNs and TAVVs. In some embodiments, token generation module 1012 may receive a token requestor ID and an account identifier or sensitive information identifier. In some embodiments, token generation module 1012 may also receive optional information such as a user name, a user address and zip code, a requested token or sensitive information type (e.g., static, dynamic, non-payment, etc.), device identifier, and/or suitable information. In some embodiments, token generation module 1012 may generate a response with the requested token or requested sensitive information, a token expiration date associated with the token, and/or a token assurance level associated with the token. In some embodiments, token generation module 1012 may, in conjunction with the processor 1001, validate the token requestor ID and maintain the correlation between the token, the sensitive information or account identifier being substituted by the token, and the associated token requestor. In some embodiments, token generation module 1012 may, in conjunction with the processor 1001, determine if a token already exists in token registry 1004 for a token request before generating a new token. In some embodiments, if a token cannot be provisioned, the token response may include a corresponding reason code. In some embodiments, token generation module 1012 may also, in conjunction with the processor 1001, provide an interface to the token requestors to submit a bulk token request file.
In some embodiments, the token may be generated on the fly using API calls. For example, when a request is received to tokenize an account identifier or other sensitive information, token generation module 1012 may determine a token range to assign the token. The token range may be assigned based on whether the issuer is provisioning the token (e.g., issuer assigned token range) or the transaction processing network is provisioning the token on behalf of the issuer (e.g., transaction processing network assigned token range). As an example, if the transaction processing network assigned token range includes “442400000-442400250,” then “4424000000005382” may be assigned as a token value. Token registry 1004 may store the relationship of the token range to the account identifier, and a token add record may be logged. In some embodiments, token generation module 1012 may consider the token range list associated with the account identifier range before assigning a token.
Verification and authentication module 1014 may be configured with the processor 1001 to execute a consumer verification and authentication process, and determine a token assurance level based on the outcome of the verification and authentication process. For example, the verification and authentication module 1014 can, in conjunction with the processor 1001, perform consumer authentication and verification through a configured authentication scheme. In some embodiments, the authentication scheme may include verification of the account identifier, verification values, and the expiration date based on the customer information stored in a database associated with the transaction processing network. In some embodiments, the authentication scheme may include direct verification of the consumer by the issuer using consumer credentials for their online banking system.
In some embodiments, the authentication scheme may include verification of the consumer credentials through the issuer ACS (Access Control Server). For example, the issuer ACS service may be part of an authentication protocol such as 3-D secure protocol by Visa®. The ACS server may be associated with an issuer that may include registered consumer account and access information. The ACS can give issuers the ability to authenticate a consumer during an online purchase, thereby reducing the likelihood of fraudulent use of the consumer account. For example, the ACS can validate that the consumer is registered, performs consumer verification at the time of the transaction, and provides digitally signed responses to the merchants. In some embodiments, the authentication scheme may include verification of the account using a transaction processing network consumer authentication service (e.g., Visa™ Consumer Authentication Service (VCAS)). For example, the VCAS service can authenticate the consumer on-behalf of the issuer prior to the authorization process.
In some embodiments, user registration, token generation, and verification and authentication may be performed as part of processing a single token request process. In some embodiments, for bulk requests, user registration and token generation may be performed by processing a bulk file from the token requestor. In such embodiments, consumer verification and authentication may be performed in a separate step. In some embodiments, the token requestor can request that the authentication and verification process be performed independently multiple times for a particular account to reflect any changes to the levels of assurance for the token over time.
Token exchange and routing module 1016 may, in conjunction with the processor 1001, process requests for the underlying sensitive information (e.g., an account identifier) associated with a given token. For example, a transaction processing computer, acquirer, issuer, etc. may issue a request for a token exchange during processing of a transaction. Token exchange and routing module 1016 may, in conjunction with the processor 1001, validate that the requesting entity is entitled to make a request for a token exchange. In some embodiments, token exchange and routing module 1016 may, in conjunction with the processor 1001, validate the account identifier (or other sensitive information) to token mapping and presentment mode based on the transaction timestamp and the token expiration timestamp. Token exchange and routing module 1016 may, in conjunction with the processor 1001, retrieve the account identifier (or other sensitive information) from token registry 1004, and provide it along with the assurance level to the requesting entity. In some embodiments, if the account identifier (or other sensitive information) to token mapping is not valid for the transaction timestamp and presentment mode, an error message may be provided.
Token life-cycle management module 1018 may, in conjunction with the processor 1001, perform life-cycle operations on the tokens managed by token server computer 1000. Life-cycle operations may include canceling a token, activating or deactivating a token, updating token attributes, renewing token with a new expiration date, etc. In some embodiments, a token requestor entity may provide a token requestor ID, a token number, a life-cycle operation identifier and one or more token attributes to token server computer 1000 to perform the requested life-cycle operation on a given token. Token life-cycle management module 1018 may, in conjunction with the processor 1001, verify the token requestor ID and the token association based on information in token registry 1004. Token life-cycle management module 1018 may, in conjunction with the processor 1001, perform the requested life-cycle operation on a given token, and update the corresponding associations in token registry 1004. Examples of life-cycle operation may include a token activation operation to activate an inactive, suspended, or temporarily locked token and its associations; a token de-activation operation to temporarily lock or suspend a token; a cancel token operation to permanently mark a token and its associations as deleted to prevent any future transactions, etc. In some embodiments, a deleted token may be used during returns/chargebacks if the same token was used to submit the corresponding original transactions.
According to some embodiments, token server computer 1000 may include a HSM 1020 to perform secure functions such as encryption and decryption operations and generation of cryptographic keys used for the encryption and decryption operations. For example, HSM 1020 may include a cryptography engine 1022 to execute encryption algorithms such as AES, DES, TDES/TDEA, or other suitable encryption algorithms using cryptographic keys of any length (e.g., 56-bit, 128-bit, 169-bit, 192-bit, 256-bit, etc.). HSM 820 may also implement a session key generator 1024 to generate a session key for each token or sensitive information request that token server computer 1000 processes. The generated session key can be used to encrypt a token or sensitive information generated or retrieved for the request, and the token or sensitive information can be provided to the token requestor in an encrypted form. For example, for each request that token server computer 1000 receives and processes, session key generator 1024 may generate a session key that can be unique for each request received from the particular token requestor, or unique to each request associate with a particular user or account. In some embodiments, the session key can be the same or different than the encryption key that is used to establish the secure communication channel (e.g., TLS, SSL, etc.) between the token requestor and token server computer 1000. Token generator 1012 may generate or otherwise retrieve a token or sensitive information to fulfill the request. The session key can be used by cryptographic engine 1022 to encrypt that token or sensitive information using an encryption algorithm, and the encrypted token or sensitive information can be provided to the token requestor. In some embodiments, the generated session key is also provided to the token requestor with the encrypted token or sensitive information.
Although token server computer 1000 and application provider computer 900 have been described with a HSM implementing only some of their functions, it should be understood that other functionalities of the respective computers (e.g., token generation) can be implemented inside a HSM as well. Furthermore, some or all of the respective HSM functionalities can also be implemented outside of a HSM.
A computer system and/or server computer may be used to implement any of the entities or components described above. The subsystems of the computer system may be interconnected via a system bus. Additional subsystems such as a printer, keyboard, fixed disk (or other memory comprising computer readable media), monitor, which is coupled to display adapter, and others may be used. Peripherals and input/output (I/O) devices, which couple to an I/O controller (which can be a processor or other suitable controller), can be connected to the computer system by any number of means known in the art, such as a serial port. For example, a serial port or external interface can be used to connect the computer apparatus to a wide area network such as the Internet, a mouse input device, or a scanner. The interconnection via system bus allows the central processor to communicate with each subsystem and to control the execution of instructions from system memory or the fixed disk, as well as the exchange of information between subsystems. The system memory and/or the fixed disk may embody a computer readable medium. In some embodiments, the monitor may be a touch sensitive display screen.
A computer system can include a plurality of the same components or subsystems, e.g., connected together by an external interface or by an internal interface. In some embodiments, computer systems, subsystem, or apparatuses can communicate over a network. In such instances, one computer can be considered a client and another computer a server, where each can be part of a same computer system. A client and a server can each include multiple systems, subsystems, or components.
It should be understood that any of the embodiments of the present invention can be implemented in the form of control logic using hardware (e.g. an application specific integrated circuit or field programmable gate array) and/or using computer software with a generally programmable processor in a modular or integrated manner. As used herein, a processor includes a single-core processor, multi-core processor on a same integrated chip, or multiple processing units on a single circuit board or networked. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement embodiments of 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, C++, C#, Objective-C, Swift, or scripting language such as Perl or Python 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 for storage and/or transmission, suitable media include 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 compact disk (CD) or DVD (digital versatile disk), flash memory, and the like. The computer readable medium may be any combination of such storage or transmission devices.
Such programs may also be encoded and transmitted using carrier signals adapted for transmission via wired, optical, and/or wireless networks conforming to a variety of protocols, including the Internet. As such, a computer readable medium according to an embodiment of the present invention may be created using a data signal encoded with such programs. Computer readable media encoded with the program code may be packaged with a compatible device or provided separately from other devices (e.g., via Internet download). Any such computer readable medium may reside on or within a single computer product (e.g. a hard drive, a CD, or an entire computer system), and may be present on or within different computer products within a system or network. A computer system may include a monitor, printer, or other suitable display for providing any of the results mentioned herein to a user.
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.
Like reference numerals are used to indicate like elements throughout the figures.
This application is Continuation Application of U.S. application Ser. No. 15/421,891, filed Feb. 1, 2017, which claims the benefit of U.S. Provisional Patent Application No. 62/289,695, filed Feb. 1, 2016, entitled “TRANSACTION SYSTEMS AND METHODS FOR MERCHANT CODE DISPLAY AND USE”, and are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5613012 | Hoffman et al. | Mar 1997 | A |
| 5781438 | Lee et al. | Jul 1998 | A |
| 5883810 | Franklin et al. | Mar 1999 | A |
| 5953710 | Fleming | Sep 1999 | A |
| 5956699 | Wong et al. | Sep 1999 | A |
| 6000832 | Franklin et al. | Dec 1999 | A |
| 6014635 | Harris et al. | Jan 2000 | A |
| 6044360 | Picciallo | Mar 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 8589300 | Hammad 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 |
| 8762263 | Gauthier et al. | Jun 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 |
| 11080696 | Flurscheim et al. | Aug 2021 | 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 |
| 20020069165 | O'Neil | Jun 2002 | A1 |
| 20020073027 | Hui et al. | Jun 2002 | A1 |
| 20020073045 | Rubin et al. | Jun 2002 | A1 |
| 20020116329 | Serbetcioglu et al. | Aug 2002 | A1 |
| 20020116341 | Hogan et al. | Aug 2002 | A1 |
| 20020133467 | Hobson et al. | Sep 2002 | A1 |
| 20020147913 | Lun Yip | Oct 2002 | A1 |
| 20030028481 | Flitcroft et al. | Feb 2003 | A1 |
| 20030089767 | Kiyomatsu | May 2003 | A1 |
| 20030130955 | Hawthorne | Jul 2003 | A1 |
| 20030135470 | Beard | Jul 2003 | A1 |
| 20030182207 | Skinner | Sep 2003 | A1 |
| 20030191709 | Elston et al. | Oct 2003 | A1 |
| 20030191945 | Keech | Oct 2003 | A1 |
| 20040010462 | Moon et al. | Jan 2004 | A1 |
| 20040050928 | Bishop et al. | Mar 2004 | A1 |
| 20040059682 | Hasumi et al. | Mar 2004 | A1 |
| 20040068465 | Nagamine et al. | Apr 2004 | A1 |
| 20040093281 | Silverstein et al. | May 2004 | A1 |
| 20040139008 | Mascavage, III | 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 |
| 20040260646 | Berardi et al. | Dec 2004 | A1 |
| 20050037735 | Coutts | Feb 2005 | A1 |
| 20050080730 | Sorrentino | Apr 2005 | A1 |
| 20050108178 | York | May 2005 | A1 |
| 20050199709 | Linlor | Sep 2005 | A1 |
| 20050211771 | Onozu | Sep 2005 | A1 |
| 20050246293 | Ong | Nov 2005 | A1 |
| 20050256802 | Ammermann et al. | Nov 2005 | A1 |
| 20050269401 | Spitzer et al. | Dec 2005 | A1 |
| 20050269402 | Spitzer et al. | Dec 2005 | A1 |
| 20060163345 | Myers et al. | Jul 2006 | A1 |
| 20060190351 | Dennis | Aug 2006 | A1 |
| 20060235795 | Johnson et al. | Oct 2006 | A1 |
| 20060237528 | Bishop et al. | Oct 2006 | A1 |
| 20060278704 | Saunders et al. | Dec 2006 | A1 |
| 20070011099 | Sheehan | Jan 2007 | A1 |
| 20070022058 | Labrou et al. | Jan 2007 | A1 |
| 20070107044 | Yuen et al. | May 2007 | A1 |
| 20070108269 | Benco et al. | May 2007 | A1 |
| 20070124211 | Smith | 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 |
| 20070266130 | Mazur et al. | Nov 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 |
| 20080099552 | Grillion | May 2008 | A1 |
| 20080114699 | Yuan et al. | May 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 |
| 20080301042 | Patzer | Dec 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 |
| 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 |
| 20100088237 | Wankmueller | Apr 2010 | A1 |
| 20100094755 | Kloster | 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 |
| 20120018506 | Hammad et al. | 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 |
| 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 |
| 20130048714 | Sharma et al. | Feb 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, 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 |
| 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 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 | 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 |
| 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 |
| 20140040628 | Fort et al. | Feb 2014 | A1 |
| 20140041018 | Bomar et al. | 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 |
| 20140149293 | Laracey | May 2014 | A1 |
| 20140164243 | Aabye et al. | Jun 2014 | A1 |
| 20140188586 | Carpenter et al. | Jul 2014 | A1 |
| 20140294701 | Dai et al. | 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 |
| 20150088674 | Flurscheim 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 |
| 20150312038 | Palanisamy | Oct 2015 | A1 |
| 20150319158 | Kumnick | Nov 2015 | A1 |
| 20150332262 | Lingappa | Nov 2015 | A1 |
| 20150356560 | Shastry et al. | Dec 2015 | A1 |
| 20160012399 | Etchegoyen | Jan 2016 | 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 |
| 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 |
| 20160210628 | McGuire | Jul 2016 | A1 |
| 20160218875 | Le Saint et al. | Jul 2016 | A1 |
| 20160224977 | Sabba et al. | Aug 2016 | A1 |
| 20160232527 | Patterson | Aug 2016 | A1 |
| 20160239842 | Cash et al. | Aug 2016 | A1 |
| 20170163617 | Laxminarayanan | Jun 2017 | A1 |
| 20170221054 | Flurscheim et al. | Aug 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 102546648 | Jul 2012 | CN |
| 2156397 | Feb 2010 | EP |
| 0135304 | May 2001 | WO |
| 0157770 | Aug 2001 | WO |
| 0135304 | May 2002 | WO |
| 2004042536 | May 2004 | WO |
| 2006000002 | Jan 2006 | WO |
| 2006000021 | Jan 2006 | WO |
| 2006002251 | Jan 2006 | WO |
| 2006063628 | Jun 2006 | WO |
| 2006113834 | Oct 2006 | WO |
| 2008045007 | Apr 2008 | WO |
| 2009032523 | Mar 2009 | WO |
| 2009055719 | Apr 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 |
| 2015013548 | Jan 2015 | WO |
| 2015105688 | Jul 2015 | WO |
| 2017136418 | Aug 2017 | WO |
| Entry |
|---|
| CN201780008623.5 , “Office Action”, dated Jan. 21, 2022, 3 pages. |
| ““Smile, please”one click, payment completed”, Fun communications GmbH Press Release, Mar. 2004, 2 pages. |
| “Cingular, Citybank and Nokia Testing Credit Card Mobile Phone, Softpedia”, Softpedia, 1 page. |
| “Citigroup, Mastercard, Cingular and Nokia team to pilot next generation mobile phone with “tap & go™” payment in New York City”, Nokia Press Release, Dec. 14, 2006, 2 pages. |
| “Fun Communications Develops “Photopay””, Mobile Payments World, 2002-2014, 1 page. |
| “Mobipay Case Study, The Payment system via the Mobile”, 5 pages. |
| “Mobipay makes Spain world leader in the development of the payments via mobile phones”, Telefonica Press Release, 6 pages. |
| “TeleTalk Best of CeBIT Award 2004 for fun communications”, Fun communications GmbH Press Release, Mar. 2004, 2 pages. |
| “Thirsty? Then Dial a Drink, internetnews.com”, Apr. 5, 2001, 1 page. |
| “What People are Saying about Ordering through Salt”, Available online at: www.saltmobile.com,, 4 pages. |
| U.S. Appl. No. 15/421,891, Advisory Action, dated Feb. 20, 2020, 5 pages. |
| U.S. Appl. No. 15/421,891, Final Office Action, dated Aug. 11, 2020, 10 pages. |
| U.S. Appl. No. 15/421,891, Final Office Action, dated Oct. 31, 2019, 37 pages. |
| U.S. Appl. No. 15/421,891, Non-Final Office Action, dated Apr. 24, 2019, 31 pages. |
| U.S. Appl. No. 15/421,891, Non-Final Office Action, dated Apr. 2, 2020, 9 pages. |
| U.S. Appl. No. 15/421,891, Notice of Allowance, dated Mar. 18, 2021, 11 pages. |
| U.S. Appl. No. 61/738,832, Management of Sensitive Data, filed Dec. 18, 2012, 22 pages. |
| U.S. Appl. No. 61/751,763, Payments Bridge, filed Jan. 11, 2013, 64 pages. |
| U.S. Appl. No. 61/892,407, Issuer Over-The-Air Update Method and System, filed Oct. 17, 2013, 28 pages. |
| U.S. Appl. No. 61/894,749, 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, 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, Payment System Canonical Address Format, filed May 19, 2014, 58 pages. |
| U.S. Appl. No. 62/003,717, Mobile Merchant Application, filed May 28, 2014, 58 pages. |
| U.S. Appl. No. 62/024,426, Secure Transactions Using Mobile Devices, filed Jul. 14, 2014, 102 pages. |
| U.S. Appl. No. 62/037,033, Sharing Payment Token, filed Aug. 13, 2014, 36 pages. |
| U.S. Appl. No. 62/038,174, Customized Payment Gateway, filed Aug. 15, 2014, 42 pages. |
| U.S. Appl. No. 62/042,050, Payment Device Authentication and Authorization System, filed Aug. 26, 2014, 120 pages. |
| U.S. Appl. No. 62/053,736, Completing Transactions Without a User Payment Device, filed Sep. 22, 2014, 31 pages. |
| U.S. Appl. No. 62/054,346, Mirrored Token Vault, filed Sep. 23, 2014, 38 pages. |
| U.S. Appl. No. 62/103,522, Methods and Systems for Wallet Provider Provisioning, filed Jan. 14, 2015, 39 pages. |
| U.S. Appl. No. 62/108,403, Wearables With NFC HCE, filed Jan. 27, 2015, 32 pages. |
| U.S. Appl. No. 62/117,291, Token and Cryptogram Using Transaction Specific Information, filed Feb. 17, 2015, 25 pages. |
| U.S. Appl. No. 62/128,709, filed Tokenizing Transaction Amounts, filed Mar. 5, 2015, 30 pages. |
| AU2008316613 , “Statement of Grounds and Particulars by Eftpos Payments Australia Limited”, Aug. 13, 2014, 21 pages. |
| CN201780008623.5, Office Action, dated Jan. 25, 2021, 20 pages. |
| CONABREE , “Telstra Mobile m-Commerce”, Aug. 13, 2002, 1 page. |
| EP17748060.5, Extended European Search Report, dated Oct. 26, 2018, 8 pages. |
| EP17748060.5 , Office Action, dated Apr. 6, 2021, 7 pages. |
| Gao et al., “Emerging Technologies for Mobile Commerce”, Journal of Theoretical and Applied Electronic Commerce Research, vol. 1, Issue 2, Aug. 2006, 5 pages. |
| Hughes et al., “M-PESA: Mobile Money for the “unbanked” Turning Cellphones into 24-Hour Tellers in Kenya”, innovations, winters spring, 2007, 19 pages. |
| Karnouskos et al., “SeMoPS: A Global Secure Mobile Payment Service”, Available online at: http://www.idea-group.com, innovations/winter and spring 2007,, 2007, pp. 237-261. |
| Luo et al., “Enabling Technology and Functionalities of Shopping Portals”, Idea Group Inc., 2007, 2 pages. |
| PCT/US2017/016009, International Preliminary Report on Patentability, dated Aug. 16, 2018, 11 pages. |
| PCT/US2017/016009, International Search Report and Written Opinion, dated Apr. 25, 2017, 12 pages. |
| SEMOPS , “SEMOPS Internet Payments”, 2 pages. |
| SEMOPS , “Semops Mobile Commerce”, 2 pages. |
| SEMOPS , “SEMOPS Point of Sale Transactions”, 2 pages. |
| Uden, “The Next Generation Electronic Payment Service, Internet + Mobile”, SEMOPS, Secure Mobile Payment Service, Deloitte, info@semops.com,, 18 pages. |
| Application No. CN201780008623.5 , Office Action, dated Sep. 29, 2021, 18 pages. |
| IN201847031951, First Examination Report, dated Jul. 29, 2021, 6 pages. |
| Application No. CN201780008623.5 , Notice of Decision to Grant, dated Apr. 24, 2022, 6 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210312433 A1 | Oct 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62289695 | Feb 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15421891 | Feb 2017 | US |
| Child | 17349708 | US |
