Skip to main content
All CollectionsThe Chargeflow App
Why is my processor deactivated?
Why is my processor deactivated?
Yuval Ben Ami avatar
Written by Yuval Ben Ami
Updated this week

At Chargeflow, we strive to provide merchants with a seamless product experience, such as dispute automation. However, we deactivate processors in specific scenarios. Below are the primary reasons for such deactivations and what they mean for you as a Chargeflow merchant. The merchant has requested explicitly to stop automating their disputes.

Per Merchant Request

If a merchant explicitly requests that we stop automating disputes, we will deactivate the specified payment processor(s). For example, a merchant may contact our support team to request the deactivation of one or more payment processors or to entirely stop dispute automation.

Impact: Once deactivated, Chargeflow is no longer responsible for managing disputes for the affected processor(s). If you wish to resume automation and reactivate your processor, you can do it quickly through the integration page.

Outstanding Debts

Processors may also be deactivated if a merchant has outstanding due debts. For example, we detect overdue balances on the merchant’s account, prompting proactive deactivation.

Impact: As outlined in our Terms and Conditions, we will not handle disputes for any deactivated processors until the debt is fully cleared and the account is in good standing. Once resolved, the deactivated processor(s) can be reactivated.

Did this answer your question?