A transaction-focused method for preparing a UK card-payment complaint: identify the payment, merchant evidence, authorisation issue, refund history, bank case and escalation record.
Identify the transaction exactly
Start with the card statement and record the transaction as the bank shows it: posting date, transaction date if different, merchant descriptor, amount, currency and any reference available. Then connect that entry to the merchant-side record such as the order confirmation, receipt or booking. Merchant trading names and statement descriptors often differ. A complaint should explain that relationship rather than assuming the bank will recognise a brand name that does not appear on the statement.
If several payments are disputed, give each transaction its own line. Do not combine them into one total unless they genuinely arise from a single order and the calculation is shown. Keep credits and reversals separate from purchases. A temporary pending item, a completed debit and a later reversal are different processing states. The chronology should show when the account was actually debited and whether the balance changed again.
Classify the problem before choosing a remedy
An unauthorised card transaction is not the same problem as non-delivery by a merchant. Duplicate processing is different from dissatisfaction with quality. A promised refund that never arrives is different again. Write the factual category at the top of the working file: authorisation, duplicate amount, wrong amount, cancelled recurring payment, non-receipt, defective performance, merchant insolvency, refund failure or another defined issue. More than one category can exist, but the supporting evidence should be kept distinct.
This classification matters because the bank may consider different legal and card-scheme routes. Chargeback is a card-scheme process rather than a statutory right in itself. Section 75 of the Consumer Credit Act 1974 may be relevant to certain qualifying credit-card transactions. Debit-card disputes and credit-card claims do not automatically follow the same route. Check current bank and Financial Ombudsman guidance against the actual card type and transaction.
Build the merchant evidence pack
For goods, retain the product description, order, dispatch information, delivery tracking, photographs if condition is disputed, return request and proof of return. For services, retain the booking, scope, scheduled date, cancellation terms and evidence of what was delivered. For subscriptions, keep the sign-up terms, renewal notice, cancellation request and confirmation. The objective is to show the transaction lifecycle from agreement through the event that created the dispute.
Record attempts to resolve the matter directly with the merchant. Save email threads, chat transcripts and call reference numbers. Where the merchant promises a refund, write down the promised amount, method and date. A merchant’s statement that a refund has been processed should be compared with the account statement. If a refund reference or acquirer reference number is given, preserve it for the bank.
Handle unauthorised-payment evidence separately
If the complaint is that the cardholder did not authorise the transaction, preserve the bank notification time, card replacement or security steps and any message received around the payment. Do not place passwords, full card numbers, one-time passcodes or authentication secrets into the complaint bundle. The bank already has secure account identifiers; ordinary correspondence should use only the minimum details needed to identify the disputed entry.
Write what the cardholder actually knows. For example, state whether the card was in their possession, whether they recognise the merchant, whether they made any related purchase and when they first saw the debit. Do not invent a theory about how fraud occurred. Authentication and device evidence may be held by the bank or payment processor; the customer’s record should distinguish observed facts from information only the institution can verify.
Track the bank’s investigation as a separate case
Once the bank is notified, create a case log containing the complaint date, channel, bank reference, documents submitted and every later request. If a provisional credit appears, record it as provisional unless the bank confirms final resolution. Banks can reverse temporary credits after investigation. The account ledger and the complaint correspondence should therefore be reconciled whenever the balance changes.
If the bank rejects the complaint, identify the precise reason. It may refer to authorisation, merchant evidence, time limits, the type of transaction or missing documents. A review or escalation should answer that reason with the relevant evidence. Repeating the original narrative without addressing the bank’s explanation rarely improves the record. Preserve every decision version because an explanation may change after further evidence is supplied.
Keep chargeback and Section 75 analysis distinct
For a potential chargeback, identify the reason category, transaction date, merchant contact and evidence expected by the bank. Scheme time limits can depend on the dispute type and can be complex, so use the bank’s current process and do not rely on a generic number of days copied from an old article. Record the date on which the bank was first asked to consider the dispute.
For a potential Section 75 claim, confirm that the transaction and card relationship meet the statutory conditions before presenting it as the applicable route. The analysis may involve the cash price of the item or service, debtor-creditor-supplier relationship and other transaction structure issues. Keep the statutory claim evidence separate from any parallel chargeback because the legal basis and decision-maker are not identical even when both relate to the same purchase.
Escalate with a complete complaint record
If the bank’s final position remains disputed, preserve the final response and the date it was received. The Financial Ombudsman Service can consider complaints within its jurisdiction, but current eligibility and time limits should be checked from its official material at the point of escalation. Prepare a compact bundle containing the statement entry, merchant documents, chronology, bank complaint, evidence submitted and final response. The reviewer should be able to see the disputed transaction without navigating dozens of unrelated statements.
State the outcome sought precisely: refund of a specified debit, restoration of interest or fees caused by the debit, correction of information, reimbursement of evidenced consequential loss or another remedy that fits the complaint. If several transactions remain open, list their individual status. Do not ask for a total that includes an item the bank has already refunded.
Verify closure on the account itself
A case is not complete because an email says it is resolved. Confirm the credit on the account, its value date and whether any temporary credit was replaced by a final adjustment. Check related fees or interest where those were part of the complaint. If the merchant also pays a refund, make sure the bank’s adjustment does not create an unintended double credit that will later be reversed.
Keep a final statement extract and closing correspondence with the complaint log. If the same merchant charges the card again, start a new transaction line rather than editing the closed one. A disciplined transaction record makes later investigation much easier because every debit, credit, merchant promise and bank decision remains tied to its own date and evidence.