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 vs txnSubType

txnType carries the transaction's classification, usually the full value shown below (e.g. purchase.settlement, fee.reversal, a2a.send), with txnSubType empty. txnSubType is only populated in two cases. For ACH, txnType is ach and txnSubType is ach.deposit or ach.withdrawal. For other.custom, txnSubType carries the program-specific code (e.g. RL).

txnType ValuesDescription
purchase.settlementFinalized transaction, including funds movement.
purchase.authorizationFunds reserved for a transaction.
purchase.preauthTemporary 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.backoutA reversal of a previously initiated transaction, typically used when an authorization needs to be reversed prior to settlement.
purchase.completionFinalization of a previously authorized transaction, posting the final amount and completing funds movement.
purchase.expirationAn authorization that expired before settlement; the held funds are released without a posting.
paymentA credit to the customer account, initiated via the Create Payment endpoint (e.g. account funding or load).
atmATM-related transaction.
achA transfer of funds between bank accounts, typically used for payroll, bill payments, and other scheduled/ad hoc transactions.
ach.depositAn incoming ACH credit posted to the account (e.g. direct deposit or inbound transfer).
ach.withdrawalAn outgoing ACH debit from the account (e.g. bill payment or outbound transfer).
refundMoney returned to the account from a previous purchase or payment.
feeA debit to the customer account, initiated via the Create Fee endpoint.
fee.reversalA reversal of a previous fee, crediting the customer account.
a2a.sendAccount to account transfer initiated via the Create A2A Transfer endpoint. This transaction type means the account sent funds to another account.
a2a.receiveAccount 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 valuesDescription
other.balance_rolloverCarryover of a remaining account or bucket balance from one period to the next. Program-specific.
other.bucket_transferMovement of funds between sub-account "buckets" within the same account. Program-specific.
other.finance_chargeInterest or finance charge assessed on the account. Applies to credit products.
other.dispute_chargebackA transaction reversal initiated by the cardholder or issuing bank due to a dispute, typically for unauthorized or fraudulent charges.
other.dispute_second_presentmentThe merchant’s response to a chargeback, providing evidence to re-present the transaction for approval.
other.dispute_exceptionsTransactions flagged during the dispute process that require special handling due to unusual circumstances or errors.
other.dispute_arbitrationThe final stage of a dispute, where the card network resolves the case between issuer and acquirer after previous attempts failed.
other.holdFunds are temporarily reserved or frozen on an account, often pending transaction settlement or verification.
other.wiresElectronic funds transfers between financial institutions, typically used for large or international payments.
other.rtfReal-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.avsAddress Verification Service; a check performed during card transactions to verify the cardholder’s billing address.
other.card_load_authAuthorization for loading funds onto a prepaid or debit card, pending final settlement.
other.card_load_postedConfirmation that funds have been successfully loaded onto a card and are available for use.
other.card_load_reversalReversal of a card load transaction, returning funds to the source due to error or cancellation.
other.force_postManual posting of a transaction to an account, typically used when standard authorization is unavailable.
other.merchant_creditFunds credited to a merchant’s account, often as a refund or adjustment.
other.denied_authA transaction authorization request that was declined, preventing the transaction from proceeding.
other.tokenizationA card tokenization event, such as provisioning the card to a mobile wallet (Apple Pay, Google Pay, Samsung Pay). No funds movement.
other.adjustmentA manual credit or debit adjustment to the account, initiated via the Create Adjustment endpoint.
other.customSee 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 ValuesDescription
backed_outThe transaction has been reversed or voided after initiation.
reversedThe transaction was completed but has since been undone, often through a refund, chargeback, or manual reversal. Funds were initially moved but later returned.
expiredThe transaction was authorized or initiated but not completed within the required timeframe, causing it to automatically expire without fund movement.
holdFunds have been reserved but not yet transferred.
settledThe transaction has been fully processed and finalized.
pendingThe transaction has been initiated but is not yet finalized.
declinedThe transaction has been declined.