Rainforest will be releasing changes to the Payment Component and Merchant Onboarding Component on October 1st, 2025 to better enhance your end users' and merchants' experience.

Payment Component

Card payments

Postal code always displayed

The Payment Component will always display the postal code field, regardless of the postal code being provided in the Payin Config. If it's provided in the Payin Config, then it will be pre-filled in the Payment Component.

Previously, if the postal code was provided in the Payin Config, then the postal code field was not visible. If the incorrect postal code was provided, then the end user could not correct this when processing their payment. Ultimately, this could result in lower approval rates if the card networks took into account the AVS check.

This change will positively impact the AVS check with the card networks as it will ensure the end user is providing the postal code associated with their card number and result in higher approval rates.

ACH payments

Name always displayed

The Payment Component will always display the name field, regardless of the name being provided in the Payin Config. If it's provided in the Payin Config, then it will be pre-filled in the Payment Component.

Previously, if the name was provided in the Payin Config, then the name field was not visible. If the incorrect name was provided, then the end user could not correct this information when processing their payment. Ultimately, this could result in an ACH Return due to the name of the account holder not accurately matching the name on file with the bank.

This change will positively impact ACH processing ensuring the name provided by the end user matches the name on file with their bank.

Account type selector

The Payment Component will now include the ability for the end user to choose the account type of Checking or Savings.

The account type will be set to Checking by default when rendering the Payment Component. To change the default to Savings, add the field-defaults prop and set it to the following:

  <rainforest-payment
    session-key='REPLACE_ME'
    payin-config-id='REPLACE_ME'
    allowed-methods='CARD,ACH'
+   field-defaults='{"ach": {"account_type": "SAVINGS"}}'
  ></rainforest-payment>

Merchant Onboarding Component

Validated ACH (Plaid) as a deposit method

The Merchant Onboarding Component will automatically enable the validated ACH flow, where the merchant can connect to their online bank account to collect the bank information. Rainforest utilizes a third-partner, Plaid, for real-time validation.

Real-time bank account validation makes onboarding faster and more reliable by:

Reducing data entry errors when a merchant enters their routing or account number
Reducing friction to complete the application, because bank login credentials are generally known or saved versus the routing and account number
Enabling Rainforest to quickly identify the owner of the account reducing the potential for documentation requests after the submission of the application

This change will no longer require Rainforest to enable this feature for your integration. To ensure your integration supports validated ACH deposit methods, see our Validated ACH in merchant onboarding guide.

Disable validated ACH

If you do not want to support the validated ACH flow, then a new allowed-deposit-methods prop can be set to only ACH.

<rainforest-merchant-onboarding
    session-key="REPLACE_ME"
    merchant-id="REPLACE_ME"
    merchant-application-id="REPLACE_ME"
+   allowed-deposit-methods='ACH'
></rainforest-merchant-onboarding>

Please contact support if you have any questions.