Driver's License and ID Check-In Compatibility

The LobbyCentral iPad app has been discontinued and cannot be downloaded from iTunes.

Native kiosk mode supports customer check-in with a driver's license that complies with the AAMVA driver's license standard.

Note: The AAMVA standard is not a requirement for states to follow. Therefore, your state's driver's license may not be compatible with driver's license check-in.

Driver's License Compatibility

While many states are moving toward the standard, many are still using a proprietary based encoding on either the magnetic strip, or the 2D barcode located on the back of the license.   

States that have moved to the new standard are only doing so on a go-forward basis and not reissuing current licenses. Thus, customers prior to the standard adoption date will be on the older format and will not be compatible with LobbyCentral.

In addition, many states are only applying the AAMVA standard to the 2D barcode and not the magnetic strip, as most states are removing this from future licenses that are issued.

Determining 2D Barcode Compliance

To determine if your state's 2D barcode follows the AAMVA standard, you may contact the state's office in charge of Motor Vehicle registrations. Generally this is the Secretary of State's office. Your local BMV/DMV may have this information as well.

If the state is not using the AAMVA standard, you cannot use the Driver's License check-in feature.

Magnetic Card Strip Compliance

Many states have utilized a proprietary data format for the magnetic strip. Your state's license may not be compatible with LobbyCentral. In this case, you can use the 2D barcode if the format follows AAMVA.  See  Determining 2D Barcode Compliance, above.

If you have a magnetic card reader, you can check the format of the data:   

  1. Using the magnetic card reader that is connected to a computer, open a text editing program such as Notepad.
  2. Ensure the cursor is located inside the editor.
  3. Swipe your license and observe the data that is captured.
  4. Compare the data to the Magnetic Format chart below.

If the format of the magnetic strip does not comply with the format shown, you cannot use the Driver's License check-in feature.

If you are designing a proprietary based ID card using the AAMVA format, you may use the Driver's License check-in feature.

Magnetic Strip AAMVA Three-Track Format

Only fields shown in BOLD are used by LobbyCentral. All other fields are ignored.

Track 1
Field Letter
Element/Definition
Position
Size
A Start Sentinel
This Character must be used at the beginning of the track.
0 1
B State of Province (addressee)
(Mailing or Residential code) this field will use the ANSI D-20 standard

1 2
C City
This field should be truncated with a field separator ^ if less than 13 characters long. If a field separator is used, the "NAME" field follows immediately.
EXAMPLE: Bear^

3 13
D Name
This field should be truncated with a field separator ^ if less than 35 characters long. If a field separator is used. The "ADDRESS" field follows immediately. The $ symbol is to be used as a delimiter between names.
EXAMPLE: Roe$Chery1$A^
EXAMPLE using "City and Name"
Bear^Roe$Chery1$A^
at this point a total of 19 bytes have been used, allowing the remainder to be used for the address.

16 35
E Address
This field has a minimum length of 29 which can be exceeded when utilizing the space from either the city and/or name field. The $ symbol can be used a as delimiter of multiple address lines.
EXAMPLE: Using the City, Address
Combination: Bear^Roe$Chery1$A^123 Something St^

51 29
F End Sentinel
This character must be the next to the last character of the track.
80 1
G LRC
This character must be used at the end of the track.
81 1
Track 2
Field Letter Element/Definition Position Size
A Start Sentinel
This character must be used at the beginning of the track.
0 1
B ANSI User Code
This field is assigned by ANSI for the utilization of Track2
1 1
C ANSI User ID
This field is the assigned identification number from ISO (International Standards Organization).
2 5
D Jurisdiction ID/DL Number
This field is used to represent the ID/DL number assigned by each jurisdiction. If less than 13 bytes are used the field is truncated by a field separator character. If 13 bytes are used the field separator character MUST appear in the 14th position. Overflow can be accommodated in field letter g.

7 14
E Expiration Date
This field will be represented in the following format YYMM.
21 4
F Birthdate
This field will be represented in the ANSI D-20 Standard YYYYMMDD

25 8
G Remainder of Jurisdictional ID/DL
This field is used to handle the overflow from the jurisdiction ID/DL field.
33 5
H End Sentinel
This character must be the next to the last character of the track.
38 1
I LRC
This character must be used at the end of the track.
39 1
Track 3
Field Letter Element/Definition Position Size
A Start Sentinel
This character must be used at the beginning of the track.
0 1
B Template Version#
1 byte table, value 01-63, this field will be used to store the magnetic strip version being used. It will be necessary to register the use with AAMVA.
1 1
C Security Version #.
1 byte table, value 01-63, this field will be used to store the magnetic strip security version used. 00 represents security is not used.
2 1
D Postal Code
This field will be used to store an 11 position Zip Code or the Canadian postal code. 11 Alphanumeric digits will soon be required to meet postal standards. Left justified with spaces filled. Use no hyphens.

3 11
E Class
This field will be alphanumeric and will represent the type of license. Use ANSI D-20 codes as modified for CDLIS.
14 2
F Restrictions
This field will be alphanumeric and will use the ANSI D-20 standard.
16 10
G Endorsements
This field will be alphanumeric and will use the ANSI D-20 standard.
26 4
H Sex
Represent as alphanumeric
30 1
I Height
Represent as numeric. See ANSI D-20
31 3
J Weight
Represent as numeric. See ANSI D-20
34 3
K Hair Color
Represent as alphanumeric. See ANSI D-20
37 3
L Eye Color
Represent as alphanumeric. See ANSI D-20
40 3
M This field can be utilized by each jurisdiction as needed, but if used it will be necessary to register the use with AAMVA 43 10
N Reserved Space
This field can be utilized by each jurisdiction as needed, but if used it will be necessary to register the use with AAMVA
53 16
O Error Correction
This field can be utilized by each jurisdiction, but is not a mandatory field.
69 6
P Security
This field is for the use of each jurisdiction.
75 5
Q End Sentinel
This character must be the next to the last character for the track.
80 1
R LRC
This character must be used at the end of the track.
81 1
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us