On the device
The sale is recorded locally.
Ringing up a sale, recording the amount and payment method, and printing or reprinting the receipt happen in the local database — whether or not the internet is up.
Loading…
Analytics
Can we measure anonymous page visits? It shows us which pages help people choose Omnix. Nothing personal is sent, and the analytics script loads only if you accept.
M-Pesa · Kenya
Omnix supports STK push, paybill, and till payments at the till. The sale itself is written to the local record whether you are online or off; the M-Pesa request to Safaricom is a connected step that needs the internet and your own business account.
How it works
However the customer chooses to pay, Omnix keeps the sale in the same local ledger. Only the confirmation of the M-Pesa payment depends on a connection.
The till sends a payment prompt to the customer’s phone number, and the customer approves it on their own handset. The prompt has to reach Safaricom and the phone, so this step needs a connection at the moment of payment.
Customers pay your paybill against an account reference, often the invoice number. The sale is already in Omnix; matching it to the incoming payment relies on the confirmation arriving over the connection.
Customers pay your till number and share the M-Pesa code. The code can be recorded against the open sale so the local record is complete even before online confirmation is reconciled.
M-Pesa payments are matched to Omnix sales by reference. Pulling and comparing confirmations against your own M-Pesa records is a connected step; the underlying sales remain in the local database regardless.
Responsibility ledger
M-Pesa spans your device, Safaricom’s network, and your own accounts. This ledger keeps those responsibilities separate so there are no surprises.
On the device
Ringing up a sale, recording the amount and payment method, and printing or reprinting the receipt happen in the local database — whether or not the internet is up.
Needs a connection
STK push, and confirmation of a paybill or till payment, require internet access at the moment of payment so the request can reach Safaricom and the customer’s phone.
Your configuration
M-Pesa collection runs against your own Safaricom Daraja business account — paybill or till — set up with valid credentials. Omnix connects to that account; it does not provide the M-Pesa account for you.
Safaricom & KRA
Transaction charges are set by Safaricom and billed directly to your business; Omnix takes no margin on M-Pesa. The tax treatment of each sale, and any eTIMS receipt, remain your statutory responsibility.
When the line is down
A dropped connection stops the online request, not the sale.
If the internet is down at the moment of payment, the STK push cannot be sent. The sale is still recorded in Omnix, and where a customer has paid by till or paybill and can share the M-Pesa code, that code can be entered against the sale so the local record is complete.
When a connection returns, M-Pesa confirmations can be reconciled against your Omnix sales, and any KRA eTIMS receipt that could not be submitted earlier can be retried. Omnix does not promise a fixed reconciliation time; it keeps the local record intact so the connected steps can catch up.
See it at your till