Finicity Transactions Mapping

This data comes from Finicity's /aggregation/v3/customers /{customerId}/accounts /{accountId}/transactions endpoint and is returned from Meld's /bank-linking/transactions endpoint.

To fetch transaction data, Meld calls GetCustomerAccountTransactions the vast majority of the time, Meld only uses the paid endpoint LoadHistoricTransactionsForCustomerAccount for historical transactions (1 time per connection on the initial load). Forced refreshes are done via RefreshCustomerAccountsByInstitutionLogin.

Finicity's transaction signs (positive and negative) are inverted when mapped to make the behavior consistent with other providers. You can find more information on signage here.

Meld	Description	Finicity Response Field
amount	The amount of the transaction	amount
currency	The currency used in the transaction	currencySymbol If null:_ Meld will default to `USD`
description	The transaction's description	description
status	The status of the transaction	status - If returns `Active`, Meld will populate the value as `POSTED` - If returns `Pending`, Meld will populate the value as `PENDING` - If returns `Shadow`, Meld will populate the value as `SHADOW` Note: Some institutions continue to modify or delete transactions long after they are first posted to the institution’s data feed. This practice can cause Finicity transactions to appear as duplicates, or to continue to appear in the Finicity data after they have disappeared from the institution’s current website. Finicity has added the ability to identify transactions that were found in an earlier aggregation of an account, but are not found in the institution’s current data source. These `SHADOW` transactions are identified in the `transaction record`.
transactionDate	The date and time the transaction was made	transactionDate If null:_ postedDate
postedDate	The date and time the transaction was posted	postedDate