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 Terms & Conditions and refund policies.
Link each transaction to customer details so you can trace it quickly if challenged. If the cardholder and service user differ, keep both sets of details.
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 Mail order/telephone order (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.
Don’t relax security for B2B or group bookings — apply the same fraud checks.
Pre-authorising £0.01 with 3D Secure at booking can reduce risk, especially for no-shows. Take action on high-risk transactions — continuing is at your own risk.
Third-party booking platforms do not guarantee security — always verify bookings yourself.
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 increases, complete the original authorisation and charge the remainder separately — and document it clearly. Avoid splitting transactions to bypass limits — this can trigger disputes. Avoid using debit cards for pre-authorisation (except a small amount to confirm the card is real).
Always use the correct refund method, onto the same payment card.
Monitor for duplicate transactions using Elavon Connect and issue prompt refunds if any are found. Use separate invoices for repeat visits or additional charges to avoid duplicate payment disputes. Respond with full documentation for duplicate charges or “paid by other means” claims — invoices, receipts, and system logs.
Keep a standard document pack ready for disputes, containing booking terms, refund policy, signed agreements, and website screenshots.
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.
Additional charges (e.g. damage, extra services) must always be authorised — ideally by PIN or written consent.
If using third-party sites, make sure their Ts & Cs and booking pages meet card scheme rules (especially Visa). If using virtual cards (issued by agencies), understand their terms override yours. Charge extras to the customer’s own card, not the virtual one. To check if a chargeback came from the guest or agency, review any documents or logos included in the notification.
If the issue involved misconduct, record everything. If police were involved, include a reference number or confirmation. If service was interrupted by external issues (like weather or disruption), show proof of how it was resolved, and reference your Ts & Cs at time of booking.
Best practice for avoiding and managing chargebacks.