Replace the wrong order evidence before final submission
Open the case, its linked payment, the corresponding store order and each draft attachment in your authorized systems. Verify the relationship through the records' references, not just a familiar customer name, matching amount or file name. Remove evidence confirmed to belong to another order from this draft, replace it only with verified records, and preserve the original files and correction history internally. For Stripe, the evidence response is submitted once and cannot be edited afterward, so first establish that the response is still a draft.
For: A research-only merchant's case owner who has found a possible wrong-order attachment in an unsubmitted payment-dispute response.
Read the case type, current response state and deadline directly from the provider's case record. This page concerns a draft that has not been finally submitted. On Stripe, a formal dispute may be accepted or challenged; accepting an inquiry does not resolve it. Identify which process is actually open before treating a button or status as the final response.
Stripe documents one evidence submission and no editing afterward. If the response has already been submitted, do not describe an internal replacement file as a corrected issuer submission. Record the error and ask the provider what, if any, route remains for that case. A support message does not itself reopen the response.
For a draft, give its owner the original deadline and the identified mismatch immediately. The correction work does not extend the response window. Keep the accept-or-challenge decision with the person authorized to make it rather than allowing an attachment correction to become an accidental final submission.
Prove the relationship through references
Start from the disputed payment named in the provider's case. Follow the payment-to-order relationship in the merchant's records, then follow that order's references to the evidence. The questions are whether this is the payment in the case, whether this is its order, and whether the attachment documents an event on that order. A buyer can have more than one order; a customer-name match does not complete that chain.
Open the actual attachment contents. A file saved under the correct order name can contain another order's invoice, messages or shipment record. Compare the original document reference and relevant event date inside the file against the source system. Use amounts and dates as cross-checks, not substitutes for a missing relationship.
Classify each attachment as matched, mismatched or unresolved. A conflict between references needs an explanation from the record owner. Do not relabel the file to make it appear to match, copy a different order's tracking reference or infer that an unmatched payment must belong to the only order you found.
Correct the association while keeping the history
Remove a confirmed wrong-order attachment from the active draft. Preserve the original source file in its proper authorized record and log which draft attachment was removed, why it was wrong, who corrected it and when. Preserving an audit trail means keeping a controlled internal history; it does not mean sending the unrelated buyer's records to the issuer.
Obtain the replacement from the correct order's source record and repeat the reference comparison on its contents. If the correct evidence cannot be retrieved, mark that gap for the case owner. Another order's document is not an acceptable substitute, even when it appears to show the same fulfillment practice.
Read the response text after replacing files. A sentence describing delivery, communication or a refund may still rely on the removed attachment. Correct the associated reference and narrow any statement the verified replacement does not support. Retain relevant contradictions within the actual case; remove unrelated evidence because it belongs elsewhere, not because it is inconvenient.
Finish the handoff with a verified draft
Before the authorized owner submits, reopen the saved draft and verify that its case reference, attachments and narrative still correspond. Record that the correction was made in the provider's draft, not merely in a local folder. If the provider's interface does not let you confirm the replacement, keep that uncertainty explicit.
The worksheet is an index of comparison results, not the evidence package. Keep customer messages, full addresses and original documents inside authorized systems. PCI SSC FAQ 1085 prohibits sending unprotected card account numbers through email, instant messaging, SMS or chat; a request to resolve a mismatch does not make those channels appropriate for card data.
Once the relationships are checked, the owner can make the submission decision using the actual case and deadline. The issuer still decides the outcome. For a Prism consultation about an order-record or checkout handoff issue, describe the mismatch without customer files. Confirm dispute-support responsibilities, scope, fees and terms before work; an inquiry does not submit the case.
Case-to-evidence match
Use one sheet for the affected draft. Enter only non-sensitive internal aliases and match results; keep the mapping to full case, payment and order references in authorized systems. Repeat the attachment rows for every file under question. Matched means the association is verified, not that the evidence wins the dispute.
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-to-evidence match. The last column is for temporary notes.
Check
Record to compare
Decision the comparison supports
Your result
Case reference
Record to compareThe actual provider case, its linked payment, case type, response state and stated deadline.
Decision the comparison supportsConfirm this is the intended case and the response remains editable before replacing an attachment.
Evidence reference
Record to compareOpen each draft file and compare its internal document reference with the source record; use a non-sensitive alias here.
Decision the comparison supportsA correct filename alone does not establish that its contents belong to the case.
Order match
Record to compareFollow the case payment to the store order, then the order to the attachment's source event.
Decision the comparison supportsMark matched, mismatched or unresolved. A shared name, amount or date is insufficient by itself.
Mismatch reason
Record to compareIdentify the exact inconsistent relationship, such as an attachment linked to a different order, without copying customer details.
Decision the comparison supportsRemove the wrong association from the draft while preserving the original internally.
Correct record owner
Record to compareName the role or team that can retrieve the genuine replacement and the source system it should come from.
Decision the comparison supportsIf no replacement exists, leave a documented evidence gap rather than borrowing another record.
Correction history
Record to compareRecord removed and replacement file aliases, correction time and responsible role in the internal change log.
Decision the comparison supportsPreserve what changed without distributing the unrelated evidence.
Saved draft and narrative
Record to compareReopen the draft; compare its remaining attachments and the statements that cite them.
Decision the comparison supportsConfirm the old association is gone and the narrative no longer relies on it before final submission.
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 one-submission rule applies to Stripe's documented dispute response. Use the actual provider's rules for another rail.
Preserve relevant unfavorable records for the correct case; removing a wrong-order file is not permission to alter originals or hide a contradiction.
Do not include card numbers, authentication codes, private links or customer documents in this worksheet or the public inquiry. The issuer decides the dispute.
Stripe respond to disputes — checked 2026-09-21. A formal dispute may be accepted or challenged; evidence is submitted once and cannot be edited afterward. The response window is limited, the issuer decides and communication records should be preserved. Accepting an inquiry does not resolve it.
PCI SSC FAQ 1085 — checked 2026-09-21. Unprotected primary account numbers must not be sent by email, instant messaging, SMS or chat. This concerns card-number handling, not a prohibition on ordinary non-sensitive case coordination.
Get help with store operations
Need help with the order, email or fulfillment step itself?