Rainforest now supports sending platform specific context on the payin, which Rainforest can use for risk analysis when processing payins and determining if a payin is fraudulent or higher risk.
Card account updater (CAU) is a process that Rainforest runs with the card networks to keep the card information on stored payment methods up-to-date.
The Rainforest Payment Component now supports inputting international postal codes when the user inputs an international card number.
Rainforest now supports BIN lookup and returning BIN information to the platform when processing payments via the Payment Component.
Canceling a Pending merchant is now available via the Rainforest API or Platform Portal. Canceling a merchant will automatically decline the associated merchant application. This is a permanent action and can only be completed on merchants prior to their initial application submission.
Rainforest will be fully depcrating API versions 2023-01-01 and 2023-12-01 on November 12th, 2025. After this date, requests to these versions will no longer be supported.
Deposit timing for payments is configured per merchant and determines when the funds for a payment will be available to be deposited to the merchant.
When processing a payment with validated ACH, you can now perform a real-time balance check before processing the payment. A balance check helps minimize the risk of the payin resulting in an ACH return for insufficient funds (R01).
Rainforest now provides an Expected Deposit Date for each payment, which represents an estimate on when the payment will be included in the merchant's deposit.
Merchants that require additional verification for onboarding move to the Needs Information status when the information can be collected via the Merchant Onboarding Component. However, it is possible that additional information is required that cannot be collected through the self-service Merchant Onboarding Component. When this occurs, Rainforest will reach out to the platform via the provided underwriting email we have on file. We've updated how this flow is represented in our API and Platform Portal to make it more clear we need additional information and have reached out to the platform.
