Method for generating customer secure card numbers subject to use restrictions by an electronic card

• US 6,805,288 B2
• Filed: 09/21/2001
• Issued: 10/19/2004
• Est. Priority Date: 05/15/2000
• Status: Expired due to Term

• Current Assignee: Jacob Y. Wong, Larry Routhenstein, Roy L Anderson, William R. Bryant
• Original Assignee: Jacob Y. Wong, Larry Routhenstein, Roy L Anderson, William R. Bryant
• Inventors: Routhenstein, Larry, Anderson, Roy L., Bryant, William R., Wong, Jacob Y.
• Primary Examiner(s): Le, Thien M.
• Assistant Examiner(s): TAYLOR, APRIL ALICIA
• Application Number:
  US09/960,714
• Publication Number:
  US 20030034388A1
• Time in Patent Office: 1,124 Days
• Field of Search: 235/375, 235/380, 235/382, 705/18, 705/39, 705/44
• US Class Current: 235/380
• CPC Class Codes: G06K 19/06196 Constructional details
• CPC Class Codes: G06K 19/06206 the magnetic marking being emulated
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• 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/3415 Cards acting autonomously as pay-media
• CPC Class Codes: G06Q 20/3576 Multiple memory zones on card
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/383 Anonymous user system
• CPC Class Codes: G06Q 20/4093 Monitoring of device authentication
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system

Abstract

A method for providing secure transactions generates a Secure Card Number (“SCN”) for a first entity that is transferred with a first entity identifier to a second entity and then to a money source that verifies that the transaction is valid by use of the first entity identifier and the SCN. The SCN includes a Transaction Information Block (“TIB”) used for invoking one or more restrictions on use of the SCN, a Counter Block, and an encrypted Personal Identification Number (“PIN”) Block. The SCN is transferred to the money source in an account number or a non-account data field. The TIB can be used by the money source to determine which of multiple account numbers associated with the first entity should be used for the first transaction. The money source can also use the TIB to determine whether the device which generated the SCN has a changed status condition, such as a low battery condition or an invalid user entry status. The low battery condition may be determined either by a diagnostic program or by an empirical record of the number of transactions presented for authorization.

Claims

1. A method for providing one or more secure transactions between a first entity and at least one additional entity, comprising the steps of:

(1) using an electronic card to generate a Secure Card Number (“

SCN”

) for the first entity, wherein the SCN is comprised of;

(a) a Transaction Information Block (“

TIB”

);

(b) a Counter Block; and

(c) an encrypted Personal Identification Number (“

PIN”

) Block;

(2) transferring the SCN and a first entity identifier to a second entity in a first transaction;

(3) transferring the SCN and the first entity identifier from the second entity to a money source; and

(4) verifying that the first transaction is valid with the money source by use of the first entity identifier and the SCN;

wherein the TIB can be used for invoking one or more restrictions on use of the SCN; and

wherein the TIB is used by the money source to determine whether the device which generated the SCN has changed status condition.

2. A device as recited in claim 1, wherein the changed status condition is a low battery condition.

3. A device as recited in claim 1, wherein the low battery condition is detected by a diagnostic program.

4. A device as recited in claim 1, wherein the low battery condition is detected by using an empirical record of the number of transactions presented for authorization.

5. A device as recited in claim 4, wherein the determination of the low battery condition is made by the electronic card.

6. A device as recited in claim 5, wherein the empirical record is kept by the electronic card.

7. A device as recited in claim 5, wherein the determination of the low battery condition is made by the money source.

8. A device as recited in claim 7, wherein the empirical record is kept by the money source.

9. A device as recited in claim 1, wherein the changed status condition is an invalid user input status.

10. A method for providing one or more secure transactions between a first entity and at least one additional entity, comprising the steps of:

(1) using an electronic card to generate a Secure Card Number (“

SCN”

) for the first entity, wherein the SCN is comprised of;

(a) a Transaction Information Block (“

TIB”

);

(b) a Counter Block; and

(c) an encrypted Personal Identification Number (“

PIN”

) Block;

(2) transferring the SCN and a first entity identifier to a second entity in a first transaction;

(3) transferring the SCN and the first entity identifier from the second entity to a money source; and

(4) verifying that the first transaction is valid with the money source by use of the first entity identifier and the SCN;

wherein the TIB can be used for invoking one or more restrictions on use of the SCN; and

wherein a set of valid SCNs are pre-calculated and stored on the electronic card.