Forward Chargebacks - Overviews

Forward Chargebacks

To begin processing chargebacks, Forter must receive each dispute event as soon as it’s filed.

Forter supports four different ways to send us your chargebacks from your PSP.

Which method is best for me to forward chargebacks from my PSPs?

PSP	Recommended Forwarding Method
- Adyen - Braintree - Checkout.com HUB - Checkout.com NAS - PayPal - PayU Latam - Primer - Stripe	Dispute Webhook connection directly with PSPs
- Amex - Chase Paymentech - Elavon - Any other PSP that offers SFTP	SFTP connection directly with PSP
Other PSP that don't support webhooks or SFTP	Dispute API

Dispute Webhooks

The most efficient way to do this is by setting up dispute webhooks between your PSP and Forter.

Why are Webhooks better?

Webhook-based forwarding enables:

Real-time claim ingestion
Faster transaction matching
Immediate eligibility assessment for dispute handling

This ensures your chargeback recovery process is fully automated and runs without delay.

For each of your PSPs, follow the instructions to set up a dispute webhook. Webhook configurations are required for processors that support webhooks. Forter can accept dispute webhook notifications from:

Alternative solutions

If you can't implement the Dispute Webhooks, you can use one of the other solutions Forter offers:

Send notifications via SFTP

If any of your PSPs are not supported through webhooks, and your processor (including but not limited to Amex, Chase, or Evalon) supports granting Forter the necessary permissions, we can automatically retrieve your new chargeback SFTP files when they become available.

Don't hesitate to contact your PSP's representative to check whether they support SFTP chargeback files.

Send notification via Dispute API

If any of your PSPs are not supported through webhooks, use the Dispute API to send each notification.

S3 CSV File Upload

If webhooks, SFTP, or Dispute API are not feasible solutions, then we can explore setting up CSV uploads to Forter on a frequent cadence.