Client Reference
This data export field displays the client reference collected from the payer in a secure LOCK or PADLOCK payment attempt.
|
Historical Data Source |
CONTACT Data Records |
|
Category |
LOCK/PADLOCK |
|
Channels |
|
|
Size (bytes) |
130 |
|
Filter |
Client Reference |
|
Dimension |
None |
Examples
This data export report shows two payment calls, each tagged with a unique client reference.
Row 1: A call with a PADLOCK (agent-assisted) payment transaction.
Row 2: A call with a LOCK (agent-free) payment transaction.
|
Client Reference |
||||||
|
2018-12-14 08:27:28 |
I |
07700900432 |
1268317001 |
Authorised |
Baz Parsons |
16671 |
|
2018-12-14 11:34:45 |
I |
07700900456 |
5008111501 |
Authorised |
3447 |
Detail
The data export field populates the customer leg of a call of an incoming or outgoing call as illustrated below. See also, Communication Legs.
|
|
External |
storm |
storm user |
|
|
Deskphone LOG IN and LOG OUT |
|
|
|
|
EXTERNAL INCOMING CALL (2 legs) |
|
|
|
OUTGOING CALL dialled directly from deskphone or storm DTA Web iPath (1st leg) |
|
|
|
or OUTGOING CALL initiated from the agent desktop (DTA) (1st leg) |
|
||
|
Initial called party leg (2nd leg) |
|||
|
|
|
|
TRANSFER of an INCOMING or OUTGOING CALL Transfer leg (3rd and subsequent legs) |
||
|
|
Filter
Filter by using any of the following relational operators on your chosen value(s):
|
Equal to |
Greater than |
Less than |
|
Not equal to |
Greater than or equal to |
Less than or equal to |
Remarks
In a live-agent payment transaction, the client reference is requested by the agent; in an agent-free call, it is collected by a Submit Transaction action cell in a FLOW script.
Multiple transaction attempts during a call are presented in a single record. For details about multiple transaction attempts, use the Lock Transactions data source.