Chargeback vs Refund: Refund, Accept, or Challenge

A refund is a merchant decision; a chargeback is a bank-led dispute process.

Before a formal dispute opens, a refund can resolve a valid complaint directly. After a dispute opens, the merchant should work inside the dispute process: accept it when the claim is valid, or challenge it with relevant evidence. If a refund was already submitted, treat that credit as evidence. Do not automatically send the customer the money a second time.

That timing distinction matters more than a generic “refunds are better” rule. The right action depends on the transaction’s current state, what the customer is entitled to receive, and what your records can prove.

Source: Visa, “Dispute Management Guide for Merchants” (October 2026, card-dispute lifecycle and prior-credit evidence); Stripe, “Refund and Cancel Payments” (refunds and disputed payments), accessed 19 October 2026. Apply the instructions for the actual provider and case.

Chargeback vs refund: the practical difference

A refund reverses all or part of a completed payment at the merchant’s instruction. The merchant approves the remedy and submits the credit through its payment provider.

Source: Stripe, “Refund and Cancel Payments” (merchant refund workflow), accessed 19 October 2026.

The issuer-led dispute process

A chargeback, also called a card dispute, is an issuer-led process carried through the card network to the acquiring side. For a cardholder complaint, the customer asks the issuing bank—the bank that issued the card—to contest a transaction. The acquirer is the institution that provides card acceptance to the merchant.

That complaint route does not cover every condition. Visa condition 10.5 can arise from network monitoring rather than a single cardholder claim.

Source: Visa, “Core Rules and Product and Service Rules” (18 April 2026, §11.7.6.1, Table 11-32); “Dispute Management Guide for Merchants” (October 2026, lifecycle and condition 10.5, printed p. 27), accessed 19 October 2026.

Source: Visa, “Visa Dispute Management Guide for Merchants” (lifecycle, pp. 2–6; response deadlines and prior-credit guidance, pp. 7–9 and 68–69), published October 2026 and accessed 19 October 2026; HaiPay, “Pricing” and “Chargeback Process: Step-by-Step Guide for Merchants” (first-party published list figures and quote-specific fee scope), accessed 19 October 2026.

For the full sequence from notification to response and possible escalation, use the chargeback process guide. This article stays with the operational choice between refunding, accepting, and challenging.

Refund, accept, or challenge: the transaction-state decision matrix

An identifier (ID) links a record to its payment, refund, or case. An Acquirer Reference Number (ARN) is a card-network tracking reference used to trace a transaction. Keep it with the original payment and refund records.

Source: HaiPay, “Acquirer Reference Number” (card transaction tracking reference), accessed 19 October 2026.

The same complaint can require a different action one day later. Start by identifying the transaction state before discussing cost or evidence. Once a formal case exists, record its dispute ID, reason code, amount, and response deadline. Put new refunds on an internal hold while the case owner checks the provider’s permitted response route.

Source: Decision synthesis based on Visa, “Visa Dispute Management Guide for Merchants” (published October 2026, pp. 7–9 and 68–69), Visa Condition 13.6, and scoped Stripe dispute documentation (“Respond to Disputes” and “Dispute Best Practices”), all accessed 19 October 2026. This matrix is an operational control framework, not a substitute for the merchant agreement, provider instructions, or legal advice.

Confirm the live case status in your provider dashboard or application programming interface (API) before support promises a credit. Stripe documents restrictions on refunding disputed payments. Confirm another provider’s exact workflow rather than assuming the same function is available.

Source: Stripe, “Refund and Cancel Payments” (pending refunds and disputes), and “Dispute Withdrawals” (refund restrictions during disputes), accessed 19 October 2026.

State 1: when to issue a refund before a chargeback

Refund before a dispute when the customer is entitled to the money and no formal dispute has opened. Common examples include a duplicate merchant-side charge, a cancellation covered by the disclosed policy, an undelivered service, or an amount error that your records confirm.

Use four checks:

1. Entitlement: Does the contract, return policy, service record, or applicable law support the customer’s request?
2. Dispute status: Has the provider created a formal dispute case for the same transaction?
3. Amount: Is the remedy full or partial, and does it match the agreed resolution?
4. Traceability: Can the team connect the credit to the original transaction and later prove its date, amount, and status?

Do not turn this into a universal value threshold. A small payment with weak evidence may not justify staff time, but a pattern of suspicious refund requests may require a fraud review. The decision combines customer entitlement, evidence strength, operational cost, and abuse risk.

Visa’s Condition 13.6 (Credit Not Processed) guidance recommends processing credits promptly, ideally within the timeframe communicated to the customer. Confirm the refund once processed and explain when it should appear. That communication does not replace the refund record; it reduces uncertainty while the credit is being processed.

Source: Visa, “Visa Dispute Management Guide for Merchants” (Condition 13.6 prevention guidance, p. 69), published October 2026 and accessed 19 October 2026.

State 2: what to do when a refund already exists

A refund does not make a later dispute notification impossible. The customer may have contacted the issuer before the credit appeared. The refund may be partial. The issuer may not have matched the credit to the original sale. A processing error may also have left the credit incomplete.

Source: Visa, “Dispute Management Guide for Merchants” (October 2026, prior-refund and credit-not-processed guidance); Stripe, “Dispute Best Practices” (partial refunds). Accessed 19 October 2026.

First match the payment, refund, and dispute records. Confirm:

• the original transaction ID and disputed amount;
• the refund ID, amount, currency, and processing timestamp;
• whether the refund is pending, succeeded, failed, or reversed;
• the masked card or account reference used for both entries;
• the Acquirer Reference Number (ARN), when available;
• the customer message that confirms the agreed remedy.

If the customer says the credit has not appeared, the ARN guide explains what to request and how it helps the issuer locate the movement.

Source: HaiPay, “Acquirer Reference Number” (tracking and tracing workflow), accessed 19 October 2026.

For the next step, use the ARN Refund Trace Assistant to check the reference format and prepare a message about the refund, reversal or failed refund. The tool does not verify live status or receipt of funds.

Visa’s merchant guide describes when prior-refund or reversal evidence can support a response. The record must connect the credit to the disputed sale, with the refund date, amount, and transaction reference. A prior refund does not guarantee that a response is available or will succeed.

For Condition 13.6 (Credit Not Processed), check both entitlement to a credit and whether it was processed correctly. Visa’s public rules list response routes for an unaddressed credit or reversal, an invalid dispute, or a cardholder who no longer disputes the transaction. Use the route permitted for the particular case through your acquirer.

Source: Visa, “Visa Dispute Management Guide for Merchants” (October 2026, printed p. 8 and pp. 68–69); Visa Core Rules, edition 18 April 2026, §11.10.7.6, Table 11-127 (printed p. 777). Accessed 19 October 2026.

State 3: when to accept a chargeback

Accepting a chargeback means you will not try to recover the disputed funds through an evidence response. It is appropriate when your records show that the customer’s claim is valid, the refund was due but never processed, or the transaction cannot be supported under the filed reason.

If a credit was due and never processed, review the case with your acquirer before submitting a response. A generic evidence bundle does not replace a valid response ground. Visa’s Condition 13.6 guidance focuses on the credit, the disclosed refund policy, and the customer’s entitlement.

Source: Visa, “Visa Dispute Management Guide for Merchants” (October 2026, Condition 13.6, printed pp. 68–69), accessed 19 October 2026.

Withdrawal is a separate, conditional path

Stripe recommends accepting a dispute when you agree the customer should keep the funds. It advises against requesting withdrawal in exchange for an ordinary refund. This is Stripe’s documented workflow; confirm another provider’s instructions separately.

Source: Stripe, “Dispute Best Practices” (accepting disputes), accessed 19 October 2026.

Visa’s merchant guide limits when a customer’s withdrawal can support a response. Documentation must be dated after dispute initiation. The guide excludes Condition 10.5, Category 11 authorization disputes, and Condition 13.8 from that withdrawal route. A customer message alone does not close the case. Stripe states that a withdrawal does not allow a refund before the issuer decides in the merchant’s favor. Confirm the rules for your own provider.

Source: Visa, “Visa Dispute Management Guide for Merchants” (October 2026, printed pp. 8–9, permitted withdrawal evidence); Stripe, “Dispute Withdrawals” (case closure and refund restrictions), accessed 19 October 2026.

Keep the historical COVID-19 bulletin in its time context

Visa’s 21 April 2020 COVID-19 bulletin reminded participants of existing practices; it did not announce new dispute rules. Its credit-and-refund guidance warned acquirers against issuing a separate credit after a valid issuer-processed dispute. Use that as historical context for duplicate-payment risk. Current provider and acquirer instructions should govern the live case.

Source: Visa, “Managing Disputes Through COVID-19: Additional Best Practices,” Visa Business News AI09996 (21 April 2020; credit/refund guidance on PDF physical p. 3). Accessed 19 October 2026.

When to challenge a chargeback

Challenge only when your evidence addresses the actual dispute reason. A prior refund is one example. Others may include proof that the service was delivered, the customer used the product, the recurring charge was properly disclosed, or the transaction data contradicts the issuer’s claim.

The reason code is the filing category, not a conclusion that the claim is true. Use the chargeback reason codes reference to identify what the issuer alleges. Then build the response around the elements that matter to that condition.

For a refund-related dispute, a useful evidence pack may contain:

• the original transaction record;
• the refund or reversal record;
• amount, currency, and processing date for both entries;
• refund status and reference numbers;
• the return, cancellation, or service policy accepted at purchase;
• customer communications showing what was agreed;
• a short cover note that maps each file to the filed reason.

More evidence is not automatically better. Irrelevant screenshots can bury the one record that proves the credit was processed. Make the amount, date, and relationship to the original transaction visible.

Source: Visa, “Dispute Management Guide for Merchants” (October 2026, responding to the filed condition and prior-credit evidence); Stripe, “Respond to Disputes” (evidence submission). Accessed 19 October 2026. The checklist is an original preparation aid, not a guarantee of response eligibility.

Partial refunds need their own control

Track three records separately: the original payment, the amount already returned, and the amount claimed in the dispute. The unrefunded arithmetic balance does not determine the issuer’s claim.

Stripe documents cases where a customer disputes the full payment after a partial refund. Where a response is permitted, it asks merchants to include proof of the partial refund, including its amount and date.

Source: Stripe, “Dispute Best Practices” (partially refunded card payments), accessed 19 October 2026.

Check the named-network exception

The same page identifies a Cartes Bancaires exception: those disputes cannot be contested through Stripe. That response route therefore cannot be used to ask the issuer to account for the earlier partial refund.

Source: Stripe, “Dispute Best Practices” (partially refunded card payments and the named Cartes Bancaires limitation), accessed 19 October 2026.

Do not generalize Stripe’s outcome mechanics to another provider. Keep the amount already returned separate from the amount claimed in the dispute, then confirm the permitted response route.

A partial-refund reconciliation example

Hypothetical, not a customer case: An original payment is 100 units, a confirmed partial refund is 30, and the dispute notice claims 100. Your record should show all three entries. The arithmetic leaves 70 from the original sale after the refund. It does not establish that the issuer must reduce the dispute to 70 or that the merchant will recover it.

Method: Original reconciliation example; 100 − 30 = 70. The provider’s permitted response and case outcome remain separate from this arithmetic.

Attach the refund receipt and match its transaction reference, currency, amount, date, and status. Ask the dispute owner to confirm how the provider handles the returned 30 before any further payment.

The double-payout prevention ledger

Assign one owner to the payment, refund, and dispute record. Support, finance, and the dispute team need the same event history before anyone authorizes another credit.

Use one ledger row for every complaint that could become a dispute:

Method: Original operating template, not a network-mandated form. Adapt the owners and identifiers to your provider’s data model.

Give support and finance the same status vocabulary

Use one shared case record before sending a customer update. Separate “refund requested,” “refund submitted,” “provider reports refund succeeded,” and “customer confirms receipt.” Map those labels to your provider’s actual status fields.

Record the disputed amount, prior credits, case status, decision owner, and next action together. When support sends a refund confirmation, include the approved amount, currency, date, and available tracking reference. Do not describe an unresolved credit as received by the customer.

Method: Original service-and-finance control for the ledger above. These are proposed internal labels, not universal network status codes or a promised refund-arrival time.

Build the prevention path before the next complaint

A good refund policy is only useful if operations can execute it before the issue becomes a dispute. Make the policy visible at purchase, give support authority limits, record every credit against the original payment, and route formal dispute notifications to one owner.

Confirm account-specific costs

For fees, use your account terms rather than a generic internet benchmark. HaiPay’s public pricing page lists US$0.30 per processed refund and US$20 per dispute. These published references do not confirm the terms for every account.

Confirm applicability, original transaction-fee treatment, dispute handling, and fee-return conditions for your contracting entity and payment methods in your written quote. The pricing page separately scopes its starting card-processing rates to US merchants contracting through HaiPay’s US entity. That condition does not independently establish the scope of every refund or dispute fee.

Review the card processing page and pricing page when preparing the account-specific questions.

Source: HaiPay, “Pricing” and “Chargeback Process: Step-by-Step Guide for Merchants” (published price references and commercial terms), accessed 19 October 2026.

Keep one decision owner

Identify the state first. Refund before a dispute when the customer is entitled to a remedy. Once a formal dispute opens, accept or challenge it through that process. If money was already returned, prove it—do not return it twice.

Sources

1. Visa, Visa Dispute Management Guide for Merchants — dispute lifecycle (pp. 2–6), prior-credit evidence and cardholder withdrawal limits (pp. 7–9), and Condition 13.6 response and prevention guidance (pp. 68–69); published October 2026, accessed 19 October 2026.
2. Visa, Visa Core Rules and Visa Product and Service Rules, Edition 18 April 2026 — Condition 13.6 §11.10.7.5 / Table 11-126 (printed pp. 776–777) and §11.10.7.6 / Table 11-127 (printed p. 777); accessed 19 October 2026.
3. Visa, Managing Disputes Through COVID-19: Additional Best Practices — Visa Business News Article ID AI09996 (PDF physical p. 3, historical credit/refund guidance to acquirers on valid-dispute acceptance and duplicate-credit control); published 21 April 2020, accessed 19 October 2026.
4. Stripe, Respond to Disputes — Stripe-scoped formal-dispute workflow; accessed 19 October 2026.
5. Stripe, Dispute Best Practices — Stripe-scoped guidance on accepting disputes vs withdrawal and partial-refund limitations (including Cartes Bancaires); accessed 19 October 2026.
6. HaiPay, Chargeback Process: Step-by-Step Guide for Merchants and HaiPay, Pricing — first-party published list figures (US$0.30 per processed refund, US$20 per dispute) and quote-specific commercial terms; accessed 19 October 2026.
7. Stripe, Dispute Withdrawals — withdrawal timing, evidence submission, case closure, and refund restrictions within Stripe; accessed 19 October 2026.
8. Stripe, Refund and Cancel Payments — pending refunds and disputed payments within Stripe; accessed 19 October 2026.

Disclosure: HaiPay publishes this article and provides payment services. Product and pricing references are first-party. The rules belong to the card networks, not to the publisher, and workflows can vary by network, region, provider, acquirer, and merchant agreement. This content is operational information, not legal, financial, or investment advice.