For a physical order, a team may look for shipping and delivery records. A course, software account, downloadable product or professional service leaves different evidence. The challenge is to show the relevant events in a form that someone outside your business can understand.
Start with the promise made to the customer, then connect the payment to the records showing what happened afterward.
Define the event you need to establish
Separate account creation, access granted, content delivered, service performed and customer acceptance. These events can occur at different times and may have different meanings. Decide which one addresses the allegation before collecting a large set of activity logs.
Stripe’s evidence guidance identifies relevant system activity as potentially useful for digital-goods disputes. The important editorial task is explaining the connection: which customer account, which purchased item, which event and which time period does a record concern?
Connect the purchase to the user or project
Document how your order or invoice links to the account, license, course enrollment or project. Use stable identifiers that your team can reconcile. If the buyer and end user differ, preserve the authorized relationship and explain it when relevant rather than silently treating them as the same person.
For business services, a purchaser may pay on behalf of a team. For a digital gift, one person may purchase access for another. These situations require accurate context. A matching email address can help locate records, but it should not be treated as universal proof of identity or authority.
Choose records that answer the complaint
- Access complaint: Review provisioning, invitation, activation and relevant support records.
- Delivery complaint: Identify the file, message, project milestone or content made available.
- Quality or scope complaint: Compare the agreed description with the relevant delivery and resolution history.
- Cancellation complaint: Connect the request, effective date, account changes and billing timeline.
- Authorization complaint: Review the payment and account context through the processor’s applicable evidence requirements.
The record set should fit the actual claim. Showing that an account logged in may be useful context, but it does not automatically establish that every promised service was delivered satisfactorily.
Translate technical events into plain language
Explain the meaning of each event label and preserve the relevant timestamp and time zone. If a log entry represents an automated background action, say so. Do not describe an automatic download request as a customer personally reading the file unless the record supports that conclusion.
Use a readable export or excerpt and include the context needed to interpret it. Remove unrelated activity, secrets and unnecessary personal information. Keep the original source under the business’s access and retention rules so the team can verify the excerpt later.
Example: a course-access complaint
Imagine a customer says they could not access a purchased course. The payment record and enrollment record match, but the invitation email bounced. A later account event shows an administrator reset access. Those facts tell a different story from simply stating that an account exists.
The team should review the support history and the resolution actually provided. The same investigation can reveal an improvement: an owner for failed invitations and a confirmation that the customer can access the purchase. This fictional example demonstrates the value of understanding the delivery process before preparing a response.
Design better records before the next dispute
Ask product, operations and support to identify the events that establish the customer journey. Confirm which records exist, who can retrieve them and how long they are kept under an approved policy. Avoid collecting extra information solely because it might someday be useful.
A good evidence process makes existing business events understandable. It should help your team answer the current claim accurately while making future delivery and support handoffs easier to review.