Record the issuer outcome without overstating what it proves
Record the issuer's decision as reported by the provider, its date, the case reference and the amount it concerns. Then separately record which order or support issue remains and who owns it. A won or lost result answers the formal case; it does not by itself establish delivery, completion of a return, fulfillment of a merchant promise or the customer's intent. Close only the work that the records actually resolve.
For: The operations or support owner of a research-only store handing an order back to the team after a card-dispute decision.
Establish that there is an issuer decision to hand over
Open the provider record for the case connected to the actual order and payment. Preserve the event type, exact status, case reference and decision date in the private case file. Stripe distinguishes formal disputes from inquiries and early fraud warnings, and the issuer decides whether a challenged dispute is won or lost. A response submission, a customer message or the absence of a new alert is not a substitute for that outcome record.
If the merchant accepted the dispute, record that action as the merchant's decision not to contest it. Do not describe acceptance as an issuer finding after review of the merchant's evidence. Stripe also states that accepting an inquiry does not resolve it. A record that still describes an inquiry or an open case requires its own follow-up instead of being marked as a completed dispute decision.
Where the provider does not expose a decision date, distinguish the date on a notice from the date your team first read it. Leave the issuer decision date unknown if that is what the available record requires. This preserves a usable chronology without manufacturing a more precise outcome than you received.
Attach the outcome to the amount and records it covers
Connect the outcome to the disputed amount and currency rather than copying the original order total into every field. Stripe documents that the disputed amount can differ from the original charge. The result for that amount should not silently close unrelated payments or items on the same order.
Keep the outcome record and any associated financial entries identifiable as separate records. If the team also needs to reconcile a balance movement, link the actual entry and mark an unmatched movement as a reconciliation question. Do not use the word won or lost as a substitute for an observed balance entry, a bank receipt or a refund record.
This handoff should preserve what was decided without adding an explanation that the provider never supplied. A result alone does not prove that a customer acted dishonestly, that every merchant statement was correct, or that a later case will receive the same result. It also does not establish future processing eligibility for the business.
Read the order again for unresolved work
Compare the decision with the latest actual fulfillment, return and support records. A parcel investigation can remain open, a return can remain unverified, and a merchant promise can still require a documented answer. These are questions to inspect in the real order, not presumed consequences of either outcome. Keep the earlier evidence and add the later decision so the order history remains intelligible.
For each remaining issue, record the last confirmed fact, the missing fact and the person authorized to decide the next action. If no issue remains, identify the records that support closing the support task. Do not choose a replacement shipment, a refund or a renewed charge merely because the case changed status. Any further action must account for what has already happened to both the order and the payment.
Stripe says a refund cannot be issued outside the dispute process while a dispute is open. If the purported outcome and the current provider status conflict, retain that restriction and clarify the actual case state before treating a refund as available. A final outcome is also not evidence that every possible refund action is now permitted; use the actual payment record and applicable provider instructions.
Give support a factual closure note and an owner
The internal handoff should state the reported outcome, its source and date, the amount concerned and the remaining work. Assign a next check or reply based on a real operating commitment. Keep completed response work separate from unresolved order work so neither team assumes the other is handling it.
A customer-facing update should state only the facts and actions the merchant can substantiate. Do not turn a bank result into an accusation, a claim that the bank confirmed delivery or a promise that the issuer will act by a date your team cannot control. Preserve the communication in the private order record and keep account and payment details out of ordinary public channels.
If repeated handoffs expose a mismatch between store messages, payment records and support actions, describe that gap in a Prism checkout-review consultation. Confirm the requested review or implementation scope, responsibilities, fees and terms before work starts. The consultation does not reopen the case, change the issuer's decision or establish account approval.
Case outcome handoff
Read the source records privately and use anonymized status and ownership notes here. Keep case closure, financial reconciliation and order resolution distinct. If a row lacks evidence, assign its follow-up rather than marking the entire customer issue resolved.
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.
Case outcome handoff. The last column is for temporary notes.
Handoff field
Evidence to read
What the next owner needs to know
Your anonymized note
Issuer outcome
Evidence to readThe provider's exact final case status and whether the merchant accepted or challenged it.
What the next owner needs to knowDistinguish a reported issuer decision from merchant acceptance, an open inquiry or a warning.
Decision date
Evidence to readThe dated provider outcome or notice, plus when your team observed it.
What the next owner needs to knowPreserve unavailable dates as unknown; observation time is not automatically decision time.
Provider record
Evidence to readThe private case-to-payment-to-order association and the amount and currency concerned.
What the next owner needs to knowLimit the handoff to the actual case; do not substitute the full order total for the disputed amount.
Financial entry
Evidence to readAny recorded movement associated with the result and its reconciliation status.
What the next owner needs to knowName an unmatched entry separately rather than asserting that the outcome proves a bank receipt or refund.
Remaining order issue
Evidence to readThe latest actual fulfillment, return, refund and merchant-promise records.
What the next owner needs to knowIdentify the unresolved fact or the evidence supporting closure of the support task.
Support owner
Evidence to readThe person authorized to decide the next action and the team's actual follow-up commitment.
What the next owner needs to knowGive unresolved work an owner without assuming the dispute-response owner also handles fulfillment.
Communication and closure basis
Evidence to readThe private customer-update record and the evidence used to close each task.
What the next owner needs to knowReport supported facts without inferring customer intent, delivery or a future outcome from the issuer result.
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.
Limits
Stripe's distinctions between disputes, inquiries and warnings and its open-dispute refund restriction are provider-specific; do not apply them indiscriminately to other payment methods or providers.
An issuer outcome does not determine every support obligation, customer intent, legal issue or future account-eligibility decision.
The worksheet and public consultation form are not places for customer messages, identity documents, card or bank details, private payment links or credentials.
Stripe respond to disputes — checked 2026-09-21. The merchant can accept or challenge a formal dispute; accepting means not contesting the amount. The issuer decides won or lost, communication records should be kept, and accepting an inquiry does not resolve it.
Stripe, how disputes work — checked 2026-09-21. Formal disputes, inquiries and early fraud warnings are different events. Stripe restricts refunds outside an open dispute, and the disputed amount can differ from the original charge. These facts do not establish the remaining fulfillment or support state.
Get help with store operations
Need help with the order, email or fulfillment step itself?