Category list

7.9 Processing restrictions

The decisions of the issuer concern the policies regarding:

The management of the Application Version Number (ICC, tag 9F08);
The management of the type of transaction to be carried out by the ICC ”Application Usage Control (ICC, tag 9F07);
Application effective/expiration dates management.

7.9.1 Application usage control

This data object with tag 9F07 in the card is mandatory to be listed in the AFL. It establishes the type of environment and the range of services for which the card is issued:

Type of environment : domestic or international;
Range of services : goods, services, and ATM cash withdrawal.

If the issuer has subscribed to a card brand offered by a financial organization, then the structure and content of the Application Usage Control is defined for each brand.

Otherwise, the issuer has to define this parameter. Let us assume that the issuer offers a credit card product to be used in the following way:

The credit card can be used for ATM cash withdrawal or for manual cash disbursement in a bank office in the international environment.
The credit card can be used for paying for goods and services in both the domestic environment and the international environment.
The credit card can be used for obtaining cashback at any POS in the domestic environment.

In this case the Application Usage Control bytes could be set up as follows .

Byte 1

Bit 8 = 0: Invalid for domestic cash transactions;
Bit 7 = 1: Valid for international cash transactions;
Bit 6 = 1: Valid for domestic goods;
Bit 5 = 1: Valid for international goods;
Bit 4 = 1: Valid for domestic services;
Bit 3 = 1: Valid for international services;
Bit 2 = 1: Valid at ATMs;
Bit 1 = 1: Valid at terminals other than ATMs;

Byte 2

Bit8=1: Domestic cashback is allowed;
Bit7=0: International cashback is not allowed;
Bit 6 “1 = RFU.

7.9.2 Application Version Number

The Application Version Number in the card (ICC, tag 9F08) is intended for the management of the backward compatibility between a card application and a terminal application.

Terminal applications will be backward compatible and will normally support all current version numbers . If the terminal identifies a card application in the ICC with a version number that is obsolete, the TVR bit will be set (bit 7, byte 2 of TVR). Contrarily, if the terminal identifies an ICC storing an application with a version number higher than its own most recent version, then the bit "ICC and terminal have different application versions" (bit 8, byte 2 of TVR) will be set. In both cases the issuer and acquirer policies, as defined in the terminal and Issuer Action Codes, are considered in order to continue or to stop the processing of the current transaction.

7.9.3 Application effective/expiration dates

The Application Expiration Date (tag 5F24 in the ICC) in the format YYMMDD must be set up by the issuer. This expiration date must be consistent with other information stored on the card:

The two digits DD for the expiration day must be the same as the last day of the expiration month embossed /laser engraved on the card.
The date in tag 5F24 must be consistent with the data on the magnetic stripe, if any, for fallback compatibility between the data in the ICC and data on the magnetic stripe.

It is not mandatory for the Application Effective Date (tag 5F25 in the ICC) to be stored in the card.