Banking integrations for retail POS: cards, mobile money, bank transfers and reconciliation
How retail POS connects to cards, M-Pesa, Airtel Money and bank settlements, why integrated payments beat standalone terminals, and how to reconcile.
Why payments integration deserves attention
A shopper does not care how a payment moves. Finance does. Every shilling a customer pays must be traceable from the lane to the bank, through the provider that processed it, with the right sale attached. When payment systems are bolted on to the till rather than integrated, errors creep in: the cashier types the wrong amount into a card terminal, a mobile money payment is not matched to a sale or a day's settlement does not agree with the day's sales.
In multi-branch retail the cost multiplies. Finance teams spend days chasing differences across dozens of tills and providers. Good integration moves that work from people to the system.
The payment methods retailers deal with
In Kenya and neighbouring markets, a typical retailer accepts several methods in the same lane:
- Cash, which still carries a large share of volume in many stores
- Cards from the major schemes, through bank or aggregator terminals
- Mobile money, such as M-Pesa and Airtel Money, in several forms
- Bank transfers, including instant interbank rails such as PesaLink
- Vouchers, gift cards, loyalty points and instalment plans issued by the retailer
- Split tender, where one sale is paid with a mix of the above
Shoppers expect to choose, so the POS must handle all of them in one transaction without confusion.
How mobile money integrates
Mobile money flows come in two broad shapes.
Prompt to the customer's phone (STK Push). The till sends the amount and phone number to the provider, which prompts the customer to approve on their handset. The POS then waits for a confirmation callback. This flow is fast and accurate because the amount comes from the sale, not from the customer typing it.
Customer-initiated payment (C2B). The customer pays to a till number or paybill using a reference, and the provider sends a confirmation to the retailer. The POS must match that confirmation to the right sale, usually by amount, phone number or reference. This flow is flexible but needs good matching rules and a place to handle payments that arrive without a clear sale.
Both flows need care around timeouts, duplicate prompts and late confirmations, covered below.
Integrated terminals versus standalone devices
| Integrated terminal | Standalone terminal | |
|---|---|---|
| Amount entry | Sent automatically from the sale | Typed by the cashier |
| Receipt and tender record | Linked to the sale | Matched afterwards, by hand |
| Error risk | Low | Wrong amounts and missed entries |
| Speed at the lane | Faster | Slower |
| Reconciliation | Automatic matching possible | Manual |
| Card data on the POS | Stays on the terminal | Not applicable |
Integrated terminals also help with security. When card details stay on the terminal and never pass through the POS software, the retailer's exposure is much smaller.
Reconciliation: the three-way match
Good reconciliation compares three records for every tender type.
- The POS record. What each till says was paid, by method.
- The provider's settlement. What the card acquirer, aggregator or mobile money operator says it processed, including fees.
- The bank statement. What actually arrived in your account, and when.
Differences are normal. The goal is to explain every one quickly. Common causes include:
- Payments in progress when the day closed
- Failed or abandoned prompts that were never completed
- Duplicate payments or reversals
- Provider fees and timing differences between the sale and the settlement
- Chargebacks and disputes on card payments
- Payments received with the wrong reference
Reconcile daily and work from an exceptions list, not from every transaction. Matching the easy ninety per cent automatically leaves your team to investigate only the differences.
Plan for failure modes
- No network. Mobile money prompts and card terminals depend on connectivity. Decide what the lane does: fall back to cash, retry, or offer another method. Cash sales should continue regardless. See offline-first retail systems.
- Timeouts and double prompts. If a customer does not respond, the cashier must be able to cancel or retry without charging twice.
- Late confirmations. A confirmation can arrive after the cashier has moved on. The system needs a way to apply it to the right sale or flag it.
- Idempotency. Retried messages must never post the same payment twice.
- Refunds. Returns must reverse the correct tender and be approved and logged.
Choosing providers and gateways
When you compare acquirers, aggregators and mobile money options, look beyond the headline fee.
- Settlement speed and consistency
- Uptime and support responsiveness, especially at peak times
- Quality of the integration interface and of the test environment
- Reporting that finance can reconcile from, such as settlement files
- Ability to handle many branches, tills and bank accounts
- Fees on refunds, reversals and chargebacks
Most multi-branch retailers end up with more than one provider, which makes a central payments view even more valuable.
Treasury and cash handling
Payments integration is not only digital. Cash still needs counting, banking and recording. Look for till close processes that record each tender, the variance and the cashier, and a reconciliation of bank deposits to the cash recorded at the till. Cash and digital reconciliations should feed the same end-of-day record so finance sees one picture.
A checklist for retailers and investors
- Does every tender type attach to the sale automatically?
- Can a cashier enter an amount that differs from the sale total?
- How are unmatched mobile money payments handled?
- How long does daily reconciliation take, and who does it?
- Is there an exceptions dashboard across all branches?
- What happens at the lane when the network drops?
- How are refunds and reversals approved and logged?