No articles found for “”.
Paystack transfer failures
If salary disbursements are failing with a "Transfer failed" or "Invalid key" error, one of two things is usually the cause.
1. Incorrect Paystack secret key
SpireSlip uses your entity's Paystack secret key to initiate salary transfers. If the key is wrong or has been rotated since you last saved it:
- Log into your Paystack dashboard.
- Go to Settings → API Keys.
- Reveal your Live Secret Key.
- In SpireSlip: go to Entities → your entity → Payroll → Disbursement.
- Click "saved, click to replace" next to the Paystack secret key field.
- Paste the correct
sk_live_...key. - Save and click Test connection.
The key must start with sk_live_ (not pk_live_ which is the public key, and not sk_test_ which is the test key).
2. Paystack OTP confirmation
SpireSlip handles OTP confirmation natively. When OTP is required, you will see a prompt on the payroll run page to enter the OTP sent to your Paystack email. You do not need to disable OTP confirmation.
After disbursement, if OTP is required, an amber banner will appear on the payroll run page with an OTP input field. If you have not confirmed it is you in the last 10 minutes, the banner shows Confirm it is you, then enter the code instead: confirm first, and the field appears when you come back to the run. Enter the code from your Paystack email and click Confirm transfers. SpireSlip uses the code for every transfer waiting for an OTP; if Paystack does not accept it for one, that transfer shows Enter the latest OTP and you confirm it with the newest code.
Do not disable OTP confirmation unless you are comfortable doing so. It is a security setting that protects your Paystack account from unauthorised transfers.
Paystack uses an ambiguous "Invalid key" error for both incorrect keys and OTP-related rejections. If you see this error, check your key first, then contact support if the key is correct.
Retrying failed transfers
Once the issue is resolved, go to the payroll run with failed transfers. Click Retry next to each failed employee. SpireSlip reattempts the transfer without creating a new payroll run. Retrying moves money, so if you have not confirmed it is you in the last 10 minutes, SpireSlip asks you to first (see Account security).
Test mode warning
If your Paystack key starts with sk_test_, SpireSlip is in test mode. No real money moves. Switch to your sk_live_ key when you are ready for live disbursements.