Step 2: Dispute Webhooks

Why is this needed?

Webhook/API access for Forter is required in order to allow Forter to facilitate claim ingestion and claim submission at scale. Through this one simple connection we establish a seamless flow of chargeback status and information.

Supported PSPs

Same as in the Fraud Management Integration. See here.

Adyen

Braintree

Checkout HUB

Checkout NAS

Paypal

Stripe

Setup a webhook per PSP

For each of your PSPs, follow the instructions within Forter's portal to set up a dispute or claims webhook.

Send the access credentials to Forter via secure S3 bucket transfer. Ensure the credentials are saved under the file naming convention "JCBR-processorName" where processorName is a placeholder for which processor these keys are for (ex. "JCBR-Stripe") and upload it to your secure Forter S3. Instructions for accessing your S3 can be found at the bottom of the Historical Data Transfer Page. Please notify your Forter Project manager once these credentials have been uploaded.

Disputes Webhooks

Same as in the Fraud Management Integration. See here.