Transaction Types & Status Values

Standard Transaction Type Values

The following table maps out the standard values returned under txnType for the Get Transactions and Get All Trans History endpoints.

txnType Values	Description
`purchase.settlement`	Finalized transaction, including funds movement.
`purchase.authorization`	Funds reserved for a transaction.
`purchase.preauth`	Temporary hold placed on funds to verify account validity and availability before the final transaction is completed. Common in scenarios like hotel bookings or gas stations.
`purchase.backout`	A reversal of a previously initiated transaction, typically used when an authorization needs to be reversed prior to settlement.
`atm`	ATM-related transaction.
`ach`	A transfer of funds between bank accounts, typically used for payroll, bill payments, and other scheduled/ad hoc transactions.
`refund`	Money returned to the account from a previous purchase or payment.
`fee`	A debit to the customer account, initiated via the Create Fee endpoint.
`fee.reversal`	A reversal of a previous fee, crediting the customer account.
`a2a.send`	Account to account transfer initiated via the Create A2A Transfer endpoint. This transaction type means the account sent funds to another account.
`a2a.receive`	Account to account transfer initiated via the Create A2A Transfer endpoint. This transaction type means the account received funds from another account.

'Other' Transaction Type Values

Transactions that do not meet the criteria above are categorized under the 'Other' transaction type.

txnType values	Description
`other.dispute_chargeback`	A transaction reversal initiated by the cardholder or issuing bank due to a dispute, typically for unauthorized or fraudulent charges.
`other.dispute_second_presentment`	The merchant’s response to a chargeback, providing evidence to re-present the transaction for approval.
`other.dispute_exceptions`	Transactions flagged during the dispute process that require special handling due to unusual circumstances or errors.
`other.dispute_arbitration`	The final stage of a dispute, where the card network resolves the case between issuer and acquirer after previous attempts failed.
`other.hold`	Funds are temporarily reserved or frozen on an account, often pending transaction settlement or verification.
`other.wires`	Electronic funds transfers between financial institutions, typically used for large or international payments.
`other.rtf`	Real-Time Funding; a transaction that instantly moves funds to or from an account, enabling immediate availability and settlement. Commonly used for rapid account funding or withdrawals.
`other.avs`	Address Verification Service; a check performed during card transactions to verify the cardholder’s billing address.
`other.card_load_auth`	Authorization for loading funds onto a prepaid or debit card, pending final settlement.
`other.card_load_posted`	Confirmation that funds have been successfully loaded onto a card and are available for use.
`other.card_load_reversal`	Reversal of a card load transaction, returning funds to the source due to error or cancellation.
`other.force_post`	Manual posting of a transaction to an account, typically used when standard authorization is unavailable.
`other.merchant_credit`	Funds credited to a merchant’s account, often as a refund or adjustment.
`other.completion`	Finalization of a transaction, confirming that all steps have been successfully processed.
`other.denied_auth`	A transaction authorization request that was declined, preventing the transaction from proceeding.
`other.custom`	See below

📘
Regarding the other.custom Transaction Type
As part of your funds flow set up, you'll configure different transaction sub types that map to specific kinds of money movement.
other.custom transaction types are specific to a given funds flow/program. For example, a retail load for a particular program may have a txnType of other.custom and txnSubType of RL

Transaction Status Values

The following table maps out the possible values returned under status for the Get Transactions and Get All Trans History endpoints.

Status Values	Description
backed_out	The transaction has been reversed or voided after initiation.
reversed	The transaction was completed but has since been undone, often through a refund, chargeback, or manual reversal. Funds were initially moved but later returned.
expired	The transaction was authorized or initiated but not completed within the required timeframe, causing it to automatically expire without fund movement.
hold	Funds have been reserved but not yet transferred.
settled	The transaction has been fully processed and finalized.
pending	The transaction has been initiated but is not yet finalized.

Updated about 2 months ago