Skip to main content

Transactions

A transaction is an individual entry that represents a financial movement within an account. The Transaction resource represents a confirmed financial transaction that were posted to the account, including its source, amount, and direction.

Transactions cannot be created using Unit's API, they are always the result of other activity, in or out of the platform, that resulted in actual movement of funds. For instance, if you originate an ACH Debit payment, a transaction will be created once the payment has been processed and the clearing period has passed. It is for this reason that transactions do not have statuses.

Transactions are final, and cannot be deleted or changed. In order to reverse a transaction (for example, a refund after a card Purchase transaction), a new, opposite, transaction will have to be created (in our example, a Card Reversal transaction).

Suggestion

Unit provides a cross-platform suite of flexible and customizable white-label UI components, including an activity component that allows the end customer to see their transactional activity on an account or card level. You may embed the activity component into your app to shorten your time to market and deliver a highly optimized experience to your end customer with minimal engineering investment.

Transaction Types

Unit currently supports the following types of transactions:

TypeDescription
Originated ACHAn ACH payment originated from a deposit account.
Received ACHAn ACH payment received by a deposit account.
Returned ACHAn ACH payment returned by the bank.
Returned Received ACHA received ACH payment that has been returned through Unit.
Dishonored Return ACHA returned ACH that was dishonored by the receiving bank.
WireA wire transaction, either received or sent.
Returned WireA returned wire transaction.
BookA payment between two accounts on the same bank.
PurchaseA purchase via debit card.
ATMA deposit or a withdrawal of funds from an ATM with a debit card.
FeeFees incurred for a transaction.
Fee ReversalA reversal of a previous fee transaction.
InterestAn Interest payment to a deposit account.
Card ReversalA reversal of a previous card transaction.
Card TransactionA transaction that represents various card transactions that are not Purchase or ATM transactions. Those might be split in the future into different types.
ReleaseA transaction releasing funds from a batch account.
AdjustmentManual Adjustment is made in situations where the correction of an amount, or a reverse of a completed transaction is needed.
DisputeDispute transaction is created in order to credit or debit a customer for an ongoing card or ACH dispute. For example, when provisional credit is provided, the customer account would be credited using the Dispute Transaction.
Check DepositA received check deposit.
Returned Check DepositA check deposit returned by the bank.
Payment CanceledCancellation of a previously processed ACH payment.
Payment AdvancePayment advance transaction is created in order to Debit an org account against a ReceivedPayment that is advanced .
Repaid Payment AdvanceRepaid payment advance transaction is created when a ReceivedPayment is Completed in order to Credit an org account and repay it for a received payment that was advanced.
ChargebackA transaction that represent a Chargeback.
RewardA transaction that represent a Reward.
Account Low Balance ClosureHandling of low balance upon account closure.
Negative Balance CoverageA transaction that occurs when closing an account with negative balance. covering the account negative balance.
Check PaymentA Debit transaction that occurs when a Check Payment is processed successfully (Processed status).
Returned Check PaymentA Credit transaction that occurs when a Check Payment has been returned through Unit (Returned status).
Push To CardA Debit transaction that was created from a PushToCard Payment originated from a deposit account.
Push To Card ReversalA Credit transaction that was created in order to reverse a previous Push To Card transaction.
Cash DepositA Credit transaction that occurs when cash is deposited at a Store Location.
Write OffA Credit transaction that occurs when an uncollectible balance is written off.

Common Transaction Fields

In addition to their own specific fields, all transaction types are guaranteed to contain the following top-level fields:

direction
string
The direction in which the funds flow- Debit or Credit.
amount
integer
The amount (cents) of the transaction.
balance
integer
The account balance (cents) after the transaction.
summary
string
Human-friendly summary of the transaction.
createdAt
RFC3339 Date string
The date the transaction was created
Note

New transaction types may be added in the future, as we introduce new financial products. To minimize code changes on your side, we recommend using the summary field when displaying transactions to end-customers.

Transaction Summaries

The transaction summary field is used whenever the transaction details are presented. This applies to monthly statements, data exports (e.g. Plaid, Intuit), and the Unit Dashboard. It is recommended that you use that field when displaying transactions within your UI. The table below describes what how the summary field is generated for each of the transaction types.

Transaction typeSummary structureExampleComments
Originated ACH<counterparty_name> | <txn_addenda>Richard Hendrix | ACH PYMT
Received ACH<txn_company_name> | <txn_description>Pied Piper INC | Pied Piper
ReturnedACHReturned due to: <txn.reason> | <txn.counterparty_name>Returned due to: InsufficientFunds | Richard Hendrix
ReturnedReceivedACHReturned received ACH transaction #<txn.relatedTransactionId> due to: <tx.reason>Returned received ACH transaction #1234567 due to: InsufficientFunds
DishonoredACHDishonored Return ACH transaction due to: <txn.reason>Dishonored Return ACH transaction due to: UntimelyReturn
Card PurchasePurchase from <txn.merchantName> | address: <txn.merchant_address> | <txn.cardLast4Digits>Purchase from 7-ELEVEN, 7-ELEVEN | Address: ORLANDO, FL, US | **1234
Return from <txn.merchantName> | address: <txn.merchant_address> | <txn.cardLast4Digits>Return from 7-ELEVEN, 7-ELEVEN | Address: ORLANDO, FL, US | **1234
Card Transaction<txn.description> | <tx.cardLast4Digits>Cash App*Cash Out, Visa Direct, CA, US | **1234
ATMWithdraw at <txn.atmName> | address: <txn.address> | <txn.cardLast4Digits>Withdraw at Community Bank, 1983 Beach Blvd | Address: Biloxi, MS, US | **1234
Deposit at <txn.atmName>| address: <txn.address> | <txn.cardLast4Digits>Deposit at Community Bank, 1983 Beach Blvd | Address: Biloxi, MS, US | **1234
Card ReversalReversal for transaction <txn.relatedTransactionId> | <txn.cardLast4Digits>Reversal for transaction #5146923 | **5380
Check Deposit<txn.description>
Check returnReturned due to: <return reason> | <description>Returned due to: Unable to Locate Account | Pied Piper
Fee<txn.description>Physical Card Replacement Fee
Fee ReversalReversal fee transaction for <relatedTransaction.id> | <description>Reversal fee transaction for #123Moves Card Replacement Fee
BookSender: txn.receiver_name | txn.descriptionSender: Richard Hendrix | Peer payment: Henry
Receiver: txn.receiver_name | txn.descriptionReceiver: Richard Hendrix | Peer payment: Henry
Batch Release<txn.description> | <txn.senderName>Cash Deposit CVS | Richard Hendrix
Interchange<txn.description>Accel ATM
Interest<txn.description>Interest February 2022
WireWire from <sender_name> | <description>Wire from SVB FOR BENEFIT OF Pied Piper | VI FUND I A SERIES OF company ID 12345
Wire to <beneficiary_name> | <description>Wire to SVB FOR BENEFIT OF Pied Piper | VI FUND I A SERIES OF company ID 12345
ReturnedWireReturned due to <reason> | <description>Returned due to: NAMEMISSMATCH | AZ -Part Commission
DisputeDispute <dispute_id> | <dispute_reason>Dispute 3432 | Final Credit
ChargeBack<txn_description>
Payment CancelledCancellation of: <txn.id> | Payment Id: <payment.id>Cancellation of: 381481 | Payment Id: 65647
Adjustment<free form summary>
WriteOff<txn.description>Write off for account 10014
  • APIs - Retrieve, list, and update transactions
  • Events - Webhook events for transaction lifecycle
  • Resources - JSON:API resource schemas for transaction types