A transaction represents a movement of funds. This includes requests via the /transfer/create route, interest paid, manual adjustments, debit card transactions, incoming ACH requests, etc.
The transaction resource is used for retrieving one or more transactions. Transactions that are initiated via the /transfer/create route with external bank accounts (or via a recurring contribution) can be voided as long as the ACH request has not yet been delivered to NACHA.
Take me to the Transaction Endpoint Reference
Data Type (length)
The Helix-assigned unique ID for the account this transaction posted against
The amount of funds the transaction represents.
The exact date and time the funds associated with the transaction became available. Returned in time zone local to the bank.
The Helix-generated unique ID for the card that created the transaction. Will be empty or 0 if this transaction is not tied to a card.
Check object related to check deposit transaction types.
The exact date and time the transaction was created. Returned in time zone local to the bank.
Customer who owns the bank account associated with the transaction.
Only used internally by Q2
depositAvailability object related to deposit transaction types.
Represents a client-specified description of the transaction.
If transaction was received from a NACHA file (
If transaction was received from an ISO-8583 interface (i.e. debit card transaction), this property contains description verbatim from DataElement 43 (Card Acceptor Name/Location) of ISO-8583 interface plus details of any fees or surcharges that may have been incurred. By law, this description must be displayed to the end user.
Otherwise, the transaction was received from a call to Helix API or it was line item in the Bulk Transfer File. This property contains the description verbatim passed by the client code.
The code of the fee this transaction represents. Possible values:
The description of the fee this transaction represents. See
A human-readable description of the transaction. This is automatically generated by Helix driven by the
The name of the financial institution that originated the transaction. Will be populated when possible, but is not always available for all transaction types.
long integer (64-bit integer)
The unique identifier created by Helix used to group related transactions together. Examples: an ACH withdrawal and a subsequent return. A debit card authorization and its corresponding completion(s). A mobile check deposit return and its corresponding original mobile check deposit.
The Nacha return code representing why the transaction was returned.
The exact date and time the transaction was settled. Returned in time zone local to the bank.
The description of the
The Merchant Category Code of the merchant where the transaction originated. Categorizes merchants with similar lines of business together. Applicable only to ISO-8583 based transactions (card).
The program-wide unique identifier provided by the caller during /transfer/create
The total transactions that meet your query criteria. Note: only a single page is returned in one call. See /transaction/list for more information.
long integer (64-bit integer)
The Helix-assigned unique ID for the transaction.
A human-readable description of the type of transaction. Example values include (but are not limited to):
A programmatic code for the type of transaction. See Transaction Types for details.
The exact date and time the transaction was voided. Returned in time zone local to the bank.
Updated 8 months ago