Changelog

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.

On January 21, 2025, Rainforest will begin automatically closing merchant applications that have been open for more than 120 days, based on the created date of the application. The result of this process will cancel the pending merchant and decline the open application.

We've improved the language in the Merchant Onboarding Component for the phone number requested. This phone number is visible to your merchant's users and appears on the payment descriptor for card payments.

Rainforest now supports processing payments with a validated ACH bank account. ACH validation is the process of validating a user's bank account to help avoid data entry errors and reduce fraud when a user wants to pay by bank.

Rainforest will automatically onboard all your merchants to 3DS making it easier for you to integrate the 3DS flow into your Payment Component.

We've updated how the Merchant Onboarding Component displays when an application can only be viewed and not edited. The review page now displays as a single page with all the information from your merchant.

We've added three new review reasons to the additional verification for merchant onboarding flow. Merchants can now self-service provide documents for business verification and financial review.

Rainforest now supports collecting a signature when processing payments with terminal devices and displaying the digital signature in various reporting components.

We've updated our merchant onboarding requirements for Public Corporation and Government representatives to not require Date of Birth or Social Security Number.