If you are using Ezidebit for direct debit payments with First Class, there are some in built actions for failed payments.
Your account settings will dictate the automated dishonour action taken for failed payments
Below is a summary of the available dishonour actions
Dishonour Actions- Ezidebit
1. Dishonour with no action
2. Re-debit in 3 days
3. Debit with next payment
4. Re-schedule after last payment
How do I know what dishonour action is being used for our account?
If you log into Ezidebit online and look up a payer, under the payment arrangement section there is a dishonour action section that will outline what dishonour response is used for that payer.
Typically all payers will default to the same default dishonour type that is set under your Ezidebit account.
Failed payment SMS
A great option to automate part of the failed payment process is to leverage SMS failed payment notifications.
When turned on, these SMS notifications are sent to customers who have had a failed payment and can outline your next dishonour step: Ie. The payment will be re-tried in 3 days.
If you have any questions about your Ezidebit set up in First Class please reach out to the First Class support team.
How to manually re-schedule your failed debits?
If your account is set up to take no action for dishonoured or failed payments, you will want to manually take action to recover those failed payments.
An easy way to do this is to manually add the failed payment amount to a future scheduled debit for that customer.
If you customer has a direct debit schedule with future debits, you can use the edit feature within the debit debit tab of the customer profile to edit the future amount.
Example
If the customer had a failed payment of $63.00 and their next scheduled payment is for $63.00 you could edit that future payment of $63.00 to $126.00 to get their schedule back on track.
If you have any questions, feel free to reach out to our support team at support@memberretentionsystems.com
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article