Challenge | How merchant matching helps solve |
---|---|
Raw merchant data from partners is inconsistent, making it hard to normalize — e.g., “Amazon”, “Amazon #1234”, and “AMAZON.COM 800‑123‑4567” may refer to the same entity. | Merchant matching normalizes every record to a single counterparty and location ID. |
Name‑only matching leads to false positives (e.g., “Sweetgreen” vs. “Sweetgreens Café”). | Spade scores every match (0–100). You choose your own similarity threshold. |
Enrichment APIs require an online call for every transaction. | Merchant matching is offline & one‑time. Once you store the Counterparty/Location IDs, you can identify them in every future transaction response instantly. |