Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: For updateSubscriptionBillingInfo, update next scheduled date on success #393

Open
larssandergreen opened this issue Oct 18, 2022 · 3 comments

Comments

@larssandergreen
Copy link

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.

@adixon
Copy link
Contributor

adixon commented Nov 7, 2022

I appreciate the idea, but I think it's a little too risky. Automated changes to recurring contribution schedules is a risk I don't want to start ...

But I can see your need, I wonder if there's another way to resolve it? e.g. maybe some on-screen messaging and/or emails?

@larssandergreen
Copy link
Author

Fair enough.

I use CiviRules to notify me whenever these are updated and that works fine for my needs for the cardholder updating their own details. It might not be a bad idea to pop up a notice on the backend when someone updates billing info prodding them to check if they need to update the next scheduled date, since it's on a different screen, so it's out of sight and out of mind.

We could maybe say something like:

Billing details updated.
The next recurring contribution will be processed on DATE.
If you want to process the contribution now, you can edit the next scheduled contribution date (link).

@larssandergreen
Copy link
Author

Or, as a perhaps more functional option, we could add the Next Scheduled Contribution Date to the Change Billing Details form, for backend users only. That way it would be right there when someone is updating someone's credit card number, so it would be obvious if it needs to be updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants