A refund failed after it was requested

Identify the failed refund rather than the original payment

Start with the refund reference in the notice and open it within the account that processed the payment. Match it to the original payment, refund amount and currency. Record when it was requested and when the provider recorded failure. If the payment has several partial refunds, identify the affected refund separately instead of treating every refund on that payment as failed.

A failure notice about the refund does not mean the original payment failed. It means the attempted return of funds needs investigation. Likewise, the absence of a credit in the buyer's report does not by itself establish provider failure. If the provider still shows pending or success, use that actual status rather than forcing the case into this workflow. Keep the time of your last status check so a later update can be recognized.

Stripe's documentation describes available balance as the funding source for refunds. For card transactions, insufficient available funds leave the refund pending until sufficient balance is available; other payment-method types can fail instead. Pending funds are not the available balance. Diagnose the state and method shown in the account before interpreting a balance shortage as a failed card refund.

Read the supplied reason without expanding it into a diagnosis

Stripe documents that a bank or issuer may be unable to process a refund. Where available, the Refund record contains a failure_reason. Preserve the actual value and its documented meaning. A missing or unknown reason remains unknown; it is not evidence that the customer closed the card or that a store plugin caused the failure.

The documented reasons distinguish several next questions. An expired or canceled card reason and a lost or stolen card reason concern the original card. A declined reason identifies a decline by Stripe's financial partners without establishing every underlying cause. The insufficient_funds failure reason describes a refund that remained pending for insufficient funds and crossed its expiry window; it is different from a card refund that is still pending.

If the reason is charge_for_pending_refund_disputed, Stripe says the charge was disputed while the refund was pending and directs the merchant to accept or challenge that dispute rather than refund again. Record the dispute reference and use the provider's dispute process. Do not attempt a second credit to make the store's refund label look complete.

Some non-card methods without native refund support use requires_action, with Stripe's next_action carrying the actual instructions, notification details and expiry. That is a method-specific collection process, not a generic fix for a failed card refund. A requires_action record should be followed through its own authorized provider workflow rather than relabeled failed.

Trace the return to the correct balance

When a bank or issuer returns a failed refund, Stripe says it adds the returned amount back to the Stripe balance. The documented Refund field failure_balance_transaction identifies the balance transaction representing that return. Use the linked record where available; an unrelated increase in the total balance is not sufficient to identify this movement.

Record the return entry's reference, amount, currency and posting date alongside the failed refund. If the return has not been found, state that it is not yet verified and keep the unresolved movement with the provider. The documentation describes a return process that can take time; this page does not promise a date for the funds to reappear.

Identify whose balance you are examining if a platform is involved. Stripe specifically says failed refunds on Connect destination charges return to the platform's Stripe balance. Do not infer that the merchant's bank account or connected-account balance received those funds. A return to the provider balance also does not mean the buyer received the refund. It records the attempted credit coming back.

Resolve the buyer's message and the next authorized step

Compare the provider's latest state with what support last told the buyer. If the buyer was told the refund had completed and the record now shows failure, correct the statement using the known status and the next follow-up your team will perform. Distinguish the refund's failure from whether the returned funds have already posted. Set a date to check the record again without presenting it as an arrival guarantee.

Stripe's failed-refund guidance says an alternative resolution may be needed when a refund cannot complete. That does not authorize an improvised transfer, collection of a new card number or an immediate duplicate refund. Ask the provider to confirm what action is appropriate for this failed attempt and original method, whether funds have returned and what restrictions or overlapping dispute apply. Record the written instruction and have the merchant's authorized owner decide and record the next action.

If the operational defect is that staff messages or store records fail to reflect provider refund outcomes, bring that specific mismatch to a scoped Prism checkout-review consultation. Describe the platform, observed statuses and unresolved handoff without submitting customer records or payment details in the public form. Confirm any investigation or implementation responsibilities before work; a consultation itself does not move money.

Failed refund trace

Use one row set for one actual failed refund. Record references only in the merchant's authorized internal worksheet and leave sensitive payment or customer details out. Mark an unobserved state unknown. The completed trace should show the failed attempt, any returned funds and the instruction authorizing the next step.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.