Restaurant Chargebacks UK: How to Prepare a Response

Start by finding the disputed payment, reading the reason and checking the deadline in your provider's notice. Then decide whether to accept the dispute or submit evidence through the provider's approved process. Build your response around the specific payment and complaint, rather than sending every document your restaurant holds.

This is a practical preparation checklist. Your payment provider's instructions govern the response you submit; no checklist can promise that a dispute will be decided in your favour.

What is a restaurant chargeback?

Visa describes a chargeback as a process through which the cardholder's bank seeks money back from the retailer's bank for a disputed purchase. It is a card-scheme process, rather than a legal right in itself ^[1].

For an owner, the useful first distinction is between a complaint you are discussing with a guest and a formal dispute already raised through the payment system. Ask your provider which stage the notice represents and what action is required. Do not treat a request for information as if the case has already been resolved.

Keep your original booking and service records intact. Start a separate case note for the dispute so your team can distinguish what happened at the time from what you have written in response.

Check the notice before searching for evidence

Read the notice in your provider's usual account or verify it through a known support route. Record the case reference, transaction reference, amount, date, dispute reason and submission deadline. Assign one person to own the response and another to check it before submission.

Do not borrow a deadline from a different provider's article. Square's UK guidance, for example, specifies a seven-day evidence window for its process ^[2]. That is an example of why you should follow the actual notice, not a general deadline copied into a restaurant policy.

Put the deadline in the owner's working calendar and leave time to resolve missing records. If the notification is unclear, contact your provider promptly with the case reference and a precise question about what they need.

Match the payment to the restaurant visit

Start with the transaction record and trace it to the booking, table bill, collection order or event. Avoid matching solely by a similar amount: a busy restaurant can have several identical bills.

Make a short worksheet:

Note uncertainty explicitly. If a record cannot be found, say so internally and ask the provider what alternative evidence may be relevant. Do not recreate a receipt and present it as the original.

Answer the reason raised

A response should address the actual issue. For a disputed duplicate, compare the payment references and amounts. For a disagreement about service, identify what was agreed and the relevant service record. For a cancelled booking, locate the terms shown before payment and the cancellation conversation.

Square's UK evidence guidance distinguishes fraud claims from complaints about service or an incorrect charge, and asks merchants to provide clear, relevant documentation ^[2]. Use that distinction to organise your questions, while following your own provider's case requirements.

A receipt and a clear account of events are more useful than a long description of how well the restaurant normally operates. Keep opinions about the guest out of the response. If your records reveal an error, explain it to the provider rather than trying to make the paperwork fit a different story.

Prepare a short chronology

Write the events in date order. Include when the booking was made, when payment was taken, when service occurred or was cancelled, and when the guest contacted you. Put the document reference beside each factual point.

Example: a fictional catering booking includes a £100 deposit and a later £300 balance. If the notice concerns the £100 transaction, identify that payment and explain how it relates to the £400 booking. Do not submit the £300 receipt as though it proves which deposit payment is being challenged. These amounts illustrate record matching, not a chargeback rule or recommended deposit.

Keep the chronology short enough for someone outside the restaurant to follow. Explain any restaurant-specific abbreviations. Where an email chain is relevant, include the part that establishes the point and enough context to avoid changing its meaning.

Check refunds with the provider

Before taking further action, check whether a refund has already been started or completed and whether a formal dispute is open. Ask the provider how to handle those two records together. Do not assume a conversation with the guest closes the payment-system case.

myPOS's own merchant guidance describes responding to its notification with supporting evidence if the merchant wants to defend a chargeback, and highlights the importance of detailed records and timely replies ^[3]. It does not establish the fee or deadline for every TrustPOS customer's agreement.

Keep any refund reference with the case. When staff have promised to look into a refund, distinguish that promise from a completed transaction. The response should say what your records show, not what someone intended to do after service.

Handle deposit disputes carefully

A booking deposit needs more than a payment receipt. Locate what the guest was booking, the policy presented before payment, any agreed changes and the messages about cancellation. Have the responsible manager check the policy and circumstances before explaining any amount retained.

Do not assume that calling a deposit non-refundable is enough to justify keeping it: CMA guidance explains that businesses cannot rely on unfair terms ^[5]. Use appropriate advice for the actual terms and circumstances. Our phone-payment guide explains collection methods; it does not decide a guest's cancellation rights.

For future bookings, test whether staff can find the confirmation and payment reference during a busy shift. A process that only one person understands is difficult to explain when that person is away.

Keep card data out of the evidence folder

Use the records and references your provider asks for through its approved channel. Do not collect extra payment-card information to strengthen a case. PCI Security Standards Council guidance prohibits storing card verification codes after authorisation, including for card-on-file arrangements ^[4].

Before upload, check documents for unrelated customer information, passwords and unnecessary card details. Ask the provider how required records should be supplied securely. Keep access to the working case limited to the staff dealing with it.

Submit, save and improve the process

Check the case reference, files and deadline one final time. Submit using the provider's instructions and retain its confirmation. Record the response date and next action, then keep monitoring that case through the normal support route.

Afterwards, review the gap that made the response difficult: an unclear bill, a missing confirmation or a refund that nobody recorded. Turn that finding into one staff-process improvement. When reviewing a new card machine or till, ask the supplier to demonstrate how you retrieve the records your restaurant actually needs; a lower headline rate does not answer that question.