RC Card File Structure

Version 2.0
The RC application data will reside in EFs under the RC-DF, which is created under
the MF. The RC-DF will contain the following EFs under it.

• Key file File Id = AE02

• SE file File Id = AE0C
• Registration Details File File Id = AE03
• Personal Details File File Id = AE04
• Vehicle Details File File Id = AE05
• Endorsement File File Id = AE06
• Axle Details File File Id = AE07
• Vehicle Permit Details File File Id = AE08
• Retro Fitting Details File File Id = AE09
• Additional Information File File Id = AE0A
• Details of alternative or additional
Semi-Trailer(s) registered with an
Articulated vehicle File Id = AE0B
• Hypothecation details File Id = AE0D
• Signature details File id = AE0E

The sections below describe the FCP and the contents of each of these files.

Directory RC-DF
The directory RC-DF will have the following FCP.

TAG LENGTH VALUE REMARKS

82 01 38 FDB ONLY
83 02 AE00 File Identifier
84 10 RC DF Name
8A 01 01 or 05 LCSI. When file is created first, it will be
in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 08 7F Security Attributes. AM Byte: 7F
FF Delete File (Self): Never
FF Terminate DF: Never
21 Activate File: (SE#1)
21 Deactivate File: (SE#1)
21 Create File DF: (SE#1)
21 Create File EF: (SE#1)
FF Delete File (Child): Never
AB 0D 86 04 22 F4 Security Attributes (expanded format)
22 F2 Command MSE Erase is: Never allowed
97 00 Command MSE Store is: Never allowed
8401DA Command PUTDATA never allowed.
9700
8D 02 AE0C File id of the SE file

Data objects:-

Field Tag Length Value

Version 02C0 3 2.0
Registration no 02C1 20 DL1ABC1234
Horse Vehicle Registration 02C2 100 {“HV1”:”NA”}
Mark, if applicable
Date of Card Activation 02C3 4(BCD) DDMMYYYY
(KMS Date)

Key File EF2

The key file will have the following FCP.

TAG LENGTH VALUE REMARKS

82 05 0C FDB (Linear variable record internal EF)
01 DCB (Write once, 1 byte Data unit)
00 15 MRL (21 bytes)
04 No. of records (4 keys)

83 02 AE02 File Identifier

88 01 10 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state
(creation). Later it will be turned into 05
(activated
state)
8C 06 6B Security Attributes. AM Byte: 6B
FF Delete self: Never
21 Terminate EF: (SE#1)
21 Deactivate EF: (SE#1)
FF Update record: Never
FF Read record: Never
SE File
The SE file will have the following FCP.
TAG LENGTH VALUE REMARKS
82 05 0C FDB (Linear variable record internal EF)
01 DCB (Write once, 1 byte Data unit)
00 0E MRL (14 bytes)
04 No. of records (04 SE Records)

83 02 AE0C File Identifier

88 01 60 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 06 6B Security Attributes. AM Byte: 6B
FF Delete self: Never
21 Terminate EF: (SE#1)
21 Deactivate EF: (SE#1)
FF Update record: Never
FF Read record: Never

Registration Details file

The FCP of the Registration Details file will be as follows.

TAG LENGTH VALUE REMARKS

80 02 07D0 File size (2000 bytes, with enough growth
space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE03 File Identifier
88 01 18 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
FF Update Binary: (NEVER)
Field Type Tag (Key) Sample (Key / Value Pair in
(Updatab JSON format)
le / Non- Note: (First two bytes will be actual
Updatabl byte length of data written)
e)
Registration Date (in dd- Non- RD1 {"RD":{“RD1”:21-Aug-2019,
Mon-yyyy format) updatable ”RD2”:21-Aug-2019, “RD3”:“N”,
Purchase Date (in dd- Non- RD2 “RD4”:20-Aug-2034,
Mon-yyyy format) updatable ”RD5”:”XYZ ABC Dealer”,
Registration Type (N, A, Non- RD3 “RD6”:”RTOAUTH ABC XYZ”}}
O, D) updatable
Registration Validity (in Non- RD4
dd-Mon-yyyy format) updatable
(To be stored ”As per
Fitness” for Transport /
Commercial vehicle)
Dealer Name Non- RD5
updatable
Registering Authority Non- RD6
Name updatable

Personal Details file

The FCP of the Personal Details file will be as follows.
TAG LENGTH VALUE REMARKS
80 02 09C4 File size (2500 bytes, with enough growth
space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE04 File Identifier
88 01 20 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
FF Update Binary: (NEVER)

Field Type Tag (Key) Sample (Key / Value Pair in

(Updatable / JSON format)
Non- Note: (First two bytes will be actual byte
Updatable) length of data written)
Owner Name Non-updatable OD1 {"OD":{“OD1”:”SHRI SURESH
Son/Wife /Daughter Non-updatable OD2 SHARMA”, “OD2”:”SHRI RAMESH
of (if Individual) SHARMA”, “OD3”:”[Link].1, LODHI
Owner Current Non-updatable OD3 ROAD, DELHI-110003”,
Address ”OD4”:”[Link].1, LODHI ROAD,
Owner Permanent Non-updatable OD4 DELHI-110003”, “OD5”:1,
Address “OD6”:”INDIVIDUAL”}}
Owner Serial No. Non-updatable OD5
Ownership Type Non-updatable OD6

Vehicle Details file

The FCP of the Vehicle Details File will be as follows.
TAG LENGTH VALUE REMARKS
80 02 0FA0 File size (4000 bytes, with enough growth
space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE05 File Identifier
88 01 28 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated
state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
FF Update Binary: (NEVER)

Field Type Tag Sample (Key /

(Updatable / (Key) Value Pair in JSON
Non-Updatable) format)
Note: (First two bytes
will be actual byte length
of data written)
Vehicle Class Non-updatable VD1 {"VD":{“VD1”:”MOT
Maker/Manufacturer Non-updatable VD2 OR CAR”,
Model Non-updatable VD3 “VD2”:”MARUTI
No. of Cylinder Non-updatable VD4 SUZUKI”,
Horse Power (format 99999.99) Non-updatable VD5 “VD3”:”BALENO”,
Seating Capacity Non-updatable VD6 “VD4”:4, “VD5”:5.5,
Standing Capacity Non-updatable VD7 “VD6”:5, “VD7”:0,
Sleeper Capacity Non-updatable VD8 “VD8”:0,
Unladen Weight (kg) Non-updatable VD9 “VD9”:1000,
Laden Weight (kg) Non-updatable VD10 “VD10”:1200,
Gross Combination Weight, if Non-updatable VD11 “VD11”:0, “VD12”:
applicable (kg) 1234, “VD13”:
Wheelbase (mm) Non-updatable VD12 1400, “VD14”:0.00,
Cubic Capacity (format 99999.99) Non-updatable VD13 “VD15”:”PETROL”,
Floor Area (sq m) (format 999.999) Non-updatable VD14 “VD16”:”ABCD1234”
Fuel Non-updatable VD15 ,
“VD17”:”1234ABCD”
Chassis No Non-updatable VD16
Engine No Non-updatable VD17 ,
Body Type Non-updatable VD18 “VD18”:”HATCHBA
Colour Non-updatable VD19 CK”,
Manufacturing Month (mm) Non-updatable VD20 “VD19”:”BLUE”,
Manufacturing Year (yyyy) Non-updatable VD21 “VD20”: 8, “VD21”:
Sale Amount Non-updatable VD22 2019,
Emission Norms Non-updatable VD23 “VD22”:1000000,
Height (mm) Non-updatable VD24 “VD23”:”BS-4”,
Length (mm) Non-updatable VD25 “VD24”: 1500,
Width (mm) Non-updatable VD26 “VD25”: 3500,
AC Fitted (Y/N) Non-updatable VD27 “VD26”:1600,
Video Fitted (Y/N) Non-updatable VD28 “VD27”:”Y”,
Audio Fitted (Y/N) Non-updatable VD29 “VD28”:”N”,
“VD29”:”Y”}}

Endorsement file
The FCP of the endorsement file will be as follows.

TAG LENGTH VALUE REMARKS

80 02 4E20 File size (20000 bytes, with enough growth space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE06 File Identifier
8A 01 01 or 05 LCSI. When file is created first, it will be in 01
state (creation). Later it will be turned into 05
(activated
state)
88 01 30 SFI – coded in 5 MSBs
8C 05 6A Security Attributes (compact form):
FF Delete File: Never
21 Terminate File: (SE#1)
21 Deactivate File: (SE#1)
22 Update binary: (SE#2)

Field Type Tag (Key) Sample (Key / Value Pair in JSON

(Updatable / format)
Non-Updatable) Note: (First two bytes will be actual byte
length of data written)
Challan No. Updatable D1 {“CD1”:{“D1”:123, “D2”:”D”, “D3”:5,
Accused category Updatable D2 “D4”:”SHRI SURESH SHARMA”,
(D – Driver, “D5”:”GURGAON”, “D6”:”21-Aug-
C – Conductor, 2019 21:29”, “D7”:”SHRI NARESH
O – Owner) SHARMA”, “D8”: 500, “D9”:12345},
Section (s) (code Updatable D3 “CD2”:{“D1”:123, “D2”:”D”, “D3”:5,
only with delimiter “,”, “D4”:”SHRI SURESH SHARMA”,
if more than 1) “D5”:”GURGAON”, “D6”:”21-Aug-
Challaning Officer Updatable D4 2019 22:58”, “D7”:”SHRI NARESH
Name SHARMA”, “D8”: 500, “D9”:12345}}
Location Updatable D5
Challan Date & Time Updatable D6
in dd-Mon-yyyy
hh24:mm format
Disposing Officer Updatable D7
Name
Penalty Updatable D8
Receipt No. Updatable D9

Axle Details file

The FCP of the Axle Details File will be as follows.

TAG LENGTH VALUE REMARKS
80 02 07D0 File size (2000 bytes, with enough growth
space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE07 File Identifier
88 01 38 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
FF Update Binary: (NEVER)

Field Type Tag Sample (Key / Value Pair in

(Updatable / (Key) JSON format)
Non- Note: (First two bytes will be actual
Updatable) byte length of data written)
Number of Axle Non-updatable AD1 {"AD":{“AD1”:2, “AD2”:2,
Number of Tyre – Front Axle Non-updatable AD2 “AD3”:”185/65 R15 1 PLY”,
Front Axle (Description and Non-updatable AD3 “AD4”: 100, “AD5”:2,
Size of Tyre) “AD6”:”17*17, 1 PLY”, “AD7”:100,
Front Axle Weight (kg) Non-updatable AD4 “AD8”:0, “AD9”:”NA”, “AD10”: 0,
Number of Tyre – Rear Axle Non-updatable AD5 “AD11”:0, “AD12”:”NA”, “AD13”:0,
Rear Axle (Description and Non-updatable AD6 “AD14”:123, “AD15”:123}}
Size of Tyre)
Rear Axle Weight (kg) Non-updatable AD7
Number of Tyre – Tandem Non-updatable AD8
Axle
Tandem Axle (Description and Non-updatable AD9
Size of Tyre)
Tandem Axle Weight (kg) Non-updatable AD10
Number of Tyre – Other Axle Non-updatable AD11
Other Axle (Description and Non-updatable AD12
Size of Tyre)
Other Axle Weight (kg) Non-updatable AD13
Overhang (mm) Non-updatable AD14
Rearhang (mm) Non-updatable AD15

Vehicle Permit file

The FCP of the Vehicle Permit File will be as follows.

TAG LENGTH VALUE REMARKS
80 02 2710 File size (10000 bytes, with enough
growth space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE08 File Identifier
88 01 40 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
24 Update Binary: (SE#4)

Field Type Tag Sample (Key / Value Pair in

(Updatable / (Key) JSON format)
Non- Note: (First two bytes will be actual byte
Updatable) length of data written)
Permit Number Updatable P1 {"PD":{“PD1”:{“P1”:1234567, “P2”:
Permit Type (Description) Updatable P2 “NATIONAL PERMIT”,
Permit IA Name Updatable P3 “P3”:”TRANSPORT ABCD”,
Validity From (in ddmmyyyy Updatable P4 “P4”:22082019, “P5”:21082020,
format) “P6”:19082019, “P7”:”STATE”,
Validity Upto (in ddmmyyyy Updatable P5 “P8”:”GURGAON”,
format) “P9”:”MUMBAI”, “P10”:2,
Replacement Date (in Updatable P6 “P11”:1500, “P12”:1}},
ddmmyyyy format) {“PD2”:{“P1”:1234567, “P2”:
Area (e.g. Local, Distt, Region, Updatable P7 “SPECIAL PERMIT”,
State etc.) “P3”:”TRANSPORT ABCD”,
Route From Updatable P8 “P4”:22082019, “P5”:21082020,
Route Upto Updatable P9 “P6”:19082019, “P7”:”STATE”,
Stages Updatable P10 “P8”:”GURGAON”,
Route Length (km) Updatable P11 “P9”:”MUMBAI”, “P10”:2,
Number of Trips per day Updatable P12 “P11”:1500, “P12”:1}}}
Retro Fitting Details file
The FCP of the File will be as follows.
TAG LENGTH VALUE REMARKS
80 02 07D0 File size (2000 bytes, with enough growth
space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE09 File Identifier
88 01 48 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
21 Update Binary: (SE#1)

Field Type Tag (Key) Sample (Key / Value Pair

(Updatable in JSON format)
/ Note: (First two bytes will be
Non- actual byte length of data
Updatable) written)
Kit Manufacturer Updatable RF1 {"RF":{“RF1”:”ABCDWXYZ”,
Kit Type Updatable RF2 “RF2”:”CNG”, “RF3”:”AAA
Kit Workshop Updatable RF3 XXX”, “RF4”:98765,
Kit Serial Number Updatable RF4 “RF5”:”ONCE PER YEAR
Kit PUCC Norms Updatable RF5 FOR BS-4”,
Workshop License No Updatable RF6 “RF6”:HR34567,
Fitment Date (in Updatable RF7 “RF7”:21082019,
ddmmyyyy format) “RF8”:21082019,
Hydro Test Date (in Updatable RF8 “RF9”:4567321}}
ddmmyyyy format)
Cylinder Serial Number Updatable RF9

Additional Information:-

The FCP of the File will be as follows.

TAG LENGTH VALUE REMARKS
80 02 00C8 File size (200 bytes, with enough growth
space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE0A File Identifier
88 01 50 Short EF id
8A 01 01 or 05 LCSI. When file is created first, it will be
in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
FF Update Binary: (Never)

Field Type Tag Sample (Key / Value Pair

(Updatable / (Key) in JSON format)
Non-Updatable) Note: (First two bytes will be
actual byte length of data
written)
Number of Non-updatable AT1 {"TD":{“AT1”:0,”AT2”:”NA”}}
attached Semi-
Trailers
Attached Non-updatable AT2
Trailer(s)
Registration Mark

Details of alternative or additional Semi-Trailer(s) registered with an articulated

vehicle:-

The FCP of the alternative or additional Semi-Trailer(s) will be as follows.

TAG LENGTH VALUE REMARKS
80 02 09C4 File size (2500 bytes, with enough growth
space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE0B File Identifier
88 01 58 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
FF Update Binary: (Never)
Field Type Tag Sample (Key / Value Pair in
(Updatable / (Key) JSON format)
Non- Note: (First two bytes will be actual
Updatable) byte length of data written)
Body Type Non- T1 {"ST":{“ST1”:{“T1”:”NA”,“T2”:123,
updatable “T3”:456, “T4”:”NA”, “T5”:”NA”,
Unladen Weight (kg) Non- T2 “T6”:1234, “T7”:”NA”, “T8”:1234,
updatable “T9”:”NA”, “T10”:1234,
Laden Weight (kg) Non- T3 “T11”:”NA”, “T12”:1234}, “ST2”:{
updatable “T1”:”NA”,“T2”:123, “T3”:456,
Chassis No Non- T4 “T4”:”NA”, “T5”:”NA”, “T6”:1234,
updatable “T7”:”NA”, “T8”:1234, “T9”:”NA”,
Front Axle (Number, Non- T5 “T10”:1234, “T11”:”NA”,
Description and Size of Tyre) updatable “T12”:1234}}}
Front Axle Weight (kg) Non- T6
updatable
Rear Axle (Number, Non- T7
Description and Size of Tyre) updatable
Rear Axle Weight (kg) Non- T8
updatable
Tandem Axle (Number, Non- T9
Description and Size of Tyre) updatable
Tandem Axle Weight (kg) Non- T10
updatable
Other Axle (Number, Non- T11
Description and Size of Tyre) updatable
Other Axle Weight (kg) Non- T12
updatable

Hypothecation Details
The FCP of the Vehicle Details File will be as follows.
TAG LENGTH VALUE REMARKS
80 02 03E8 File size (1000 bytes, with enough growth
space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE0D File Identifier
88 01 68 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
FF Update Binary: (Never)
Field Type Tag (Key) Sample (Key / Value Pair in
(Updatable / JSON format)
Non-Updatable) Note: (First two bytes will be actual
byte length of data written)
Name of Financier Non-updatable H1 {"HD":{“HD1”:{“H1”:”STATE
BANK OF INDIA”},
“HD2”:{“H1”:”NA”}}}

Signature Details
The FCP of the Vehicle Details File will be as follows.
TAG LENGTH VALUE REMARKS
80 02 3000 File size (12288 bytes, with enough
growth space)
82 02 01 FDB (Transparent working EF)
01 DCB Write Once, One byte data unit
83 02 AE0E File Identifier
88 01 70 Short EF id

8A 01 01 or 05 LCSI. When file is created first, it will be

in 01 state (creation). Later it will be
turned into 05 (activated state)
8C 05 6A Security Attributes. AM Byte: 6A
FF Delete File (Self): Never
21 Terminate EF: (SE#1)
21 Deactivate File: (SE#1)
21 Update Binary: (SE#1)

Total Size of card: - 64 KB.

Data size: - 58628 bytes.

FCP size: - 425 bytes.

Total size used: - 59053 bytes

(With enough growth space)