Use case
Kederi for expense and business banking
An expense product puts each payment in a category. A card payment names a merchant, so that is easy. A Nigerian business pays most suppliers by transfer, and a transfer names a person or a company and a few words that the sender typed.
Without those words, a transfer is a manual entry. Kederi returns the party, the purpose and a category, so more rows go to a category with no person. The people, accounts and references in the examples are invented. The businesses are real merchants in our directory. A test runs each one through the engine and compares each answer on this page.
A transfer to a supplier
The party is in name and counterparty. The words that the sender typed are in remark. Your rules, or your customer, decide the category from the two.
Diesel, with FOR
NIP TRANSFER TO IFEOMA OBI FOR DIESEL SUPPLYCounterparty Ifeoma Obi, remark diesel supply. In this narration, the words after FOR are the purpose, so they are not in the name.
Office supplies, with a slash
NIP/ACCESS/GRACELAND VENTURES/OFFICE STATIONERYCounterparty Graceland Ventures, remark office stationery.
A card payment
For a card payment, Kederi returns the merchant's name, a category and a merchant category code (MCC), so the row can follow the same rules as a card feed from any other market.
A ride
UBER *TRIP HELP.UBER.COMName Uber, category Transport, MCC 4121.
A supermarket
POS PURCHASE SHOPRITE LEKKIName Shoprite, category Supermarket, MCC 5411.
More than one row
POST /enrich takes one row, or a batch of up to 1,000. Send an account_id, an amount and a date with each row of a batch. If three or more rows go to the same party at a regular interval, with a similar amount, each of them comes back with a recurrence.
POST /reports gives the reports over the rows of one account, for example fees for the bank charges and subscriptions for the software and the bills that repeat each month.
POST /feedback takes a correction from your customer. GET /feedback shows what happened to it.
What Kederi does not do
Kederi does not read receipts, issue cards or approve spend. It reads the bank's row and returns structured data.
Kederi stores no transaction. Your customer's rows are in your request, and the answer comes back. Nothing stays on our side to read later. A correction that your customer sends with POST /feedback is the one exception, and only when they send it. See the privacy page.
Try it on your rows
The playground reads one narration with no account. The API reference has each request in six languages. To talk about your volume, contact us.
Sign up