How do online refunds work?

A refund is linked to a completed payment

A refund normally follows a payment that has already succeeded or been captured. If a payment has not completed, canceling or voiding it may be the relevant action instead. That distinction affects what appears in the merchant dashboard and on the customer's account. The related guide to the difference between a void and a refund explains the operational boundary.

Current Stripe documentation says its merchants can refund all or part of a successful payment, while Square's current merchant instructions likewise support full, partial, or itemized refunds in eligible workflows. Those examples illustrate a common pattern, not a promise that every processor, gateway, platform, or payment method offers identical controls.

Where the refunded money goes

For standard card refunds, the safest general expectation is that the credit follows the original payment path. Stripe's current refund documentation states that refunds on its platform can only return to the original payment method. Square's API documentation similarly says a linked payment refund normally returns funds to the original payment source. Provider-specific exceptions and non-card methods can behave differently, so merchants should not promise an alternate destination without confirming the documented workflow.

An expired or replaced card does not automatically mean a merchant should send money somewhere else. The card issuer may route a valid credit to a replacement account or provide its own resolution. If the provider marks a refund as failed, follow the provider's instructions before arranging any alternative. Never ask a customer to send a complete card number, bank credential, password, or security code through email or a general contact form.

Controls that make refunds easier to manage

• Limit permissions: Give refund access only to team members who need it, and review access when roles change.
• Require transaction matching: Link the refund to the original order and payment whenever the system permits.
• Keep a decision record: Store the amount, reason, operator, date, and provider status in the appropriate business system.
• Reconcile consistently: Match refund records with order adjustments, inventory changes when relevant, and payment reports.
• Communicate accurately: Tell customers when the request was submitted without guaranteeing when their institution will display it.

Businesses should also publish a clear customer-facing policy before purchase. The guide to what a refund policy should include provides a practical framework. A refund and a payment dispute are different processes; review how refunds and chargebacks interact when a customer has already contacted an issuer.

Questions merchants often ask

Can an online payment be partially refunded?

Many payment systems support partial refunds, but availability and limits are provider- and payment-method-specific. Confirm the current controls for the original transaction before promising a partial credit.

Why did the original charge disappear?

A refund initiated close to the payment may be processed as a reversal. In that case, the customer may not see a separate credit because the original charge is removed or adjusted.

What if the refund fails?

Check the provider's refund status and failure instructions. Confirm whether the amount returned to the merchant balance before arranging another payment, because an uncoordinated second refund can create duplicate reimbursement.