3 ms·
Sorry for not getting this right away: but are you solely matching the string to a merchant and then returning all of the (already-stored) information for that
by fitzn 5y ago
Sorry for not getting this right away: but are you solely matching the string to a merchant and then returning all of the (already-stored) information for that merchant? Or are you joining that to some other public record of transactions to get additional information?
In other words, in the example on the homepage, is all of the returned data except the dollar amount static data from a DB once you have matched the transaction to the merchant (Google in this case)?
And then sort of unrelated, what are your long-term plans? If step 1 is perfectly hydrating a merchant to a transaction, what is step 2 (if there is one)?
- ferradas 5y agoGreat questions. Yes, we match the raw string to a merchant with extra static fields (URL, icon, logo, Merchant Category Code). In our mind, merchant enrichment unlocks many possibilities. The most obvious one is to have a nice and modern bank transaction feed. But our customers also use us to lock company cards to particular merchants, group by merchants to see where people are spending the most, and more. Would love to hear if you had other "step 2"s in mind!