NACHA verification

Effortlessly comply with NACHA regulations with Recurly's pre-verification feature, ensuring seamless ACH transactions and reduced instances of bad accounts or fraudulent transactions.

Overview

Prerequisites

  • Access to one or more supported payment gateways or;
  • A direct integration with an ACH verification provider, such as Plaid or Giact.

Limitations

  • Only new bank accounts will be verified. Bank accounts on file are not subject to preverification rules.
  • Adyen gateway requires use of Giact.
  • Stripe gateway requires use of Financial Connections and cannot support externally verified bank accounts.

Definition

Recurly’s Bank Account Verification Support feature provides merchants with the ability to verify consumer bank details (ACH) in the United States before processing transactions or setting up subscriptions, specifically when a new bank account is being provided. This capability is essential for businesses that operate in the United States and are accepting ACH transactions.

Note: Not all gateways support pre-verification. For ACH gateways that are not supported, external verification should be done before sending bank details to Recurly for processing.

NACHA Verification Regulations can be found on the NACHA.org site and by reading their Account Validation best practices guide.

Gateways with NACHA verification support

These gateways allow you to accept payments in any currency within Recurly:

  • Adyen: You must enable Giact with your Adyen account and ensure you have enabled the feature within your gateway configuration on Recurly.
  • Stripe: You must specifically be using Stripe Elements, and make use of Stripe's Financial Connections platform to pre-verify bank account details using Plaid.

Gateways requiring pre-verification externally

Suggested flow for external verifications

You may use an external provider for any of our ACH supported gateways (excluding Stripe) to verify bank accounts prior to adding billing information to the Recurly platform. General best practices including verifying any new bank account information provided to you by a consumer, so that you can verify it is usable for a WEB (online) transaction.

The direct language from the mandate, effective March 2021, is as follows:

  • Validate first-use consumer account information for consumer debit payments authorized or initiated over an online channel (often called WEB Debits).

You may require users to authenticate via Plaid, or even via micro-transactions and verify the debits/credits, prior to adding their billing info to Recurly. If the external integration verifies that a consumer's bank account is valid for online processing, and can be debited, you may follow your existing flow with Recurly today.