Handling Refunds and Returns

Nobody likes processing a refund, but how you handle one says a great deal about your business. A customer who gets their money back quickly and politely often returns. A customer who has to chase you tends to call their bank, and then you face a chargeback on top of the lost sale.

Refunds are also a place where mistakes and misuse hide. Money flows out of your account, staff have access and the rules for returning card payments are specific. Understanding the mechanics, writing a plain policy and putting a few controls around refunds will save you money and awkward conversations.

Void or refund: choose the right tool

A void cancels a transaction before it settles, usually before the batch closes that day. The customer's authorization is released, and in most cases the sale never appears as a posted charge, so there is typically no processing fee on a voided sale. A refund reverses a settled transaction by sending money back to the card, which takes additional days to appear on the cardholder's statement.

When a customer changes their mind soon after paying, check whether the batch is still open. If so, void it. If it has settled, issue a refund. Using the right one reduces fees and spares the customer a long wait.

Refund to the original card

The general rule, supported by card network practice, is to refund to the same card used for the purchase. This ties the refund to a legitimate sale, creates an audit trail and prevents refund schemes in which stolen cards are used to buy goods that are then refunded to a different method. If the original card is no longer valid, ask your processor how to handle the case rather than improvising with cash.

Also consider the reverse: refunding a card payment with cash can look generous but leaves the original charge in place, which sometimes ends in the customer being refunded twice, once in cash and once through a dispute.

What refunds cost you

Processing fees on the original sale are generally not returned when you issue a refund. Interchange is typically not given back, and your processor's per-transaction fee is usually kept. Say you refund a $100 sale originally charged at 2.9 percent. In this hypothetical you may have paid about $2.90 plus a per-item fee, and you often do not recover it.

That cost is another reason to reduce refunds at the source: describe products accurately, check orders before they ship and confirm service details in writing. A refund that avoids a chargeback is still the better outcome, because a dispute adds its own fee and affects your dispute ratio.

Partial refunds deserve their own rule. When a customer returns one item from a larger order, or you agree to a price adjustment, refund only the amount owed and note the reason in the system. Avoid refunding more than the original sale, and keep a link between each partial refund and the transaction it relates to. Clean partial refunds make end-of-month reconciliation easier and show a dispute reviewer exactly what you agreed to, item by item.

Write a policy people can follow

A clear return policy prevents disagreements. It should be posted where customers decide and printed on receipts. Cover these points:

• The time window for returns, measured from purchase or delivery.
• Condition requirements, such as unused, original packaging or a receipt.
• Exceptions, including custom, perishable and final-sale items.
• Refund method: original card, store credit or exchange, and typical timing.
• Who pays return shipping for online orders.
• Restocking or cancellation fees, if any, stated before purchase.

Controls that prevent refund abuse

Because refunds move money out, they deserve oversight. Give each employee a unique login so every refund is tied to a person. Require manager approval above a set amount and review a daily report of refunds and voids by employee. Watch for patterns, such as many refunds to the same card, refunds just below the approval threshold or refunds processed outside business hours.

Online, be alert to refund requests that follow suspicious orders, and never refund to a different card than the one used. If a customer claims not to have received a refund, give them the transaction reference and explain that it can take several business days to appear.

Processing a refund step by step

Use a consistent routine for every return.

1. Look up the original sale and confirm the amount, date and card used.
2. Check whether the batch is still open, and void if so.
3. If settled, issue a full or partial refund to the original card.
4. Send the customer a receipt showing the refund amount and reference.
5. Tell them it may take several business days to appear.
6. Record the reason in your system for later review.

Getting help

MCCPS reporting shows refunds and voids by device and user, and free 24/7 support is available if a refund will not process. Call 844.826.6227 for help, and consider the free statement analysis to see what refunds and related fees cost your business each month.

This article is general information, not legal, tax or compliance advice. Card-network and state rules change — confirm current requirements before acting. Savings depend on your individual statement analysis.