Build the order timeline before a payment dispute response
Put the order's real events in time order before anyone submits a dispute response: the order, the payment result, messages, shipment, delivery or a delivery problem, cancellation, and refund. Tie each event to the store record it came from, and leave a contradiction visible. On a Stripe dispute, Stripe says you submit the response once and cannot edit it afterward, and card issuers do not follow links. The deadline and the outcome belong to the provider and the issuer. This timeline does not submit the response and does not predict it. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: An owner or support lead at a research-use-only peptide business who needs the order's own records gathered before a provider's dispute process.
Updated 2026-09-21
The timeline is not the dispute submission
A dispute response is the provider's process. Stripe's dispute document says a cardholder's question to the issuer becomes a dispute on the card network, and that Stripe then debits the payment amount and the dispute fee. Stripe's response document says the business is notified by email and in the Dashboard, and that the response is submitted there or through the API. It also says there is one opportunity to submit, Stripe forwards the files immediately, and the response cannot be edited afterward.
That is why the timeline comes first. It is the store's chronology, not the file the issuer receives. This page does not set a deadline. Stripe says there is a limited window and that missing it loses the dispute. Read the date on the dispute notice. Do not replace that date with a number from a general article, and do not use this worksheet as the submission form.
Use the events the order record already has
WooCommerce's order document says the order notes panel stores events such as payment results and stock changes. System notes are added for status changes, payment results, and webhook callbacks, and they are not visible to the customer. Private notes are internal. Customer notes are sent to the customer by email. A timeline that uses only the customer-visible notes will miss the payment result.
The status word is not the money movement. WooCommerce says pending payment means the order was received and no payment has been made. Processing means payment was received and the order awaits fulfillment. Refunded means an admin or shop manager fully refunded the order value after payment. The same page says a manual refund can reach the refunded status without the customer's funds having been returned. Record the gateway note and the status as two events when they disagree.
Keep the original messages and shipment evidence in the merchant’s authorized records. In this worksheet, record only whether each relevant event exists, its time, and a non-sensitive summary of a delivery problem, cancellation, or refund. WooCommerce says a cancelled order may still need a refund, so cancellation and refund are not the same event. A shipment investigation with a missing scan is a separate worksheet. Put the event on this timeline and point to that investigation rather than rewriting it.
A link is not the record
Stripe's prevention guidance says that when tracking is submitted as dispute evidence, card issuers do not follow links, so a screenshot has to be provided. Preserve the original carrier record or screenshot in the merchant’s authorized evidence system; enter only the event type and timestamp in this worksheet. A tracking URL that might change is not a preserved event. The same point applies to a policy or an email: keep the copy that existed, not a link the issuer would have to open later.
Stripe also says to keep a record of communication with the customer during the dispute. Keep the original messages unchanged in the merchant’s authorized system. Add only their timestamps and non-sensitive event summaries to this worksheet; do not copy customer message text or identifying details. If two records conflict, keep both and mark the conflict. Removing the event that weakens the story changes the record. This page does not tell you which event will matter to the issuer.
What the team can finish, and what it cannot
The team can order the events, name the source of each one, and stop a submission that is missing an event the store already has. It cannot decide the dispute. Stripe says the cardholder's bank reviews a challenged dispute and decides the outcome. Accepting or challenging the dispute is a later choice in the provider's process, not a result of having a neat timeline.
Do not put the card number, the full customer list, or the dispute file in Prism's public form. The form asks for the website, the products, and the question, and it says to leave out payment card details, passwords, and customer records. Whether the issuer will accept a particular event, and what another provider's deadline is, remain that provider's written answer.
Order-event timeline
Add only events you can point to in a store, carrier, or payment record. Leave an event blank when it did not happen or you cannot find it. Keep contradictions. Do not enter card numbers. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.
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.
Order-event timeline. The last column is for temporary notes.
Event
Where the store record is
What must stay visible
Your note
Order placed
Where the store record isThe order number, time, and status history in WooCommerce.
What must stay visibleA draft checkout record is not a submitted order. WooCommerce treats draft as a temporary checkout state.
Payment result
Where the store record isThe system order note or gateway note that says whether payment was received, pending, or declined.
What must stay visibleThe status word alone is not the payment. Pending payment means no payment has been made.
Messages
Where the store record isWhether a relevant customer or private note exists, its timestamp, and a non-sensitive summary of the event.
What must stay visibleKeep the original communication unchanged in the merchant’s authorized system; do not copy customer message text or identifying details into this worksheet.
Shipment
Where the store record isThe carrier record or a saved screenshot. A tracking link is not the preserved event, because issuers do not follow links.
What must stay visibleIf the scan is missing, say missing. Do not invent a delivery.
Delivery or delivery problem
Where the store record isThe carrier-event type or an anonymized delivery-issue summary, with the timestamp on the source record.
What must stay visibleA later status change does not erase an earlier failed or missing scan.
Cancellation
Where the store record isThe order note and the cancelled status. WooCommerce says stock returns when inventory management is on, and a refund may still be required.
What must stay visibleCancellation is not itself a refund.
Refund
Where the store record isThe gateway record showing whether funds moved. WooCommerce says a manual refund can mark the order refunded without returning funds.
What must stay visibleIf the status and the gateway disagree, keep both.
Contradiction or missing event
Where the store record isTwo times, two amounts, or a gap you cannot close from the records.
What must stay visibleLeave it visible. Do not delete the less convenient event before submission.
These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.
Limits
A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
This timeline does not submit a dispute, state a deadline, or predict the outcome.
Do not fabricate an event or omit one because it weakens the response.
Confirm any dispute-support scope separately. Neither this guide nor a consultation guarantees a dispute outcome.
Stripe disputes — checked 2026-09-21. A dispute begins when the cardholder questions the payment with the issuer. Stripe debits the payment amount and the dispute fee. The Dashboard guides the response.
Stripe respond to disputes — checked 2026-09-21. There is a limited response window, and missing it loses the dispute. The response is submitted once in the Dashboard or API and cannot be edited. The issuer decides the outcome. Communication records should be kept.
Stripe dispute-prevention best practices — checked 2026-09-21. Card issuers do not follow tracking links, so a screenshot is required when tracking is used as evidence.
WooCommerce order page — checked 2026-09-21. Order notes record payment results and stock changes. System notes, private notes, and customer notes are different, and customer notes are emailed.
WooCommerce order statuses — checked 2026-09-21. Pending payment means no payment has been made. Processing means payment was received. Refunded can be reached by a manual refund without funds being returned. A cancelled order may still need a refund. Draft is a temporary checkout state.
Prism contact — checked 2026-09-21. The form asks for the website, products, and question, and says to leave out payment card details, passwords, and customer records. A request does not submit a processing application.
Request a consultation
Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.