When a card payment is disputed, your team needs to establish what happened to that payment and the travel it paid for. A booking reference is a starting point. The useful record connects the sale, the customer's instructions, the supplier outcome and any money returned.

Build those connections during ordinary booking work. It is harder to reconstruct which terms applied or which document was sent when the response deadline is already approaching. This guide focuses on organising evidence; use the wider travel payments guide for the surrounding payment and consumer-protection topics.

Read the actual dispute before assembling a response

Assign one person to read the notice and record the case reference, disputed payment, reason and response deadline. They should check the provider's instructions for that case and decide who can approve the response. An allegation that a service wasn't received calls for different evidence from a claim that a payment wasn't authorised.

Stripe's response guidance says to review the dispute category and any claim details provided by the bank. It also states that a submitted response cannot be edited or supplemented through its standard submission process. Check your own provider's process before submitting, including the deadline shown for the case.

Decide whether the available facts support accepting or challenging the dispute. Keep customer-service work connected to that decision, including any refund already made. The aim is an accurate account of the transaction, with unresolved facts clearly identified.

Keep the original sequence visible

Link the booking to each payment reference and record the amount, currency and date. A fictional booking with a deposit and a later balance has two payment events to trace. If only the balance is disputed, the team should be able to identify it without confusing it with the deposit or the total booking value.

Retain the relevant version of the offer and conditions through your approved records process, together with the available evidence of customer acceptance. A screenshot of today's website cannot establish what a customer saw months earlier. Label later explanations as later explanations and preserve the dates on the original records.

Keep supplier confirmations, customer messages and amendments connected to the same booking. The booking documents guide covers keeping those versions consistent. For a dispute, you also need to explain what each record establishes and which part of the customer's claim it addresses.

Distinguish a reservation from evidence of service

A confirmation records a reservation. It doesn't, on its own, establish that every purchased service was provided. Where that is the disputed point, ask the relevant supplier for the available records and follow your payment provider's requirements for the specific case.

Stripe's category guidance includes service documentation and the date the service was received among its evidence examples. Treat those as examples to assess against the actual complaint. Don't describe a supplier booking status as proof of a traveller's attendance unless the record supports that conclusion.

If a cancellation or refund is involved, record the request, the action taken and the confirmed outcome separately. A note saying "refund requested" isn't evidence that the money was returned. Find the provider's transaction record and identify any remaining uncertainty before preparing the response.

Make the evidence readable

Stripe recommends organising evidence chronologically, grouping it by type and explaining what each item shows. Use relevant extracts with enough context to remain accurate. A long email chain can obscure the particular instruction or agreement the reviewer needs to see.

Check the permitted file types, size and submission rules with your provider. Stripe says the bank reviewing its submissions won't open external links for more information, so a link to a document store is not a substitute for the requested evidence. Have a second colleague check that the files are readable and match the case before the authorised person submits them.

Set a purpose for retaining the records

The ICO's storage-limitation guidance says personal data should not be kept longer than needed and that UK GDPR does not prescribe one fixed retention period for every record type. Agree retention and review arrangements with the person responsible for your data and relevant legal obligations. A possible future dispute isn't a reason to keep every customer record indefinitely.

Use controlled access to the evidence working folder and avoid copying unrelated traveller information into it. Follow the agreed review process when the case closes. Keep the final decision and any resulting operational action linked to the case record.

Try an evidence-retrieval exercise

Copy these fields into an internal test record: fictional case reference; disputed payment; complaint; deadline source; response owner; relevant booking records; missing supplier evidence; refund status; proposed response; reviewer; retention review. Use fictional or appropriately anonymised material for the exercise and don't submit a test dispute to a live payment service.

Accurate, accessible records help your team prepare a response, but they do not guarantee the card issuer's decision. Ask a colleague to assemble the record using your normal travel payments and booking process. Note the first missing link and give someone responsibility for fixing it.