TERMINAL APPLICATION CERTIFICATION

GUIDE

Document Status: Final

Version: 1.7C
Date: June 2021
Data Classification: CONFIDENTIAL
Data Owner INTERAC CORP
Audience: Canadian Acquirers
Test Tool Vendors

INTERAC TERMINAL APPLICATION CERTIFICATION GUIDE

VERSION 1.7C – CONFIDENTIAL

TABL E OF CO NT E NT S

TABLE OF CONTENTS ................................................................... 2

1. CHANGE HISTORY NOTES ............................................................ 5

2 INTRODUCTION ..................................................................... 10

2.1 Overview 10
2.2 Audience 10
2.3 Terminal Application Certification 10
2.4 Specifications 11
2.5 Pre-Requisite 11
2.6 Testing/Test Tool Requirements 12
2.7 Related Certifications 12
2.7.1 ICC Application Certification 12
2.7.2 Functional Certification 12
2.7.3 End to End Certification 12
2.8 Terms and Abbreviations 12

3 TERMINAL PARAMETERS ........................................................... 14

4 TEST CASES ........................................................................ 20

4.1 Selection 20
4.1.1 Select01 – Interac Application 20
4.1.2 Select02 - Interac Application with Partial Name Selection 21
4.1.3 Select03 - Interac Application when the ICC Supports PSE 21
4.1.4 Select04 - Interac Application with PSE and Multiple Applications 22
4.1.5 Select05- Interac Application, Terminal Supports PSE, ICC Does Not 23
4.1.6 Select06- No Mutually Supported AID contained in PSE 23
4.1.7 Select07- Interac Application, ICC Supports PSE, Terminal Does Not 24
4.1.8 Select09 - Check Issuer Country Code, Multiple Applications on ICC 25
4.1.9 Select13 - Check Application Selection Flag, Application Not Permitted for POS {POS} 26
4.1.10 Select19 – Applications Placed in Primary are Offered for Selection 27
4.1.11 Select21 – Application is Blocked {POS} 29
4.1.12 Select26 - Check Application Selection Flag, Application Not Permitted for ABM {ABM} 30
4.1.13 Select32 – Applications Placed in Primary are Offered for Selection {ABM} 31
4.1.14 Select34 - Application is Blocked {ABM} 32
4.1.15 Select39 – Multi-Application Card –Terminal Supports One Application 32
4.1.16 Select40a – Multi-Application Card –Terminal Supports Both Applications 35
4.1.17 Select40b – Multi-Application Card –Terminal Supports Both Applications 37
4.1.18 Select41 – Multi-Application Card –Terminal Supports Both, Interac Application Not Permitted for POS {POS}
40
4.1.19 Select42 – Multi-Application Card –Terminal supports both applications {ABM} 43
4.1.20 Select43 - Interac Application is the Only Mutually Supported Application 45
4.1.21 Select44 - Interac Application, Application Permitted for ABM Only {ABM} 47
4.1.22 Select45 - Interac Application, Application Permitted for POS Only {POS} 50
4.1.23 Select46 – Multi-Application Card –Terminal Supports Both Applications {POS} 53
4.2 Card Reading Tests 56
4.2.1 Card01 – ICC Read not Magnetic Stripe (Service Code Begins with a ‘2’) 56

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 2

 4.2.2 Card02 – ICC Read not Magnetic Stripe (Service Code Begins with a ‘6’) 56
4.3 Function Tests 57
4.3.1 Function01 –Get Processing Command 57
4.3.2 Function02 –Card with a PDOL 58
4.3.3 Function04 – Offline Data Authentication Not Supported 59
4.3.4 Function07 – Offline Plaintext PIN 59
4.3.5 Function08 – Offline Enciphered PIN 60
4.3.6 Function09 – Offline Plaintext PIN {ABM} 61
4.3.7 Function10 –Offline Enciphered PIN {ABM} 62
4.3.8 Function11 –Online PIN 63
4.3.9 Function12 – Online PIN {ABM} 64
4.3.10 Function17 – Get Challenge 64
4.3.11 Function22 – Floor Limit {ABM} 65
4.3.12 Function23 – Floor Limit {POS} 66
4.3.13 Function24a – Offline Data Authentication successful (SDA Supported) 66
4.3.14 Function24b – OFFLINE Data Authentication Failed (SDA Supported) 67
4.3.15 Function25 – Enciphered Offline PIN verification fails – Key Absent 69
4.3.16 Function26a – Offline Data Authentication Successful (CDA Supported) 69
4.3.17 Function26b – Offline DAta Authentication Failed (CDA Supported) 70
4.3.18 FUNCTION27a - Offline Data Authentication Successful (DDA Supported) 71
4.3.19 FUNCTION27b - Offline Data Authentication Failure (DDA Supported) 73
4.4 Minimum Data Elements 80
4.4.1 Data01 – Data Elements Resident (1) 80
4.4.2 Data02 – Data Elements Resident (2) 81
4.4.3 Data03 – Data Elements Resident (3) 82
4.4.4 Data04 – Data Elements Resident (4) 83
4.4.5 Data06 – Card Verification Method Results, CVM Failure 83
4.4.6 Data07 – Card Verification Method Results, CVM Unknown {ABM} 84
4.4.7 Data08 – Card Verification Method Results, CVM Success 85
4.4.8 Data09 – POS Entry Mode Code Setting 86
4.5 Cardholder Interface 87
4.5.1 Inter02 – Language - French and English 87
4.5.2 Inter03 – Language - French 87
4.5.3 Inter04 – Language - English 88
4.5.4 Inter05 – Language - Use 2nd Language Supported by the ICC 89
4.6 Other 90
4.6.1 Other03 – Fallback Card Faulty 90
4.6.2 Other04 – Fallback Card Faulty 90
4.7 Transit 92
4.7.1 Transit001 – SAF (Purchase Approved with CDA) 92
4.7.2 Transit002 – SAF (Purchase Declined with CDA) 93
4.7.3 Transit003 – SAF (Purchase Approved with no CDA) 94
4.8 Terminal to Acquirer Host testing (Internal tests) 96
4.8.1 EndToEnd01 – Terminal Sends ARQC in Authorisation Message 96
4.8.2 EndToEnd04 – Issuer Script is sent to ICC (‘72’ tag’) 96
4.8.3 EndToEnd05 – Issuer Script is sent to ICC (‘71’ tag’) 97
4.8.4 EndToEnd06 – Support of Large Issuer Script (‘72’ tag’) 98
4.8.5 EndToEnd07 – Support of Large Issuer Script (‘71’ tag’) 98
4.8.6 EndToEnd09 - Reversal Sent if ICC Responds with AAC 99
4.8.7 EndToEnd10 – Fallback Card Faulty 100

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 3

 4.9 Receipt Printing 101
4.9.1 Tr_Record01 – Print Transaction Record (Approved) 101
4.9.2 Tr_Record02 – Print Transaction Record (Declined) 102

5 INFORMATION CONFORMANCE STATEMENT (ICS) FORM ......................... 104

6 APPENDIX A - CHECK LIST ........................................................ 105

6.1 POS Terminal Tests – Mandatory Tests 105

6.2 POS Terminals Tests – Additional Tests based on supported functionality in ICS 106
6.2.1 POS Terminal Supports SDA [ICS 3.1 = YES] 106
6.2.2 POS Terminal Supports DDA [ICS 3.2 = YES] 106
6.2.3 POS Terminal Supports CDA [ICS 3.3 = YES] 107
6.2.4 POS Terminal with combined Chip / Magnetic Stripe Reader [ICS 1.5 = YES] 107
6.2.5 POS Terminal with Separate Magnetic Stripe Reader [ICS 1.7 = YES] 107
6.2.6 POS Terminal supports PSE SELECTION [ICS 4 = YES] 107
6.2.7 POS Terminal DOES Not Supports PSE Selection [ICS 4 = NO] 108
6.2.8 POS Terminal Does Not Support Offline Data Authentication [ICS 1.1= YES and ICS 3 = NO]108
6.2.9 POS Terminal Supports Online PIN [ICS 1.4 = YES] 108
6.2.10 POS Terminals Support Transit Open Payments [ICS 5 = YES] 108
6.3 ABM Terminal Tests – Mandatory Tests 109
6.4 ABM Terminals Tests – Additional tests based on supported functionality in ICS 110
6.4.1 ABM Terminal DOES not Support Offline Data Authentication [ICS 3 = ‘No] 110
6.4.2 ABM Terminal Supports SDA [ICS 3.1=YES] 110
6.4.3 ABM Terminal Supports DDA [ICS 3.2=YES] 110
6.4.4 ABM Terminal Supports CDA [ICS 3.3=YES] 110
6.4.5 ABM Terminal supports PSE Selection [ICS 4 = ‘Yes’] 111
6.4.6 ABM Terminal Does Not Support PSE Selection [ICS 4 = ‘No’] 111
6.4.7 ABM Terminal Supports Offline PIN Verification [ICS 2.1=YES] 111
6.5 Terminal to Acquirer Host Testing (optional, as require connectivity to a host simulator) 111

7 APPENDIX B - CARD PROFILES USED IN THE TESTING PROCESS ................ 112

7.1 Default Card 1 – Supports Offline Enciphered and Plaintext PIN 112
7.2 Card 2 – Supports SDA 114
7.3 Card 3 Supports Offline Enciphered PIN 115
7.4 Card 4 – Supports DDA and Plaintext PIN 116
7.5 Card 5 – Card Contains a PSE 117
7.6 Card 6 – Card Contains 2 Mutually Supported Applications 117
7.7 Card 7 – Supports Online Enciphered PIN 117
7.8 Card 8 – Supports CDA 117
7.9 Card 10 – Multi Application Non-cobadge Card 120
7.10 Card 11a – Multi Application Cobadge Card 121
7.11 Card 11b – Multi Application Cobadge Card 121
7.12 Card 12 – Multi Application Credit Card 121
7.13 Card 13 – Supports all offline data authentication methods 122
7.14 Other Card Information 124
7.15 Issuer RSA Key Information 124

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 4

1 . CHA NGE HI S TO RY NOT E S

Date Author Version Change Reference/ CR #

Sept 2006 Interac Corp. 1.0 Minor amendments due to comments on Draft D and
upgraded to version 1.0

Nov 2006 Interac Corp. 1.0 Reformatting of document

Removal of Card01,02 from mandatory tests

Minor wording changes

Nov 2006 Interac Corp. 1.1 Updates based on comments from

Participants/Vendors.

Feb 2007 Interac Corp. 1.2 Service Code in Card Profile set to ‘220’ and ICC
Private Key added

Procedure and card details change for Data06

Minor amendments to test Function02 due to

Participant comments

Function17 and 23 removed from the ABM checklist

as POS test

Function22 removed from POS checklist as ABM test

and moved to be an optional ABM test

Function12 moved to be an optional test as the user

may or may not have access to a host

Changes made due to Bulletin #5

- Terminal Action Codes for Online Terminals with

offline capability have been amended
- Tests Other04,05 have had their specification
references updated
Changes made due to Bulletin #4

- Terminal Action Codes for ABMs for TAC-Online

and Default have been added

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 5

Date Author Version Change Reference/ CR #
May 2007 Interac Corp. 1.2 Removed Select12 test as same test as Select26

Hash for the CA Public Key added

Function21 procedure and pass criteria enhanced for

clarity

Terminal Parameters section and card profiles

(profile 6) have been amended so that the 2nd
Application supported by the terminal can be an
existing supported Application i.e. Visa or Mastercard
and does not necessarily have to be the test
application

May 2008 Interac Corp. 1.3 Test case clarifications – Select 21, 34 and Data 09,
add CA Private key part in Terminal parameters

May 2011 Interac Corp. 1.4 Modify card profiles, to extend application expiration
date

Card 1

Card 2

Card 3

Card 4

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 6

Date Author Version Change Reference/ CR #
February Interac Corp. 1.5 Update all test cases from 4.1 to 4.9 to include
2019 reference to actual specification sections.

Removed Test cases:

- Select 08, 10, 11, 14, 15, 16, 17, 18, 20, 24, 22, 23,
25, 27, 28, 29, 30, 31, 33, 35
- Function 13, 20, 21
-Inter 01
-Offline 03, 04, 08, 09, 10, 11, 12

Added Test cases:

- Select 39, 40a, 40b, 41, 42, 43, 44, 45, 46
-Function 24, 25, 26, 27, 31
- Offline 13
- Tr_Record01, Tr_record02

Update Test Cases:

- - Select 09
- - Function 17
- - Offline 01, 02- End to End02,03,08 now Function
28,29,30. These are now mandatory POS test cases
to validate that Faster EMV (Quick chip) is not
supported in Canada.

Added new card profiles:

Card 8, 10, 11a, 11b, 12

Revised ICS Form - Appendix A

Revised Checklist – Appendix B
Revised Card Profile – Appendix C

Update Test Cases:

- - Pass criteria for Select 04
-
Removed Test cases:
- Function 27

Update Default Card Profile 1 with tag 8E value

’00 00 00 00 00 00 00 00 04 03 01 03 02 03’

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 7

Date Author Version Change Reference/ CR #
March Interac Corp. 1.5b - Update Default Card Profile 1
2019 - Updated Card profile 3

November Interac Corp. 1.6 Updates

2019
Section 3 - terminal parameters (key 07)
Section 5- ICS (removed Offline only and added
Transit)
Section 6 Appendix A – updated checklist
Section 6 Appendix B: updated card profiles 1, 2, 4, 8,
13

Modified test cases

Select09,19,21, 34, 39, 40a, 40b, 41, 42, 43, 44, 45,
46

New test cases

Transit001, 002, 003, 24a, 24b, 26a, 26b, 27a, 27b

Removed test cases:

Function24, 26, 27, 28, 29, 30
Offline01, 02, 05, 06, 07, 13

January Interac Corp. 1.7 Updates

2020 Appendix A ICS to include option for COTS
certification

January Interac Corp. 1.7a Removed CA Private Key data from

2020 section 3 Terminal Parameters

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 8

Date Author Version Change Reference/ CR #
February Interac Corp. 1.7b Terminal Parameters section updated with:
2020 - UpdateCA Public Key Check Sum Value
- Removed CA Public Key Check Hash Value

May 2020 Interac Corp. 1.7C - Default Card 1 Updated PAN

- Updated Terminal Parameters with CA Public Key
Index ‘03’
- Updated test cases
• Function 07; Function 08; Function 09;
Function 10; Function 25; Function 26a
- Added test cases.
• Function 26c; Function 28; Function 29;
Function 30; Function 31
- Updated checklist sections 6.1; 6.2.3
- Updated Card 8
- New Card 8a
- Added section 7.16 Issuer RSA Key Information

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 9

 2 I NT ROD UCT I ON

2.1 Overview

The objective of the Certification is to ensure that a Participant’s chip terminals operate
accurately when implemented on the Inter-Member Network (IMN) and does not affect the
reliability of the existing Shared Services.

The overall Certification includes certifying various components prior to implementation on

the IMN with Chip terminal and ICC cards.
• Terminal Application Certification
• ICC Application Certification
• Functional Certification
• End to End(E2E) Certification

Certification does not include volume, stress or regression testing. The Participant is
responsible for testing this internally.

The Certification Guide is to be read in conjunction with the Operating Regulations. If the
Certification Guide and the Regulations appear to be contradictory, the Regulations will
always take precedence.

2.2 Audience

The intended audience of this document is Interac Corp. and Interac Corp. Participants who
wish to achieve certification with Interac. Test tool vendors must use this document to
implement their scripts for the certification procedure.

2.3 Terminal Application Certification

This is required to certify Interac Debit and Interac Cash Terminal application functionality
between the terminal application and the ICC.
Terminal Certification consists of two parts – device and application:
• Device
o Participants certify the PED in compliance with PCI SSC Standards.

• Terminal application
o Terminal to card interface
▪ Participants run a series of test scripts using Interac test tool.
▪ Participants submit a completed certification checklist to Interac
Corp. for review and approval for certification.
o Terminal to Acquirer interface

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 10

 ▪ Participants run a series of test scripts using an Internal test tool
or other test environment.
▪ Onus is on the Participant to run the test cases internally.
▪ Test cases are provided in this document for terminal to acquirer
interface as guidelines. Participants are responsible to test this
appropriately.

This guide is designed to help the Interac Participant to test their terminal application so
that certification can be achieved with Interac. Anything referenced within the Interac
Specification as being ‘as per EMV specification’ is outside the scope of this guide as one
of the pre-requisites is that the terminal has already achieved EMV Level 2 certification with
EMVCo.

The execution of the certification process is the Participant’s responsibility. The Participant
must acquire the appropriate Interac approved test tool and corresponding test scripts.
Interac Corp. maintains a list of approved test tool vendors. During Certification, the
Participant can demonstrate that the application is working correctly by enacting a series of
test cases and test scripts as detailed in this test guide.

There are a number of configurations that exist (i.e. whether the terminal is an ABM or a
POS, or online only terminal, etc.). The Tester will select the checklist (using Appendix A
“Checklist” as a guide), to certify the terminal application. The results of the test cases will
be recorded and submitted (along with the other relevant documentation) to Interac Corp.
for review and approval.

2.4 Specifications

The specifications used within are:

• EMV Books 1 - 4, version 4.3

• Interac Cash Terminal Specification 4.4 or higher
• Interac Debit Terminal Specification 4.7 or higher
• Reader Terminal specification for Interac Flash 1.5b or higher

2.5 Pre-Requisite

The following pre-requisites are needed before the application is submitted for certification:

• The terminal must be formally approved and recognized by EMVCo for EMV
Level 1
• The terminal must be formally approved and recognized by EMVCo for EMV
Level 2
• The terminal must be formally approved and recognized by PCI SSC.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 11

 2.6 Testing/Test Tool Requirements

• The Interac test tool used allows the tester to see the communication between
the card and the terminal i.e. the test tool should have the ability to show the
commands sent and received by the card, and the result of the commands.
• That logs can be provided to Interac for support and investigation purposes.
• The tester has the relevant knowledge of the test tool and can interpret any log
files or diagnostics produced to determine whether the test case has passed.
• This document tests the functionality between the terminal application and the
ICC hence most of the mandatory tests do not need to go online however an
online terminal may attempt to go online to complete the transaction. While the
use of a test host is outside the scope of this document, in this version there are
a few mandatory tests that need to go online for ARQC validation using a test
host or host simulator. (For the optional tests in section ‘Terminal to Acquirer
Host testing’, the user will need a test host).

2.7 Related Certifications

2.7.1 ICC APPLICATION CERTIFICATION

This is required to certify the ICC application. The process and test cases are specified in the
ICC Application Certification Guide.

2.7.2 FUNCTIONAL CERTIFICATION

This is required to certify the IMN/AIL functionality and the host processing of the transactions.
The process and test cases are specified in the Certification Guides Volumes 1 – 3.

2.7.3 END TO END CERTIFICATION

This is the final stage of certification process to test all the certified components together end to
end. The process and test cases are defined in the Certification Guide Volumes 1 – 3.

2.8 Terms and Abbreviations

AAC Application Authentication Cryptogram

AAR Application Authorisation Referral
AC Application Cryptogram
AFL Application File Locator
AID Application Identifier
ARPC Authorisation Response Cryptogram
ARQC Authorisation Request Cryptogram
ASI Application Selection Indicator
ATR Answer To Reset

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 12

CDA Combined DDA/Application Cryptogram Generation
CDOL Card Risk Management Data Object List
CID Cryptogram Information Data
CVM Cardholder Verification Method
CVMR Card Verification Method Results
DDA Dynamic Data Authentication
EMV Europay, Mastercard and VISA
ICC Integrated Circuit Card
IDP Interac Direct Payment
MAC Message Authentication Code
PAN Primary Application Number
PED PIN Entry Device
PIN Personal Identification Number
POS Point of Sale
PSE Payment Systems Environment
SCD Interac Shared Cash Dispensing
SDA Static Data Authentication
SW1 First byte of the Status Words returned by the card
SW2 Second byte of the Status Words returned by the card
TC Transaction Certificate
TVR Terminal Verification Results

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 13

 3 T E RM I NAL PA RA M E T E RS

The following table contains an example as to how the terminal may be configured for the
certification process. If a data element needs to be a specific value due to the specification or to
ensure that testing can be fully performed will be highlighted in blue:

Data Element Value(s) Comment

Application Identifiers ‘A0000002 77 10 10’ Interac AID

Supported (AIDs)
The terminal should be This AID will also be used
configured with all AIDs as a partial match for other
supported Test Apps on the card i.e.
the card will contain test
application AIDs:

‘A0000002 77 10 10 01’ and

‘A0000002 77 10 10 02’

Another AID will also be

needed for some of the
tests
Application Selection For both AIDs above
Indicator ‘A000000277 10 10’

- the associated AID in the terminal

can match up to the length of the
AID in the terminal
Application Version ‘01’
Number
CA Public Key Index ‘07’ Index for Interac Public Key
CA Public Key Modulus ‘B2 CE 89 72 6B 6B 2D 16 90 A0
F8 CA 75 CD 0B 6B 1A CD FB E6
6D 53 BA 00 C5 00 BE 61 2F B4 21
42 36 84 FF 18 68 55 4A 77 22 25
80 12 E5 88 ED 1C D2 06 C6 7B
B2 F7 59 8F 3C E6 7F 23 A8 88 B8
ED 74 21 C4 9A 2E BA 22 4D FB
D8 66 F6 2E 59 33 8E 9F 62 6D 0D
FD 4C 9A CC 62 6E 42 EC 03 75
EE 42 4C 93 E5 DB 57 73 FC 98
E4 AC 9F CD EB D0 52 1B 15 29
5C 79 7D CA BB 46 79 C0 55 AC

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 14

 37 4A 81 B2 45 AB F1 09 2A 3D 46
E1 CC E1 0A 84 F9 FC 2F C6 ED
91 02 51 21 58 9C 9A A6 8B 56 B7
FB F0 D8 6B 4C 8E 3C 9C 08 40
6D BB 46 09 BB FC 53 08 F3 25 A8
27 3C B6 D3 6F 3E 0A F7 72 50 7B
F8 A2 A9 F5 A7 49 B5 AF 98 CC
EA B2 82 6C 2D 9C 2A B9 10 3B
1B AB 0D E9 20 99 C8 07 24 77 EC
56 40 62 AC 38 18 4C 60 DA D2 98
EF 35 2D 92 DF A0 41 DD E3 DB
26 0C E5 30 2B 47 A7 E9’
CA Public Key Exponent ’010001’
Certification Authority 44 F2 C1 33 73 A5 06 8B 63 C9 33
Public Key Check Sum 4E 91 4D DE 6A B7 0C E0 F1

Certification Authority 01
Hash Algorithm Indicator
Certification Authority 01
Public Key Algorithm
Indicator

CA Public Key Index ‘03’ Index for Interac Public

Key
CA Public Key Modulus E5 15 05 CC EC DD 07 99 BA FE 09 72
00 DF 40 FF C2 15 48 36 B8 D6 7F 1E 99
D4 D4 15 F7 3C 04 A9 FA D7 38 25 D3
2A E5 BA 77 FC D0 25 97 39 3C E4 D8 10
4B 60 10 D5 A8 F2 8F 2B 47 BB 82 98 DA
FD 63 C9 C0 BE F6 2A F9 37 26 56 14 E3
1A E2 AB 45 B6 0B 96 8D B9 DE E5 56
02 C1 69 F6 C1 6D 45 79 BA A2 47 65 56
03 00 A3 05 6F 89 4B A8 FF A5 66 D9 CC
D7 94 53 D8 04 B9 7D A1 4F 21 F9 C3 52
8E D8 B8 A3 68 A9 FA CF 05 C4 6C 13
A9 BA 02 06 18 42 5E F1 AC F6 CB 4D
D5 DC D0 50 27 35 02 11 4B 59 EE 90 EB
D8 33 F7 0C 2F 32 47 41 E7 9A 19 A1
CA Public Key Exponent ’010001’
Certification Authority 0F B6 0A 1B CA 38 09 5F 3C C5 78 D2
Public Key Check Sum DE C9 5F 77 98 40 A3 43
Certification Authority 01
Hash Algorithm Indicator
Certification Authority 01
Public Key Algorithm
Indicator

Data Element Value(s) Comment

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 15

Default Dynamic Data Contains the tag ‘9F37’
Authentication Data
Object List (DDOL)
Terminal Action Code – For Online Terminals with Offline Not applicable for offline
Default Capability: only terminals
‘FC50F8A8F0’

For ABM terminals:

‘FFFFFFFFFF’
Terminal Action Code – For Online Terminals with Offline
Denial Capability:
‘1010580000’

For Offline only Terminals

‘FC50FCB870’
Terminal Action Code – For Online Terminals with Offline Not applicable for
Online Capability: offline only terminals
‘FCF8E4B870’

For ABM terminals:

‘FFFFFFFFFF’
Terminal Country Code ‘0124’
(‘9F1A’)
Terminal Floor Limit $0 for all online capable POS terminals
(‘9F1B’)

$0 if the terminal is an ABM

Terminal Type (‘9F35’) ‘11’ or ‘21’ Attended online only
’11’ if Acquirer controlled
’21’ if Merchant controlled

‘12’ or ‘22’ Attended online only with

offline capability
’12’ if Acquirer controlled
’22’ if Merchant controlled

‘13’ or ‘23’ Attended offline only

’13’ if Acquirer controlled
’23’ if Merchant controlled

‘14’ or ‘24’ Unattended online only

’14’ if Acquirer controlled
’24’ if Merchant controlled

‘15’ or ‘25’ Unattended online only with

offline capability
’15’ if Acquirer controlled
’25’ if Merchant controlled

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 16

 ‘16’ or ‘26’ Unattended offline only
’16’ if Acquirer controlled
’26’ if Merchant controlled
Transaction Currency ‘0124’
Code (’5f2a’)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 17

The following data elements are needed but are up to the implementer as they do not have a
direct impact on the testing:

Data Element Value(s) Comment

Acquirer Identifier (‘9F01’) Up to Implementer
Additional Terminal Up to Implementer
Capabilities (‘9F40’)
Application Version Up to Implementer
Number (‘9F09’)
Interface Device Serial Up to Implementer
Number (‘9F1E’)
Maximum Target Up to Implementer To be used in Terminal Risk
Percentage to be used for Management
Biased Random Selection
Merchant Category Code Up to Implementer
(‘9F15’)
Merchant Identifier(‘9f16’) Up to Implementer
Point of Service (POS) Up to Implementer
Entry Mode (‘9F39’)
Target Percentage to be Up to Implementer To be used in Terminal Risk
used for Random Management
Selection
Terminal Capabilities Up to Implementer For online only terminals, the
(‘9F33’) terminal must have the following
set:
- ICC with contact Plaintext
PIN for ICC verification

- Enciphered PIN for offline

verification

- Administrative transactions
- Numeric Keys
- Command Keys
- Print – Attendant
- Display – Attendant

Terminals supporting offline

transactions must also support:

- Static Data Authentication

- Dynamic Data
Authentication
- CDA

For ABM terminals the terminal

must have the following set:

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 18

 - ICC with contact
- Enciphered PIN for online
verification
- Cash
- Numeric Keys
- Command Keys
- Print – Cardholder
- Display – Cardholder
Terminal Identification Up to Implementer
(‘9F1C’)
Threshold Value for Up to Implementer To be used in Terminal Risk
Biased Random Selection Management

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 19

 4 T E S T CAS E S

The following section details all the tests applicable for Terminal Application Certification.
Terminals are not required to execute all tests, as they may not support the required
functionality. For each test the required Terminal Configuration is detailed i.e. for the tests
testing PSE functionality the Terminal Configuration is that the terminal supports PSE, if it
doesn’t then the test is not executed on that terminal. Appendix A details the tests that are
applicable for each terminal type, which are mandatory for ABMs and POS, and also details the
optional tests.

4.1 Selection

The following test cases test the application selection functionality of the terminal
application under test.

4.1.1 SELECT01 – INTERAC APPLICATION

Objective To ensure that the terminal can select the Interac application
using full name selection

Specification Interac Debit Terminal Specification (Application Selection)

Interac Cash Terminal Specification (Application Selection)

The terminal shall support full name selection

Terminal All
Configuration

Card Profile to Default card 1

Use

Procedure The card is inserted into the terminal, application selection is

performed, and the transaction goes to completion

Pass Criteria 1. The Interac application should be selected by the

termina.
2. The Select command contains the full Interac AID

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 20

 4.1.2 SELECT02 - INTERAC APPLICATION WITH PARTIAL NAME SELECTION

Objective To ensure that the terminal can select the Interac application
using partial name selection

Specification Interac Debit Terminal Specification (Application Selection)

Interac Cash Terminal Specification (Application Selection)

The terminal shall support full name selection, and partial name
selection

Terminal All - the Interac AID has the ASI indicating partial match is
Configuration accepted i.e. the partial AID is “A0000002771010”

Card Profile to As default card 1 except that the beginning of the AID in the
Use card matches the beginning of the Interac AID kept in the
terminal i.e. the partial AID is “A0000002771010” (actual AID is
‘A000000277101001’

Procedure The card is inserted into the terminal, application selection is

performed, and the transaction goes to completion

Pass Criteria 1. The application ‘A000000277101001’should be

selected by the terminal.
2. The terminal sends the Select command containing
the partial AID followed by Select [Next] command.
3. The AID ‘A000000277101001’ will be the final
SELECT command

4.1.3 SELECT03 - INTERAC APPLICATION WHEN THE ICC SUPPORTS PSE

Objective To ensure that if the terminal and the card support the Payment
System Environment (PSE) that the Interac application can be
selected using the PSE

Specification Interac Debit Terminal Specification (Application Selection)

Interac Cash Terminal Specification (Application Selection)

The terminal may optionally support application selection using

Payment Systems Directories (PSD) as specified in EMV Book 1
Part III, Section 12.3.2.

Terminal PSE Supported [ICS 4 = YES]

Configuration

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 21

Card Profile to As the default card 1 but containing a PSE
Use

Procedure The card is inserted into the terminal, application selection is

performed, and the transaction goes to completion

Pass Criteria 1. The terminal sends the Select command for the PSE
2. The Interac application should be selected by the
terminal

4.1.4 SELECT04 - INTERAC APPLICATION WITH PSE AND MULTIPLE APPLICATIONS

Objective To ensure that if the terminal and the card support the PSE and
the card has more than one application supported by the
terminal, that the Interac application can be selected using the
PSE

Specification Interac Debit Terminal Specification (Application Selection)

Interac Cash Terminal Specification (Application Selection)

The terminal may optionally support application selection using

Payment Systems Directories as specified in EMV Book 1 Part
III, Section 12.3.2. If the terminal supports application selection
using Payment Systems Directory and the PSE is present in the
ICC, the terminal shall proceed with building the list of mutually
supported applications using the Payment Systems Directories.

Terminal PSE Supported [ICS 4 = YES]

Configuration

Card Profile to As the default card 1 but containing a PSE and another
Use application supported by the terminal. The Interac application
has priority ‘1’ whereas the 2nd application has a priority of ‘’02’

Procedure The card is inserted into the terminal, application selection is

performed, and the transaction goes to completion

Pass Criteria 1. The terminal sends the Select command for the PSE.

2. The Interac application should be selected by the

terminal unless Cardholder selection is supported. If
Cardholder selection is supported, then the tester
should select the INTERAC application.

3. The final Select command is for the Interac application.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 22

 4.1.5 SELECT05- INTERAC APPLICATION, TERMINAL SUPPORTS PSE, ICC DOES NOT

Objective To ensure that if the terminal supports application selection

using the PSE but the card does not, that the Interac application
can be selected

Specification Interac Debit Terminal Specification (Application Selection)

Interac Cash Terminal Specification (Application Selection)

If the terminal supports application selection using Payment

Systems Directories, and the PSE is not present in the ICC or
no common application is found in the PSE, the terminal shall
proceed with building the list of mutually supported applications
using the list of AIDs as described in EMV Book 1 Part III,
Section 12.3.3

Terminal PSE Supported [ICS 4 = YES]

Configuration

Card Profile to Default card 1

Use

Procedure The card is inserted into the terminal, application selection is

performed, and the transaction goes to completion

Pass Criteria 1. The terminal sends a series of Select commands for

each AID supported.
2. The final Select command is for the Interac
application

4.1.6 SELECT06- NO MUTUALLY SUPPORTED AID CONTAINED IN PSE

Objective To ensure that if the terminal and the card support application
selection by PSE but the card and terminal do not have a
mutually supported application then the terminal will attempt to
retrieve a mutually supported application using the list of AIDs.

Specification Interac Debit Terminal Specification (Application Selection)

Interac Cash Terminal Specification (Application Selection)

If the terminal supports application selection using Payment

Systems Directories, and the PSE is not present in the ICC or
no common application is found in the PSE, the terminal shall
proceed with building the list of mutually supported applications
using the list of AIDs as described in EMV Book 1 Part III,
Section 12.3.3

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 23

Terminal PSE Supported [ICS 4 = YES]
Configuration

Card Profile to Default Card 1 contains a PSE, but the Interac application is not
Use contained within the PSE

Procedure The card is inserted into the terminal, application selection is

performed, and the transaction goes to completion

Pass Criteria 1. The terminal sends a Select PSE followed by Select

commands for each AID supported.
2. The final Select command is for the Interac
application

4.1.7 SELECT07- INTERAC APPLICATION, ICC SUPPORTS PSE, TERMINAL DOES NOT

Objective To ensure that if the terminal does not support application

selection using the PSE but the card does, that the Interac
application can be selected

Specification Interac Debit Terminal Specification (Application Selection)

Interac Cash Terminal Specification (Application Selection)

If the terminal does not support application selection using

Payment Systems Directories, the terminal shall proceed with
building the list of mutually supported applications using the list of
AIDs as described in EMV Book 1 Part III Section 12.3.3

Terminal PSE Not Supported [ICS 4 = NO]

Configuration

Card Profile to As the default card 1 but containing a PSE

Use

Procedure The card is inserted into the terminal, application selection is

performed, and the transaction goes to completion

Pass Criteria 1. The terminal sends a series of Select commands for

each AID supported.
2. The final Select command is for the Interac application.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 24

 4.1.8 SELECT09 - CHECK ISSUER COUNTRY CODE, MULTIPLE APPLICATIONS ON ICC

Objective To check that the terminal checks the Issuer Country code
(‘5F56’) in the list of mutually supported applications and places
the application in the Primary sub-list

Specification Interac Debit Specification (Final Selection)

Interac Cash Specification (Final Selection)

After building the list of mutually supported applications the

terminal shall examine each application for the presence of the
optional Issuer Country Code and Application Selection Flag
data elements. The terminal shall produce two sub-lists of
mutually supported applications: a PRIMARY and a
SECONDARY sub-list.

Step #1: The terminal shall follow these steps for each
application in the list of mutually supported applications to build
the PRIMARY and SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application

to the PRIMARY sub-list if any one or more of these
conditions are true:
i. The Issuer Country Code (alpha3 format) data element is not
present.
ii. The ASF data element is not present.
iii. The Issuer Country Code (alpha3 format) is present for the
application in question, and the value of the Issuer Country
Code is not equal to “CAN”.
iv. The Issuer Country Code (alpha 3 format) is present and is
equal to “CAN” and the ASF indicates that the application
can be used at non-ABM/ATM terminals as a PRIMARY
application (Byte 2, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and is
equal to “CAN” and the ASF indicates that the application
can be used at non-ABM/ATM terminals as a PRIMARY
application (Byte 2, Bit 8 = “1”) and as a SECONDARY
application (Byte 2, Bit 7 = “1”) at non-ABM/ATM terminals.
Note that the application should only be added to the
PRIMARY sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place

the application in the PRIMARY sub-list, then the terminal

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 25

 shall add the application to the SECONDARY sub-list if
the following condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 2, Bit 7 = “1” and
Byte 2, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has not
already been placed on the PRIMARY sub-list due to
any of the conditions from #1 above.

If none of the conditions place the application in the PRIMARY

or SECONDARY sub-list, the POS terminal shall ignore the
application and not add it to either the PRIMARY or the
SECONDARY sub-list of mutually supported applications

Terminal All
Configuration

Card Profile to Card 6. There are 2 mutually supported applications – Interac

Use Application and another
The first application does not have the Issuer Country code
(‘5F56’) present.
The second application has the Issuer Country code (‘5F56’) but
it is not equal to ‘CAN’ and has the Application Priority Indicator
set to ‘02’.

Procedure The card is inserted into the terminal.

Pass Criteria Both applications should be presented to the cardholder if

cardholder selection supported otherwise App1 should be
selected

4.1.9 SELECT13 - CHECK APPLICATION SELECTION FLAG, APPLICATION NOT PERMITTED FOR POS
{POS}

Objective To check that the terminal checks the Application Selection

Flag if the Issuer Country code (‘5F56’) is present and equal to
“CAN” and if the Application Selection Flag indicates that the
application cannot be used at POS terminals as a PRIMARY
application or SECONDARY application when the terminal is a
POS terminal then the application cannot be selected.

Specification Interac Debit Terminal Specification (Final Selection)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 26

 The coding of the optional Application Selection Flag data
element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use as
PRIMARY
application at ABM
Bit 7= 1: Use as
SECONDARY
application at ABM
Bit 6-1:RFU
2 Non-ABM (i.e. b Bit 8 = 1: Use as
POS) usage PRIMARY
application at non-
ABM terminals
Bit 7= 1: Use as
SECONDARY
application at non-
ABM terminals
Bit 6-1:RFU
3 - 32 RFU -

Terminal POS terminal [ICS = 1]

Configuration

Card Profile to Default Card 1 with the Application Selection Flag (DF62) set
Use as ‘8000’.
There is only 1 mutually supported application – Interac
Application.
The application has the Application Selection Flag present and
has byte 1 bit 8 set and byte 2 bit 8 and 7 not set. The
application has the Issuer Country code (‘5F56’) equal to ‘CAN’

Procedure The card is inserted into the terminal but the application on the
card cannot be used at an POS terminal

Pass Criteria The terminal should terminate the transaction as a mutually

supported application cannot be found.

4.1.10 SELECT19 – APPLICATIONS PLACED IN PRIMARY ARE OFFERED FOR SELECTION

Objective To ensure that if there are 2 applications in the card and both
applications are placed into the PRIMARY list that both are
presented to the customer

Specification Interac Terminal Specification (Final Selection)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 27

Step #1: The terminal shall follow these steps for each
application in the list of mutually supported applications to
build the PRIMARY and SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application

to the PRIMARY sub-list if any one or more of these
conditions are true:
i. The Issuer Country Code (alpha3 format) data element
is not present.
ii. The ASF data element is not present.
iii. The Issuer Country Code (alpha3 format) is present for
the application in question, and the value of the Issuer
Country Code is not equal to “CAN”.
iv. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”) and as a
SECONDARY application (Byte 2, Bit 7 = “1”) at non-
ABM/ATM terminals. Note that the application should
only be added to the PRIMARY sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place

the application in the PRIMARY sub-list, then the terminal
shall add the application to the SECONDARY sub-list if the
following condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 2, Bit 7 = “1” and
Byte 2, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has
not already been placed on the PRIMARY sub-list
due to any of the conditions from #1 above.

If none of the conditions place the application in the PRIMARY

or SECONDARY sub-list, the POS terminal shall ignore the
application and not add it to either the PRIMARY or the
SECONDARY sub-list of mutually supported applications.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 28

 If the PRIMARY sub-list of mutually supported application(s) is
not empty, the POS terminal shall present to the Cardholder
this list of application(s).

Terminal POS terminal [ICS = 1]

Configuration

Card Profile to Use Card 6

There are 2 mutually supported applications App1 and App2

App1 does not contain the Application Selection and has
priority ‘1.’
App2 has the Application Selection Flag with byte 2 bit 8 set
for PRIMARY application at POS terminals and has the Issuer
Country code (‘5F56’) equal to ‘CAN’

Procedure The card is inserted into the terminal

Pass Criteria Both applications should be presented to the cardholder if

cardholder selection supported otherwise App1 should be
selected

4.1.11 SELECT21 – APPLICATION IS BLOCKED {POS}

Objective To ensure that if there are 2 applications in the card with one
defined as a PRIMARY and the other as a SECONDARY and
if the application in the PRIMARY is blocked that the other
application is not offered for selection

Specification Interac Debit Terminal Specification (Final Selection)

If the PRIMARY sub-list becomes empty because of blocked

applications or other EMV means, then the transaction shall be
terminated as specified in EMV Book 1 Part III, Section 12.4

Terminal POS terminal [ICS = 1]

Configuration

Card Profile to Use Card 6 without the Application Selection Flag (DF62) and
blocked at final selection, however, this card will contain a
second application with DF62 = ‘0040’.

There are 2 mutually supported applications App1 and App2

App1 does not contain the Application Selection Flag and is
blocked at final selection.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 29

 App2 has the Application Selection Flag with byte 2 bit 7 set
for SECONDARY application at POS terminals and has the
Issuer Country code (‘5F56’) equal to ‘CAN’

Procedure The card is inserted into the terminal

Pass Criteria The terminal should terminate the transaction after the
selection phase without offering an application for Selection

4.1.12 SELECT26 - CHECK APPLICATION SELECTION FLAG, APPLICATION NOT PERMITTED FOR ABM
{ABM}

Objective To check that the terminal checks the Application Selection

Flag if the Issuer Country code (‘5F56’) is present and equal to
“CAN” and if the Application Selection Flag indicates that the
application cannot be used at ABM terminals as a PRIMARY
application or SECONDARY application when the terminal is
an ABM terminal then the application cannot be selected.

Specification Interac Cash Terminal Specification (Final Selection)

The coding of the optional Application Selection Flag data

element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use
as PRIMARY
application at
ABM
Bit 7= 1: Use
as
SECONDARY
application at
ABM
Bit 6-1:RFU
2 Non-ABM (i.e. b Bit 8 = 1: Use
POS) usage as PRIMARY
application at
non-ABM
terminals
Bit 7= 1: Use
as
SECONDARY
application at
non-ABM
terminals
Bit 6-1:RFU
3 - 32 RFU -

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 30

Terminal ABM terminal [ICS = 2]
Configuration

Card Profile to Use Default Card 1. There is only 1 mutually supported application
– Interac Application.
The application has the Application Selection Flag present and
has byte 2 bit 8 set and byte 1 bit 8 is not set.
The application has the Issuer Country code (‘5F56’) equal to
‘CAN’

Procedure The card is inserted into the terminal but the application on the
card cannot be used at an ABM terminal

Pass Criteria The terminal should terminate the transaction as a mutually

supported application cannot be found

4.1.13 SELECT32 – APPLICATIONS PLACED IN PRIMARY ARE OFFERED FOR SELECTION {ABM}

Objective To ensure that if there are 2 applications in the card and both
applications are placed into the PRIMARY list that both are
presented to the customer

Specification Interac Cash Terminal Specification (Final Selection)

If the PRIMARY sub-list of mutually supported application(s) is

not empty, the ABM terminal shall present to the Cardholder
this list of application(s).

Terminal ABM terminal [ICS = 2]

Configuration

Card Profile to Use Card 6. There are 2 mutually supported applications App1 and
App2.
App1 does not contain the Application Selection and has
priority ‘1’.
App2 has the Application Selection Flag with byte 1 bit 8 set
for PRIMARY application at ABM terminals and has the Issuer
Country code (‘5F56’) equal to ‘CAN’

Procedure The card is inserted into the terminal

Pass Criteria Both applications should be presented to the cardholder if

cardholder selection is supported otherwise App1 will be
selected

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 31

 4.1.14 SELECT34 - APPLICATION IS BLOCKED {ABM}

Objective To ensure that if there are 2 applications in the card with one
defined as a PRIMARY and the other as a SECONDARY and
if the application in the PRIMARY is blocked that the other
application is not offered for selection

Specification Interac Cash Terminal Specification (Final Selection)

If the PRIMARY sub-list becomes empty because of blocked

applications or other EMV means, then the transaction shall be
terminated as specified in EMV Book 1 Part III, Section 12.4

Terminal ABM terminal [ICS = 2]

Configuration

Card Profile to Use Card 6. There are 2 mutually supported applications App1 and
App2
App1 does not contain the Application Selection Flag and is
blocked at final selection.
App2 has the Application Selection Flag with byte 1 bit 7 set
for SECONDARY application at ABM terminals and has the
Issuer Country code (‘5F56’) equal to ‘CAN’

Procedure The card is inserted into the terminal

Pass Criteria The terminal should terminate the transaction after the
selection phase without offering a final application Selection

4.1.15 SELECT39 – MULTI-APPLICATION CARD –TERMINAL SUPPORTS ONE APPLICATION

Objective To check that if the card is a multi-application card but the

POS does not support the second application that the
INTERAC application is automatically selected.

Specification Interac Debit Terminal Specification (Final Selection)

The coding of the optional Application Selection Flag data

element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use
as PRIMARY
application at
ABM
Bit 7= 1: Use
as
SECONDARY

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 32

 application at
ABM
Bit 6-1:RFU
2 Non-ABM b Bit 8 = 1: Use
(i.e. POS) as PRIMARY
usage application at
non-ABM
terminals
Bit 7= 1: Use
as
SECONDARY
application at
non-ABM
terminals
Bit 6-1:RFU
3- RFU -
32

After building the list of mutually supported applications the

terminal shall examine each application for the presence of the
optional Issuer Country Code and Application Selection Flag data
elements. The terminal shall produce two sub-lists of mutually
supported applications: a PRIMARY and a SECONDARY sub-list.

Step #1: The terminal shall follow these steps for each application
in the list of mutually supported applications to build the PRIMARY
and SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application to

the PRIMARY sub-list if any one or more of these conditions
are true:
i. The Issuer Country Code (alpha3 format) data element
is not present.
ii. The ASF data element is not present.
iii. The Issuer Country Code (alpha3 format) is present for
the application in question, and the value of the Issuer
Country Code is not equal to “CAN”.
iv. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”) and as a

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 33

 SECONDARY application (Byte 2, Bit 7 = “1”) at non-
ABM/ATM terminals. Note that the application should
only be added to the PRIMARY sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place the

application in the PRIMARY sub-list, then the terminal shall add
the application to the SECONDARY sub-list if the following
condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 2, Bit 7 = “1” and
Byte 2, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has
not already been placed on the PRIMARY sub-list
due to any of the conditions from #1 above.

If none of the conditions place the application in the PRIMARY or

SECONDARY sub-list, the POS terminal shall ignore the
application and not add it to either the PRIMARY or the
SECONDARY sub-list of mutually supported applications.

If the PRIMARY sub-list of mutually supported application(s) is not

empty, the terminal shall present to the Cardholder this list of
application(s). This presentation of applications shall be as
specified in EMV Book 1 part III, Section 12.4. The terminal shall
provide for confirmation of application by the Cardholder when
specified by the ICC.

Terminal POS Terminal [ICS = 1]

Configuration

Card Profile to Card 10

Use
There is 1 mutually supported application.
App1 and App2 both contain the Application Selection and
have the Issuer Country code (‘5F56’) equal to ‘CAN’
App1 has the Application Selection Flag with byte 1 bit 8 byte
and 2 bit 8 set for PRIMARY application at ABM and POS
terminals.

App2 on the card is not supported by the terminal (Visa Plus).

Procedure The card is inserted into the terminal

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 34

 Pass Criteria The terminal should automatically select the INTERAC
application.

4.1.16 SELECT40A – MULTI-APPLICATION CARD –TERMINAL SUPPORTS BOTH APPLICATIONS

Objective To check that if the card has more than one application
supported by the terminal, the terminal checks the Application
Selection Flag if the Issuer Country code (‘5F56’) is present
and equal to “CAN” and if the Application Selection Flag
indicates that the other application cannot be used at POS
terminals as a PRIMARY application or SECONDARY
application then only the application with bit 8 set is placed in
the PRIMARY list.

Specification Interac Debit Terminal Specification (Final Selection)

The coding of the optional Application Selection Flag data

element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use
as PRIMARY
application at
ABM
Bit 7= 1: Use
as
SECONDARY
application at
ABM
Bit 6-1:RFU
2 Non-ABM b Bit 8 = 1: Use
(i.e. POS) as PRIMARY
usage application at
non-ABM
terminals
Bit 7= 1: Use
as
SECONDARY
application at
non-ABM
terminals
Bit 6-1:RFU
3- RFU -
32

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 35

After building the list of mutually supported applications the
terminal shall examine each application for the presence of the
optional Issuer Country Code and Application Selection Flag data
elements. The terminal shall produce two sub-lists of mutually
supported applications: a PRIMARY and a SECONDARY sub-list.

Step #1: The terminal shall follow these steps for each application
in the list of mutually supported applications to build the PRIMARY
and SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application to

the PRIMARY sub-list if any one or more of these conditions
are true:
i. The Issuer Country Code (alpha3 format) data element
is not present.
ii. The ASF data element is not present.
iii. The Issuer Country Code (alpha3 format) is present for
the application in question, and the value of the Issuer
Country Code is not equal to “CAN”
iv. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”) and as a
SECONDARY application (Byte 2, Bit 7 = “1”) at non-
ABM/ATM terminals. Note that the application should
only be added to the PRIMARY sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place the

application in the PRIMARY sub-list, then the terminal shall add
the application to the SECONDARY sub-list if the following
condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 2, Bit 7 = “1” and
Byte 2, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has
not already been placed on the PRIMARY sub-list
due to any of the conditions from #1 above.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 36

 If none of the conditions place the application in the PRIMARY or
SECONDARY sub-list, the POS terminal shall ignore the
application and not add it to either the PRIMARY or the
SECONDARY sub-list of mutually supported applications.

If the PRIMARY sub-list of mutually supported application(s) is not

empty, the terminal shall present to the Cardholder this list of
application(s). This presentation of applications shall be as
specified in EMV Book 1 part III, Section 12.4. The terminal shall
provide for confirmation of application by the Cardholder when
specified by the ICC.

Terminal All
Configuration

Card Profile to Card 11a

Use
Card contains 2 mutually supported applications – App1
(Interac AID) and App2.

App1 (INTERAC application) has the Application Selection

Flag present and has Byte 2 bit 8 set to “1” and the Application
Priority Indicator set to priority ‘02’.

App2 (Visa Debit) on the card has the Application Priority

Indicator set to ‘01’.

Procedure The card is inserted into the terminal

Pass Criteria The terminal should automatically select the INTERAC

application.

4.1.17 SELECT40B – MULTI-APPLICATION CARD –TERMINAL SUPPORTS BOTH APPLICATIONS

Objective To check that if the card has more than one application
supported by the terminal, the terminal checks the Application
Selection Flag if the Issuer Country code (‘5F56’) is present
and equal to “CAN” and if the Application Selection Flag
indicates that the other application cannot be used at POS
terminals as a PRIMARY application or SECONDARY
application then only the application with bit 8 set is placed in
the PRIMARY list.

Specification Interac Debit Terminal Specification (Final Selection)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 37

 The coding of the optional Application Selection Flag data
element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use
as PRIMARY
application at
ABM
Bit 7= 1: Use
as
SECONDARY
application at
ABM
Bit 6-1:RFU
2 Non-ABM b Bit 8 = 1: Use
(i.e. POS) as PRIMARY
usage application at
non-ABM
terminals
Bit 7= 1: Use
as
SECONDARY
application at
non-ABM
terminals
Bit 6-1:RFU
3- RFU -
32

After building the list of mutually supported applications the

terminal shall examine each application for the presence of the
optional Issuer Country Code and Application Selection Flag data
elements. The terminal shall produce two sub-lists of mutually
supported applications: a PRIMARY and a SECONDARY sub-list.

Step #1: The terminal shall follow these steps for each application
in the list of mutually supported applications to build the PRIMARY
and SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application to

the PRIMARY sub-list if any one or more of these conditions
are true:
i. The Issuer Country Code (alpha3 format) data element is
not present.
ii. The ASF data element is not present.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 38

 iii. The Issuer Country Code (alpha3 format) is present for the
application in question, and the value of the Issuer Country
Code is not equal to “CAN”.
iv. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”) and as a
SECONDARY application (Byte 2, Bit 7 = “1”) at non-
ABM/ATM terminals. Note that the application should only
be added to the PRIMARY sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place the

application in the PRIMARY sub-list, then the terminal shall add
the application to the SECONDARY sub-list if the following
condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 2, Bit 7 = “1” and
Byte 2, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has
not already been placed on the PRIMARY sub-list
due to any of the conditions from #1 above.

If none of the conditions place the application in the PRIMARY

or SECONDARY sub-list, the POS terminal shall ignore the
application and not add it to either the PRIMARY or the
SECONDARY sub-list of mutually supported applications.

If the PRIMARY sub-list of mutually supported application(s) is

not empty, the terminal shall present to the Cardholder this list
of application(s). This presentation of applications shall be as
specified in EMV Book 1 part III, Section 12.4. The terminal
shall provide for confirmation of application by the Cardholder
when specified by the ICC.

Terminal All
Configuration

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 39

 Card Profile to Card 11b.
Use Card contains 2 mutually supported applications – App1
(Interac AID) and App2.

App1 (INTERAC application) has the Application Selection

Flag present and has Byte 2 bit 8 set to “1” and the Application
Priority Indicator set to priority ‘02’.

App2 (Maestro) on the card has the Application Priority

Indicator set to ‘01’.

Procedure The card is inserted into the terminal

Pass Criteria The terminal should automatically select the INTERAC

application.

4.1.18 SELECT41 – MULTI-APPLICATION CARD –TERMINAL SUPPORTS BOTH, INTERAC APPLICATION

NOT PERMITTED FOR POS {POS}

Objective To check that if the card has more than one application
supported by the terminal, the terminal checks the Application
Selection Flag if the Issuer Country code (‘5F56’) is present
and equal to “CAN” and if the Application Selection Flag
indicates that Interac application cannot be used at POS
terminals as a PRIMARY application or SECONDARY
application then only the application with bit 8 set is placed in
the PRIMARY list.

Specification Interac Debit Terminal Specification (Final Selection)

The coding of the optional Application Selection Flag data

element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use
as PRIMARY
application at
ABM
Bit 7= 1: Use
as
SECONDARY
application at
ABM
Bit 6-1: RFU
2 Non-ABM b Bit 8 = 1: Use
(i.e. POS) as PRIMARY
usage application at

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 40

 non-ABM
terminals
Bit 7= 1: Use
as
SECONDARY
application at
non-ABM
terminals
Bit 6-1: RFU
3- RFU -
32

After building the list of mutually supported applications the

terminal shall examine each application for the presence of the
optional Issuer Country Code and Application Selection Flag data
elements. The terminal shall produce two sub-lists of mutually
supported applications: a PRIMARY and a SECONDARY sub-list.

Step #1: The terminal shall follow these steps for each application
in the list of mutually supported applications to build the PRIMARY
and SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application to

the PRIMARY sub-list if any one or more of these conditions
are true:
i. The Issuer Country Code (alpha3 format) data element is
not present.
ii. The ASF data element is not present.
iii. The Issuer Country Code (alpha3 format) is present for the
application in question, and the value of the Issuer Country
Code is not equal to “CAN”.
iv. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”) and as a
SECONDARY application (Byte 2, Bit 7 = “1”) at non-
ABM/ATM terminals. Note that the application should only
be added to the PRIMARY sub-list in this case.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 41

 2. SECONDARY Sub-list: If none of the conditions place the
application in the PRIMARY sub-list, then the terminal shall add
the application to the SECONDARY sub-list if the following
condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 2, Bit 7 = “1” and
Byte 2, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has
not already been placed on the PRIMARY sub-list
due to any of the conditions from #1 above.

If none of the conditions place the application in the PRIMARY or

SECONDARY sub-list, the POS terminal shall ignore the
application and not add it to either the PRIMARY or the
SECONDARY sub-list of mutually supported applications.

If the PRIMARY sub-list of mutually supported application(s) is not

empty, the terminal shall present to the Cardholder this list of
application(s). This presentation of applications shall be as
specified in EMV Book 1 part III, Section 12.4. The terminal shall
provide for confirmation of application by the Cardholder when
specified by the ICC.

Terminal POS terminal [ICS 1 = YES]

Configuration

Card Profile to Card 12.

Use Card contains 2 mutually supported applications – App1
(Interac AID) and App2 (e.g Visa Credit or Mastercard Credit).

App1(INTERAC application) has the Application Selection Flag

present and has Byte 2 bit 8 set to ‘0’, and the Application
Priority Indicator set to ‘02’.

App2 on the card has the Application Priority Indicator set to

“01”.

Procedure The card is inserted into the terminal

Pass Criteria The terminal should automatically select App2 (non-INTERAC)

application.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 42

4.1.19 SELECT42 – MULTI-APPLICATION CARD –TERMINAL SUPPORTS BOTH APPLICATIONS {ABM}

Objective To ensure that if there are 2 applications in the card and the
2nd application is placed in the SECONDARY list only the 1st
application is available for selection from the PRIMARY list.

Specification Interac Cash Terminal Specification (Final Selection)

The coding of the optional Application Selection Flag data

element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use as
PRIMARY
application at ABM
Bit 7= 1: Use as
SECONDARY
application at ABM
Bit 6-1:RFU
2 Non-ABM (i.e. b Bit 8 = 1: Use as
POS) usage PRIMARY
application at non-
ABM terminals
Bit 7= 1: Use as
SECONDARY
application at non-
ABM terminals
Bit 6-1: RFU
3 - 32 RFU -

After building the list of mutually supported applications the

terminal shall examine each application for the presence of the
optional Issuer Country Code and Application Selection Flag data
elements. The terminal shall produce two sub-lists of mutually
supported applications: a PRIMARY and a SECONDARY sub-list.

Step #1: The terminal shall follow these steps for each application
in the list of mutually supported applications to build the PRIMARY
and SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application to

the PRIMARY sub-list if any one or more of these conditions
are true:
i. The Issuer Country Code (alpha3 format) data element is
not present.
ii. The ASF data element is not present.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 43

 iii. The Issuer Country Code (alpha3 format) is present for the
application in question, and the value of the Issuer Country
Code is not equal to “CAN”.
iv. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at ABM/ATM terminals as a
PRIMARY application (Byte 1, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at ABM/ATM terminals as a
PRIMARY application (Byte 1, Bit 8 = “1”) and as a
SECONDARY application (Byte 1, Bit 7 = “1”) at ABM/ATM
terminals. Note that the application should only be added
to the PRIMARY sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place the

application in the PRIMARY sub-list, then the terminal shall add
the application to the SECONDARY sub-list if the following
condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 1, Bit 7 = “1” and
Byte 1, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has
not already been placed on the PRIMARY sub-list
due to any of the conditions from #1 above.

If none of the conditions place the application in the PRIMARY

or SECONDARY sub-list, the ABM terminal shall ignore the
application and not add it to either the PRIMARY or the
SECONDARY sub-list of mutually supported applications.

If the PRIMARY sub-list of mutually supported application(s) is

not empty, the terminal shall present to the Cardholder this list
of application(s). This presentation of applications shall be as
specified in EMV Book 1 part III, Section 12.4. The terminal
shall provide for confirmation of application by the Cardholder
when specified by the ICC.

Terminal ABM terminal [ICS 2 = YES]

Configuration

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 44

 Card Profiles Card 6, ASF and 5F56 as per the subcases
to Use Card 10
Card 12

Procedure Case 1: Card 6 containing 2 apps - App1 with No ASF, APP2

with ASF = “4000”

Case 2: Card 6 containing 2 apps - App1 with No tag ‘5F56’,

APP2 with ASF = “4000”

Case 3: Card 6 containing 2 apps - App1 with tag ‘5F56’ not

equal “CAN, APP2 with ASF = “4000”

Case 4: Card 6 containing 2 apps - App1 with ASF = “8000”,

APP2 with ASF = “4000”

Case 5: Card 10

Case 6: Card 12

The card is inserted into the terminal

Pass Criteria The terminal should automatically select the INTERAC

application.

4.1.20 SELECT43 - INTERAC APPLICATION IS THE ONLY MUTUALLY SUPPORTED APPLICATION

Objective To ensure that the terminal can select the Interac application if
it is the only mutually supported application, terminal checks the
Issuer Country code (‘5F56’) is equal to “CAN” (If present) and
the Application Selection Flag indicates that the application
can be used at the terminal as a PRIMARY application or
SECONDARY application (if present).

Specification Interac Debit Terminal Specification (Final Selection)

The coding of the optional Application Selection Flag data

element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use as
PRIMARY
application at ABM

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 45

 Bit 7= 1: Use as
SECONDARY
application at ABM
Bit 6-1: RFU
2 Non-ABM b Bit 8 = 1: Use as
(i.e. POS) PRIMARY
usage application at non-
ABM terminals
Bit 7= 1: Use as
SECONDARY
application at non-
ABM terminals
Bit 6-1: RFU
3 - 32 RFU -

Step #1: The terminal shall follow these steps for each application in
the list of mutually supported applications to build the PRIMARY and
SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application to the

PRIMARY sub-list if any one or more of these conditions are true:
i. The Issuer Country Code (alpha3 format) data element is
not present.
ii. The ASF data element is not present.
iii. The Issuer Country Code (alpha3 format) is present for the
application in question, and the value of the Issuer Country
Code is not equal to “CAN”.
iv. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”) and as a
SECONDARY application (Byte 2, Bit 7 = “1”) at non-
ABM/ATM terminals. Note that the application should only
be added to the PRIMARY sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place the

application in the PRIMARY sub-list, then the terminal shall add
the application to the SECONDARY sub-list if the following
condition is true:

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 46

 • The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 2, Bit 7 = “1” and
Byte 2, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has not
already been placed on the PRIMARY sub-list due to
any of the conditions from #1 above.

If none of the conditions place the application in the PRIMARY

or SECONDARY sub-list, the POS terminal shall ignore the
application and not add it to either the PRIMARY or the
SECONDARY sub-list of mutually supported applications.

Terminal All
Configuration

Card Profile There is only 1 mutually supported application – Interac

to Use Application.

Default Card 1, ASF and 5F56 as per the subcases.

Procedure Case 1: Card 1

Case 2: Card 1 with tag ‘5F56’ removed.

Case 3: Card 1 with tag ‘DF62’ removed.

Case 4: Card 1 with the ASF (DF62) set as ‘8040’.

Case 5: Card 1 with the ASF (DF62) set as ‘4080’.

The card is inserted into the terminal, the Interac application

shall be selected, and the transaction goes to completion

Pass Criteria The Interac application should be selected.

4.1.21 SELECT44 - INTERAC APPLICATION, APPLICATION PERMITTED FOR ABM ONLY {ABM}
Objective To ensure that the terminal can select the Interac application if
it is the only mutually supported application, terminal checks
the Issuer Country code (‘5F56’) is equal to “CAN” and the
Application Selection Flag indicates that the application can be
used at ABM terminal as a PRIMARY application or
SECONDARY application

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 47

Specification Interac Cash Terminal Specification (Final Selection)

The coding of the optional Application Selection Flag data

element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use as
PRIMARY
application at ABM
Bit 7= 1: Use as
SECONDARY
application at ABM
Bit 6-1: RFU
2 Non-ABM b Bit 8 = 1: Use as
(i.e. POS) PRIMARY
usage application at non-
ABM terminals
Bit 7= 1: Use as
SECONDARY
application at non-
ABM terminals
Bit 6-1: RFU
3 - 32 RFU -

Step #1: The terminal shall follow these steps for each application in
the list of mutually supported applications to build the PRIMARY and
SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application to the

PRIMARY sub-list if any one or more of these conditions are true:

i. The Issuer Country Code (alpha3 format) data element is

not present.
ii. The ASF data element is not present.
iii. The Issuer Country Code (alpha3 format) is present for the
application in question, and the value of the Issuer Country
Code is not equal to “CAN”
iv. The Issuer Country Code (alpha 3 format) is present and is
equal to “CAN” and the ASF indicates that the application
can be used at ABM/ATM terminals as a PRIMARY
application (Byte 1, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and is
equal to “CAN” and the ASF indicates that the application
can be used at ABM/ATM terminals as a PRIMARY

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 48

 application (Byte 1, Bit 8 = “1”) and as a SECONDARY
application (Byte 1, Bit 7 = “1”) at ABM/ATM terminals. Note
that the application should only be added to the PRIMARY
sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place the

application in the PRIMARY sub-list, then the terminal shall add
the application to the SECONDARY sub-list if the following
condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at ABM/ATM terminals as a SECONDARY
application only (Byte 1, Bit 7 = “1” and Byte 1, Bit 8 =
“0”). Note that the application should only be added to
the SECONDARY sub-list if it has not already been
placed on the PRIMARY sub-list due to any of the
conditions from #1 above.

If none of the conditions place the application in the PRIMARY or

SECONDARY sub-list, the ABM terminal shall ignore the application
and not add it to either the PRIMARY or the SECONDARY sub-list of
mutually supported applications.

Step #2: Once the list of mutually supported applications has been
processed, the PRIMARY and SECONDARY sub-lists processing
shall be conducted as follows:

If the PRIMARY sub-list of mutually supported application(s) is

not empty, the ABM terminal shall present to the Cardholder this
list of application(s). This presentation of applications shall be as
specified in EMV Book 1 part III, Section 12.4. The terminal shall
provide for confirmation of application by the Cardholder when
specified by the ICC.

If the PRIMARY sub-list of mutually supported application(s) is

empty but the SECONDARY sub-list of mutually supported
application(s) is not empty, the ABM terminal shall present to the
Cardholder the SECONDARY sub-list of mutually supported
application(s). This presentation of applications shall be as
specified in EMV Book 1 Part III, Section 12.4. The terminal
shall provide for confirmation of application by the Cardholder
when specified by the ICC.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 49

 Terminal ABM terminal [ICS 2 = YES]
Configuration

Card Profile There is only 1 mutually supported application – Interac

to Use Application.

Default Card 1, ASF as per the subcases.

Procedure Case 1: Card 1 with the ASF (DF62) set as ‘4000’.

Case 2: Card 1 with the ASF (DF62) set as ‘8000’.

The card is inserted into the terminal, the Interac application

shall be selected, and the transaction goes to completion

Pass Criteria The Interac application should be selected

4.1.22 SELECT45 - INTERAC APPLICATION, APPLICATION PERMITTED FOR POS ONLY {POS}
Objective To ensure that the terminal can select the Interac application if
it is the only mutually supported application, terminal checks
the Issuer Country code (‘5F56’) is equal to “CAN” and the
Application Selection Flag indicates that the application can be
used at POS terminal as a PRIMARY application or
SECONDARY application

Specification Interac Debit Terminal Specification (Final Selection) section 8.5

The coding of the optional Application Selection Flag data

element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM Usage b Bit 8 = 1: Use as
PRIMARY
application at ABM
Bit 7= 1: Use as
SECONDARY
application at ABM
Bit 6-1: RFU
2 Non-ABM b Bit 8 = 1: Use as
(i.e. POS) PRIMARY
usage application at non-
ABM terminals
Bit 7= 1: Use as
SECONDARY

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 50

 application at non-
ABM terminals
Bit 6-1: RFU
3 - 32 RFU -

Step #1: The terminal shall follow these steps for each application in
the list of mutually supported applications to build the PRIMARY and
SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application to the

PRIMARY sub-list if any one or more of these conditions are true:
i. The Issuer Country Code (alpha3 format) data element is
not present.
ii. The ASF data element is not present.
iii. The Issuer Country Code (alpha3 format) is present for the
application in question, and the value of the Issuer Country
Code is not equal to “CAN”.
iv. The Issuer Country Code (alpha 3 format) is present and is
equal to “CAN” and the ASF indicates that the application
can be used at non-ABM/ATM terminals as a PRIMARY
application (Byte 2, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and is
equal to “CAN” and the ASF indicates that the application
can be used at non-ABM/ATM terminals as a PRIMARY
application (Byte 2, Bit 8 = “1”) and as a SECONDARY
application (Byte 2, Bit 7 = “1”) at non-ABM/ATM terminals.
Note that the application should only be added to the
PRIMARY sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place the

application in the PRIMARY sub-list, then the terminal shall add
the application to the SECONDARY sub-list if the following
condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 2, Bit 7 = “1” and
Byte 2, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has not
already been placed on the PRIMARY sub-list due to
any of the conditions from #1 above.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 51

 If none of the conditions place the application in the PRIMARY
or SECONDARY sub-list, the POS terminal shall ignore the
application and not add it to either the PRIMARY or the
SECONDARY sub-list of mutually supported applications.

Step #2: Once the list of mutually supported applications has

been processed, the PRIMARY and SECONDARY sub-lists
processing shall be conducted as follows:

If the PRIMARY sub-list of mutually supported application(s) is

not empty, the POS terminal shall present to the Cardholder this
list of application(s). This presentation of applications shall be as
specified in EMV Book 1 part III, Section 12.4. The terminal shall
provide for confirmation of application by the Cardholder when
specified by the ICC.

If the PRIMARY sub-list of mutually supported application(s) is

empty but the SECONDARY sub-list of mutually supported
application(s) is not empty, the POS terminal shall present to the
Cardholder the SECONDARY sub-list of mutually supported
application(s). This presentation of applications shall be as
specified in EMV Book 1 Part III, Section 12.4. The terminal
shall provide for confirmation of application by the Cardholder
when specified by the ICC.

Terminal POS terminal [ICS 1 = YES]

Configuration

Card Profile There is only 1 mutually supported application – Interac

to Use Application.

Default Card 1, ASF as per the subcases.

Procedure Case 1: Card 1 with the ASF (DF62) set as ‘0080’

Case 2: Card 1 with the ASF (DF62) set as ‘0040’

The card is inserted into the terminal, the Interac application

shall be selected, and the transaction goes to completion

Pass Criteria The Interac application should be selected

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 52

4.1.23 SELECT46 – MULTI-APPLICATION CARD –TERMINAL SUPPORTS BOTH APPLICATIONS {POS}

Objective To ensure that if there are 2 applications in the card and the
2nd application is placed in the SECONDARY list only the 1st
application is available for selection from the PRIMARY list.

Specification Interac Debit Terminal Specification (Final Selection) section

8.5

The coding of the optional Application Selection Flag data

element (Tag ‘DF62’) is as follows:

Byte Description Format Value

1 ABM b Bit 8 = 1: Use as
Usage PRIMARY
application at ABM
Bit 7= 1: Use as
SECONDARY
application at ABM
Bit 6-1: RFU
2 Non-ABM b Bit 8 = 1: Use as
(i.e. POS) PRIMARY
usage application at non-
ABM terminals
Bit 7= 1: Use as
SECONDARY
application at non-
ABM terminals
Bit 6-1: RFU
3- RFU -
32

After building the list of mutually supported applications the

terminal shall examine each application for the presence of the
optional Issuer Country Code and Application Selection Flag data
elements. The terminal shall produce two sub-lists of mutually
supported applications: a PRIMARY and a SECONDARY sub-list.
Step #1: The terminal shall follow these steps for each application
in the list of mutually supported applications to build the PRIMARY
and SECONDARY sub-list of applications.

1. PRIMARY Sub-list: The terminal shall add the application to

the PRIMARY sub-list if any one or more of these conditions
are true:
i. The Issuer Country Code (alpha3 format) data element
is not present.
ii. The ASF data element is not present.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 53

 iii. The Issuer Country Code (alpha3 format) is present for
the application in question, and the value of the Issuer
Country Code is not equal to “CAN”.
iv. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”).
v. The Issuer Country Code (alpha 3 format) is present and
is equal to “CAN” and the ASF indicates that the
application can be used at non-ABM/ATM terminals as a
PRIMARY application (Byte 2, Bit 8 = “1”) and as a
SECONDARY application (Byte 2, Bit 7 = “1”) at non-
ABM/ATM terminals. Note that the application should
only be added to the PRIMARY sub-list in this case.

2. SECONDARY Sub-list: If none of the conditions place the

application in the PRIMARY sub-list, then the terminal shall add
the application to the SECONDARY sub-list if the following
condition is true:
• The Issuer Country Code (alpha 3 format) is equal to
“CAN” and the ASF indicates that the application can
be used at non-ABM/ATM terminals as a
SECONDARY application only (Byte 2, Bit 7 = “1” and
Byte 2, Bit 8 = “0”). Note that the application should
only be added to the SECONDARY sub-list if it has
not already been placed on the PRIMARY sub-list
due to any of the conditions from #1 above.

If none of the conditions place the application in the

PRIMARY or SECONDARY sub-list, the POS terminal shall
ignore the application and not add it to either the PRIMARY
or the SECONDARY sub-list of mutually supported
applications.

Step #2: Once the list of mutually supported applications has

been processed, the PRIMARY and SECONDARY sub-lists
processing shall be conducted as follows:

• If the PRIMARY sub-list of mutually supported

application(s) is not empty, the terminal shall present to
the Cardholder this list of application(s). This
presentation of applications shall be as specified in EMV
Book 1 Part III, Section 12.4. The terminal shall provide

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 54

 for confirmation of application by the Cardholder when
specified by the ICC.

Terminal POS terminal [ICS 1 = YES]

Configuration

Card Profiles Card 6, ASF and 5F56 as per the subcases

to Use Card 10
Card 11a and 11b

Procedure Case 1: Card 6 containing 2 apps - App1 with No ASF, APP2

with ASF = “0040”

Case 2: Card 6 containing 2 apps - App1 with No tag ‘5F56’,

APP2 with ASF = “0040”

Case 3: Card 6 containing 2 apps - App1 with tag ‘5F56’ not

equal “CAN, APP2 with ASF = “0040”

Case 4: Card 6 containing 2 apps - App1 with ASF = “0080”,

APP2 with ASF = “0040”

Case 5: Card 10
Case 6: Card 11a

Case 7: Card 11b

The card is inserted into the terminal

Pass Criteria The terminal should automatically select the INTERAC

application.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 55

 4.2 Card Reading Tests

These tests identified are to ensure that when a card is inserted into the terminal it is
processed by the correct means i.e. if it is an ICC card the chip data is used in the
transaction and not the magnetic stripe data.

4.2.1 CARD01 – ICC READ NOT MAGNETIC STRIPE (SERVICE CODE BEGINS WITH A ‘2’)

Objective To ensure that the terminal uses the chip as opposed to the
magnetic stripe when the IFD of a terminal combines both the
IC reader and the magnetic stripe reader and the magnetic
stripe on the card has a service code beginning with a “2”

Specification Interac Debit Terminal Specification (Card Reading)

Interac Cash Terminal Specification (Card Reading)

When the IFD of a terminal combines both the IC reader and a

magnetic stripe reader, and the magnetic stripe reader reads a
service code beginning with a “2” or a “6” indicating that an IC
is present, the terminal shall process the transaction using the
IC.

Terminal Terminals with combined magnetic stripe and IC reader [ICS

Configuration 1.5 = YES]

Card Profile to Use Default card 1

Procedure The card is inserted into the terminal and transaction

performed

Pass Criteria The terminal should use the chip interface and send all the
commands for an EMV transaction including:
• Select command.
• GPO command
• Read Records
• Generate AC

4.2.2 CARD02 – ICC READ NOT MAGNETIC STRIPE (SERVICE CODE BEGINS WITH A ‘6’)

Objective To ensure that the terminal uses the chip as opposed to the
magnetic stripe when the IFD of a terminal combines both the
IC reader and the magnetic stripe reader and the magnetic
stripe on the card has a service code beginning with a “6”

Specification Interac Debit Terminal Specification (Card Reading)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 56

 Interac Cash Terminal Specification (Card Reading)

When the IFD of a terminal combines both the IC reader and a

magnetic stripe reader, and the magnetic stripe reader reads a
service code beginning with a “2” or a “6” indicating that an IC
is present, the terminal shall process the transaction using the
IC.

Terminal Terminals with combined magnetic stripe and IC reader [ICS

Configuration 1.5 = YES]

Card Profile to Use Default card 1

Procedure The card is inserted into the terminal and transaction

performed

Pass Criteria The terminal should use the chip interface and send all the
commands for an EMV transaction including:
• Select command.
• GPO command
• Read Records
• Generate AC

4.3 Function Tests

These tests are to ensure that the terminal supports the functions identified in the Terminal
Specifications.

4.3.1 FUNCTION01 –GET PROCESSING COMMAND

Objective To ensure that the terminal supports all functions necessary for an
EMV Transaction. In order to initiate application processing and to
read the data from the card the terminal must send the Get
Processing command and issue the appropriate Read Records

Specification Interac Debit Terminal Specification (Read Application Data)

Interac Cash Terminal Specification (Read Application Data)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the conditions
described in this section.
Read Application Data shall be performed as specified in EMV
Book 3 Part III Section 10.2

Terminal All
Configuration

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 57

Card Profile to Use Default card 1

Procedure The card is inserted into the terminal and transaction performed

Pass Criteria The terminal should send the Get Processing command after the
final selection of the Interac application and issue the Read
Records as specified in the AFL returned by the card

4.3.2 FUNCTION02 –CARD WITH A PDOL

Objective Although Interac do not mandate the use of a PDOL, if the

card contains a PDOL which has an amount data element then
the terminal must supply the amount in the Get Processing
Options command

Specification Interac Debit Terminal Specification (Initiate Application

Processing)
Interac Cash Terminal Specification (Initiate Application
Processing)

The Processing Options Data Object List (PDOL) data element

is not used by the Interac ICC application. The PDOL allows
the ICC to inform the POS {ABM} terminal of terminal resident
data elements that must be included in the Get Processing
Option command. I f used by the Issuer, and if the PDOL
includes an amount the terminal shall provide the amount to
the ICC as specified in EMV Book 4 Part II Section 6.3.1

Terminal All
Configuration

Card Profile to Card containing a PDOL with the data element ‘9F02’ –
Use Amount Authorised

Procedure The card is inserted into the terminal and transaction

performed

Pass Criteria The terminal should send the Get Processing command
containing the amount of the transaction – amount should not
be zero if the terminal type is ‘2x’

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 58

 4.3.3 FUNCTION04 – OFFLINE DATA AUTHENTICATION NOT SUPPORTED

Objective If the terminal is an on-line only terminal and it does not support
Offline Data Authentication should set the “Data Authentication
was not performed” bit in the TVR to ‘1’

Specification Interac Debit Terminal Specification (Offline Data Authentication)

Interac Cash Terminal Specification (Offline Data Authentication)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the conditions
described in this section.

An online-only terminal not supporting offline data authentication

as specified in the Terminal Capabilities shall set to “1” the “Data
authentication was not performed” bit in the Terminal Verification
Results (TVR).

Terminal Online-only terminal not supporting Offline Data Authentication

Configuration [ICS 3 = NO]

Card Profile to Card 2 - Card Supporting SDA

Use

Procedure The card is inserted into the terminal and transaction performed

Pass Criteria The terminal should set byte “1” bit “8” - Data authentication was
not performed in the TVR to 1 in the first Generate AC command

4.3.4 FUNCTION07 – OFFLINE PLAINTEXT PIN

Objective A POS should support plaintext PIN verification.

Specification Interac Debit Terminal Specification (Offline PIN Verification

and Conditions for Support of Functions)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

Offline PIN verification (plaintext and enciphered) shall be

supported in POS terminals for both online authorizations and
offline authorizations.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 59

 The terminal shall comply with EMV Book 3, the Application
Specification. It shall support all functions subject to the
conditions described in this section.

The conditions for Support of Functions in terminals supporting

only online authorizations shall be as shown in the following
table:

Function Online-only Terminal

Verify command Mandatory

Terminal POS Terminal [ICS 1 = YES]

Configuration

Card Profile to Use Default Card 1 (CAPK Index “07”) with

CVM List ’00 00 00 00 00 00 00 00 01 03 02 03’

Procedure The card is inserted into the terminal and transaction

performed with PIN entry

Pass Criteria 1. The terminal should prompt for PIN entry.

2. The Verify command [for plaintext PIN] should be
sent to the card.
3. The PIN value sent to the card should be the PIN
value entered.
4. The terminal shall set the CVM Results to “010302”
indicating Offline Plaintext PIN was successful.

4.3.5 FUNCTION08 – OFFLINE ENCIPHERED PIN (CAPK = “07”)

Objective A POS should support enciphered offline PIN verification

Specification Interac Debit Terminal Specification (Offline PIN Verification

and Conditions for Support of Functions)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

Offline PIN verification (plaintext and enciphered) shall be

supported in POS terminals for both online authorizations and
offline authorizations.

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 60

 The conditions for Support of Functions in terminals supporting
only online authorizations shall be as shown in the following
table:

Function Online-only Terminal

Verify command Mandatory

Terminal POS terminal [ICS 1 = YES]

Configuration

Card Profile to Use Card 3 - Card supporting enciphered offline PIN. CAPK Index
“07”

Procedure The card is inserted into the terminal and transaction

performed with PIN entry

Pass Criteria 1. The terminal should prompt for PIN entry.

2. The Verify command [for enciphered PIN] should be sent to the
card.
3. The PIN value sent to the card should be the PIN value
entered.
4. The terminal shall set the CVM Results to “040002” indicating
Offline Enciphered PIN was successful.

4.3.6 FUNCTION09 – OFFLINE PLAINTEXT PIN {ABM}

Objective If an ABM supports offline PIN verification, then plaintext PIN

should be supported

Specification Interac Cash Terminal Specification (Offline PIN Verification

and Conditions for Support of Functions)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.
Offline PIN verification may be supported in ABMs at the
option of the Acquirer.
If offline PIN verification is provided then both offline plaintext
PIN verification and offline enciphered PIN verification shall be
supported.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 61

 The terminal shall comply with EMV Book 3, the Application
Specification. It shall support all functions subject to the
conditions described in this section.

The conditions for Support of Functions in terminals supporting

only online authorizations shall be as shown in the following
table:

Function Online-only Terminal

Verify command Optional

Terminal ABM terminal supporting offline PIN Verification [ICS 2 = YES

Configuration and 2.1 = YES]

Card Profile to Use Default Card 1 with

CVM List ’00 00 00 00 00 00 00 00 01 03 02 03’

Procedure The card is inserted into the terminal and transaction

performed with PIN entry

Pass Criteria 1. The terminal should prompt for PIN entry.

2. The Verify command [for plaintext PIN] should be
sent to the card.
3. The PIN value sent to the card should be the PIN
value entered.
4. The terminal shall set the CVM Results to “010302”
indicating Offline Plaintext PIN was successful.

4.3.7 FUNCTION10 –OFFLINE ENCIPHERED PIN {ABM}

Objective If an ABM supports offline PIN verification, then enciphered

offline PIN should be supported

Specification Interac Cash Terminal Specification (Offline PIN Verification

and Conditions for Support of Functions)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.
Offline PIN verification may be supported in ABMs at the
option of the Acquirer
If offline PIN verification is provided then both offline plaintext
PIN verification and offline enciphered PIN verification shall be
supported.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 62

 The terminal shall comply with EMV Book 3, the Application
Specification. It shall support all functions subject to the
conditions described in this section.

The conditions for Support of Functions in terminals supporting

only online authorizations shall be as shown in the following
table:

Function Online-only Terminal

Verify command Optional

Terminal ABM terminal supporting offline PIN Verification [ICS 2 = YES

Configuration and 2.1 = YES]

Card Profile to Use Card 3 - supporting enciphered offline PIN

Procedure The card is inserted into the terminal and transaction

performed with PIN entry

Pass Criteria 1. The terminal should prompt for PIN entry.

2. The Verify command [for enciphered PIN] should be
sent to the card.
3. The PIN value sent to the card should be the PIN
value entered.
4. The terminal shall set the CVM Results to “040002”
indicating Offline Enciphered PIN was successful.

4.3.8 FUNCTION11 –ONLINE PIN

Objective If a POS terminal supports online PIN verification, then the

terminal should request a PIN and set the TVR appropriately
when the card supports online PIN. The PIN should be sent in
the online message

Specification Interac Debit Terminal Specification (Online PIN Verification)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.
Online PIN verification for ICC transactions is optional in POS
terminals. Online PIN verification for ICC transactions shall be
performed when supported by the Terminal and specified by
the ICC.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 63

Terminal POS terminal supporting online PIN [ICS 1 = YES and 1.4 =
Configuration YES]

Card Profile to Use Card 7 - Card supporting online PIN

Procedure The card is inserted into the terminal and transaction

performed with PIN entry

Pass Criteria 1. The terminal should prompt for PIN entry.

2. A Verify command should not be sent to the card.
3. The terminal should set byte 3 bit 3 to ‘1’ of TVR–
online PIN entered.
4. Message sent to the host should a PIN value

4.3.9 FUNCTION12 – ONLINE PIN {ABM}

Objective An ABM terminal must support online PIN verification. The

terminal should request a PIN and set the TVR appropriately
when the card supports online PIN. The PIN should be sent in
the online message

Specification Interac Cash Terminal Specification (Online PIN Verification)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.
Online PIN verification shall be performed when specified by
the ICC.

Terminal ABM terminal [ICS 2 = YES]

Configuration

Card Profile to Use Card 7 - Card supporting online PIN

Procedure The card is inserted into the terminal and transaction

performed with PIN entry

Pass Criteria 1. The terminal should prompt for PIN entry.

2. A Verify command should not be sent to the card.
3. The terminal should set byte 3 bit 3 to ‘1’ of TVR –
online PIN entered.
4. Message sent to the host should a PIN value

4.3.10 FUNCTION17 – GET CHALLENGE

Objective The Get Challenge command is mandatory

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 64

Specification Interac Debit Terminal Specification (Conditions for Support of
Functions)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

The conditions for Support of Functions in terminals supporting

only online authorizations shall be as shown in the following
table:

Function Online-only Terminal

Get Challenge command Mandatory

Terminal POS terminal [ICS 1 = YES]

Configuration

Card Profile to Use Card 3 - Card with offline enciphered PIN in the CVM

Procedure The card is inserted in the terminal and a transaction should

be performed with PIN entry

Pass Criteria The card should receive a Get Challenge command prior to
the verify for offline enciphered PIN

4.3.11 FUNCTION22 – FLOOR LIMIT {ABM}

Objective To ensure that the ABM floor limit is set to zero to ensure that
all transactions go online

Specification Interac Cash Terminal Specification (Terminal Risk

Management)

The Terminal Floor Limit where used, shall be set to zero.

Terminal ABM Terminal [ICS 2 = YES]

Configuration

Card Profile to Use Default Card 1 with Terminal Risk Management supported set
in the AIP and PDOL contains floor limit

Procedure The card is inserted in the terminal and the transaction should
be performed with the minimum amount allowed by the ABM

Pass Criteria The terminal should request an ARQC and the first 4 bytes of
the PDOL should contain the Terminal Floor limit = ‘00000000’

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 65

 The TVR byte 4 bit 8 should be set to ‘1’ – Transaction
exceeds floor limit

4.3.12 FUNCTION23 – FLOOR LIMIT {POS}

Objective To ensure that the POS floor limit is set to zero to ensure
that all transactions go online

Specification Interac Debit Terminal Specification (Terminal Risk

Management) and (Terminal Action Analysis)

The online-only POS terminal shall support the EMV

terminal risk management function Floor Limits. The
Terminal Floor Limit data element shall be set to zero to
force all authorisations online.
For online-only POS terminals, the Acquirer shall set the
terminal data element Terminal Floor Limit (Tag ‘9F1B’) to
zero to have all transactions processed online (approved
and declined online) if not declined by the ICC.

Terminal Online-Only or Online capable POS terminals [ICS 1.1 =

Configuration YES or 1.3 = YES]

Card Profile to Card 1 - Default Card with Terminal Risk Management

Use supported set in the AIP and PDOL contains floor limit
(PDOL Tag 9F38 = ‘9F1B04’)

Procedure The card is inserted in the terminal and the transaction

should be performed with the minimum amount allowed by
the POS

Pass Criteria The terminal should request an ARQC and the first 4 bytes
of the PDOL should contain the Terminal Floor limit =
‘00000000’

4.3.13 FUNCTION24a – OFFLINE DATA AUTHENTICATION SUCCESSFUL (SDA SUPPORTED)

Objective To ensure that if both the terminal and the card support a common
method of offline data authentication (i.e. SDA), the terminal shall
perform SDA validation

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 66

 Specification Reader Terminal Specification for Interac Flash (Data
Authentication, Online Capable Terminal, Online Only Terminal
Implementation)

Offline Data Authentication is performed as defined in [EMV book

2] and [EMV book 3]. It consists of performing SDA, DDA or CDA
process. The result of Data Authentication is the setting of
appropriate bits in Terminal Verification Result (TVR).

For an online-capable Terminal (i.e. not online only):

• Offline Data Authentication support is mandatory:
o SDA or SDA+DDA or SDA+DDA+CDA in contact
mode. Interac recommends the support of CDA.

An online only terminal will never perform a transaction offline: it

declines transactions offline or request for online transactions. It
means that such a terminal can request an Authorization Request
Cryptogram (ARQC) in first GENERATE AC command, if the
transaction is not declined.
To simplify the implementation, for an online only terminal:
• Offline Data Authentication is optional in contact and contactless
mode.

Terminal SDA supported [ICS 3.1 = YES]

Configuration

Card Profile to Card 2- Card supporting SDA

Use

Procedure The card is inserted into the terminal and transaction performed,

Pass Criteria SDA Validation is successful, and the following conditions are met:

1. The terminal should set TVR byte “1” bit “8” to ‘0’ Data
authentication was not performed)
2. TVR byte “1” bit “7” should be ‘0‘(SDA failed)
3. The terminal should set TVR byte “1” bit “2 “to “1” SDA
selected)

4.3.14 FUNCTION24b – OFFLINE DATA AUTHENTICATION FAILED (SDA SUPPORTED)

Objective To ensure that If both the terminal and the card support a common
method of offline data authentication (i.e. SDA), the terminal shall
perform SDA Validation

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 67

Specification Reader Terminal Specification for Interac Flash (Data
Authentication, Online Capable Terminal, Online Only Terminal
Implementation)

Offline Data Authentication is performed as defined in [EMV book

2] and [EMV book 3]. It consists of performing SDA, DDA or CDA
process. The result of Data Authentication is the setting of
appropriate bits in Terminal Verification Result (TVR).

For an online-capable Terminal (i.e. not online only):

• Offline Data Authentication support is mandatory:
o SDA or SDA+DDA or SDA+DDA+CDA in contact
mode. Interac recommends the support of CDA.

An online only terminal will never perform a transaction offline: it

declines transactions offline or request for online transactions. It
means that such a terminal can request an Authorization Request
Cryptogram (ARQC) in first GENERATE AC command, if the
transaction is not declined.
To simplify the implementation, for an online only terminal:
• Offline Data Authentication is optional in contact and contactless
mode

Terminal SDA supported [ICS 3.1 = YES]

Configuration

Card Profile to Card 2- Supporting SDA with CA Public Key Index and Interac RID
Use missing

Procedure The card is inserted into the terminal and transaction performed

Pass Criteria SDA Validation failed and the following conditions are met:

1. The terminal should set TVR byte “1” bit “8” to ‘0’ (Data
authentication was not performed)
2. The terminal should set TVR, “SDA failed”, byte “1” bit “7” to
‘1‘failed)
3. The terminal should set TSI byte 1, bit 8 = '1' (Offline Data
Authentication was performed) in the first Generate AC
command

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 68

4.3.15 FUNCTION25 – ENCIPHERED OFFLINE PIN VERIFICATION FAILS – KEY ABSENT

Objective To ensure that if the terminal supports enciphered Offline PIN, and if
no CA Public Keys is available for Interac RID and CA Public Key
Index, the terminal fails enciphered offline pin verification.

Specification Interac Cash Terminal Specification (Security Requirements)

For enciphered offline PIN verification, the PED Secure Module

must support the Interac CA Public Key, verify the Issuer Public Key
Certificate, verify the ICC Public Key Certificate for PIN
Encipherment, and encipher the PIN using RSA as specified in EMV
v4.3, Nov 2011, Book 2 Part II, Section 7.

Terminal Offline Enciphered PIN supported [ICS 1 = YES OR 2.1 = YES]

Configuration

Card Profile to Card 3 but CA index (tag ‘8F’) is set to ‘AA’

Use

Procedure The card is inserted into the terminal and transaction performed

Pass Criteria 1. The terminal should set TVR byte 3, bit 8 = '1' (Cardholder
verification was not successful) in the first Generate AC
command.
2. The terminal should set TSI byte 1, bit 7 = '1' (Cardholder
verification was performed) in the first Generate AC command.
3. The terminal shall set the CVM Results to “040001” indicating
Offline Enciphered PIN was unsuccessful.
4. The terminal should decline the transaction.

4.3.16 FUNCTION26a – OFFLINE DATA AUTHENTICATION SUCCESSFUL (CDA SUPPORTED)

Objective To ensure that If both the terminal and the card support a common
method of offline data authentication (i.e. CDA), the terminal shall
perform CDA validation. Use CAPK Index “07”, 1984-bit key.

Specification Reader Terminal specification for IDP (Data Authentication, Online

Capable Terminal, Online Only Terminal Implementation)

Offline Data Authentication is performed as defined in [EMV book

2] and [EMV book 3]. It consists of performing SDA, DDA or CDA

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 69

 process. The result of Data Authentication is the setting of
appropriate bits in Terminal Verification Result (TVR).

For an online-capable Terminal (i.e. not online only):

• Offline Data Authentication support is mandatory:
o SDA or SDA+DDA or SDA+DDA+CDA in contact
mode. Interac recommends the support of CDA.

An online only terminal will never perform a transaction offline: it

declines transactions offline or request for online transactions. It
means that such a terminal can request an Authorization Request
Cryptogram (ARQC) in first GENERATE AC command, if the
transaction is not declined.
To simplify the implementation, for an online only terminal:
• Offline Data Authentication is optional in contact and contactless
mode
Terminal CDA supported [ICS 3.3 = YES]
Configuration

Card Profile to Card 8- Card supporting CDA, CAPK index “07”, 1984-bit key
Use

Procedure The card is inserted into the terminal and transaction performed,

Pass Criteria CDA Validation is successful, and the following conditions are met:

1. The terminal should set TVR byte “1” bit “8” to ‘0’ Data
authentication was not performed)
2. TVR byte “1” bit “3” should be ‘0‘(CDA passed)

4.3.17 FUNCTION26b – OFFLINE DATA AUTHENTICATION FAILED (CDA SUPPORTED)

Objective To ensure that If both the terminal and the card support a common
method of offline data authentication (i.e. CDA), the terminal shall
perform CDA validation.

Specification Reader Terminal specification for Interac Flash [Offline Data

Authentication (CDA Signature Verification) – Contact Impact]

For contact transactions, Offline Data Authentication is performed

according to [EMV Book 2] & [EMV Book 3].

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 70

 For contact transactions, Interac Corp. recommends the support of
CDA.

Terminal Terminal Supporting CDA [ICS 3.3 = YES]

Configuration

Card Profile to Card 8 - Card supporting CDA with tag 8F set to ‘AA’
Use

Procedure The card is inserted into the terminal and transaction performed.
Terminal requests ARQC with CDA at 1st GENERATE AC

Pass Criteria CDA Validation fails, and the following conditions are met:

1. The terminal should set TVR byte “1” bit “8” to ‘0’ (Data
authentication was not performed)
2. The terminal should set TVR, byte 1, bit 3 = '1'(CDA failed) in
the first Generate AC command.
3. The terminal should set TSI byte 1, bit 8 = '1' (Offline Data
Authentication was performed) in the first Generate AC
command.

4.3.18 FUNCTION26C – OFFLINE DATA AUTHENTICATION SUCCESSFUL (CDA SUPPORTED)

Objective To ensure that If both the terminal and the card support a common
method of offline data authentication (i.e. CDA), the terminal shall
perform CDA validation. Use CAPK index “03” 1408-bit key.

Specification Reader Terminal specification for IDP (Data Authentication, Online

Capable Terminal, Online Only Terminal Implementation)

Offline Data Authentication is performed as defined in [EMV book

2] and [EMV book 3]. It consists of performing SDA, DDA or CDA
process. The result of Data Authentication is the setting of
appropriate bits in Terminal Verification Result (TVR).

For an online-capable Terminal (i.e. not online only):

• Offline Data Authentication support is mandatory:
o SDA or SDA+DDA or SDA+DDA+CDA in contact
mode. Interac recommends the support of CDA.

An online only terminal will never perform a transaction offline: it

declines transactions offline or request for online transactions. It

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 71

 means that such a terminal can request an Authorization Request
Cryptogram (ARQC) in first GENERATE AC command if the
transaction is not declined.
To simplify the implementation, for an online only terminal:
• Offline Data Authentication is optional in contact and
contactless mode
Terminal CDA supported [ICS 3.3 = YES]
Configuration

Card Profile to Card 8a- Card supporting CDA – CAPK index “03”, 1408-bit key
Use

Procedure The card is inserted into the terminal and transaction performed,

Pass Criteria CDA Validation is successful, and the following conditions are met:

3. The terminal should set TVR byte “1” bit “8” to ‘0’ Data
authentication was not performed)
4. TVR byte “1” bit “3” should be ‘0‘(CDA passed)

4.3.19 FUNCTION27a - Offline Data Authentication Successful (DDA Supported)

Objective To ensure that If both the terminal and the card support a
common method of offline data authentication (i.e. DDA), the
terminal shall perform DDA validation.

Specification IDP Terminal Specification (Terminal Capabilities)

The Terminal Capabilities for offline fund authorization are the

same as for online authorisations. In addition, the terminal
supporting offline authorisations must support both Static Data
Authentication (SDA) and Dynamic Data Authentication.

Terminal Terminal supporting offline authentication [ICS 3.2 = YES]

Configuration

Card Profile to Use Card 4 - Card supporting DDA

Procedure The card is inserted into the terminal and transaction

performed

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 72

Pass Criteria 1. The terminal should set TVR byte “1” bit “8” to ‘0’
(Data authentication was not performed) in the first
Generate AC command
2. The terminal should set TVR byte ‘1’ bit ‘4’ to ‘0’
(DDA passed)
3. The terminal should set TSI byte ‘1’ bit ‘8’ to ‘1’
(Offline Data Authentication was performed
4. The terminal should send an Internal Authenticate
command

4.3.20 FUNCTION27b - Offline Data Authentication Failure (DDA Supported)

Objective To ensure that If both the terminal and the card support a
common method of offline data authentication (i.e. DDA), the
terminal shall perform DDA validation.

Specification IDP Terminal Specification (Terminal Capabilities)

The Terminal Capabilities for offline fund authorization are the

same as for online authorisations. In addition, the terminal
supporting offline authorisations must support both Static Data
Authentication (SDA) and Dynamic Data Authentication.

Terminal Terminal supporting offline authentication [ICS 3.2 = YES]

Configuration

Card Profile to Use Card 4- Card supporting DDA with tag 8F set to ‘AA’

Procedure The card is inserted into the terminal and transaction

performed

Pass Criteria 1.The terminal should set TVR byte “1” bit “8” to ‘0’ (Data
authentication was performed) in the first Generate AC
command.
2. The terminal should set TVR byte ‘1’ bit ‘4’ to ‘1’ (DDA did
not pass)
3. The terminal should set TSI byte ‘1’ bit ‘8’ to ‘1’ (Offline Data
Authentication was performed

4.3.21 FUNCTION28 – OFFLINE ENCIPHERED PIN FAIL CVM

Objective To ensure that if both the terminal and the card support a
common method CVM from the CVM List, and if the CVM List

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 73

 indicates to fail cardholder verification if this CVM is
unsuccessful, the terminal fails enciphered PIN verification.

To ensure that the terminal set TVR and CVM Results

correctly.

Specification Interac Debit Terminal Specification (Offline PIN Verification

and Conditions for Support of Functions)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

Offline PIN verification (plaintext and enciphered) shall be

supported in POS terminals for both online authorizations and
offline authorizations.

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

Terminal POS Terminal [ICS 1 = YES]

Configuration

Card Profile to Use Card 1 (CVM List is 00000000 00000000 0403 0103 0203)
as default with
- PIN Try Counter “2”.
- 1st Generate AC returns an ARQC
- CDOL1 contains the CVM Results (‘9F34’)

Procedure The card is inserted into the terminal and transaction

performed with PIN entry.

Pass Criteria 1. The terminal prompts for PIN entry and an incorrect PIN is
entered
2. The Verify command [for enciphered PIN] should be sent to the
card.
3. Offline Enciphered PIN fails
4. PIN Try Counter is decremented to “1”.
5. The terminal prompts for PIN entry and an incorrect PIN is
entered
6. The Verify command [for enciphered PIN] should be sent to the
card.
7. Offline Enciphered PIN fails again.
8. PIN Try Counter is now “0”.
9. Terminal

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 74

 a. Shall not prompt for PIN entry again.
b. Shall set the “PIN Try Limit exceeded’ bit in the TVR to
1.
c. Shall set the CVM Results to “040301” indicating Offline
Enciphered PIN has failed.

4.3.22 FUNCTION29 – OFFLINE ENCIPHERED PIN - SUCCEEDING CVM

Objective To ensure that if both the terminal and the card support a
common method CVM from the CVM List, and if the CVM List
indicates to apply succeeding CVM, the terminal fails
enciphered PIN verification when the PIN Try Limit has been
exceeded.

To ensure that the terminal set TVR and CVM Results

correctly.

Specification Interac Debit Terminal Specification (Offline PIN Verification

and Conditions for Support of Functions)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

Offline PIN verification (plaintext and enciphered) shall be

supported in POS terminals for both online authorizations and
offline authorizations.

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

Terminal POS Terminal [ICS 1 = YES]

Configuration

Card Profile to Use Card 1 as default with

- CVM List is 00000000 00000000 4403 0103 0203
- PIN Try Counter “2”.
- 1st Generate AC returns an ARQC
- CDOL1 contains the CVM Results (‘9F34’)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 75

Procedure The card is inserted into the terminal and transaction
performed with PIN entry.

Pass Criteria 1. The terminal prompts for PIN entry and an incorrect PIN is
entered
2. The Verify command [for enciphered PIN] should be sent to the
card.
3. Offline Enciphered PIN fails
4. PIN Try Counter is decremented to “1”.
5. The terminal prompts for PIN entry and an incorrect PIN is
entered
6. The Verify command [for enciphered PIN] should be sent to the
card.
7. Offline Enciphered PIN fails again.
8. PIN Try Counter is now “0”.
9. Terminal
a. Shall attempt the next CVM on the CVM List (Offline
plaintext PIN)
b. Shall not prompt for PIN entry again because PIN Try
Counter is ‘0’.
c. Shall set the “PIN Try Limit exceeded’ bit in the TVR to
1.
d. Shall set the CVM Results to “010301” indicating Offline
Enciphered PIN has failed.

4.3.23 FUNCTION30 – OFFLINE ENCIPHERED PIN - SUCCEEDING CVM

Objective To ensure that If both the terminal and the card support a common
method CVM from the CVM list, and the CVM Lists indicates to
apply succeeding CVM, the next CVM is applied.

To ensure that the terminal set CVM Results correctly.

Specification Interac Debit Terminal Specification (Offline PIN Verification and

Conditions for Support of Functions)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the conditions
described in this section.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 76

 Offline PIN verification (plaintext and enciphered) shall be
supported in POS terminals for both online authorizations and
offline authorizations.

The terminal shall comply with EMV Book 3, the Application

Specification.

EMV Book 2, Security and Key Management, Section 7.1 Keys

and Certificates.

The first step of PIN encipherment shall be the retrieval of the

public key to be used by the terminal for the encipherment of the
PIN. This process takes place as follows.
1. If the terminal has obtained all the data objects specified in
Table 24 from the ICC, then the terminal retrieves the ICC PIN
Encipherment Public Key in exactly the same way as it retrieves
the ICC Public Key for offline dynamic data authentication (see
section 6).
2. If the terminal has not obtained all the data objects specified in
Table 24 but has obtained all the data objects specified in Table
12, then the terminal retrieves the ICC Public Key as described in
section 6.
3. If the conditions under points 1 and 2 above are not satisfied or
if as described in Section 6.1.2 for dynamic data authentication, the
Issuer Public Key Certificate has been revoked, then PIN
encipherment has failed and the Offline Enciphered PIN CVM has
failed.

Terminal POS Terminal [ICS 1 = YES]

Configuration

Card Profile to Use Card 1 as default with

- CVM List is 00000000 00000000 4403 0103 0203
- Certification Public Key Index is “10.’
- PIN Try Counter “2”.
- 1st Generate AC returns an ARQC
- CDOL1 contains the CVM Results (‘9F34’)

Procedure The card is inserted into the terminal and transaction performed.

Pass Criteria 1. The terminal determines that the retrieval of the public key to
be used for encipherment of the PIN has failed
2. The terminal prompts for a PIN and a correct PIN is entered
3. The terminal shall send a Verify command [for plaintext PIN] to
the card based on the succeeding CVM in the CVM list.
4. Offline Plaintext PIN verification is successful

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 77

 5. The terminal shall set the CVM Results to “010302” indicating
Offline Plaintext PIN was successful.

4.3.24 FUNCTION31 – OFFLINE ENCIPHERED PIN – CAPK “03”

Objective To ensure that If both the terminal and the card support a common
method CVM from the CVM list, and the CVM Lists indicates to
apply succeeding CVM, the next CVM is applied.

To ensure that the terminal set CVM Results correctly.

Specification Interac Debit Terminal Specification (Offline PIN Verification and

Conditions for Support of Functions)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the conditions
described in this section.

Offline PIN verification (plaintext and enciphered) shall be

supported in POS terminals for both online authorizations and
offline authorizations.

The terminal shall comply with EMV Book 3, the Application

Specification.

EMV Book 2, Security and Key Management, Section 7.1 Keys

and Certificates.

The first step of PIN encipherment shall be the retrieval of the

public key to be used by the terminal for the encipherment of the
PIN. This process takes place as follows.
1. If the terminal has obtained all the data objects specified in
Table 24 from the ICC, then the terminal retrieves the ICC PIN
Encipherment Public Key in exactly the same way as it retrieves
the ICC Public Key for offline dynamic data authentication (see
section 6).
2. If the terminal has not obtained all the data objects specified in
Table 24,but has obtained all the data objects specified in Table
12, then the terminal retrieves the ICC Public Key as described in
section 6.
3. If the conditions under points 1 and 2 above are not satisfied or
if as described in Section 6.1.2 for dynamic data authentication, the
Issuer Public Key Certificate has been revoked, then PIN

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 78

 encipherment has failed and the Offline Enciphered PIN CVM has
failed.

Terminal POS Terminal [ICS 1 = YES]

Configuration

Card Profile to Use Card 8a as default with

- PIN Try Counter “2.”
- 1st Generate AC returns an ARQC
- CDOL1 contains the CVM Results (‘9F34’)

Procedure The card is inserted into the terminal and transaction performed.

Pass Criteria 1. The terminal prompts for a PIN and a correct PIN is entered
2. The terminal shall send a Verify command [for enciphered PIN].
3. Offline enciphered PIN verification is successful.
4. The terminal shall set the CVM Results to “440302” indicating
Offline enciphered PIN was successful.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 79

4.4 Minimum Data Elements

These tests are to test that a minimum set of Data Elements are resident in the terminal.

4.4.1 DATA01 – DATA ELEMENTS RESIDENT (1)

Objective The terminal should send the appropriate values to the

following data elements in the Get Processing Options
command:

Additional Terminal Capabilities

Terminal Capabilities
Terminal Type
Transaction Sequence Counter

Specification Interac Debit Terminal Specification (Data Elements)

Interac Cash Terminal Specification (Data Elements)

The terminal (ABM & POS) shall support the following

application-independent data elements:

Name Description Tag

Additional Indicates the data input ‘9F40’
Terminal and output capabilities of
Capabilities the terminal

Terminal Indicates the card data ‘9F33’

Capabilities input, CVM and security
capabilities of the terminal.

Terminal Indicates the environment ‘9F35’

Type of the terminal, its
communication capability
and its operational control.

Transaction Counter maintained by the ‘9F41’

Sequence terminal that is
Counter incremented by one for
each transaction

Terminal All
Configuration

Card Profile to As default but the Select command contains a PDOL with the
Use following data items:
- 9F40 9F33 9F35 9F41in that order

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 80

 Procedure The card is inserted in the terminal and a transaction is
performed

Pass Criteria In the Get Processing Option command the terminal should
send valid data values for the 4 data elements 9F40, 9F33,
9F35 and 9F41.

4.4.2 DATA02 – DATA ELEMENTS RESIDENT (2)

Objective The terminal should send the appropriate values to the

following data elements in the Get Processing Options
command:
Amount Authorised (numeric)
Amount, Other (numeric)
Application Identifier (AID)
Application Version Number
Cardholder Verification Method (CVM) Results (should be
‘000000’)

Specification Interac Debit Terminal Specification (Data Elements)

Interac Cash Terminal Specification (Data Elements)

The data elements listed are mandatory for Interac Debit and
Interac Cash ICC transactions. The data elements that must
reside in the POS or ABM terminal.

Terminal All
Configuration

Card Profile to As default but the Select command contains a PDOL with the
Use following data items:
- 9F02 9F03 9F06 9F09 9F34 in that order

Procedure The card is inserted in the terminal and a transaction is

performed

Pass Criteria In the Get Processing Option command the terminal should
send valid data values for the data elements 9F02 9F03 9F06
9F09 9F34

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 81

4.4.3 DATA03 – DATA ELEMENTS RESIDENT (3)

Objective The terminal should send the appropriate values to the

following data elements in the Get Processing Options
command:
Certification Authority Public Key Index (Should be ‘’00’)
Point of Service (POS) Entry Mode
Terminal Country Code
Terminal Identification
Terminal Verification Results (Should be ‘0000000000’)

Specification Interac Debit Terminal Specification (Data Elements)

Interac Cash Terminal Specification (Data Elements)

The data elements listed are mandatory for Interac Debit and
Interac Cash ICC transactions. The data elements that must
reside in the POS or ABM terminal.

Terminal All
Configuration

Card Profile to As default but the Select command contains a PDOL with the
Use following data items:
- 9F22 9F39 9F1A 9F1C 95 in that order
Procedure The card is inserted in the terminal and a transaction is
performed

Pass Criteria In the Get Processing Option command the terminal should
send valid data values for the data elements 9F22 9F39 9F1A
9F1C 95

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 82

 4.4.4 DATA04 – DATA ELEMENTS RESIDENT (4)

Objective The terminal should send the appropriate values to the

following data elements in the Get Processing Options
command:
Transaction Currency Code
Transaction Date
Transaction Status Information (should be ‘0000’)
Transaction Time
Transaction Type
Unpredictable number

Specification Interac Debit Terminal Specification (Data Elements)

Interac Cash Terminal Specification (Data Elements)

The data elements listed are mandatory for Interac Debit and
Interac Cash ICC transactions. The data elements that must
reside in the POS or ABM terminal

Terminal All
Configuration

Card Profile to As default but the Select command contains a PDOL with the
Use following data items:
- 5F2A 9A 9B 9F21 9C 9F37 in that order

Procedure The card is inserted in the terminal and a transaction is

performed

Pass Criteria In the Get Processing Option command the terminal should
send valid data values for the data elements 5F2A 9A 9B 9F21
9C 9F37

4.4.5 DATA06 – CARD VERIFICATION METHOD RESULTS, CVM FAILURE

Objective If the CVM performed fails, then the terminal sets the CVM
Results data item appropriately

Specification Interac Debit Terminal Specification (CVM Results)

The terminal shall set the CVM results (tag ‘9F34’) as follows:
Byte 1: CVM Method Codes
The CVM Method Codes of the CVM actually
performed by the
terminal (first byte of the last CVM performed)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 83

 Byte 2: CVM Condition Codes
The CVM Conditions Codes of the CVM actually
performed by the
terminal (second byte of the last CVM performed)
Byte 3: CVM Results
Result of the (last) CVM performed as known by the
terminal:
’00’ = Unknown
’01’ = Failed
’02’ = Successful

Terminal POS Terminal [ICS 1 = YES]

Configuration

Card Profile to Use Card 1 - As default with

PIN Try Counter is ‘01’
CVM List being ‘0100’.
1st Generate AC returns an AAC.
CDOL1 contains the CVM Results (‘9F34’)

Procedure A transaction is performed with an incorrect PIN

Pass Criteria The first Generate AC command returns the following value for
CVM Results.
- ‘010001’

4.4.6 DATA07 – CARD VERIFICATION METHOD RESULTS, CVM UNKNOWN {ABM}

Objective If the CVM performed fails, then the terminal sets the CVM
Results data item appropriately

Specification Interac Cash Terminal Specification (CVM Results)

The terminal shall set the CVM results (tag ‘9F34’) as follows:
Byte 1: CVM Method Codes
The CVM Method Codes of the CVM actually
performed by the
terminal (first byte of the last CVM performed)
Byte 2: CVM Condition Codes
The CVM Conditions Codes of the CVM actually
performed by
the terminal (second byte of the last CVM performed)
Byte 3: CVM Results
Result of the (last) CVM performed as known by the
terminal:
’00’ = Unknown
’01’ = Failed
’02’ = Successful

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 84

Terminal ABM Terminal [ICS 2 = YES]
Configuration

Card Profile to Use As default with

CVM List being ‘0200’.
1st Generate AC returns an ARQC.
CDOL1 contains the CVM Results (‘9F34’)

Procedure The card is inserted in the terminal and a transaction is

performed with an incorrect PIN

Pass Criteria The first Generate AC command returns the following value for
CVM Results.
- ‘020000’

4.4.7 DATA08 – CARD VERIFICATION METHOD RESULTS, CVM SUCCESS

Objective If the CVM performed fails, then the terminal sets the CVM
Results data item appropriately

Specification Interac Debit Terminal Specification (CVM Results)

The terminal shall set the CVM results (tag ‘9F34’) as follows:
Byte 1: CVM Method Codes
The CVM Method Codes of the CVM actually
performed by the
terminal (first byte of the last CVM performed)
Byte 2: CVM Condition Codes
The CVM Conditions Codes of the CVM actually
performed by
the terminal (second byte of the last CVM performed)
Byte 3: CVM Results
Result of the (last) CVM performed as known by the
terminal:
’00’ = Unknown
’01’ = Failed
’02’ = Successful

Terminal POS Terminal [ICS 1 = YES]

Configuration

Card Profile to Use As default with

CVM List being ‘0100’.
1st Generate AC returns an AAC.
CDOL1 contains the CVM Results (‘9F34’)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 85

Procedure The card is inserted in the terminal and a transaction is
performed with a correct PIN

Pass Criteria The first Generate AC command returns the following value for
CVM Results.
- ‘010002’

4.4.8 DATA09 – POS ENTRY MODE CODE SETTING

Objective The data element Point of Service (POS) Entry Mode Code is set
correctly if the ICC is read

Specification Interac Debit Terminal Specification (POS Entry Mode Code)

Interac Cash Terminal Specification (POS Entry Mode Code)

The POS Entry Mode Code indicates the source of Cardholder

account data at the terminal according to ISO 8583:1987. If the ICC
is read, the terminal shall generate POS Entry Mode Code value:
‘05’ = ICC Read

Terminal All
Configuration

Card Profile to Use As default with PDOL requesting the POS Entry Mode Code

Procedure The card is inserted in the terminal and a transaction is performed

Pass Criteria The Get Processing Options command returns the value of the POS
Entry Mode (‘9F39’) as ‘05’.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 86

 4.5 Cardholder Interface

This section has identified some tests for the Cardholder Interface.

4.5.1 INTER02 – LANGUAGE - FRENCH AND ENGLISH

Objective If the terminal offers the cardholder a choice of languages, then

that choice must include English and French

Specification Interac Debit Terminal Specification (Language selection)

Interac Cash Terminal Specification (Language selection)

The language selection shall be done by reading the language

code from the ICC unless the card is being read on a magnetic
stripe only reader.
The terminal shall compare the Language Preference list stored
in the IC with the language supported by the terminal and use
the language with the highest preference. If the terminal
supports none of the languages specified in the Language
Preference list the terminal shall allow the Cardholder to select
one of the languages supported by the terminal, which must
include English and French.

Terminal All
Configuration

Card Profile to Use As default with a language preference of Russian

Procedure The card is inserted in the terminal and a transaction is

performed

Pass Criteria The choice of languages offered to the Cardholder includes

English and French

4.5.2 INTER03 – LANGUAGE - FRENCH

Objective If the card supports French, then the transaction must be

conducted in French

Specification Interac Debit Terminal Specification (Language selection)

Interac Cash Terminal Specification (Language selection)

The language selection shall be done by reading the language

code from the ICC unless the card is being read on a magnetic
stripe only reader.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 87

 The terminal shall compare the Language Preference list stored
in the IC with the language supported by the terminal and use
the language with the highest preference. If the terminal
supports none of the languages specified in the Language
Preference list the terminal shall allow the Cardholder to select
one of the languages supported by the terminal, which must
include English and French.

Terminal All
Configuration

Card Profile to Use As default with a language preference of French

Procedure The card is inserted in the terminal and a transaction is

performed

Pass Criteria After application selection the cardholder interface should be in

French

4.5.3 INTER04 – LANGUAGE - ENGLISH

Objective If the card supports English, then the transaction must be

conducted in English

Specification Interac Debit Terminal Specification (Language selection)

Interac Cash Terminal Specification (Language selection)

The language selection shall be done by reading the language

code from the ICC unless the card is being read on a magnetic
stripe only reader.

The terminal shall compare the Language Preference list stored

in the IC with the language supported by the terminal and use
the language with the highest preference. If the terminal
supports none of the languages specified in the Language
Preference list the terminal shall allow the Cardholder to select
one of the languages supported by the terminal, which must
include English and French.

Terminal All
Configuration

Card Profile to Use As default with a language preference of English

Procedure The card is inserted in the terminal and a transaction is

performed

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 88

Pass Criteria After application selection the cardholder interface should be in
English

4.5.4 INTER05 – LANGUAGE - USE 2ND LANGUAGE SUPPORTED BY THE ICC

Objective If the terminal does not support the 1st language in the
Language Preference list on the IC then the 2nd Language
should be used

Specification Interac Debit Terminal Specification (Language selection)

Interac Cash Terminal Specification (Language selection)

The language selection shall be done by reading the language

code from the ICC unless the card is being read on a magnetic
stripe only reader.
The terminal shall compare the Language Preference list stored
in the IC with the language supported by the terminal and use
the language with the highest preference. If the terminal
supports none of the languages specified in the Language
Preference list the terminal shall allow the Cardholder to select
one of the languages supported by the terminal, which must
include English and French.

Terminal All
Configuration

Card Profile to Use As default with a language preference of Russian followed by

French

Procedure The card is inserted in the terminal and a transaction is

performed

Pass Criteria After application selection the cardholder interface should be in

French

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 89

 4.6 Other

This section describes further tests identified from the Terminal Specifications.

4.6.1 OTHER03 – FALLBACK CARD FAULTY

Objective If the chip is faulty the terminal should perform an online

fallback transaction using the magnetic stripe (which will be
declined)

Specification Interac Debit Terminal Specification (Card Reading)

Interac Cash Terminal Specification (Card Reading)

If the terminal fails to process the answer-to-reset because of

an IFD or IC failure, the terminal shall display an error
message to the Cardholder and the Attendant (if POS) and, if
the magnetic stripe has been read, proceeds with a Fallback
transaction using the magnetic stripe of the card.

Terminal All terminals which reads the magnetic stripe and chip together
Configuration [ICS 1.5 = YES]

Card Profile to Use Default but the chip is faulty - Card does not respond to ATR

Procedure The card is inserted in the terminal, and a transaction

performed

Pass Criteria The transaction should go online using the magnetic stripe
data

4.6.2 OTHER04 – FALLBACK CARD FAULTY

Objective If the chip is faulty the terminal should perform an online

fallback transaction using the magnetic stripe (which will be
declined)

Specification Interac Debit Terminal Specification (Card Reading)

Interac Cash Terminal Specification (Card Reading)

In Fallback situations at terminals that have a separate

magnetic stripe reader, the terminal must inform the
Cardholder and the attendant (if POS) to use the magnetic
stripe reader. When the card is swiped, the Fallback magnetic
stripe transaction can be performed.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 90

Terminal POS terminals which have magnetic stripe reader separate to
Configuration the Chip Reader
[ICS 1 and 1.6]
Card Profile to Use Default but the chip is faulty - Card does not respond to ATR

Procedure The card is inserted in the terminal, and a transaction

performed after the magnetic stripe has been swiped

Pass Criteria 1. The terminal should prompt the user to swipe the
card.
2. The transaction should go online using the magnetic
stripe data.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 91

 4.7 Transit

4.7.1 TRANSIT001 – SAF (PURCHASE APPROVED WITH CDA)

Objective SAFing at a POS terminal is permitted for gift shops,

restaurants or other merchants operating on ferries or other
transit vehicles. Merchants in this group may SAF purchase
requests transactions only with message type 0200.

Specification Reader Terminal Specification for Interac Flash

(Section 5.3.5.5.1)

SAFing at a POS terminal is also permitted for gift shops,

restaurants or other merchants operating on ferries or other
transit vehicles. The same conditions defined in Section
5.3.5.4 apply to these merchants with the exception of the
following:

1. Merchants must use MCC value of “4111”, Local and

Suburban Commuter Passenger Transportation, Including
Ferries.

2. The MTI value must reflect the appropriate merchant type.

For example, a restaurant on a ferry would use MCC “4111”
with MTI = “01”. These terminals must not use MTI = “04”.

3. These merchants may SAF contact and contactless

transactions.

4. Merchants in this group may SAF Purchase Authorization

request messages only, message type 0200.

Terminal
Configuration MTI =01 and MCC = 4111
[ICS 1 = Yes and 5 = YES]

Card Profile to Use Use Card 8 – supports CDA

Procedure Perform a contact purchase transaction at a POS terminal on

transit vehicle. Terminal performs the transaction requesting
an ARQC, card returns ARQC and terminal performs CDA
validation.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 92

 SubCase 01: No connectivity during transaction

SubCase 02: No connectivity at the time of transaction,

connectivity is then re-established moments after with the
acquirer host.

Pass Criteria SubCase 01:

CDA validation is successful, terminal stores transaction for
later transmission and displays or signal an approval that rider
is allowed entry. If a transaction record is produced, it must not
indicate the transaction was approved offline.

SubCase 02:
Terminal submits store and Forward transaction to the
Acquirer

4.7.2 TRANSIT002 – SAF (PURCHASE DECLINED WITH CDA)

Objective SAFing at a POS terminal is permitted for gift shops,
restaurants or other merchants operating on ferries or other
transit vehicles. Merchants in this group may SAF purchase
requests transactions only with message type 0200

Specification Reader Terminal Specification for Interac Flash

(Section 5.3.5.5.1)

SAFing at a POS terminal is also permitted for gift shops,

restaurants or other merchants operating on ferries or other
transit vehicles. The same conditions defined in Section
5.3.5.4 apply to these merchants with the exception of the
following:

1. Merchants must use MCC value of “4111”, Local and

Suburban Commuter Passenger Transportation, Including
Ferries.

2. The MTI value must reflect the appropriate merchant type.

For example, a restaurant on a ferry would use MCC “4111”
with MTI = “01”. These terminals must not use MTI = “04”.

3. These merchants may SAF contact and contactless

transactions.

4. Merchants in this group may SAF Purchase Authorization

request messages only, message type 0200.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 93

Terminal
Configuration MTI =01 and MCC = 4111
[ICS 1 = Yes and 5 = YES]

Card Profile to Use Use Card 8 – supports CDA

Procedure Perform a contact purchase transaction at the transit terminal

with card having an invalid dynamic signature. Terminal
performs the transaction requesting an ARQC with CDA.

Pass Criteria CDA Validation fails, terminal does not store or send
transaction and should display or signal a decline that rider is
not permitted entry.

4.7.3 TRANSIT003 – SAF (PURCHASE APPROVED WITH NO CDA)

Objective SAFing at a POS terminal is permitted for gift shops,
restaurants or other merchants operating on ferries or other
transit vehicles. Merchants in this group may SAF purchase
requests transactions only with message type 0200

Specification Reader Terminal Specification for Interac Flash

(Section 5.3.5.5.1)

SAFing at a POS terminal is also permitted for gift shops,

restaurants or other merchants operating on ferries or other
transit vehicles. The same conditions defined in Section
5.3.5.4 apply to these merchants with the exception of the
following:

1. Merchants must use MCC value of “4111”, Local and

Suburban Commuter Passenger Transportation, Including
Ferries.

2. The MTI value must reflect the appropriate merchant type.

For example, a restaurant on a ferry would use MCC “4111”
with MTI = “01”. These terminals must not use MTI = “04”.

3. These merchants may SAF contact and contactless

transactions.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 94

 4. Merchants in this group may SAF Purchase Authorization
request messages only, message type 0200.

Terminal
Configuration MTI =01 and MCC = 4111
[ICS 1 = Yes and 5 = YES]

Card Profile to Use Use Card 1 – no CDA

Procedure Perform a contact purchase transaction at the transit terminal.

Terminal should request ARQC but should not request CDA,
card returns ARQC.

SubCase 01: No connectivity during transaction

SubCase 02: No connectivity at the time of transaction,

connectivity is then re-established moments after with the
acquirer host.

Pass Criteria SubCase 01: Terminal stores transaction for later

transmission. If a transaction record is produced, it must not
indicate the transaction was approved offline.

SubCase 02: Terminal submits Store and Forward transaction

to the Acquirer; transaction is approved without CDA. If a
transaction record is produced, it must not indicate the
transaction was approved offline.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 95

 4.8 Terminal to Acquirer Host testing (Internal tests)

This section will be enhanced with further tests once End-To-End testing has been fully
defined. It is recommended that the following tests should be performed as part of the
certification process.

4.8.1 ENDTOEND01 – TERMINAL SENDS ARQC IN AUTHORISATION MESSAGE

Objective When the terminal receives an ARQC in the response of the 1st
Generate AC then the online authorisation request must send
the ARQC received from the card in the message

Specification Interac Debit Terminal Specification (Online Processing)

Interac Cash Terminal Specification (Online Processing)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

For Interac Direct Payment an Authorization request

Cryptogram (ARQC) and an Authorization Response
Cryptogram (ARPC) are mandatory. The terminal must send
the ARQC in the online authorization request.

Terminal All
Configuration

Card Profile to Use Default returning ARQC in response to first Generate AC

command

Procedure The card is inserted into the terminal and transaction performed

Pass Criteria The ARQC received by the terminal from the card should be the
same one transmitted to the Host

4.8.2 ENDTOEND04 – ISSUER SCRIPT IS SENT TO ICC (‘72’ TAG’)

Objective When the terminal receives an Issuer Script from the Host the
terminal sends it to the card

Specification Interac Debit Terminal Specification (Issuer-to-Card Script

Processing)
Interac Cash Terminal Specification (Issuer-to-Card Script
Processing)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 96

 The terminal shall comply with EMV Book 3, the Application
Specification. It shall support all functions subject to the
conditions described in this section.

Issuer-to-card scripts processing shall be supported as

described in the EMV Book 3 Part III. Section 10.10

Terminal All
Configuration

Card Profile to Use Default Card 1 returning ARQC in response to first Generate
AC command and accepting a PIN Unblock or Application
Block script command

Procedure The card is inserted into the terminal and transaction

performed
Host returns an Issuer Script containing a PIN Unblock or
Application Block inside a ‘72’ tag

Pass Criteria The card should receive an Issuer Script command after the
2nd Generate AC command

4.8.3 ENDTOEND05 – ISSUER SCRIPT IS SENT TO ICC (‘71’ TAG’)

Objective When the terminal receives an Issuer Script from the Host the
terminal sends it to the card

Specification Interac Debit Terminal Specification (Issuer-to-Card Script

Processing)
Interac Cash Terminal Specification (Issuer-to-Card Script
Processing)
The terminal shall comply with EMV Book 3, the Application
Specification. It shall support all functions subject to the
conditions described in this section.

Issuer-to-card scripts processing shall be supported as

described in the EMV Book 3 Part III. Section 10.10

Terminal All
Configuration

Card Profile to Use Default Card 1 - Returning ARQC in response to first Generate
AC command and accepting a PIN Unblock or Application
Block script command

Procedure The card is inserted into the terminal and transaction

performed

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 97

 Host returns an Issuer Script containing a PIN Unblock or
Application Block inside a ‘71’ tag

Pass Criteria The card should receive an Issuer Script command before the
2nd Generate AC command

4.8.4 ENDTOEND06 – SUPPORT OF LARGE ISSUER SCRIPT (‘72’ TAG’)

Objective The terminal should be able to receive a number of Issuer

Scripts from the Host so long as the total length of the Issuer
Script is less than 128 bytes

Specification Interac Debit Terminal Specification (Issuer-to-Card Script

Processing)
Interac Cash Terminal Specification (Issuer-to-Card Script
Processing)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

Issuer-to-card scripts processing shall be supported as

described in the EMV Book 3 Part III. Section 10.10

The terminal shall support Issuer scripts up to 128 bytes (total

length of all Issuer scripts)

Terminal All
Configuration

Card Profile to Use Default returning ARQC in response to first Generate AC

command and accepting a number of Issuer Script commands

Procedure The card is inserted into the terminal and transaction

performed
Host returns an Issuer Script containing a number of Issuer
Script commands inside a ‘72’ tag – total length including tag
and length of the Issuer script is 128 bytes

Pass Criteria The card should receive all Issuer Script commands sent from
the Issuer after the 2nd Generate AC command

4.8.5 ENDTOEND07 – SUPPORT OF LARGE ISSUER SCRIPT (‘71’ TAG’)

Objective The terminal should be able to receive a number of Issuer

Scripts from the Host so long as the total length of the Issuer
Script is less than 128 bytes

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 98

Specification Interac Debit Terminal Specification (Issuer-to-Card Script
Processing)
Interac Cash Terminal Specification (Issuer-to-Card Script
Processing)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

Issuer-to-card scripts processing shall be supported as

described in the EMV Book 3 Part III. Section 10.10

The terminal shall support Issuer scripts up to 128 bytes (total

length of all Issuer scripts)

Terminal All
Configuration

Card Profile to Use Default returning ARQC in response to first Generate AC

command and accepting a number of Issuer Script commands

Procedure The card is inserted into the terminal and transaction

performed
Host returns an Issuer Script containing a number of Issuer
Script commands inside a ‘71’ tag – total length including tag
and length of the Issuer script is 128 bytes

Pass Criteria The card should receive all Issuer Script commands sent from
the Issuer before the 2nd Generate AC command

4.8.6 ENDTOEND09 - REVERSAL SENT IF ICC RESPONDS WITH AAC

Objective The terminal should send a reversal to the host if the card
returns an AAC to the second Generate AC command even
though the Issuer approved the transaction

Specification Interac Debit Terminal Specification (Transaction Reversal)

Interac Cash Terminal Specification (Transaction Reversal)

The terminal shall comply with EMV Book 3, the Application

Specification. It shall support all functions subject to the
conditions described in this section.

A transaction reversal shall be performed for online

authorizations under the following conditions:
- The terminal has received an authorization approval from the
Issuer, the terminal requests a TC in the second Generate AC
command and the ICC returns an AAC

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 99

Terminal All
Configuration

Card Profile to Use Default returning ARQC in response to first Generate AC

command and an AAC in response to the second Generate
AC

Procedure The card is inserted into the terminal and transaction

performed
Host should return an approval

Pass Criteria 1. The card should receive the 1st and 2ndGenerate AC
commands
2. The 2nd Generate AC command received by the
card should be for a TC, but the card returns an
AAC
3. The terminal should send a reversal

4.8.7 ENDTOEND10 – FALLBACK CARD FAULTY

Objective If the chip is faulty and the card is and if the service code on
the magnetic stripe starts with a ‘2’ or a ‘6’, the terminal should
set the appropriate value in the POS Entry Mode data
element, the Issuer should decline

Specification Interac Debit Terminal Specification (Card Reading)

Interac Cash Terminal Specification (Card Reading)

If the terminal fails to process the answer-to-reset because of

an IFD or IC failure, the terminal shall display an error
message to the Cardholder and if the magnetic stripe has
been read, proceeds with a fallback transaction using the
magnetic stripe of the card. The terminal shall report the
exception to the Issuer in the POS Entry Mode data element.
The Issuer shall decline all fallback transactions.

Terminal All
Configuration

Card Profile to Use Default but the chip is faulty - Card does not respond to ATR

Procedure The card is inserted in the terminal, and a transaction

performed

Pass Criteria The transaction should go online using the magnetic stripe
data and the POS Entry Mode data element sent to the host
should be set accordingly.

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 100

4.9 Receipt Printing

4.9.1 TR_RECORD01 – PRINT TRANSACTION RECORD (APPROVED)

Objective To ensure that the Terminal shall either print a Transaction Record
automatically or offer and provide it at the Cardholder’s request and
must be provided upon completion of the Transaction.

Specification Interac Debit Terminal Specification (Printer, Transaction Record)

All POS terminals require a printer for printing customer transaction

records. The printer shall be capable of printing at least 20
characters per line.

The Cardholder transaction record shall contain the AID of the

Interac ICC application and the data that is currently printed on
transaction records for magnetic stripe IDP. “Card Swipe” shall be
changed to “Card Read” or equivalent language when present on
transaction records for ICC transactions.

The Transaction record shall contain the following minimum

information. The order in which this information is printed is a
proprietary matter:

Terminal POS Terminal [ICS 1 = YES]

Configuration

Card Profile to Default Card produces Approved transaction (returning TC)

Use

Procedure The card is inserted in the terminal, and a transaction is performed

Pass Criteria The Transaction record shall contain the following minimum
information. The order in which this information is printed is a
proprietary matter:

1) the local time at the POS Terminal and date of the Transaction;
2) the Issuer Authorization number;
3) a unique Terminal number that performed, or requested the
Transaction (optional);
4) retailer’s trade name and store location (optional);
5) the type of Transaction, (for example, purchase, correction or
credit);

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 101

 6) the amount of the Transaction and account type (for example
savings, chequing) being credited or debited;
7) a Retrieval Reference Number (optional);
8) the last 4 digits of the PAN read electronically from the Card.
9) the disposition of the Transaction (for example, approved or
declined);
10) the amount of any Surcharge charged by the Acquirer (optional);
11) Transaction Records for Chip-initiated Transactions must contain
the AID of the INTERAC Application.
12) POS entry mode
13) The Transaction Record shall not contain any confidential,
financial or personal Cardholder information other than the data
elements listed above

4.9.2 TR_RECORD02 – PRINT TRANSACTION RECORD (DECLINED)

Objective To ensure that the POS Terminal shall either print a Transaction
Record automatically or offer and provide it at the Cardholder’s
request and must be provided upon completion of the Transaction,
regardless of the Transaction’s final status

Specification Interac Debit Terminal Specification (Printer, Transaction Record)

All POS terminals require a printer for printing customer transaction

records. The printer shall be capable of printing at least 20
characters per line.

The Cardholder transaction record shall contain the AID of the

Interac ICC application and the data that is currently printed on
transaction records for magnetic stripe IDP. “Card Swipe” shall be
changed to “Card Read” or equivalent language when present on
transaction records for ICC transactions.

The Transaction record shall contain the following minimum

information. The order in which this information is printed is a
proprietary matter:

Terminal POS Terminal [ICS 1 = YES]

Configuration

Card Profile to Default Card produces Declined transaction (returning AAC)

Use

Procedure The card is inserted in the terminal, and a transaction performed

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 102

Pass Criteria The Transaction record shall contain the following minimum
information. The order in which this information is printed is a
proprietary matter:

1) the local time at the IDP Terminal and date of the Transaction;
2) a unique Terminal number that performed, or requested the
Transaction (optional);
3) retailer’s trade name and store location (optional);
4) the type of Transaction, (for example, purchase, correction or
credit);
5) the amount of the Transaction and account type (for example
savings, chequing) being credited or debited;
6) a Retrieval Reference Number (optional);
7) the last 4 digits of the PAN read electronically from the Card.
8) the disposition of the Transaction (for example, approved or
declined);
9) the amount of any Surcharge charged by the Acquirer (optional);
10) Transaction Records for Chip-initiated Transactions must contain
the AID of the INTERAC Application.
11) POS entry mode
12) The Transaction Record shall not contain any confidential,
financial or personal Cardholder information other than the data
elements listed above

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 103

 5 I NF ORM AT I ON C ONF O RM A NCE S TAT E M E NT ( I CS) F ORM
Organization Name: Test Execution Date:

Reader Make and Model: Terminal Make and Model:

Contact kernel Application name and version: Payment application name and version:

PCI PTS Certification #: EMV L1 Contact Certification #:

PCI COTS Certification # EMV L2 Contact Certification #:

(mandatory for SPOC solutions only)

Test Tool Used: Test Tool Version #:

Function / Capability Yes No Comments

1 Is Terminal POS If ‘Yes’, must support offline PIN
verification (plaintext and enciphered)
1.1 Online Only If ‘Yes’, 3 is optional
1.3 Online Capable If ‘Yes’, 3.2 is mandatory
1.4 Supports Online PIN
1.5 Supports combine Mag-stripe and chip reader
1.6 Separate Mag Stripe Reader
2 Is Terminal ABM If ‘Yes’, must support online PIN
2.1 ABM Supports Offline PIN Verification If ‘Yes’, must support (plaintext and
enciphered)

3 ODA Capability
3.1 Supports Static Data Authentication and Dynamic Mandatory for offline only or online
Data Authentication capable POS Terminals

3.2 Supports Dynamic Data Authentication (DDA)

3.3 Supports Combined Dynamic Data

Authentication (CDA)

4 Support PSE
5 Supports Transit Open Payments If ‘Yes’ CDA on ARQC is mandatory
MTI=01 and MCC=4111
6 Indicate if the device is SCRP If ‘Yes’ PCI COTS Certification is
mandatory
SCRP (Secure Card Reader – PIN) is a PTS approval class that
For Interac Information only
supports PIN entry on COTS devices
No Functional test cases in the checklist
Appendix A
(Software-Based PIN Entry on COTS (SPOC) Solutions enable EMV
contact transactions with PIN entry on the merchant's consumer
device using a secure PIN entry application in combination
with a Secure Card Reader for PIN (SCRP)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 104

 6 AP P E NDI X A - CHE CK L I S T

The tables below detail the tests that must be performed on the terminal depending what is
supported. There is a table of Mandatory tests for POS terminals and a table of
Mandatory Tests for ABM terminals. It the terminal supports Selection using PSE then the
tests in section ‘POS Terminals supporting PSE Selection’ (if the terminal is a POS)
must also be executed.

The last table is a table of OPTIONAL tests that must also be executed against a POS
terminal if it supports offline transactions.

6.1 POS Terminal Tests – Mandatory Tests

The tests in the table below should be performed on all POS terminals:

Organization Name: Certification Date:

Test Tool Used: Test Tool Version #:

TEST Pass / Fail Comment

Select01
Select02
Select09
Select13
Select19
Select21
Select39
Select40a
Select40b
Select41
Select43
Select45
Select46
Function01
Function02
Function07
Function08
Function17
Function23
Function25
Function28
Function29
Function30
Function31
Data01

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 105

 Data02
Data03
Data04
Data06
Data08
Data09
Inter02
Inter03
Inter04
Inter05
Tr_Record01
Tr-Recorrd02

6.2 POS Terminals Tests – Additional Tests based on supported

functionality in ICS

The following tables should be executed if the terminal supports the functionality.

6.2.1 POS TERMINAL SUPPORTS SDA [ICS 3.1 = YES]

If the POS terminal supports Offline Data Authentication [SDA], then the following test
needs to be performed in addition to the tests above for POS terminals:

TEST Pass / Comment

Fail
Function24a
Function24b

6.2.2 POS TERMINAL SUPPORTS DDA [ICS 3.2 = YES]

If the POS terminal supports Offline Data Authentication [SDA], then the following test
needs to be performed in addition to the tests above for POS terminals:

TEST Pass / Comment

Fail
Function27a
Function27b

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 106

 6.2.3 POS TERMINAL SUPPORTS CDA [ICS 3.3 = YES]

If the POS terminal supports Offline Data Authentication [CDA], then the following test
needs to be performed in addition to the tests above for POS terminals:

TEST Pass / Comment

Fail
Function26a
Function26b
Function26c

6.2.4 POS TERMINAL WITH COMBINED CHIP / MAGNETIC STRIPE READER [ICS 1.5 = YES]

If the POS terminal has a combined Magnetic stripe / chip reader, then the following test needs
to be performed in addition to the tests above for POS terminals:

TEST Pass / Fail Comment

Other03
Card01
Card02

6.2.5 POS TERMINAL WITH SEPARATE MAGNETIC STRIPE READER [ICS 1.7 = YES]

If the POS terminal has a separate Magnetic stripe / chip reader, then the following test needs
to be performed in addition to the tests above for POS terminals:

TEST Pass / Fail Comment

Other04

6.2.6 POS TERMINAL SUPPORTS PSE SELECTION [ICS 4 = YES]

If the POS terminal supports PSE selection, then the following tests are mandatory and need to
be performed in addition to the tests above for POS terminals:

TEST Pass / Fail Comment

Select03
Select04
Select05
Select06

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 107

 6.2.7 POS TERMINAL DOES NOT SUPPORTS PSE SELECTION [ICS 4 = NO]

If the POS terminal does not support PSE selection, then the following test needs to be
performed in addition to the tests above for POS terminals:
TEST Pass / Fail Comment
Select07

6.2.8 POS TERMINAL DOES NOT SUPPORT OFFLINE DATA AUTHENTICATION [ICS 1.1= YES AND ICS 3 =
NO]

If the POS terminal does not support Offline Data Authentication, then the following test
needs to be performed in addition to the tests above for POS terminals:

TEST Pass / Fail Comment

Function04

6.2.9 POS TERMINAL SUPPORTS ONLINE PIN [ICS 1.4 = YES]

If the POS terminal supports online PIN, then the following test should be performed in addition
to the tests above for POS terminals (a host connection is required for this optional test):

TEST Pass / Fail Comment

Function11

6.2.10 POS TERMINALS SUPPORT TRANSIT OPEN PAYMENTS [ICS 5 = YES]

If the POS terminal supports Transit Open Payments, then the following tests should be
performed in addition to the tests above for POS

TEST Pass / Fail Comment

Transit001
Transit002
Transit003

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 108

6.3 ABM Terminal Tests – Mandatory Tests

The tests in the table below should be performed on all ABM terminals:
Organization Name: Certification Date:

Test Tool Used: Test Tool Version #:

TEST Pass / Fail Comment

Select01
Select02
Select09
Select26
Select32
Select34
Select40a
Select40b
Select42
Select43
Select44
Card01
Card02
Function01
Function02
Function12
Function22
Data01
Data02
Data03
Data04
Data07
Data09
Inter02
Inter03
Inter04
Inter05
Other03

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 109

 6.4 ABM Terminals Tests – Additional tests based on supported
functionality in ICS

The following tables should be executed if the terminal supports the functionality.

6.4.1 ABM TERMINAL DOES NOT SUPPORT OFFLINE DATA AUTHENTICATION [ICS 3 = ‘NO]

If the terminal is an ABM and it does not support Offline Data Authentication, then the following
test must be performed:

TEST Pass / Fail Comment

Function04

6.4.2 ABM TERMINAL SUPPORTS SDA [ICS 3.1=YES]

If the terminal is an ABM and it supports Offline Data Authentication, then the following
tests must be performed:

TEST Pass / Fail Comment

Function24a
Function24b

6.4.3 ABM TERMINAL SUPPORTS DDA [ICS 3.2=YES]

If the terminal is an ABM and it supports Offline Data Authentication, then the following
tests must be performed:

TEST Pass / Fail Comment

Function27a
Function27b

6.4.4 ABM TERMINAL SUPPORTS CDA [ICS 3.3=YES]

If the terminal is an ABM and it supports Offline Data Authentication, then the following
tests must be performed:

TEST Pass / Fail Comment

Function26a
Function26b

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 110

 6.4.5 ABM TERMINAL SUPPORTS PSE SELECTION [ICS 4 = ‘YES’]

If the ABM terminal supports PSE selection, then the following tests need to be performed in
addition to the tests above for ABM terminals:

TEST Pass / Fail Comment

Select03
Select04
Select05
Select06

6.4.6 ABM TERMINAL DOES NOT SUPPORT PSE SELECTION [ICS 4 = ‘NO’]

If the ABM terminal does not support PSE selection, then the following test needs to be
performed in addition to the tests above for ABM terminals:

TEST Pass / Fail Comment

Select07

6.4.7 ABM TERMINAL SUPPORTS OFFLINE PIN VERIFICATION [ICS 2.1=YES]

If the ABM terminal supports offline PIN then the following tests needs to be performed in
addition to the tests above for ABM terminals:

TEST Pass / Fail Comment

Function09
Function10
Function25

6.5 Terminal to Acquirer Host Testing (optional, as require connectivity

to a host simulator)

The following tests are recommended.

TEST Pass / Fail Comment

EndToEnd01
EndToEnd04
EndToEnd05
EndToEnd06
EndToEnd07
EndToEnd09
EndToEnd10

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 111

 7 AP P E NDI X B - CARD P R OF I L E S US E D I N T HE T E S T I NG
P ROCE S S

This section is detailing the card profiles to be used by the test tool in order to perform the
tests in this guide.

The majority of the testing will be tested against the base card configuration. Some of the
tests will change / add / remove values from the base configuration in order to test specific
functionality i.e.

• the Application Selection Flag (DF62) may change

• LCOL, UCOL data elements may be added
• Issuer Country code (‘5F56’) may be removed
• PDOL may be added

Language Preference may change Data Elements added to CDOL so that the terminal can
log certain data element values, but the majority of the card profile will remain the same.
The test case will state which of the data elements needs a different value or element
adding (if different from the base card).

The PAN (tag 5A) and Track 2 equivalent data (tag 57) are suggested values. Tool
implementer can choose to use other values

7.1 Default Card 1 – Supports Offline Enciphered and Plaintext PIN

Data Element Value Comment

Application Currency ‘0124’

Code (’9F42’)
Application Expiration ‘281231’
Date (5F24)
Application File Locator Up to Test Implementer
Application ID (4F) ‘A000000277 1010’
Application Interchange ‘1C00’
Profile (82)
Application Label (50) ‘496E7465726163’ “Interac”
Application Primary 0012020000001
Account Number (PAN)
(5A)
Application Selection Flag ‘8080’
(DF62)
Application PAN ‘01’
Sequence No. (5F34)
Application Priority ‘01’
Indicator (87)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 112

Application Usage Control ‘AB00’
(9F07)
Application Version ‘0001’
Number (9F08)
CDOL1 (8C) ‘9F0206 9F0306 9F1A02 9505
5F2A02 9A03 9C01 9F3704’
CDOL2 (8D) ’8A 02 9F0206 9F0306 9F1A02 9505
5F2A02 9A03 9C01 9F3704’

or

‘91 0A 8A 02 95 05 9B 02’
Cardholder Name (5F20) “Test Card 1”
Certification Public Key ‘07’
Index
CVM List (8E) ’00 00 00 00 00 00 00 00 04 03 01 03
02 03’
ICC PIN Encipherment ’04AD4F9DC046FD7488920CB34BC
Public Key Certificate BB801350BD08F1330F3078F5D3A8
(‘9F2D’) B8FEA1B7E44E6E20ECC99A51045
56521B5A1FBCFC353BCA6945FB29
765906A5BDE92221EF859652655B
EA34D450D9C50DCEA353EB8577E
FB507E32A22C582E780166E28626
C6C7CF7705B940BE73CDFAC8DF
DF944BFF6454E59DE222A4013C02
D11859680948DD86621F70D235A2
3A021393D5427’
ICC PIN Encipherment ‘010001’
Public Key Exponent
(‘9F2E’)
ICC PIN Encipherment ’3DE7243E95903F6506FFDFFC170E
Public Key Remainder 6E3C93FD8E3E8829F4CCA549’
(‘9F2F’)
Issuer Public Key 1935B30D499CD477F02D09006E81
Certificate (90) 778414C49D0EADE98CB8BAE3D7B
547E7B9302F5FFF5D6F6AB129E87
B756AA88221C0E1C5DE9A76711B3
E631008ABC9F1527455F2343FD9E
77346B621A19671BF9A5FFC31D94
D5AE8E777622340A2E5E81FBE8C9
F064710AD96C0B69E97CBC7EA85
7A1CE1366C7977D2C20B31E1EDF
64D923D56EE74CAACA481EDF578
63F170F648DB1B90F718BA7547E5
B3BD71E68263B630B76C7DFA3C1
03CCD981D89668C45750499F579E

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 113

 02BEFAE7B3439997130D3391B2B6
D4462DB53F674752289253C80A3E
3B1EC799E7ED6A776918E7289B15
23D0614CFABD6FA2BDE090E8C2A
65C2D956D89D84FC2260D1B625’
Issuer Public Key ’010001’
Exponent (9F32)
Issuer Public Key N/A
Remainder (92)
Issuer Action code - ‘F078FCB800’
Default (9F0D)
Issuer Action Code - ‘0010D80000’
Denial (9F0E)
Issuer Action Code – ‘FC7824F880’
Online (9F0F)
Issuer Code Table Index ‘01’
(9F11)
Issuer Country Code ‘43414E’ “CAN”
(5F56)

Data Element Value Comment

Language Preference ‘656E6672’ en – English

(5F2D) fr - French
PIN reference Data ‘24 1234 FFFFFFFFFF’
PIN Try Counter (9F17) ‘03’ Initial Value
PIN Try Limit ‘03’ Internal value
Service Code (5F30) ‘0220’
Track 2 Equivalent Data 0012020000001D2812220001230000
(57) 0002

7.2 Card 2 – Supports SDA

This card is as per the default card except that the data elements below are needed in
order for the terminal to perform SDA

Data Element Value Comment

Application Interchange ‘5C00’

Profile
Certification Public Key ‘07’
Index

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 114

Issuer Public Key 1935B30D499CD477F02D09006
Certificate (90) E81778414C49D0EADE98CB8B
AE3D7B547E7B9302F5FFF5D6
F6AB129E87B756AA88221C0E1
C5DE9A76711B3E631008ABC9
F1527455F2343FD9E77346B62
1A19671BF9A5FFC31D94D5AE
8E777622340A2E5E81FBE8C9F
064710AD96C0B69E97CBC7EA
857A1CE1366C7977D2C20B31
E1EDF64D923D56EE74CAACA
481EDF57863F170F648DB1B90
F718BA7547E5B3BD71E68263B
630B76C7DFA3C103CCD981D8
9668C45750499F579E02BEFAE
7B3439997130D3391B2B6D446
2DB53F674752289253C80A3E3
B1EC799E7ED6A776918E7289
B1523D0614CFABD6FA2BDE09
0E8C2A65C2D956D89D84FC22
60D1B625
Issuer Public Key 010001
Exponent (9F32)
Issuer Public Key N\A
Remainder (92)
Signed Static Application 7D33C7E50E3FFF32FDD63550
Data (93) E237FE74D75815166C3AEEE5
BE3065C37FC114B08B7A4C25
7D2F60A0B51086486A5789B8B
F8611A067176BED8F11911925
D4038B86A03E62120FFED7796
0731FCC995F64E37F62702968
03B36725CB12B1E5EC29EC04
EB78E13BCC88779CB3BFD1B2
B347751497506DA5D427C1836
20AC817BC7ADBFC7AFA94D54
1DFFFCC32700CDD671A

7.3 Card 3 Supports Offline Enciphered PIN

This card is as per the default card except that the data elements below are needed in
order for the terminal to perform enciphered PIN Offline.

Data Element Value Comment

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 115

CVM List (8E) ‘00000000000000000400’

7.4 Card 4 – Supports DDA and Plaintext PIN

As per card image 1 but with the additional / changed data elements so that DDA can be
performed:

Data Element Value Comment

Application Interchange ‘7C00’

Profile
Certification Public Key ‘07’
Index
ICC Public Key Certificate 0DE2798921C3E549645024A95
(‘9F46’) 2877CCE1B963006100C816B06
D46AE09EFB8A2270098CF8F5
ACAAC3D67162E69E4103E590
AF7F38B4E0E0F43CDB67416B
2733B68069897B5455F39A2C0
7CFBDE9181A0A71F4BC56294
ADB0E600E0EFB6283ADDD9F
E1A422BF151F775895A49C6C4
64A9E509C656E177E306A7AE1
2481BCC6169A09D8E5C7D8A7
104A746A0EC041AC84A7
ICC Public Key Exponent 010001
(‘9F47’)
ICC Public Key 3DE7243E95903F6506FFDFFC1
Remainder (‘9F48’) 70E6E3C93FD8E3E8829F4CCA
549
Issuer Public Key 1935B30D499CD477F02D09006
Certificate (90) E81778414C49D0EADE98CB8B
AE3D7B547E7B9302F5FFF5D6
F6AB129E87B756AA88221C0E1
C5DE9A76711B3E631008ABC9
F1527455F2343FD9E77346B62
1A19671BF9A5FFC31D94D5AE
8E777622340A2E5E81FBE8C9F
064710AD96C0B69E97CBC7EA
857A1CE1366C7977D2C20B31
E1EDF64D923D56EE74CAACA
481EDF57863F170F648DB1B90
F718BA7547E5B3BD71E68263B
630B76C7DFA3C103CCD981D8
9668C45750499F579E02BEFAE
7B3439997130D3391B2B6D446
2DB53F674752289253C80A3E3

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 116

 B1EC799E7ED6A776918E7289
B1523D0614CFABD6FA2BDE09
0E8C2A65C2D956D89D84FC22
60D1B625
Issuer Public Key 010001
Exponent (9F32)
Issuer Public Key N/A
Remainder (92)
Signed Static Application 7D33C7E50E3FFF32FDD63550
Data (93) E237FE74D75815166C3AEEE5
BE3065C37FC114B08B7A4C25
7D2F60A0B51086486A5789B8B
F8611A067176BED8F11911925
D4038B86A03E62120FFED7796
0731FCC995F64E37F62702968
03B36725CB12B1E5EC29EC04
EB78E13BCC88779CB3BFD1B2
B347751497506DA5D427C1836
20AC817BC7ADBFC7AFA94D54
1DFFFCC32700CDD671A
DDOL Not present

7.5 Card 5 – Card Contains a PSE

As per the default card image but PSE is supported on the card

7.6 Card 6 – Card Contains 2 Mutually Supported Applications

As per the default card image but a further AID will be contained on the card. This AID can
be any AID supported by the terminal (i.e. a VISA AID or a Mastercard AID for example)

7.7 Card 7 – Supports Online Enciphered PIN

This card is as per the default card except that the data elements below are needed in
order for the terminal to perform enciphered PIN Online

Data Element Value Comment

CVM List (8E) ‘00000000000000000200’

7.8 Card 8 – Supports CDA – CAPK Index “07”, 1984-bit key

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 117

 Data Element Value Comment

Application Interchange ‘1900’

Profile
Certification Public Key ‘07’
Index
ICC Public Key Certificate 0DE2798921C3E549645024A95
(‘9F46’) 2877CCE1B963006100C816B06
D46AE09EFB8A2270098CF8F5
ACAAC3D67162E69E4103E590
AF7F38B4E0E0F43CDB67416B
2733B68069897B5455F39A2C0
7CFBDE9181A0A71F4BC56294
ADB0E600E0EFB6283ADDD9F
E1A422BF151F775895A49C6C4
64A9E509C656E177E306A7AE1
2481BCC6169A09D8E5C7D8A7
104A746A0EC041AC84A7
ICC Public Key Exponent 07
(‘9F47’)
ICC Public Key 3DE7243E95903F6506FFDFFC1
Remainder (‘9F48’) 70E6E3C93FD8E3E8829F4CCA
549
Issuer Public Key 1935B30D499CD477F02D09006
Certificate (90) E81778414C49D0EADE98CB8B
AE3D7B547E7B9302F5FFF5D6
F6AB129E87B756AA88221C0E1
C5DE9A76711B3E631008ABC9
F1527455F2343FD9E77346B62
1A19671BF9A5FFC31D94D5AE
8E777622340A2E5E81FBE8C9F
064710AD96C0B69E97CBC7EA
857A1CE1366C7977D2C20B31
E1EDF64D923D56EE74CAACA
481EDF57863F170F648DB1B90
F718BA7547E5B3BD71E68263B
630B76C7DFA3C103CCD981D8
9668C45750499F579E02BEFAE
7B3439997130D3391B2B6D446
2DB53F674752289253C80A3E3
B1EC799E7ED6A776918E7289
B1523D0614CFABD6FA2BDE09
0E8C2A65C2D956D89D84FC22
60D1B625
Issuer Public Key 010001
Exponent (9F32)

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 118

Issuer Public Key N\A
Remainder (92)
Signed Static Application 7D33C7E50E3FFF32FDD63550
Data (93) E237FE74D75815166C3AEEE5
BE3065C37FC114B08B7A4C25
7D2F60A0B51086486A5789B8B
F8611A067176BED8F11911925
D4038B86A03E62120FFED7796
0731FCC995F64E37F62702968
03B36725CB12B1E5EC29EC04
EB78E13BCC88779CB3BFD1B2
B347751497506DA5D427C1836
20AC817BC7ADBFC7AFA94D54
1DFFFCC32700CDD671A
DDOL Not present
CDOL1 (8C) ‘9F0206 9F0306 9F1A02 9505
5F2A02 9A03 9C01 9F3704
9F45 02 9F4C 08 9F34 03’
CDOL2 (8D) ’91 0A 8A 02 9505 9F37 04 9F4C
08’
7.9 Card 8a – Supports CDA – CAPK Index “03”, 1408-bit key

Data Element Value Comment

Application Interchange ‘1900’

Profile
Certification Public Key ‘03’
Index
ICC Public Key Certificate 4961E0988139F727B656C3C15
(‘9F46’) 671695AA532301872A8A2472C
6200FEC7BD3AE6A19DFB5D0C
E4456E5FD350FF341A4EFFCC
9F16F253B9EC4970075AA16FC
7BF6BCA2C243EF7E774FB666
4CB303E98303236B0A0677BBE
AC614901C3D5BB8AD1D1CAD
4D70D6DDA9D8EE8170919C09
1EE86E383B02B38C735349BC
B75D8B6C129331699BDCAC08
BDE87B8CBE926164B6111
ICC Public Key Exponent 010001
(‘9F47’)
ICC Public Key 3DE7243E95903F6506FFDFFC1
Remainder (‘9F48’) 70E6E3C93FD8E3E8829F4CCA
549

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 119

Issuer Public Key 5C3E7A4CB69952D42D256143
Certificate (90) AB5131F1E6AFFB4D5915E840
E6A0BC0C452AA949A64E7E32
B08F6295E61B5A4854C74BB9B
CED564E1D62152C871A62B04
DFAEC4D475E06C2B466D7F6A
21060BB9B4ADB26532EC17A3
5B919697FAF3E523F906412970
80760245DB9BB38B3ADF0B706
44809E0D41EF410AA17FE93BF
8A339D5870618C20FD073310C
FE8EBC38472102CBFACEF135
FA751DFE60CCF00EA564E158
453492B94FA1F7C4364D7F583
D1DCECB63
Issuer Public Key 03
Exponent (9F32)
Issuer Public Key 48809D71
Remainder (92)
Signed Static Application 895F5B3E2DBC6B7E98C191CD
Data (93) 9AF056AF700EE11471BF92A3B
816B83411257E0FFAD1636C4A
2C147CB4D58F0BFF5A0918056
BEC3C7CA1CA20EF873460A5A
76B9C6BDB7E573881915A8B22
97C7C5092D31D5E302CFECFB
223BFF70AFA4C630C73BBB9B
054B9B7FCADED10F20504C68
BCE2D0345D1425B414CB6703
47CA94AD572D52B7AB182B8F
639FB0D490FE20F4B79D
DDOL Not present
CDOL1 (8C) ‘9F0206 9F0306 9F1A02 9505
5F2A02 9A03 9C01 9F3704
9F45 02 9F4C 08 9F34 03’
CDOL2 (8D) ’91 0A 8A 02 9505 9F37 04 9F4C
08’

7.10 Card 10 – Multi Application Non-cobadge Card

The card as per default card 1 with PSE containing another AID ‘A0 00 00 00 03 80 10'
Interac and Visa Plus

Data Element Value Comment

INTERAC AID ‘A0000002771010’ ASF 8080

API 01

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 120

 AUC FF00
5F56 CAN

Visa PLUS AID 'A0000000038010' ASF 4000

API 02
5F56 CAN

7.11 Card 11a – Multi Application Cobadge Card

Interac and Visa Debit

Data Element Value Comment

INTERAC AID ‘A0000002771010’ ASF 8080

API 02
AUC FF00
5F56 CAN
Visa Debit AID ‘A0000000031010’ ASF 4000
API 01
5F56 CAN

7.12 Card 11b – Multi Application Cobadge Card

Interac and Maestro

Data Element Value Comment

INTERAC AID ‘A0000002771010’ ASF 8080

API 02
AUC FF00
5F56 CAN

AID - Maestro ‘A0000000043060’ ASF 4000

API 01
5F56 CAN

7.13 Card 12 – Multi Application Credit Card

Card containing 2 AIDS – INTERAC AID and Credit Card. The Credit Card AID can be any
AID supported by the terminal (i.e. a VISA Credit Card AID or a Mastercard Credit AID)

Data Element Value Comment

INTERAC AID ‘A0000002771010’ ASF 8000

API 02
AUC FF00
5F56 CAN

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 121

Other AID e.g ASF 4080
'A0000000031010' API 01
‘A0000000041010’ 5F56 CAN

7.14 Card 13 – Supports all offline data authentication methods

Data Element Value Comment

Application Interchange ‘7D00’

Profile
Certification Public Key ‘07’
Index
ICC Public Key Certificate 0DE2798921C3E549645024A95
(‘9F46’) 2877CCE1B963006100C816B06
D46AE09EFB8A2270098CF8F5
ACAAC3D67162E69E4103E590
AF7F38B4E0E0F43CDB67416B
2733B68069897B5455F39A2C0
7CFBDE9181A0A71F4BC56294
ADB0E600E0EFB6283ADDD9F
E1A422BF151F775895A49C6C4
64A9E509C656E177E306A7AE1
2481BCC6169A09D8E5C7D8A7
104A746A0EC041AC84A7
ICC Public Key Exponent 010001
(‘9F47’)
ICC Public Key 3DE7243E95903F6506FFDFFC1
Remainder (‘9F48’) 70E6E3C93FD8E3E8829F4CCA
549
Issuer Public Key 1935B30D499CD477F02D09006
Certificate (90) E81778414C49D0EADE98CB8B
AE3D7B547E7B9302F5FFF5D6
F6AB129E87B756AA88221C0E1
C5DE9A76711B3E631008ABC9
F1527455F2343FD9E77346B62
1A19671BF9A5FFC31D94D5AE
8E777622340A2E5E81FBE8C9F
064710AD96C0B69E97CBC7EA
857A1CE1366C7977D2C20B31
E1EDF64D923D56EE74CAACA
481EDF57863F170F648DB1B90
F718BA7547E5B3BD71E68263B

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 122

 630B76C7DFA3C103CCD981D8
9668C45750499F579E02BEFAE
7B3439997130D3391B2B6D446
2DB53F674752289253C80A3E3
B1EC799E7ED6A776918E7289
B1523D0614CFABD6FA2BDE09
0E8C2A65C2D956D89D84FC22
60D1B625
Issuer Public Key 010001
Exponent (9F32)
Issuer Public Key N\A
Remainder (92)
Signed Static Application 7D33C7E50E3FFF32FDD63550
Data (93) E237FE74D75815166C3AEEE5
BE3065C37FC114B08B7A4C25
7D2F60A0B51086486A5789B8B
F8611A067176BED8F11911925
D4038B86A03E62120FFED7796
0731FCC995F64E37F62702968
03B36725CB12B1E5EC29EC04
EB78E13BCC88779CB3BFD1B2
B347751497506DA5D427C1836
20AC817BC7ADBFC7AFA94D54
1DFFFCC32700CDD671A
DDOL Not present
CDOL1 (8C) ‘9F0206 9F0306 9F1A02 9505
5F2A02 9A03 9C01 9F3704
9F45 02 9F4C 08 9F34 03’
CDOL2 (8D) ’91 0A 8A 02 9505 9F37 04 9F4C
08’

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 123

 7.15 Other Card Information

Data Element Value Comment

ICC Public Key Modulus A85AEFF8D3A72E7187FC351F

5C93E20BE17E3D4E900C6D59
429F9134DA790D8A4C1AEC26
4203EB495F859768895ECB426
1F3F9229A1605A08330ECB9BA
6110F5831221744FD48E8B2769
7E84416482924F241C1B15DC8
C7C39EE81A356017C1EF8D35
33EC6753DE7243E95903F6506
FFDFFC170E6E3C93FD8E3E88
29F4CCA549
ICC Private Key Exponent 1DB425C0E63F09FFB7F974B9F
AD090C27DDF931B8868D8E63
5CE0785A6C252F442A7416122
A6A45DC6BFC04E0E66AE4021
1E35A7B83E087220938240E6B
47794403A3968948F10DA1AE2
458AC891D53BCEA7FB95F17A
F394EBA812E0FEC48A0AE8E5
79222FF63EDAE5E165D9C4526
61BC964B0CB4707CDD750CEA
3AF5733062D

7.16 Issuer RSA Key Information

This section is provided for informational purposes only.

Data Element Value Comment

Issuer Public Key DD2CD3EF49EAECEDCA12C9E

Modulus 04AC943B654E219655534F504E
27D35A02F303D878CB223AE4D
154CAEA3450126B1EF853B327
A07A11E047B7BA86E30F3583B
1B801DD553C94F0F5B352F8D9
3D31BD1F86D83CCE1816372FC
3C82333AA24167CF1CC384B28
7B331A169F74BDB5CD3599A21
B3577FE8A31BBD9307E5CD976
ED43BB0606B7C3BE3198138DA
BDF6218195FA21

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 124

Issuer Private Exponent 12D0886AD7A7E365CB05D4247
F5825A9720915CDF7F49C4F41
1113A9BFB9E3D20F16EC501C8
08E5860CD32EEDEBE186053C7
EBB43A00799CA8544F57B40EB
B2527E488CF1C299B417F725D
9CED3BB5DE522A53324C0F8B
568D86F1CBE6D687983C6EEF8
6133A2322A0CEFE0362CEFDC
E0F969BDD10B5EB04319C0E06
B9CC8223E767E0AA55E7E0572
0FF0DDD404DD9DD

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 125

Copyright © 2021 Interac Corp. All rights reserved.

Except as permitted by law, no part of this document may be reproduced or transmitted by any process or means without prior
written consent of Interac Corp.

Published by Interac Corp, Royal Bank Plaza, North Tower, 200 Bay Street, Suite 2400, P.O. Box 45, Toronto, ON, M5J 2J1

Tel: 416-362-8550 Fax: 416-869-5080

INTERAC TERMINAL APPLICATION CERTIFICATION

VERSION 1.7C – CONFIDENTIAL 126