Always use the safest payment method: Chip & PIN or contactless, or use 3D Secure online. Avoid manual entry wherever possible. Train staff to spot mismatches between how a card was entered and what the receipt says.
Set up email chargeback alerts so you never miss a notification.
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 Terms & Conditions 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.
Make sure customer records link clearly to payments and transactions — including third-party bookings.
If the customer and cardholder are different, keep both sets of details.
Train staff on chargebacks, so frontline teams understand how disputes work and feel confident in knowing how to spot risks and unusual behaviour.
Use secure transaction methods.
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. Process refunds correctly always refund the original card used. Don’t use cash, bank transfer, or a different card.
Set up fraud screening and take immediate action on high-risk transactions.
Save evidence linking the booking, customer, and payment
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 the amount changes, process a new sale and document the difference.
Avoid splitting transactions to bypass limits — this can trigger disputes.
Avoid using debit cards for pre-authorisation, except for verifying the card with a very low value transaction (£0.01)
Always use the correct refund method, onto the same payment card.
Monitor for duplicate transactions using Elavon Connect and issue prompt refunds if found.
Respond with full documentation for duplicate charges or “paid by other means” claims — invoices, receipts, and system logs
Best practice for avoiding and managing chargebacks.