Orders and support

A link is not the same as evidence the issuer can review

If the response requires the issuer to open a carrier page, policy URL or other external page to see the evidence, the record is not contained in the response. Stripe says card issuers do not follow links and specifically calls for a screenshot when tracking is used as evidence. Preserve the authentic source, identify the relevant content and include it through the format supported by your provider's dispute process. A link can remain an internal reference; it should not be the only way to read the evidence.

For: A support or operations lead at a research-only merchant preparing records for a card dispute through the merchant's actual payment provider.

Updated 2026-10-01

Judge the response by what is inside it

Read the prepared response without opening any external link. Identify each factual statement that becomes unsupported under that constraint. A tracking URL without the delivery event leaves the event outside the response. A link to a policy leaves the policy's wording outside it. A link to a private support system leaves the communication outside it, regardless of whether your own team can open that system.

Stripe's dispute-prevention guidance makes the tracking case explicit: issuers do not follow links, so tracking evidence requires a screenshot. This is evidence-accessibility guidance for Stripe's dispute process. For another provider, confirm its permitted evidence fields and upload format from that provider's actual instructions. Neither a working Stripe integration nor this documentation establishes that Stripe accepts a particular research-only business.

Preserve the record before preparing a readable extract

Retain the original carrier record, policy version or communication in the merchant's authorized evidence storage. Prepare a readable copy that includes the portion relevant to the claim, with enough surrounding context to show what the record says. Keep the source date distinct from the date you captured it. A current carrier status or policy page should not be described as a copy of an earlier state unless your records establish that.

For tracking, make the event and its associated shipment reference legible in the evidence copy used through the provider's secure process. Do not merely capture the page header or a button that opens the tracking details. For a policy or message, preserve the wording and context actually available; a new policy cannot establish what a buyer saw on an earlier order.

Keep contradictory events or missing information visible in your preparation notes. Do not alter a scan, invent a timestamp or reconstruct a customer conversation to make the response appear complete. A missing authentic record remains a gap even when a polished screenshot or explanation would be easy to create.

Match each record to the supported submission form

Separate the internal source from the material to be submitted. The internal source is where your team can retrieve and authenticate the record. The submission copy is what the issuer will actually receive through the provider. Record which available text field or supported attachment will carry the relevant content; do not assume that a share link is an attachment.

Review the provider's current upload instructions for the actual case before preparing files. This page does not prescribe file extensions, sizes or page limits. Open the prepared material and verify that the relevant text or event is readable without logging into your store, following a link or accessing your private evidence system.

Review sensitive information separately from evidential relevance. Keep originals unchanged in authorized storage, and prepare the submission copy according to the provider's secure-process requirements. Do not indiscriminately remove the references needed to connect a record to the disputed order. The worksheet below records non-sensitive descriptions and internal reference labels, not customer messages, full addresses or card information.

Resolve accessibility before the final submission

Stripe says evidence is submitted once and cannot be edited after submission, within the response window shown for the dispute. That makes an inaccessible attachment or a link-only assertion a preparation issue to resolve before the authorized owner submits. Read the actual deadline rather than assuming that collecting more records extends it.

Being readable does not make evidence relevant or decisive. The response still has to address the stated dispute reason; the issuer decides the outcome. A complete chronology and a reason-specific evidence selection are separate tasks from converting links into reviewable records. If the case is an inquiry rather than a formal dispute, do not assume that accepting the inquiry resolves it.

For a Prism checkout consultation about the store's evidence handoff, describe which record the workflow cannot preserve or retrieve and where the handoff fails. Confirm any requested dispute-support scope, responsibilities, fees and terms before work. Keep the dispute file in the provider's authorized process, not in the public consultation form.

Evidence format conversion

Use this as an internal preparation index for each real record you intend to rely on. Repeat the check for every link-dependent claim. A record is ready for the format check only when the relevant content is readable in a supported submission field or file and its authentic original is retained. Do not paste customer content or private URLs here.

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.

Evidence format conversion. The last column is for temporary notes.
Preparation checkWhat to record from the real evidenceWhat an unresolved finding meansYour finding
Source recordA non-sensitive reference label for the original carrier event, policy version or communication, with its record date.A URL without a retained record leaves authenticity or historical content unestablished.
Relevant excerptA description of the specific event or wording the response needs, and the context that must accompany it.If the content is missing from the proposed submission, the issuer would have to open an external source.
Supported submission formThe field or attachment option permitted by the actual provider process and the applicable instructions.An internal share link is not a supported evidence file merely because staff can open it.
Tracking captureWhether the prepared screenshot visibly contains the relevant event and its connection to the shipment.A screenshot of a tracking link alone still leaves the event outside the response.
Authenticity referenceThe retained original's internal reference, its original date and the separate capture date.Do not present a later capture as proof of what a page contained at the time of purchase.
Sensitive detail reviewWhether the secure submission copy contains the necessary references and omits unrelated sensitive data under provider instructions.Resolve required content through the secure process; never put card data, credentials or customer records in this table.
Final readability and ownerWho checked the prepared content without external links and who controls the actual submission deadline.A readable package still needs reason-specific review and an authorized submission; it does not predict an issuer decision.

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 documented process does not establish another provider's file requirements, deadlines or outcome.
  • Preserve authentic records and contradictions; do not fabricate screenshots, events, policy history or communications.
  • Do not enter card numbers, authentication codes, private link tokens, API secrets, full bank details or identity documents in the worksheet or public inquiry.

Sources

  • Stripe dispute and fraud prevention — checked 2026-09-21. Stripe advises tracking and delivery confirmation for physical goods when possible. Card issuers do not follow links, so tracking submitted as evidence needs a screenshot; this does not establish merchant eligibility.
  • Stripe respond to disputes — checked 2026-09-21. Stripe distinguishes a formal dispute from an inquiry, limits the response window, allows evidence submission once without later editing, and assigns the outcome to the issuer. Accepting an inquiry does not resolve it.
  • Prism solutions — checked 2026-09-21. Published support is a storefront review, processing preparation, and help with a provider's website questions. Scope, fees, and terms are discussed before work. The provider decides eligibility and account terms.

Get help with store operations

Need help with the order, email or fulfillment step itself?