As of 13 August 2026, AI can only partly respond to a customer chargeback.

What to actually do

1. Hand it to a person

   The route this page recommends

   Someone with a licence or accountable authority has to sign this before it counts.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open the payment processor's chargeback notice and save the case reference, reason code, response deadline, submission instructions and evidence requirements.
   2. Gather the order record, invoice, payment confirmation, dispatch and delivery evidence, refund records, cancellation terms, product or service description and relevant customer communications.
   3. Remove full card numbers, security codes, passwords and unnecessary personal data, then paste the processor notice and the supporting records into a chatbot using the prompt.
   4. Ask the chatbot to produce the evidence table and compare each listed requirement with the original files, correcting any wrong date, amount, attachment name or customer statement.
   5. Replace every [NEEDS CONFIRMATION] marker with a verified fact or remove the statement, and check that the draft does not claim evidence that is not in your records.
   6. Ask a solicitor or payment-dispute specialist to assess the response where the amount is material, the facts are contested, fraud is alleged or the processor's rules are unclear.
   7. Submit the checked response and attachments through the processor's official dispute portal before the deadline, then save the final submission and confirmation.

   Prompt

   Help me prepare a response to a customer chargeback for a UK business. Use only the facts and documents I provide. Do not invent transaction details, delivery evidence, customer statements, legal rules, card-scheme rules or deadlines. Treat the payment processor's dispute notice as the controlling source for the required format, evidence and deadline.
   
   First, extract the reason for the chargeback, the response deadline, the required evidence and any submission limits from the processor notice. Quote or cite the relevant section for each point. Then create an evidence table with these columns: requirement, evidence available, exact source, missing evidence, and risk if omitted. Next, draft a concise response for submission, using neutral factual language and clearly separating facts from arguments. Mark every factual statement that is not directly supported by the supplied documents as [NEEDS CONFIRMATION]. Do not include full payment-card numbers, security codes, passwords or unnecessary personal data. End with a checklist of facts, attachments and submission details that I must verify before sending. If the documents do not establish that the chargeback should be rejected, say so plainly and identify what a solicitor or payment-dispute specialist should assess.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.