Set up email chargeback alerts so you never miss a notification.
Train staff on chargebacks, so frontline teams understand how disputes work and feel confident in knowing how to spot risks. Process refunds correctly always refund the original card used. Don’t use cash, bank transfer, or a different card. Reply on time to all chargebacks. Never miss the “Respond By” date – especially around holidays or busy periods.
Avoid additional refunds once a chargeback is issued. Accept the case or provide a full defence, but make sure you don’t double-pay. Keep your merchant details updated, including trading names and addresses, to avoid disputes due to confusion or mismatched info.
Provide clear, disclosed Ts & Cs and refund policies.
Avoid links or cloud-based files when submitting evidence. Use PDFs, images or text files only. Prepare standard response packages with Ts & Cs, refund policies, screenshots, and user guides to make defending cases easier.
Keep all transaction records clear and connected to customer details, booking reference and payment method. Be especially careful when dealing with business or group bookings – always follow your usual security steps.
Use secure transaction methods.
Train staff to spot unusual behaviour, especially attempts to distract during payment or enter details manually. Disable manual entry if not needed for MOTO transactions and switch instead to secure pay-by-link methods where possible. Use fraud filters and Address Verification Service (AVS)/Network Access Control (NAC) checks. If the check fails, consider declining the payment.
Try using a £0.01 pre-auth with 3D Secure to help verify a card during booking. If a card is later used with a PIN, it further proves legitimacy. Remember that bookings that come through a third-party site do not carry a guarantee of the cardholder’s identity, and fraud processes may not match yours
Don’t force transactions if the card is declined. Make sure you follow prompts carefully: if a voice referral is requested, call the number provided. Don’t treat it as a PIN request. Use authorisation codes only when issued by the system, never accept authorisation codes from customers.
Use authorisation codes only once and don’t reuse or reverse codes after a transaction has been completed. If you need to charge more than pre-authorised, process a new transaction and note it clearly. Avoid pre-auths on debit cards unless just to verify (e.g. £0.01) Avoid splitting transactions to bypass limits — this can trigger disputes.
Always use the correct refund method, onto the same payment card.
Monitor for duplicate transactions using Elavon Connect and issue prompt refunds if found. If a customer queries a duplicate charge, double-check all records and card numbers.
Respond with full documentation for duplicate charges or “paid by other means” claims — invoices, receipts, and system logs.
If extending a service or providing additional products, provide a new invoice for every additional charge to avoid confusion or claims of duplication.
Keep a standard document pack ready for disputes, containing booking terms, refund policy, signed agreements, and website screenshots. Include before/ after photos if relevant. Keep a record of all complaints, resolutions and customer correspondence — especially for claims like “service not as described”. Provide full evidence of any resolution steps taken.
For extra charges (like damage, parts, cleaning or refuelling), get written agreement or proof the customer accepted. If working with third-party platforms, their Ts & Cs may override yours. Check if the dispute came from the guest or agency (documents often show this). If customer misbehaviour caused cancellation (e.g. police called), keep official records. For cancellations due to disasters or external events, share your terms and proof of refund or customer agreement.
Best practice for avoiding and managing chargebacks.