Kenya payment troubleshooting

How to review an M-PESA casino payment pending or declined

Use a structured sequence to compare transaction records, separate a delayed status from a reversal or decline, and handle unexpected payment requests cautiously.

Explore M-PESA payments in Kenya

When an M-PESA casino payment pending or declined status appears, payment and support teams should begin by establishing what each available record shows. A pending status, a reported reversal and a decline should be treated as separate cases until the transaction references, amounts, timestamps and account records have been compared.

This guide provides a neutral diagnostic order rather than a conclusion about any individual payment. It does not establish whether funds moved, whether an operator credited an account or whether a reversal is available. Those questions require the relevant transaction records and the applicable M-PESA terms.

Establish the recorded transaction state

Start with the records already available to the payment team and the operator. Identify the transaction reference, amount, displayed status, timestamp and destination details. Keep the original record unchanged, and note when each status was observed.

Compare like with like. A mobile-money transaction record and an operator account entry may use different labels, so record each label exactly rather than assuming that two differently worded statuses mean the same thing. If the records do not align, document the mismatch for investigation instead of immediately initiating another payment.

  • Confirm that the transaction reference being reviewed is the same in every record.
  • Compare the amount and recorded time without altering the original evidence.
  • Record whether each system displays pending, reversed, declined, completed or another label.
  • Check whether the operator record identifies a matching account entry.
  • Avoid treating the absence of an operator credit as proof of a specific payment outcome.

Query and reconcile through established channels

Safaricom's documented Daraja API list includes customer-to-business, business-to-customer, transaction-query and account-balance functions. This means an authorised business team may have distinct records or functions available for receiving payments, sending payments, querying transactions and checking balances.

Use only the channels and permissions already established by the organisations involved. The practical objective is to compare the customer-facing reference with the operator's payment record and any authorised transaction-query result. Do not infer a final outcome merely from the existence of a query function.

  • Match the customer-facing transaction reference to the operator's recorded reference.
  • Compare amounts, timestamps and destination details across authorised records.
  • Record any missing entry, duplicate reference or status mismatch for further review.
  • Do not submit a replacement payment solely because one record has not yet changed.

Check the applicable terms before attempting a reversal

The M-PESA product terms describe procedures and limits for transaction reversals. A reversal should therefore not be presented as automatic or guaranteed. Its handling depends on the applicable terms and the circumstances of the transaction.

Before pursuing that route, establish whether the transaction is recorded as completed, pending, declined or already reversed. Preserve the relevant references and status records so that the request concerns the correct transaction. If the evidence remains inconsistent, the case should stay unresolved rather than being assigned a guessed outcome.

  • Identify the exact transaction before considering a reversal request.
  • Check the applicable M-PESA terms and the circumstances shown in the records.
  • Do not describe a reversal as certain, immediate or available in every case.
  • Keep a record of any status change observed during the review.

Handle unexpected payment requests safely

Safaricom warns customers to keep their M-PESA PIN secret and to verify suspicious requests. It also advises verification with known contacts before money is sent in response to an unexpected request.

If a message, call or prompt is unexpected, pause the payment process and verify the request through a known channel. Do not disclose a PIN, code or credential. Keep the security review separate from the status investigation so that urgency around a pending payment does not override basic verification.

  • Treat unexpected requests for another payment as unverified until checked.
  • Verify the requester through a known contact path.
  • Never share an M-PESA PIN, code or credential.
  • Preserve the suspicious message or request as part of the incident record.
Questions

Frequently asked questions

What should be checked before attempting a reversal?

Confirm the exact transaction reference, amount, timestamp, destination and current recorded status. The M-PESA product terms describe procedures and limits for reversals, so availability should not be assumed; it depends on the applicable terms and transaction circumstances.

How can a suspicious payment request be handled safely?

Pause and verify the request through a known contact path before sending money. Safaricom warns customers to keep their M-PESA PIN secret, verify suspicious requests and check with known contacts when a request is unexpected.

Which records should be compared with the operator?

Compare the transaction reference, amount, timestamp, destination details and displayed status in the available customer and operator records. Safaricom's Daraja API list includes transaction-query and account-balance functions alongside customer-to-business and business-to-customer functions.

Evidence

Primary sources

Last reviewed:

Review the broader M-PESA payment context

Continue to the M-PESA payment-method hub for the surrounding directory structure and related payment information.

Explore M-PESA payments in Kenya