Automate Evidence

Automate Evidence Automate Evidence

Forter already receives most of the evidence through Orders and Claims Data; however, we provide a Request for Evidence Webhook & Evidence API that enables customers to share additional evidence with Forter in an automated way.

Elements of Evidence Automation 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)
• Merchant → Forter: Customers provide compelling evidence to Forter (Evidence API)

Note: Not all customers will need both capabilities.

Automating Evidence Upload with Forter Automating Evidence Upload with Forter

Leverage our Request for Evidence Webhook & Evidence API

Automating Evidence Collection and Sending 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.

1. 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

2. 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

3. 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