What does M-Pesa error 1032 mean?

Result code 1032 means the customer received the STK Push prompt but pressed Cancel instead of entering their PIN. Offer a friendly retry.

What does M-Pesa error 1037 mean?

Result code 1037 is a timeout — the STK prompt could not reach the phone or the customer did not respond in time (phone off or poor coverage). Ask them to retry.

What does M-Pesa error 2001 mean?

Result code 2001 means authorization failed because the customer entered the wrong M-Pesa PIN (or the initiator credentials were invalid).

Reference

M-Pesa and Daraja error codes, decoded

.md

Every Safaricom M-Pesa result code and Daraja API error decoded — cause, fix, and a customer-facing message. Searchable.

M-Pesa reports a problem as a number and gives almost no other information. resultCode: 1037 is an example. That number means nothing until you decode it.

This page decodes every result code. For each code it gives the meaning, the cause, whether a retry can help, and the message for the customer.

How to read a failure

A failed payment gives you two fields. The two fields come from two different places:

Field	Where it comes from
HTTP status	paylod. `401` wrong API key, `422` wrong body, `502` Daraja refused the request. See API errors.
`resultCode` / `resultDesc`	M-Pesa. The customer cancelled the prompt, or the PIN was wrong, or the handset was off. This page decodes these codes below.

A 202 and then resultCode: 1032 is not a bug. The push worked, and the customer pressed Cancel.

You do not have to implement this table

The Node SDK decodes result codes offline. It makes no network call. It needs no API key at call time.

decode.ts

import { decodeError } from "@paylod/node";

const err = decodeError(1032);

err.title;            // "Payment cancelled by the customer"
err.category;         // "customer"
err.retryable;        // true
err.customerMessage;  // "Payment cancelled — you can try again whenever you're ready."

On a failed payment, collectAndWait() returns the same object as outcome.detail. A payment.failed webhook carries the same object as event.data.decoded. The two objects are byte-for-byte identical. The message that you show to a customer is therefore the same for every integration. The SDK also exports the whole catalogue as ERROR_CATALOG.

Most integrations do not need the raw catalogue. outcome.message is the decoded sentence for the customer. outcome.retryable tells you whether a second charge is safe. Use the catalogue below for your records, for your dashboards, and for debug work during an incident.

The CLI decodes the same catalogue in your terminal. Run paylod errors 1032. This command is the fastest way to read the meaning of a code during an incident.

Do not show a failure for the codes `4999` and `500.001.1001`. These two codes mean pending, not failed. Daraja returns them while the customer still looks at the PIN prompt. They decode with category: "pending" and retryable: false. Here retryable: false does not mean that a retry is pointless. It means that the first prompt is still live, and a second push can double-charge the customer. Do not collect again on these two codes. Continue to poll the status. The SDK polls for you.

The most common codes

Code	Meaning	What to do
`0`	Success.	Fulfil the order, but first check the settled `amount`.
`1032`	The customer pressed Cancel on the prompt.	Offer the customer a retry. This code is not an error in your code.
`1037`	Timeout. The prompt did not reach the handset, or the customer ignored it.	Retry. The handset was off, or out of coverage, or the customer did not answer.
`2001`	Wrong M-Pesa PIN.	Ask the customer to try again.
`1`	Insufficient balance.	Tell the customer that the M-Pesa balance is too low.
`4999`	Not a failure. The customer did not enter the PIN yet.	Continue to poll. Never collect again: the prompt is still live, and a second push can double-charge the customer.

The catalogue below contains every other code. It contains every Daraja API error, every C2B result code and every B2C result code. You can search it.

Full catalogue

Error codes

Search Safaricom's M-Pesa result and error codes by number or description. Every failed payment in Payments is decoded with the same reference.

32 codes

0STK resultSuccessNot retryable

Success

The STK Push transaction completed and the customer's payment was received successfully.

Fix

Treat the transaction as paid, read the receipt from CallbackMetadata, and fulfil the order.