> For the complete documentation index, see [llms.txt](https://help.jupico.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jupico.com/disputes/dispute-prevention.md). # Dispute Prevention Unfortunately, it’s impossible to completely eliminate the risk of chargebacks. But there are key things you as merchant can employ as part of your overall strategy in preventing them. ### Best practices for preventing chargebacks * Post clear and visible cancellation, return and refund policies prior to the checkout process. * Make sure customer service contact information is easy to find and access. * Always ask for Card Identification Number (3-digit security code on the card back or four-digit security code on the card face) for card-not-present transactions. * Use Automated Address Verification service (often referred to as AVS) to validate cardholder information * Process credits immediately when necessary, and notify cardholders of refund statuses, since they are better than chargebacks * Use clear statement descriptors. We recommend using your website domain or business name to make sure customers can easily identify their purchase when they look at their statement. * When shipping physical goods to customers, use carriers and services that provide online tracking and delivery confirmation whenever possible. Provide this information to your customers as soon as it’s available (if you need to submit tracking information as dispute evidence, be aware that card issuers don’t follow links so screenshots must be provided). {% hint style="info" %} Questions or need more explanation please email our Support Team at . {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.jupico.com/disputes/dispute-prevention.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.