What's Tag91 - Revision history

Mahong: Replaced content with "{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/emv/whats-tag91}}"

2024-04-08T05:15:28Z

Replaced content with "{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/emv/whats-tag91}}"

← Older revision		Revision as of 05:15, 8 April 2024
Line 1:		Line 1:
	~~=== Definition and Purpose~~: ~~===~~		{{Migrating\|https://smartpossdk.gitbook.io/cloudpossdk/faq/emv/whats-tag91}}
	* '''Tag 91''' in the context of EMV (Europay, MasterCard, and Visa) standards refers to 'Issuer Authentication Data'.
	* This data is crucial for the authentication process during an EMV transaction. It is provided by the card issuer and plays a significant role in securing the transaction.
	~~=== Operational Context: ===~~
	* '''Host Response:''' Tag 91 is typically returned by the host (e.g., bank or card issuer's server) as part of the transaction response.
	* '''Integration with EMV Kernel:''' Once received, the issuer authentication data in Tag 91 must be correctly set or inputted into the EMV kernel of the smart POS system. This step is essential for the completion and validation of the transaction process.
	~~=== Key Considerations: ===~~
	* '''Security and Compliance:''' The handling of Tag 91 data must adhere to EMV security standards and protocols to ensure the integrity and security of the transaction.
	* '''Software Integration:''' Smart POS systems must have robust software capable of accurately processing and integrating Tag 91 data into the transaction flow.
	~~=== Technical Implementation: ===~~
	* '''Data Format and Content:''' The issuer authentication data may contain cryptographic information essential for validating the transaction. The format should be compatible with the EMV kernel's requirements.
	* '''Error Handling:''' The smart POS system should be equipped to handle any errors or discrepancies in Tag 91 data, alerting the operator and taking appropriate actions as per defined protocols.
	~~=== Usage in Transaction Process: ===~~
	* During an EMV transaction, the smart POS system retrieves Tag 91 data from the transaction response and utilizes it as part of the issuer authentication procedure.
	~~'''Note:'''~~
	* Understanding and correctly implementing the handling of Tag 91 is vital for developers and technicians working with EMV systems in smart POS terminals. It ensures not only the security of transactions but also compliance with global EMV standards.

Simon no use at 17:43, 14 January 2024

2024-01-14T17:43:01Z

← Older revision		Revision as of 17:43, 14 January 2024
Line 1:		Line 1:
	Tag 91 is issuer authentication data~~, which will~~ be ~~returned by~~ the ~~host~~ and ~~needs~~ to be ~~set~~ to ~~emvkernel~~.		=== Definition and Purpose: ===
			* '''Tag 91''' in the context of EMV (Europay, MasterCard, and Visa) standards refers to 'Issuer Authentication Data'.
			* This data is crucial for the authentication process during an EMV transaction. It is provided by the card issuer and plays a significant role in securing the transaction.
			=== Operational Context: ===
			* '''Host Response:''' Tag 91 is typically returned by the host (e.g., bank or card issuer's server) as part of the transaction response.
			* '''Integration with EMV Kernel:''' Once received, the issuer authentication data in Tag 91 must be correctly set or inputted into the EMV kernel of the smart POS system. This step is essential for the completion and validation of the transaction process.
			=== Key Considerations: ===
			* '''Security and Compliance:''' The handling of Tag 91 data must adhere to EMV security standards and protocols to ensure the integrity and security of the transaction.
			* '''Software Integration:''' Smart POS systems must have robust software capable of accurately processing and integrating Tag 91 data into the transaction flow.
			=== Technical Implementation: ===
			* '''Data Format and Content:''' The issuer authentication data may contain cryptographic information essential for validating the transaction. The format should be compatible with the EMV kernel's requirements.
			* '''Error Handling:''' The smart POS system should be equipped to handle any errors or discrepancies in Tag 91 data, alerting the operator and taking appropriate actions as per defined protocols.
			=== Usage in Transaction Process: ===
			* During an EMV transaction, the smart POS system retrieves Tag 91 data from the transaction response and utilizes it as part of the issuer authentication procedure.
			'''Note:'''
			* Understanding and correctly implementing the handling of Tag 91 is vital for developers and technicians working with EMV systems in smart POS terminals. It ensures not only the security of transactions but also compliance with global EMV standards.

Jeff nouse at 07:24, 30 March 2020

2020-03-30T07:24:48Z

← Older revision		Revision as of 07:24, 30 March 2020
Line 1:		Line 1:
	Tag 91 is issuer authentication data, it will be returned by host and ~~need~~ to be set to emvkernel.		Tag 91 is issuer authentication data, which will be returned by the host and needs to be set to emvkernel.

Jeff nouse at 07:21, 30 March 2020

2020-03-30T07:21:17Z

← Older revision		Revision as of 07:21, 30 March 2020
Line 1:		Line 1:
	Tag 91 is issuer authentication data, it will be returned by host and need to be set to emvkernel.		Tag 91 is issuer authentication data, it will be returned by host and need to be set to emvkernel.

Mahong: Created page with " Tag 91 is issuer authentication data, it will be returned by host and need to be set to emvkernel."

2019-05-13T03:00:41Z

Created page with " Tag 91 is issuer authentication data, it will be returned by host and need to be set to emvkernel."

New page

Tag 91 is issuer authentication data, it will be returned by host and need to be set to emvkernel.