Training Your Team on Payment Operations

If you are the only person in your business who knows how to check the Paystack Dashboard, you become a bottleneck. Every customer complaint about a payment has to wait for you. Every refund request needs your approval and your hands on the keyboard. Every "did this person pay?" question requires your time.

Training your team on payment operations means they can handle routine payment issues independently. You focus on running the business while your customer support team resolves complaints quickly and your operations team processes orders without waiting for you to confirm payments.

Training also reduces errors. An untrained team member who tries to "help" with a payment issue can make things worse: processing an incorrect refund, sharing sensitive information with a customer, or changing settings they do not understand.

Every team member who handles customer interactions should be able to do the following in the Paystack Dashboard:

Look up a transaction. Search by customer email, amount, or date range. Understand what each status means: successful, failed, abandoned, reversed.

Read transaction details. Click on a transaction to see the payment method used, the timestamp, the reference number, and any error messages for failed transactions.

Check settlements. Understand where to find settlement information and how to tell if a settlement has been sent to the bank.

Navigate customer records. Find a customer's payment history by searching for their email in the Customers section.

Create a cheat sheet with screenshots showing where to find each of these things. Keep it printed or saved where the team can access it quickly. Walk new team members through the dashboard on their first day and have them look up real transactions as practice.

Create written scripts for the most common complaints:

"I paid but my order is not showing."

1. Look up the transaction in Paystack by customer email
2. If status is "successful": apologize, confirm the payment manually, escalate to operations to process the order, tell the customer the order is being processed
3. If status is "failed": tell the customer the payment did not go through and ask them to try again
4. If no transaction found: ask the customer to check their bank for a deduction and to try paying again

"I was charged twice."

1. Search for multiple transactions from the same customer email with similar amounts
2. If duplicate is confirmed: apologize and initiate a refund for the duplicate (if authorized to do so, or escalate to a manager)
3. If only one transaction shows: explain that the second charge may be a temporary bank hold and ask them to check again in 24 to 48 hours

"When will I get my refund?"

1. Check the refund status in the dashboard
2. Tell the customer: "Your refund has been processed. It typically takes [X] business days to appear in your account, depending on your bank."
3. Never promise a specific date

Print these scripts and keep them at every customer support station. See handling customer payment complaints for a complete guide.

Decide in advance who is authorized to process refunds and under what conditions. Write these rules down:

• Who can authorize refunds? Is it any team member, a supervisor, or only you?
• What amount threshold requires manager approval? For example, refunds under 5,000 can be processed by any team member, while refunds over 5,000 need a manager.
• What documentation is required? Should the team member note the reason for the refund, the customer's complaint, and the transaction reference?
• How quickly should refunds be processed? Set a target response time (for example, within 24 hours of the complaint being confirmed).

For team members authorized to process refunds, walk them through the actual process in the Paystack Dashboard: finding the transaction, clicking the refund button, entering the amount, and confirming. Have them do it with a test transaction before they do it with real money.

Keep a log of all refunds processed. Review this log weekly to spot patterns (same product getting many refunds, same employee processing unusual refunds).

These rules should be non-negotiable for every team member:

• Never share API keys with anyone. Not with customers, not with people claiming to be from Paystack support, not with anyone who emails or calls asking for them.
• Never change the settlement bank account. This should be a manager-only action, and even then, verified through a separate channel.
• Never share your Paystack login credentials. Each team member should have their own login with appropriate role-based permissions.
• Never discuss specific transaction amounts or customer payment details in public channels. Payment information is private.
• Report suspicious requests immediately. If anyone (customer, external caller, email) asks for payment credentials or suggests changing bank details, report it to a manager.
• Lock your computer when you step away. An unattended computer with the Paystack Dashboard open is a security risk.

Make every team member sign a document acknowledging they understand these rules. It sounds formal, but it underscores the seriousness of handling payment data.

Paystack allows you to add team members with specific roles and permissions. Use this to give each person access to only what they need:

• Customer support: View transactions, view customer records. No refund or settings access.
• Operations manager: View transactions, process refunds (with limits). No settings or API key access.
• Finance/accounting: View transactions, view settlements, export reports. No refund or settings access.
• Owner/admin: Full access to everything including settings, API keys, and bank account details.

Check Paystack's current team management features for the exact roles and permissions available. The specific options may vary, but the principle is the same: give the minimum access needed for each person's job.

When a team member leaves the company, remove their access immediately. Do not wait. An ex-employee with payment system access is an unnecessary risk.

Payment training is not a one-time event. Schedule refreshers:

• Monthly: Quick 15-minute review of common issues encountered in the past month and how they were handled.
• Quarterly: Review and update your written procedures. Remove scenarios that no longer apply and add new ones that have come up.
• When something changes: Any time you update your Paystack integration, change your refund policy, or add new payment methods, brief the team.
• After incidents: If a security scare, fraud attempt, or significant payment issue occurs, do a debrief with the team. What happened, how was it handled, what could be better.

The goal is a team that handles 90% of payment issues without needing to escalate to you or your developer. The remaining 10% (unusual cases, technical bugs, system issues) get escalated through a clear process.

This article is part of the Paystack for business owners series.