EMV L2 (8) — Processing Restrictions

The purpose of Processing Restrictions is to determine the degree of compatibility between the application in the terminal and the application in the ICC, and to perform any necessary adjustments, including the possibility of rejecting the transaction. The results are recorded in the TVR (Terminal Verification Results).

The terminal should always perform the Processing Restrictions function, which can be executed at any stage after Read Application Data and before the Terminal Action Analysis.

Processing Restrictions consist of three parts:

1. Application Version Number Checking
2. Application Usage Control Checking (AUC)
3. Application Effective/Expiration Dates Checking

Application Version Number Checking

If both the Terminal Application Version Number (Tag 9F09) and the ICC Application Version Number (Tag 9F08) are present, and the two versions are different, the bit “ICC and terminal have different application versions” in the TVR must be set.

If only one of the Terminal Application Version Number (Tag 9F09) or ICC Application Version Number (Tag 9F08) is present, or if both are absent, the two versions are considered compatible, and no comparison or further action is required.

Application Usage Control Checking

The Application Usage Control indicates restrictions limiting the application geographically or to certain types of transactions. If this data object is present, the terminal shall make the following checks:

• If the transaction is being conducted at an ATM, the ‘Valid at ATMs’ bit must be on in Application Usage Control.
• If the transaction is not being conducted at an ATM, the ‘Valid at terminals other than ATMs’ bit must be on in Application Usage Control.
• If the Application Usage Control and Issuer Country Code are both present in the ICC, the terminal shall make the checks described in Table 32.

If any of the above tests fail, the terminal shall set the ‘Requested service not allowed for card product’ bit in the TVR to 1.

Application Effective/Expiration Dates Checking

• Application Effective Date, Tag9F25 Card data, n6, 3bytes
• Application Expiration Date, Tag9F24 Card data, n6, 3bytes；

If the Application Effective Date is present in the ICC, the terminal shall check that the current date is greater than or equal to the Application Effective Date.

If it is not, the terminal shall set the ‘Application not yet effective’ bit in the TVR to 1.

The terminal shall check that the current date is less than or equal to the Application Expiration Date.

If it is not, the terminal shall set the ‘Expired application’ bit in the TVR to 1.