Success+ and maintaining Duty of Care
This article explains how you can leverage Success+ to maintain a duty of care towards your customers.
How does the 90% failure flag in Success+ work?
The Success+ intelligent retry engine calculates how likely a failed payment is to be recovered. If our algorithm determines there is a 90% or higher chance that a payment retry will fail, we automatically stop the retry to save you time and unnecessary effort.
The smart algorithm learns from millions of GoCardless transactions and makes its automated decisions based on three specific categories of data:
- Payment data: This includes specific transaction details like the payment amount and the regional payment scheme being used.
- Merchant data: This assesses your business vertical and your history of collecting payments with us.
- Payer data: This reviews the payer's overall payment history across the GoCardless platform.
You can read our full help article here for more detailed information.
A quick note on ROI: When looking into the performance of this filter, our data shows that merchants often get a better return on investment when they leave this flag disabled. Even though some retries carry a low chance of success and clear transaction costs, the ultimate value you gain from those recovered payments usually outweighs the cost of the extra retries.
How does Success+ support vulnerable payers?
If you use Success+, you can maintain full control over exactly which payments we retry by using our API.
Our system includes a dedicated developer flag called retry_if_possible, which gives you complete command over the retry behaviour:
- Set to true: Success+ will automatically retry the payment if a failure occurs.
- Set to false: Success+ will completely skip any automated retries for this specific payment.
If your team does not explicitly set this flag when creating a payment, the system defaults to false.
Because you know your customers best, the responsibility sits on your side to identify vulnerable payers and adjust this flag's value whenever you create a payment. For a technical breakdown of how to configure this feature, take a look at our developer documentation here.