CAP 134
|
|
| Category: |
Financial intelligence |
| Business Goal: |
BG-003 — Intelligent financial assistant |
| System Domain: |
SD07 — Data Platform |
| Satisfying Module: |
MOD-087 Transaction enrichment engine (module in design) |
Description
Every transaction in the bank is enriched with a normalised merchant name, merchant logo, merchant category code (MCC), geolocation, and human-readable category before it is surfaced to the customer. Raw payment processor data (e.g. "MCDONALD'S 1234 *NZ AU" becomes "McDonald's" with logo and "Eating out" category).
This is the foundational capability that all other intelligence (classification, geo-spatial analysis, expense automation) builds on. Without clean enrichment, no higher-order capability is reliable.
Enrichment dimensions
| Dimension |
Source |
Example |
| Merchant name |
Normalised from MCC + acquirer descriptor |
"McDonald's" |
| Merchant logo |
Brand asset library (merchant entity match) |
Brand icon |
| Merchant category |
MCC → category mapping + ML override |
"Eating out" |
| Geolocation |
Payment metadata + merchant registry |
lat/lng + address |
| Chain grouping |
Entity resolution — all branches = one merchant |
"McDonald's NZ" |
| Country / jurisdiction |
From geolocation |
NZ |
Consumers
| Consumer |
Usage |
| SD08 transaction history (MOD-070) |
Display enriched merchant on every transaction |
| CAP-135 expense classification |
Enriched merchant is primary classification input |
| CAP-137 rental property attribution |
Merchant type signals property expense |
| MOD-039 customer risk score |
Merchant category signals used in risk features |
| MOD-041 transaction categorisation |
Builds on enrichment to add spend categories |