Authcodelog Database Table

Log of Authorisation challenges and responses

Fields

Physkey

#100, Datatype: String 44 bytes
Unique internal key identifying this record

cdtu

#101, Datatype: DateTime
Datetime UTC this record was created

challenge

#102, Datatype: String 44 bytes
Original challenge text

authcode

#103, Datatype: String 44 bytes
Returned Authorisation code

authip

#104, Datatype: String 44 bytes
IP address of the caller generating the authorisation code

Physkeys

#105, Datatype: String 44 bytes
Unique id of the sale this auth record relates too, if applicable

localsid

#106, Datatype: Integer

overdraftflooramt

#107, Datatype: Money/Currency

overdraftcreditamt

#108, Datatype: Money/Currency

entrytype

#109, Datatype: Integer
What type of record this authlog contains

Possible Values

Value	Description
7	Completed requested and used authorisation request
1	Challenge code generated
2	AuthCode generated
4	AuthCode used

Adtu

#110, Datatype: DateTime
Datetime UTC the authcode was created

Udtu

#111, Datatype: DateTime
Datetime UTC the authcode was finally used

AuthTid

#112, Datatype: Integer
If a positive integer then it is the Teller Id who generated the Authorisation code. Negative values indicate special cases

Possible Values

Value	Description
-1	Direct local authorisation password was used
-2	Central authorisation password was used
-3	Direct API authorisation password was used

Comments

#113, Datatype: String 120 bytes
Brief comments

CallerAuthId

#114, Datatype: String 94 bytes
Detected authentication id of the caller. This is typically the Windows login name

CallerAuthIdType

#115, Datatype: Integer
Indicates type of information held in CallerAuthId field

Remarks

Records written to this table may include partial details, the following sequence explains the process

An account attempts to go overlimit at a Point of Sale. The staff member is alerted and challenged for an AuthCode.
The Point of Sale will write a record with the following information
```
Physkey=Unique Key
Challenge=Challenge Text displayed
Physkeys=Unique Sale Key
EntryType=1
```
A head office staff member enters the challenge and generates an AuthCode which is given to the store
A record with the following information will be written. The record written at step #1 may not be availble at this time, so two records will now exist for this challenge
```
Physkey=Unique Key
Challenge=Challenge Text displayed
AuthCode=Generated AuthCode
EntryType=2
Plus details of who generated the AuthCode
```
The store repeats the sale and enters the AuthcCode to complete the sale
The Point of Sale will write a record with the following information
```
Physkey=Unique Key
Challenge=Challenge Text displayed
AuthCode=Generated AuthCode
Physkeys=Unique Sale Key
EntryType=4
```
OR, The customer changes their mind and does not continue. This can happen at steps 1, 2 or 3
No additional information will be written if this happens

The system will detect the records of type 1, 2 and 4, merging these into a single record of EntryType=7 and remove the records of type 1, 2 and 4.

Physkey=Unique Key
Challenge=Challenge Text displayed
AuthCode=Generated AuthCode
Physkeys=Unique Sale Key
EntryType=7
ADtu=Datetime the AuthCode was generated
UDtu=Datetime the AuthCode was used

This table can be joined to the sales table with Sales.Physkey=AuthLogCode.PhyskeyS - note the final "S" on the AuthCodeLog table field name.