{"id":139,"date":"2026-11-19T13:00:36","date_gmt":"2026-11-19T10:00:36","guid":{"rendered":"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/"},"modified":"2026-11-19T13:00:36","modified_gmt":"2026-11-19T10:00:36","slug":"mpesa-payment-received-invoice-unpaid-kenya","status":"publish","type":"post","link":"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/","title":{"rendered":"M-Pesa Payment Received but Invoice Still Unpaid: Causes and Fixes"},"content":{"rendered":"<p><strong>If money has reached your business M-Pesa account but the invoice still shows unpaid, the collection and the allocation may have become disconnected.<\/strong> Do not ask the customer to pay again just because your website, POS or rent ledger has not updated. First verify the transaction against an authorised business-side record, then trace how it should reach the invoice.<\/p>\n<p>This guide explains the checks for Kenyan businesses using M-Pesa with websites, billing software, tenant accounts or POS systems. The scenarios are diagnostic examples, not claimed customer results. Available APIs and transaction information depend on your Safaricom account, permissions and integration.<\/p>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_89 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#Start_by_separating_three_different_states\" >Start by separating three different states<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#What_to_check_before_changing_the_invoice\" >What to check before changing the invoice<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#1_The_payment_result_never_reached_your_application\" >1. The payment result never reached your application<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#2_The_callback_arrived_but_processing_failed\" >2. The callback arrived, but processing failed<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#3_The_reference_does_not_identify_the_intended_invoice\" >3. The reference does not identify the intended invoice<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#4_The_payment_is_partial_duplicated_or_posted_elsewhere\" >4. The payment is partial, duplicated or posted elsewhere<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#5_The_ledger_is_correct_but_the_screen_is_stale\" >5. The ledger is correct, but the screen is stale<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#A_worked_example_two_receipts_one_remaining_balance\" >A worked example: two receipts, one remaining balance<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#What_to_ask_an_integration_specialist_to_demonstrate\" >What to ask an integration specialist to demonstrate<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#Frequently_asked_questions\" >Frequently asked questions<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#Should_I_tell_the_customer_to_pay_again\" >Should I tell the customer to pay again?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#Can_I_just_mark_the_invoice_paid_manually\" >Can I just mark the invoice paid manually?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#Will_reconnecting_the_API_recover_all_old_payments\" >Will reconnecting the API recover all old payments?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#Is_this_an_M-Pesa_outage_or_a_software_fault\" >Is this an M-Pesa outage or a software fault?<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#Get_help_tracing_the_payment\" >Get help tracing the payment<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/muki.co.ke\/blog\/mpesa-payment-received-invoice-unpaid-kenya\/#Official_technical_references\" >Official technical references<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Start_by_separating_three_different_states\"><\/span>Start by separating three different states<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ol>\n<li><strong>Payment requested:<\/strong> your software initiated a prompt or displayed payment instructions. This is not proof of payment.<\/li>\n<li><strong>Payment confirmed:<\/strong> an authoritative provider result or verified business account record confirms the receipt.<\/li>\n<li><strong>Payment allocated:<\/strong> the verified receipt has been posted to the correct order, invoice or customer account.<\/li>\n<\/ol>\n<p>An invoice can remain unpaid when step two succeeded but step three did not. A customer-facing \u201csuccess\u201d screen or a screenshot alone should not override the business\u2019s reconciliation controls.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_to_check_before_changing_the_invoice\"><\/span>What to check before changing the invoice<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li>The receiving business account or shortcode: was this payment made to the correct recipient?<\/li>\n<li>The original M-Pesa transaction reference, amount and time from the authorised business-side record.<\/li>\n<li>The intended invoice or account reference and any other payments already allocated to it.<\/li>\n<li>Whether the money was reversed or adjusted, and whether your records reflect that.<\/li>\n<li>Whether the problem affects one payment, one customer or all recent transactions.<\/li>\n<\/ul>\n<p>Do not paste customer statements, API credentials, PINs or full callback payloads into public support channels. Use an agreed secure channel and remove unnecessary personal information from diagnostic examples.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"1_The_payment_result_never_reached_your_application\"><\/span>1. The payment result never reached your application<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A callback endpoint may be unreachable because of a routing change, certificate problem, hosting outage or access rule. The provider can receive the money while your application receives no usable notification.<\/p>\n<p><strong>Check:<\/strong> the configured endpoint, relevant server access logs and application errors around the transaction time. Verify the endpoint and credentials against the current provider setup. A request reaching the server does not prove that your application accepted and saved it.<\/p>\n<p><strong>Fix:<\/strong> restore the endpoint, then reconcile the affected period using an authorised source. Do not assume that historical notifications will automatically be delivered again. If a supported status or transaction API is available to your account, use it according to its documented requirements.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"2_The_callback_arrived_but_processing_failed\"><\/span>2. The callback arrived, but processing failed<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>An application can receive an event and still fail before recording the payment. Examples include a validation mismatch, an unavailable database, a stopped worker or an exception while finding the related order. These are possibilities to investigate, not a diagnosis based only on the invoice status.<\/p>\n<p><strong>Check:<\/strong> the provider reference in application logs, queued or failed jobs if your implementation uses them, and the saved payment record. Redact sensitive fields when sharing logs.<\/p>\n<p><strong>Fix:<\/strong> correct the processing fault before replaying anything. Any reprocessing path must prevent the same confirmed receipt from being posted twice. Preserve the original reference and an audit trail of the recovery action.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"3_The_reference_does_not_identify_the_intended_invoice\"><\/span>3. The reference does not identify the intended invoice<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A customer may enter the wrong account number, pay for several invoices together or use a payment method whose reference differs from your normal checkout flow. Matching only by amount can allocate money to the wrong person, especially when many customers owe the same rent or fee.<\/p>\n<p><strong>Check:<\/strong> the receipt against the customer account, invoice history and approved supporting information. Establish whether the reference is missing, mistyped or mapped to a different account.<\/p>\n<p><strong>Fix:<\/strong> send ambiguous payments to a review queue. An authorised reviewer should record why an allocation was made. Do not silently replace a reference or mark a sale paid merely because the amount looks plausible.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"4_The_payment_is_partial_duplicated_or_posted_elsewhere\"><\/span>4. The payment is partial, duplicated or posted elsewhere<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Receiving some money does not necessarily settle the invoice. A receipt may cover only part of the balance, have been allocated to an earlier charge or already exist under a different record. Duplicate imports can also make the payment list and ledger disagree.<\/p>\n<p><strong>Check:<\/strong> all allocations for the original transaction reference, not just the latest invoice screen. Compare the invoice total, existing credits and remaining balance. Confirm whether business rules permit splitting one receipt across several charges.<\/p>\n<p><strong>Fix:<\/strong> use the application\u2019s controlled allocation or adjustment process. Do not create a second cash receipt to make the screen balance. Corrections should preserve who acted, the source receipt and the reason.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"5_The_ledger_is_correct_but_the_screen_is_stale\"><\/span>5. The ledger is correct, but the screen is stale<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Sometimes the payment and allocation are saved correctly while a dashboard, cached response or report has not refreshed. This is different from missing money or a failed callback.<\/p>\n<p><strong>Check:<\/strong> the authoritative account history and receipt record. Compare them with the affected screen. Refreshing the browser is a diagnostic step, not a financial correction.<\/p>\n<p><strong>Fix:<\/strong> repair the update or reporting path. Do not alter financial records just to force a visual refresh.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"A_worked_example_two_receipts_one_remaining_balance\"><\/span>A worked example: two receipts, one remaining balance<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In this fictional example, invoice INV-1042 totals KSh 12,000. The first verified receipt is KSh 7,000 and is correctly allocated, leaving KSh 5,000. A second verified receipt of KSh 5,000 arrives with the wrong reference.<\/p>\n<p>The second receipt should remain visible as unallocated while the invoice remains open. After an authorised reviewer confirms the intended invoice, that existing receipt is allocated to INV-1042. The invoice then shows KSh 12,000 settled through two distinct receipts. Importing the second transaction again must not create a third receipt.<\/p>\n<p>This example illustrates the difference between receiving, recording and allocating a payment. It is not evidence that every system supports the same review controls.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"What_to_ask_an_integration_specialist_to_demonstrate\"><\/span>What to ask an integration specialist to demonstrate<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ol>\n<li>A successful payment linked to its intended invoice.<\/li>\n<li>A cancelled or failed request that does not mark the invoice paid.<\/li>\n<li>A repeated notification or import that does not duplicate the receipt.<\/li>\n<li>A missing or incorrect reference that remains available for review.<\/li>\n<li>A partial payment and any approved handling for reversals or corrections.<\/li>\n<li>A reconciliation report whose totals can be traced to the original records.<\/li>\n<\/ol>\n<p>For product-based evidence, see the <a href=\"https:\/\/muki.co.ke\/case-studies\/rentaldesk-rent-payment-workflow\">RentalDesk rent and payment workflow<\/a> and the <a href=\"https:\/\/muki.co.ke\/case-studies\/vega-pos-payment-stock-workflow\">Vega POS checkout and payment workflow<\/a>. Both articles state what their public evidence does and does not establish.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Frequently_asked_questions\"><\/span>Frequently asked questions<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<h3><span class=\"ez-toc-section\" id=\"Should_I_tell_the_customer_to_pay_again\"><\/span>Should I tell the customer to pay again?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Not solely because the invoice is still open. First verify whether the original payment reached the correct business account. A second payment could create an overpayment while leaving the original integration problem unresolved.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Can_I_just_mark_the_invoice_paid_manually\"><\/span>Can I just mark the invoice paid manually?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Only through an authorised process based on a verified receipt and your accounting controls. A status change with no underlying allocation can leave balances, receipts and reports inconsistent.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Will_reconnecting_the_API_recover_all_old_payments\"><\/span>Will reconnecting the API recover all old payments?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Not necessarily. Historical availability, account permissions and the chosen API or statement source determine what can be recovered. Agree the date range and reconciliation method before promising a backfill.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Is_this_an_M-Pesa_outage_or_a_software_fault\"><\/span>Is this an M-Pesa outage or a software fault?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>The invoice screen alone cannot establish that. Trace the transaction from the receiving account to the application record, allocation and displayed balance to identify where the two systems diverge.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Get_help_tracing_the_payment\"><\/span>Get help tracing the payment<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>For an existing ledger mismatch, start with <a href=\"https:\/\/muki.co.ke\/mpesa-reconciliation-kenya\">M-Pesa payment reconciliation<\/a>. For a broken checkout or callback implementation, review <a href=\"https:\/\/muki.co.ke\/mpesa-integration-kenya\">M-Pesa API integration<\/a>. If records need to move between several applications, see <a href=\"https:\/\/muki.co.ke\/business-systems-integration-kenya\">business systems integration<\/a>.<\/p>\n<p><a href=\"https:\/\/wa.me\/254725345345?text=Hi%20Muki%2C%20a%20verified%20M-Pesa%20payment%20has%20not%20updated%20our%20invoice.%20Can%20we%20arrange%20a%20reconciliation%20review%3F\" target=\"_blank\" rel=\"noopener\">Request a scoped reconciliation review<\/a>. Describe the software, the date range and the failure pattern first; do not send credentials or private transaction records in the initial message.<\/p>\n<h2><span class=\"ez-toc-section\" id=\"Official_technical_references\"><\/span>Official technical references<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<ul>\n<li><a href=\"https:\/\/developer.safaricom.co.ke\/\" target=\"_blank\" rel=\"noopener\">Safaricom Daraja developer portal<\/a><\/li>\n<li><a href=\"https:\/\/developer.safaricom.co.ke\/apis\/PullTransaction\" target=\"_blank\" rel=\"noopener\">Safaricom Pull Transactions API<\/a> \u2014 access and requirements must be confirmed for your account.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>M-Pesa payment received but the invoice is still unpaid? Trace callbacks, references, duplicate receipts and allocation safely before asking a customer to pay again.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-139","post","type-post","status-publish","format-standard","hentry","category-software-development"],"_links":{"self":[{"href":"https:\/\/muki.co.ke\/blog\/wp-json\/wp\/v2\/posts\/139","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/muki.co.ke\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/muki.co.ke\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/muki.co.ke\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/muki.co.ke\/blog\/wp-json\/wp\/v2\/comments?post=139"}],"version-history":[{"count":0,"href":"https:\/\/muki.co.ke\/blog\/wp-json\/wp\/v2\/posts\/139\/revisions"}],"wp:attachment":[{"href":"https:\/\/muki.co.ke\/blog\/wp-json\/wp\/v2\/media?parent=139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/muki.co.ke\/blog\/wp-json\/wp\/v2\/categories?post=139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/muki.co.ke\/blog\/wp-json\/wp\/v2\/tags?post=139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}