For the complete documentation index, see llms.txt. This page is also available as Markdown.

0x0205 - Banking Functions Operation Complete

This notification reports information about progress and state changes that occur during interaction with the Banking Functions modules.

For this notification, Notification Detail described in section 3.2.2.3 Notification Message contains one byte each to indicate:

  • The User Interface Module (UI) involved

  • The Reason (Rsn) for the notification (UI Event)

  • Detail (Det) about the notification that has different meanings depending on the Reason, and

  • An Extra field (Ext) that has different meanings depending on the Reason.

Notification Detail Codes - 0x0205

UI
Rsn
Det
Ext
Meaning

Module 0x01 Touchscreen contains UI notification detail codes that are specific to the touchscreen module (Touch Only)

  • Reason 0x01 = Signature Capture

  • Reason 0x02 = PIN Entry (Banking Functions Only)

01

02

01

01

(Banking Functions Only) Touchscreen, PIN Entry, Success, Data Attached — In this case, the device includes additional data defined in Table XXX, or in Table XXX if the device is including account data with PIN data.

01

02

02

01

(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Timeout

01

02

02

02

(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Hardware Not Available

01

02

02

03

(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Canceled

01

02

02

04

(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Error

01

02

02

05

(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, PIN Verify Failed

01

02

02

06

(Banking Functions Only) Touchscreen, PIN Entry, Operation Failed, Account Data Capture Failed

Notification Payload for Touchscreen, PIN Entry, Success, Data Attached without Account Data (Banking Functions Only)

Tag
Len
Value / Description
Typ
Req
Default

Beginning of Notification Message

0205 = User Interface Operation Complete

84

var

Notification Payload

B

R

/F5

var

Container for Encrypted PIN Data

B

R

//DF71

01

PIN Block Format

  • 0x00 = ISO Format 0

  • 0x01 = ISO Format 1

  • 0x03 = ISO Format 3

  • 0x04 = ISO Format 4

B

R

//99

var

Encrypted PIN Block — ISO Formats 0, 1, and 3 are 8 bytes; ISO Format 4 is 16 bytes

B

R

//DFDF41

var

PIN Key Serial Number (KSN)

B

R

//DFDF42

01

PIN Encryption Type — See section 4.4 Encryption Type for a list of valid values.

B

R

End of Notification Message

Notification Payload for Touchscreen, PIN Entry, Success, Data Attached with Account Data (Banking Functions Only)

Tag
Len
Value / Description
Typ
Req
Default

Beginning of Notification Message

0205 = User Interface Operation Complete

84

var

Notification Payload

B

R

/DFDF59

var

Encrypted Data Primitive — Decrypt the value of this TLV data object using the algorithm and variant specified in the Encrypted Data KSN parameter and the Encrypted Data Encryption Type parameter to read its contents. The format of the decrypted data is shown in Table XXX.

B

R

/DFDF56

var

Encrypted Data KSN

B

R

/DFDF57

01

Encrypted Data Encryption Type — See Encryption Type for a list of valid values.

B

R

/F5

var

Container for Encrypted PIN Data

TC

R

//DF71

01

PIN Block Format

  • 0x00 = ISO Format 0

  • 0x01 = ISO Format 1

  • 0x03 = ISO Format 3

  • 0x04 = ISO Format 4

B

R

//99

var

Encrypted PIN Block — ISO Formats 0, 1, and 3 are 8 bytes; ISO Format 4 is 16 bytes

B

R

//DFDF41

var

PIN KSN

B

R

//DFDF42

01

PIN Encryption Type — See Encryption Type for a list of valid values.

B

R

End of Notification Message

Account Data DFDF59 Decrypted Contents (Banking Functions Only)

Tag
Len
Value / Description
Typ
Req
Default

FC

var

Decrypted Data Container

T

R

/DF42

var

MSR Track 2 Clear Text Data

B

O

/57

var

Track 2 Equivalent Data

B

O

/5A

var

Primary Account Number

B

O

Padding to force DFDF59 plus padding to be a multiple of 8 bytes

Last updated