Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(MPesa Error) 404.001.03: Invalid Access Token #51

Open
Kevokoma opened this issue Oct 20, 2021 · 11 comments
Open

(MPesa Error) 404.001.03: Invalid Access Token #51

Kevokoma opened this issue Oct 20, 2021 · 11 comments

Comments

@Kevokoma
Copy link

Hi Dev team,

First things first, thanks for sharing such a valuable tool with us for free. I truly appreciate it.

Now, I was trying to setup an stk push for a client using your plugin but I am at an impasse.

I keep getting this error: (MPesa Error) 404.001.03: Invalid Access Token.

Despite the fact that all credentials are the same.

What could be the issue?

Could you kindly assist me on this?

@maukoese
Copy link
Contributor

What version of the plugin are you using?

@Kevokoma
Copy link
Author

Version 3.0.0

@maukoese
Copy link
Contributor

The latest release?

@Kevokoma
Copy link
Author

Yes, the one from the master branch.
Last update was made 9 days ago

@Kevokoma
Copy link
Author

Your assistance on this will be greatly appreciated.

@muthumbinick
Copy link

The latest release?

I really appreciate your work.

Version 3.0.1RC shows the following error when I try enabling manual payments.
Kindly assist

“Callback URLs Registration

Error Occurred - Invalid Access Token - Invalid access token”

@maukoese
Copy link
Contributor

maukoese commented Nov 4, 2021

I'm having a similar issue with B2C transactions. I'm checking if it's an MPESA error or a fault on my end.

@muthumbinick
Copy link

I realized swapping the shortcode and store number for C2B on version 1.20.99 gets the URLs registered but then that’s no fix.
This one is a real brainer.
Hopefully it’s solved soon.

@maukoese
Copy link
Contributor

I fixed this one on the more recent versions.

@OliverWachira
Copy link

hello, i have tried debugging this issue of invalid access token too but i still keep getting the same error even after entering the Production credentials on the Live environment, i have been careful to enter the correct values but to no avail.

kindly assist @maukoese

@maukoese
Copy link
Contributor

maukoese commented Mar 16, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants