1.9 Transaction Types

EHI sends the following transaction type messages to the external host:

Message Type	Description	How to Process	How you should respond
Authorisation	A request message to approve or decline a payment. Authorisation type transactions include normal authorisation requests and authorisation reversals. An authorisation request message should result in blocking the approved amount on the card to cover a later financial message which is expected to follow.	Gateway or Cooperative Processing (modes 1, 2 and 4): Approve or decline. If approved and you maintain the balance, block the approved amount on the customer’s card.	Gateway or Cooperative Processing (modes 1, 2 and 4): Return a decision (approve or decline) and an acknowledgement. Full Service Processing (mode 3): Return an acknowledgement.
Financial	A notification message which Thredd generates based on the batch clearing files received from the card schemes. Financial type transactions include: First Presentment, Financial Reversal, Second Presentment, Chargeback, Chargeback Reversal and Fees.	Match to an existing authorisation or financial. Gateway or Cooperative Processing (modes 1, 2 and 4): Update the card balance	Return an acknowledgement.
Load	A notification that the customer’s card balance has been credited (via a Web Service, Cards API, Thredd Portal or Smart Client).	Full Service Processing (mode 3): just acknowledge Gateway Processing (modes 1 and 4): not applicable Cooperative Processing (mode 2): Only applicable if Thredd maintains the balance.	Return an acknowledgement.
Unload	A notification that the customer’s card balance has been debited (via a Web Service, Cards API, Thredd Portal or Smart Client).	Full Service Processing (mode 3): just acknowledge Gateway Processing (modes 1 and 4): not applicable Cooperative Processing (mode 2): Only applicable if Thredd maintains the balance.	Return an acknowledgement.
Payment	A notification of a payment originating from a non-card network entity (e.g. Faster Payment or direct debit), paying funds into or out of the customer's card. Note: Only relevant to Agency Banking transactions.	Full Service Processing (mode 3): just acknowledge Gateway Processing (modes 1 and 4): acknowledge and process (update balance) Cooperative Processing (mode 2): Please check with your Implementation Manager.	Return an acknowledgement.
Balance Adjustment	A notification that the customer’s balance has been updated (via a Web Service, Cards API, Thredd Portal or Smart Client). This can be either a credit or debit.	Full Service Processing (mode 3): just acknowledge Gateway Processing (modes 1 and 4): not applicable Cooperative Processing (mode 2): Only applicable if Thredd maintains the balance.	Return an acknowledgement.
Card Expiry	A notification that the customer’s card has expired. Thredd generates this based on the expiry date configured for the card.	Just acknowledge. You can decide whether to renew the card (using the Thredd API)	Return an acknowledgement.