Refund Processing

Refund processing is the set of steps a merchant or payment provider follows to return money to a customer for a completed payment, from approving the refund to sending the funds back through the original payment method and recording it in the books. It applies when goods are returned, an order is cancelled after payment, a service is not delivered, or an overcharge is corrected.

A refund is started by the merchant, which distinguishes it from a chargeback, where the cardholder's bank forces the return of funds through a payment dispute. It also differs from payment cancellation, which stops a payment before it completes, and from a reversal of an authorization that was never captured. Merchants set refund policies within the limits of consumer law and card network rules.

When you return a shirt to a shop, the cashier does not hand you cash from the till if you paid by card. Instead, they run your card again, this time for a "minus" amount, and your bank adds the money back to your account a few days later.

Behind the counter, the shop has to do several things: check that you really bought the shirt, decide whether you get the full price back, send the minus payment to the right card, and note in its records that the sale has been undone. Refund processing is the name for all of that. Online it works the same way, just without the counter, and the slow part is usually the banks passing the money back, not the shop pressing the button.

1. Approval. The merchant checks the refund against its policy and the original order.
2. Refund request. The merchant sends a refund (credit) transaction that references the original sale through its payment gateway to the acquirer.
3. Authorization of the credit. Visa and Mastercard now require refunds to be sent for authorization like purchases, a change both networks rolled out in recent years. This lets the issuing bank show the pending refund to the cardholder quickly and helps detect refund fraud.
4. Clearing and settlement. The refund goes through payment clearing via the card network in the next batch, the acquirer deducts it from the merchant's settlement, and the issuer credits the cardholder. The credit can take several business days to appear as available funds.

Network rules generally require card refunds to go back to the card used for the purchase, not to another card or in cash, which closes off a common money laundering and fraud route. Refunds are capped at the original amount; a goodwill payment above it is a separate transaction.

• Bank transfers. There is no built-in link to the original payment, so the merchant sends a new credit transfer to the customer's account, ideally after checking the details through bank account verification to avoid misdirected funds. On instant rails such as UPI and PIX, the scheme provides a refund message type that references the original payment.
• ACH debits. A merchant that collected by ACH pull refunds with an ACH credit, as a reversal entry is only permitted for specific errors such as duplicates.
• Wallets and BNPL. Digital wallets and buy now, pay later providers pass refunds back to the funding source or reduce the outstanding instalments.
• Cross-border payments. Refunds in a foreign currency are converted at the rate on the refund date, so the cardholder may receive more or less than they paid, especially if dynamic currency conversion was used at purchase.

In the EU and UK, consumers who buy at a distance generally have a 14-day right to withdraw from the contract, and the trader must refund within 14 days of being told of the withdrawal (or of receiving the goods back, where it may wait for them), using the same payment method unless agreed otherwise. In the US, federal law does not require merchants to accept returns, but merchants must honour the refund policy they disclose, and a card issuer can treat a refund that was promised but not processed as a billing error under the Fair Credit Billing Act or Regulation E. Visa and Mastercard rules require merchants to disclose return policies clearly at checkout.

Refunds are not free for merchants. Many acquirers do not return the payment processing fee charged on the original sale, so a refunded sale can cost the merchant the fee with no revenue, though some pass back part of the interchange. Even so, a prompt refund is cheaper than a chargeback, which adds a dispute fee and counts against the merchant's dispute ratio and chargeback risk profile.

Refunds are also a fraud channel. Insiders may push refunds to their own cards, and organised groups exploit lenient return policies. Controls include refunding only to the original payment method, dual approval for large refunds, role limits in the refund tool and monitoring for unusual refund patterns, part of wider payment fraud controls. On the accounting side, a refund reverses revenue and, under IFRS 15 and ASC 606, merchants that expect returns record a refund liability instead of recognising all sales as revenue at once. Each refund must also match a debit on the settlement report during payment reconciliation, and each request should carry an idempotency key so a retried request does not refund twice.

• Visa Core Rules and Visa Product and Service Rules
• 12 CFR 1026.13 Billing error resolution (Regulation Z)