System for authorizing transactions using specially formatted smart cards

• US 20020147907A1
• Filed: 04/06/2001
• Published: 10/10/2002
• Est. Priority Date: 04/06/2001
• Status: Abandoned Application

• Current Assignee: Bruce Ross
• Original Assignee: Bruce Ross
• Inventors: Ross, Bruce
• Application Number:
  US09/828,714
• Publication Number:
  US 20020147907A1
• Time in Patent Office: Days
• US Class Current: 713/159
• CPC Class Codes: G06Q 20/045 using payment protocols involving tickets
• 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/346 Cards serving only as information carrier of service
• CPC Class Codes: G06Q 20/357 Cards having a plurality of specified features
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G07B 15/00 Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points handling coins or valuable papers, e.g. banknotes, G07D; apparatus for vending or hiring articles or services activated by coins, credit cards, paper currency or the like G07F7/00, G07F17/00
• CPC Class Codes: G07F 17/42 for ticket printing or like apparatus , e.g. apparatus for dispensing of printed paper tickets or payment cards
• 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: G07G 1/14 Systems including one or more distant stations co-operating with a central processing unit data transmission in general H04L; telemetry systems for selectively calling a substation from a main station H04Q9/00

Abstract

A transaction system includes the use of a fixed data structure that allows multiple point-of-sale systems to recognize and access a transaction card regardless of upper level user interfaces. More specifically, a smart card includes a memory with a defined data file structure, wherein the data file structure includes at least one read only field, at least one encrypted read/write field, and at least one non-encrypted read/write field. The read only field preferably includes at least one of a manufacturer identification field, a card identification field and a theater identification field. The encrypted read/write field preferably includes at least one of a transaction log field, an issue date field, a first dollar value field, a second dollar value field, a first point value field, a second point value field and a ticket storage field. The non-encrypted read/write field preferably includes at least one of a first dollar value display field, a second dollar value display field, a first point value display field, a second point value display field and a user defined field. The smart card is utilized in a transaction system the includes at least one smart card authorization device, a communication interface, and a transaction verification server. The smart card authorization device interacts with a defined data file structure provided on a smart card of the type described above.

Claims

1. A smart card including a memory with a defined data file structure, said data file structure comprising:

at least one read only field;

at least one encrypted read/write field; and

at least one non-encrypted read/write field.

2. A smart card as claimed in claim 1, wherein the read only field includes at least one of a manufacturer identification field, a card identification field and a theater identification field.

3. A smart card as claimed in claim 1, wherein the encrypted read/write field includes at least one of a transaction log field, an issue date field, a first dollar value field, a second dollar value field, a first point value field, a second point value field and a ticket storage field.

4. A smart card as claimed in claim 1, wherein the non-encrypted read/write field includes at least one of a first dollar value display field, a second dollar value display field, a first point value display field, a second point value display field and a user defined field.

5. A transaction system including:

at least one smart card authorization device;

a communication interface; and

a transaction verification server;

wherein the smart card authorization device interacts with a defined data file structure provided on a smart card.

6. A transaction system as claimed in claim 5, wherein said data file structure comprises:

at least one read only field;

at least one encrypted read/write field; and

at least one non-encrypted read/write field.

7. A transaction system as claimed in claim 6, wherein the read only field includes at least one of a manufacturer identification field, a card identification field and a theater identification field.

8. A transaction system as claimed in claim 6, wherein the encrypted read/write field includes at least one of a transaction log field, an issue date field, a first dollar value field, a second dollar value field, a first point value field, a second point value field and a ticket storage field.

9. A transaction system as claimed in claim 6, wherein the non-encrypted read/write field includes at least one of a first dollar value display field, a second dollar value display field, a first point value display field, a second point value display field and a user defined field.

10. A transaction system comprising:

at least one smart card including a memory with a defined data structure, wherein said defined data structure includes at least one read only field, at least one encrypted read/write field, and at least one non-encrypted read/write field; and

read/write means for reading and writing data to the memory of the smart card, wherein said read/write means includes an application program interface that utilizes a predefined set of commands to control the reading and writing of data to the memory card based on the defined data structure.

11. A transaction system as claimed in claim 10, wherein the read only field includes at least one of a manufacturer identification field, a card identification field and a theater identification field.

12. A transaction system as claimed in claim 10, wherein the encrypted read/write field includes at least one of a transaction log field, an issue date field, a first dollar value field, a second dollar value field, a first point value field, a second point value field and a ticket storage field.

13. A transaction system as claimed in claim 10, wherein the non-encrypted read/write field includes at least one of a first dollar value display field, a second dollar value display field, a first point value display field, a second point value display field and a user defined field.

14. A transaction system as claimed in claim 10, wherein the read/write means further comprises means for encrypting and decrypting data read from and written to said encrypted data field.

15. A transaction system as claimed in claim 10, wherein the predefined commands include a set of general commands, a set of read commands and a set of write commands.