Terminal Data Capability Emv
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).
[Types]
1. Application Independent[1] 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[2] Data:
[Characteristic]
- 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)
Counter
Record (updatable)
Comparable
Reference
Notes: Terminal data element, ICC data element, Issuer data element, EMV function.
[Counter]
[Record]
Cardholder Verification Method (CVM) Results:
- Being set/updated upon Cardholder Verification
[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).
[Types]
1. Application Independent[1] 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[2] Data:
[Characteristic]
- 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)
Counter
Record (updatable)
Comparable
Reference
Notes: Terminal data element, ICC data element, Issuer data element, EMV function.
[Counter]
[Record]
Cardholder Verification Method (CVM) Results:
- Being set/updated upon Cardholder Verification