The Processing Restrictions function is performed by the terminal using data elements from the terminal and the card. It includes checks on application versions, effective and expiration dates, and conditions at the point of transaction.
Processing Restrictions shall be performed as specified in EMV Book 3, section 10.4, and EMV Book 4, section 6.3.3 and Annex A.
This chapter includes the following sections:
7.1 Card Data 7.2 Terminal Data 7.3 Processing
7.4 Prior Related Processing
7.5 Subsequent Related Processing
7 Processing Restrictions Visa Integrated Circuit Card Specification (VIS)
7.1 Card Data Version 1.5
7.1 Card Data
The card data elements used in Processing Restrictions are listed and described in Table 7-1. For a detailed description of these data elements and their usage, see Appendix A, VIS Data Element Tables.
Table 7-1: Processing Restrictions—Card Data
Data Element Description
Application Effective Date, '5F25'
The Application Effective Date is the date when the application becomes activated for use.
Application Expiration Date, '5F24'
The Application Expiration Date is the date after which the application is no longer available for use.
Application Version Number, '9F08'
This data element indicates the version of the application on the card. It is used in Application Version Number checking by the terminal. Cards complying with this specification should use 150.
Application Usage Control (AUC), '9F07'
The AUC is an optional data element. This data element indicates any restrictions set forth by the issuer on the geographic usage and services permitted for the card application. It is used in Application Usage Control checking by the terminal.
Issuer Country Code, '5F28' This Issuer Country Code is the EMV-defined data element indicating the country of the card issuance. It is used in Application Usage Control checking by the terminal.
Visa Integrated Circuit Card Specification (VIS) 7 Processing Restrictions
Version 1.5 7.2 Terminal Data
7.2 Terminal Data
The terminal data elements used in Processing Restrictions are listed and described in Table 7-2. For a detailed description of these data elements and their usage, see Appendix A, VIS Data Element Tables.
7.3 Processing
The card performs no processing during the Processing Restrictions function.
The following sections describe how the terminal uses data from the card during Processing Restrictions.
7.3.1 Application Version Number
The terminal compares the Application Version Number from the card to the Application Version Number in the terminal to see whether they are the same. If the Application Version Numbers are not the same, then the terminal sets the ‘ICC and terminal have different application versions’ bit of the TVR to 1b.
Table 7-2: Processing Restrictions—Terminal Data
Data Element Description
Application Version Number, '9F09'
This data element indicates the version of the application in the terminal.
Transaction Type, '9C' This data element indicates the type of financial transaction. (It is
represented by the first two digits of ISO 8583-1987, Processing Code.) It is used in Application Usage Control checking by the terminal.
Terminal Country Code, '9F1A' This data element indicates the country where the terminal is located. It is used in Application Usage Control checking by the terminal.
Transaction Date, '9A' This is the local date (in the terminal) when the transaction is taking place. It is used by the terminal in effective and expiration date checking.
7 Processing Restrictions Visa Integrated Circuit Card Specification (VIS)
7.3 Processing Version 1.5
7.3.2 Application Usage Control
During Application Usage Control, the terminal checks various conditions at the point of transaction to determine whether processing should continue. If the Application Usage Control (AUC) and the Issuer Country Code were received from the card during Read Application Data, then the terminal checks the following application restrictions:
1. Domestic and International Checking Domestic
The terminal compares the Issuer Country Code to the Terminal Country Code. If they are equal, then the transaction is considered domestic for AUC processing. If the transaction is domestic, then, in the AUC from the card, the domestic indicator corresponding to Transaction Type must be 1b to indicate that the requested service is allowed.
For example, if the transaction is a cash transaction, then the ‘Valid for domestic cash transactions’ bit of the AUC must be 1b for the transaction to continue.
International
If the country codes are not equal, then the transaction is considered international for AUC processing. If the transaction is international, then, in the AUC from the card, the international indicator corresponding to Transaction Type must be 1b to indicate that the requested service is allowed.
For example, if the transaction is a cash transaction, then the ‘Valid for international cash transactions’ bit of the AUC must be 1b for the transaction to continue.
2. ATM Checking
If the card acceptance device is an ATM, then the ‘Valid at ATMs’ bit of the AUC must be 1b. If the card acceptance device is not an ATM, then the ‘Valid at terminals other than ATMs’ bit of the AUC must be 1b.
If any of the above checks performed by the terminal fail, then the terminal sets the
‘Requested service not allowed for card product’ bit of the TVR to 1b.
Visa Integrated Circuit Card Specification (VIS) 7 Processing Restrictions
Version 1.5 7.3 Processing
The manner in which the AUC from the card is used in this processing is illustrated in Table 7-3. If the indicated bit has a value of 1b, then that usage or capability is supported.
Note: An EMV terminal does not differentiate between goods and services (see EMV Application Note No. 27). In Application Usage Control, the value of ‘Valid for domestic goods’ must be the same as the value of ‘Valid for domestic services’, and the value of ‘Valid for international goods’ must be the same as the value of
‘Valid for international services’.
7.3.3 Application Effective Date
The terminal performs Application Effective Date checking when the card application data includes the Application Effective Date. It ensures that the application is active by
validating that the Application Effective Date from the card is less than or equal to the Transaction Date (local to the terminal). If the Application Effective Date is greater than Table 7-3: Application Usage Control (AUC)
Byte b8 b7 b6 b5 b4 b3 b2 b1 Usage
1 1b x x x x x x x Valid for domestic cash transactions
1 x 1b x x x x x x Valid for international cash
transactions
1 x x 1b x x x x x Valid for domestic goods
1 x x x 1b x x x x Valid for international goods
1 x x x x 1b x x x Valid for domestic services
1 x x x x x 1b x x Valid for international services
1 x x x x x x 1b x Valid at ATMs
1 x x x x x x x 1b Valid at terminals other than ATMs
2 1b x x x x x x x Domestic cashback allowed
2 x 1b x x x x x x International cashback allowed
7 Processing Restrictions Visa Integrated Circuit Card Specification (VIS)
7.4 Prior Related Processing Version 1.5
7.3.4 Application Expiration Date
The terminal validates that the application has not expired by ensuring that the
Application Expiration Date from the card is greater than or equal to the Transaction Date (local to the terminal). If the Application Expiration Date is less than the Transaction Date, then the terminal sets the ‘Expired application’ bit of the TVR to 1b.
7.4 Prior Related Processing
Read Application Data
The terminal uses the READ RECORD command to obtain ICC records to be used for the application. These records include the Issuer Country Code, Application Version Number, and Application Expiration Date and, if present, the AUC and Application Effective Date.
7.5 Subsequent Related Processing
Terminal Action Analysis
During Terminal Action Analysis, the terminal checks the Issuer Action Codes (IAC) and Terminal Action Codes (TAC) to determine the transaction disposition if application versions differ, the card is not yet effective or expired, or the requested service is not allowed for the card.
Visa Integrated Circuit Card Specification (VIS) 8 Cardholder Verification
Version 1.5