Method and system for secure payments over a computer network

Abstract

A method of conducting a financial transaction by a purchaser over a communications network is provided where the purchaser does not transmit his or her “real” payment card information over the network but instead secure payment application software is provided which allows for the transmission of a pseudo account number that is cryptographically processed for purposes of responding to an authorization request based on the real account number.

Description

BACKGROUND OF INVENTION

[0002] This invention relates to a method and system for conducting secure financial transactions over a communications network and more particularly to a method and system for transmitting payments securely over a computer network, such as the Internet, and for transmitting sensitive information securely over public communication channels.

[0003] As is self-evident, on-line commerce has experienced tremendous growth over the last few years but even with that growth consumers are still troubled and concerned about using personal financial information and transmitting such information, such as credit card numbers and personal identification numbers, over public communications networks, such as the Internet. As a result, over the last few years, companies have struggled to find a way—the best way—to ensure the security of payments made over a computer network and to decrease the risk of theft or misuse of financial information.

[0004] For example, U.S. Pat. No. 5,883,810 entitled “Electronic Online Commerce Card With Transaction Proxy Number For Online Transactions” and assigned to Microsoft Corporation, is directed to a system which provides for each transaction a temporary transaction number and associates it with the permanent account number; the transaction number looks like a real credit card number and the customer uses that transaction number and submits it to the merchant as a proxy for the customer account number. In this matter, the customer does not have to transmit over a public network his or her real credit card number.

[0005] In the '810 patent, the merchant passes along the transaction number to the issuing institution, which in turn uses the transaction number as an index, accesses the real customer account number and processes the authorization, sending the authorization reply back to the merchant under the transaction number. As a result, risk is purportedly minimized not only because the customer only transmits a transaction number but also because the proxy number is good only for a single purchase—theft “would not greatly benefit a thief because it cannot be repeatedly used for other purchases or transactions.” Col. 2, lines 60-61.

[0006] There is still a need to improve upon the prior art systems and in particular there is a need for a method and system for conducting a secure financial transaction over the Internet which avoids requiring the creation and transmission of a unique repeatedly generated transaction number to replace the transmission of the permanent account number for each conducted transaction.

SUMMARY OF THE INVENTION

[0007] According to the present invention, a “pseudo” account number is assigned to a customer and cryptographically linked to a consumer's payment account number. The payment account number is an account number issued by a financial institution or other organization that a consumer may use to make a payment for goods and/or services. For example, the payment account number may be the account number from a payment card, such as a credit or debit card, or from a payment application, such as an electronic cash application stored on a consumer's computer. The pseudo account number appears to be an actual payment account number to a merchant. That is, the pseudo account number has the same length as a valid payment account number and begins with a valid identification number (e.g., a “5” for MasterCard International Incorporated (“MasterCard”)). The pseudo account number is used by the customer instead of the real account number for all of his or her on-line financial transactions.

[0008] All transactions based on pseudo account numbers are preferably cryptographically authenticated using a secret key that is unique for each account number. The authentication may be based on the private key of a public-key pair (“public-key authentication”), or based on a secret key other than a private key (“secret-key authentication”). Thus, if unauthorized persons were to ascertain any pseudo account numbers, they would be unable to make fraudulent transactions using them.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Further objects, features and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying figures showing a preferred embodiment of the invention, on which:

[0010] FIG. 1 is a block diagram of the system for obtaining a secure payment application from a provider over the Internet in accordance with the invention;

[0011] FIG. 2A is a block diagram of the system for conducting a secure payment over the Internet using the present invention with secret-key authentication of pseudo account numbers, in accordance with the invention;

[0012] FIG. 2B is a block diagram of the system for conducting a secure payment over the Internet using the present invention with public-key authentication of pseudo account numbers, in accordance with the present invention;

[0013] FIG. 3A is a block diagram illustrating the process preferably performed to obtain a pseudo account number for a given “real” account number, in accordance with the present invention;

[0014] FIG. 3B is a block diagram illustrating the process preferably performed to convert a pseudo account number back into its corresponding “real” account number;

[0015] FIGS. 4A and 4B illustrate the steps that are performed in accordance with the present invention when a card holder places an order with a merchant on the Internet and the merchant requests an authorization from an acquirer;

[0016] FIG. 5 is a block diagram illustrating the process of clearing a transaction in accordance with the present invention;

[0017] FIG. 6 is a block diagram illustrating exception processing in accordance with the present invention.

[0018] Throughout the figures, the same reference numerals and characters, unless otherwise stated, are used to denote like features, elements, components or portions of the illustrated embodiment. Moreover, while the subject invention will now be described in detail with reference to the figures, it is done so in connection with a preferred embodiment. It is intended that changes and modifications can be made to the described embodiment without departing from the true scope and spirit of the subject invention as defined by the appended claims.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0019] FIG. 1 illustrates an initial setup whereby a consumer who has, in this instance, a MasterCard financial transaction card decides to obtain a secure payment application from a secure payment application provider, such as MasterCard, over the Internet. The reader should understand that although there is repeated reference in the specification and Figures to MasterCard this is by way of example only.

[0020] As shown in FIG. 1, a provider, such as MasterCard (or an agent of MasterCard) has in its control one or more tamper-resistant security modules 10, which offer physical protection for the information stored inside the modules. These security modules each contain the following secret keys: 1) one or more translation keys that are used to translate between pseudo account numbers and “real” account numbers; 2) if secret-key authentication is used, one or more derivation keys that are used to re-create the card-unique secret cryptographic keys; and 3) if public-key authentication is used, one or more provider “root” private keys. The process, then, would preferably proceed as follows:

[0021] The cardholder contacts MasterCard's web site via the Internet.

[0022] The cardholder identifies himself/herself to MasterCard by providing, preferably under Secure Socket Layer (SSL) encryption known to those skilled in the art, the card account number, card expiration date, and card verification code or CVC2 from his/her MasterCard card. CVC2 refers to authenticating information that is issued with some payment cards. These cards have the account number printed on the signature panel of the card followed by a three or four digit value. This value is generated by the issuing bank using a secret cryptographic key, and can be verified using this same key. Payment card brands have varying names for the value:

[0023] MasterCard—Card Verification Code 2 (CVC2); American Express—Four-digit batch code (4DBC); and Visa—Card Verification Value 2 (CVV2). Supplying this value provides evidence that the person participating in a transaction had physical possession of the card at some point in time, because the value is not encoded on the magnetic stripe and thus not included in a normal transaction.

[0024] MasterCard verifies the CVC2 for the cards of those issuers for which MasterCard is provided (by secure means) the CVC2 keys. MasterCard may confirm the legitimacy of the other card data by obtaining a zero amount authorization from the issuer. MasterCard may obtain this authorization over its Banknet™ communications network.

[0025] After MasterCard has confirmed the legitimacy of the cardholder-provided card data, the secure payment application software is made available to the cardholder and may be downloaded over the Internet under SSL encryption. The software includes a secret cryptographic key that is unique to this card. If secret-key authentication is used, the secret key is preferably determinable from the card's “real” account number (i.e., the actual card payment account number issued by the cardholder's issuing bank). If public-key authentication is used, MasterCard provides a certificate that links the real account number with the corresponding public key, which certificate is signed by a MasterCard “root” private key. The software also includes the cardholder's “real” account number, and a “pseudo” account number that MasterCard may relate to the “real” account number.

[0026] The cardholder may provide a password to MasterCard prior to downloading the secure payment application or may select a password when the secure payment application is being installed on the cardholder's computer. If a password is provided or selected, the cardholder will thereafter be required to enter this password in order to activate the secure payment application.

[0027] If secret-key authentication is used, the card-unique secret key may be cryptographically computed from the card's “real” account number using a higher-level secret cryptographic key that is common to many or all account numbers. The higher-level secret cryptographic key preferably resides solely within physically-secure and tamper-resistant hardware devices (referred to as “security modules”) that are controlled by MasterCard or by acquirer institutions. If the secure payment application includes a card-unique private key (for public-key authentication), the associated certificate is signed using a MasterCard private “root” key that resides only in a relatively few security modules that are controlled directly by MasterCard or by trusted agents to whom MasterCard has delegated this certificate-signing function.

[0028] The pseudo account number has the same length as the “real” account number, consists solely of decimal digits, and begins with a valid identification number (e.g., a “5” for MasterCard). Therefore, the pseudo account number will appear to be a valid account number to merchants.

[0029] In order for an acquirer or MasterCard to be able to differentiate between a “real” account number and a pseudo account number, there must be an indication in the account number or in the transaction record of the type of account number being used. In one embodiment of the present invention, this indication is provided in the second digit of the pseudo account number, which acts as a special identifier. For example, for MasterCard cards, the second digit of an account number may be made a “9” to indicate a pseudo account number. In this case, the 16th digit of the account number, which is normally a check digit used to detect manual entry errors, is deleted to make room for the additional second digit.

[0030] In some cases, it may be possible that the transaction record may include data indicating that the account number is a pseudo account number.

[0031] MasterCard may periodically update the secure payment application.

[0032] If secret-key authentication is used, the following steps may be performed within a security module controlled by MasterCard or one of its agents to obtain a card-unique secret key to be included in the MasterCard secure payment application. The following steps assume the use of the DEA (Data Encryption Algorithm, which is a U.S. Government standard cryptographic algorithm) with a double-length key. They also assume that the MasterCard security module holds a secret high-level key called the Per-Card Key Derivation Key that consists of 16 bytes and is used with many or all card account numbers to cryptographically compute a card-unique secret key, called the Per-Card Key, given the card's 16-digit payment account number. The steps are:

[0033] 1. Considering the payment account number as 16 binary-coded-decimal digits of 4 bits each, DEA-encrypt these 64 bits using as the encryption key the left-most 8 bytes of the 16-byte Per-Card Key Derivation Key.

[0034] 2. DEA-decrypt the result of Step 1 using as the decryption key the right-most 8 bytes of the 16-byte Per-Card Key Derivation Key.

[0035] 3. DEA-encrypt the result of Step 2 using as the encryption key (again) the left-most 8 bytes of the 16-byte Per-Card Key Derivation Key.

[0036] 4. Use the result of Step 3 as the left-most 8 bytes of the unique Per-Card Key.

[0037] 5. DEA-encrypt the result of Step 3 using as the encryption key the left-most 8 bytes of the 16-byte Per-Card Key Derivation Key.

[0038] 6. DEA-decrypt the result of Step 5 using as the decryption key the right-most 8 bytes of the 16-byte Per-Card Key Derivation Key.

[0039] 7. DEA-encrypt the result of Step 6 using as the encryption key (again) the left-most 8 bytes of the 16-byte Per-Card Key Derivation Key.

[0040] 8. Use the result of Step 7 as the right-most 8 bytes of the 16-byte unique Per-Card Key, and place this key in the secure payment application in such a way that it will not be disclosed during the normal operation of this application.

[0041] If public-key authentication is used, the following steps may be performed within a security module controlled by MasterCard or one of its agents to provide a card-unique private key and a card-unique certificate for the corresponding public key, which private key and certificate are to be included in the MasterCard secure payment application:

[0042] 1. For a recognized public-key algorithm (e.g. RSA, Elliptic Curve), compute a unique private key and the corresponding public key using established security procedures.

[0043] 2. Using a recognized secure hash algorithm (e.g. SHA-1), hash, for example, (1) the just-generated public key for the card in question, (2) the pseudo account number for this card, (3) an appropriate date (to be optionally used to determine certificate expiration) and (4) the identity of the current MasterCard “root” key (in the event that this key should change).

[0044] 3. Using a recognized public key algorithm, and a MasterCard “root” private key, create a digital signature on the result of Step 2 (with appropriate padding).

[0045] 4. In the per-card secure payment application, place the just-generated private key in such a way that it cannot be disclosed in normal operation. Also place in this secure payment application a digital certificate consisting of (for example) (1) the card-unique public key, (2) the card's pseudo account number, (3) the above-indicated date, (4) the identity of the MasterCard “root” key used to sign the certificate, and (4) the above-described digital signature.

[0046] FIG. 2 a is a diagram of a system for conducting a secure payment over the Internet using the present invention with secret-key authentication of pseudo account numbers.

[0047] As shown in FIG. 2a, an acquirer 12 has in its control one or more tamper-resistant security modules, which offer physical protection for the information stored inside the modules. These security modules each contain one or more secret keys, the translation key or keys, that are used to translate between pseudo account numbers and “real” account numbers. Each of these modules also contain one or more higher-level secret keys, called the derivation key or keys, that are used to re-create the card-unique secret cryptographic keys.

[0048] The modules may be provided by MasterCard to the acquirer and may function similarly to the security modules currently installed in banks that operate Cirrus automatic teller machines (ATMs). MasterCard provides to the acquirer a security specification and/or software application, which the acquirer may make available to merchants that desire to accept MasterCard cards with pseudo account numbers. Although it is preferred for an acquirer to have a security module, it is not required. If a security module is not provided to an acquirer, the acquirer will be required to forward all pseudo account numbers to MasterCard for translation and authentication.

[0049] FIG. 2B is a diagram of a system for conducting a secure payment over the Internet using the present invention with public-key authentication of pseudo account numbers. As shown in FIG. 2b, the only significant difference with FIG. 2a is that a public-key pair is utilized. Like before, the acquirer 12 has in its control one or more tamper-resistant security modules 10, which offer physical protection for the information stored inside the modules. These security modules each contain one or more secret keys, i.e., the translation key or keys, that are used to translate between pseudo account numbers and “real” account numbers. Like above, the modules are provided by MasterCard to the acquirer and may function similarly to the security modules currently installed in banks that operate Cirrus automatic teller machines (ATMs). MasterCard provides to the acquirer a security specification and/or software application, which the acquirer may make available to merchants that desire to accept MasterCard cards with pseudo account numbers. Although it is preferred for an acquirer to have a security module, it is not required. If a security module is not provided to an acquirer, the acquirer will be required to forward all pseudo account numbers to MasterCard for translation and authentication.

[0050] FIG. 3 illustrates the process that may be performed within a security module to obtain the pseudo account number for a given “real” account number. The process utilizes the DEA with a double-length key. It is assumed that the security module holds a secret high-level key (the Account Number Translation Key) that consists of 16 bytes and is used with many or all card account numbers to obtain the pseudo account number that corresponds to each. It is assumed that the first three digits of the “real” account number occur unchanged in the pseudo account number with the digit “9” inserted between the first and second digits, and that the 16th digit (the check digit) of the “real” account number is ignored. The twelve digits from Digit 4 through Digit 15 of the “real” account number are encrypted and become digits 5 through 16 of the pseudo account number. This encryption is illustrated as function “E1” in FIG. 3a. This encryption method may use a methodology known as ‘DESX’ to maintain high security while minimizing the number of DEA operations that are required. The following defines possible steps to achieve the encryption:

[0051] 1. Select the 6 digits from positions 4 through 9 of the “real” account number (the 6 left-most of the 12 account-number digits to be encrypted). Represent each digit as a 4-bit binary-coded decimal value.

[0052] 2. Left-justify the 24 bits produced by Step 1 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘001’.

[0053] 3. Exclusive-or the result of Step 2 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0054] 4. DEA encrypt the result of Step 3 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0055] 5. Exclusive-or the result of Step 4 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0056] 6. Consider the result of Step 5 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001’, decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of the Step 5, this time selection only those 4h-bit digits with a value greater than binary ‘1001’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0057] 7. Select the 6 digits from positions 10 through 15 of the “real” account number (the 6 right-most of the 12 account-number digits to be encrypted). Represent each digit as a 4-bit binary-coded decimal value. Mod-10 add each of these 6 binary-coded-decimal digits to the corresponding binary-coded-decimal digit resulting from Step 6.

[0058] 8. Left-justify the 24 bits produced by Step 7 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘010’.

[0059] 9. Exclusive-or the result of Step 8 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0060] 10. DEA encrypt the result of Step 9 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0061] 11. Exclusive-or the result of Step 10 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0062] 12. Consider the result of Step 11 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001’, decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of Step 11, this time selection only those 4-bit digits with a value greater than binary ‘1001’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0063] 13. Mod-10 add each of the 6 binary-coded-decimal digits resulting from Step 12 to the corresponding binary-coded-decimal digit resulting from Step 1.

[0064] 14. Left justify the 24 bits produced by Step 13 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘011’.

[0065] 15. Exclusive-or the result of Step 14 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0066] 16. DEA encrypt the result of Step 15 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0067] 17. Exclusive-or the result of Step 16 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0068] 18. Consider the result of Step 17 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001’, decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of Step 17 , this time selection only those 4-bit digits with a value greater than binary ‘1001’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0069] 19. Mod-10 add each of the 6 binary-coded-decimal digits resulting from Step 18 to the corresponding binary-coded-decimal digit resulting from Step 7.

[0070] 20. Left-justify the 24 bits produced by Step 19 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘100’.

[0071] 21. Exclusive-or the result of Step 20 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0072] 22. DEA encrypt the result of Step 21 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0073] 23. Exclusive-or the result of Step 22 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0074] 24. Consider the result of Step 23 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001’ , decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of Step 23 , this time selection only those 4-bit digits with a value greater than binary ‘1001’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0075] 25. Mod-10 add each of the 6 binary-coded-decimal digits resulting from Step 24 to the corresponding binary-coded-decimal digit resulting from Step 13.

[0076] 26. Left-justify the 24 bits produced by Step 25 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘101’.

[0077] 27. Exclusive-or the result of Step 26 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0078] 28. DEA encrypt the result of Step 27 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0079] 29. Exclusive-or the result of Step 28 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0080] 30. Consider the result of Step 29 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001’, decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of Step 29, this time selection only those 4-bit digits with a value greater than binary ‘1001 ’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0081] 31. Mod-10 add each of the 6 binary-coded-decimal digits resulting from Step 30 to the corresponding binary-coded-decimal digit resulting from Step 19.

[0082] 32. Concatenate left-to right (1) four decimal digits consisting of the left-most 3 decimal digits of the “real” account number with the digit ‘9’ inserted between the first and second digit, with (2) the 6 decimal digits resulting from Step 25 , with (3) the 6 decimal digits resulting from Step 31. Use the resulting 16 decimal digits as the pseudo account number.

[0083] FIG. 3 b illustrates the process performed by a security module in the acquirer's facility to convert a pseudo account number (created from a “real” account number using the procedure described in FIG. 3a) back into its corresponding “real” account number. The process utilizes the DEA with a double-length key. It is assumed that the security module holds a secret high-level key (the Account Number Translation Key) that consists of 16 bytes and is used with many or all card account numbers to obtain the pseudo account number from “real” account numbers and vice-versa. It is assumed that the first three digits of the “real” account number occur unchanged in the pseudo account number with the digit “9” inserted between the first and second digits, and that 16th digit (the check digit) of the “real” account number is not included in the pseudo account number. Therefore to convert from a pseudo account number to a “real” account number it is necessary to decrypt Digit 5 through Digit 16 of the pseudo account number to provide Digit 4 through Digit 15 of the “real” account number. The decryption is illustrated as function “D1” in FIG. 3b. Digit 1 through Digit 3 of the “real” account number are obtained from Digit 1 through Digit 4 of the pseudo account number by discarding the second digit (always a ‘9’). Finally, the 16th digit of the “real” account number must be computed from the other 15 digits by applying an appropriate check-digit-generation algorithm. The translation process is as follows:

[0084] 1. Select the 6 digits from positions 5 through 10 of the pseudo account number (the 6 left-most of the 12 pseudo account-number digits to be decrypted). Represent each digit as a 4-bit binary-coded decimal value.

[0085] 2. Left-justify the 24 bits produced by Step 1 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘101’.

[0086] 3. Exclusive-or the result of Step 2 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0087] 4. DEA encrypt the result of Step 3 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0088] 5. Exclusive-or the result of Step 4 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0089] 6. Consider the result of Step 5 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001 ’ (decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of the Step 5, this time selection only those 4-bit digits with a value greater than binary ‘1001’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0090] 7. Select the 6 digits from positions 11 through 16 of the pseudo account number (the 6 right-most of the 12 account-number digits to be decrypted). Represent each digit as a 4-bit binary-coded decimal value. From each of these 6 binary-coded-decimal digits, subtract the corresponding binary-coded-decimal digit resulting from Step 6.

[0091] 8. Left-justify the 24 bits produced by Step 7 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘100’.

[0092] 9. Exclusive-or the result of Step 8 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0093] 10. DEA encrypt the result of Step 9 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0094] 11. Exclusive-or the result of Step 10 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0095] 12. Consider the result of Step 11 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001’, decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of Step 11, this time selection only those 4-bit digits with a value greater than binary ‘1001’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0096] 13. Mod-10 subtract each of the 6 binary-coded-decimal digits resulting from Step 12 from the corresponding binary-coded-decimal digit resulting from Step 1.

[0097] 14. Left-justify the 24 bits produced by Step 13 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘011 ’.

[0098] 15. Exclusive-or the result of Step 14 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0099] 16. DEA encrypt the result of Step 15 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0100] 17. Exclusive-or the result of Step 16 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0101] 18. Consider the result of Step 17 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001’, decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of Step 17 , this time selection only those 4-bit digits with a value greater than binary ‘1001’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0102] 19. Mod-10 subtract each of the 6 binary-coded-decimal digits resulting from Step 18 from the corresponding binary-coded-decimal digit resulting from Step 7.

[0103] 20. Left-justify the 24 bits produced by Step 19 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘010’.

[0104] 21. Exclusive-or the result of Step 20 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0105] 22. DEA encrypt the result of Step 21 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0106] 23. Exclusive-or the result of Step 22 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0107] 24. Consider the result of Step 23 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001’, decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of Step 23 , this time selection only those 4-bit digits with a value greater than binary ‘1001’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0108] 25. Mod-10 subtract each of the 6 binary-coded-decimal digits resulting from Step 24 from the corresponding binary-coded-decimal digit resulting from Step 13.

[0109] 26. Left-justify the 24 bits produced by Step 25 in a 64-bit field, where the 37 bits to the immediate right of these bits are all set to binary zero, and the three right-most bits of the 64-bits are set to binary ‘001’.

[0110] 27. Exclusive-or the result of Step 26 with the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0111] 28. DEA encrypt the result of Step 27 using as the key the right-most 8 bytes of the Account Number Translation Key.

[0112] 29. Exclusive-or the result of Step 28 with (again) the left-most 8 bytes (64 bits) of the Account Number Translation Key.

[0113] 30. Consider the result of Step 29 as 16 hexadecimal digits. Starting with the left-most digit, select those digits with the value of ‘9’ or less until 6 such digits (from the binary set ‘0000’ through ‘1001’, decimal 0 through 9) have been selected. If fewer then 6 such digits were found, select the remaining digits by re-scanning the result of Step 23, this time selection only those 4-bit digits with a value greater than binary ‘1001’ (decimal ‘9’), and subtract binary ‘1010’ (decimal ‘10’) from each. This process produces 6 binary-coded-decimal digits.

[0114] 31. Mod-10 subtract each of the 6 binary-coded-decimal digits resulting from Step 30 from the corresponding binary-coded-decimal digit resulting from Step 19.

[0115] 32. Concatenate, left-to-right, (1) the first four digits of the pseudo account number with the second digit (the ‘9’) discarded (thus providing three digits) with (2) the 6 decimal digits resulting from Step 25 with (3) the 6 decimal digits resulting from Step 31. Compute the 16th (right-most) digit by applying the check-digit-generation algorithm to the 15 decimal digits resulting from the concatenation. The resulting 16 digits are the “real” account number.

[0116] FIGS. 4 a and 4b illustrate the steps that are performed when the cardholder contacts and places an order with a merchant on the Internet and the merchant requests an interchange authorization from an acquirer. It is assumed that the cardholder has enrolled in the MasterCard secure payment program and has installed the MasterCard secure payment application on his/her computer.

[0117] The cardholder contacts a merchant on (for example) the Internet and informs the merchant that he/she wishes to make a purchase.

[0118] The merchant responds by sending to the cardholder a merchant identification number (“MID”) that has been given to it by its acquiring bank (which bank ensures that it gives a unique merchant identification number to each of its merchants), along with a transaction sequence number (“TSN”) that is unique to this transaction. (This response is presumably generated within merchant software that the merchant obtained, for example, (1) from its acquiring bank, and that the acquiring bank had obtained from MasterCard, or (2) from the MasterCard Web site, or (3) from its software vendor, and that this vendor had obtained from MasterCard.) It is assumed that these are decimal numbers and that neither exceeds 8 digits.

[0119] The cardholder executes the MasterCard secure payment application software (if it is not already executing) and enters his/her password.

[0120] The application may display the cardholder's “real” and pseudo account numbers to the cardholder. The Internet merchants, however, never see the “real” account number.

[0121] The application concatenates the merchant identification number and the transaction sequence number (shown in FIGS. 4a and 4b as function “C”), then either:

[0122] 1. With reference to FIG. 4a, when the cardholder uses secret-key authentication, the cardholder generates a Message Authentication Code (“MAC”) on the concatenated result, using the unique Per-Card Key placed by MasterCard in the secure payment application (shown in FIG. 4a as function “E2”). As an example of the generation of the MAC, the merchant identification number and the transaction sequence number, represented as binary-coded-decimal, are concatenated, and padded to the right with zeros to produce 16 hexadecimal digits. This is DEA encrypted using, as the key, the left 8-bytes of the Per-Card Key. This result is DEA decrypted using, as the key, the right 8 bytes of the Per-Card Key, and this second cryptographic result is DEA encrypted using, as the key, the left 8-bytes of the Per-Card Key. Finally the MAC itself is produced by taking the left-most 4 bytes of this 8-byte final result, discarding the right-most 4 bytes. Or:

[0123] 2. With reference to FIG. 4b, when the cardholder uses public-key authentication, the cardholder creates a digital signature on the concatenated result of the merchant identification number and the transaction sequence number further concatenated with the transaction amount agreed to by the cardholder (all with appropriate padding) using the card-unique private key placed in the application by MasterCard (or its agent).

[0124] The MasterCard secure payment application then sends to the merchant, using SSL encryption, the following data:

[0125] 1. the cardholder's pseudo account number alone (secret-key authentication) or the card-unique digital certificate (public-key authentication) that includes the card's pseudo account number;

[0126] 2. the cardholder's card expiration date;

[0127] 3. the merchant identification number and transaction sequence number as received from the merchant;

[0128] 4. the MAC (secret-key authentication) or the digital signature (public-key authentication) generated by the secure payment application;

[0129] 5. the transaction amount agreed to by the cardholder.

[0130] In some cases, the secure payment application may also send data in the transaction record indicating that the account number transmitted is a pseudo account number.

[0131] The merchant, using the MasterCard-application software, verifies that the merchant identification number and the transaction sequence number are the correct numbers for this transaction.

[0132] If the transaction uses public-key authentication (FIG. 4b), the merchant, using the MasterCard-application software:

[0133] 1. Selects the MasterCard “root” public key indicated by the “root” key identifier in the card's digital certificate (which public keys are included in the MasterCard application software).

[0134] 2. Uses this “root” public key to authenticate the card's digital certificate.

[0135] 3. Uses the card's public key to authenticate the appropriate transaction data.

[0136] 4. Either (a) rejects the transaction if either authentication process fails, or (b) logs all of the data related to the certificate and the transaction signature (so that the merchant can subsequently demonstrate that it successfully verified the certificate and signature).

[0137] The merchant verifies that the pseudo account number starts with a “5”. The merchant may also verify that the second digit is a “9” for a MasterCard pseudo account number.

[0138] The merchant may approve the transaction without authorization if that is its practice or it may pass the pseudo account number and card expiration date to the acquiring bank. If secret-key authentication is used (see FIG. 4a), the merchant additionally passes to the acquiring bank the merchant identification number, transaction sequence number, and MAC.

[0139] The transaction amount passed from the cardholder to the merchant may be different from the transaction amount passed from the merchant to the acquirer. Therefore, the latter amount is referred to as “authorization amount” in FIGS. 4a and 4b.

[0140] The acquirer receiving the authorization request from the merchant recognizes that it contains a pseudo account number (by the ‘9’ as the second digit, and/or by the inclusion of the fields not found in a conventional authorization request) and sends to its MasterCard-provided security module the pseudo account number. If secret-key authentication is performed, the acquirer additionally sends to the security module (a) the merchant identification number, (b) the transaction sequence number, and (c) the MAC produced by the cardholder's secure application.

[0141] Upon receipt of this data, the security module cryptographically processes the pseudo account number to produce the “real” account number as described above with reference to FIG. 3b. (The translation is shown in FIGS. 4a and 4b as using function “D1”.)

[0142] If secret-key authentication is required (see FIG. 4a), the security module additionally performs the following steps:

[0143] 1. Generates the Per-Card Key, unique to the card of this transaction, using the “real” account number and the Per-Card Key Derivation Key as defined previously. (The generation of the Per-Card Key is shown in FIG. 4a as using function “E3”.)

[0144] 2. Uses this just-derived key to create a MAC on the merchant identification number and the transaction sequence number, as defined previously.

[0145] 3. Compares this generated MAC with the MAC given to it with the transaction data, and rejects the transaction if the two versions of the MAC are not identical.

[0146] 4. If the two versions of the MAC are identical, outputs the “real” account number.

[0147] Once the acquirer has obtained the “real” account number from the security module, it combines this with the expiration date from the transaction data. The acquirer may process the resulting transaction internally in its own facility if it is a provider of such processing services, or it may pass the transaction on to MasterCard over Banknet communication lines for MasterCard to send to the issuer in a conventional mode.

[0148] The response received by the acquirer from the issuer is identical in all respects to conventional processing, and provides an approval or rejection based on the “real” account number.

[0149] If the acquirer passes the account number to the merchant as part of its response, it must first convert the “real” account number back into a pseudo account number using the appropriate cryptographic key stored in the security module, and using the previously-discussed process.

[0150] FIG. 5 illustrates the process of clearing a transaction. The merchant sends all the transactions to the acquirer at the end of the day or periodically during the day. Each of these transactions includes all of the conventional MasterCard transaction details, except that they may contain a pseudo account number rather than a “real” account number. The acquirer takes all of the pseudo account numbers from these transactions and processes them through the MasterCard-provided security module, thus converting pseudo account numbers to “real” account numbers. The acquirer then processes the transactions internally or routes them to MasterCard International for clearing to the issuer in a conventional manner.

[0151] FIG. 6 illustrates how charge-backs, retrieval requests, etc., are processed in the MasterCard interchange. The figure shows that both the acquirer and the issuer have security modules 10. However, the issuer need not have a security module unless it will take cardholder inquiries over the Internet and unless the cardholder's computer communicates with the issuer by outputting a pseudo account number rather than a “real” account number. In this situation the issuer needs a security module in order to be able to convert the pseudo account number to the “real” account number. The issuer does not need a security module if the cardholder communicates with the issuer through postal mail.

[0152] The acquirer may have a security module in order to be able to process a transaction as a second presentment or retrieval request fulfillment from a merchant, where the merchant can only reference the transaction with a pseudo account number. Therefore the MasterCard-provided security module at the acquiring bank's facility needs the capability to translate from “real” account numbers to pseudo account numbers as well as from pseudo account numbers to “real” account numbers.

[0153] The transactions that go through MasterCard will be routed through Banknet with the “real” account number and not the pseudo account number. If secret-key authentication is used, it may be necessary for the acquirer to confirm that the transaction sequence number is unique for the merchant in question. If public-key authentication is used, it may be necessary for the merchant to produce the card's digital certificate, its signature, the cardholder-agreed transaction amount, the merchant identification number and the transaction sequence number, so that it can demonstrate that it actually verified the certificate and signature.

[0154] When public-key authentication is used, the above discussion considers a one-level key hierarchy in which MasterCard itself directly signs the certificate for every card. However a multi-level hierarchy is also possible. For example, MasterCard might sign a certificate for each of its issuers, and the issuer would in turn sign the certificates for the cards it issued. This would be an example of a two-level hierarchy.

[0155] Advantageously, the present invention provides enhanced security for the use of payment account numbers over the Internet. With the present invention, if one or more pseudo account numbers were to be stolen from a merchant, the stolen pseudo account numbers could not be used to conduct fraudulent transactions because transactions based on pseudo account numbers are preferably cryptographically authenticated using a secret key that is unique for each account number. This secret key is located only within the cardholder's secure payment application. Furthermore, a pseudo account number can not be used to make conventional MasterCard transactions (at point-of-sale terminals, for example) because the pseudo account number does not disclose the “real” account number.

[0156] The foregoing merely illustrates the principles of the invention. It will thus be appreciated that those skilled in the art will be able to devise numerous systems and methods which, although not explicitly shown or described herein, embody the principles of the invention and thus within the spirit and scope of the invention.

Claims

1. A method of conducting a transaction by a purchaser over a communications network, comprising: (a) assigning to said purchaser a first payment account number having a status which changes over time; (b) providing a second payment account number associated with said first payment account number, said second payment account number not being a transaction number and having an encryption key assigned thereto; (c) requesting authorization for payment of said transaction with said second payment account number and not said first payment account number; (d) identifying said purchaser's first payment account number in response to said authorization request; and (e) responding to said authorization request based upon said status of said first payment account number at the time of the transaction.

2. The method of claim 1, wherein said authorization request includes a cryptographic code based on said encryption key, and wherein said response to said authorization request is further based on said cryptographic code.

3. The method of claim 2, wherein said status is a function of the credit balance available for use by said purchaser, which credit balance changes over time as a result of the purchases made by the purchaser.

4. A method of conducting a transaction by a purchaser over a communications network, comprising: (a) assigning to said purchaser a first payment account number having a status which changes over time; (b) providing said purchaser with a secure payment application which includes a cryptographic key that is unique to said account number and a pseudo account number having the same length as and associated with said first payment account number; (c) providing said purchaser with merchant data based on the transaction; (d) generating a message authentication code as a function of at least said merchant data and said cryptographic key; (e) providing said merchant said pseudo account number and said message authentication code and not said first payment account number; (f) verifying that said merchant data is the correct data for the transaction; (g) requesting an authorization for payment of said transaction, said authorization request not including said first payment account number but including said pseudo account number; (h) recognizing said pseudo account number and cryptographically processing said pseudo account number to produce said first payment account number; and (i) responding to said authorization request based on the status of said first payment account number, and passing said response back without transmission of said first payment account number.

5. The method of claim 4 wherein said pseudo account number is indicated to be different from said first payment account number by a special identifier within the pseudo account number.

6. The method of claim 4 wherein said pseudo account number is indicated to be such by data within a transaction record.

7. The method of claim 4 wherein said cryptographic key is a secret key.

8. The method of claim 4 wherein said cryptographic key is a private key and said secure payment application further includes a card-unique certificate for the corresponding public key and said message authentication code comprises a digital signature generated by said secure payment application.

9. The method of claim 4 wherein said pseudo account number is obtained by encrypting the associated first payment account number utilizing DESX methodology.

10. The method of claim 4 wherein said pseudo account number is converted back into its associated first payment account number utilizing DEA with a double-length key.