PCI Watch

Tracking changes across the Payment Card Industry

TTA Bulletin nº 210: Contact Terminal Level 2 – Test Cases SB197 Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN

v2.0 Type Approval Bulletins
ChipContact Acceptance Device

countries.

EMV® Terminal Type Approval Bulletin No. 210 Second Edition, December 2018 Terminal Level 2 Test Cases SB197 Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN

Applicability

This Bulletin applies to:

  • EMV® Terminal Type Approval - Level 2 Test Cases – version 4.3g

Related Documents

  • Specification Bulletin 197 Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN).

Effective Date

  • January 1st, 2019

Description

EMVCo introduced the Specification Bulletin 197 Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN). Related to this SB 197, update of tests cases is required in the EMVCo Type Approval Terminal Level 2 Test Cases v4.3g. Update to Section 5 ‘Test Setting’ Add a section 5.4 ‘Output Data The Product Provider must provide a way to observe the kernel output data required in some pass criteria. The preferred option is to provide these data in the network messages

countries.

Update to EMVCo Type Approval Terminal Level 2 Test Cases v4.3g Revised test cases: 2CA.122.02 2CA.122.03 2CA.122.04 2CA.123.01 2CA.129.00 2CA.130.00 2CA.131.00 2CA.132.00 2CA.133.00 2CA.134.00 2CA.135.00 2CA.136.00 2CA.137.00 2CA.138.00 2CA.139.00 2CA.140.00 New test cases: None Deleted test cases: None

countries.

2CA.122.02 EMV reserved Data objects processing (1) Test No: 2CA.122.02 – Revision 43h – Number of sub cases: 9 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference EMV 4.3: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal Configuration: NA Terminal Configuration (New format): [NA] Conditions:

  • All Data Elements listed in the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • Response to GENERATE AC contains all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’,‘9F28’and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’ and shall be encoded in template 77
  • Case 01: FCI (tag 6F) of ADF contains additionally all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’ within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) o f ADF contains additionally all EMV primitve tags (reseved but not used in the EMV specification, (for example ‘9F0C’, ‘‘9F28’ and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’
  • Case 03: Response to GENERATE AC contains all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ and shall be encoded in template 77 and LT request ARQC on first Generate AC
  • Case 04: Records contains: all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’ (splitted over SFI 1 to 10).
  • Case 05: Response to GET PROCESSING OPTIONS contains all EMV primitve tags reseved but not used in the EMV specification, (for countries. 2CA.122.02 EMV reserved Data objects processing (1) example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ and shall be encoded in template 77
  • Case 06: The PDOL of LT contains all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’
  • Case 07: The CDOL1 of LT contains all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’
  • Case 08: The CDOL2 of LT contains all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’ and LT request ARQC on first Generate AC
  • Case 09: The TDOL of LT contains all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria: The terminal shall accept the card and process the transaction until completion, by requesting a TC either at First or Second GENERATE AC. countries. 2CA.122.03 EMV reserved Data objects processing (2) Test No: 2CA.122.03 - Revision 43h - Number of sub cases: 3 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference EMV 4.3: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal Configuration: [PSE] supported Terminal Configuration (New format): [PSE] Conditions:
  • All Data Elements listed in the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • PSE contains a directory file with entries for ADF.
  • Case 01: FCI Issuer discretionary Data (tag BF0C) of PSE contains additionally all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘‘9F28’ and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’'.
  • Case 02: FCI (tag 6F) of PSE contains additionally all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’.
  • Case 03: Template '73' of ADF Directory Entry contains: additionally all EMV primitve tags reseved but not used in the EMV specification, (for example ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’. Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria: The terminal shall accept the card and process the transaction until completion, by requesting a TC. countries. 2CA.122.04 Proprietary Data objects processing (1) Test No: 2CA.122.04 - Revision 43h - Number of sub cases: 7 Objective: To ensure that the terminal ignores Proprietary Data Objects. Reference EMV 4.3: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal Configuration: NA Terminal Configuration (New format): [NA] Conditions:
  • All Data Elements listed in the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • Case 01: FCI (tag 6F) of ADF contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21 within the FCI template
  • Case 02: FCI Issuer di scretionary Data (tag BF0C) of ADF contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21
  • Case 03: Response to GET PROCESSING OPTIONS contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21and shall be encoded in template 77
  • Case 04: The PDOL of LT contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21
  • Case 05: The CDOL1 of LT contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21
  • Case 06: The CDOL2 of LT contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21and LT request ARQC on first Generate AC
  • Case 07: The TDOL of LT contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21 Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. countries. 2CA.122.04 Proprietary Data objects processing (1) Pass Criteria: The terminal shall accept the card and process the transaction until completion, by requesting a TC. countries. 2CA.123.01 EMV reserved Data objects processing Test No: 2CA.123.01 - Revision 43h - Number of sub cases: 2 Objective: To ensure that the terminal ignores EMV reserved Data Objects. Reference EMV 4.3: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal Configuration: [DDA] supported Terminal Configuration (New format): [DDA] Conditions:
  • All Data Elements listed in the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • Case 01: Response to INTERNAL AUTHENTICATE contains all EMV primitve tags reserved but not used in the EMV specification, (for example ‘9F’, ‘9F0C’, ‘9F28’ and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’ and shall be encoded in template 77
  • Case 02: The DDOL of LT contains all EMV primitve tags reserved but not used in the EMV specification, (for example ‘9F’, ‘9F0C’, ‘9F25’ and ‘9F29’, …) in the range ‘80 ’ to ‘9E’ and ‘9F01’ to ‘9F4F’ Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria: The terminal shall accept the card and process the transaction until completion, by requesting a TC. countries. 2CA.129.00 Tokenisation Data in Authorisation or in Financial Request Test No: 2CA.129.00 - Revision 43h - Number of sub cases: 9 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by LT command is transmitted in the Authorisation Request or in Financial Transaction Request. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: ([Online Only] OR [Offline/Online capable]) supported Terminal Configuration (New format): ([Online Only] OR [Offline/Online capable]) Conditions:
  • IAC’s and TAC’s are set so that ARQC is requested at first GENERATE AC.
  • LT returns ARQC at first GENERATE AC
  • Case 01: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 03: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24)
  • Case 04: Response to GET PROCESSING OPTIONS contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 05: Response to First GENERATE AC contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 06: An EMV Record (in the SFI range 1 to 10) to be read contains Token Requestor ID Data Object (tag 9F19)
  • Case 07: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 08: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77 countries. 2CA.129.00 Tokenisation Data in Authorisation or in Financial Request
  • Case 09: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) Action: NA Procedure: Application in LT is selected and transaction is performed online with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC at Second GENERATE AC
  • The output data from the Kernel shall contain the Tokenisation Data Objects with same value as contained in LT. countries. 2CA.130.00 Tokenisation Data in Authorisation or in Financial Request (2) Test No: 2CA.130.00 - Revision 43h - Number of sub cases: 3 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by INTERNAL AUTHENTICATE command is transmitted in the Authorisation Request or the Financial Transaction Request. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: [DDA] AND ([Online Only] OR [Offline/Online capable]) supported Terminal Configuration (New format): [DDA] AND ([Online Only] OR [Offline/Online capable]) Conditions:
  • IAC’s and TAC’s are set so that ARQC is requested at first GENERATE AC.
  • LT returns ARQC at first GENERATE AC
  • Case 01: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to INTERNAL AUTHENTICATE contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 03: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77 Action: NA Procedure: Application in LT is selected and transaction is performed online with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC at Second GENERATE AC
  • The output data from the Kernel shall contain the Tokenisation Data Objects with same value as contained in LT countries. 2CA.131.00 Tokenisation Data in Authorisation or in Financial Request and Response Test No: 2CA.131.00 - Revision 43h - Number of sub cases: 9 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by LT command is transmitted in the Authorisation Request and Response or in the Financial Transaction Request and Response. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: ([Online Only] OR [Offline/Online capable]) supported Terminal Configuration (New format): ([Online Only] OR [Offline/Online capable]) Conditions:
  • IAC’s and TAC’s are set so that ARQC is requested at first GENERATE AC.
  • LT returns ARQC at first GENERATE AC
  • The Authorisation Response (or Financial Transaction Response) contains the PAR Data Object (tag 9F24) and the Last 4 Digits of PAN Data Object (tag 9F25).
  • Case 01: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 03: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24)
  • Case 04: Response to GET PROCESSING OPTIONS contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 05: Response to First GENERATE AC contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 06: An EMV Record (in the SFI range 1 to 10) to be read contains Token Requestor ID Data Object (tag 9F19)
  • Case 07: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77 countries. 2CA.131.00 Tokenisation Data in Authorisation or in Financial Request and Response
  • Case 08: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 09: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) Action: NA Procedure: Application in LT is selected and transaction is performed online with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC at Second GENERATE AC
  • The output data from the Kernel shall contain the Tokenisation Data Objects with same value as contained in LT countries. 2CA.132.00 Tokenisation Data in Authorisation or in Financial Request and Response (2) Test No: 2CA.132.00 - Revision 43h - Number of sub cases: 3 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by INTERNAL AUTHENTICATE command is transmitted in the Authorisation Request and Response. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: [DDA] AND ([Online Only] OR [Offline/Online capable]) supported Terminal Configuration (New format): [DDA] AND ([Online Only] OR [Offline/Online capable]) Conditions:
  • IAC’s and TAC’s are set so that ARQC is requested at first GENERATE AC.
  • LT returns ARQC at first GENERATE AC
  • The Authorisation Response (or the Financial Transaction Response) contains the PAR Data Object (tag 9F24) and the Last 4 Digits of PAN Data Object (tag 9F25).
  • Case 01: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to INTERNAL AUTHENTICATE contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 03: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77 Action: NA Procedure: Application in LT is selected and transaction is performed online with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC at Second GENERATE AC
  • The output data from the Kernel shall contain the Tokenisation Data Objects with same value as contained in LT. countries. countries. 2CA.133.00 Tokenisation Data in Batch Data Capture Test No: 2CA.133.00 - Revision 43h - Number of sub cases: 9 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by LT command is transmitted in the Batch Data Capture. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: [Batch Data Capture] supported Terminal Configuration (New format): [Batch Data Capture] Conditions:
  • Case 01: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 03: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24)
  • Case 04: Response to GET PROCESSING OPTIONS contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 05: Response to First GENERATE AC contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 06: An EMV Record (in the SFI range 1 to 10) to be read contains Token Requestor ID Data Object (tag 9F19)
  • Case 07: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 08: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 09: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) Action: NA Procedure: Application in LT is selected and transaction is performed with LT. countries. 2CA.133.00 Tokenisation Data in Batch Data Capture Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC at First GENERATE AC
  • The output data from the Kernel shall contain the Tokenisation Data Objects with same value as contained in LT countries. 2CA.134.00 Tokenisation Data in Batch Data Capture (2) Test No: 2CA.134.00 - Revision 43h - Number of sub cases: 3 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by INTERNAL AUTHENTICATE command is transmitted in the Batch Data Capture. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: [Batch Data Capture] AND [DDA] supported Terminal Configuration (New format): [Batch Data Capture] AND [DDA] Conditions:
  • Case 01: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to INTERNAL AUTHENTICATE contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 03: Response to INTERNAL AUTHENTICATE contains Tokenisation Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77 Action: NA Procedure: Application in LT is selected and transaction is performed with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC at First or Second GENERATE AC
  • The output data from the Kernel shall contain the Tokenisation Data Objects with same value as contained in LT. countries. 2CA.135.00 Tokenisation Data in Reserval Test No: 2CA.135.00 - Revision 43h - Number of sub cases: 9 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by LT command is transmitted in the Reversal. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: [Online Data Capture] AND ([Online Only] OR [Offline/Online capable]) supported Terminal Configuration (New format): [Online Data Capture] AND ([Online Only] OR [Offline/Online capable]) Conditions:
  • IAC’s and TAC’s are set so that ARQC is requested at first GENERATE AC.
  • LT returns ARQC at first GENERATE AC
  • Transactions are captured online (financial message)
  • Authorization Response Code returned is 'online approved'
  • LT returns AAC to second GENERATE AC.
  • Case 01: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 03: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24)
  • Case 04: Response to GET PROCESSING OPTIONS contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 05: Response to First GENERATE AC contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 06: An EMV Record (in the SFI range 1 to 10) to be read contains Token Requestor ID Data Object (tag 9F19)
  • Case 07: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 08: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77 countries. 2CA.135.00 Tokenisation Data in Reserval
  • Case 09: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) Action: NA Procedure: Application in LT is selected and transaction is performed online with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion
  • The output data from the Kernel shall contain the Tokenisation Data Objects countries. 2CA.136.00 Tokenisation Data in Reserval (2) Test No: 2CA.136.00 - Revision 43h - Number of sub cases: 3 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by INTERNAL AUTHENTICATE command is transmitted in the Reversal. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: [Online Data Capture] AND [DDA] AND ([Online Only] OR [Offline/Online capable]) supported Terminal Configuration (New format): [Online Data Capture] AND [DDA] AND ([Online Only] OR [Offline/Online capable]) Conditions:
  • IAC’s and TAC’s are set so that ARQC is requested at first GENERATE AC.
  • LT returns ARQC at first GENERATE AC
  • Transactions are captured online (financial message)
  • Authorization Response Code returned is 'online approved'
  • LT returns AAC to second GENERATE AC.
  • Case 01: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to INTERNAL AUTHENTICATE contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 03: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77 Action: NA Procedure: Application in LT is selected and transaction is performed online with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion
  • The output data from the Kernel shall contain the Tokenisation Data Objects countries. 2CA.137.00 Tokenisation Data in Online Advice Test No: 2CA.137.00 - Revision 43h - Number of sub cases: 9 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by LT command is transmitted in the Online Advice. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: [Online Data Capture] AND [Advice] AND ([Online Only] OR [Offline/Online capable]) supported Terminal Configuration (New format): [Online Data Capture] AND [Advice] AND ([Online Only] OR [Offline/Online capable]) Conditions:
  • LT requests an Advice in response to First GENERATE AC.
  • LT returns AAC at first GENERATE AC
  • Case 01: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 03: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24)
  • Case 04: Response to GET PROCESSING OPTIONS contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 05: Response to First GENERATE AC contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 06: An EMV Record (in the SFI range 1 to 10) to be read contains Token Requestor ID Data Object (tag 9F19)
  • Case 07: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 08: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 09: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) Action: NA countries. 2CA.137.00 Tokenisation Data in Online Advice Procedure: Application in LT is selected and transaction is performed online with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion
  • The output data from the Kernel shall contain the Tokenisation Data Objects countries. 2CA.138.00 Tokenisation Data in Online Advice (2) Test No: 2CA.138.00 - Revision 43h - Number of sub cases: 3 Objective: To ensure that the presence of Tokenisation Data Object in the data field returned by INTERNAL AUTHENTICATE command is transmitted in the Online Advice. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: [Online Data Capture] AND [Advice] AND [DDA] AND ([Online Only] OR [Offline/Online capable]) supported Terminal Configuration (New format): [Online Data Capture] AND [Advice] AND [DDA] AND ([Online Only] OR [Offline/Online capable]) Conditions:
  • LT requests an Advice in response to First GENERATE AC.
  • LT returns AAC at first GENERATE AC
  • Case 01: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to INTERNAL AUTHENTICATE contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 03: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded i n template 77 Action: NA Procedure: Application in LT is selected and transaction is performed online with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion
  • The output data from the Kernel shall contain the Tokenisation Data Objects countries. 2CA.139.00 Tokenisation Data supported Test No: 2CA.139.00 - Revision 43h - Number of sub cases: 9 Objective: To ensure that the presence of Tokenisation data object in the data field returned by LT command is ignored when the terminal does not use it, or accepts when the terminal use it. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: NA Terminal Configuration (New format): [NA] Conditions:
  • Case 01: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 03: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24)
  • Case 04: Response to GET PROCESSING OPTIONS contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 05: Response to First GENERATE AC contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 06: An EMV Record (in the SFI range 1 to 10) to be read contains Token Requestor ID Data Object (tag 9F19)
  • Case 07: Response to GET PROCESSING OPTIONS contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 08: Response to First GENERATE AC contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 09: An EMV Record (in the SFI range 1 to 10) to be read contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) Action: NA Procedure: Application in LT is selected and transaction is performed with LT. countries. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC on first GENERATE AC or Second GENERATE AC. countries. 2CA.140.00 Tokenisation Data supported (2) Test No: 2CA.140.00 - Revision 43h - Number of sub cases: 3 Objective: To ensure that the presence of Tokenisation data object in the data field returned by INTERNAL AUTHENTICATE command is ignored when the terminal does not use it, or accepts when the terminal use it. Reference EMV 4.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data Objects – Payment Account Reference (PAR) (April 2016) Terminal Configuration: [DDA] supported Terminal Configuration (New format): [DDA] Conditions:
  • Case 01: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and shall be encoded in template 77
  • Case 02: Response to INTERNAL AUTHENTICATE contains Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77
  • Case 03: Response to INTERNAL AUTHENTICATE contains PAR Data Object (tag 9F24) and Token Requestor ID Data Object (tag 9F19) and shall be encoded in template 77 Action: NA Procedure: Application in LT is selected and transaction is performed with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC on first GENERATE AC or Second GENERATE AC. countries.

Legal Notice

This document summarizes EMVCo’s present plans for evaluation services and related policies and is subject to change by EMVCo at any time. This document does not create any binding obligations upon EMVCo or any third party regarding the subject matter of this document, which obligations will exist, if at all, only to the extent set forth in separate written agreements executed by EMVCo or such third parties. In the absence of such a written agreement, no product provider, test laboratory or any other third party should rely on this document, and EMVCo shall not be liable for any such reliance. No product provider, test laboratory or other third party may refer to a product, service or facility as EMVCo approved, in form or in substance, nor otherwise state or imply that EMVCo (or any agent of EMVCo) has in whole or part approved a product provider, test laboratory or other third party or its products, services, or facilities, except to the extent and subject to the terms, conditions and restrictions expressly set forth in a written agreement with EMVCo, or in an approval letter, compliance certificate or similar document issued by EMVCo. All other references to EMVCo approval are strictly prohibited by EMVCo. Under no circumstances should EMVCo approvals, when granted, be construed to imply any endorsement or warranty regarding the security, functionality, quality, or performance of any particular product or service, and no party shall state or imply anything to the contrary. EMVCo specifically disclaims any and all representations and warranties with respect to products that have received evaluations or approvals, and to the evaluation process generally, including, without limitation, any implied warranties of merchantability, fitness for purpose or non-infringement. All warranties, rights and remedies relating to products and services that have undergone evaluation by EMVCo are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo will have no liability whatsoever in connection with such products and services. This document is provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in this document. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON -INFRINGEMENT, AS TO THIS DOCUMENT. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to this document. EMVCo undertakes no responsibility to determine whether any implementation of this document may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of this document should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, this document may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement this document is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party's infringement of any intellectual property rights in connection with this document.