Responding to a Credit Not Processed Chargeback

A credit-not-processed dispute says the merchant owed the customer a refund or credit and failed to deliver it. The decisive record is usually not the original purchase; it is the return/cancellation and refund ledger.

Reconstruct the refund obligation

Identify: - original charge and order; - customer request date; - return authorization; - item return-delivery date if physical; - cancellation date if service; - refund policy version; - amount eligible for refund; - restocking or nonrefundable amount only if properly disclosed and lawful; - promised refund timing.

If the customer never completed the return required by an accepted policy, show that. If they did everything required, move to the processor record.

Prove the refund with a transaction, not an internal status

Strong evidence includes: - refund/credit transaction ID; - original charge ID; - amount; - date submitted; - date succeeded/settled if exposed; - card/account credited where processor shows it.

“We clicked refund” or a CRM note is weaker than a payment-processor record.

If the refund failed, do not represent it as completed. Find out why and correct it.

Reconcile partial refunds

A customer may return one of three items. Show the line-item values and the partial credit.

If shipping or service fees were nonrefundable under the policy, identify the disclosure and explain the calculation. Avoid a one-line “partial refund per policy” note.

If you gave store credit rather than a card refund, confirm that the customer agreed to that remedy when relevant. A store-credit balance may not answer a cardholder claim that a promised card credit never appeared.

Timing matters

Processors and banks can take time to display a refund. If the merchant issued the refund before the dispute, include the refund timestamp and any customer notification.

If the chargeback opened before you processed the refund, check the processor workflow. Some platforms prevent or complicate refunding after a dispute has started because the disputed funds are already being handled.

Do not create a second reimbursement without understanding the case status.

When no refund was due

If the customer falls outside the return/cancellation terms, submit the policy that governed the purchase and evidence it was displayed or accepted.

Then show the facts: - request arrived after deadline; - item was never returned; - excluded custom item; - service already completed; - cancellation was after nonrefundable cutoff.

A policy alone is not enough if it was hidden or inconsistent with law. Keep the argument factual.

Prevent credit disputes with a refund queue

Every refund should have states such as requested, approved, submitted to processor, succeeded, failed, and customer notified.

Alert when a refund remains approved-but-not-submitted beyond an internal SLA. Reconcile processor failures daily.

Use the original payment ID so support staff can see whether the money actually left the merchant account and whether the same order is now in dispute.

Shopify’s guidance for credit-not-processed disputes similarly focuses on refund/return policy, communication, actual refund evidence, or the reason a customer was not entitled to a refund.

A strong response can be very short: “Customer returned item May 3. Refund of $128.40 was processed May 4 against payment X and marked succeeded; Exhibit 2 is the processor record.” That is better than ten pages of order screenshots.

Reconcile the refund across three systems

A credit-not-processed dispute should be tested against the merchant’s order system, processor record, and bank-settlement record. The order system may say “refunded” even when the processor request failed; the processor may show a successful refund while the customer is searching for it under a different statement date.

Capture the refund amount, transaction or refund identifier, date submitted, destination card or payment instrument reference, and processor status. If only part of the purchase was refunded, explain the calculation and show why the remaining amount was retained. When a refund was promised but never actually initiated, do not contest the dispute merely because an employee wrote “refund approved” in a ticket.

If the refund and chargeback crossed in time, flag that explicitly. Merchants should avoid creating a double credit by blindly issuing another refund after a dispute has already removed funds. Follow the processor’s instructions for the specific case and use the case timeline to explain whether a separate credit has already settled.

Distinguish a refund from a void

A void cancels a card transaction before final settlement; a refund is a separate credit after settlement. Processor dashboards may display both as “reversed” in casual language. Use the processor's transaction type and identifiers so the packet does not claim a refund was issued when the original authorization was simply voided.

Use the processor's settlement date

Customers often search by the date a merchant initiated a refund, while card statements can show the credit later. Record both initiation and settlement status when the processor provides them, and avoid promising a posting date the merchant cannot control.

If the credit failed because the original card was closed or replaced, follow the processor's current refund guidance and preserve the failure message rather than inventing an alternate credit outside the case workflow.