When an ACH return is initiated from the issuing bank, Rainforest will create an ACH return. You can be notified of an ACH return by subscribing to relevant webhook events.

📘

Available on API version 2024-10-16

If you are integrated against a previous API version and your minimum API version is not 2024-10-16, then you'll need to upgrade your API version to 2024-10-16 to access the ACH return functionality outlined in this guide. See the API version upgrades guide for more information.

The flow of an ACH return within the Rainforest ecosystem can result in two outcomes, depending on the timing of the ACH return and the status of the payin. The two scenarios are explained here.

The two scenarios can also be interpreted by listening to the ACH return webhooks.

ACH payin and ACH return in the same deposit

If the ACH payin was in the Processing status and has not been funded in a previous deposit, then two webhooks will fire:

• ach_return.created
• payin.returned

The payin.returned webhook will include the following indicators to let you know the details of the ACH return.

The payin and ACH return will be included in the next deposit to account for any fees associated to the ACH payin and the ACH return.

This scenario usually occurs for ACH returns where the return code time frame is within 2 banking days of processing the ACH payin.

ACH payin and ACH return in separate deposits

If the ACH payin has already been funded in a previous deposit, the only webhook received will be ach_return.created. The ACH return will be deducted from the merchant's next deposit along with any return fees.

The payin status will stay as Succeeded since the merchant already received the funds for the ACH payin.

This scenario usually occurs for ACH returns where the return code time frame is more than 5 banking days from processing the ACH payin.