Gasboy CFN Series - Manual (Page 24)

Card Formats Service Card Format
Page 20 MDE-4602 Gasboy CFN Series Card Encoding Manual · November 2006
Service Card Format
If you have a CFN 4 and Mag Card encoder, you can encode and use Service cards. A Service
card enables the cardholder to get the status, set a limited number of configurations, and reboot
the CFN system from a reader.
The site recognizes the card as a Service card when two field separators follow the system ID
and the digit 6 follows the expiration date or the field separator after the account number, if no
expiration date is configured.
The layout for Service cards is -ssssss--ccccccccccccccccccc-yymm6, where:
• “-” is a field separator.
• “ssssss” is a four- to six-digit system ID number.
• “--” are two field separators; these and the digit 6 at the end of the card indicate that this is
a service card.
• “ccccccccccccccccccc” contains up to 19 digits of account information. This entire area
can be used for a string of information up to 19 digits; or it can be split into sub-fields, the
total of which does not exceed 19 digits. For example, if you use 19 digits for the card
number, you cannot define any other field. Usually this 19-digit area is broken down as
follows:
- The first field is a four- to six-digit card number.
- Fields after the first field are broken down into vehicle, employee, account number,
department, or any other specification, up to a total of 19 digits.
• “-” is a field separator.
• “yymm” is a four-digit expiration date. This field can also be of two digits (yy) only.
Code Card Format
If you have a site controller configured to accept Code cards, you can encode Code cards. All
American Banker’s Association (ABA) track-two cards follow the standard format; start
sentinel, data (field separators, numbers, A's, E's, and so on), end sentinel, and a Longitudinal
Redundancy Check (LRC) checksum. The start sentinel, end sentinel, and the LRC checksum
are encoded automatically by the card encoding equipment, such as a Gasboy MCE 300 Mag
Card Encoder. To encode a Code card, you must have two start sentinels at the beginning of
the card. Once the code is read from the card, the site searches the code file in the Site
Controller I memory or the LOOKUP file on a Site Controller II/III for a matching record
entry. If the entry exists, the data loaded for that code is used for the transaction. If the entry
does not exist, the card is denied. The site recognizes the card as a Code card when two start
sentinels are found at the beginning of the card.