Zepto (formerly Split Payments); enhancements to Process Direct Debit Payments wizard if a Bank Interface fails to Send

Several changes have been made to the Process Direct Debit Payments wizard to streamline the Zepto Bank Interface, especially where Transactions are auto-sent to Zepto and fail due to a 422 Unprocessable Entity error. This error can occur where the Direct Debit Agreement is no longer valid, such as when the customer has requested a block with their bank.

You may see a failure with a message like:

• Authoriser contact (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) bank account ((xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) is blocked and not eligible.
• Authoriser contact (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) must have a valid agreement in place before a Payment Request can be issued.
• The remote server returned an error: (422) Unprocessable Entity.

Changes include:

• Process Direct Debit Payments wizard
• A more specific message is displayed at the end of the Commit if a Transaction failed to be sent for processing.
• Option to open the Export Bank Transactions wizard now defaults "Send Bank Transactions via a Bank Interface (Web API) Service?"
• By opening and running this wizard you can see what Bank Transactions failed to send and why

• Export Bank Transactions wizard
• Simplified. more User friendly error message, i.e. no longer includes technical information, if a 422 error is detected
• "Invalid Message" column now shows the error after trying to send a Bank Transaction
• If the Processing Status is "Send Failed", as well as the "Resend" button there is now a "Reverse" button.
• The Reverse button is a shortcut to open the Bank Transaction Reverse wizard

The following standard Summary Page block has been updated:

• BankTransactionView_ExportDetails
• Version: 2.06 (19/09/2022)