When you need to connect an integration

Use this article to decide whether you need a payment processor integration for Prevent or Deflect. It explains when an integration supports Prevent auto-refunds, when you can leave auto-refund off, and why Deflect does not require an integration.

This article is about the decision to connect an integration. It does not cover the step-by-step setup for a specific processor, and it does not explain how to set up auto-refund thresholds. For those, see the connection guide for your processor or the auto-refund setup guide.

Connect a payment processor to an integration if:

You can also keep an integration connected without auto-refund enabled. In that case, the system still searches your processor for transactions and may provide direct transaction links for faster lookup.

Keeping the integration enabled (but auto-refund disabled) gives you flexibility. You can decide case-by-case whether to auto-refund alerts without disconnecting and reconnecting.

If we don’t support your processor, you can still use Prevent, but you must manually refund transactions linked to Ethoca Alerts and Cardholder Dispute Resolution Network (CDRN) alerts. If you're signing up, select Other during onboarding.

If you already have an account, you won’t see Other. Instead, add billing descriptors and ARNs in your enrollment settings.

For the steps, see Add billing descriptors to alert solutions.

You can leave your integration connected and turn off automatic refunds for Ethoca Alerts and CDRN. Follow the auto-refund setup guide for the steps.

You don’t need an integration if you plan to manually refund all pre-dispute alerts.

Deflect uses Order Insight for Visa and Consumer Clarity for Mastercard. Neither program requires a store or payment processor integration. Integrations, including Slack, do not support Deflect lookup activity.