When a customer complains about a payment, your first step is always to check the Paystack Dashboard. Search for the transaction by customer email or amount. The transaction status tells you what happened: successful means the money came through, failed means it did not, and abandoned means the customer started but never completed the payment. Respond to the customer with the specific status and next steps. Never guess or promise a resolution you cannot confirm.
Before you respond to any payment complaint, log into your Paystack Dashboard. Go to Transactions and search for the customer's email address or the transaction amount and approximate time.
The transaction status tells you what happened:
With this information, you can give the customer a factual, specific response instead of guessing.
This is the most common payment complaint. The customer paid (or believes they paid) but their order is not showing as confirmed, they did not receive their product, or they did not get a receipt.
If the Paystack Dashboard shows the transaction as successful: The customer did pay. The problem is that your system did not register the payment. This is usually a webhook issue. Tell the customer: "We can see your payment was received. There was a delay in our system updating your order. We are processing it now." Then manually confirm the order on your end and contact your developer to fix the webhook.
If the Paystack Dashboard shows the transaction as failed: The customer was not charged, even though they may have seen a deduction attempt. Tell them: "We checked and the payment did not go through. You were not charged. Please try again." If the customer insists money left their account, ask them to check their bank statement in a day or two. Failed transactions sometimes show as a temporary hold that gets reversed automatically.
If you cannot find any transaction: The customer may have left the payment page before the transaction was initiated with Paystack. Ask them to try paying again.
Get weekly developer tips
Join 25,000+ developers. Practical guides, job tips, and new content — straight to your inbox.
No spam. Unsubscribe anytime.
Search the Paystack Dashboard for the customer's email. If you see two successful transactions with the same or similar amounts close together, the customer was indeed charged twice. This is usually an integration problem where the pay button allowed multiple clicks.
Respond immediately: "We can see a duplicate charge and we apologize for the inconvenience. We are processing a refund for the extra charge right now." Then initiate a refund for the duplicate transaction from the Paystack Dashboard.
If you only see one successful transaction, the customer might be seeing a temporary hold from a failed attempt. Ask them to check again in 24 to 48 hours, as temporary holds from failed attempts are usually released by the bank automatically.
After resolving the immediate issue, talk to your developer. Double charges should not happen. The integration needs to be fixed to prevent this from recurring. See signs your integration was built badly for more details.
Customers will sometimes ask for refunds for legitimate reasons: they changed their mind, the product was not as described, or the service was not delivered. Here is how to handle this:
Check your refund policy. If you have a refund policy on your website, follow it. If you do not have one, consider creating one. A clear policy prevents arguments.
Initiate the refund through Paystack. In the Paystack Dashboard, find the transaction and click the refund option. You can refund the full amount or a partial amount. The refund is sent back to the customer through the same payment method they used.
Set expectations about timing. Tell the customer how long the refund will take. Refunds are not instant. Depending on the payment method and the customer's bank, it can take several business days to a couple of weeks for the money to appear back in their account.
Be aware of fee implications. In most cases, Paystack does not refund the transaction fee back to you. So a refund costs you the original transaction fee. This is standard for payment gateways, but it means refunds are not free for your business.
Keep records. Note the refund reference, the reason, and the date. This helps with reconciliation and with spotting patterns (for example, if the same product generates many refund requests, the product might be the problem).
Most payment complaints can be resolved using the dashboard. But some situations require Paystack's help:
When contacting Paystack support, include:
Paystack's support team responds faster when you give them specific details. "My money is missing" takes longer to resolve than "Settlement reference SET_abc123 from July 15th shows as sent but has not arrived in my GTBank account ending in 1234."
The best complaint is one that never happens. Here are ways to reduce payment complaints:
A customer complaining about a payment is often anxious or angry. Their money is involved. Here are communication principles:
Respond quickly. Speed matters more than perfection. Even a quick "We are looking into this and will get back to you within the hour" is better than silence.
Be specific. "We have checked and your payment of 5,000 with reference PAY_xyz was received at 3:42 PM. Your order is being processed." This is much better than "We will look into it."
Acknowledge the frustration. "I understand this is frustrating and I am sorry for the trouble" goes a long way, even if the problem was not your fault.
Do not blame the customer. Even if the customer made a mistake (entered the wrong amount, did not complete the payment), phrase it neutrally. "It looks like the payment session timed out before it was completed" is better than "You did not finish paying."
Follow up. After resolving the issue, send a brief follow-up: "Just confirming that your refund of 3,000 was processed today. You should see it in your account within 3 to 5 business days." This closes the loop and shows professionalism.
KES 2,999
The definitive guide to building payment systems with Paystack — from your first transaction to production-grade payment infrastructure across Africa. 9 modules, 47 lessons. Free preview available.
Start Paystack Course