-
Notifications
You must be signed in to change notification settings - Fork 40
Description
I've tried to train our folks to always update the next scheduled recurring date when updating credit card details for a recurring contribution that has failed, but they always assume it will process right away. Presumably we always want to process the card right away, since we're behind the previously set recurring schedule. Same applies for self-service updates. If there's a need to return to a previously set schedule like the first of the month, that can be adjusted for the next contribution.
Here's my proposal: If the card has just been successfully updated and the failure count is > 0, then set the next scheduled date to today. That way the card will be processed on the next cron run. If we're on the front end, notify the user that their card will be processed in the next 24h. If we're on the backend, notify the user that the card will be processed in the next 24h, but they can change the date before cron runs if needed.
No change if failure count = 0 and the card is being updated before it fails.
I can submit a patch if this makes sense.