Paystack 401 "Invalid key" on POST transaction/initialize

TL;DR

For "Client error: POST https://api.paystack.co/transaction/initialize resulted in a 401 Unauthorized response: {"status": false, "message": "Inv": one reporter had the same error specifically when setting keys at runtime with Config::set from a database table, while hardcoding the same key in the config file returned 200. If you set keys at runtime with Config::set, know the package reads config early, so dynamic keys may not be picked up.

Client error: POST https://api.paystack.co/transaction/initialize resulted in a 401 Unauthorized response: {"status": false, "message": "Invalid key"}

Steps

1. Every pay attempt failed with Client error: POST https://api.paystack.co/transaction/initialize resulted in a 401 Unauthorized response: {"status": false, "message": "Invalid key"}. The keys looked right in the config file. One reporter had the same error specifically when setting keys at runtime with Config::set from a database table, while hardcoding the same key in the config file returned 200.
2. The 401 with "Invalid key" means exactly what it says: the public or secret key Paystack received isnt valid for your account. Check these in order:
3. Make sure PAYSTACK_PUBLIC_KEY and PAYSTACK_SECRET_KEY in your .env are the real keys from your Paystack dashboard (test vs live keys are easy to mix up).
4. After changing .env, clear the config cache (php artisan config:cache, php artisan cache:clear); Laravel keeps serving old cached keys otherwise.
5. If you set keys at runtime with Config::set, know the package reads config early, so dynamic keys may not be picked up. One reporter solved it by writing the key to the environment first, so it was set before the request.

When to use

You are seeing this: Every pay attempt failed with Client error: POST https://api.paystack.co/transaction/initialize resulted in a 401 Unauthorized response: {"status": false, "message": "Invalid key"}. Use this skill when you run into "Paystack 401 "Invalid key" on POST transaction/initialize".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://api.paystack.co/transaction/initialize

Someone asked: Every pay attempt failed with Client error: POST https://api.paystack.co/transaction/initialize resulted in a 401 Unauthorized response: {"status": false, "message": "Invalid key"}. The keys looked right in the config file. One reporter had the same error specifically when setting keys at runtime with Config::set from a database table, while hardcoding the same key in the config file returned 200. The verified resolution was: The 401 with "Invalid key" means exactly what it says: the public or secret key Paystack received isnt valid for your account. Check these in order:

1. Make sure PAYSTACK_PUBLIC_KEY and PAYSTACK_SECRET_KEY in your .env are the real keys from your Paystack dashboard (test vs live keys are easy to mix up).
2. After changing .env, clear the config cache (php artisan config:cache, php artisan cache:clear); Laravel keeps serving old cached keys otherwise.
3. If you set keys at runtime with Config::set, know the package reads config early, so dynamic keys may not be picked up. One reporter solved it by writing the key to the environment first, so it was set before the request.

Source: https://github.com/unicodeveloper/laravel-paystack/issues/86 Original thread: https://vectle.com/threads/thr_z0e3Yc4YYCnKy5WGMzGgkQ