The length of Field 22 usually 3-digits (or 4-digits in case it is BCD packed into two Bytes) in protocols based on ISO 8583:1987 or 12-digits in case protocols based on ISO 8583:1993 version. Customized protocols could use different sub-fields content and values meaning behind.
While you use short values in the requested question, I guess, your Field 22 based on ISO 8583:1987 version and you lost the leading and/or ending zero. So, your sample values becomes 3 digits length - 052
, 800
, 022
, and 090
or 900
.
Usually the 3-digits Field 22 splited into two sub-fields:
- Position 1 and 2 - Personal Account Number (PAN) Entry (or capability);
- Position 3 - Personal Identification Number (PIN) Entry (or capability);
Here are the possible interpretations:
02
- PAN auto-entry via magnetic stripe, track data is not required, 2
- no PIN.
05
- PAN auto-entry via chip, 2
- no PIN.
09
- E-Commerce, 0
- unknown PIN capability.
80
- Fallback to magnetic stripe, 0
- unknown PIN capability.
90
- PAN auto-entry via magnetic stripe, track data should be transmitted within the authorization request, 0
- unknown PIN capability.
etc.
90
used in case track data present in the ISO 8583 request message, 02
- if, for same reason, acquirer or terminal device not qualified to transfer track data in the request messages.
Depending of protocol requirements could be exceptions with Field 22 values. It is usually checked during the terminal device and communication interface certifications.
02
and90
? – Beveridge