Product Overview

forter’s chargeback recovery solution enables merchants to manage chargebacks at scale by combining automated dispute handling with flexible policy controls this guide outlines how forter helps ingest chargeback claims, determine dispute eligibility, and submit supporting evidence—all tailored to your business rules benefits of forter's chargeback recovery boost win rates and revenue recovery use ai to tailor dispute packages with the most relevant evidence for each bank, increasing your chances of success cut costs with automation automate dispute generation and evidence enrichment to reduce manual work and improve team efficiency resolve disputes faster manage disputes in real time with forter’s tools and integrations, enabling quick, scalable responses performance visibility track chargeback performance across all systems in one place, with insights to guide business strategy forter’s approach to automation ✨ ai powered optimization forter’s ai fine tunes dispute arguments based on issuer preferences, helping you build high performing packages that boost win rates ⚡ built in automation forter automates evidence enrichment and package creation, simplifying dispute handling and reducing manual effort how disputing at forter works merchants configure automatic, manual, or hybrid dispute submission flows evidence can be added via the portal or the evidence api (beta) until 48 hours prior to the due date more evidence submitted = higher chance of success once forter submits the representment letter, no additional evidence can be added the issuing bank makes a decision (win/loss) merchants should regularly review forter’s portal to see chargeback metrics (win, loss, recovered, etc ) or if in a manual/hybrid flow for new chargebacks, evidence deadlines, or recommended actions chargeback flow flowchart td %% define nodes a\[chargeback created] external > b\[send to forter] merchant b > c\[match to transaction] forter c > d\[forter analyzes] forter d >|dispute not recommended| e\[closed] forter d >|dispute recommended| f\[request evidence] forter f > g\[merchant provides evidence] merchant g > h\[submit dispute package] forter h > i\[issuer decision] external %% style classes classdef merchant fill #d1fae5,stroke #10b981,color #065f46; %% green classdef forter fill #e0f2fe,stroke #3b82f6,color #1e3a8a; %% blue classdef external fill #f3f4f6,stroke #6b7280,color #374151; %% gray chargeback evidence when forter determines that a chargeback should be disputed, we’ll request additional evidence from the merchant we will notify you by either request for evidence webhook forter notifies you of the evidence needed portal flag the portal will show you what evidence is missing per chargeback and request you upload it then you will need to provide evidence using one or more of the following methods manual portal upload evidence api (beta) s3 file upload order status updates (e g , tracking number) evidence types may include post purchase evidence an image or text filled by the merchant indicating the type of evidence collected static evidence includes things like logo, description, purchase flow and terms and conditions that forter will automatically pre fill to every chargeback method description notes processor webhook forter receives real time chargeback data directly from the payment processor ✅ preferred method for automation and data completeness dispute api merchant sends chargebacks to forter via api requires data normalization; more dev effort s3 file upload merchant uploads csv/pdf files of chargebacks to a forter managed s3 bucket common for batch workflows or limited dev resources