Docs
You are viewing:
Product Catalog 2.0
This article explains why certain chargebacks, especially for Direct Debit payments processed through gateways like Mollie and Adyen, may not be automatically marked as chargebacks in Chargebee.
In such cases, while the payment may be reversed and the invoice updated to Not Paid, the subscription remains active, and no chargeback notification or dunning workflow is triggered.
We'll also clarify how to distinguish true chargebacks from late payment failures, and guide you on configuring Chargebee to better manage these events through dunning and notifications.
Not all gateway-reported chargebacks are genuine chargebacks. Some are actually late payment failures, which occur when a previously successful Direct Debit payment later fails due to:
This issue is primarily seen with Mollie SEPA and Adyen ACH/SEPA payment methods.
When Chargebee requests a Direct Debit payment, the customer's bank may provide provisional approval within 5–7 days. However, the actual funds settlement happens later. If the transaction ultimately fails during this period, the initial "successful" status is reversed, and the payment is marked as failed.
Different gateways handle late failures differently:
When the failure does not qualify as a genuine chargeback:
Payment of $XX removed due to late failure against transaction parent_success_transaction_ID
in gateway_name
. Invoice moved to 'Not Paid' state.
To stay proactive and ensure timely handling of these failures:
Was this article helpful?