# 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?](https://docs.forter.com/forward-chargebacks#which-method-is-best-for-me-to-forward-chargebacks)

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

## [Dispute Webhooks](https://docs.forter.com/forward-chargebacks#dispute-webhooks)

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

### [Why are Webhooks better?](https://docs.forter.com/forward-chargebacks#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.

### [Setup a webhook per PSP](https://docs.forter.com/forward-chargebacks#setup-a-webhook-per-psp)

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:

- [Adyen](https://docs.forter.com/adyen-dispute-webhook)
- [Braintree](https://docs.forter.com/braintree-dispute-webhook)
- [Checkout.com HUB](https://docs.forter.com/checkout-hub-dispute-webhook)
- [Checkout.com NAS](https://docs.forter.com/checkout-nas-platform-dispute-webhook)
- [PayPal](https://docs.forter.com/paypal-dispute-webhook)
- [PayU Latam](https://docs.forter.com/payu-latam-dispute-webhook)
- [Primer](https://docs.forter.com/primer-dispute-webhook)
- [Stripe](https://docs.forter.com/stripe-dispute-webhook)

## [Alternative solutions](https://docs.forter.com/forward-chargebacks#alternative-solutions)

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

### [Send notifications via SFTP](https://docs.forter.com/forward-chargebacks#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](https://docs.forter.com/forward-chargebacks#send-notification-via-dispute-api)

If any of your PSPs are _not_ supported through webhooks, use the [Dispute API](https://docs.forter.com/reference/dispute "Dispute API") to send each notification.

### [S3 CSV File Upload](https://docs.forter.com/forward-chargebacks#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.