Skip to content
CodeWave Systems

Payment Verification & Business Operations

MVerify Know when the payment arrives.

MVerify is a payment verification and operational platform designed to help businesses confirm and monitor M-Pesa transactions — and to connect that confirmation to what happens next at the counter, on the floor and across branches.

Request a DemoTalk to Our Team
Platforms
Android app · Web dashboard
Payment rails
Till · PayBill · STK Push
Built for
Counters, branches, field staff
Technology
Laravel · Android · MySQL

01 · The problem

“Has the money come in?”

Most businesses that take M-Pesa answer that question with a glance at a customer's phone, a shout across the counter, or a message to whoever owns the line the confirmation lands on.

None of those leave a record the business can use afterwards. MVerify is designed for operations where that moment happens dozens or hundreds of times a day — and where being wrong costs stock, time or trust.

Confirmation by screenshot

Staff are asked to trust a message on a customer's screen — which is exactly what a forged or edited confirmation relies on.

One phone holds the answer

The confirmation reaches the owner or one manager, so everyone else waits for a reply before releasing goods.

The queue pays for the delay

Verifying by hand slows the counter at the busiest hour, when the cost of a mistake is highest.

No view across branches

Each till knows its own morning. Nobody sees the whole operation without collecting statements outlet by outlet.

No usable record afterwards

A verbal "it came through" cannot be searched, tied to a branch and a staff member, or reviewed a week later.

Reconciliation after hours

Matching a statement against what was actually released becomes an evening job instead of a by-product of the work.

02 · Who it is for

Businesses where payment and hand-over happen in the same minute.

MVerify is designed for operations that take M-Pesa at a counter, a table or a doorstep — where goods or services move as soon as the payment is confirmed.

Retail counters and shops

Supermarkets, hardware, agrovet, electronics and general retail, where a queue forms behind every unverified payment.

  • Till
  • Multiple cashiers

Pharmacies and clinics

Front desks that confirm payment before dispensing, with a record tied back to the branch and the attendant.

  • PayBill
  • Front desk

Restaurants, bars and cafés

Waiters and cashiers confirming payments at the table, with the manager able to see every settled bill.

  • Floor staff
  • Shifts

Delivery and field collection

Riders, sales agents and field staff who collect payment away from the shop and need confirmation on the spot.

  • Android app
  • Field

Multi-branch businesses

Operations with several tills or outlets that need one view across all of them rather than one statement per branch.

  • Branches
  • Roles

Service businesses

Workshops, salons, schools, lodges and similar operations where service is released against a confirmed payment.

  • STK Push
  • Records

03 · How it works

From the customer's phone to the manager's dashboard.

One transaction, followed the whole way: received, matched, confirmed by the person serving the customer, and kept as a record the business can use.

  1. 01

    Customer makes payment

    The customer pays the business Till or PayBill, at the counter or wherever the sale happens.

    Customer

  2. 02

    M-Pesa transaction

    The payment completes on the M-Pesa side and carries the details of what was paid.

    M-Pesa

  3. 03

    MVerify receives it

    Transaction information reaches the platform and is processed for the business it belongs to.

    MVerify

  4. 04

    Transaction is matched

    The payment is identified against the business, the branch and the till it came through.

    MVerify

  5. 05

    Staff receive it

    Authorised staff see the transaction in the app or dashboard for the branch they work in.

    Staff app

  6. 06

    Staff verify the payment

    The person serving the customer confirms the payment and releases the goods or service.

    Counter

  7. 07

    The business records it

    The confirmation is stored with the transaction, the branch and the staff member who handled it.

    Record

  8. 08

    Management monitors

    Owners and managers follow transactions across branches, staff and time from one dashboard.

    Dashboard

Built for the counter

Confirmation is designed to be a few seconds of work for the person already serving the customer.

Scoped by role

What a staff member can see and confirm follows the branch they belong to and the role they were given.

One record per payment

Transaction, branch, staff member and confirmation stay together in transaction history.

04 · Core workflow

Two ways a payment reaches the counter.

Some customers pay before anyone asks. Others need to be prompted. MVerify is designed to handle both without the staff member changing what they do next.

Path A

The customer has already paid

The customer pays the Till or PayBill themselves. The transaction reaches MVerify, the staff member finds it, confirms it, and the sale continues.

  1. 1 Customer pays the business Till or PayBill.
  2. 2 The transaction reaches MVerify and is matched to the business and branch.
  3. 3 The staff member opens their branch list in the app or dashboard.
  4. 4 They confirm the payment against what the customer is buying.
  5. 5 The confirmation is stored with the staff member and the branch.

Path B

The business requests the payment

Instead of dictating a Till number and an amount, the staff member sends an STK Push to the customer's phone. The customer approves it there, and the resulting transaction is handled exactly like any other.

  1. 1 Staff enter the customer number and the amount.
  2. 2 An STK Push prompt reaches the customer's phone.
  3. 3 The customer approves the payment with their PIN.
  4. 4 The resulting transaction reaches MVerify and is matched.
  5. 5 Staff see the confirmed payment without retyping anything.

Fewer mistyped Till numbers — and fewer payments sent to the wrong business — are the practical reason most operations reach for the second path once they have it.

05 · Key features

What the platform covers.

Capability areas described in business terms — what each one does for the people running the operation.

M-Pesa payment verification

Payments are confirmed against transaction information held by the business, not against a message on a customer's phone.

Till and PayBill monitoring

Transactions received through the business Till and PayBill are monitored in one place as they arrive.

STK Push

Staff can prompt a customer's phone for payment instead of dictating a number and an amount.

Staff Android application

A focused app for the people confirming payments away from a desk — counter, table, gate or delivery.

Web dashboard

Owners and managers work from the browser: transactions, branches, staff and history in one view.

Business accounts

Each business operates in its own account, with its own tills, staff, branches and history.

Branches

Outlets and tills are modelled as branches, so activity can be read per branch or across the whole business.

User roles

Owners, managers and staff get different levels of access; permissions follow the role rather than the person's phone.

Transaction history

Every transaction and confirmation stays searchable with its branch, staff member and time.

Billing

Subscription and billing are part of the platform, so account status is managed inside the system rather than beside it.

Operational monitoring

Managers can watch activity as it happens rather than reconstructing the day after it has ended.

Controlled access

Access is authenticated per user, scoped by role and branch, and actions are recorded against the account that took them.

06 · Roles and users

Four people, one transaction, different jobs.

Access follows the role. The cashier sees the work in front of them; the owner sees the operation.

Business Owner

Runs the business and carries the risk when a payment is wrongly confirmed.

In MVerify

  • Sees transactions across every branch
  • Adds branches, staff and roles
  • Reviews history over time
  • Manages the account and billing

Manager

Responsible for a branch or a shift, and for the people working it.

In MVerify

  • Monitors transactions for their branch
  • Follows staff activity during a shift
  • Checks confirmations and history
  • Handles what the counter escalates

Cashier

Takes payment at the till, usually with a queue waiting.

In MVerify

  • Confirms payments at the counter
  • Requests payment with STK Push
  • Works within their assigned branch
  • Uses the app or the dashboard

Waiter / field staff

Serves customers away from the till — a table, a gate, a delivery.

In MVerify

  • Confirms payment where the customer is
  • Works from the Android application
  • Sees only what their role allows
  • Leaves a record against their own account

07 · Interface

What the people using it actually see.

Illustrations of the interface, drawn for this page. Amounts and transaction codes are deliberately masked — these show structure, not real business activity.

Web dashboard — interface illustration
Branch and staff activity — interface illustration

On the staff phone

The Android application keeps the same transaction in front of the person serving the customer: find it, confirm it, or request it with STK Push. It is deliberately narrow — one job, done quickly, with a queue waiting.

08 · Integrations

Connected to the rails the business already uses.

MVerify sits between M-Pesa and the people who have to act on a payment. Anything beyond that is integration work CodeWave scopes per business.

Discuss an integration

M-Pesa Daraja

In the platform

Till and PayBill transactions and STK Push requests, handled through Safaricom's Daraja API together with the callbacks and retries that go with them.

Android devices

In the platform

The staff application runs on the phones the team already carries — no dedicated hardware at the counter.

Web dashboard

In the platform

Any modern browser; managers and owners install nothing.

POS, ERP and accounting

Scoped per business

Where a business runs its own system, verified transactions can be passed to it through an integration designed for that system.

Notifications

Where configured

Alerting staff or managers to transactions that need attention can be configured as part of an engagement.

09 · Business benefits

What changes once payments are verified in one place.

Practical outcomes the platform is designed to produce — described without figures, because the figures belong to your operation rather than to a marketing page.

A faster counter

The person serving the customer can confirm a payment themselves instead of waiting for someone else to check a phone.

Fewer disputed payments

Confirmation is made against transaction information the business holds, which takes the argument off the customer's screen.

Accountability by name

Every confirmation carries the staff member and branch behind it, so a question has a place to start.

Visibility across branches

Owners look at every outlet from one account instead of chasing one statement per till.

A record that survives

Transaction history stays searchable long after the shift ends — for reconciliation, review or a customer query.

Reconciliation as a habit

Matching what was received against what was released becomes part of the day rather than an evening exercise.

10 · Technology

Engineered as a product, not a script.

MVerify is built on the stack CodeWave uses for systems that have to keep running: a Laravel application and API, a relational data model behind it, and an Android client for the people at the counter.

Laravel Android MySQL M-Pesa Daraja REST APIs

Hosting details, environment configuration and integration credentials stay private to each deployment and are not published here.

Architecture at a conceptual level

11 · FAQ

MVerify questions.

Something not covered here? Ask us directly — the answer usually depends on how your counter works today.

Talk to Our Team

Prefer the engineering story? Read the MVerify case study.

What does MVerify actually verify?

MVerify is built around the M-Pesa transactions a business receives through its Till or PayBill. Rather than staff reading a customer's SMS or screenshot, the transaction reaches the platform and is matched to the business and branch it belongs to, so the person at the counter is confirming a record the business itself holds.

Do staff need the Android application?

The Android application is designed for the people who confirm payments away from a desk — a cashier, a waiter, a delivery rider, an attendant. Managers and owners can work from the web dashboard instead. Both look at the same transactions; what differs is what each role is allowed to see and do.

Can MVerify request a payment instead of waiting for one?

Yes. STK Push is part of the platform, so a staff member can prompt the customer's phone for the payment instead of dictating a Till number and an amount. The transaction that comes back is handled the same way as any other: received, matched, confirmed and recorded.

Does it work for a business with several branches?

Businesses, branches and user roles are part of the data model. A cashier works within the branch they are assigned to, a manager follows that branch, and the owner can look across all of them from one account.

Does MVerify replace our point-of-sale or accounting system?

No. MVerify is focused on the moment a payment is confirmed and the record that moment leaves behind. Where a business already runs a POS, ERP or accounting package, CodeWave can design an integration so verified transactions reach it — that work is scoped per business rather than shipped as a switch you turn on.

What is needed to get started?

A business with an M-Pesa Till or PayBill, the staff who will use it, and a short conversation about how payments are confirmed today. CodeWave handles setup, the M-Pesa side of the integration and staff onboarding.

Is MVerify only for businesses in Kenya?

The platform is built around M-Pesa, so it fits Kenyan businesses first. For operations in other markets, CodeWave builds the equivalent verification workflow around the payment rails available there — talk to us about the market you operate in.

More from CodeWave

Explore more CodeWave products

All products

Business Management

POS & ERP Systems

One system from the till to the back office.

  • POS and sales
  • Inventory
  • Customers and suppliers
Explore POS & ERP Systems

FinTech / Payments

Wallet & Payment Platforms

Payment systems engineered around the money, not around the demo.

  • M-Pesa and STK Push
  • Stripe and PayPal
  • Transaction workflows
Explore Wallet & Payment Platforms

Property Management

Rental Management Platform

Every property, unit, tenant and payment in one place.

  • Properties, units and tenants
  • Rent and invoicing
  • M-Pesa payments
Explore Rental Management Platform

Request a demo

See MVerify against the way your counter works today.

Tell us how payments are confirmed in your business right now. We will show you what the same moment looks like in MVerify — and what it would take to get there.

Request a DemoTalk to Our Team
info@codewavesystems.co.ke +254 708 604 940