How to Automate iKhokha

iKhokha sells a card machine and hands over a business account

The first thing an iKhokha merchant buys is a card machine: the iK Flyer, the smaller iK Flyer Lite, or iK Tap on Phone, which turns the handset already in a pocket into the reader. iKhokha is a South African fintech, and that reader is the front door to everything else it sells.

What arrives with it is a set of tools that all share a prefix. iK Dashboard holds the sales history, every transaction, the tax invoices and the payouts, with the next payout total on the same screen. iK Invoice creates unlimited digital invoices, each carrying a built-in iK Pay Link so the customer pays from the invoice itself, and iK Pay Link sends the same thing on its own to somebody nowhere near the shop. iK Accounting tracks sales, expenses and cash flow, iK Cash Advance funds stock, and iK Prepaid sells airtime and electricity over the counter for a margin.

The businesses on it are restaurants, retail shops, guesthouses, salons and home-service trades.

The links get sent and then somebody has to chase them

Taking the money is quick. Everything that comes after the tap is slow.

A pay link goes out on a Tuesday and the customer means to pay it. Nobody follows up on Wednesday, and by Friday it is a phone call instead of a click. Add the invoices sitting at thirty days and there is a list nobody is keeping.

The payout side has its own homework. iK Dashboard shows what the machines took and what the next payout should be. The bank shows what landed, net of the rate, on its own cycle. Setting those two beside each other is a person with two tabs open and a calculator.

Then a reader goes flat halfway through a Saturday and nobody notices until a queue forms. A reversal appears and there are days, not weeks, to answer it. Somebody prices the reorder at the wholesaler and reads the reviews.

That is the tax on taking money six different ways, and it gets paid in evenings.

iKhokha

The links nobody followed up on Pay links and invoices still open, sorted by age, with the customer, the amount and a reminder written and left for you to send.

A payout that arrived light, named the same day Yesterday's transactions in iK Dashboard set against what the bank actually credited, while the reference is still findable.

A machine that has taken nothing since ten Trading watched through the day, so a reader that has gone quiet on a busy Saturday is a message rather than a discovery.

iK Accounting already pulls the bank feed in

iKhokha does more for itself than a merchant who only ever uses the card machine would guess.

iK Accounting links a bank account and pulls transactions through automatically, matching them against sales, payouts and business expenses, with reporting written for someone who is not an accountant. That closes the biggest gap on this list before anything else is needed. iK Invoice tracks paid and unpaid, so an outstanding invoice is visible rather than remembered.

Where it stops is where every merchant tool stops. iK Accounting reconciles the accounts it has been connected to. It does not open the wholesaler's ordering page to find that a case of cooldrink went up eleven rand this week, or a delivery platform's back end to add in the orders that never touched an iK Flyer, or the map listing where last night's one-star review is sitting. Every one of those pages belongs to somebody else, and the only key to it is the merchant's own login.

Every unpaid link is a customer who meant to pay

Give something those same logins and the chasing stops being remembered and starts being done.

Pay links and invoices sent and never settled, listed by age, each with a name, an amount and a reminder already written. The ones that need a phone call flagged separately, because a builder four months down is not a WhatsApp problem.

Yesterday's transactions in iK Dashboard set against what the bank actually credited, so a payout that came in light is a query while the reference is still findable. Reversals watched daily instead of found at the deadline, with the receipt, the transaction record and the time stamp gathered before anybody has to argue about them.

The buying side reads the same way. This week's wholesale price, and the rate on your own last order beside it, so a case that costs more than it did last month is caught before you reorder.

And the mechanical one that saves a Saturday: a reader that has taken nothing since ten in the morning, when it normally takes something every twenty minutes.

The chasing is a list, not a talent

The dashboard says one thing, the bank says another, and the difference between them only shows up when the two are put side by side by hand. In a shop this size, the hand is the owner's.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens iK Dashboard, reads yesterday's transactions, invoices and payouts, then opens the bank, a supplier's ordering page, a delivery platform or the review listing, and hands back one short list: who has not paid, what did not clear, what changed, what stopped.

It runs on your schedule in your own private environment, and any run can be watched and stopped. A reminder to a customer, an order to a supplier, a reply to a review or a dispute with a provider is drafted and waits for a person, because each is said in the business's name.

The workflows below are already built, and each one names what it opens.