search

safaricom / LNMOnlineAndroidSample

Lipa Na MPESA Online (STK Push) Android Sample Application. This app demonstrates an e-commerce purchase and checkout process via Mpesa and Daraja :smile:
https://developer.safaricom.co.ke/
Apache License 2.0
129 stars 128 forks source link

No response received at callback url endpoint #16

Closed Aleqi closed 6 years ago

Aleqi commented 6 years ago

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

nellycheboi commented 6 years ago

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

kisese commented 6 years ago

@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

Aleqi commented 6 years ago

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 notifications@github.com 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 https://github.com/safaricom/LNMOnlineAndroidSample/issues/16#issuecomment-378144519, or mute the thread https://github.com/notifications/unsubscribe-auth/AP3rWEZT02-IQVw-PZFpbXf7TgngVkxhks5tkxlUgaJpZM4TC7c6 .

Aleqi commented 6 years ago

@nellycheboi12 No luck yet

Aleqi commented 6 years ago

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 aleqikam@gmail.com 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 notifications@github.com 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 https://github.com/safaricom/LNMOnlineAndroidSample/issues/16#issuecomment-378144519, or mute the thread https://github.com/notifications/unsubscribe-auth/AP3rWEZT02-IQVw-PZFpbXf7TgngVkxhks5tkxlUgaJpZM4TC7c6 .

weddingjuma commented 4 years ago

@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?

ngangavic commented 4 years ago

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

weddingjuma commented 4 years ago

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

kalyangadgil commented 2 years ago

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

em-manuel commented 1 year ago

Any luck @itsKirk ?

angwandi commented 1 year ago

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

em-manuel commented 1 year ago

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

ngangavic commented 1 year ago

@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

angwandi commented 1 year ago

@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?

mwongeraE commented 9 months ago

Still a problem

samuelmaina commented 7 months ago

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