No response received at callback url endpoint

Question

No response received at callback url endpoint

Closed this issue 6 years ago · 18 comments

Hi, everything is working perfectly well with the api on the android side but the callback endpoint at the server is not receiving any response. Please help

Answer 1 · 2018-04-02T21:35:00.000Z

@Aleqi any luck with this? I having the same problem

Answer 2 · 2018-04-03T06:40:15.000Z

@Aleqi @nellycheboi12 You need to define your own callback URL inorder to receive the callbacks. Use this tutorial on how you can use firebase and PHP for that https://www.androidhive.info/2012/10/android-push-notifications-using-google-cloud-messaging-gcm

Answer 3 · 2018-04-03T07:57:17.000Z

I have already defined my own callback and previously it was working perfectly. But since Thursday 29th March, 2018 last week there is no response being received at my callback endpoint from mpesa server.

…

On Tue, Apr 3, 2018 at 9:40 AM, Brian Kisese ***@***.***> wrote: @Aleqi <https://github.com/Aleqi> @nellycheboi12 <https://github.com/nellycheboi12> You need to define your own callback URL inorder to receive the callbacks. Use this tutorial on how you can use firebase and PHP for that https://www.androidhive.info/ 2012/10/android-push-notifications-using-google-cloud-messaging-gcm — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AP3rWEZT02-IQVw-PZFpbXf7TgngVkxhks5tkxlUgaJpZM4TC7c6> .

Answer 4 · 2018-04-03T08:10:03.000Z

@nellycheboi12 No luck yet

Answer 5 · 2018-04-04T09:11:02.000Z

Finally it's working. I can get response at the callback endpoint. It was a bug on the api developers side.

…

On Tue, Apr 3, 2018 at 10:57 AM, Alex Kamande ***@***.***> wrote: I have already defined my own callback and previously it was working perfectly. But since Thursday 29th March, 2018 last week there is no response being received at my callback endpoint from mpesa server. On Tue, Apr 3, 2018 at 9:40 AM, Brian Kisese ***@***.***> wrote: > @Aleqi <https://github.com/Aleqi> @nellycheboi12 > <https://github.com/nellycheboi12> You need to define your own callback > URL inorder to receive the callbacks. Use this tutorial on how you can use > firebase and PHP for that https://www.androidhive.info/2 > 012/10/android-push-notifications-using-google-cloud-messaging-gcm > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#16 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AP3rWEZT02-IQVw-PZFpbXf7TgngVkxhks5tkxlUgaJpZM4TC7c6> > . >

Answer 6 · 2020-02-14T19:34:13.000Z

@Aleqi I have the same issue, which kind a bug was it, cant get responses on my callback url. Like the c2b urls, are we suppose to register this STK callback url?

Answer 7 · 2020-02-14T20:05:40.000Z

I came to notice that there are some servers that have a problem with this and after several times of retrying Mpesa drop the response

Answer 8 · 2020-02-29T15:40:49.000Z

I think thats the reason for my case, I will try changing server

Answer 9 · 2022-05-19T13:35:10.000Z

hello @Aleqi

what kind of bug you were getting at api side ? I am implementing Lipa Na Mpesa STK push and I am not getting response at my callback url after transaction .

please help

Answer 10 · 2023-01-02T19:51:40.000Z

it's strange. I simply cannot get any response from Safaricom through the callbackurl despite all systems working fine previously. What kind of a bug is this @Aleqi? Hey @nellycheboi did you resolve yours?

Answer 11 · 2023-01-29T16:43:57.000Z

Any luck @itsKirk ?

Answer 12 · 2023-02-04T18:31:34.000Z

yeah @em-manuel it turned out to be a bug and it was only on sandbox environment. After two days I got a response from Daraja API guys and confirmed the same but all is well now.

Answer 13 · 2023-11-06T00:08:41.000Z

This issue is still there. Sometimes it works, most of the time the endpoint doesn't get the response from Safaricom. Frustrating really.

Answer 14 · 2023-11-06T07:36:01.000Z

@angwandi,
I have resolved to going straight to production environment to avoid the massive time wastage on the sandbox environment.

Answer 15 · 2023-11-06T07:38:03.000Z

@angwandi, I have resolved to going straight to production environment to avoid the massive time wastage on the sandbox environment.

This is the best possible solution

Answer 16 · 2023-11-06T10:55:51.000Z

@ngangavic @em-manuel I think I will do the same then. Thank you.

But what's the point of offering a sandbox test account that doesn't work?

Answer 17 · 2024-02-22T11:33:09.000Z

Still a problem

Answer 18 · 2024-04-01T23:20:31.000Z

Well someone can get the result of the test transaction by querying mpesa with the CheckoutRequestID (this is returned in the body of initial sdk ).One can make a post request to https://sandbox.safaricom.co.ke/mpesa/stkpushquery/v1/query.
I found how to query by login->select APIs->click on query button in the M-Pesa Express card.
Hope this helps those in test env but I would suggest one moves to production to avoid the many hustle of dealing with CheckoutRequestIDs