Enabling Validated ACH in merchant onboarding requires minimal development changes in your integration.

1. Utilize permission groups in component sessions
2. Update your Content Security Policy
3. Contact Rainforest to enable validated ACH

Component sessions

📘

Available on API version 2023-12-01

If you are integrated against a previous API version and your minimum API version is not at least 2023-12-01, then you'll need to upgrade your API version to access validated ACH in merchant onboarding. See the API version upgrades guide for more information.

Your component sessions need to utilize authentication permission groups in order to support validated ACH in the Merchant Onboarding Component.

Your session should include the following statement:

{
  "permissions": ["group#merchant_onboarding_component"],
    "constraints": {
      "merchant": {
        "merchant_id": "{{REPLACE_ME}}"
      }
    }
}

This will ensure you have access to all resources required to complete the real-time validation to connect with the merchants bank account.

Content security policy (CSP)

If your platform uses a Content Security Policy (CSP), you will need to add the following directives to allow Plaid, the third-party partner, to run on your website:

default-src https://cdn.plaid.com/
script-src https://cdn.plaid.com/
frame-src https://cdn.plaid.com/
connect-src https://production.plaid.com/

Enable validated ACH

Once your integration is ready, please contact your Customer Success Manager or Rainforest support to request validated ACH to be enabled for merchant onboarding.

Sandbox

In production, merchants will select "Connect with bank login" to launch the Plaid flow to select their bank and they will be directed to log in or use OAuth credentials.

In sandbox, Rainforest will connect to Plaid's sandbox environment, which offers a variety of fake banks with different flows. The Plaid sandbox environment will always return the Citizens Bank, no matter the issuing bank chosen in the Plaid flow.

Here is an example: