Method and system for transmission of financial data4984270Abstract An improved system for transmission financial data includes, in preferred embodiments, an encryption key stored on a bank card and used to encrypt preselected data prior to transmission. Encrypted data is then transmitted through all intermediate computers without decryption and reencryption. Decryption occurs only at the final destination, where the encryption key has been stored. In preferred embodiments, the encryption key is combined with a terminal identification valve to provide further security. Claims I claim: Description TECHNICAL FIELD
______________________________________
4-Bit Hexadecimal
4-Bit Hexadecimal
Series Character Series Character
______________________________________
0000 0 1000 8
0001 1 1001 9
0010 2 1010 A
0011 3 1011 B
0100 4 1100 C
0101 5 1101 D
0110 6 1110 E
0111 7 1111 F
______________________________________
The Issuer Security Key may be any length from a minimum of one character (4 bits) to a maximum length of sixteen characters (64 bits). Each of the three magnetic stripe tracks has a different combination of coded character set and bit recording density per the ISO 7811/2 standard. According to ISO 7811/2, each track has the minimum physical encoding length requirement of 2.957 inches (magnetic stripe length). All encoding discussions in this document will consider the maximum encoding length capability of any specific track to be the 2.957 inches. Each track's encoding capabilities to support the Issuer Security Key is described in the following clauses. TRACK 1 ISSUER SECURITY KEY ENCODING Track 1 uses a code character set of 6 bits per character plus a parity bit as defined in ISO 7811/2. The Issuer Security Key character set shall be composed of the characters from Column 0, Rows 0-15 as defined in ISO 7811/2 for the Track 1 character set and shall use odd parity. Given the Track 1 recording structure as defined in ISO 7813, the maximum number of encoded characters shall not exceed 79 characters including the LRC character. This provides, at a minimum, the recording capability for an Issuer Security Key of 9 characters (36 bits). Issuers wishing to record 16 characters (64 bits) for the Issuer Security Key shall only encode a maximum of 74 characters for the Track 1 recorded structure. The shorter encoding length of Track is well within the issuer's options of recording Track 1 information per the ISO 7813 standard. Calculations used in determining the Issuer Security Key recording capability per ISO 7811/2 and ISO 7813: Total Track 1 physical recording capacity; (2.957 inches available).times.(210 bits per inch recording density)=620.97 bit positions. Track 1 physical recording capacity after the LRC character given the maximum Track 1 recording structure as defined in ISO 7813; (79 characters).times.(6-bit code character set+1 parity bit) 553 bit positions encoded. 620.97-553=67.97 bit positions are then available after the last LRC character encoded bit. Therefore, the minimum always available for the Issuer Security Key is 67.97.div.7=9.71 characters (actually 9 whole characters). Since only the lower order four bits of the six-bit character set are used for the Issuer Security Key, (4 bits).times.(9 characters) =36, 36 total bits are available for the Issuer Security Key value. TRACK 2 ISSUER SECURITY KEY ENCODING Track 2 uses a code character set of 4 bits per character plus a parity bit as defined in ISO 7811/2. The Issuer Security Key character set shall be composed of the 4-bit characters from Rows 0 through 15 as defined in ISO 7811/2 for the Track 2 character set and shall use odd parity. Given the Track 2 recording structure as defined in ISO 7813, the maximum number of encoded characters shall not exceed 40 characters including the LRC character. This provides at a minimum, the recording capability for an Issuer Security Key of 4 characters (16 bits). Issuers wishing to record 16 characters (64 bits) for the Issuer Security Key shall only encode a maximum of 28 characters for the Track 2 recorded structure. The shorter encoding length of Track 2 is well within the issuer's options of recording Track 2 information per the ISO 7813 standard.
______________________________________
Start sentinel 1
Primary Account Number
16
Separator 1
Expiration date 4
Interchange designator
1
Service code 2
Discretionary data 1
End sentinel 1
LRC 1
Recorded Length 28 Characters
______________________________________
Calculations used in determining the Issuer Security Key recording capability per ISO 7811/2 and ISO 7813: Total Track 2 physical recording capacity; (2.957 inches available).times.(75 bits per inch recording density=221.77 bit positions. Track 2 physical recording capacity after the LRC character given the maximum Track 2 recording structure as defined in ISO 7813; (40 characters).times. (4 bit code character set+1 parity bit)=200 bit positions encoded. 221.77-200=21.77 bit positions are available after the last encoded LRC character Therefore, the minimum always available for the Issuer Security Key is 21.77.div.5 =4.354 characters. Since only the lower order four bits of the character set are used for the Issuer Security Key, (4 bits).times. (4 characters)=16, 16 total bits are available for Issuer Security Key value. TRACK 3 ISSUER SECURITY KEY ENCODING Track 3 uses a code character set of 4 bits per character plus a parity bit as defined in ISO 7811/2. The Issuer Security Key character set shall be composed of the 4 bit characters from Rows 0 through 15 as defined in ISO 7811/2 for the Track 3 character set and shall be odd parity. Given the Track 3 recording structure as defined in ISO 4909, the maximum number of encoded characters shall not exceed 107 characters including the LRC character. This provides at a minimum the recording capability for an Issuer Security Key of 16 characters (64 bits). Calculations used in determining the Issuer Security Key recording capability per ISO 7811/2 and ISO 4909: Total Track 3 physical recording capacity; (2.957 inches available).times.(210 bits per inch recording density)=620.97 bit positions. Track 3 physical recording capacity after the LRC character given the maximum Track 3 recording structure as defined in ISO 4909; (107 characters).times. (4 bit code character set+1 parity bit)=535 bit positions encoded. 620.97-535=85.97 bit positions are then available after the last encoded LRC character encoded bit. Therefore, the minimum always available for the Issuer Security Key is 85.97.div.5=17.194 characters. Since only the lower order four bits of the character set are used for the Issuer Security Key, (4 bits).times. (16 characters)=64, 64 total bits are available for the Issuer Security Key value. READING THE MAGNETIC STRIPE ENCODED ISSUER SECURITY KEY Since the Issuer Security Key is after the Longitudinal Redundancy Check (LRC) character, and may vary in encoded length, the following procedure, or any similar magnetic stripe reading process, may be used to read the encoded Issuer Security Key. According to ISO 7811/2, clocking bits (zeros) shall be recorded on a magnetic stripe from the last recorded bit for the LRC character to the end of the magnetic stripe. Therefore, the end of the Issuer Security Key can be found by searching for the cocking bits. Since the clocking bits are all zeros including the parity bit position, the Issuer Security Key can support the character value of 0 (where b1-b4 are 0000) since the parity bit shall be set to 1 to maintain odd parity. To ensure the Issuer Security Key has been read successfully, and since no LRC character is encoded after the last encoded Issuer Security Key character, the parity bit position of each Issuer Security Key character shall be tested for odd parity. This maintains the character recording method as defined for all tracks in ISO 7811/2. An Issuer Security Key character read error from the financial transaction identification card on an odd parity bit test failure shall cause the Issuer Security Key to not be used in any DEA encryption process by the point-of-service device. This will cause the DEA encryption process to use a DEA key of all pad characters as described in the following clause. ISSUER SECURITY KEY USE To use the Issuer Security Key as a DEA key as defined in the ANSI X3.92 and FIPS PUB 46 standards, the Issuer Security Key must be expanded to a 64-bit form. To perform this process, the Issue Security Key read from the financial transaction identification card shall be left justified in a 64-bit block and padded to the right with all one (1) bits to complete the 64-bit block. Odd parity adjustment is then made before using the key in a DEA process. Odd parity is established by setting the parity of every 8-bit byte in a left to right pattern to odd (for example, 1111 1111 shall be set to 1111 1110). The padding of the 1 bits to complete the 64-bit block is used since an odd number of 4-bit Issuer Security Key characters can be recorded on the financial transaction identification card. Normally DEA keys are represented in the 64-bit form as sixteen hexadecimal characters (0, 1-9, and A, B - F) with a space between every pair of characters. Example: 1F 2A 3D 49 5E 6B 7C 8F. Given an Issuer Security Key recorded as 81 54 BE 1 (seven 4-bit characters) on the financial transaction identification card, its value will be 8A 54 BE 1F FF FF FF FF after the padding process. After the odd parity adjustment the key used by the DEA process shall be 8A 54 BF 1F FE FE FE FE. The most ideal Issuer Security Key recorded on the financial transaction identification card by the card issuer is a complete 64-bit key already adjusted to odd parity. Since the encrypted result of a DEA process using the Issuer Security Key will always be the same at any point-of-service device for the same DEA input block, implementations of the Issuer Security Key may include another data element exclusive OR'd to the key before use by the Data Encryption Algorithm. Whatever other data is selected, it must be available to the card issuer, or its agent, for recreating the DEA key used by the point-of-service device. An example would be a terminal identification number. The terminal identification number is then sent from the point-of-service device to the card issuer in the clear as part of a message. Given the encrypted DEA results in the same message as the terminal identification number, the Issuer Security Key is still not easily obtainable. Even if the input block was a cardholder-entered PIN and the PIN was known and the terminal identifier was known, the Issuer Security Key could still only be attacked by repetition of all possible 64-bit key combinations until a match of the DEA encryption process results is found. This makes fraud in the communications environment between the point-of-service device and the card issuer difficult with the reward of knowing only the Issuer Security Key for one financial transaction identification card. Other DEA key management systems in place may disclose all cardholder-entered PINs for all financial transaction identification cards used at a point-of-service device when the key is compromised. Also, no greater protection of the DEA key is provided by other DEA key management systems since all combinations of the 64-bit key must be attempted until a match is found. ISSUER SECURITY KEY EXAMPLE The most typical use of the Issuer Security key will be to secure the cardholder-entered Personal Identification number (PIN) at a point-of-service device which also reads a financial transaction identification card magnetic stripe. The PIN can then be sent in an encrypted form end-to-end from the point-of-service device to the card issuer, or its agent, for PIN verification processing. The following flow describes an implementation of this use:
______________________________________
Place of Process
Description
______________________________________
Card Issuer 1. Card issuer manufactures a finan-
cial transaction identification
card and encodes an Issuer Secur-
ity Key on Tracks 1 and 2.
Card Issuer 2. The card issuer stores the Issuer
Security Key on a Primary Account
File for the Primary Account Num-
ber recorded on the card.
Card Issuer 3. Before storing the Issuer Secur-
ity Key, the card issuer creates
a cryptogram for actual storage.
The cryptogram is created by
using the Data Encryption Algo-
rithm encrypt function usng the
issuer Security Key as the input
block and an issuer masterkey for
the DEA key.
Card Issuer 4. To ensure security, the card
issuer performs the cryptogram
process in a hardware security
module to protect the issuer's
master key and not compromise the
Issuer Security Key within the
card issuer's facility.
Card Issuer 5. The most ideal situation would be
a hardware security module that
randomly creates Issuer Security
Keys and provides the clear
Issuer Security Key directly to
the card manufacturing process
and creates the key cryptogram
for file storage.
Card Issuer 6. As part of the card manufacturing
process, the card issuer also
creates a Personal Identification
Number (PIN) to be used with the
card.
Card Issuer 7. Through common card issuance and
PIN issuance, both are supplied
separately to the cardholder.
Point-of-Service
8. The cardholder uses a point-
Device of-service device (e.g., POS
terminal) by swiping the finan-
cial transaction identification
card and entering the card-
holder's PIN.
Point-of-Service
9. The magnetic stripe reader of the
Device terminal reads Track 1 and cap-
tures the encoded Issuer Security
Key.
Point-of-Service
10. The Issuer Security Key is
Device exclusive OR'd to the terminal
identification number to create a
DEA key.
Point-of-Serivce
11. The cardho1der-entered PIN is
Device exclusive OR'd to the Primary
Account Number per the ANSI X9.8
and ISO TC68/SC2 working draft
N177 standards procedure to
create the DEA input block.
Point-of-Servce
12. The result of the DEA encrypton
Device process is then sent in a finan-
cial transaction request message
to the card issuer for PIN
validation.
Point-of-Service
13. The terminal identification
Device number is also sent to the card
issuer in the same message in the
clear. The use of the terminal
identification number had been
previously agreed to by the card
acquirer and card issuer in a
network operating rule business
agreement.
Card Issuer 14. The card issuer receives
theencrypted PIN in the financial
transaction request message.
Card Issuer 15. To verify the cardholder-entered
PIN, the card issuer passes the
encrypted PIN, Primary Account
File stored issuer Security Key
cryptogram, the terminal identifi-
cation number received in the
request message and PIN valida-
tion data to a hardware security
module for PIN validation.
Card Issuer 16. The hardware security module
decrypts the Issuer Security Key
cryptogram and exclusive OR's the
terminal identification number to
the now clear key to recreate the
same DEA key used by the point-of-
service device.
Card Issuer 17. Next, the hardware security
module decrypts the received
customer-entered PIN following
ANSI X9.8 and ISO standard proce-
dure to verify 1:1 to the card
issuer's recalculated PIN also
created in the hardware security
module.
Card Issuer 18. The PIN verification process
can be speeded up by the card
issuer if, during the card
issuance process, the originally
created PIN had been stored
encrypted under the card issuer's
master key on the Primary Account
Fi1e. The entire PIN
verification process is at the
option of the card issuer. The
card issuer could have also
chosen not to use hardware
security modules and perform all
DEA decryption and PIN
verification in a security
software routine.
______________________________________
From the foregoing it will be appreciated that, although specific embodiments of the invention have been described herein for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. Accordingly, the invention is not to be limited except as by the appended claims.
|
Same subclass Same class Consider this |
||||||||||
