Creditcrest Enrich
Transactions in; the category, the third party, and how confident it is and why.
Paste a list of transactions and get back, for each one, the category, the third party, and how confident it is and why — with the rule and the words that matched. Where it does not recognise a payee it says unknown, which is the honest answer and is the one an analyst can act on.
It predicts; it does not decide. Whoever holds the credit licence decides. Creditcrest Statement is this same reading turned into income, commitments and expenses, and it calls exactly this.
What happens to what you paste. It is read while the request is open and then it is gone. Nothing is written to disk, nothing is written to a log, nothing is put in a database — there is no database here to put it in. The transactions travel in the request body rather than the address bar, so this reading has no link, which means there is no link to leak.
The cost of that is honest too. Reload and the reading is gone, and the form re-sends what you gave it from your own browser, because there is nothing on this end to refer back to.
No account, no email address, no cookie, no analytics, and nothing on this page is fetched from anywhere. Nothing here calls a hosted model: the rules are a text file in this repository and the whole prediction happens in this process.
What this is for. Categories and third parties are what let you club transactions together, and clubbing them is what turns a list of payments into ongoing commitments and liabilities. That is why a lender wants it, and it is why the output of this is the input to a decision rather than the decision.
What it will not do. It will not decide, it will not score anybody, and it will not fill a gap. A payee it does not recognise is unknown, not other — and a third party is the words a rule recognised in a bank's description rather than a fact about who was paid.