Whilst it was originally specified that the process for retrying a direct debit payment would be as follows:
1- User creates payment batch
2- User submits payment batch using the submit button
3- Contributions are updated to completed status
4- For any failed payments user should update the status manually and set status to cancelled.
5- The batch screen should pick up any payments which are cancelled also so that it can retry
6- If the user does not want to retry then they should cancel the recurring contribution which will ensure that no further payments are displayed in the batch screen regardless of status.
Having discussed, the ability to retry payments with a cancelled status is confusing for users and there are situations where an organisation might want to take a one off payment by credit card or another payment method.
A suggested solution is to have some sort of "duplicate contribution as pending" feature outside the batch screens entirely (e.g on the contributions list) so users can duplicate any contribution they want in pending status and for it to be available in batches .
Before
There was no easy way to handle (e.g retry them) cancelled or failed payments after the payment batch is submitted.
After
A new action is added called "Duplicate As Pending Contribution" that allows users to duplicate any contribution they want as a pending contribution, the action is available on any contribution list page such as the contact contributions list and in "find contributions" results :
Here is how it work in action :
This action require the user to have "CiviContribute: edit contribution".
also hence that the duplicate contribution will be attached to the same recur contribution if the original contribution is part of recur contribution.
Introduction
Whilst it was originally specified that the process for retrying a direct debit payment would be as follows:
1- User creates payment batch 2- User submits payment batch using the submit button 3- Contributions are updated to completed status 4- For any failed payments user should update the status manually and set status to cancelled. 5- The batch screen should pick up any payments which are cancelled also so that it can retry 6- If the user does not want to retry then they should cancel the recurring contribution which will ensure that no further payments are displayed in the batch screen regardless of status.
Having discussed, the ability to retry payments with a cancelled status is confusing for users and there are situations where an organisation might want to take a one off payment by credit card or another payment method.
A suggested solution is to have some sort of "duplicate contribution as pending" feature outside the batch screens entirely (e.g on the contributions list) so users can duplicate any contribution they want in pending status and for it to be available in batches .
Before
There was no easy way to handle (e.g retry them) cancelled or failed payments after the payment batch is submitted.
After
A new action is added called "Duplicate As Pending Contribution" that allows users to duplicate any contribution they want as a pending contribution, the action is available on any contribution list page such as the contact contributions list and in "find contributions" results :
Here is how it work in action :
This action require the user to have "CiviContribute: edit contribution".
also hence that the duplicate contribution will be attached to the same recur contribution if the original contribution is part of recur contribution.