Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Payments & Reconciliation 6 min read

Refund and chargeback operations: common problems and fixes

Why refunds stall, duplicate and fail reconciliation, and the order records, approvals and evidence packs that fix the process.

E
EncryptTechBD · 0 comments
Stacked coins
Photo: Negative Space / StockSnap

Refunds look like a button. In practice they are a small operational system that touches the order record, the payment provider, the delivery record, customer support, finance and sometimes a mobile financial service agent. When one of those pieces is missing, the customer waits, the agent guesses and the month-end reconciliation stops balancing.

This guide is written as a troubleshooting sequence. Start with the symptom you recognise, then work back to the cause. The fixes are deliberately unglamorous: clearer states, named owners, approval limits, evidence and a daily match.

Symptoms that point to a process problem

  • The system says "refunded" but the customer says the money never arrived.
  • The same refund is issued twice, or a partial refund is paid twice.
  • A chargeback deadline passes while the team is still collecting evidence.
  • The refund amount is wrong after a discount, delivery charge or partial return.
  • A refund is approved before the product is returned or inspected.
  • A cash-on-delivery order is refunded through the wrong channel.
  • Support cannot match a payment to an order without asking finance.
  • Month-end reconciliation shows unexplained differences that nobody owns.

These are not payment-provider failures. They are signs that the business has no single refund state, no decision rules and no evidence trail.

Cause 1: the refund is a note, not a state

If the only record of a refund is a comment such as "done" or "sent to accounts", nobody can tell whether the money left, whether it reached the customer, or whether the provider rejected it. Replace free text with a small set of states:

  1. Requested: the customer has asked and the reason is recorded.
  2. Approved or rejected: a named person made a decision under a defined limit.
  3. Sent: the instruction has gone to the provider or bank.
  4. Confirmed: the provider or settlement file shows the money moved.
  5. Closed: the customer has been informed and the case is complete.
  6. Failed: the instruction failed and needs a retry or a different channel.

Each state change should record the amount, channel, provider reference, actor and timestamp. That single change fixes most "where is my refund?" conversations.

Cause 2: nobody owns the decision

Support wants to keep the customer happy, operations wants the product back, and finance wants the ledger to balance. Without a decision matrix, each case becomes a negotiation.

Write down four things:

  • Reason codes: damaged, wrong item, late delivery, change of mind, duplicate payment, fraud, goodwill.
  • Evidence required: photo, courier receipt, return scan, payment reference, chat record.
  • Approval limits: who can approve a refund, and at what value or risk level a second person must agree.
  • Channel rule: refund to the original payment method wherever possible, and a documented exception route for cash-on-delivery or mobile financial service payments.

The limit can be set by the business. The important part is that it is written, enforced in the system and reviewed when abuse appears.

Cause 3: the evidence pack is assembled too late

A chargeback is a deadline-driven evidence exercise. If the team starts collecting documents when the dispute arrives, it will miss some deadlines and submit weak cases.

Build the evidence pack at order time and keep it with the order:

  • Order confirmation, items, amounts, discounts and delivery address.
  • Payment record with provider reference and settlement date.
  • Delivery record, courier tracking and proof of delivery where available.
  • Customer communication, including the policy shown at purchase.
  • Return or refund record with timestamps and the person who approved it.
  • Any fraud signals or prior dispute history for the same customer.

Store the pack in one place with a retention period agreed with finance. A folder per order is enough; the point is that anyone can assemble a submission without hunting through chat.

Cause 4: deadlines are tracked in someone's head

Chargeback and dispute windows are counted in days, and the exact rules depend on the card scheme, the acquirer and the provider agreement. Do not rely on memory or a weekly meeting.

  • Create a dispute register with received date, response due date, owner and status.
  • Set alerts at seven, three and one day before the deadline.
  • Record the submission date and the provider reference.
  • Review closed disputes monthly for recurring reasons and weak evidence.

Cause 5: refunds are not reconciled daily

Refund accuracy depends on matching three records: the order, the payment provider's transaction record and the bank or mobile financial service settlement. If the business only checks at month-end, errors have weeks to hide.

Run a daily exception report:

  1. Import the provider's settlement or transaction export.
  2. Match each refund instruction to a settlement line by reference and amount.
  3. List unmatched items with an owner and an age.
  4. Investigate anything older than two business days.
  5. Escalate repeated failures to the provider relationship owner.

Automate the match where the provider offers an API or a scheduled export. Where it does not, use a controlled import and never scrape a consumer app.

Diagnostic sequence for a messy process

  1. Count refunds by state for the last 30 days. Look for a large "sent but not confirmed" bucket.
  2. Sample ten "refunded but not received" cases and compare the order record, provider dashboard and settlement file.
  3. List every open dispute with its due date and whether the evidence pack is complete.
  4. Check who has permission to issue or approve a refund, and whether the limits are enforced in the system.
  5. Review reason codes and the written policy customers see at purchase.
  6. Compare the rules for card, mobile financial service and cash-on-delivery refunds.
  7. Fix the highest-volume failure first, then re-run the sample after two weeks.

Metrics that show whether it is working

  • Median time from refund request to confirmed payment.
  • First-pass accuracy: refunds paid correctly without a retry.
  • Share of disputes with a complete evidence pack before the deadline.
  • Chargeback rate and win rate, tracked as your own trend rather than a market benchmark.
  • Refunds older than seven days, by owner.
  • Duplicate refunds and unexplained reconciliation items.

Where this fits

If refunds and disputes are consuming support time, start with Commerce Systems. The pricing page explains how we scope commerce work. For the cost side of the problem, read what returns and refunds really cost an online seller.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes