Message format for communicating financial information

• US 20020097715A1
• Filed: 08/01/2001
• Published: 07/25/2002
• Est. Priority Date: 07/27/2000
• Status: Abandoned Application

• Current Assignee: LVWA LLC
• Original Assignee: LVWA LLC
• Inventors: Roerick, Michael L.
• Application Number:
  US09/920,546
• Publication Number:
  US 20020097715A1
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G07F 19/20 Automatic teller machines [ATMs]
• CPC Class Codes: G07F 19/202 Depositing operations within ATMs depositing in general G07D11/00
• CPC Class Codes: G07F 19/203 Dispensing operations within ATMs dispensing in general G07D11/00
• CPC Class Codes: G07F 19/211 Software architecture within ATMs or in relation to the ATM network

Abstract

A transmission message having a fixed terminal information segment with a field defining the format of a variable field authorization segment, and with a field defining the format of a variable field service payload segment. The fixed terminal information segment has other fields defining parameters of a terminal from which the transmission message is transmitted. The authorization segment has fields defining a method of payment by a user of the terminal. The service payload segment has fields defining the goods or services desired to be purchased by the user.

Claims

1. A message format for use in communicating information, comprising:

a plurality of message segments, each message segment having one or more data fields;

a first message segment having at least one data field storing data that does not change for each communication of financial information;

a second message segment having an arrangement of data fields that store data as a function of the type of financial transaction, and said arrangement of data fields changes for different financial transactions; and

said first message segment having a field that defines a format of the data fields of said second message segment, whereby the format of said second message segment is variable and changes as a function of the type of financial transaction communicated.

2. The message format of claim 1, further including a third message segment having a plurality of fields, an arrangement of the fields of said third segment being a function of the type of goods/service to purchase, and further including at least one field in said first message segment defining a format of the arrangement of data fields in said third segment.

3. The message format of claim 1, wherein said first message segment has a data field that defines a terminal from which a user of the terminal initiates a financial transaction, and said second message defines a method of payment chosen by the user of the terminal.

4. The message format of claim 2, wherein said third message segment includes at least one data field relating to a product or service being purchased by the user via the terminal.

5. The message format of claim 3, wherein one data field of said second message segment is adapted for holding data indicating that a chosen method of payment by the user is currency.

6. The message format of claim 1, wherein said second message segment includes different numbers of data fields as a function of the methods of payments allowed by the terminal, and the data in the respective fields is different.

7. A message format for use in communicating financial information, comprising:

a first message segment, a second message segment and a third message segment;

said first message segment having one or more data fields storing data for identifying a terminal from which a financial transaction is communicated using said message format, said first message segment having at least one data field defining an arrangement of data fields of said second message segment, and said first message segment having at least one data field defining an arrangement of data fields of said third message segment;

said second message segment for carrying data in respective fields thereof relating to a method of payment selected by a user using the terminal; and

said third message segment for carrying data in respective fields thereof relating to an identification of goods or services selected by the user of the terminal.

8. The message segment of claim 7, wherein a data field of said first message segment specifies one of a method of payment selected from a group consisting of ATM card, credit card, debit card, smart card or cash.