Appendix

The following section includes supplementary information about IDmission IDentity APIs.

APPENDIX A - Submitting ID Images & Photos

BLOB fields can be of different types such as images or attachments. To handle them appropriately, you may submit different attributes to the server.

Example: ID Image Front (JSON)

<ID_Image__Front>
{
    "fieldId": "",
    "fileContent": "BASE_64_DATA_OF_IMAGE",
    "fileUploadType": "Y",
    "isImageControlData": "Y",
    "name": "#UniqueID#.jpeg",
    "type": "data:image/jpeg;base64",
    "uniqueId": #UniqueID#
}
</ID_Image__Front>

"fileContent": "BASE_64_DATA_OF_IMAGE": It contains Base_64 data of image.

APPENDIX C – Form Status and State Codes

The following table contains a list of values that will be returned in the tag ‘State’ in the response. This indicates the overall result of the ID Validation and/or any additional processing based on the Service ID. The table also includes a recommendation for action for the requesting application.

Note: If Manual Review is supported for your configuration, these initially would go into a result state with the word ‘Review…’ in front of the result. Once the form is actioned by the manual review team, it would be updated to reflect the states below. These Form Status and State Code values for Manual Review are in APPENDIX D.

Form State Returns and State Codes Table

State Code	Form Status	Description	Recommended Actions
00	Approved	All checks in our system have passed Data was extracted with the level of accuracy within our defined thresholds based on image quality.	No action required ID is approved
50	Barcode Unreadable	A barcode is expected to be present, but the barcode data is not detected by IDmission.	The application using this API should prompt the user to recapture the images where the barcode is present in better lighting without glare so the ID can be processed properly.
32	Biometric Match Fail	If the user’s biometric data (face, voice, and/or fingerprint) captured does not match the biometric data in the database from a previously enrolled user.	The application using this SDK/API should prompt the user to recapture their biometric information, ensuring that face, fingerprint, and voice can be captured with clarity and accuracy.
46	Customer Found	If the customer biometric data (face, voice, and/or fingerprint) has matched the biometric data in the database of a previous enrollment.	No action required Customer verification is approved.
44	Customer Not Found	If the customer biometric data (face, voice, and/or fingerprint) does not match the biometric data in the database from a previously enrolled user.	The application using this SDK/API should prompt the user to recapture their biometric information. The capture should be completed in a well-lit room with the customer biometric fully visible.
34	Customer Onboarded	All validation and security checks in our system have passed. The customer was successfully enrolled in the database.	No action required. Customer enrollment is approved.
37	Customer Onboarding Failed	The customer ID documents and/or biometric have failed one or more validation checks in our system. The customer was not enrolled into the database.	The application using this SDK/API should prompt the user to reattempt enrollment. When reattempting to enroll, the recapture should be completed in a well-lit room with the ID documents and biometric fully visible. The customer failed to enroll.
39	Customer Updated	If the capture of customer data has updated a previously enrolled customer record.	No action required Customer data is successfully updated.
135	DOB Match Failed	If the Date of Birth submitted in the request for the Customer or the Employee doesn’t meet the matching thresholds against the Date of Birth extracted from the ID Document.	The application using this API should prompt the user to provide a valid ID as this was deemed invalid.
35	Duplicate Customer	The biometric data provided by the customer for a new enrollment has matched to a previously enrolled user.	The application using the SDK should request the user to use the original unique customer identifier that was used during enrollment. If not, the application using the SDK should delete the previous record and prompt the user to reattempt enrollment.
36	Duplicate Employee	The biometric data provided by the employee for a new enrollment has matched to biometric data from a previous enrollment.	The application using the SDK should request the user to use the original unique employee identifier that was used during enrollment. If not, the application using the SDK should delete the previous record and prompt the user to reattempt enrollment.
47	Employee Found	If the customer biometric data (face, voice, and/or fingerprint) has matched the biometric data in the database of a previous enrollment.	No action required. Customer verification is approved
45	Employee Not Found	If the customer biometric data (face, voice, and/or fingerprint) does not match the biometric data in the database from a previously enrolled user.	The application using this SDK/API should prompt the user to recapture their biometric information. The capture should be completed in a well-lit room with the customer biometric fully visible.
33	Employee Onboarded	All validation and security checks in our system have passed. The employee was successfully enrolled in the database.	No action required. Employee enrollment is approved.
38	Employee Onboarding Failed	The employee ID documents and/or biometric data have failed one or more validation checks in our system. The employee was not enrolled into the database.	The application using this SDK/API should prompt the user to reattempt enrollment. When reattempting to enroll, the recapture should be completed in a well-lit room with the ID documents and biometric fully visible. The employee failed to enroll.
41	Employee Updated	If the capture of employee data has updated a previously enrolled customer record.	No action required Employee data is successfully updated.
40	Expired ID	The expiration date on the ID is equal to or less than the current date.	The application using this API should prompt the user to provide an ID with a valid expiration date.
137	Expiry Date Match Failed	If the Expiration Date submitted in the request for the Customer or the Employee doesn’t meet the matching thresholds against the Expiration Date extracted from the ID Document.	The application using this API should prompt the user to provide a valid ID as this was deemed invalid.
31	Face Not Detected	A face is not detected on an image. Typically, this occurs when the face is not present on the ID. In some cases, is due to poor image quality or image glare.	The application using this API should prompt the user to provide a clear image of an ID that includes a photo.
30	Facial Biometric Match Failed	If a customer photo is captured and does not biometrically match the photo in the ID document, the ability to review the images is in the back office.	The application using this API should prompt the user to capture a new selfie image.
10	ID Back Image not found	The back of an ID is expected to be present. The back image was not sent or A blank image was provided.	The application using this API should prompt the user to provide a clear image of the back of the ID.
52	ID Face Not Found	When conducting facial biometric verification, no face is found on submitted ID to match with selfie. Accordingly, facial biometric verification cannot be validated with the submitted ID	The application using this SDK/API should prompt the user to provide a clear ID with a clear face image to ensure that facial biometric verification can be completed.
60	ID Front and Back Mismatch	If the data extracted from the back of the ID image does not belong to the data presented on the front of the ID image.	The application using the API should prompt the user to provide new front and back images because inconsistences were found. Note: If this occurs more than once, the application could decide to push this to a manual review queue because it could be an issue with OCR extraction accuracy.
11	ID Front Image Not Found	The front of an ID is not uploaded, or a blank image was provided.	The application using this API should prompt the user to provide a clear image of the front of the ID.
61	ID Not Accepted	The uploaded ID contains an invalid configuration for the selected country.	The application using this API should prompt the user to provide an ID that is in the list of accepted ID Types. Note: The application should prompt the user to select an ID type from a dropdown list, which reduces the likeliness of this result.
62	ID Type Mismatch	If the ID Type submitted doesn’t match the ID Type extracted from the ID Image.	The application using this API should prompt the user to select the ID Type that matches the Type of ID that was uploaded/captured.
51	IDNumber Match Failed	The ID Number that was extracted by OCR from the ID does not match the ID Number that was extracted from the MRZ or Barcode, OR the ID Number submitted in the request does not match the ID Number that was extracted through OCR.	The application using this SDK/API should prompt the user to retry ID Validation.
63	Invalid ID Number	The ID Number on the ID does not match the pattern defined in the ID Template.	The application using this API should prompt the user to provide a valid ID.
12	Key Component Not Visible	If one of the key components on the ID such as the date of birth or expiration date is missing.	The application using this SDK should prompt the user that: The ID they have provided is not valid or the image provided may be blurred or unreadable in some portions or to recapture or capture an image of a different ID.
13	Low Resolution	The front or back image that is uploaded has been detected as low resolution or The ID image is not a color/grayscale image based on resolution thresholds defined by IDmission.	The application using this API should prompt the user to recapture the images in better lighting without glare so the ID can be processed properly.
48	Live Face Detected	If our system detects a live face from the selfie.	No action required. Live face detection was approved.
49	Live Face Not Detected	If our system does not detect a live face from the selfie image (e.g., if the selfie image is a photo of a photo, if the selfie image is a screen capture of a face, etc.)	The application using the SDK should prompt the user to retake the selfie ensuring that a live face is captured in good lighting.
64	MRZ and ID Data Mismatch	If the data extracted from the MRZ does not match the data extracted from the ID image itself.	The application using the API should prompt the user to provide new image(s) because inconsistences were found. Note: If this occurs more than once, the application could decide to push this to a manual review queue because it could be an issue with OCR extraction accuracy.
65	MRZ Invalid	The MRZ Validation flag (Machine Readable Zone) results in determining that the MRZ Data was not correct according to the standards.	The application using this API should prompt the user that the ID they have provided is not valid and to capture image of a different ID.
66	Name Match Failed	If the name submitted for the Customer or the Employee doesn’t meet the matching thresholds against the name extracted from the ID Document.	The application using this API should prompt the user to provide a valid ID as this was deemed invalid.
14	No Image Found	The ID front and back images are black or white and missing an ID Image.	The application using this API should prompt the user to recapture the images in better lighting without glare so the ID can be processed properly.
N/A	Pending Review	Initial state of the form. System checks are still pending.	No action required. Final results are sent via the POST API
53	Real ID Detected	If our system detects a real ID from the ID image.	No action required. Real ID Detection was approved.
54	Real ID Not Detected	If our system does not detect a real ID from the ID image (e.g., if the ID image is a photocopy, if the ID image is a screen capture of an ID, etc.)	The application using the SDK should prompt the user to retake the ID image ensuring that a real ID is captured in good lighting.
67	Sample ID	If an ID has been confirmed as a sample after manual review.	The application using this API should prompt the user that: The ID they have provided is not valid and to capture a different ID image.
68	Security Feature Invalid	One or more security features defined for the ID template are a mismatch with the provided image.	The application using this API should prompt the user to recapture the ID or a different one.
01	Submitted	If it is an asynchronous call via the API, the ID is awaiting process completion to be categorized into a form state.	No action required. OR If the call is asynchronous, the application using this SDK/API should get-process-data.
69	Suspected Sample	An ID has been detected as a sample (logic has been configured to recognize sample ID numbers, names, watermarks and other suspected sample data.)	The application using this API should prompt the user that the ID they have provided is not valid and to capture image of a different ID.
70	Suspected Tampering	Photo editing software (e.g. Microsoft Paint, Adobe Photoshop) was detected. Dates have been falsely created or modified in the ID document image.	The application using this API should prompt the user that the ID they have provided is not valid and to capture image of a different ID.
73	Suspicious ID	If an ID is found to be suspicious based on IDmission’s AI logic.	The application using this API should prompt the user that the ID they have provided is not valid and to capture an image of a different ID.
71	Tampered ID	An ID has been confirmed to be tampered with after manual review.	The application using this API should prompt the user that the ID they have provided is not valid and to capture image of a different ID.
15	Template Not Found	The correct template cannot be matched against those configured for the client. Note: The system will not find a template to associate with the image for correct data extraction and validation.	The application using the API should prompt the user to capture a different ID.
80	Third Party Verification Failed	If an ID has not been successfully verified by a third party.	The application using this SDK/API should prompt the user that the ID they have provided is not valid and to capture an image of a different ID. If the user thinks it is an error, they can retry.
72	Under the age of 18	The date of birth (extracted from the barcode / MRZ) calculates the individual as under the age of 18.	The date of birth indicates that the user is under the age of 18 Note: The API can determine if this was already indicated in the application. If it was not indicated, the API should prompt for correct ID.
118	Under the Age of 21	The date of birth (extracted from the barcode / MRZ) calculates the individual as under the age of 21.	The date of birth indicates that the user is under the age of 21. Note: The API can determine if this was already indicated in the application. If it was not indicated, the API should prompt for correct ID.
129	VideoID Audio Match Failed	The user’s Audio captured in the videoID does not match the Audio data in the database from a previously enrolled user.	The application using this SDK/API should prompt the user to recapture their VideoID and can be captured with clarity and accuracy.
131	ID and VideoID Not Matched	The user's captured ID does not match the ID in the VideoID	The application using this SDK/API should prompt the user to recapture their VideoID and can be captured with clarity and accuracy.
133	VideoID Face Match Failed	The user's captured Selfie does not match the Face in the VideoID	The application using this SDK/API should prompt the user to recapture their VideoID and can be captured with clarity and accuracy.

APPENDIX D – Manual Review Form Status and State Codes

If Manual Review is requested and the form moves into a ‘Review…’ formStatus, this is the list of values that the formStatus will show until manual review is completed. These are not the final form states, this is just a temporary formStatus that will be present until review is completed.

State Code	Form Status	Description	Recommended Actions
104	Review Barcode	If a barcode is expected to be present, and the barcode data is not detected by our system.	Manual review of the ID in the Back Office to verify the information on the front of the ID against what is shown on the back.
111	Review Duplicate Employee Found	If the submitted biometric data matches data already associated with an enrolled employee.	The submission will be manually reviewed in the back-office to determine if the matches found are true duplicates and will action the form accordingly.
134	Review DOB Match Failed	If the Date of Birth submitted in the request for the Customer or the Employee doesn’t meet the matching thresholds against the Date of Birth extracted from the ID Document.	Manual Review in the Back Office to compare the Date of Birth submitted in the request against the Date of Birth extracted from the ID.
95	Review Expired ID	If an ID has an expiration date that is expired as of today's date.	Manual review of the ID in the back-office to determine if the ID is truly expired or not.
136	Review Expiry Date Match Failed	If the Expiration Date submitted in the request for the Customer or the Employee doesn’t meet the matching thresholds against the Expiration Date extracted from the ID Document.	Manual Review in the Back Office to compare the Expiration Date submitted in the request against the Expiration Date extracted from the ID.
93	Review Face Not Detected	If a face is not detected on an image. The main reason for this is that the face was not present on the ID, however in some cases this could be due to poor image quality, or if there is a glare throughout the image.	Manual review of the ID in the Back Office to determine if a face is actually present on the ID.
102	Review Facial Biometric Match Not Verified	If a customer photo is captured and does not biometrically match the photo in the ID document, the ability to review the images is in the back office.	Manual review of the ID in the Back Office to determine if the Customer Photo is a match to the photo on the ID. If the person appears to be the same, it would be Approved, if not, it would be marked as ‘Facial Biometric Match Failed’.
90	Review Forced	This form state occurs when the Manual Review flag is set to F (Forced), which requires every form to be reviewed by the back-office team.	The ID will be manually reviewed in the back-office and decisioned into the appropriate form state.
94	Review ID Back Image not found	If the flags that determine a back image is not found are questionable, then the ability to review the ID back image is available in the back office.	Manual review of the ID back image in the Back Office to determine if its present and valid.
105	Review ID Front and Back Mismatch	If the back of an ID is expected to be present and if the data extracted from the front of the ID data does not match the data extracted from the barcode, then the ability to review the data is available in the Back Office.	Manual review of the ID in the Back Office because the data from the front does not match the data extracted from the barcode. The back office user will need to be able to see the ID Number field that was extracted from the front of the ID vs what was extracted from the barcode. They can manually compare this to the image to see if it's actually a mismatch or if it was an issue with OCR extraction.
103	Review ID Front Image Not Found	If the front of an ID is not uploaded or a blank image was provided.	Manual review of the ID front image in the Back Office to see if its present and valid.
108	Review ID Type Mismatch	If the ID Type submitted doesn’t match the ID Type extracted from the ID Image.	Manual Review of the ID in the Back Office to determine if the template match is correct based on the ID Type submitted.
126	Review IDNumber Match Failed	The ID Number that was extracted by OCR from the ID does not match the ID Number that was extracted from the MRZ or Barcode, OR the ID Number submitted in the request does not match the ID Number that was extracted through OCR.	Manual Review in the Back Office to compare the ID Number submitted in the request against the ID Number extracted from the ID.
63	Review Invalid ID Number	The ID Number on the ID does not match the pattern defined in the ID Template.	The ID will be manually reviewed in the back office to determine if the ID number matches the pattern defined in the ID template and was extracted incorrectly.
109	Review Key Component Not Visible	A key component that is expected on the ID is missing such as the Date of birth, expiration date, photo, etc.	Manual Review of the ID in the Back Office to determine if the components are present but just weren’t extracted.
116	Review Live Face Not Detected	If the live photo submitted fails the liveness checks based on IDmission's liveness detection logic.	Manual Review in the back-office. This occurs when an image fails the liveness check.
96	Review Low Resolution	If either the front or back image that is uploaded has been detected as low resolution or the ID image is not a color/gray scale image. This is based on resolution thresholds defined in our system.	Manual review of the ID in the Back Office to determine if the ID images have a clear enough resolution to be reviewed and validated.
106	Review MRZ and ID Data Mismatch	If the data extracted from the MRZ does not match the data extracted from the ID image itself.	Manual review of the ID in the Back office because the data from the front does not match the data extracted from the MRZ. The back-office user will need to be able to see the ID Number field that was extracted from the front of the ID vs what was extracted from the MRZ. They can manually compare this to the image to see if it's actually a mismatch or if it was an issue with OCR extraction.
91	Review MRZ Invalid	If the MRZ Validation flag (Machine Readable Zone) is questionable, and MRZ Data is expected to be present, then the ability to review the MRZ is available in the back office. An MRZ parsing tool is provided in the event the MRZ extracted might have a few characters transposed.	Manual Review of the ID in the Back Office. The MRZ String should be provided and an MRZ parsing tool should be present for the back-office user to utilize. In most cases, this is due to a glare on the MRZ so the data was extracted improperly. It can be manually fixed and tested to ensure the MRZ is truly valid.
107	Review Name Match Failed	If the name submitted for the Customer or the Employee doesn’t meet the matching thresholds against the name extracted from the ID Document.	Manual Review in the Back Office of the name submitted against the name extracted from the ID.
98	Review No Image Found	If the ID front and back images were not uploaded or a blank image was provided.	The ID front and back images will be manually reviewed in the back-office to see if they are present and valid.
97	Review Security Feature Invalid	If one or more security features defined for the ID template are detected as not matching with the image provided.	Manual Review in the Back Office. This occurs when the ID Template the image is matched against indicates the placement of the security feature is off or is not present.
112	Review Suspected Tampering	If photo editing software (e.g., Microsoft Paint, Adobe Photoshop) or other means of ID tampering were detected.	The ID will be manually reviewed in the back-office to investigate whether the ID has been tampered with.
113	Review Suspicious ID	If an ID is found to be suspicious based on IDmission’s AI logic.	Manual Review in the back-office. This occurs when an ID is found to be suspicious.
92	Review Template Not Found	If the image provided does not match any ID templates that are configured for a client, it can be reviewed by a back office team to determine if the image was just of poor quality and if it should be accepted OR if it should be rejected OR if the template needs to be setup and configured for that client.	Manual Review in the Back Office. This is generally due to poor image quality, so a manual check is required to see if it's truly a valid and accepted ID type for the region / customer.
101	Review Under the age of 18**	If the date of birth (extracted from the barcode/MRZ) calculates the individual as under the age of 18.	Manual review of the ID in the Back Office to determine if the date of birth extracted has resulted in a proper calculated age.
114	Review Verification Results	If the verification results through a third-party verification process are flagged to be reviewed. For example, the customer name matched against a watchlist.	The verification results will be manually reviewed in the back-office
117	Review Under the age of 21	If the date of birth (extracted from the barcode/MRZ) calculates the individual as under the age of 21.	Manual review of the ID in the Back Office to determine if the date of birth extracted has resulted in a proper calculated age.
128	Review VideoID Audio Match Failed	The user’s Audio captured in the videoID does not match the Audio data in the database from a previously enrolled user.	Manual review of the VideoID Audio in the Back Office to determine if the Customer Audio is a match to the VideoID Audio previously recorded. If the person appears to be the same, it would be Approved, if not, it would be marked as ‘VideoID Audio Match Failed'.
130	Review ID and VideoID Not Matched	The user's captured ID does not match the ID in the VideoID	Manual review of the VideoID ID in the Back Office to determine if the Customer ID is a match to the ID captured in the Video . If the person appears to be the same, it would be Approved, if not, it would be marked as ‘ID and VideoID Not Matched'.
132	Review VideoID Face Match Failed	The user's captured Selfie does not match the Face in the VideoID	Manual review of the Selfie and Face in the VideoID in the Back Office to determine if the Customer's Face is a match. If the person appears to be the same, it would be Approved, if not, it would be marked as ‘VideoID Face Match Failed’.

APPENDIX E – ID Types Codes

ID Type Code	ID Type Description
PP	PASSPORT
NID	NATIONAL_ID
RID	RESIDENCE_CARD
DL	DRIVERS_LICENSE
PID	PHOTO_ID
VID	VOTER_ID_CARD
TID	TAX_ID_CARD
WV	WORK_VISA_PERMIT
SV	STUDENT_VISA_PERMIT
GID	MILITARY_POLICE_GOVERNMENT_ID
BID	BOAT_SHIP_ID_CARD
OTH	OTHERS
GE	GLOBAL_ENTRY_CARD
PPC	PASSPORT CARD
NSP	NOT SPECIFIED
UNR	UNITED_NATION_REFUGEE_CARD
TD	TRAVEL_DOCUMENT
BC	BANK_CARD
PPA	PASSPORT_ADDRESS

APPENDIX F – ISO Country Codes

Country Code	Country Name
AFG	Afghanistan
ALA	Aland Islands
ALB	Albania
DZA	Algeria
ASM	American Samoa
AND	Andorra
AGO	Angola
AIA	Anguilla
ATA	Antarctica
ATG	Antigua and Barbuda
ARG	Argentina
ARM	Armenia
ABW	Aruba
AUS	Australia
AUT	Austria
AZE	Azerbaijan
BHS	Bahamas
BHR	Bahrain
BGD	Bangladesh
BRB	Barbados
BLR	Belarus
BEL	Belgium
BLZ	Belize
BEN	Benin
BMU	Bermuda
BTN	Bhutan
BOL	Bolivia
BES	Bonaire, Sint Eustatius and Saba
BIH	Bosnia and Herzegovina
BWA	Botswana
BVT	Bouvet Island
BRA	Brazil
IOT	British Indian Ocean Territory
BRN	Brunei Darussalam
BGR	Bulgaria
BFA	Burkina Faso
BDI	Burundi
KHM	Cambodia
CMR	Cameroon
CAN	Canada
CPV	Cape Verde
CYM	Cayman Islands
CAF	Central African Republic
TCD	Chad
CHL	Chile
CHN	China
CXR	Christmas Island
CCK	Cocos (Keeling) Islands
COL	Colombia
COM	Comoros
COG	Congo
COD	Congo, The Democratic Republic of
COK	Cook Islands
CRI	Costa Rica
CIV	Cote d'Ivoire
HRV	Croatia
CUB	Cuba
CUW	Curaçao
CYP	Cyprus
CZE	Czechia
DNK	Denmark
DJI	Djibouti
DMA	Dominica
DOM	Dominican Republic
ECU	Ecuador
EGY	Egypt
SLV	El Salvador
GNQ	Equatorial Guinea
ERI	Eritrea
EST	Estonia
ETH	Ethiopia
FLK	Falkland Islands (Malvinas)
FRO	Faroe Islands
FJI	Fiji
FIN	Finland
FRA	France
GUF	French Guiana
PYF	French Polynesia
ATF	French Southern Territories
GAB	Gabon
GMB	Gambia
GEO	Georgia
DEU	Germany
GHA	Ghana
GIB	Gibraltar
GRC	Greece
GRL	Greenland
GRD	Grenada
GLP	Guadeloupe
GUM	Guam
GTM	Guatemala
GGY	Guernsey
GIN	Guinea
GNB	Guinea-Bissau
GUY	Guyana
HTI	Haiti
HMD	Heard and Mc Donald Islands
VAT	Holy See (Vatican City State)
HND	Honduras
HKG	Hong Kong
HUN	Hungary
ISL	Iceland
IND	India
IDN	Indonesia
IRN	Iran, Islamic Republic of
IRQ	Iraq
IRL	Ireland
IMN	Isle of Man
ISR	Israel
ITA	Italy
JAM	Jamaica
JPN	Japan
JEY	Jersey
JOR	Jordan
KAZ	Kazakstan
KEN	Kenya
KIR	Kiribati
PRK	Korea, Democratic People's Republic of
KOR	Korea, Republic of
XKX	Kosovo (temporary code)
KWT	Kuwait
KGZ	Kyrgyzstan
LAO	Lao, People's Democratic Republic
LVA	Latvia
LBN	Lebanon
LSO	Lesotho
LBR	Liberia
LBY	Libyan Arab Jamahiriya
LIE	Liechtenstein
LTU	Lithuania
LUX	Luxembourg
MAC	Macao
MKD	Macedonia, The Former Yugoslav Republic Of
MDG	Madagascar
MWI	Malawi
MYS	Malaysia
MDV	Maldives
MLI	Mali
MLT	Malta
MHL	Marshall Islands
MTQ	Martinique
MRT	Mauritania
MUS	Mauritius
MYT	Mayotte
MEX	Mexico
FSM	Micronesia, Federated States of
MDA	Moldova, Republic of
MCO	Monaco
MNG	Mongolia
MNE	Montenegro
MSR	Montserrat
MAR	Morocco
MOZ	Mozambique
MMR	Myanmar
NAM	Namibia
NRU	Nauru
NPL	Nepal
NLD	Netherlands
NCL	New Caledonia
NZL	New Zealand
NIC	Nicaragua
NER	Niger
NGA	Nigeria
NIU	Niue
NFK	Norfolk Island
MNP	Northern Mariana Islands
NOR	Norway
OMN	Oman
PAK	Pakistan
PLW	Palau
PSE	Palestinian Territory, Occupied
PAN	Panama
PNG	Papua New Guinea
PRY	Paraguay
PER	Peru
PHL	Philippines
PCN	Pitcairn
POL	Poland
PRT	Portugal
PRI	Puerto Rico
QAT	Qatar
SRB	Republic of Serbia
REU	Reunion
ROU	Romania
RUS	Russia Federation
RWA	Rwanda
BLM	Saint Barthélemy
SHN	Saint Helena
KNA	Saint Kitts & Nevis
LCA	Saint Lucia
MAF	Saint Martin
SPM	Saint Pierre and Miquelon
VCT	Saint Vincent and the Grenadines
WSM	Samoa
SMR	San Marino
STP	Sao Tome and Principe
SAU	Saudi Arabia
SEN	Senegal
SYC	Seychelles
SLE	Sierra Leone
SGP	Singapore
SXM	Sint Maarten
SVK	Slovakia
SVN	Slovenia
SLB	Solomon Islands
SOM	Somalia
ZAF	South Africa
SGS	South Georgia & The South Sandwich Islands
SSD	South Sudan
ESP	Spain
LKA	Sri Lanka
SDN	Sudan
SUR	Suriname
SJM	Svalbard and Jan Mayen
SWZ	Swaziland
SWE	Sweden
CHE	Switzerland
SYR	Syrian Arab Republic
TWN	Taiwan, Province of China
TJK	Tajikistan
TZA	Tanzania, United Republic of
THA	Thailand
TLS	Timor-Leste
TGO	Togo
TKL	Tokelau
TON	Tonga
TTO	Trinidad and Tobago
TUN	Tunisia
TUR	Turkey
XTX	Turkish Rep N Cyprus (temporary code)
TKM	Turkmenistan
TCA	Turks and Caicos Islands
TUV	Tuvalu
UGA	Uganda
UKR	Ukraine
ARE	United Arab Emirates
GBR	United Kingdom
USA	United States
UMI	United States Minor Outlying Islands
URY	Uruguay
UZB	Uzbekistan
VUT	Vanuatu
VEN	Venezuela
VNM	Vietnam
VGB	Virgin Islands, British
VIR	Virgin Islands, U.S.
WLF	Wallis and Futuna
ESH	Western Sahara
YEM	Yemen
ZMB	Zambia
ZWE	Zimbabwe

APPENDIX G – ISO State Codes

State Code	Country Code	State Name
AL	USA	Alabama
AK	USA	Alaska
AZ	USA	Arizona
AR	USA	Arkansas
CA	USA	California
CO	USA	Colorado
CT	USA	Connecticut
DE	USA	Delaware
FL	USA	Florida
GA	USA	Georgia
HI	USA	Hawaii
ID	USA	Idaho
IL	USA	Illinois
IN	USA	Indiana
IA	USA	Iowa
KS	USA	Kansas
KY	USA	Kentucky
LA	USA	Louisiana
ME	USA	Maine
MD	USA	Maryland
MA	USA	Massachusetts
MI	USA	Michigan
MN	USA	Minnesota
MS	USA	Mississippi
MO	USA	Missouri
MT	USA	Montana
NE	USA	Nebraska
NV	USA	Nevada
NH	USA	New Hampshire
NJ	USA	New Jersey
NM	USA	New Mexico
NY	USA	New York
NC	USA	North Carolina
ND	USA	North Dakota
OH	USA	Ohio
OK	USA	Oklahoma
OR	USA	Oregon
PA	USA	Pennsylvania
RI	USA	Rhode Island
SC	USA	South Carolina
SD	USA	South Dakota
TN	USA	Tennessee
TX	USA	Texas
UT	USA	Utah
VT	USA	Vermont
VA	USA	Virginia
WA	USA	Washington
WV	USA	West Virginia
WI	USA	Wisconsin
WY	USA	Wyoming
ON	CAN	Ontario
QC	CAN	Quebec
NS	CAN	Nova Scotia
NB	CAN	New Brunswick
MB	CAN	Manitoba
BC	CAN	British Columbia
PE	CAN	Prince Edward Island
SK	CAN	Saskatchewan
AB	CAN	Alberta
NL	CAN	Newfoundland and Labrador
NSW	AUS	New South Wales
QLD	AUS	Queensland
SA	AUS	South Australia
TAS	AUS	Tasmania
VIC	AUS	Victoria
WA	AUS	Western Australia