Use a unique account reference and verify the recipient name on the confirmation screen before you send any money; if the name doesn’t match your target service, cancel the transaction and recheck the number. Save the official billing number from the provider’s website and avoid numbers received via chats, forwarded SMS, or screenshots.

Before transferring, lock down access: enable a SIM PIN, set a phone screen lock, and keep your M-Pesa PIN private. For high-value transfers, split the amount into two smaller sends and confirm the first one posts correctly; this reduces loss if you mistype a digit or select the wrong entry from saved contacts.

During the transfer, type the business number manually, confirm the account/reference field character by character, then review the fee and total amount shown in the preview screen. After completion, keep the SMS receipt (transaction ID, amount, date/time) and reconcile it with your wallet statement; for known merchants such as betika paybill, match the reference format they specify to avoid unallocated funds.

If a transaction doesn’t reflect within the expected window, do not resend immediately. First check the message status, your wallet balance, and the statement entry; if there’s a mismatch, contact the merchant support with the transaction ID and masked phone number, and escalate to Safaricom support only after you have those details recorded.

Verify the Paybill Number, Account Reference, and Recipient Details Before Sending

Type the business number manually from the official invoice, contract, or the recipient’s verified website, then compare it against at least one second source (SMS reply thread, printed receipt, or a signed email footer). Recheck the account reference character-by-character: a single swapped digit can route the credit to the wrong ledger and delay service activation. Confirm the recipient name shown on the confirmation screen matches the exact organization you intend to fund; if the displayed name is abbreviated, request the full registered name and cross-check it with the invoice header.

Use this quick pre-send checklist:

• Business number: confirm length and spacing; don’t trust numbers copied from social posts or forwarded chats.
• Account reference: verify required prefixes (e.g., INV-2026-0149, ADM10293) and case sensitivity if your provider enforces it.
• Recipient identity: match the on-screen recipient label to the invoice payee; if it differs, cancel and call a known phone number from the invoice (not the message that shared the number).
• Amount sanity check: compare to the invoice total; if partial payment is allowed, include the installment code in the reference.

Complete the Mobile Money Deposit Workflow: Amount Entry, PIN Confirmation, and Transaction Review

Enter the amount manually rather than using quick presets, then verify the currency symbol and decimal placement (e.g., 1,500.00 vs 15,000.00) before tapping “Continue.” If fees are shown, add them into your total so the recipient receives the intended value; if fees are not displayed, assume a small charge and avoid sending your full available balance to prevent an “insufficient funds” failure.

On the PIN screen, pause and check that the phone’s keypad is the official in-app keypad (not a floating third‑party overlay). Type the PIN once, confirm that no extra digits appear, and never share it over calls, chat, or USSD prompts that ask for it twice. If you mistype, cancel and re-enter instead of repeatedly guessing–multiple failed attempts can trigger a lockout that delays funding.

Review the transaction summary line by line: recipient name or business label, account/reference string, amount, service charge, and the final total to be deducted. Compare the reference against your source document (invoice, meter number, subscription ID) character by character; a single transposed digit can route funds incorrectly and make reversal unlikely. If the recipient field shows only a short code without a name, back out and reselect the destination so you get a populated identity label.

Submit only after the confirmation screen matches your intent, then wait for the success message and store the receipt ID (copy to notes or screenshot). If you see “pending,” do not retry immediately–check your balance and transaction history first, and allow 2–5 minutes for settlement to avoid duplicate transfers.

Confirm Success and Handle Problems: SMS Receipt Checks, Reversals, and Support Tickets

Verify completion by matching the SMS receipt to your transaction details: confirm the reference code, the credited amount, the service number, and the account/ID you entered; then screenshot the message and save it for at least 30 days. If you don’t receive an SMS within 2–5 minutes, check your handset inbox filters/spam, ensure the SIM has network signal, and review the in-app “Recent transactions” log for a posted status before trying again.

If the money left your wallet but the biller account is not credited, wait 10–30 minutes (some processors post in batches), then compare timestamps: the SMS time, the wallet ledger time, and any confirmation shown on the biller side. A mismatch usually points to a delayed posting rather than a failed payment. Do not repeat the payment while the first one shows “Processing/Queued”; repeated attempts often create duplicates that require manual reconciliation.

Request a reversal only when you can show one of these: wrong service number, wrong account/ID, or double payment. Use the receipt reference code and exact amount; note the recipient details as entered, plus your phone number and transaction time. Reversals are commonly rejected if funds already settled to the merchant; in that case, ask the merchant to refund using their own back-office tools and provide their refund confirmation alongside your receipt.

For a support ticket, include: receipt/reference code, amount, date/time (with time zone), service number, account/ID, your phone number, screenshots of the SMS and wallet history, and a short problem label (“no confirmation SMS”, “debited/not credited”, “paid wrong account”, “duplicate charge”). Submit through the operator’s help channel or app chat, keep the ticket ID, and follow up after 24 hours if no update; avoid sharing PINs or one-time codes in any message.