Transaction Statuses
A description of the transaction statuses in the Canopy system, and whether they represent a final state or control certain functionality.
This is a description of the transaction statuses in the Canopy system and what they mean in terms of how they control functionality.
Line Item Statuses
Line Item Statuses and Transaction Statuses are equivalent in semantics and application in the system.
Transaction Status | Description | Final State? |
---|---|---|
VALID | A status used to indicate that the transaction's balance has been finalized and posted to the account. An example would be a charge against an an account that had been authorized then posted. | Yes |
INVALID | A final status used to indicate that a transaction's balance should not be applied to the account. | Yes |
OFFSET | An offset transaction is functionally equivalent to an invalid transaction. | Yes |
PENDING | A status used to indicate a transactions which has been initiated, but not yet completed. | No |
AUTHORIZED | A status used to indicate a pending | No |
DECLINED | A final status used for | Yes |
POSTED | Deprecated | β |
VOID | A final status used to indicate that a transaction has been cancelled by the merchant. | Yes |
REVERSED | A final status used to indicate that a transaction previously in a | Yes |
RETRO_VALID | A final status used internally by Canopy to indicate a parent transaction created in retroactive processing: such a transaction will have child transactions in | Yes |
SPLIT VALID | A status used internally by Canopy to indicate a | Yes |
Updated 5 days ago