System, method, and apparatus for smart card pin management via an unconnected reader

A system of changing the PIN associated with a smart card is described. A user can initiate the PIN change using a personal unwired smart card reader, rather than using a system, such as an ATM machine. The smart card reader, loaded with the smart card provides a cryptogram code, which can contain the user's requested new PIN or it can be provided to the issuer via alternative methods. Via various methods the cryptogram code is delivered to the card issuer's PIN change management system, including the user transposing the code from smart card reader screen to the card issuer's web site or audio DTMF transmission from the smart card reader speaker to the card issuer IVR system. Returned from the issuer, via a similar path, will be a command code that when processed by the smart card reader will result in a PIN change on the smart card.

RELATED APPLICATION

The Application is related to U.S. patent application Ser. No. 12/479,490, entitled SMART CARD PIN MANAGEMENT VIA AN UNCONNECTED READER, filed Jun. 5, 2009, which is incorporated by reference in its entirety for any and all purposes.

BACKGROUND OF THE INVENTION

Adoption of smart cards technology into financial payment card that allow a user to purchase goods or services have become prevalent around the world. Access to the smart card technology requires a special terminal (sometimes referred to a smart card readers) which provide multi-point connections to the smart card to deliver power to the smart card chip and provide communications between terminal and the card. Smart cards contain the same data as might be found on the Magnetic Strip plus additional risk management and typically the user's personal identification number (PIN).

A security feature of smart cards is that they are able to verify the PIN directly on the smart card chip. In order to achieve this ‘offline’ PIN verification the card needs to be loaded with the PIN. The PIN is typically selected by the Issuer at issuance of the card, or carried forward from the previously issued card, and if required the user is advised of the selected PIN by the Issuer.

With several accounts or smart cards, the user may have several PINs. The number of PINs can become difficult to remember, or the user may confuse which PIN is associated with a smart card or account. It has become apparent that a method to allow the user to select and manage their card's PIN is important. Unfortunately, smart cards are technically difficult to modify, and relies on a real-time two-way communication between the smart card and the Issuer. To date the methods available to change the PIN has been either 1) the user using the Issuers automated teller machine (ATM) or an ATM operated by a partner of the Issuer, or 2) A PIN change device directly connected to the Issuers network, typically located within an Issuer facility. Thus, to change the PIN, the Issuer has to provide services and systems to support PIN change and the user needs to travel to such a device. For many users this is not possible or practical due the Issuer not providing such services or those services being located too far away for the user to use.

BRIEF SUMMARY OF THE INVENTION

Embodiments presented herein are generally directed to a system where a user can perform a PIN change to a smart card supplied by an Issuer thought a smart card reader without a real-time connection to the Issuer's network. The user can execute a PIN change to their smart card without requiring the smart card to be inserted into networked Issuer device. Instead the user inserts their smart card into a stand-alone smart card reader device, which produces a cryptogram for the Issuer's PIN change management system and waits for a response cryptogram in order to complete the PIN change execution.

The PIN change management system can also include additional messages for the smart card such as unblock locked smart cards or setting risk management parameters on the smart card.

The new PIN value is embedded within the response cryptogram from the Issuer's PIN change management system.

The supply of the PIN to the PIN change management system can be conducted by several methods, and is out of scope of this invention. However for the purpose of providing a complete view of the PIN change process the method of PIN update explained thought the rest of this document is based on the User providing the new PIN to the smart card reader for embedding within the cryptogram generated by the smart card/card reader and provided to the Issuer PIN change management system. Privacy and integrity is managed purely by the smart card, the smart card reader device providing process flow to the smart card reader and communications interfaces.

With the smart card inserted into the smart card reader, the User is prompted to enter the new PIN value into the smart card reader device. The smart card is prompted, by way of a payment transaction, to create a cryptogram using data including the new PIN by the smart card reader. The smart card reader converts the resultant cryptogram into a form suitable for transmission. Examples of the cryptogram transmission include: 1) Compacting and decimalization, and displayed to User, 2) Audio DTMF encoding via device speaker. The User now has the task of providing the cryptogram data to the Issuer via methods such as: 1) Entry of data on to web page, 2) Telephone connection, 3) Email, and 4) SMS text message. Issuer's PIN management systems utilizes cryptogram and the new PIN along with user account information known to the system to build PIN change smart card command, generally in the form of a smart card instruction, command, encrypted data and integrity cryptogram. The PIN change command is converted into a form suitable for transmission.

Further, utilizing the cryptogram, smart card details and cryptographic keys the PIN management system can revival the new PIN and build a PIN change command code. On return of the PIN change command code to the smart card reader, the smart card reader formats and transmits the code as a smart card command (APDU) to the smart card which decrypts and processes the instruction from the PIN management system as a PIN change.

For the transfer of the PIN change command code from the PIN management system to the remote smart cards reader, such as the user transposing the code from an Issuer hosted web page, as an audibly encoded data stream, such as DTMF codes interpreted by the smart cards reader's microphone, and the Issuer hosted web page displaying the codes as a sequence of flashing lights interpreted by the smart cards reader's optical interface. Where the smart card reader repackages and sends the supplied data into the appropriate smart card commands. The success of the smart card processing would be returned to the User for reassurance purposes.

In addition to PIN change the solution described can also unblock smart cards where the user has entered the PIN incorrectly too many times, resenting the PIN to the same value or a new value. Once the PIN change command has been processed by the smart card the user can continue use of their smart card with the PIN changed and/or unblocked.

DETAILED DESCRIPTION OF THE INVENTION

Embodiments of the disclosure generally relate to systems and methods for managing a user's PIN associated with the user's smart card. In embodiments, a user supports the communication between an issuer's PIN management system and the smart card/smart card reader device. The communications used by can be can be the Internet or other public or private network, such as a feature provided on the Issuer's web site, telephone, text messaging, email or other open channel open between the User community and the Issuer.

The user communicates with a smart card reader at the user's facility. A user instructs the smart card reader to complete a PIN change for a smart card. The smart card reader reads information from the smart card. Further, the user can enter information into the smart card reader, for example, the new PIN. A message is created using the information from the smart card and the information from the user. In embodiments, the message is a seed to support the request to change the PIN. The message can include the new PIN requested, or the new PIN could be made available to the Issuer's PIN management system via other channels. The user supports the forwarding of the message to the PIN management system.

Generally, current systems do not have the ability to send the PIN change request though channels other than an open connection between the system of the Issuer and the smart card reader.

The PIN management system can be software at a card issuer or a separate system in communication with the card issuer. The PIN management system can receive the message from the user and send the PIN change request over a private network to the card issuer. The card issuer can receive the request message and authenticate the user with the information in the PIN change request message, such as a flag indicating the smart card has verified the current PIN. Other out of bound user authentication methods could be used such as username and password. If authenticated, the card issuer uses the provided cryptogram to build a PIN change command and sends a message back containing the PIN change command back to the user. The user can forward the response command to the smart card read, which changes the PIN information on the smart card. With this system, the user can manage the PIN and unblock their smart card without having to use an ATM or bank system to change the PIN.

The embodiments here are for use with existing smart card PIN change protocols such as those defined in EMVCo LLC specifications (EMV v4.2 Book 3 section 6.5.10). To communicate the PIN change command, the PIN management system may create an authorization message encoded to include the PIN change command.

Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits may be shown in block diagrams in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments. In some embodiments, a computing system may be used to execute any of the tasks or operations described herein. In embodiments, a computing system includes memory and a processor and is operable to execute computer-executable instructions stored on a computer-readable medium that define processes or operations described herein.

The usage of the user to assist in the transfer of data between the Issuer systems and the smart card device includes, but is not limited to, web site entry and display, audio transmission of codes, visually/optical transmission of codes.

Furthermore implementations may be designed to link the Issuer systems and the smart card device via the use of a personal computer connected to the internet or other such public network, removing the user responsibility of data transfer. In such as case the user104will be replaced by a personal computer operated by the user.

An embodiment of a system100for providing management of a user's PIN on a smart card114is shown inFIG. 1. A user104will communicate with a smart card reader102. The smart card reader102is a system or device having hardware and/or software that can communicate with a smart card. A smart card114is a device confirming the ISO 7816 and/or ISO 14443 specifications or future specification of a similar nature. The smart card reader102, in embodiments, can include or be in communication with a user interface106that allows the user to enter information into or receive information from the smart card reader102. Optical interface118can be included to allow data to be interpreted by the smart card reader102from an optical source being a static image or a moving image sequence. Audio interface116may comprise of a speaker and/or microphone to enable data to transferred as audible signals such as, but not limited to DTMF tones.

In embodiments, the user104is operable to receive communications from and send communications to the smart card reader102. Further, the user104is operable to receive communications from and send communications to a PIN management system108. In embodiments, the user104communicates with the PIN management system108via an Issuer portal112. The portal is a public network, for example, a web site on the Internet, telephone system available via a published number or email address provided to the user. The user104may be a supported by devices such as a laptop computer, a desktop computer, a mobile phone, a cellular device, a personal digital assistant with communication capability, etc. In alternative embodiments, one or more portions of the portal112between the user104and the PIN management system108include wired or wireless media, for example, a LAN, WAN, the Internet, a telephone system, etc.

The PIN management system108, in embodiments, is part of the card issuer110or a physically separate entity that processes PIN management requests on behalf of a card issuer110desiring to allow PIN changes over a public network. The PIN management system108may communicate PIN change requests and receive PIN change commands for a card issuer. In other embodiments, the PIN management system108may be a function of the card issuer110, for example, a bank, that processes credit or debit authorization requests without a separate outside entity. The PIN management system108may have a predefined relationship with the card issuer110that issued the smart card114, such that the PIN management system108communicates requests and receives commands over a private network between the PIN management system108and the card issuer110.

Turning now toFIG. 2, which illustrates a smart card reader and a PIN management system for use in a system for managing a user's PIN. The PIN engine234can verify the current PIN and instructs the smart card231to change to the new PIN when received. A PIN engine can receive the new PIN or request to change the PIN from the user interface224through the Message creator228. To verify the old PIN or change to the new PIN, the PIN engine234communicates with the smart card interface233. The PIN engine234reads the messages from the smart card231to extract information for generating the messages for the smart card231. The message creator228is either hardware, software, or both hardware and software that builds condenses and formats messages to and from the PIN management system222. The message creator228receives the PIN change information from the PIN engine234. In embodiments, the message creator228prepares the cryptogram or other specially designed message for presentation to the user200on the user interface224or output via the audio interface226. The user may copy the message from the user interface display into another application to send to the PIN management system222. In other embodiments, the message creator228automatically sends the message through the user200to the PIN management system222. The message can be a PIN change request message that includes the new PIN and is recognized as a PIN change request. Authentication of the user to the PIN management system is out of bounds but could include the current PIN validation performed by the smart card231.

The portal interface236is operable to communicate with the user200or user200's computer. The portal interface236may be any technology or system that can complete communications, such as a web site, telephone, IVR, email, text messaging, TCP/IP or other technology.

The authentication module240, in embodiments, is a module that authenticates the smart card user using the information sent from the user200optionally with information sent from the smart card23. The authentication information may include one or more of, but is not limited to, the user's name, the user's account number, the user's PIN, a password, a user-selected logon name, or another identifier for the user or the smart card. Thus, the authentication module240is operable to extract this information from the communication from the user200and authenticate the information to ensure the authenticity of the transaction. In alternative embodiments, the authentication module240is part of the HSM246. If an authentication is unsuccessful, a signal may be sent to the user200.

The Message processor242can receive a signal from the authentication module240that the information in the transaction is validated includes additional data from the User Data241that will be required by the Message processor242to complete its task.

One or more data structures used to store information in one or more components or transport information between the smart card231, smart card reader202, the user200, and the PIN management system222are shown inFIGS. 3A-C.

The data structure field300FIG. 3A, in embodiments, includes one or more fields used in typical PIN change request messages; the fields may include, but are not limited to, Transaction Date/Time (310), Terminal Country Code (312), Transaction Currency Code (314), Transaction Amount (316). The precise details required to be provided by the smart card reader102to the smart card114are defined by the developer of the smart card.

The transaction details field300includes one or more fields containing information about the “pseudo transaction.” The transaction details field300represents a pseudo transaction because the message, while formatted like a PIN change request message, is encoded to be a PIN change request message. As such, the transaction details field300may contain fields similar to a typical PIN change request message but may contain data representative of a PIN change request. The amount field316would typically contain the price being authorized for the transaction. For example, if the total for the transaction was $46.00, this amount would be entered in the amount field316. Additional data elements may be required to be provided to the smart card as represented by the ellipses318.

To provide the new PIN, the new PIN is entered into one of the fields of the transaction details field300. In embodiments, the new PIN is entered into the amount field316. As such, rather than containing an amount of a transaction, the amount field316includes the new PIN and can be recognized as having the new PIN. In one embodiment, all zeroes, other null values, or value determined form the smart card are entered into at least a portion or one or more data fields in the transaction details field300. For example, all zeroes are entered into the Transaction Date field310, Transaction Time field312. In another embodiment, a predetermined code is entered into one or more fields. For example, the Terminal Country Code field314will contain a value previously known the smart card reader102by interrogation of the smart card114.

FIG. 3Billustrates transaction details307, which includes encrypted elements and can be decrypted by holder of the cryptographic key, generally restricted to the card issuer or the card issuer's service providers. In alternative embodiments, the transaction details307include one or more unencrypted items. In still other embodiments, the transaction details307include both encrypted and unencrypted copies of portions of the transaction details300along with other internal smart card data, such as Response Type ID322, Transaction Counter324, and Optional Data330. Encryption also prevents a nefarious individual from having access to the PIN change request information, which could allow smart card transactions to altered or fraudulent transactions to be generated. In other embodiments, the cryptogram328is encrypted and can only be decrypted by holder of the cryptographic key, generally restricted to the card issuer or the card issuer's service providers.

In further embodiments,FIG. 3Cincludes a PIN management system user smart card reader response308. In one embodiment the smart card reader response may include a number of blocks field, blocks1to n, and a checksum field. However, other fields may be included.

An embodiment of a method400executed at a smart card reader202for generating a cryptogram request that is included with the PIN change request is shown inFIG. 4. In embodiments, the method400generally begins with a START operation402and terminates with an END operation418. The steps shown in the method400may be executed in a computer system or other electronic device as a set of computer-executable instructions. While a logical order is shown inFIG. 4, the steps shown or described can, in some circumstances, be executed in a different order than presented herein. Further, the steps shown inFIG. 4may only be a subset or may be substituted for other steps not shown inFIG. 4. The method400ofFIG. 4will be explained with reference to the drawings inFIGS. 1-3C.

The smart card reader202receives a request to change the PIN for a smart card114in step404. In embodiments, the user interface224of the smart card reader receives a selection of a PIN change, for example, a button or menu selection.

The smart card reader202may then prompt the user for a new PIN. Entry of the new PIN is not required if the user wishes to provide the new PIN via other channels or does not wish to change the PIN purely unblock the smart card that has locked due to too many failed PIN entries. The new PIN may be input into user interface224. In another embodiment, the user provides the new PIN to the PIN management system via alternative methods including but not limited to clear text entry on to the card issuer's PIN entry web page, via DTMF tones into the PIN management system IVR interface, via SMS text message to the PIN management systems SMS interface, acceptance of a randomly generated PIN, or acceptance of a PIN from a selection of randomly generated PINs shared with the user on the Issuer's web page, where the user needs to make a selection either directly on the web site or entering the selection PIN identification number in to the user interface224. The PIN or indication of chosen PIN, if locally entered, is sent to the message creator228and/or the PIN engine234. The smart card reader202interacts with the smart card231. In response to the request, the message creator228can direct the PIN engine234to extract information from the smart card231. The PIN engine234sends the information request to the smart card interface233which interacts with the smart card231.

The smart card reader202may then prompt the user for a current PIN. Entry of the current PIN is not required as it may no longer be known to the user. Step406, receive and validate current PIN, is auctioned if the user wishes to enter the current PIN, via user interface224then the current PIN is sent to the message creator228and/or the PIN engine234. The smart card reader202interacts with the smart card231. In response to the request, the message creator228can direct the PIN engine234to extract information from the smart card231. The PIN engine234sends the information request to the smart card interface233which interacts with the smart card231.

Entering the current PIN onto a smart card capable of validating the user PIN offline enables the smart card cryptogram328to indicate to the PIN management system the successfully authentication of the user. In other embodiments the current PIN is included into the cryptogram328enabling the transport of the encrypted current PIN to be transferred to the PIN management system for authentication of the user. In furthermore embodiments the authentication of the user is conducted via alternative methods by the PIN management system including but not limited to user credential validated via online banking username and password onto a card issuer web site.

A cryptogram, PIN, or other information is acquired in step408. In embodiments, the smart card interface233acquires the information from the smart card231and sends the information to the Message creator228.

The PIN change request message is created in step410. The PIN change request message one or more multiple purposes, including but not limited to, enter the smart card into a state ready to accept PIN change and/or other parameter management commands, to generate a seed needed by the PIN management system to preparing a PIN change command and/or other parameter management commands, to enable sensitive data to be securely transfer from the smart card to the PIN management system, and to allow the PIN management system to qualify if the current PIN has been verified by the smart card. The PIN change request message can include the cryptogram(s) and/or other data received from the smart card231.

The Message creator228generates a code in step412and formats the data into a format suitable for transmission, via the User interface224and/or audio interface226. Depending on the transmission method of the PIN change request message to the PIN management system various encoding methods can be used, such as but not limited to, DTMF tones in order for the message data to be transmitted and received by the PIN management system, or compacting in order to reduce the amount of data transferred and format the data into a limited range of characters such as but not, limited to 0 . . . 9(decimal), 0 . . . 9+A . . . Z (numeric plus uppercase letters), 0 . . . 9+A . . . Z+a . . . z (numeric, uppercase letters plus lowercase letters), all standard keyboard characters (for example ASCII characters codes 0x21 . . . 0x7E inclusive).

The Message creator228may build the cryptogram generation command to the smart card231utilizing zeroes or other predetermined codes into one or more of the fields of the cryptogram request message, as explained in conjunction withFIG. 3A. Further, the Message creator228can write data for secure transmission to the PIN management system, such as the new PIN received from the user and/or the current PIN, into the cryptogram request message in step414. For example, the Message creator228enters the new PIN in the amount field316of the cryptogram request message as explained in conjunction withFIG. 3A. The smart card reader202sends or forwards the cryptogram request message in step416. The PIN change request message can be sent by the user interface224or the audio interface226to be sent to the PIN management system222.

An embodiment of a method500executed at a PIN management system222for processing a PIN change request and generating PIN change command for a smart card231is shown inFIG. 5. In embodiments, the method500generally begins with a START operation502and terminates with an END operation520. The steps shown in the method500may be executed in a computer system as a set of computer-executable instructions. While a logical order is shown inFIG. 5, the steps shown or described can, in some circumstances, be executed in a different order than presented herein. Further, the steps shown inFIG. 5may only be a subset or may be substituted for other steps not shown inFIG. 5. The method500ofFIG. 5is explained with reference to the drawings inFIGS. 1 and 2.

The PIN change management system222receives a PIN change request message in step504. The PIN change request message can be as described in conjunction withFIGS. 3B and 3C. The portal interface236may receive web requests from the user200having a PIN change request message. In other embodiments the portal interface236may receive messages as DTMF signals. In further embodiments the portal interface236may receive TCP/IP message from a front-end computer.

The Authentication module240reads the PIN change request message in step504. The Authentication module re-formats where the PIN change request is based on a compacted to reformulate the fully formed cryptogram and any other associated data. In embodiments where the PIN is not provided via the PIN change request message, new PIN will have been previously agreed and will be retrieved by the Authentication module240from the User Data241.

Utilizing the information attained previously, such as the user's account number and data in the PIN change request message the Authentication engine240determines the validity of the cryptogram any other associated data. At step506, the user account details are looked up. At step508the Authentication module240may determine if the user has been authenticated by the smart card231or conduct user authentication with the current PIN cryptographically embedded within the PIN change request message. In other embodiments and if the users has no knowledge of their current PIN, the Authentication module will ensure satisfactory methods of user authentication are or have been conducted.

The Message processor242can read the new PIN in the Amount field316in step510. In other embodiments, when the new PIN is not provided via the PIN change request message, the new PIN will be provided to the Message processor242from the Authentication module240. The Message processor242may validate that the new PIN against the card issuer's weak PIN rules and reject PIN change requests determined to be weak at step512. If the PIN is determined to be weak (or otherwise unsuitable), at step514the user is informed that the selected PIN is unsuitable. Otherwise the process continues to step516.

The Message processor242will build a PIN change message. The new PIN along with additional user smart card data, such as Account Number, Transaction Counter and Cryptographic Key(s) will be processed typically with the support of a Hardware Security Module (HSM)246to create a smart card update command (APDU).

When the PIN change command has been generated (at step516) the Message processor242will format and/or compact the message, according to the communication channel being utilized, ready for transmission to the user200. The PIN management system222sends or forwards the PIN change message to the user200for onward transport to the smart card reader202in step518. In embodiment the utilize optical or audible DTMF tones for data transmission the Portal interface236will prompt the user200for correct placement of the smart card reader202, upon instruction from the user200the transmission of the PIN change message will be started.

An embodiment of a method600executed at a smart card reader202for identifying a PIN change command and changing a PIN for a smart card231is shown inFIG. 6. In embodiments, the method600generally begins with a START operation602and terminates with an END operation610. The steps shown in the method600may be executed in a computer system as a set of computer-executable instructions. While a logical order is shown inFIG. 6, the steps shown or described can, in some circumstances, be executed in a different order than presented herein. Further, the steps shown inFIG. 6may only be a subset or may be substituted for other steps not shown inFIG. 6. The method600ofFIG. 6will be explained with reference to the drawing inFIG. 1.

The smart card reader202will remain in a state awaiting a response from the PIN management system, the user200to manually cancel the procedure or a timeout event. At step604receipt of a PIN change message occurs. The PIN change message can be as described in conjunction withFIGS. 3A-3C. The user interface224will receive a message from the PIN management system222, via the user200, conforming to a PIN change message. Other embodiments utilize the optical and/or audio interface226to receive the message from the PIN management system222.

The message creator228will package the PIN change message into a smart card command for processing by the smart card interface233and smart card231. In other embodiments the PIN change message from the PIN management system will include parameter management commands for the user's smart card, in these cases the Message creator228will packing the data into one or more smart card commands in addition to or instead of a PIN change command. At step606, the new PIN is read, and then at step608the PIN change command is executed.

An embodiment of a method700executed at a smart card reader202(FIG. 2B) for processing a PIN change request is shown inFIG. 7. In embodiments, the method700generally begins with a START operation702and terminates with an END operation716. The steps shown in the method700may be executed in a computer system as a set of computer-executable instructions. While a logical order is shown inFIG. 7, the steps shown or described can, in some circumstances, be executed in a different order than presented herein. Further, the steps shown inFIG. 7may only be a subset or may be substituted for other steps not shown inFIG. 7. The method700ofFIG. 7will be explained with reference to the drawings inFIG. 1.

The user200receives a request to change the PIN for a smart card114in step704. In embodiments, the user interface224receives a selection of a change PIN user interface device, for example, a button or other icon in a window. The user200interacts with the smart card reader202in step706. The user200may also initiate a PIN change program to change the PIN of the smart card231.

The user may be asked for a new PIN and a new PIN may be received in step709. The new PIN may be input into the PIN change program and communicated to smart card reader202. The user computer can receive a PIN change message created by the smart card reader202in step708. The PIN change message can be a cryptogram or other indecipherable message presented to the user200from the smart card reader202. The user may copy the message (the cryptogram) from the user interface window of a PIN change program to a web page or other user interface window. Then, the user200can forward the PIN change message300to the PIN management system222in step710.

The user200can receive a response message320from the PIN management system222in step712. The response message307may be another indecipherable message that the user copies from the user interface window of a web page or other program to the user interface window of the PIN change program. The user200may then forward the response message307to the smart card reader202in step714.

In other embodiments, the user200generates the PIN change message after receiving the new PIN in709. In this embodiment, the smart card reader202may send information to the user200to generate the PIN change message. The user200may also authenticate with the authentication module208before interacting with the smart card reader202in step706. To authenticate, the user200may request information that can be checked against stored information at the PIN management system database241.

An embodiment of a method800executed at a smart card reader202for changing a PIN for a smart card231is shown inFIG. 8. In embodiments, the method800generally begins with a START operation802and terminates with an END operation818. The steps shown in the method800may be executed in a computer system as a set of computer-executable instructions. While a logical order is shown inFIG. 8, the steps shown or described can, in some circumstances, be executed in a different order than presented herein. Further, the steps shown inFIG. 8may only be a subset or may be substituted for other steps not shown inFIG. 8. The method800ofFIG. 8will be explained with reference to the drawings inFIG. 1.

The smart card reader202receives a request to change the PIN associated with the smart card231in step804. In an embodiment, the user200sends a request to the user interface224that the user desires to change the PIN. In another embodiment, the user inputs the request to change the PIN into a user interface. The request is sent to the message creator228and/or the PIN engine234. The smart card reader202interacts with the smart card231in step806. In response to the request, the message creator228can direct the PIN engine234to extract information from the smart card231. The PIN engine234sends the information request to the smart card interface233which interacts with the smart card231.

A cryptogram, PIN, or other information is acquired in step808. In embodiments, the smart card interface233acquires the information from the smart card231and sends the information to the PIN engine234. The PIN engine234can store the information. The PIN engine234may create the cryptogram with the information from the smart card231. A message is created in step810. The message may be the cryptogram or include the cryptogram. In embodiments, the message is the same or similar to data structure300. A user may provide the new PIN as an input to the user interface, which is received through the user interface224. The message may be created by the message creator228with information provided by the PIN engine234. The smart card reader202forwards the message in step812.

A response message may be received by the smart card reader202in step814. The response message may be the same or similar to message307. The message creator228can then receive the message and extract the PIN change command for the PIN engine234. The PIN engine234commands the smart card231to change the PIN in step816. The PIN change command is sent to the smart card231through the smart card interface233. A PIN change is made at the smart card231in accordance with the PIN change command. In embodiments, the smart card231stores the new PIN.

An embodiment of a method900executed at a PIN management system222and/or a card issuer246is shown inFIG. 9. In embodiments, the method900generally begins with a START operation902and terminates with an END operation912. The steps shown in the method900may be executed in a computer system as a set of computer-executable instructions. While a logical order is shown inFIG. 9, the steps shown or described can, in some circumstances, be executed in a different order than presented herein. Further, the steps shown inFIG. 9may only be a subset or may be substituted for other steps not shown inFIG. 9. The method900ofFIG. 9will be explained with reference to the drawings inFIG. 1.

The PIN change management system222receives a PIN change message in step904. The portal interface236may receive a TCP/IP message from the user computer200having a PIN change cryptogram included in the message. In embodiments, the message is the same or similar to message300.

To verify the user and/or the message, the authentication module240can authenticate the message or user in step906. Authentication may include verifying a checksum or code embedded in the message or verifying information provided in the message with information stored in the user database241. If the message is not authenticated, an error message may be sent to the user200. The user200can attempt to resend the message. If the authentication fails for a predetermined number of messages, for example, three messages, the PIN management system222may prevent the PIN change by refusing further PIN change requests. If the message and/or user is authenticated, the message processor242of the PIN change management system222can generate a message to be sent to the card issuer system246.

In other embodiments, the PIN management system222coverts the received message and send the message to the card issuer246. For example, the received message may be a web-based message, and the message is converted to a format or protocol for sending to the card issuer, such as over an ACH network.

The message creator228generates the change PIN message in step908. The PIN change message may be the same or similar to the message308described in conjunction withFIG. 3C. Information for the message may include a second cryptogram that represents a PIN change command, the new PIN, and other information. A PIN engine234can create the information. The PIN engine234can also change the PIN in step910. The message can be sent though the ACH/Proprietary network interface and through the PIN management system222or through a network portal236to the user200. Thus, the PIN change command is sent to the user200without sending the message through the PIN management system222.

Embodiments of the different systems represented in this disclosure, which may include the PIN management system222, the user's200computer, and/or the smart card reader202, may be a computer system, such as computer system1000shown inFIG. 10. While a basic computer system is shown, one skilled in the art will recognize the configuration changes and/or modifications that may be required to make operable the systems (e.g. smart card reader202, PIN management system222, etc.) described herein. The computer system1000comprises a processor1002, which completes the operations described in conjunction withFIGS. 4 through 9or makes the systems operable described in conjunction withFIG. 1. Further, the computer system1000can execute functions in response to receiving the data structures described inFIGS. 3A-3C. The processor1002may be any type of processor operable to complete the operations or implement the systems described herein. For example, the processor1002may be an Intel Pentium processor, an ASIC, an FPGA, or other device.

The computer system1000also comprises memory1004to hold data or code being executed by processor1002. The memory1004may permanently or temporarily store the instructions described in conjunction withFIGS. 4 through 9or the data elements described in conjunction withFIGS. 3A-3C. Memory may be classified as a computer-readable medium, for example, RAM, ROM, magnetic media, optical media, etc.

The computer system1000also can comprise software elements, including an operating system and/or other code, such as one or more application programs for authorizing contactless payments at any of the PIN management system222and/or the smart card reader202. The application programs may comprise computer programs described herein, and/or may be designed to implement methods described herein and/or configure systems described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed in conjunction withFIGS. 4-7might be implemented as code and/or instructions executable by the computer system1000(and/or the processor1002within the computer system1000).

Further embodiments of the computer system1000comprise input/output (I/O) modules of systems1006. I/O systems1006may include displays such as LCDs, plasma screen, cathode ray tubes, etc. The displays can provide a visual representation of data to a user. I/O system1006may also include input devices such as mice, keyboards, touch screens, etc. Input devices allow the user to input information into the computer system. I/O systems1006may also comprise communication systems such as wired, wireless, or other communication systems. Further, communication systems may communicate with peripheral devices, such as printers, modems, or other devices.

In light of the above description, a number of advantages of the present invention are readily apparent. For example, the systems allow for a user to change the PIN associated with the smart card at a user's home or business, or in embodiments when the user has access to a telephone.

While the principles of the invention have been described above in connection with specific apparatuses and methods, it is to be clearly understood that this description is made only by way of example and not as limitation on the scope of the invention.