About
An API that reads bank statements
You send a row from a bank statement. Kederi returns who the money went to or came from, what it was for, and a category. Your product then uses that answer, not the bank's shorthand. Kederi is built first for Nigerian statements, which are mostly transfers in free text.
Who uses it
Teams that read bank statements that their customers share with them. Each page shows the rows that a team sends and what comes back.
Lenders and loan teams
Salary credits, the applicant's own transfers, other loans and betting.
Accounting and audit
Named payees, bank charges by type, and bills that repeat.
Expense and business banking
A category for a transfer to a supplier, from the party and the purpose.
Compliance and screening
The name of the other party, ready for a screening tool.
Why a Nigerian statement needs its own reader
A card statement names a shop. Most rows on a Nigerian statement are transfers between people and businesses, in free text. The row names a bank and a payment service, and the purpose is a few words that the sender typed.
So Kederi reads a transfer for the other party and the purpose first. It finds a shop or a biller in a directory of local merchants, billers and organisations. If a row names nobody, the answer says so. If Kederi is not sure of a name, the answer is marked low, so your product can send that row to a person.
What happens to your data
Kederi stores no transaction. Your rows are in your request, and the answer comes back. Nothing stays on our side to read later. A correction that you send to POST /feedback is the one exception, and only when you send it.
In the console, a CSV, OFX or QIF statement stays in your browser, and only the rows go to the API. A PDF goes to the API, and the console asks you first. See the privacy page.
A bank we do not read yet
If your bank's file or narrations do not read well, tell us the bank and the file type. A real statement from a bank that we do not cover helps most. A tool scrambles its account numbers, phone numbers and references before we keep anything, and nothing from it is ever published. If you can share one, contact us.
Sign upMerchants, billers and counterparty organisations, each carrying the aliases it actually arrives under, so what comes back is a name your user recognises rather than the string their bank sent.