Overview
MoneyKit enhances transaction data from providers by categorizing it into human-readable formats. Enrichment occurs in the background during transaction retrieval, and a webhook notification is sent once the process completes. Only transactions with sufficient data are enriched, and each enriched transaction includes a confidence score reflecting the accuracy of its categorization.
Enrichment data is stored within the transactions.enrichment object, containing the following fields:
- Category: The primary category assigned to the transaction. Available for all enriched transactions. Refer to the full taxonomy below.
- Subcategory (optional): The secondary category for the transaction. Refer to the full taxonomy below.
- Merchant (optional): The predicted merchant, such as a business or store.
- Processor (optional): The predicted payment processor for the transaction.
- Recurrence (optional): Indicates the transaction's regularity if a pattern is detected.
For more detail, refer to our transactions documentation.
Note
The category field in our transaction response has been deprecated, but will still be displayed when available. They are labeled using dotted notation in the format
category[.subcategory][.extra]
. The .subcategory
suffix is optional, and may be omitted, or given as .other
where a more exact subcategory can't reasonably be assigned. If the subcategory is other, extra information may be appended as another dotted string; for example, fee.other.misc_charge
orwages.other.supplemental
.