The present invention provides a method for conducting a transaction that includes receiving a pseudo account identifier that corresponds to a primary account identifier. The pseudo account identifier may be received at a portable wireless device and may be generated by a remote server computer. The portable wireless device can receive the pseudo account identifier over a first network and provide the pseudo account identifier to an access device. The access devices generally comprises a reader that can receive the pseudo account identifier, and thereafter send a message to request authorization of a transaction. The authorization request message may include the pseudo account identifier and is sent to a payment processing network. The authorization request message is sent to the payment processing network over a second network. The payment processing network may then process the authorization message and return a response that indicates if the transaction is authorized or not.
|
18. A method comprising:
receiving, by an access device using a contactless reader, a pseudo account identifier from a portable wireless phone comprising a contactless transmitter to conduct a transaction, wherein the pseudo account identifier corresponds to a consumer's account identifier and was retrieved by the portable wireless phone over a communications network via a wireless access point, wherein the pseudo account identifier was previously generated and stored by a server computer upon the server computer receiving a request that was automatically generated by the portable wireless phone in response to a selection of an account associated with the consumer's account identifier, and wherein generation of the pseudo account identifier by the server computer and retrieval of the pseudo account identifier by the portable wireless phone is transparent to a consumer such that the consumer does not know the pseudo account identifier is received;
sending, by the access device, a transaction authorization request comprising the pseudo account identifier to a payment processing network, wherein the pseudo account identifier is thereafter converted to the consumer's account identifier by the server computer, and wherein the transaction authorization request is processed to approve or deny the transaction; and
receiving, by the access device, an authorization response message via the payment processing network, wherein the authorization response message indicates if the transaction is approved or not approved.
1. A method comprising:
receiving, by a portable wireless phone, a selection of an account from a consumer;
retrieving, automatically by the portable wireless phone, a pseudo account identifier associated with the selected account in response to receiving the selection of the account by:
sending, by the portable wireless phone, a request for the pseudo account identifier associated with the selected account over a first network, the request including an account identifier for the selected account; and
receiving, by the portable wireless phone, over the first network, the pseudo account identifier that corresponds to the account identifier associated with the selected account, the pseudo account identifier being generated by a server computer, wherein generation of the pseudo account identifier by the server computer and retrieval of the pseudo account identifier by the portable wireless phone is transparent to the consumer such that the consumer does not know the pseudo account identifier is received; and
transmitting, by the portable wireless phone using a contactless transmitter, the pseudo account identifier to an access device comprising a contactless reader to conduct a transaction, wherein the access device thereafter sends an authorization request message comprising the pseudo account identifier to a payment processing network over a second network that is different than the first network, wherein the payment processing network converts the pseudo account identifier in the authorization request message back to the account identifier, wherein the payment processing network sends the authorization request message including the account identifier to an issuer associated with the account identifier, wherein the issuer generates an authorization response message and sends the authorization response message to the payment processing network, and wherein the access device thereafter receives the authorization response message indicating whether the transaction is approved or not approved.
10. A portable wireless phone for performing a proximity transaction comprising:
a long range communication element;
a short range communication element;
a processor coupled to the long range communication element and the short range communication element;
a memory coupled to the processor, the memory comprising computer code for performing a method, the method comprising:
receiving a selection of an account from a user;
in response to receiving the selection of the account, automatically retrieving a pseudo account identifier associated with the selected account by:
sending a request for a pseudo account identifier associated with the selected account using the long range communication element, the request including an account identifier for the selected account; and
receiving the pseudo account identifier that corresponds to the account identifier associated with the selected account at the portable wireless phone over a first network using the long range communication element, the pseudo account identifier being generated a server computer, wherein generation of the pseudo account identifier by the server computer and retrieval of the pseudo account identifier by the portable wireless phone is transparent to the user such that the users does not know the pseudo account identifier is received; and
transmitting the pseudo account identifier to an access device comprising a reader using the short range communication element, wherein the access device thereafter sends an authorization request message comprising the pseudo account identifier to a payment processing network over a second network, wherein the payment processing network converts the pseudo account identifier in the authorization request message back to the account identifier, wherein the payment processing network sends the authorization request message including the account identifier to an issuer associated with the selected account, wherein the issuer generates an authorization response message and sends the authorization response message to the payment processing network, and wherein the access device thereafter receives the authorization response message indicating whether the proximity transaction is approved or not approved.
17. A server computer comprising:
a processor;
a computer readable medium coupled to the processor, the computer readable medium comprising computer code for performing a method, the method comprising:
receiving a request for retrieving a pseudo account identifier corresponding to a consumer's account identifier, wherein the request is received over a first network, and wherein the request for the pseudo account identifier is automatically generated by a portable wireless phone in response to a selection by a consumer of an account associated with the consumer's account identifier;
generating the pseudo account identifier corresponding to the first consumer's account identifier;
storing the generated pseudo account identifier as being associated with the consumer's account identifier;
sending the generated pseudo account identifier to the portable wireless phone over the first network, wherein the portable wireless phone is thereafter capable of performing one or more transactions by transmitting the pseudo account identifier to an access device using a contactless transmitter of the portable wireless phone and a contactless receiver of the access device, and wherein generation of the pseudo account identifier by the server computer and retrieval of the pseudo account identifier by the portable wireless phone is transparent to the consumer such that the consumer does not know the pseudo account identifier is received;
receiving an authorization request message comprising the pseudo account identifier over a second network that is different than the first network for a transaction;
determining the consumer's account identifier associated with the pseudo account identifier;
converting the pseudo account identifier in the authorization request message to the consumer's account identifier;
sending the authorization request message to an issuer associated with the consumer's account identifier, wherein the issuer generates an authorization response message including an indication of whether the transaction is approved or not approved;
receiving the authorization response message; and
forwarding the authorization response message to the access device for completion of the transaction based on the indication of whether the transaction is approved or not approved.
13. A method comprising:
receiving, by a server computer, a request for retrieving a pseudo account identifier corresponding to a consumer's account identifier, wherein the request is received over a first network, wherein the request for the pseudo account identifier is automatically generated by a portable wireless phone in response to a selection by a consumer of an account associated with the consumer's account identifier;
generating, by the server computer, the pseudo account identifier corresponding to the consumer's account identifier;
storing, by the server computer, the generated pseudo account identifier as being associated with the consumer's account identifier;
sending, by the server computer, the generated pseudo account identifier to the portable wireless phone over the first network, wherein the portable wireless phone is thereafter capable of performing one or more transactions by transmitting the pseudo account identifier to an access device using a contactless transmitter of the portable wireless phone and a contactless receiver of the access device, and wherein generation of the pseudo account identifier by the server computer and retrieval of the pseudo account identifier by the portable wireless phone is transparent to the consumer such that the consumer does not know the pseudo account identifier is received;
receiving, by the server computer, an authorization request message for a transaction, the authorization request message comprising the pseudo account identifier over a second network that is different than the first network;
determining, by the server computer, the consumer's account identifier associated with the pseudo account identifier by retrieving the consumer's account identifier associated with the stored pseudo account identifier;
converting, by the server computer, the pseudo account identifier in the authorization request message to the consumer's account identifier;
sending, by the server computer, the authorization request message to an issuer associated with the consumer's account identifier, wherein the issuer generates an authorization response message including an indication of whether the transaction is approved or not approved;
receiving, by the server computer, the authorization response message; and
forwarding, by the server computer, the authorization response message to the access device for completion of the transaction based on the indication of whether the transaction is approved or not approved.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
9. The method of
11. The portable wireless phone of
12. The portable wireless phone of
14. The method of
15. The method of
16. The method of
19. The method of
20. The method of
21. The method of
|
This application is a continuation application of U.S. patent application Ser. No. 12/145,352 filed Jun. 24, 2008 which claims priority to U.S. Provisional Patent Application No. 60/946,113 filed Jun. 25, 2007, of which are all herein incorporated by reference.
Visa International Service Association, Inc. and Visa U.S.A. are parties to a Joint Research Agreement.
Embodiments of the present invention relate to portable wireless devices that may be used to conduct contactless payment transactions. More specifically, embodiments of the present invention relate to conducting those transactions in a secure manner.
In today's society the presence of portable wireless devices carried by consumers has become almost ubiquitous. Cellular telephones, Personal Digital Assistants (PDAs), pagers, and the like are being carried by larger and larger numbers of people. These devices are being used to perform a wide variety of tasks, such as standard voice communications, e-mail access, internet web surfing, and a whole host of other activities. One of the activities that is currently contemplated is the use of a portable wireless device to act as a replacement for a payment card, such as a standard credit or debit card.
At least one major manufacturer of cellular phones has introduced a phone that is capable of being used as a payment card. In addition to the standard elements and capabilities of a cellular phone, the device also contains an additional element that is capable of storing a user's payment card information, such as their credit card account number, in the element on the phone. This element is further tied in with a short range wireless transmission element, such as a Radio Frequency Identification (RFID) tag, to allow the phone to transmit the account number over a short range to a contactless reader.
Contactless readers are becoming more and more commonplace in the market as a replacement for standard credit card readers. As opposed to a standard card reader, whose operation involves a merchant or the consumer physically sliding the payment card through the card reader in order for the payment card account information to be read, a contactless card reader is able to retrieve the payment card information from the device through the use of a short range radio transmission, such as those provided by RFID tags. The device need only be held in the vicinity of the contactless reader. A real world example of such a contactless reader can be seen in a payment system offered by a major gasoline seller in the US. In that system, a consumer is issued a small device that may be attached to a keyring, and that further contains the consumers payment account information and a short range wireless transmission element. When the user purchases gasoline at the pump, he merely needs to wave this device in front of a designated area on the pump, and the payment account information is transferred to the seller to process the transaction.
Although the use of contactless card readers provides for increased convenience to the user, there are also disadvantages that this technology presents. Due to the wireless nature of the contactless reader, it is possible that the contactless reader may be used for surreptitious interrogation of the portable wireless device by intercepting the portable wireless device's communications. In addition, it is conceivable that a contactless reader may be developed or modified to enhance its power and sensitivity and thereby increase its ability to interrogate with and intercept signals from the portable wireless device from a greater distance than specified in standards used for contactless readers.
Theft of sensitive information, such as an account number, using wireless interrogation or interception of communications from portable wireless device is a major concern for consumers and businesses alike. Unfortunately, given the sophistication of the wireless interrogation equipment and the nature of wireless signals, it is easy for wireless interrogation to occur at virtually any time and place. Once the victim of the wireless interrogation discovers that they had sensitive information stolen, it is often too late to discover where the theft took place. The victim must then deal with the consequences and hassle of correcting the unauthorized access and possible uses of the information.
In response to such risk, many payment service providers have instigated safeguards for protecting purchases from fraudulent attacks, for example, by employing encryption technologies to encrypt the payment account number and other data associated with account transactions. Encryption generally involves encrypting transaction data on one end of a transmission with a key, and then regenerating the original transaction data by decrypting the encrypted data received with the same key on the other end of the transmission. While encryption technologies have proven to be highly effective in preventing information theft, implementing or upgrading to the latest encryption technology often requires upgrades by the end users of payment processing networks. Due to the cost, time, and risk of potential business interruption (e.g., loss of sales), many merchants, for example, resist making necessary upgrades to their procedures and systems to implement such safeguards. Therefore, such safeguards have had limited success as they are generally expensive to implement, can be overcome, and have not been fully accepted by the credit card industry, merchants, payment processors, etc.
In the case of a portable wireless device, such as that described above in relation to a cellular phone, it may be possible to require some type of code, such as a Personal Identification Number (PIN) to be entered prior to enabling the short range wireless transmission element. Although this may partially resolve the issue of the wireless transmission being intercepted while the user is not actively using the device, it still does not resolve the situation where the sensitive information is intercepted while the user is making a legitimate purchase and has thus already entered the PIN.
Therefore, what is needed is a cost effective device and method that integrates easily with existing payment processing networks and prevents an unauthorized user from using data wirelessly interrogated or intercepted from a portable wireless device.
Embodiments of the invention address the above problems and other problems individually and collectively.
Embodiments of the present invention provide a device and methods for conducting transactions using pseudo primary account identifiers from portable wireless devices.
Embodiments of the invention include the use of “primary account identifiers” and “pseudo primary account identifiers.” A “primary account identifier” is an example of an “account identifier.” A “pseudo primary account identifier” is also an example of a “pseudo account identifier.” These account identifiers may include account numbers or any other alphanumeric sequence. An account identifier may be used to relate a transaction to a specific account.
In one embodiment, the present invention provides a method for conducting a transaction that includes receiving a pseudo account identifier that corresponds to a consumer's account identifier. The pseudo account identifier may be received at a portable wireless device and may have been previously generated by a remote server computer. The portable wireless device can receive the pseudo account identifier over a first network. This embodiment may also include providing the pseudo account identifier to an access device. The access device may generally comprise a reader that can receive the pseudo account identifier, and thereafter send a message to request authorization of a transaction. The reader may be a contact based reader or a contactless reader. The authorization request message may include the pseudo account identifier and may be sent to a payment processing network. Generally, the authorization request message may be sent to the payment processing network over a second network. The payment processing network may then process the authorization message and return a response that indicates if the transaction is approved or not approved.
In another embodiment, the present invention provides a method that includes receiving a request for a pseudo account identifier, wherein the pseudo account identifier corresponds with an account identifier. The request for the pseudo account identifier may be received over a first network. The method may further include generating a pseudo account identifier, where the pseudo account identifier is generally related to an account identifier. The pseudo account identifier may then be sent to a portable wireless device over the first network. Thereafter, the portable wireless device may use the pseudo account identifier to conduct one or more transactions, by providing the pseudo account identifier to an access device.
In yet another embodiment, the present invention provides for receiving a pseudo primary account identifier from a portable wireless device. The pseudo primary account identifier may be generally related to a primary account identifier. The method may further comprise sending a transaction authorization request that may contain the pseudo account identifier. The pseudo primary account identifier may then be received by a payment processing network and the payment processing network can convert the pseudo primary account identifier to the related primary account identifier. The authorization request message can then be processed using the primary account identifier and the transaction may be approved or denied and a response to the authorization request may be sent. The authorization response message may then be received and its contents can indicate if the transaction is approved or not approved.
In yet another embodiment, the present invention provides a portable wireless device for performing contactless transactions. The portable wireless device may include a long range wireless communications element. The portable wireless devices may also include a short range communications element. The portable wireless device can also includes a processor that is coupled to both the long and short range wireless communications elements. The processor can also be coupled to a memory that comprises computer code that allows the portable wireless device to receive a pseudo account identifier that generally corresponds to a primary account identifier. The pseudo account identifier may be generated by a remote server and sent to the portable wireless device over a first network. The pseudo account identifier may then be received by the portable wireless device by using the long range communications element. The memory may also comprise code that allows the portable wireless device to provide the pseudo account identifier to an access device. The portable wireless device can generally provide the pseudo account identifier to the access device by using the short range communications element. The memory may also contain code that allows the potable wireless device to store a primary account identifier.
In yet another embodiment, the present invention provides a method for conducting a transaction that includes generating a pseudo account identifier that corresponds to a consumer's account identifier. The pseudo account identifier may be sent by a portable wireless device and may be sent to a remote server computer. The portable wireless device can send the pseudo account identifier over a first network. This embodiment may also include providing the pseudo account identifier to an access device. The access device may generally comprise a reader that can receive the pseudo account identifier, and thereafter send a message to request authorization of a transaction. The reader may be a contact based reader or a contactless reader. The authorization request message may include the pseudo account identifier and may be sent to a payment processing network. Generally, the authorization request message may be sent to the payment processing network over a second network. The payment processing network may then process the authorization message and return a response that indicates if the transaction is approved or not approved.
In yet another embodiment, the present invention provides a method that includes receiving a pseudo account identifier, wherein the pseudo account identifier corresponds with an account identifier. The pseudo account identifier may be received over a first network. The method may further include storing the pseudo account identifier, where the pseudo account identifier is generally related to an account identifier. A receipt acknowledgement may then be sent to a portable wireless device over the first network. Thereafter, the portable wireless device may use the pseudo account identifier to conduct one or more transactions, by providing the pseudo account identifier to an access device.
In yet another embodiment, the present invention provides a portable wireless device for performing contactless transactions. The portable wireless device may include a long range wireless communications element. The portable wireless devices may also include a short range communications element. The portable wireless device can also includes a processor that is coupled to both the long and short range wireless communications elements. The processor can also be coupled to a memory that comprises computer code that allows the portable wireless device to generate a pseudo account identifier that generally corresponds to a primary account identifier. The pseudo account identifier may be sent to a remote server by the portable wireless device over a first network. The pseudo account identifier may then be sent to the remote server by using the long range communications element. The memory may also comprise code that allows the portable wireless device to provide the pseudo account identifier to an access device. The portable wireless device can generally provide the pseudo account identifier to the access device by using the short range communications element. The memory may also contain code that allows the potable wireless device to store a primary account identifier.
These and other embodiments of the invention are described in further detail below.
Embodiments of the invention are directed to the use of a pseudo account identifier such as a pseudo primary account identifier obtained by a portable wireless device. A portable wireless device according to an embodiment of the invention may be a mobile cellular phone, a PDA, and the like, capable of wireless transmission of a pseudo primary account identifier, in lieu of a user's real account identifier such as a primary account identifier (PAI) or a user's real primary account number (PAN). The portable wireless device may also be capable of receiving a pseudo primary account identifier that corresponds to a real account identifier.
Pseudo primary account identifiers may include account identifiers that are similar in format to a consumer's real account identifier. For example, if a user's real primary account identifier contains nineteen digits, the pseudo primary account identifier may also contain nineteen digits. In some embodiments, the pseudo primary account identifier may be of any length or type as long as it resembles the format of a real primary account identifier, such as a credit card number, debit card number, gift card number, and the like. For example, the pseudo primary account identifier may resemble a gift card number that is twenty one digits in length, when the user's real primary account identifier is nineteen digits long. The pseudo primary account identifier may also be described using terms such as bogus, fake, decoy, substitute, or the like.
From a merchant's perspective, transaction processing using a pseudo primary account identifier is completely transparent. That is to say that a merchant processing a transaction using a pseudo primary account identifier can process the transaction in exactly the same manner as if the transaction was occurring with a real primary account identifier. In some embodiments, it is actually preferable that the merchant have no knowledge as to whether a real or pseudo primary account identifier is being used in the transaction. As such, a merchant can continue to process transactions with currently installed equipment and no change is required at the merchant in order to process transactions using pseudo primary account identifiers.
In embodiments of the invention, the pseudo primary account identifier may be received by the portable wireless device through the use of any suitable communications network. Examples of such networks may include the cellular telephone network, networks provided by wireless e-mail service providers, and the like. Typically, these networks are open access networks and provide features and services that may be completely unrelated to transaction processing. For example, the cellular telephone network may be used for general voice communication. The cellular telephone network may also be used for data communications, to enable the user to perform tasks such as surfing the internet, reading e-mail, or any other tasks that are associated with a general purpose data network.
In one embodiment of the invention, a portable wireless device may have stored within its internal memory one or more primary account identifiers. A consumer who wishes to perform a transaction using the portable wireless device may begin by first enabling the device. Enabling the device may comprise turning the device on or entering a personal identification number (PIN) or password into the device to allow the user to access the device's functions. The user may then select which account he wishes to use to perform the transaction by selecting from among the one or more primary account identifiers that have been stored in the device. Selection of a primary account on the portable wireless device can occur using any suitable input mechanism. Examples can include keypad entry, touch screen entry, with or without a stylus, keyboard entry, voice response entry, and the like.
In this exemplary embodiment, the portable wireless device may then access the communications network through the use of one or more wireless access points provided by the network. The particular structure of a wireless access point may vary depending on the specific communications network, however access to a wireless communications network by a portable wireless device through the use of a wireless network access point is well known. For example, wireless communication from a cellular telephone to cellular base station wireless access points to gain access to the cellular telephone network is well known. Other types of wireless access technologies may include Bluetooth, WiFi, and the like.
Upon gaining access to the communications network, in this exemplary embodiment, the portable wireless device may send a request through the communications network to a payment processing network in order to retrieve a pseudo primary account identifier that corresponds to the primary account identifier that was previously selected. This request may be in the form of a message that includes sufficient information to identify for which primary account a pseudo primary account identifier is desired. In the simplest case, this request message may include the primary account identifier. In response, the payment processing network can return a pseudo primary account identifier that corresponds to the primary account identifier. The payment processing network may dynamically generate the pseudo primary account identifier, select it from a list of predefined pseudo primary account identifiers, or use any other means to create a pseudo primary account identifier. The payment processing network can further store the pseudo primary account identifier's relationship to the primary account identifier. The payment processing network can respond to the request from the portable wireless device with a response message that contains a pseudo primary account identifier. The response can be sent over the communications network back to the portable wireless device.
In addition to storing the relationship of the pseudo primary account identifier to the primary account identifier, the payment processing network may also store additional details about the relationship. For example, the pseudo primary account number may be set to expire after a certain number of transactions or after a certain time period. Doing so can help to ensure that if for some reason a pseudo primary account number is revealed to anyone other than an authorized user, the amount of damage that can be done is limited due to the limited lifetime of the pseudo primary account number.
Although in the exemplary embodiment described above, the pseudo primary account identifier is sent by the payment processing network in response to a request from the portable wireless device, the present invention is not limited to such implementations. In alternative implementations, the pseudo primary account identifier may not be requested at all, but rather is pushed to the portable wireless device at any time, such as when the device is turned on, when the device is idle, periodically, or through any other such criteria. Likewise, in the exemplary embodiment presented above, a request for a pseudo primary account identifier need not occur only after a user has enabled the device and selected an account. A request for a pseudo primary account identifier corresponding to a primary account identifier may occur at any time, such as when the device is turned on, when the device is idle, periodically, or through any other such criteria.
In an alternative embodiment, the pseudo primary account identifier may not be requested by the portable wireless device at all. The portable wireless device may generate the pseudo primary account identifier. The generated pseudo primary account identifier may then be sent to the payment processing network over the communications network. The payment processing network can store the received pseudo primary account identifier and store the association with the primary account identifier. The payment processing network can send an acknowledgement to the portable wireless device indicating that the pseudo primary account identifier has been received.
The payment processing network may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. An exemplary payment processing network may include VisaNet™. Payment processing networks such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, includes a single message system (SMS) that automatically authorizes and provides enough information to automatically clear and settle a financial transaction, and/or a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system, which performs clearing and settlement services.
In an exemplary embodiment, once the portable wireless device has a pseudo primary account identifier that is associated with a primary account identifier and has been enabled for use, the user may then proceed to use the portable wireless device to conduct a transaction. Typically, in addition to the elements for the portable wireless device to communicate with the communications network, the device can also have elements for shorter range wireless communication (e.g. near field communication). In one embodiment, the shorter range communication element may be a Radio Frequency Identification (RFID) tag or element, although embodiments of the invention are not limited to the use of RFID, and any suitable form of short range wireless transmission may be used. In alternative embodiments, the same elements that are used for communications with the communications network may also be used for the short range transmission.
The user may then utilize the short range wireless transmission element of the portable wireless device to transmit the pseudo primary account number to a contactless reader at a merchant site. A contactless reader can be part of an access device, which can have wireless communication and transmission modules (e.g., receiver, transceiver, etc.). Such contactless readers may be present in access devices such as point-of-sale (POS) terminals, ATMs (automatic teller machines), and the like. The portable wireless devices according to embodiments of the invention may operate with any number of such contactless reader devices using a variety of operating standards.
Although this exemplary embodiment has referred to access devices that contain contactless readers, the present invention is not limited to access devices containing contactless readers. Any suitable form of access device, including both contact and contactless access devices, are within the scope of embodiments of the present invention.
After receiving the pseudo primary account identifier from the contactless device, the merchant may then use that identifier, as well as additional information to form an authorization request message. An authorization request message can include a request for authorization to conduct an electronic payment transaction or some other type of activity. It may include one or more of an account holder's payment account number, currency code, sale amount, merchant transaction stamp, acceptor city, acceptor state/country, POS transaction number, POS transaction type, etc. Optionally, an authorization request message may be protected using a secure encryption method—e.g., 128-bit SSL or equivalent-in order to prevent data from being compromised.
Because the pseudo primary account identifier can be transitory and may have a limited lifetime, it can be noted that this provides a level of protection to the consumer's account. If the pseudo primary account identifier transmitted between the portable wireless device and the contactless reader is intercepted, it would be of limited or no use to a person wishing to use it for conducting unauthorized transactions, as it would likely have expired before any illicit use could be made. It is further noted that the primary account is also protected from unscrupulous merchants because the merchant only receives the transitory pseudo primary account identifier and never receives the real primary account identifier.
Additionally, because the pseudo primary account identifier is structured in such a way as to be indistinguishable from a real primary account identifier, the merchant will not have to alter any of his transaction processing systems. From the merchants point of view, the transaction proceeds exactly the same, regardless of if a real or pseudo primary account identifier is being used.
As mentioned above, transaction processing from the merchant's point of view occurs without any changes. Typically, after the merchant generates an authorization request message, that message is sent to the merchant's acquirer. An acquirer is typically a business entity (e.g., a commercial bank) that has a business relationship with a particular merchant. The authorization request message is typically sent to the acquirer using a transaction processing network. The transaction processing network is typically more secure than the communications network that has been discussed previously, because access is generally limited to only those parties that are involved in the authorization and settlement of transactions.
The acquirer can then forward the authorization request message to the payment processing network using the transaction processing network. The payment processing network, having previously generated or received the pseudo primary account identifier and stored the relationship to a primary account identifier, may then convert the pseudo primary account identifier in the authorization request message back to the real primary account identifier. Conversion of the pseudo primary account identifier to the real primary account identifier can be done through any suitable means, such as a mathematical operation, a database table look up, generating the primary account identifier based on the pseudo primary account identifier, or any other means that are well known. The authorization request message that now contains the real primary account identifier may then be sent to the issuer of the primary account identifier.
An issuer is typically a business entity (e.g., a bank) that issues accounts, such as a credit or debit card to a consumer. These accounts are generally identified by a primary account identifier. Some entities such as American Express perform both issuer and acquirer functions. Embodiments of the invention encompass such single entity issuer-acquirers.
Typically, an electronic payment transaction is authorized if the consumer conducting the transaction has sufficient funds or credit to conduct the transaction. Conversely, if there are insufficient funds or credit in the consumer's account, or if the consumer's portable wireless device is on a blacklist (e.g., it is indicated as stolen), then an electronic payment transaction may not be authorized (e.g., declined). After making a determination if the transaction is authorized or not, the issuer may return an authorization response to the payment processing network over the transaction processing network. The payment processing network may then return this response to the acquirer over the transaction processing network. The response may then be finally sent back to the originating merchant from the acquirer over the transaction processing network.
The user, through the merchant, then receives indication from the response to indicate that the transaction has been approved or denied. Examples of such indication could be an approval message displayed on a screen at the merchant or a receipt being printed at the merchant.
Throughout the discussion above of exemplary embodiments of the present invention, reference has been made to a communications network and a transaction processing network. Although referenced as two separate networks, it should be understood that the networks may share some common physical elements. For example, the portable wireless communications device may access the communications network through the use of a wireless network access point. From there, messages sent from the device to the payment processing network may be sent over a general purpose network such as the Internet. Likewise, communications in the transaction processing network, such as those between the acquirer and the payment processing network or those between the payment processing network and the issuer, may also be sent over the Internet. Through the use of various protocols, encryptions, network configurations, and the like, which are all known within the art, the communications network and the transaction processing network may be thought of as two logically separated networks, despite the fact that they may share some common physical elements.
The portable wireless device 102 according to embodiments of the invention may be in any suitable form. For example, the portable wireless device 102 may include any such device that contains a wireless communication element. Such devices may include cellular telephones, Personal Digital Assistants (PDA), pagers and the like. Such portable wireless devices 102 can have one or more antennas coupled with wireless transmission elements to wirelessly transmit and receive data using a wireless communications media. One exemplary embodiment of a portable wireless device 102 may include a cellular telephone. The cellular telephone may be equipped with one or more antennas that are coupled with long range transmission elements to allow the cellular telephone to communicate with a communications network 116, such as the cellular telephone network.
In this exemplary embodiment, the cellular telephone 102 may communicate with the cellular network 116 through the use of one or more wireless access points 118. The access points 118 may be wireless base stations that provide coverage to large geographic areas or may be more localized such as those access points that provide in building coverage. In any case, access to the communications network 116 is provided to the portable wireless device through the use of wireless access points 118. There are many forms of wireless access to a communications network that would be know to a person of skill in the art and any suitable alternative would be within the scope and spirit of the present invention.
The communications network 116 may be one of any suitable form. As discussed above, one such network may be the cellular telephone network. Other examples may include the public switched telephone network, a proprietary network such as the RIM network, or any other network capable of transmitting and receiving data between two or more endpoints. The communications network 116 allows for a communications channel between any two suitably configured end points.
The portable wireless device 102 may also contain a short range transmission element that may be used to communicate with a contactless reader 104. The short range transmission element can be one of many types that would be well known to a person of skill in the art. Examples of these types of communications elements could be elements such as Radio Frequency Identification Tags (RFID), optical communications, such as through the use of optical transponders, or any other method of communications over a short range that are known in the art. The contactless reader 104 may be a device capable of communicating with the portable wireless device and may contain communications elements to support such communications. The contactless reader 104 may be capable of wirelessly receiving primary and pseudo primary account identifiers. The contactless reader 104 can be located at a merchant's 106 location, or may be simply operated by the merchant 106.
The merchant 106 may also be operatively connected to an acquirer 108 through at least a portion of a transaction processing network 114. The acquirer 108 may be operatively coupled to one or more merchants 106 in order to provide the merchants 106 with access to a payment processing network 110. The acquirer 108 in turn may be operatively coupled to a payment processing network 110 through the transaction processing network 114. The acquirer 108 may receive transaction requests from the merchant 106 and transmit the transaction requests to the payment processing network 110. The acquirer 108 typically communicates with the payment processing network through the use of a secured communications channel, such as that provided by the transaction processing network 114. Although the secured communications channel may make use of elements of the communications network 116, access to the payment processing network 110 by the merchant 106 through the acquirer 108 is restricted.
The payment processing network 110 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, and clearing and settlement services. An exemplary payment processing network 110 may include VisaNet™. Payment processing networks such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, includes a single message system (SMS) that automatically authorizes and provides enough information to automatically clear and settle a financial transaction, and/or a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system, which performs clearing and settlement services.
The payment processing network 110 may include a server computer. A server computer is typically a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a web server. The payment processing network 110 may use any suitable wired or wireless network, including the Internet.
The payment processing network 110 may further be connected to a communications network 116. This connection allows the payment processing network to send and receive messages to any other entity that may also be connected to the communications network 116. Although the payment processing network 110 may make use of common physical network elements to communicate with acquirers 108 and portable wireless devices 102, it is understood that embodiments of the invention allow for communication with the payment processing network 110 through the use of at least two separate communications channels (e.g., the transaction processing network 114 and the communications network 116). The first channel, or network may be a publicly available communications network 116, such as the cellular telephone network. The second channel, or network, may be a restricted access network, such as the one used to communicate between acquirers 108 and the payment processing network 110.
The payment processing network 110 may be configured to receive a request for a pseudo primary account identifier that corresponds to a primary account identifier over the communications network 116. The payment processing network 110 may then generate a pseudo primary account number corresponding to a primary account number and return the pseudo primary account number to the source of the request using the communications network 116. Additionally, the payment processing network 110 can store the pseudo primary account identifier that was generated so that it may be later converted back into the associated primary account identifier.
In an alternative embodiment, the payment processing network 110 may be configured to receive a pseudo primary account identifier that corresponds to a primary account identifier over the communications network 116. The payment processing network 110 may then store the pseudo primary account number corresponding to a primary account number and return an acknowledgement to the source of the request using the communications network 116. Additionally, the payment processing network 110 can store the pseudo primary account identifier that was received so that it may be later converted back into the associated primary account identifier.
As used herein, “generated” pseudo account identifiers can include those that are created for the first time for the particular transaction or transactions taking place. A pseudo account number may alternatively be generated by retrieving the pseudo account number from a memory or computer readable medium, wherein the pseudo account number was previously created and then stored.
Additionally, the payment processing network 110 is also operatively coupled to one or more issuer 112 systems through the transaction processing network 114. An issuer 112 is typically a business entity (e.g. a bank) that issues financial accounts. Issuers 112 generally track the accounts that are issued through the use of a primary account identifier. An issuer 112 may receive a transaction authorization message that is generated at a contactless reader 104, passed through a merchant 106 via an acquirer 108, to a payment processing network 110 and transmitted to the issuer 112 over a transaction processing network 114. The issuer 112 may then process the transaction authorization request message to determine if the transaction is authorized and return a response back to the merchant 106 through the use of the transaction processing network 114.
The user then may select which virtual card they wish to use to conduct the transaction 214. A virtual card corresponds to an account that the user has with an issuer and may be identified by the issuer through the use of a primary account identifier. A user may have several different accounts which may be issued by several different issuers. All of these accounts may be stored on the portable wireless device and the user selects which one he wishes to use for this transaction.
In this exemplary embodiment, the portable wireless device 202 may then request a pseudo primary account identifier that corresponds with a primary account identifier from the payment processing network 210. The request 216 for the pseudo account number will contain information that is necessary for the payment processing network to identify the primary account identifier and generate a pseudo primary account identifier. In one embodiment, the request message may contain the primary account identifier itself 216. The request message can be sent from the portable wireless device 202 to the payment processing network 210 over a communications network that is generally separate from the network used to authorize the transaction. In an alternative embodiment, the portable wireless device 202 may generate a pseudo primary account identifier that corresponds to a primary account identifier, and send the generated pseudo primary account identifier to the payment processing network 210.
The payment processing network 210 may then receive the request for a pseudo primary account identifier (PAI), along with sufficient information to identify the primary account identifier 216. The payment processing network 210 can then generate a pseudo primary account identifier and store the pseudo primary account identifier for later use 218. The pseudo primary account identifier may then be returned to the portable wireless device 202 through the communications network 220. The pseudo primary account number may then be used to conduct the transaction. Although in this exemplary embodiment, the pseudo primary account number is not requested until the user has entered his PIN, it should be noted that in alternative embodiments, the request could be made at any time. For example, a request for a pseudo primary account identifier could be made at the time the portable wireless device is powered on, at certain periodic time intervals, or at any time the portable wireless device is idle. In other alternative embodiments, the pseudo primary account identifier may not be requested but rather may be pushed from the payment processing network to the portable wireless device. In another alternative embodiment the pseudo primary account number is generated by the portable wireless device and sent to the payment processing network. The payment processing network can store the pseudo primary account identifier and send an acknowledgement of receipt to the portable wireless device.
Once the portable wireless device has received the pseudo primary account number, the transaction may continue. The user can hold the portable wireless device 202 in the vicinity 222 of the contactless reader 204. Through the use of the short range communications element in the portable wireless device 202, the pseudo primary account number may be transmitted 224 to the contactless reader 204 and to the merchant 206, 226. The pseudo primary account identifier can then be included in an authorization request message 228 that is sent to an acquirer 208. The acquirer 208 may then send the authorization request message that includes the pseudo primary account number 230 to the payment processing network 210. The messages that are sent between the merchant 206, the acquirer 208, and the payment processing network 210, are typically sent over a restricted access network that is separate from the communications channel used to request the pseudo primary account identifier.
The authorization request message containing the pseudo primary account identifier 230 may then be received by the payment processing network 210. Using the data stored when the pseudo primary account number was generated or received 218, the pseudo primary account identifier can be converted to the primary account identifier 232. An authorization request containing the real primary account identifier may then be sent 234 to an issuer 212 which can process the transaction to determine if it should be allowed or denied 236. The response to the authorization request message, indicating if the transaction is approved or not can then be sent 238 from the issuer 212, through the payment processing network 210, 240 and acquirer 208, 242, back to the merchant 206. Based on this response 242 the merchant can determine if the transaction should proceed or not 244.
The message flow in
The process continues at step 404 where the portable wireless device attempts to retrieve a pseudo primary account identifier from the payment processing network. If a pseudo primary account identifier is successfully retrieved 406, the process moves to step 408 where the pseudo primary account number is transmitted to the acquirer. The acquirer then transmits the pseudo primary account identifier to the payment processing network 410. The payment processing network will then convert the pseudo primary account identifier back to the primary account identifier and further transmit the request to the issuer 412.
If the portable wireless device fails to retrieve a pseudo primary account identifier at step 406 the process continues on to step 414 where the transaction proceeds using the primary account identifier. The primary account identifier is transmitted from the portable wireless device to the acquirer at step 416. From there the acquirer transmits the primary account identifier to the payment processing network at step 418. Because no pseudo primary account identifier was retrieved, there is no need to convert the primary account identifier, and it is further transmitted to the issuer at step 418.
At step 420, the issuer receives the transaction request that contains the primary account identifier. Using any number of criteria, such as the account specified by the primary account identifier being in good standing, having sufficient funds available, having sufficient credit available, etc., the issuer makes a decision at step 422 to either approve or deny the transaction. If the transaction is denied, the process moves to step 424, and a message is returned indicating the transaction has been denied. If the transaction is approved at step 422 a message indicating approval is sent to the originator. Furthermore, settlement and clearing processes occur at step 428 to actually transfer funds from the account held at the issuer to the merchant.
The long range wireless communications element 504 may be designed to transmit and receive communications between the portable wireless device 502 and a wireless access point 118, the access point providing access to a communications network 116 through which the portable wireless device may communicate with a payment processing network 110. Any number of long range wireless communications elements are well known in the art and may be used to accomplish the reception and transmission of data between the portable wireless device 502 and the wireless access point 118. The long range wireless communications element may use any viable communications link such as optical transmission or RF transmission.
The short range wireless communications element 506 may be designed to transmit and receive communications between the portable wireless device 502 and a contactless reader 104. Any number of short range wireless communications elements are well known in the art and may be used to accomplish this function. In one embodiment, the short range wireless transmission element may be a RFID tag, although any suitable short range wireless transmission element may be used.
The processor 508 may be virtually any type of integrated circuit and/or data processing system, such as a microprocessor, field programmable gate array (FPGA), application specific integrated circuit (ASIC), and the like, that may be configured to perform embodiments of the present invention.
The memory 510 can be a non-volatile or volatile memory such as a random access memory that has sufficient space to hold the necessary programming and data structures of the invention. While the memory 510 is shown as a single entity, it should be understood that the memory 510 may in fact comprise a plurality of modules, and that the memory 510 may exist at multiple levels, from high speed registers and caches to lower speed but larger direct random access memory (DRAM) chips. In one embodiment, the memory 510 may include a program that includes computer code for receiving a pseudo primary account identifier through the long range wireless transmission element 504. The memory 510 may also include code for generating a pseudo primary account number and sending the pseudo primary account number using the long range wireless transmission element 504. The memory 510 may further include computer code for providing the pseudo primary account identifier to an access device including a contactless reader 104, through the short range wireless communications element 506. The memory 510 may also include code to store one or more primary account identifiers. The program may use any one of a number of different programming languages. For example, the program code can be written in PLC code (e.g., ladder logic), a higher-level language such as C, C++, Java, or a number of other languages.
The user interface module 512 may be any type of interface that allows a user to interact with the portable wireless device 502. Examples of such interfaces may be keypads, keyboards, touch screens, voice response units, and the like.
Embodiments of the invention have a number of advantages. First, since a pseudo account identifier is sent over a different communication network than the network that is used to conduct the authorization for the transaction, the merchant never receives the actual account identifier. There are many fraudulent merchants and this process reduces fraud as the merchant does not see the consumer's real account number. Second, since the “back end” server computer at the payment processing network (or at some other location) sends the pseudo account identifier, or alternatively receives a pseudo primary account identifier, it knows what account identifier to expect. The back end, remote server computer can change the pseudo account number as often as needed (e.g., with ever transaction, with every third transaction, etc.). Third, since the pseudo account identifier is retrieved (in some embodiments) when the user is selecting a virtual card or is otherwise manipulating his portable wireless device to conduct the transaction, the user does not experience any delay in conducting the purchase. The retrieval of the pseudo account identifier is transparent to the consumer, and the consumer need not know that the pseudo account identifier is ever retrieved. The same transparency to the consumer is also present in embodiments where the portable wireless device generates the pseudo primary account identifier.
The portable wireless device that is used in embodiments of the invention may be in any suitable form. For example, suitable portable wireless devices can be hand-held and compact so that they can fit into a consumer's wallet and/or pocket (e.g., pocket-sized). They may include smart cards, ordinary credit or debit cards (with a magnetic strip and without a microprocessor), keychain devices (such as the Speedpass™ commercially available from Exxon-Mobil Corp.), etc. Other examples of portable consumer devices include cellular phones, personal digital assistants (PDAs), pagers, payment cards, security cards, access cards, smart media, transponders, and the like. The portable consumer devices can also be debit devices (e.g., a debit card), credit devices (e.g., a credit card), or stored value devices (e.g., a stored value card).
An exemplary portable consumer device 602 in the form of a phone may comprise a computer readable medium and a body as shown in
Information in the memory may also be in the form of data tracks that are traditionally associated with credits cards. Such tracks include Track 1 and Track 2. Track 1 (“International Air Transport Association”) stores more information than Track 2, and contains the cardholder's name as well as account number and other discretionary data. This track is sometimes used by the airlines when securing reservations with a credit card. Track 2 (“American Banking Association”) is currently most commonly used. This is the track that is read by ATMs and credit card checkers. The ABA (American Banking Association) designed the specifications of this track and all world banks must abide by it. It contains the cardholder's account, encrypted PIN, plus other discretionary data.
The portable wireless device 602 may further include a contactless element 618, which is typically implemented in the form of a semiconductor chip (or other data storage element) with an associated wireless transfer (e.g., data transmission) element, such as an antenna. Contactless element 618 is associated with (e.g., embedded within) portable consumer device 602 and data or control instructions transmitted via a cellular network may be applied to contactless element 618 by means of a contactless element interface (not shown). The contactless element interface functions to permit the exchange of data and/or control instructions between the mobile device circuitry (and hence the cellular network) and an optional contactless element 618.
Contactless element 618 is capable of transferring and receiving data using a near field communications (“NFC”) capability (or near field communications medium) typically in accordance with a standardized protocol or data transfer mechanism (e.g., ISO 14443/NFC). Near field communications capability is a short-range communications capability, such as RFID, Bluetooth™, infra-red, or other data transfer capability that can be used to exchange data between the portable wireless device 602 and an interrogation device. Thus, the portable wireless device 602 is capable of communicating and transferring data and/or control instructions via both cellular network and near field communications capability.
The portable consumer device 602 may also include a processor 608 (e.g., a microprocessor) for processing the functions of the portable consumer device 602 and a display 610 to allow a consumer to see phone numbers and other information and messages. The portable wireless device 602 may further include input elements 612 to allow a consumer to input information into the device, a speaker 614 to allow the consumer to hear voice communication, music, etc., and a microphone 622 to allow the consumer to transmit her voice through the portable wireless device 602. The portable wireless device 602 may also include an antenna 604 for wireless data transfer (e.g., data transmission).
The various participants and elements in
The above description is illustrative but not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.
A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary.
Patent | Priority | Assignee | Title |
10552807, | Mar 19 2012 | Fidelity Information Services, LLC | Systems and methods for real-time account access |
10726416, | Jun 25 2007 | Visa International Service Association | Secure mobile payment system |
11526878, | Mar 19 2012 | Fidelity Information Services, LLC | Systems and methods for real-time account access |
11556907, | Mar 19 2012 | Fidelity Information Services, LLC | Systems and methods for real-time account access |
11562334, | Mar 19 2012 | Fidelity Information Services, LLC | Systems and methods for real-time account access |
11678229, | Jul 14 2008 | Sony Corporation | Communication apparatus, communication system, notification method, and program product |
11983708, | Mar 19 2012 | Fidelity Information Services, LLC | Systems and methods for real-time account access |
Patent | Priority | Assignee | Title |
5253345, | Jul 07 1988 | Sears Brands, LLC | Point of sale register system |
5613012, | Nov 28 1994 | Open Invention Network, LLC | Tokenless identification system for authorization of electronic transactions and electronic transmissions |
5781438, | Dec 19 1995 | Pitney Bowes Inc. | Token generation process in an open metering system |
5883810, | Sep 24 1997 | Microsoft Technology Licensing, LLC | Electronic online commerce card with transactionproxy number for online transactions |
5953710, | Oct 09 1996 | Children's credit or debit card system | |
5956699, | Oct 03 1996 | Jaesent Inc. | System for secured credit card transactions on the internet |
6000832, | Sep 24 1997 | Microsoft Technology Licensing, LLC | Electronic online commerce card with customer generated transaction proxy number for online transactions |
6014635, | Dec 08 1997 | SHC DIRECT, INC | System and method for providing a discount credit transaction network |
6044360, | Apr 16 1996 | RESTRICTED SPENDING SOLUTIONS, LLC | Third party credit card |
6163771, | Aug 28 1997 | PayPal, Inc | Method and device for generating a single-use financial account number |
6227447, | May 10 1999 | JPMORGAN CHASE BANK, N A | Cardless payment system |
6236981, | Nov 20 1996 | British Telecommunications public limited company | Transaction system |
6253328, | Feb 12 1998 | Method and apparatus for securing passwords and personal identification numbers | |
6267292, | Jun 13 1997 | PayPal, Inc | Method and apparatus for funds and credit line transfers |
6327578, | Dec 29 1998 | PayPal, Inc | Four-party credit/debit payment protocol |
6341724, | May 10 1999 | JPMORGAN CHASE BANK, N A | Cardless payment system |
6385596, | Feb 06 1998 | Microsoft Technology Licensing, LLC | Secure online music distribution system |
6422462, | Mar 30 1998 | Apparatus and methods for improved credit cards and credit card transactions | |
6425523, | Aug 17 1998 | TUMBLEWEED HOLDINGS LLC | Method for preventing unauthorized use of credit cards in remote payments and an optional supplemental-code card for use therein |
6456984, | May 28 1999 | Qwest Communications International Inc | Method and system for providing temporary credit authorizations |
6592044, | May 15 2000 | Privasys, Inc | Anonymous electronic card for generating personal coupons useful in commercial and security transactions |
6636833, | Mar 25 1998 | ORBIS PATENTS LTD | Credit card system and method |
6748367, | Sep 24 1999 | Method and system for effecting financial transactions over a public network without submission of sensitive information | |
6805287, | Sep 12 2002 | Liberty Peak Ventures, LLC | System and method for converting a stored value card to a credit card |
6879965, | Mar 01 2000 | SLINGSHOT TECHNOLOGIES LLC | Method, system and computer readable medium for web site account and e-commerce management from a central location |
6891953, | Jun 27 2000 | Microsoft Technology Licensing, LLC | Method and system for binding enhanced software features to a persona |
6901387, | Dec 07 2001 | Liberty Peak Ventures, LLC | Electronic purchasing method and apparatus for performing the same |
6931382, | Jan 24 2001 | Kioba Processing, LLC | Payment instrument authorization technique |
6938019, | Aug 29 2000 | AMPACASH CORPORATION | Method and apparatus for making secure electronic payments |
6941285, | Apr 14 2000 | Method and system for a virtual safe | |
6980670, | Feb 09 1998 | Open Invention Network, LLC | Biometric tokenless electronic rewards system and method |
6990470, | Apr 11 2000 | MasterCard International Incorporated | Method and system for conducting secure payments over a computer network |
6991157, | Sep 12 2002 | Liberty Peak Ventures, LLC | System and method for re-associating an account number to another transaction account |
7051929, | Oct 18 2004 | Secure credit card having daily changed security number | |
7069249, | Jul 26 1999 | iPrivacy, LLC | Electronic purchase of goods over a communications network including physical delivery while securing private and personal information of the purchasing party |
7103576, | Sep 21 2001 | JPMORGAN CHASE BANK, N A | System for providing cardless payment |
7113930, | Feb 23 2001 | HEWLETT-PACKARD DEVELOPMENT COMPANY L P | Conducting transactions |
7136835, | Mar 25 1998 | ORBIS PATENTS LTD | Credit card system and method |
7177835, | Aug 28 1997 | PayPal, Inc | Method and device for generating a single-use financial account number |
7177848, | Apr 11 2000 | MasterCard International Incorporated | Method and system for conducting secure payments over a computer network without a pseudo or proxy account number |
7194437, | May 14 1999 | Amazon Technologies, Inc | Computer-based funds transfer system |
7209561, | Jul 19 2002 | Cybersource Corporation | System and method for generating encryption seed values |
7264154, | Jul 12 2004 | HARRIS INTELLECTUAL PROPERTY, LP | System and method for securing a credit account |
7287692, | Jul 28 2004 | Cisco Technology, Inc. | System and method for securing transactions in a contact center environment |
7292999, | Mar 15 2001 | Liberty Peak Ventures, LLC | Online card present transaction |
7350230, | Dec 18 2002 | CITIBANK, N A ; NCR Atleos Corporation | Wireless security module |
7353382, | Aug 08 2002 | InterDigital Patent Holdings, Inc | Security framework and protocol for universal pervasive transactions |
7379919, | Apr 11 2000 | MasterCard International Incorporated | Method and system for conducting secure payments over a computer network |
7415443, | Mar 15 2001 | Liberty Peak Ventures, LLC | Online card present transaction |
7444676, | Aug 29 2001 | Direct authentication and authorization system and method for trusted network of financial institutions | |
7469151, | Sep 01 2006 | MasterCard International Incorporated | Methods, systems and computer program products for over the air (OTA) provisioning of soft cards on devices with wireless communications capabilities |
7548889, | Jan 24 2005 | Microsoft Technology Licensing, LLC | Payment information security for multi-merchant purchasing environment for downloadable products |
7567934, | Mar 25 1998 | ORBIS PATENTS, LTD | Credit card system and method |
7567936, | Oct 14 2003 | BENHOV GMBH, LLC | Method and apparatus for handling pseudo identities |
7571139, | Feb 19 1999 | EXXONMOBIL RESEARCH & ENGINEERING CO | System and method for processing financial transactions |
7571142, | Jan 22 1999 | ORBIS PATENTS LTD | Credit card system and method |
7580898, | Mar 15 2004 | Fitbit, Inc | Financial transactions with dynamic personal account numbers |
7584153, | Mar 15 2004 | Fitbit, Inc | Financial transactions with dynamic card verification values |
7593896, | Mar 25 1998 | Orbis Patents Ltd. | Credit card system and method |
7606560, | Aug 08 2002 | PCMS HOLDINGS, INC | Authentication services using mobile device |
7627531, | Mar 07 2000 | Liberty Peak Ventures, LLC | System for facilitating a transaction |
7627895, | Mar 31 2004 | British Telecommunications public limited company | Trust tokens |
7650314, | May 25 2001 | Liberty Peak Ventures, LLC | System and method for securing a recurrent billing transaction |
7685037, | Mar 26 2001 | 3 M FUTURE LIMTIED | Transaction authorisation system |
7702578, | Jun 14 2001 | SLINGSHOT TECHNOLOGIES LLC | Method, system and computer readable medium for web site account and e-commerce management from a central location |
7707120, | Apr 17 2002 | Visa International Service Association | Mobile account authentication service |
7712655, | Jan 20 2004 | Banking computer account system with lock for secure payment via telephone | |
7734527, | Aug 29 2000 | AMPACASH CORPORATION | Method and apparatus for making secure electronic payments |
7753265, | Jul 12 2004 | HARRIS INTELLECTUAL PROPERTY, LP | System and method for securing a credit account |
7770789, | May 17 2007 | Shift4 Corporation | Secure payment card transactions |
7784685, | Apr 26 2007 | United Services Automobile Association (USAA); United Services Automobile Association | Secure card |
7793851, | May 09 2005 | DYNAMICS INC | Dynamic credit card with magnetic stripe and embedded encoder and methods for using the same to provide a copy-proof credit card |
7801826, | Aug 08 2002 | PCMS HOLDINGS, INC | Framework and system for purchasing of goods and services |
7805376, | Jun 14 2002 | Liberty Peak Ventures, LLC | Methods and apparatus for facilitating a transaction |
7805378, | Jul 10 2001 | Liberty Peak Ventures, LLC | System and method for encoding information in magnetic stripe format for use in radio frequency identification transactions |
7818264, | Jun 19 2006 | Visa U.S.A. Inc.; VISA U S A INC | Track data encryption |
7828220, | May 09 2005 | DYNAMICS INC | Dynamic credit card with magnetic stripe and embedded encoder and methods for using the same to provide a copy-proof credit card |
7835960, | Mar 07 2000 | Liberty Peak Ventures, LLC | System for facilitating a transaction |
7841523, | May 17 2007 | Shift4 Corporation | Secure payment card transactions |
7841539, | Feb 15 2007 | Smart card with random temporary account number generation | |
7844550, | Aug 28 1997 | PayPal, Inc | Method and device for generating a single-use financial account number |
7848980, | Dec 26 2006 | Visa U.S.A. Inc. | Mobile payment system and method using alias |
7849020, | Apr 19 2005 | Microsoft Technology Licensing, LLC | Method and apparatus for network transactions |
7853529, | Aug 28 1997 | PayPal, Inc | Method and device for generating a single-use financial account number |
7853995, | Nov 18 2005 | Microsoft Technology Licensing, LLC | Short-lived certificate authority service |
7865414, | Mar 01 2000 | SLINGSHOT TECHNOLOGIES LLC | Method, system and computer readable medium for web site account and e-commerce management from a central location |
7873579, | Mar 15 2001 | Liberty Peak Ventures, LLC | Merchant facilitation of online card present transaction |
7873580, | Mar 15 2001 | Liberty Peak Ventures, LLC | Merchant system facilitating an online card present transaction |
7890393, | Feb 07 2002 | PayPal, Inc | Method and system for completing a transaction between a customer and a merchant |
7891563, | May 17 2007 | Shift4 Corporation | Secure payment card transactions |
7896238, | Apr 03 2007 | XYLON, LLC | Secured transaction using color coded account identifiers |
7908216, | Jul 22 1999 | Visa International Service Association | Internet payment, authentication and loading system using virtual smart card |
7922082, | Jan 04 2008 | M2 INTERNATIONAL LTD | Dynamic card validation value |
7931195, | May 09 2005 | DYNAMICS INC | Dynamic credit card with magnetic stripe and embedded encoder and methods for using the same to provide a copy-proof credit card |
7937324, | Sep 13 2007 | Visa U.S.A. Inc. | Account permanence |
7938318, | Apr 03 2007 | Kioba Processing, LLC | System and method for controlling secured transaction using directionally coded account identifiers |
7954705, | May 09 2005 | DYNAMICS INC | Dynamic credit card with magnetic stripe and embedded encoder and methods for using the same to provide a copy-proof credit card |
7959076, | Apr 26 2007 | United Services Automobile Association (USAA); United Services Automobile Association | Secure card |
7996288, | Nov 15 2000 | iPrivacy, LLC | Method and system for processing recurrent consumer transactions |
8025223, | Jun 10 2005 | Liberty Peak Ventures, LLC | System and method for mass transit merchant payment |
8046256, | Apr 14 2000 | Liberty Peak Ventures, LLC | System and method for using loyalty rewards as currency |
8060448, | May 30 2001 | Late binding tokens | |
8060449, | Jan 05 2009 | T-MOBILE INNOVATIONS LLC | Partially delegated over-the-air provisioning of a secure element |
8074877, | Dec 24 2007 | Dynamics Inc. | Systems and methods for programmable payment cards and devices with loyalty-based payment applications |
8074879, | Jul 12 2004 | HARRIS INTELLECTUAL PROPERTY, LP | System and method for securing a credit account |
8082210, | Apr 29 2003 | The Western Union Company | Authentication for online money transfers |
8095113, | Oct 17 2007 | First Data Corporation | Onetime passwords for smart chip cards |
8104679, | Dec 17 2003 | Fitbit, Inc | Display payment card with fraud and location detection |
8109436, | Apr 26 2007 | United Services Automobile Association (USAA); United Services Automobile Association | Secure card |
8121942, | Jun 25 2007 | Visa U.S.A. Inc. | Systems and methods for secure and transparent cardless transactions |
8121956, | Jun 25 2007 | Visa U.S.A. Inc. | Cardless challenge systems and methods |
8126449, | Nov 13 2008 | Liberty Peak Ventures, LLC | Servicing attributes on a mobile device |
8171525, | Sep 15 2011 | GOOGLE LLC | Enabling users to select between secure service providers using a central trusted service manager |
8175973, | Jul 22 1999 | Visa International Service Association | Internet payment, authentication and loading system using virtual smart card |
8190523, | Sep 13 2007 | Visa U.S.A. Inc. | Account permanence |
8196813, | Dec 03 2008 | PayPal, Inc | System and method to allow access to a value holding account |
8205791, | Oct 11 2005 | National Payment Card Association | Payment system and methods |
8219489, | Jul 29 2008 | Visa U.S.A. Inc. | Transaction processing using a global unique identifier |
8224702, | Dec 28 2007 | PayPal, Inc | Systems and methods for facilitating financial transactions over a network |
8225385, | Mar 23 2006 | Microsoft Technology Licensing, LLC | Multiple security token transactions |
8229852, | Jun 25 2007 | Visa International Service Association | Secure mobile payment system |
8265993, | Apr 14 2000 | Liberty Peak Ventures, LLC | System and method for using loyalty rewards as currency |
8280777, | Dec 28 2007 | PayPal, Inc | Systems and methods for facilitating financial transactions over a network |
8281991, | Aug 07 2008 | VISA U S A INC | Transaction secured in an untrusted environment |
8328095, | May 17 2007 | Shift4 Corporation | Secure payment card transactions |
8336088, | Apr 19 2010 | Visa International Service Association | Alias management and value transfer claim processing |
8346666, | Jan 19 2010 | Visa International Service Association | Token based transaction authentication |
8376225, | Apr 26 2007 | United Services Automobile Association (USAA) | Secure card |
8380177, | Apr 09 2010 | PayPal, Inc | Mobile phone payment processing methods and systems |
8387873, | Jun 10 2005 | Liberty Peak Ventures, LLC | System and method for mass transit merchant payment |
8401539, | Nov 13 2008 | Liberty Peak Ventures, LLC | Servicing attributes on a mobile device |
8401898, | Apr 14 2000 | Liberty Peak Ventures, LLC | System and method for using loyalty rewards as currency |
8402555, | Mar 21 2010 | UNITED STATES DEPARTMENT OF THE TREASURY BUREAU OF THE FISCAL SERVICE | Personalized digital media access system (PDMAS) |
8403211, | Sep 04 2008 | PATHWARD, NATIONAL ASSOCIATION | System, program product and methods for retail activation and reload associated with partial authorization transactions |
8412623, | Jul 15 2002 | CITICORP CREDIT SERVICES, INC USA | Method and system for a multi-purpose transactional platform |
8412837, | Jul 08 2004 | ROSKIND, JAMES A , DR | Data privacy |
8417642, | Sep 14 2004 | CORK GROUP TRADING LTD | Online commercial transaction system and method of operation thereof |
8433116, | Nov 03 2009 | STRATA SKIN SCIENCES, INC | Showing skin lesion information |
8447699, | Oct 13 2009 | Qualcomm Incorporated | Global secure service provider directory |
8453223, | Sep 23 2011 | Method, device and system for secure transactions | |
8453925, | Mar 02 2006 | VISA INTERNATIONAL SERVICE CORPORATION | Method and system for performing two factor authentication in mail order and telephone order transactions |
8458487, | Mar 03 2010 | OPEN TEXT HOLDINGS, INC | System and methods for format preserving tokenization of sensitive information |
8484134, | Mar 15 2001 | Liberty Peak Ventures, LLC | Online card present transaction |
8485437, | Dec 24 2007 | Dynamics Inc. | Systems and methods for programmable payment cards and devices with loyalty-based payment applications |
8494959, | Aug 17 2007 | EMC IP HOLDING COMPANY LLC | Payment card with dynamic account number |
8498908, | Dec 28 2007 | PayPal, Inc | Systems and methods for facilitating financial transactions over a network |
8504475, | Aug 10 2009 | Visa International Service Association | Systems and methods for enrolling users in a payment service |
8504478, | Dec 21 2007 | Liberty Peak Ventures, LLC | Systems, methods and computer program products for performing mass transit merchant transactions |
8510816, | Feb 25 2010 | SecureAuth Corporation | Security device provisioning |
8533860, | Jan 11 2013 | UNITED STATES DEPARTMENT OF THE TREASURY BUREAU OF THE FISCAL SERVICE | Personalized digital media access system—PDMAS part II |
8538845, | Jun 03 2011 | FINTIV, INC | Monetary transaction system |
8555079, | Dec 06 2011 | WWPass Corporation | Token management |
8566168, | Jan 05 2012 | T-MOBILE INNOVATIONS LLC | Electronic payment using a proxy account number stored in a secure element |
8567670, | Mar 27 2009 | Aura Sub, LLC | Dynamic card verification values and credit transactions |
8571939, | Jul 07 2010 | Toshiba Global Commerce Solutions Holdings Corporation | Two phase payment link and authorization for mobile devices |
8577336, | Nov 18 2010 | COM INVESTMENTS, LLC | System and method for transaction authentication using a mobile communication device |
8577803, | Jun 03 2011 | Visa International Service Association | Virtual wallet card selection apparatuses, methods and systems |
8577813, | Feb 21 2006 | Universal Secure Registry, LLC | Universal secure registry |
8578176, | Mar 26 2008 | PROTEGRITY US HOLDING, LLC | Method and apparatus for tokenization of sensitive sets of characters |
8583494, | Nov 30 2007 | BLAZE MOBILE, INC | Processing payments at a management server with user selected payment method |
8584251, | Apr 07 2009 | PRINCETON PAYMENT SOLUTIONS, LLC DELAWARE , WHOLLY-OWNED SUBSIDIARY OF FINANCIAL TRANSACTION SERVICES, LLC | Token-based payment processing system |
8589237, | Nov 30 2007 | BLAZE MOBILE, INC | Online purchase from a mobile device using a default payment method |
8589271, | Feb 04 2002 | ST ISIDORE RESEARCH, LLC | System and method for verification, authentication, and notification of transactions |
8589291, | Jun 25 2007 | Visa U.S.A. Inc. | System and method utilizing device information |
8595098, | Mar 18 2009 | NETWORK MERCHANTS, LLC | Transmission of sensitive customer information during electronic-based transactions |
8595812, | Dec 18 2009 | SABRE GLBL INC | Tokenized data security |
8595850, | Jan 30 2012 | MICRO FOCUS LLC | System for protecting sensitive data with distributed tokenization |
8606638, | Mar 02 2009 | First Data Corporation | Systems, methods and apparatus for facilitating transactions using a mobile device |
8606700, | Jun 25 2007 | VISA U.S.A., Inc. | Systems and methods for secure and transparent cardless transactions |
8606720, | Nov 13 2011 | GOOGLE LLC | Secure storage of payment information on client devices |
8615468, | Jan 27 2010 | CA, INC | System and method for generating a dynamic card value |
8620754, | Nov 30 2007 | BLAZE MOBILE, INC | Remote transaction processing using authentication information |
8635157, | Jul 19 2010 | PAYME, INC | Mobile system and method for payments and non-financial transactions |
8636203, | Dec 06 2005 | VISA U S A INC | Partial authorization of a financial transaction |
8646059, | Dec 17 2010 | GOOGLE LLC | Wallet application for interacting with a secure element application without a trusted server for authentication |
8651374, | Jun 02 2008 | TRANSFORM SR BRANDS LLC | System and method for payment card industry enterprise account number elimination |
8656180, | Dec 06 2011 | WWPass Corporation | Token activation |
8751391, | Mar 29 2002 | JPMORGAN CHASE BANK, N A | System and process for performing purchase transactions using tokens |
8762263, | Sep 06 2005 | Visa U.S.A. Inc. | System and method for secured account numbers in proximity devices |
8793186, | Sep 13 2007 | Visa U.S.A. Inc. | Account permanence |
8838982, | Sep 21 2011 | Visa International Service Association | Systems and methods to secure user identification |
8856539, | Mar 16 2001 | Universal Secure Registry, LLC | Universal secure registry |
8887308, | Mar 21 2010 | UNITED STATES DEPARTMENT OF THE TREASURY BUREAU OF THE FISCAL SERVICE | Digital cloud access (PDMAS part III) |
9065643, | Jun 26 2007 | VISA U S A INC | System and method for account identifier obfuscation |
9070129, | Sep 04 2007 | Visa U.S.A. Inc.; VISA U S A INC | Method and system for securing data fields |
9100826, | Feb 21 2006 | Universal Secure Registry, LLC | Method and apparatus for secure access payment and identification |
9160741, | Apr 17 2007 | Visa U.S.A. Inc. | Remote authentication system |
9229964, | Oct 27 2011 | Visa International Service Association | Database cloning and migration for quality assurance |
9245267, | Mar 03 2010 | Visa International Service Association | Portable account number for consumer payment account |
9249241, | Mar 27 2013 | UT-Battelle, LLC | Surface-functionalized mesoporous carbon materials |
9256871, | Jul 26 2012 | Visa U.S.A. Inc. | Configurable payment tokens |
9280765, | Apr 11 2011 | Visa International Service Association | Multiple tokenization for authentication |
9530137, | Feb 21 2006 | Universal Secure Registry, LLC | Method and apparatus for secure access payment and identification |
20010029485, | |||
20010034720, | |||
20010054003, | |||
20020007320, | |||
20020016749, | |||
20020029193, | |||
20020035539, | |||
20020035548, | |||
20020059146, | |||
20020073045, | |||
20020116341, | |||
20020128977, | |||
20020133467, | |||
20020147913, | |||
20020170960, | |||
20030028481, | |||
20030130955, | |||
20030158960, | |||
20030191709, | |||
20030191945, | |||
20040010462, | |||
20040050928, | |||
20040059682, | |||
20040093281, | |||
20040139008, | |||
20040143532, | |||
20040158532, | |||
20040159700, | |||
20040187012, | |||
20040203601, | |||
20040210449, | |||
20040210498, | |||
20040232225, | |||
20040260646, | |||
20050037735, | |||
20050065875, | |||
20050077349, | |||
20050080730, | |||
20050108178, | |||
20050184145, | |||
20050199709, | |||
20050246293, | |||
20050269401, | |||
20050269402, | |||
20060026098, | |||
20060085340, | |||
20060143101, | |||
20060175396, | |||
20060235795, | |||
20060237528, | |||
20060278704, | |||
20070022058, | |||
20070083444, | |||
20070100691, | |||
20070107044, | |||
20070129955, | |||
20070136193, | |||
20070136211, | |||
20070170247, | |||
20070179885, | |||
20070208671, | |||
20070245414, | |||
20070288377, | |||
20070291995, | |||
20080015988, | |||
20080029607, | |||
20080035738, | |||
20080052226, | |||
20080054068, | |||
20080054079, | |||
20080054081, | |||
20080065554, | |||
20080065555, | |||
20080126145, | |||
20080201264, | |||
20080201265, | |||
20080228646, | |||
20080243685, | |||
20080243702, | |||
20080245855, | |||
20080245861, | |||
20080275779, | |||
20080283591, | |||
20080302869, | |||
20080302876, | |||
20080306876, | |||
20080313264, | |||
20090006262, | |||
20090010488, | |||
20090037333, | |||
20090037388, | |||
20090043702, | |||
20090048971, | |||
20090106112, | |||
20090106160, | |||
20090134217, | |||
20090157555, | |||
20090159673, | |||
20090159700, | |||
20090159707, | |||
20090173782, | |||
20090200371, | |||
20090248583, | |||
20090276347, | |||
20090281948, | |||
20090294527, | |||
20090307139, | |||
20090308921, | |||
20090327131, | |||
20100008535, | |||
20100088237, | |||
20100094755, | |||
20100106644, | |||
20100120408, | |||
20100133334, | |||
20100138347, | |||
20100145860, | |||
20100161433, | |||
20100185545, | |||
20100211505, | |||
20100223186, | |||
20100228668, | |||
20100235284, | |||
20100258620, | |||
20100291904, | |||
20100299267, | |||
20100306076, | |||
20100325041, | |||
20110010292, | |||
20110016047, | |||
20110016320, | |||
20110040640, | |||
20110047076, | |||
20110083018, | |||
20110087596, | |||
20110093397, | |||
20110125597, | |||
20110153437, | |||
20110153498, | |||
20110154466, | |||
20110161233, | |||
20110178926, | |||
20110191244, | |||
20110238511, | |||
20110238573, | |||
20110246317, | |||
20110258111, | |||
20110272471, | |||
20110272478, | |||
20110276380, | |||
20110276381, | |||
20110276424, | |||
20110276425, | |||
20110295745, | |||
20110302081, | |||
20120023567, | |||
20120028609, | |||
20120030047, | |||
20120035998, | |||
20120041881, | |||
20120047237, | |||
20120066078, | |||
20120072350, | |||
20120078735, | |||
20120078798, | |||
20120078799, | |||
20120095852, | |||
20120095865, | |||
20120116902, | |||
20120123882, | |||
20120123940, | |||
20120129514, | |||
20120143767, | |||
20120143772, | |||
20120158580, | |||
20120158593, | |||
20120173431, | |||
20120185386, | |||
20120197807, | |||
20120203664, | |||
20120203666, | |||
20120215688, | |||
20120215696, | |||
20120221421, | |||
20120226582, | |||
20120231844, | |||
20120233004, | |||
20120246070, | |||
20120246071, | |||
20120246079, | |||
20120265631, | |||
20120271770, | |||
20120297446, | |||
20120300932, | |||
20120303503, | |||
20120303961, | |||
20120304273, | |||
20120310725, | |||
20120310831, | |||
20120316992, | |||
20120317035, | |||
20120317036, | |||
20130017784, | |||
20130018757, | |||
20130019098, | |||
20130031006, | |||
20130054337, | |||
20130054466, | |||
20130054474, | |||
20130081122, | |||
20130091028, | |||
20130110658, | |||
20130111599, | |||
20130117185, | |||
20130124290, | |||
20130124291, | |||
20130124364, | |||
20130138525, | |||
20130144888, | |||
20130145148, | |||
20130145172, | |||
20130159178, | |||
20130159184, | |||
20130166402, | |||
20130166456, | |||
20130173736, | |||
20130185202, | |||
20130191286, | |||
20130191289, | |||
20130198071, | |||
20130198080, | |||
20130200146, | |||
20130204787, | |||
20130204793, | |||
20130212007, | |||
20130212017, | |||
20130212019, | |||
20130212024, | |||
20130212026, | |||
20130212666, | |||
20130218698, | |||
20130218769, | |||
20130226799, | |||
20130226813, | |||
20130246199, | |||
20130246202, | |||
20130246203, | |||
20130246258, | |||
20130246259, | |||
20130246261, | |||
20130246267, | |||
20130254028, | |||
20130254052, | |||
20130254102, | |||
20130254117, | |||
20130262296, | |||
20130262302, | |||
20130262315, | |||
20130262316, | |||
20130262317, | |||
20130275300, | |||
20130275307, | |||
20130275308, | |||
20130282502, | |||
20130282575, | |||
20130282588, | |||
20130297501, | |||
20130297504, | |||
20130297508, | |||
20130304649, | |||
20130308778, | |||
20130311382, | |||
20130317982, | |||
20130332344, | |||
20130339253, | |||
20130346314, | |||
20140007213, | |||
20140013106, | |||
20140013114, | |||
20140013452, | |||
20140019352, | |||
20140025581, | |||
20140025585, | |||
20140025958, | |||
20140032417, | |||
20140032418, | |||
20140040137, | |||
20140040139, | |||
20140040144, | |||
20140040145, | |||
20140040148, | |||
20140040628, | |||
20140041018, | |||
20140046853, | |||
20140047551, | |||
20140052532, | |||
20140052620, | |||
20140052637, | |||
20140068706, | |||
20140074637, | |||
20140108172, | |||
20140114857, | |||
20140143137, | |||
20140164243, | |||
20140188586, | |||
20140294701, | |||
20140297534, | |||
20140310183, | |||
20140330721, | |||
20140330722, | |||
20140331265, | |||
20140337236, | |||
20140344153, | |||
20140372308, | |||
20150019443, | |||
20150032625, | |||
20150032626, | |||
20150032627, | |||
20150046338, | |||
20150046339, | |||
20150052064, | |||
20150088756, | |||
20150106239, | |||
20150112870, | |||
20150112871, | |||
20150120472, | |||
20150127529, | |||
20150127547, | |||
20150140960, | |||
20150142673, | |||
20150161597, | |||
20150178724, | |||
20150180836, | |||
20150186864, | |||
20150193222, | |||
20150195133, | |||
20150199679, | |||
20150199689, | |||
20150220917, | |||
20150269566, | |||
20150312038, | |||
20150319158, | |||
20150332262, | |||
20150356560, | |||
20160028550, | |||
20160042263, | |||
20160065370, | |||
20160092696, | |||
20160092872, | |||
20160119296, | |||
20160224976, | |||
20170046696, | |||
20170103387, | |||
20170220818, | |||
20170228723, | |||
EP2156397, | |||
KR1020060022304, | |||
KR1020060111200, | |||
KR20030020189, | |||
RE40444, | Dec 29 1998 | PayPal, Inc | Four-party credit/debit payment protocol |
RE43157, | Sep 12 2002 | Liberty Peak Ventures, LLC | System and method for reassociating an account number to another transaction account |
WO188785, | |||
WO3075192, | |||
WO2001035304, | |||
WO2004042536, | |||
WO2005073931, | |||
WO2006113834, | |||
WO2009032523, | |||
WO2010078522, | |||
WO2012068078, | |||
WO2012098556, | |||
WO2012142370, | |||
WO2012167941, | |||
WO2013048538, | |||
WO2013056104, | |||
WO2013119914, | |||
WO2013179271, | |||
WO3083793, | |||
WO2006023839, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
May 29 2012 | Visa International Service Association | (assignment on the face of the patent) | / |
Date | Maintenance Fee Events |
Jan 19 2022 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Date | Maintenance Schedule |
Aug 07 2021 | 4 years fee payment window open |
Feb 07 2022 | 6 months grace period start (w surcharge) |
Aug 07 2022 | patent expiry (for year 4) |
Aug 07 2024 | 2 years to revive unintentionally abandoned end. (for year 4) |
Aug 07 2025 | 8 years fee payment window open |
Feb 07 2026 | 6 months grace period start (w surcharge) |
Aug 07 2026 | patent expiry (for year 8) |
Aug 07 2028 | 2 years to revive unintentionally abandoned end. (for year 8) |
Aug 07 2029 | 12 years fee payment window open |
Feb 07 2030 | 6 months grace period start (w surcharge) |
Aug 07 2030 | patent expiry (for year 12) |
Aug 07 2032 | 2 years to revive unintentionally abandoned end. (for year 12) |