Standartization and Enrichments

Feezback's layer of transactions identification, standartization, labeling and categorization.

On top of the raw transaction reported by the bank, Feezback attaches an _aggregate object to every transaction with a standardized name, a category, and a set of flags indicating transaction type and occurrence patterns.

Standardized transaction name code

Every transaction's _aggregate object includes:

FieldDescription
standardNameFeezback's canonical name for the transaction. Collapses multiple raw bank description variants into one label — e.g. both חיוב חברת פרטנר and חברת פרטנר תקש map to the standard name פרטנר.
transactionCodeTransaction code mapped to ISO-20022 financial transaction standardisation.

Unique transaction ID

While data providers may return a transaction ID, the availability is unregulated, unexpected and applies different uniqueness rules across different banks. To ensure you don't process the same transaction twice, Feezback generates a unique transactionId for each transaction.

FieldDescription
transactionIdFeezback's unique transactionId. Must have a value.
aspspOriginalIdTransaction ID assigned by the data provider. May be empty.

Categorization

Every CACC/CARD transaction's _aggregate object includes a Hebrew category label:

- ביטוח

- שירותים פיננסיים

- דלק וחנויות נוחות

- הלוואות

- העברות

- כרטיסי אשראי

- לימודים והשכלה גבוהה

- מזומן

- מט"ח

- מים, חשמל וגז

- משכורת

- משכנתה

- ניירות ערך

- עיקולים

- עמלות

- פיקדונות וחסכונות

- פנאי ובילוי

- ריביות

- רפואה, פארם ובתי מרקחת

- שוברים

- שיקים


- תחבורה

- תקשורת

- הוראות קבע


- עירייה וממשלה

Card transactions use a separate, much larger merchant-name-based lookup (not the list above), so card transaction categories are more granular than account-transaction categories — you'll see more specific labels like insurance sub-types or "online shopping."

Transaction type

Every CACC transaction's _aggregate object includes a type object with the following flags:

FlagMeaning
isExpense
Marks the transaction as an expense. Confidence-scored 0.0–1.0, omitted if 0.0. Excludes: buying securities, transfers to savings, pension contributions, foreign currency conversion, cash withdrawals, reversed transactions, loan repayments.
isIncome
Marks the transaction as income. Confidence-scored 0.0–1.0, omitted if 0.0. Excludes: money coming in from deposits/savings, returned/reversed payments, taking out loans, foreign currency conversion, selling securities.
isSalary
Marks a specific transaction as a salary payment.
recurring
Includes value(confidence score), isFixed, isBiMonthly, and relatedTransactionIds (other transactions in the same recurring series). card transactions with the same sub-fields — on cards the field is spelled recurring.expanse (not "expense"), a confirmed typo in the live API — code defensively for that exact spelling.
duplicateCharge
Includes relatedTransactionIds. also available on card transactions with the same sub-fields.
isCCPayment
Marks a transaction as a credit-card payment.
isSecuritiesFee
Marks a transaction as a securities-related fee.

Financial events

The type object includes flags for risk indicators for credit underwriting, including:

FlagMeaning
isNsfEvent
Marks a transaction tied to an NSF (non-sufficient-funds) / bounced-payment event.
isLoanPayment
Marks a transaction as a loan payment.
isWarningEvent
Marks a transaction tied to a bank warning event.
isLoanPayment
DelayEvent
Marks a delayed loan payment.
isTechnicalCheck
BounceEvent
Marks a technical check bounce.

Did this page help you?