CA2561077A1

CA2561077A1 - System and method for secure verification of electronic transactions

Info

Publication number: CA2561077A1
Application number: CA002561077A
Authority: CA
Inventors: Ernest H. Nachtigall
Original assignee: IBM Canada Ltd
Current assignee: IBM Canada Ltd
Priority date: 2006-09-26
Filing date: 2006-09-26
Publication date: 2008-03-26
Also published as: US20080077798A1; US8621230B2

Abstract

There is provided a system and method for secure verification of electronic transactions, and in particular secure processing of personal identification numbers when third party processors are involved. In an embodiment, a variable length PIN
associated with a credit card or debit card is encrypted, then hashed using a one-way hash algorithm before it is passed along to and stored by a third party processor. The encrypted-hashed PIN always remains in an encrypted form while in the hands of the third party processor.
At the third party processor, secure cryptographic hardware is used to store the one-way hash algorithm.
Encrypted PIN values received for verification (e.g. from a retail point-of-sale terminal) are converted and hashed using the one-way hash algorithm, and the resulting hashed-encrypted value is compared against the hashed-encrypted PIN values previously stored at the third party processor. As the PIN has a variable length, and the third party processor has no access to the hash algorithm, the encrypted PIN values are highly resistant to reverse engineering or decryption.

Description

SYSTEM AND METHOD FOR SECURE
VERIFICATION OF ELECTRONIC TRANSACTIONS
COPYRIGHT NOTICE

[0001] A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND

[0002] The present invention relates to systems and methods for verification of electronic transactions, and in particular secure processing of personal identification numbers.

[0003] Electronic payments for goods and services has become commonplace, and payment via a credit card or bank card/debit card is now widely available at many retail locations as well as at many virtual store locations on the internet. As the use of electronic payment grows, the need for secure verification by third party processors is also increasing. However, involving third party processors may involve the need to disclose secure cryptographic keys that may compromise control by the owning banking institution. While various approaches have been proposed for offering secure verification for electronic payments, these approaches may exhibit limitations, especially when third party processing is involved.

[0004] What is needed is an improved method and system for secure verification of electronic transactions and PIN processing.

SUMMARY

[0005] The present invention provides a system and method for secure verification of electronic transactions, and in particular secure processing of personal identification numbers when third party processors are involved.

[0006] In an embodiment, a variable length PIN associated with a credit card or debit card is encrypted, then hashed using a one-way hash algorithm before it is passed along to and stored by a third party processor. The encrypted-hashed PIN always remains in an encrypted form while in the hands of the third party processor. At the third party processor, secure cryptographic hardware is used to store the one-way hash algorithm. Encrypted PIN values received for verification (e.g. from a retail point-of-sale terininal) are converted and hashed using the one-way hash algorithin, and the resulting hashed-encrypted value is compared against the hashed-encrypted PIN values previously stored at the third party processor. As the PIN has a variable length, and the third party processor has no access to the hash algorithm, the encrypted PIN values are highly resistant to reverse engineering or decryption.

[0007] In an aspect of the invention, there is provided a method of processing a personal identification number (PIN), comprising: encrypting at an owning institution processor a clear PIN input using an encryption algorithm to generate a first encrypted PIN; hashing at the owning institution processor the first encrypted PIN using a one-way hash algorithm to generate a first hashed-encrypted PIN; storing at a third party processor the first hashed-encrypted PIN.

[0008] In an embodiment, the method further comprises: receiving at the third party processor a second encrypted PIN generated from a clear PIN input; translating at the third party processor the second encrypted PIN into a third encrypted PIN in a form usable by the third party processor; hashing at the third party processor the third encrypted PIN using the one-way hash algorithm to generate a second hashed-encrypted PIN; and comparing at the third party processor the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to detennine if the second encrypted PIN is generated from the same clear PIN input as that of the first encrypted PIN.

[0009] In an embodiment, the method further comprises securing at the third party processor the one-way hash algorithm in cryptographic hardware.

[0010] In an embodiment, the method further comprises receiving at the owning institution processor a user generated clear PIN input.

[0011] In an embodiment, the user generated clear PIN input has a variable length, and the method further comprises generating at the owning institution processor the first hashed-encrypted PIN from the variable length PIN, and storing at the third party processor the first hashed-encrypted PIN from the variable length PIN.

[0012] In an embodiment, the method further comprises receiving at the third party processor the second encrypted PIN generated from a clear PIN input; translating at the third party processor the second encrypted PIN into a third encrypted PIN in a form usable by the third party processor; hashing at the third party processor the third encrypted PIN
using the one-way hash algorithm to generate a second hashed-encrypted PIN; comparing at the third party processor the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to determine if the second encrypted PIN is generated from the same variable length clear PIN
input as that of the first encrypted PIN.

[0013] In another aspect of the invention, there is provided a system for processing a personal identification number (PIN), comprising: an encryption algorithm module provided at an owning institution processor and configured to encrypt a clear PIN input and to generate a first encrypted PIN; a one-way hash algorithm module provided at the owning institution processor and configured to hash the first encrypted PIN and to generate a first hashed-encrypted PIN; storage provided at the third party processor for storing the first hashed-encrypted PIN.

[0014] In an embodiment, the system further comprises: a PIN translator module provided at the third party processor for translating a second encrypted PIN into a third encrypted PIN in a form usable by the third party processor; a one-way hash algorithm module provided at the third party processor for hashing the third encrypted PIN to generate a second hashed-encrypted PIN; a comparison module provided at the third party processor for comparing the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to determine if the second encrypted PIN is generated from the same clear PIN input as that of the first encrypted PIN.

[0015] In another embodiment, the system further comprises cryptographic hardware provided at the third party processor for securing the one-way hash algorithm.

[0016] In another embodiment, the system further comprises receiving means provided at the owning institution processor for receiving a user generated clear PIN input.

[0017] In another embodiment, the system further comprises a PIN translator module provided at the third party processor for translating a second encrypted PIN
into a third encrypted PIN in a form usable by the third party processor; a one-way hash algorithm module provided at the third party processor for hashing the third encrypted PIN to generate a second hashed-encrypted PIN; a comparison module provided at the third party processor for comparing the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to determine if the second encrypted PIN is generated from the same clear PIN
input as that of the first encrypted PIN.

[0018] In another embodiment, the system further comprises cryptographic hardware provided at the third party processor for securing the one-way hash algorithm.

[0019] In another aspect of the invention, there is provided a computer readable medium storing computer code that when loaded into one or more data processors adapts the processors to provide a method of processing a personal identification number (PIN), the computer readable medium comprising: code for encrypting at a owning institution processor a clear PIN input using an encryption algorithm to generate a first encrypted PIN; code for hashing at the owning institution processor the first encrypted PIN using a one-way hash algorithm to generate a first hashed-encrypted PIN; code for storing at a third party processor the first hashed-encrypted PIN.

[0020] In another embodiment, the computer readable medium further comprises:
code for receiving at the third party processor a second encrypted PIN generated from a clear PIN
input; code for translating at the third party processor the second encrypted PIN into a third encrypted PIN in a forin usable by the third party processor; code for hashing at the third party processor the first encrypted PIN using the one-way hash algorithm to generate a second hashed-encrypted PIN; and code for comparing at the third party processor the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to determine if the second encrypted PIN is generated from the same clear PIN input as that of the first encrypted PIN.

[0021] In another embodiment, the computer readable medium further comprises code for receiving a user generated clear PIN input.

[0022] In another embodiment, the user generated clear PIN input has a variable length, and the computer readable medium further comprises code for generating the first hashed-encrypted PIN from the variable length PIN at the owning institution processor and storing the first hashed-encrypted PIN from the variable length PIN at the third party processor.

[0023] In another einbodiment, the computer readable further comprises code for securely accessing the one-way hash algorithm secured in cryptographic hardware at the third party processor.

[0024] These and other aspects of the invention will become apparent from the following more particular descriptions of exemplary embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

[0025] In the figures which illustrate exemplary embodiments of the invention:

FIG. 1 shows a generic data processing system that may provide a suitable operating environment;

FIG. 2 shows a schematic block diagram of a PIN verification system;

FIG. 3 shows a schematic block diagram of a PIN encryption system and method in accordance with an embodiment;

FIG. 4 shows a schematic block diagram of a PIN decryption system and method in accordance with an embodiment.

DETAILED DESCRIPTION

[0026] As noted above, the present invention relates a system and method for secure verification of electronic transactions, and in particular secure processing of personal identification numbers or PINs.

[0027] The invention may be practiced in various embodiments. A suitably configured data processing system, and associated communications networks, devices, software and firmware may provide a platfonn for enabling the system and method. By way of example, FIG. 1 shows a generic data processing system 100 that may include a central processing unit ("CPU") 102 connected to a storage unit 104 and to a random access memory 106.
The CPU
102 may process an operating system 101, application program 103, and data 123. The operating system 101, application program 103, and data 123 may be stored in storage unit 104 and loaded into memory 106, as may be required. An operator 107 may interact with the data processing system 100 using a video display 108 connected by a video interface 105, and various input/output devices such as a keyboard 110, mouse 112, and disk drive connected by an I/O interface 109. In known manner, the mouse 112 may be configured to control movement of a cursor in the video display 108, and to operate various graphical user interface ("GUI") controls appearing in the video display 108 with a mouse button. The disk drive 114 may be configured to accept data processing system readable media 116. The data processing system 100 may form part of a network via a network interface 111, allowing the data processing system 100 to communicate with other suitably configured data processing systems (not shown). The particular configurations shown by way of example in this specification are not meant to be limiting. For example, in a mainframe environment, video interface 105, video display 108, keyboard 100, and mouse 112 may be provided at a workstation operatively connected to a mainframe (not shown), and not at the mainfraine itself.

[0028] Now referring to FIG. 2, shown is a schematic block diagram of an electronic transaction verification system 200 that may include one or more data processing systems 100 suitably configured for various purposes. As shown, electronic transaction verification system 200 may include a banking institution 202 connected via a network 204 to its own automated teller machine (ATM) 206. The banking institution 202 may maintain a banking institution database 203 containing information on debit cards or credit cards issued to various customers. In a closed environment involving only the banking institution 202 and its ATMs 206, the banking institution 202 processes its own electronic payment transactions and validates PINs entered by its customers at ATM 206 by accessing records stored in database 203.

[0029] Typically, PIN processing is one of the most secure areas within any bank as any security breach may be devastating from a reputation standpoint, as well as from the viewpoint of exposure to legal risks. Nevertheless, in order to provide enhanced banking services, the banking institution 202 may want a third party processor to have the ability to process electronic transactions on its behalf. This may be done, for example, in situations where the banking institution 202 may not able to verify the transaction itself (e.g. due to a communication problem or system maintenance, or because of geographic location).

[0030] Still referring to FIG. 2, banking institution 202 may be connected via network 204 to a third party processor 208. The third party processor 208 may be, for example, a service provider that may be engaged by the banking institution 202 to verify credit card or debit card transactions on its behalf. Third party processor may maintain a third party database 209 that may store data that may be provided by banking institution 202 for the purposes of conducting electronic transaction verification on the banking institution 202's behalf.

[0031] Third party processor 208 may be accessible via a network 214 to retail location 210 having a point-of-sale (POS) terminal 212. The third party processor 208 may also be connected to various other retail locations via network 210, such as retail location 216 having POS termina1218.

[0032] Presently, there are a number of available techniques that may be used by the third party processor 208 to accomplish PIN verification processing. The first technique requires that all cryptographic keys and processing infonnation available to the owning banking institution 202 also be available to the third party processor 208 such that the normal authorization processes done at the banking institution 202 can also be performed at the third party processor 208. A drawback to this approach is that highly sensitive cryptographic keys may need to be made available outside the banking institution 202's direct control. If this is done, it is possible that rogue personnel with the third party processor 208 could use the cryptographic keys to manufacture counterfeit cards with their respective PINs.

A second technique requires that encrypted PIN information be maintained at the banking institution 202 and at the third party processor 208 within client records (e.g. in a cardholder database in banking institution database 203 and third party database 209).
With this approach, transaction processing requires that the encrypted PIN received from POS terminals 212, 218 be securely translated from encryption under a session key (used at the POS
terrninals 212, 218) to encryption under the database encryption key (used at the third party processor 208). The translated cryptogram may then be compared against the database cryptogram. A match between the session key and the database stored encryption key means that the same PIN was used. Although the PIN information stored in the third party database 209 is usually encrypted, the possibility exists that a rogue third party insider could translate the database encrypted PINs using that same database encryption key which may be available to that insider. It is then simply a matter of decrypting the PIN values for the entire database.

[0033] A third technique requires using two sets of cryptographic keys and two separate PIN
algorithms. With this third technique, the banking institution 202 may use either of the two above approaches to process PINS -- i.e. the banking institution 202 may calculate PINs via an algorithm, or it may store encrypted PIN values in a client database. A
second, separate cryptographic key may then be provided to the third party processor 208. The banking institution 202 may use this cryptographic key to generate PIN Verification Values (PVV).
For example, a PVV may be generated from encrypting the client account number (i.e. the credit card or debit card number) and the clear (i.e. unencrypted) value of an encrypted PIN.
In this case, the algorithm requires an encrypted value which it may then securely decrypt within the confines of secure cryptographic hardware. The result is then passed through an extraction routine and, typically, a four-digit reference may be produced.
With this third technique, the banking institution 202 creates the reference, and the third party processor 208 may use the PVV algorithm to verify the reference. In this case, the third party processor 208 does not have access to cryptographic information that can be used to manufacture credit/debit cards. Unfortunately, the PVV algorithms in use today typically only allow a relatively short fixed number of digits (typically 4 digits) which may allow the PIN to be hacked in a concerted effort.

[0034] As will now be described, a novel solution is proposed which may significantly reduce the possibility that encrypted PIN information may be decrypted by the third party processor 208.

[0035] Now referring to FIG. 3, shown is a schematic block diagram of a PIN
encryption system and method that may be provided at the banking institution 202 in the system 200 of FIG. 2. As shown, PIN encryption system 300 may include a PIN encryption algorithm module 304, and a one-way hash algorithm module 308. The P1N encryption algorithm module 304 may be configured to receive a clear PIN input 302, and to produce an encrypted P1N output 306. A one-way hash algorithm module 308 may be configured to receive the encrypted PIN output 306 and produce a hashed-encrypted PIN output 310.

[0036] A corresponding method may proceed as follows: First, a PIN value provided at clear PIN input 302 is encrypted via a PIN encryption algorithm 304 to produce an encrypted PIN
output 306. The PIN encryption 304 may be, for example, a third party database cryptographic key (e.g. ANSI X9.8, also known as ISO-0). Next, the encrypted PIN output 306 may be passed through one-way hash algorithm 308 to produce a hashed-encrypted PIN
output 310. The hash algorithm 308 used may be, for example, Secure Hash Algorithm (SHA)-256. The resulting value (output of the one-way HASH) is now the obscured version of the encrypted PIN.

[0037] In an embodiment, the owning banking institution 202 may make available a shared encryption key (KPEV) to the third party processor 208. The banking institution 202 then translates all PIN values from encryption under a banking institution key to encryption under this shared KPEV.

[0038] Every time a customer changes their PIN (e.g. via customer PIN
selection), the resulting encrypted PIN is again translated into encryption under the KPEV.
The KPEV
encrypted PIN is then processed through the one-way hash algorithin 308.

[0039] In an embodiment, the banking institution 202 may allow customers to have PINs that may have a variable number of digits. Although the PIN may be virtually any length, certain parameters may be set for a minimum number of characters and a maximum number of characters. By way of example, the minimum length may be 4 digits, and the maximum length may be 12 digits, as per PIN standards.

[0040] In an embodiment, the original PIN may be encrypted in the ANSI X9.8 or format, for example, such that the encrypted values are unique. Using ANSI
X9.8/ISO-0 format, even though a four digit PIN value can be from 0000 to 9999, all PINs may be virtually unique since the actual PIN may be exclusive OR'ed with, for example, the 12 most significant digits of a unique account number. Since the accounts are unique, the resulting PIN value will also be virtually unique.

[0041] Whatever the length or value of the PIN input at clear PIN input 302, PIN encryption algorithm module 304 and one-way hash algorithm module 308 translates the value into a hashed-encrypted PIN output 310. Since hashing is a one-way function, and as the PIN does not have a fixed number of values, it will be appreciated that the hashed-encrypted PIN output 310 will be highly resistant to hacking, and the clear PIN input 302 may not be reasonably recovered by the third-party processor 208. Thus, the hashed-encrypted PIN
output 310 for each client PIN may be safely stored in the third party database 209 and made available to the third party processor 208 for secure PIN verification.

[0042] Now referring to FIG. 4, shown is a schematic block diagram of a third party PIN
verification system and method that may be provided at the third party processor 208. As shown, the third party PIN verification system 400 may include an encrypted PIN translation module 404, a one-way hash algorithm module 406, and a comparison module 410.
The encrypted PIN translation module 404 may be configured to receive an encrypted PIN input 402 (e.g. from POS 212 or 218) and to produce a translated PIN output 405. The one-way hash algorithm module 406 may be configured to receive the translated PIN
output 405 and to produce a hashed-encrypted PIN output 408. The comparison module 410 may be configured to compare the hashed-encrypted PIN output 408 to a previously stored hashed-encrypted PIN
value (e.g. as may be stored in third party database 209).

[0043] A corresponding method may proceed as follows: Upon receiving a card verification request (e.g. from a customer using a credit card or debit card at POS 212 or 218), the PIN
entered by the user may be received as an encrypted PIN input 402.

[0044] In an embodiment, this encrypted PIN input 402 may be translated (e.g.
by using the Encryption PIN translation module 404) by the third party processor 208 using a shared device encryption key to another encrypted fonn usable by the third party processor (i.e. the KPEV provided by the banking institution). Encryption PIN translation module 404 produces a translated PIN 405.

[0045] Thus, rather than comparing the converted encrypted PIN directly, as previously done, the third party processor 208 uses a one-way hash algorithm 406 provided in secure cryptographic hardware to produce a hashed-encrypted PIN output 408 from the translated PIN 405. This hashed-encrypted PIN 408 is then compared to the hashed-encrypted values previously stored in the third party database 209. As the third party processor 208 cannot practically reverse engineer the one-way hash algorithm used in one-way hash algorithm module 406, and does not know the length of the variable PIN used, the third party processor 308 does not have sufficient information to generate the original clear PINs.
Effective control is thus retained by the banking institution 202.

[0046] In an einbodiment, the proposed solution may further involve validation of a supplied token (e.g. a magnetically striped card as in credit or debit) to verify that, again, the owning banking institution 202 actually produced and generated a cryptographic checksum that verifies the original. This verification may happen both at the banking institution 202 when it does validation processing and also at the third party processor 208.

[0047] For example, credit card issuers such as VISATM, Master CardTM, and AMEXTM use various card verification techniques (e.g. card verification value / card verification code / card security code - CVV/CVC/CSC) that involve the use of proprietary cryptographic keys. At the banking institution 202, the normal card verification algorithm may be used which can verify and also create valid tokens (e.g. CVV/CVC/CSC). The banking institution 202 then uses most of the data normally used for this verification, as well as the cryptographically generated checksum to then pass this modified data through the normal CVV/CVC/CSC
algorithm. This value is then made available to the stand-in system and serves to validate that the supplied token was generated by the owning bank institution 202 (since the third party processing site uses the clear text, yet the owning bank institution securely generated the checksum) in its verification process.

[0048] This means only the owning banking institution 202 can generate valid tokens and supply a new checksuin (used only by the stand-in system) using the owning institution's securely generated checksum and new secure keys for the generation of the stand-in checksum. The third party processing system 208, not knowing the secure keys used by the banking institution 202, cannot then generate tokens that would be validated at either the banking institution 202 or stand-in third party sites.

[0049] During processing at the third party processor 208, the encrypted PIN
value of an account is received (e.g. from POS devices 212, 218), then translated using the KPEV. The result is hashed and that result is then compared to the values resident in the third party database 404. To verify that the supplied magnetically striped card has been issued by the banking institution 202, it is possible to still use the CVV/CVC/CSC function.
However, the banking institution 202 will create its true CVV/CVC/CSC value using its own secret cryptographic keys. The CVV/CVC/CSC value, as is customary, may still be written to the magnetic stripe of the client card. A separate CVV/CVC/CSC cryptographic key (hereinafter "KVCV") may then be shared with the third party processor 208.

[0050] Once the banking institution 202 has generated the true CVV/CVC/CSC
value, the KVCV is then used to also process the CVV/CVC/CSC again, but this time, instead of using a SERVICE CODE field, the true CVV/CVC/CSC is used in its place. This helps to ensure that the resulting cryptographic "checksum" also includes, and is dependant on, the true CVV/CVC/CSC generated from the banking institution 202's cryptographic keys.
This recalculated CVV/CVC/CSC is then also made available to the third party processor 208 and stored in the third party database 404 along with the above described hashed-encrypted PIN
output 310.

[0051] Since this new CVV/CVC/CSC does not directly use the original banking institution 202's cryptographic keys, the KVCV cannot be used to generate valid magnetic stripe cards.
Thus, the CVV/CVC/CSC as described here is also a cryptographic one-way function such that the result cannot be used to recover the original source.

[0052] The above description has shown how to make PIN validation and CVV
validation available to a third party processor 208 without exposing the true cryptographic keys that could be used to manufacture PINs and magnetic cards. Copying or compromising the database maintained at the third party processor will allow no viable attacks on true account information.

[0053] Not only can the above techniques be used to "secure" a third party outsourced system, but if the PIN technique is also used by the owning banking institution 202, rather than keeping a database of client information and associated encrypted PIN
values, an owning institution's KPEV key can be used to translate true PINs, into hashed-encrypted PIN values.
Attacks on this database to recover PINs would then be practically infeasible.

[0054] While various illustrative embodiments of the invention have been described above, it will be appreciated by those skilled in the art that variations and modifications may be made.
Thus, the scope of the invention is defined by the following claims.

Claims

1. A method of processing a personal identification number (PIN), comprising:
encrypting at an owning institution processor a clear PIN input using an encryption algorithm to generate a first encrypted PIN;
hashing at the owning institution processor the first encrypted PIN using a one-way hash algorithm to generate a first hashed-encrypted PIN;
storing at a third party processor the first hashed-encrypted PIN.

2. The method of claim 1, further comprising:
receiving at the third party processor a second encrypted PIN generated from a clear PIN input;
translating at the third party processor the second encrypted PIN into a third encrypted PIN in a form usable by the third party processor;
hashing at the third party processor the third encrypted PIN using the one-way hash algorithm to generate a second hashed-encrypted PIN;
comparing at the third party processor the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to determine if the second encrypted PIN is generated from the same clear PIN input as that of the first encrypted PIN.

3. The method of claim 2 further comprising securing at the third party processor the one-way hash algorithm in cryptographic hardware.

4. The method of claim 1 further comprising receiving at the owning institution processor a user generated clear PIN input.

5. The method of claim 4 wherein the user generated clear PIN input has a variable length, and the method further comprises generating at the owning institution processor the first hashed-encrypted PIN from the variable length PIN, and storing at the third party processor the first hashed-encrypted PIN from the variable length PIN.

6. The method of claim 5 further comprising:
receiving at the third party processor the second encrypted PIN generated from a clear PIN input;
translating at the third party processor the second encrypted PIN into a third encrypted PIN in a form usable by the third party processor;
hashing at the third party processor the third encrypted PIN using the one-way hash algorithm to generate a second hashed-encrypted PIN;
comparing at the third party processor the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to determine if the second encrypted PIN is generated from the same variable length clear PIN input as that of the first encrypted PIN.

7. The method of claim 6, further comprising securing at the third party processor the one-way hash algorithm in cryptographic hardware.

8. A system for processing a personal identification number (PIN), comprising:
an encryption algorithm module provided at an owning institution processor and configured to encrypt a clear PIN input and to generate a first encrypted PIN;
a one-way hash algorithm module provided at the owning institution processor and configured to hash the first encrypted PIN and to generate a first hashed-encrypted PIN;
storage provided at the third party processor for storing the first hashed-encrypted PIN.

9. The system of claim 8 further comprising:
a PIN translator module provided at the third party processor for translating a second encrypted PIN into a third encrypted PIN in a form usable by the third party processor;
a one-way hash algorithm module provided at the third party processor for hashing the third encrypted PIN to generate a second hashed-encrypted PIN;

a comparison module provided at the third party processor for comparing the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to determine if the second encrypted PIN is generated from the same clear PIN input as that of the first encrypted PIN.

10. The system of claim 9 further comprising cryptographic hardware provided at the third party processor for securing the one-way hash algorithm.

11. The system of claim 9 further comprising receiving means provided at the owning institution processor for receiving a user generated clear PIN input.

12. The system of claim 11 further comprising:

a PIN translator module provided at the third party processor for translating a second encrypted PIN into a third encrypted PIN in a form usable by the third party processor;
a one-way hash algorithm module provided at the third party processor for hashing the third encrypted PIN to generate a second hashed-encrypted PIN;
a comparison module provided at the third party processor for comparing the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to determine if the second encrypted PIN is generated from the same clear PIN input as that of the first encrypted PIN.

13. The system of claim 12, further comprising cryptographic hardware provided at the third party processor for securing the one-way hash algorithm.

14. A computer readable medium storing computer code that when loaded into one or more data processors adapts the processors to provide a method of processing a personal identification number (PIN), the computer readable medium comprising:
code for encrypting at a owning institution processor a clear PIN input using an encryption algorithm to generate a first encrypted PIN;
code for hashing at the owning institution processor the third encrypted PIN
using a one-way hash algorithm to generate a first hashed-encrypted PIN;
code for storing at a third party processor the first hashed-encrypted PIN.

15. The computer readable medium of claim 14, further comprising:

code for receiving at the third party processor a second encrypted PIN
generated from a clear PIN input;
code for translating at the third party processor the second encrypted PIN
into a third encrypted PIN in a form usable by the third party processor;
code for hashing at the third party processor the third encrypted PIN using the one-way hash algorithm to generate a second hashed-encrypted PIN;
code for comparing at the third party processor the second hashed-encrypted PIN to the stored first hashed-encrypted PIN to determine if the second encrypted PIN
is generated from the same clear PIN input as that of the first encrypted PIN.

16. The computer readable medium of claim 15 further comprising code for receiving a user generated clear PIN input.

17. The computer readable medium of claim 16 wherein the user generated clear PIN
input has a variable length, and the computer readable medium further comprises code for generating the first hashed-encrypted PIN from the variable length PIN at the owning institution processor and storing the first hashed-encrypted PIN from the variable length PIN
at the third party processor.

18. The computer readable medium of claim 17 further comprising code for securely accessing the one-way hash algorithm secured in cryptographic hardware at the third party processor.