Terminal Data Capability
[What is it?]
- Generally, It is a data element that stores information particularly on terminal that can be individually addressed by tag ID.
Data element resident in the terminal shall be under control of one of the following parties:
• Terminal manufacturer: For example, IFD Serial Number
• Acquirer/Agent: For example, Merchant Category Code
• Merchant: For example, Local Date and Local Time (these may be controlled by either merchant or acquirer)
Terminal should be constructed in such a way that data which is under control of acquirer is only initialised and updated by the acquirer (or its agent).
1. Application Independent Data:
• Terminal related data
• Transaction related data
-Unique to terminal.
-Shall have parameters initialised so that it can identify what language(s) supported to process the card’s language preference.
2. Application Dependent Data:
- A terminal data shall be initialized in the terminal or obtainable at the time of a transaction.
- A terminal data can be of any format: alphabetic, numeric to binary.
- Some terminal data serves as a constant whereas the rest is updatable.
- Each terminal data has its own functionality and usage which facilitates an EMV transaction.
- The dependency of the terminal data in application indicates how data management is done in terminal.
- During the transaction, the terminal shall ignore any data object coming from the ICC which is terminal-sourced or issuer-sourced.
[How it involved in EMV]
Transaction (Exchange/Supply Data to ICC)
Notes: Terminal data element, ICC data element, Issuer data element, EMV function.
Cardholder Verification Method (CVM) Results:
- Being set/updated upon Cardholder Verification completion. [P102B3]
- Consists of 3 bytes: CVM Performed, CVM Condition, and CVM Result.
- There are 5 applicable CVMs in Cardholder Verification: Online PIN, Offline PIN, Signature, No CMV Required, and Combo CVM (2 CVM combination).
- After a successful CVM, CVM Results reflect the successful CVM; an unsuccessful CVM, CVM Results reflect the unsuccessful CVM.
- Byte 3 of CVM Results is set to ‘successful’, IFF:
i. Applicable CVM is ‘No CVM required’, and terminal supports it.
ii. Offline PIN verification by the ICC is successful.
- Byte 3 of CVM Results is set to ‘unknown’, IFF:
i. Applicable CVM is ‘Signature’, and terminal supports it.
ii. Online PIN verification is successful.
- Byte 3 of CVM Results is set to ‘failed’, IFF:
i. Previous applicable CVM is failed, and succeeding (last) application CVM failed as well.
- Byte 1 and byte 2 of CVM Results indicate method and condition of the last performed CVM throughout CMV List. In addition, byte 2 is set to ‘00’ (No meaning) IFF byte 1 is ‘3F’ (No CVM performed).
- Table 2: shows all the possible failed/unknown CVM Results. [P49P121B4]
Terminal Verification Result (TVR)
Initialized to 0: Initiate Application Processing
Function: Offline Data Authentication, Processing Restrictions, Cardholder Verification, Terminal Risk Management, Online Processing, Issuer-to-Card Script Processing.
Use in analysis: Terminal Action Analysis.
Description: Status of different function as seen from terminal.
TVR bytes breakdown:
|TVR byte |EMV Function |Status jotted on bits |When will it be set | | | |RFU |Reserved for future use...
Please join StudyMode to read the full document