One of your ideas has been delivered from your suggestion.Validating New Bank Accounts for Automated Clearing House Electronic Payments

You can choose to validate all your customers’ new bank account details prior to their first use for automated clearing house electronic payments using NACHA. This is regardless of whether the bank account details are entered via self-service activities, agent-assisted manual one-time payments, or added to the Account - Automatic Payment (CI_ACCT_APAY) table via the application.

Previously, Web Debit Account Validation functionality was provided to support validating a customer's bank accounts entered through the following means:

  • Self-service activities
    • Automatic Payment Setup
    • Make One Time Payment
    • Manage Payment Options (wallet)
  • Agent-assisted manual one-time payments via the alternative Payment Event pop-up window

To support bank account validation when details are added to the Account - Automatic Payment (CI_ACCT_APAY) table, the following updates have been made:

  • Updated the processing associated with the Account - Automatic Payment (CI_ACCT_APAY) table to trigger bank account validation when a customer's bank savings/checking account is entered via the application. The validation is managed by a service task based on the Bank Account Auto Pay Setup Task (C1-BankAcctApaySetupTask) business object. If there is a subsequent attempt to add or change an account's automatic payment bank details and validation is still in progress, you will be notified through an informational message displayed on the Account - Auto Pay page.
  • The Validate state in the business object invokes the account validation processing that is configured on Auto Pay Route Type (or CIS Division, if the override configuration exists). It also creates a customer contact. The Customer Contact Class and Customer Contact Type for the customer contact are retrieved from the service task type based on the new Bank Account Auto Pay Setup Task Type (C1-BankAcctApaySetupTaskType) business object.

This reduces the need for implementation-specific extensions to support validating customers' bank account details.

Steps to Enable

To enable this feature, refer to the Web Debit Account Validation section in the Administrative User Guide for more information.