|Additional data you pass with the tender. The
additionalData object is a generic container that can hold extra response fields. The system uses the card number as a key to collect relevant additional data, for example loyalty data or recurring contract information.
Additional data elements
When the additional data callback is triggered the cash register is provided with a large number of data elements which can be used in business processes to make decisions on the progress of the transaction. This is typically used for loyalty as the most distinguishing information concerns the cardholder-specific information. An example list contains the following:
This field returns time in GMT format.
|Optionally additional elements can be provided:
|Perform a cash back or deactivate a card by passing a stored value redemption type in additional data.
The cashback and deactivate values can be piped to chain the tasks by passing "cashback|deactivate".
All these elements are present for chip-based transactions while several are non-existent for MSR or NFC transactions. Non-existence should not block the cash register from standard operating. Additional elements may be present depending on the transaction options like Gratuity.
Use this object in the following calls and callbacks to represent the Additional Data: