Requesting execution of instructions on accounts in ABDS system

• US 6,952,773 B2
• Filed: 02/01/2003
• Issued: 10/04/2005
• Est. Priority Date: 08/04/2000
• Status: Expired due to Term

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: Wheeler, Lynn Henry, Wheeler, Anne M.
• Primary Examiner(s): Barrón, Gilberto
• Assistant Examiner(s): Zand, Kambiz
• Application Number:
  US10/248,620
• Publication Number:
  US 20030115463A1
• Time in Patent Office: 976 Days
• Field of Search: 713155-157, 713/170, 713/176, 380/284
• US Class Current: 713/170
• CPC Class Codes: G06F 21/32 using biometric data, e.g. fingerprints, iris scans or voiceprints
• CPC Class Codes: G06F 2221/2113 Multi-level security, e.g. mandatory access control
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/0855 involving a third party
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G06Q 20/3558 Preliminary personalisation for transfer to user
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/3676 Balancing accounts
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: G06Q 20/3825 Use of electronic signatures
• CPC Class Codes: G06Q 20/3829 involving key management
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/388 using mutual authentication without cards, e.g. challenge-response
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G06Q 20/403 : Solvency checks
• CPC Class Codes: G06Q 20/40975 : using encryption therefor
• CPC Class Codes: G06Q 50/188 : Electronic negotiation
• CPC Class Codes: G07F 7/0886 : the card reader being portable for interacting with a POS or ECR in realizing a payment transaction
• CPC Class Codes: G07F 7/1008 : Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: G07F 7/1016 : Devices or methods for securing the PIN and other transaction-data, e.g. by encryption arrangements for secret communication, see H04L9/00
• CPC Class Codes: H04L 2209/42 : Anonymization, e.g. involving pseudonyms
• CPC Class Codes: H04L 2209/56 : Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/0428 : wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0442 : wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/062 : for key distribution, e.g. centrally by trusted party cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819
• CPC Class Codes: H04L 63/0823 : using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/083 : using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/12 : Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 9/321 : involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3247 : involving digital signatures

Abstract

A method of requesting an account authority to execute an instruction with regard to an account maintained by the account authority includes, (a) for a first account, composing an electronic message including, an instruction regarding the first account and a first unique identifier by which a first account authority identifies the first account, digitally signing the electronic message using a private key of a public-private key pair for which the public key is associated by the first account authority with the first account, and sending the electronic message and digital signature to the first account authority, and (b) for a second account digitally signing a similar message of instruction using the same private key of the public-private key pair, and sending the electronic message and digital signature to the second account authority.

Claims

1. A method of requesting a plurality of account authorities to execute a respective instruction with regard to a respective account maintained by each respective account authority and for which each account authority has previously associated in a computer database the same public key of a public-private key pair with a respective unique identifier of the respective account such that the public key is retrievable by each respective account authority based on the respective unique identifier comprising the steps of:

(a) for a first account maintained by a first account authority,

(i) composing a first electronic message including,

(A) an instruction regarding the first account, and

(B) a first unique identifier by which the first account authority identifies the first account from accounts maintained by the first account authority,

(ii) digitally sing the first electronic message using the private key of the public-private key pair, and

(iii) sending the electronic message and digital signature to the first account authority over a communications medium, and

(b) for a second account maintained by a second account authority,

(i) composing a second electronic message including,

(A) an instruction regarding the second account, and

(B) a second unique identifier by which the second account authority identifies the second account from accounts maintained by the second account authority,

(ii) digitally signing the second electronic message using the same private key of the public-private key pair, and

(iii) sending the electronic message and digital signature to the second account authority over a communications medium.

2. The method of claim 1, wherein the public key is included in at least one of the messages.

3. The method of claim 1, wherein the unique identifiers comprises the associated public key.

4. The method of claim 1, wherein each of the respective unique identifiers comprises an account number of the respective account.

5. The method of claim 1, further comprising the step of composing one of the electronic messages external to a device possessing the private key used to generate the corresponding digital signature.

6. The method of claim 5, further comprising the step of calculating a hash value for the electronic message external to the device.

7. The method of claim 5, further comprising the step of inputting the electronic message into the device for generation of the digital signature.

8. The method of claim 1, further comprising the step of composing one of the electronic messages within a device possessing the private key used to generate the corresponding digital signature.

9. The method of claim 8, further comprising the step of calculating a hash value for the electronic message within the device.

10. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises a personal computer.

11. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic me sage comprises a cell phone.

12. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises a PDA.

13. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises an electronic key.

14. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises a dongle.

15. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises a subcutaneous implant.

16. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises a secure chip.

17. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises jewelry.

18. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises an IC card.

19. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises a credit card.

20. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises a debit card.

21. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises a security card.

22. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message comprises an ID badge.

23. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message transmits the digital signature through physical contact with a device interface.

24. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message plugs into device interface for transmission of the digital signature.

25. The method of claim 23, wherein the device is swiped through the device interface.

26. The method of claim 1, wherein a device possessing the private key used to generate a digital signature of an electronic message transmits the digital sign to a device interface without physical contact therewith.

27. The method of claim 26, wherein the device transmits the digital signature through wireless communication.

28. The method of claim 26, wherein the device transmits the digital signature trough an RF transmission.

29. The method of claim 1, wherein the communications medium is open and insecure.

30. The method of claim 1, wherein the communications medium comprises the Internet.

31. The method of claim 1, wherein the respective electronic messages are not encrypted.

32. The method of claim 1, wherein the respective electronic message are encrypted.

33. The method of claim 1, wherein the respective electronic messages includes no personally-identifying information regarding an owner of the account.

34. The method of claim 1, wherein the respective electronic messages includes no account-identifying information other than the respective unique identifier of the respective account.

35. The method of claim 1, wherein the unique identifiers are identical.

36. The method of claim 1, wherein the unique identifiers are different.

37. A method of requesting a plurality of account authorities to execute a respective instruction with regard to a respective account maintained by each respective account authority and for which each account authority has previously associated in a computer database a same public key of a public-private key pair with a respective unique identifier of the respective account such that the public key is retrievable based on the respective unique identifier, and wherein the corresponding private key of the public-private key pair is not known or accessible by the plurality of account authorities, comprising the steps of:

(a) for a first account,

(i) composing a first electronic message including,

(A) an instruction regarding the first account, and

(B) a first unique identifier by which a first account authority identifies the first account from accounts maintained by the fit account authority,

(ii) digitally signing the first electronic message using the corresponding private key, and

(iii) sending the electronic message and digital signature to the first account authority over a communications medium, and

(b) for a second account,

(i) composing a second electronic message including,

(A) an instruction regarding the second account, and

(B) a second unique identifier by which a second account authority identifies the second account from accounts maintained by the second account authority,

(ii) digitally signing the second electronic message using the corresponding private key, and

(iii) sending the electronic message and digital signature to the second account authority over a communications medium.

38. A method of requesting a plurality of account authorities to execute a respective instruction with regard to a respective account maintained by each respective account authority and for which each account authority has previously associated in a computer database a same public key of a public-private key pair with a respective unique identifier of the respective account such that the public key is retrievable based on the respective unique identifier, comprising the steps of:

(a) for a first account,

(i) composing a first electronic message including,

(A) an instruction regarding the first account, and

(B) a first unique identifier by which a first account authority identifies the first account from accounts maintained by the fit account authority,

(ii) digitally signing the first electronic message using the private key of the public-private key pair, the private key securely residing only within a device used to digitally-sign the first electronic message, and

(iii) sending the electronic message and digital signature to the first account authority over a communications medium, and

(b) for a second account,

(i) composing a second electronic message including,

(A) an instruction regaling the second account, and

(B) a second unique identifier by which a second account authority identifies the second account from accounts maintained by the second account authority,

(ii) digitally signing the second electronic message using the same private key securely residing within the device, and

(iii) sending the electronic message and digital signature to the second account authority over a communications medium.