It is 11pm. A member sends a DM: "I have paid oh, why am I not in the group?" The message comes with a screenshot of what looks like a successful transfer of ₦8,000 to your account. You open your bank app, scroll through the day's transactions, and find nothing. No ₦8,000. No matching name. No record at all.
Most payment guides assume you are on Stripe with a dispute management portal and a 90-day chargeback window. That is not this. In a Nigerian community, the dispute is informal: a member who believes they paid, a creator who cannot find the record, and no shared system to break the tie.
If you collect payments manually, this conversation finds you eventually. How you handle it matters to the member in front of you and to how many similar conversations happen next month.
What a payment dispute actually looks like in Nigeria
The word "dispute" suggests something formal: a bank review, a merchant portal, a paper trail. Most of the time, it is a DM.
The most common version is the unverifiable screenshot. A member sends an image of a completed bank transfer or a Paystack payment confirmation page. The screenshot looks real. The amount is right. The date is recent. But you cannot find the transaction in your bank app. The screenshot may be genuine and the transfer may simply not have cleared yet. It may also be edited. Without a reference number, there is no way to know from the image alone.
The second version is the wrong account. A member claims to have paid ₦12,000 but transferred it to an old account number you changed six months ago, or to a different account entirely because they saved your details incorrectly. The money left their account and arrived somewhere. Just not yours. Who carries the error depends on what account information they were given and when.
The third is the split payment. A member who owes ₦8,000 sends two transfers of ₦4,000 each and expects full access. They paid the total. You found one transfer, not both, and removed them or declined their access by mistake. This one is particularly common when members pay from two different phones or try to split between two bank accounts. The math adds up; the problem is that you were looking for a single ₦8,000 entry that never appeared.
Then there is the formal version: a card chargeback through Paystack. A member pays by card, contacts their bank directly, and disputes the charge with the card issuer. It is the rarest of these scenarios and the one with the most formal process attached to it.
Why disputes happen at all
The root cause is almost always manual verification. When you post your account number in the group and wait for transfers, the only record of payment is a screenshot the member controls and a bank statement only you can see. There is no common ground. When the two sources conflict, the dispute has nowhere to go except someone's word against someone else's, and that is not a process.
This is the structural problem screenshot-based payment collection creates for Nigerian community creators. The screenshot sits on the member's phone. The bank record sits in your app. Neither side can show the other something they both trust.
What to do when a member claims they paid
Ask for the transaction reference number, not another screenshot. Every bank transfer and every Paystack card payment generates a unique reference stamped in the sender's transaction history. A reference number exists independently in the bank's systems and cannot be edited into an image after the fact. When a member provides the correct one, you can check it against your bank statement or Paystack dashboard and confirm within seconds.
Open your bank app and search for that reference. Check the amount received and the account it landed in. If both match, the dispute is over. Add the member.
If the reference does not appear, there are two possibilities. The transfer may still be processing, particularly for inter-bank transfers that take longer to post. Wait 24 hours before drawing any conclusion. The other possibility is that the payment did not complete, either because the transfer was reversed or because it landed in a different account.
When you cannot confirm payment, respond with the facts. Something like: "I have checked and cannot find a transaction with that reference in my account. Please confirm the account number you transferred to and the exact amount. If the payment went to the right account, it should show in my records within 24 hours. If it does not appear, I will ask you to complete the payment." This gives the member a clear next step without accusing them of anything. The tone matters: a member who feels accused of dishonesty is much less likely to renew, even if they eventually pay.
If the member cannot provide a reference number at all, that is the meaningful signal. A genuine transfer always produces a reference. When a member has only a screenshot but no reference, either the screenshot is edited or the transaction was reversed after it was captured. You are not obligated to accept a screenshot as confirmation, and saying so plainly is not an accusation. "I need the transaction reference number to verify this on my end. Bank screenshots can look complete even when a transfer was reversed, so I use references to confirm. Please send it when you have it."
If the member says the transfer went to the wrong account, the money moved but the destination was wrong. Check what account details you shared and when. If you gave them an incorrect number, help them chase it down: ask for the receiving account details so they can request a reversal from their bank, then send them the correct payment information. If they used an old number they saved without checking, the error is theirs, but offering temporary access while they sort it out usually costs less than losing the member entirely.
How to prevent disputes before they happen
The most direct fix is removing manual verification. When a member pays through Paystack via a Memberlet checkout page, the system records the payment, issues a subscription, and adds them to the group. There is no screenshot, no manual check. The platform shows an active subscription or it does not, and both the creator and the member can see that record.
For creators still collecting bank transfers manually, the space between payment and confirmation is where disputes live. Send written payment instructions to every member before their renewal date: one account number, one exact amount, one reference format, such as the member's name and phone number. Not posted once in the group and left to scroll away. Sent directly, each time payment is due. Keep a dated log of every confirmed transfer, even a basic spreadsheet updated the same day.
For more on setting up recurring payments that members can track and complete accurately, the process applies whether or not the rest of the collection is automated.
When a formal Paystack chargeback arrives
A card chargeback is a different situation. Paystack sends a notification by email with the transaction details and a response deadline, typically five days. For a ₦5,000 transaction it looks something like: "Dispute received. Transaction reference PAY-ABC123. Amount: ₦5,000. You have until [date] to submit evidence."
The evidence is proof the member received access. That can be the subscription confirmation email Paystack sent at the time of payment, a screenshot of their active subscription record in your Memberlet dashboard showing the exact access dates, or any chat history showing them inside the group during the paid period.
Log into your Paystack merchant dashboard, go to the Disputes section, and submit the evidence before the deadline. Paystack forwards it to the member's bank. If your evidence shows the service was delivered, the decision typically goes in the creator's favour. If nothing is submitted, the bank defaults to the cardholder.
The practical defence is documentation that exists from the moment of payment. When access is automated and logged, that documentation is already there. When it is not, you are reconstructing it under time pressure.
Set up automated payment and access on Memberlet. Free to start, and every payment is recorded the moment it is made, by both you and the member.
