HoldingTransactionAction
HoldingTransactions within the platform transition through a number of different workflows depending on the operational model of the markets being operated. The actions that move a HoldingTransaction from one state to another are modelled in this HoldingTransactionAction enumeration.
Values
| Key | Value | Description |
|---|
| Reject | 0 | Move the transaction to the terminal state of an incompleted transaction where the reason for the incomplete state is rejection by the external system. |
| Confirm | 1 | Confirm that the transaction has been completed successfully. |
| Cancel | 2 | Move the transaction to a terminal state showing it as an incompleted transaction where the reason for the incomplete state is the result of a cancellation by an actor within the system. |
| Process | 3 | When a HoldingTransaction is pre-verified by the initiating actor. This is the action when the processing of the transaction has been passed off to the external system for its processing of the transaction. |
| AchReject | 4 | The US payments system has rejected/returned the transaction via an ACH transaction. The rejection will be finalised by an ApprovalReject status change. |
| ApprovalReject | 5 | Complete the transaction rejection via an ACH return instruction. |
| Void | 6 | Void the transaction, similar to Cancel, but moves to Voided status to indicate this was voided by Operators as a mistake. |
| NOP | 99 | A (N)o (OP)eration transaction to allow for the system to ignore incoming banking transactions that have no applicable function in MarketGrid. |
Referenced by
Messages