Customer refunds: refund the original payment without creating a second fraud risk

A customer refund should reverse or reduce the original commercial transaction and remain traceable to it. Sending money to a completely new bank account can turn a routine refund into a fraud or reconciliation problem, especially where the original payment was made by card.

For card payments, issue the refund from the original transaction where the processor supports it

Stripe's current UK merchant guidance lets businesses refund a non-disputed card payment directly from the original payment record or via the API, either in full or partially. This keeps the refund linked to the original transaction and preserves the payment-provider audit trail.

That is usually cleaner than asking a card customer to email bank details for a separate Faster Payment. The refund remains connected to the charge, cardholder and original order. If the customer's card has since been replaced or expired, the issuer and card network can often still route the refund appropriately, depending on the circumstances.

A card refund is not always visible to the customer immediately

Stripe's UK support guidance says refunds commonly take five to ten business days to appear on the customer's account. A refund can also appear as a reversal, where the original card charge disappears or is adjusted instead of a separate refund line being shown.

Tell customer-service staff not to promise "the money will be back today" merely because finance clicked refund. Provide the date the refund was submitted and, where the processor supplies one, an ARN or STAN that can help the customer's bank trace the transaction after the normal processing window.

A partial refund should reduce the original sale rather than look like unrelated spending

Where a £500 order receives a £100 partial refund, the accounting record should show £400 of net retained sale value and the £100 refund or sales adjustment according to the company's accounting policy. Do not post the £100 as a generic operating expense merely because cash left the processor balance.

Keep the reason code or customer-service note: returned item, damaged goods, price adjustment or service credit. This helps management understand refund rates by product and prevents the finance team from confusing ordinary refunds with chargebacks or discretionary goodwill payments.

Refunds can remain pending when settlement or processor balance is not ready

Stripe's current UK guidance says a refund can remain pending because the payment itself is still processing, a bank or financial partner is processing the refund, or the merchant has insufficient available balance with the processor. The refund status should therefore be monitored rather than assumed complete once requested.

If the business runs with very low processor balances, a wave of refunds after an event cancellation or product recall can create a liquidity problem. Include expected refunds in the cash forecast and maintain enough reserve or settlement cash to honour customer obligations without waiting for new sales to fund yesterday's refunds.

Manual bank-transfer refunds need independent verification of the destination account

Sometimes the original payment route cannot be used, for example where the customer paid by bank transfer and a separate refund must be sent. Do not accept changed bank details from one unexpected email without verification. Confirm the customer identity and account details using information already held or another trusted channel, especially for material amounts.

Where possible, refund to the same bank account that made the original transfer. If the customer asks for payment to a different person or entity, escalate the request. A supplier-invoice fraud mindset applies here too: money leaving the company to new account details should never be treated as low risk merely because it is labelled a refund.

Connect the refund to the original sale, fees and bank settlement

Reconcile the original gross payment, original processing fee, refund amount, any refund fee under the merchant's pricing and the effect on future payouts. Stripe's current UK pricing guidance says standard-pricing businesses can face refund-related fees for some bank-transfer methods, while original card-processing and currency-conversion fees are not necessarily returned.

Keep each processor's treatment visible. A £1,000 sale refunded in full does not always create a £1,000 economic reversal if the original acceptance cost remains with the merchant. Management should see refund cost and refund volume separately so it can distinguish customer-service policy from payment-processing expense.

Review refund patterns monthly by product, channel and reason. A rise in refunds for one product can signal fulfilment, quality or description problems rather than a payment issue. Finance should therefore share refund data with operations and customer service instead of treating every credit as an isolated accounting event.