Chargeback Recovery
...
Providing Evidence
Automate Evidence
3 min
automate evidence forter already receives most of the evidence through orders and claims data; however, we provide a request for evidence webhook docid\ okukf01 us 1pfk4icq4r & evidence api docid\ pchwsj6 awn o2bnvbacu that enables customers to share additional evidence with forter in an automated way elements of evidence automation once chargebacks are ingested into forter, our recommendation engine will suggest additional evidence to add to your dispute to bolster your win rate for an automated flow, forter enables a call and response workflow forter → merchant forter sends notification to customers of recommended evidence to upload ( request for evidence webhook docid\ okukf01 us 1pfk4icq4r ) merchant → forter customers provide compelling evidence to forter ( evidence api docid\ pchwsj6 awn o2bnvbacu ) note not all customers will need both capabilities automating evidence upload with forter leverage our request for evidence webhook & evidence api automating evidence collection and sending while forter provides methods and locations for evidence submission, you are responsible for automating this process within your own system how can i automate sending files to forter? internal systems forter doesn’t connect to oms/crm systems you have to set up automation to our apis cron jobs you can set up automated jobs to upload files to s3 and send api requests how to know when to send evidence? send all evidence same evidence for every chargeback send targeted evidence only forter requested evidence for claim ids grabbed either via csv download or evidence request webhook why must i upload to s3 first, then send the file path via api? provide file path in the api call for forter to link file with the specific chargeback id security requirement we use a 2 step process for safety and security screening industry standard stripe and braintree leverage the same approach