Understanding onboarding
Understanding merchant onboarding in the Rainforest ecosystem
Rainforest requires your merchants be onboarded before they can collect payments. The merchant onboarding process at Rainforest is designed to quickly collect accurate data from your customers to complete required account verification and comply with rules and regulations prior to accepting payments.
The Rainforest ecosystem has two entities, Merchant and Merchant Applications, to represent your merchant and their status within Rainforest.
- A merchant is a business that your platform will enable to take payments. It represents a single legal entity, such as an LLC with a specific tax ID number.
- A merchant application represents information about the business that goes through the underwriting process by Rainforest. A merchant's information might change over time, such as phone number, address, or bank account, and changes would be approved through a new merchant application.
A merchant is identified by the merchant_id
in the Rainforest ecosystem. The prefix for a merchant_id
is mid_
on Production and sbx_mid_
on Sandbox.
A merchant application is identified by the merchant_application_id
in the Rainforest ecosystem. The prefix for a merchant_application_id
is app_
on Production and sbx_app_
on Sandbox.
Onboarding process
The onboarding process consists of 3 phases:
- Merchant creation and application submission: the merchant is created, the required information is collected in the merchant application, and the application is submitted for approval.
- Account verification: the information provided is reviewed to ensure compliance with any application rules and regulations, Rainforest policy, and for accuracy. Rainforest may require additional verification before a decision can be made.
- Decisioning: The merchant application is either approved or declined. If the application is approved, the merchant becomes Active and is immediately ready to process payments.
Application requirements
Once a merchant is created with their initial application, the merchant will be in the status of Pending and the application in the status of Created. The application will move to In Progress when the merchant begins entering their information into the application, indicating they've started the process.
Rainforest must collect certain information about your merchant in order to underwrite and approve your merchant for payment processing. Head over to the merchant onboarding requirements guide for details on all requirements per organization type.
Account verification
Once the merchant submits their application, the application status will move to Processing. Rainforest will review the application and determine next steps. If additional verification is required, the application will move to Needs Information or In Review. Head over to the additional verification for merchant onboarding guide for details on the additional verification process.
Decisioning
Once the application is submitted, or re-submitted after entering the Needs Information status, Rainforest will make a decision on your merchant.
If Rainforest approves the merchant application, the application will move to Completed and the merchant will move to Active. The merchant is now ready to process payments.
If Rainforest declines the merchant application, the application will move to Declined and the merchant will move to Canceled. The merchant will no longer appear in the Merchants report in the Rainforest Platform Portal.
Onboarding integrations
Rainforest offers three options to onboard merchants:
- Merchant Onboarding Component (Recommended): Integrate Rainforest's low-code embeddable component into your platform, allowing merchants to securely submit their information directly through your software.
- Rainforest Platform Portal : Enter merchant information manually through the Rainforest Platform Portal, suitable for low-volume onboarding or administrative purposes.
- Rainforest API : Utilize the API to programmatically submit merchant data, providing flexibility for custom workflows and integrations.
Each integration option ensures compliance with necessary verification and regulatory requirements before merchants can begin accepting payments.
Auto-cancelation of merchants
Open applications of 120 days
Rainforest will automatically cancel merchants that are in the status of Pending or Onboarding for more than 120 days, based on the created date of the merchant.
The result of this process will move the merchant to the Canceled status and the associated open application to the Declined status.
You should listen to the merchant and merchant application webhooks to know when Rainforest automatically closes an application. The following webhooks will trigger:
merchant.canceled
merchant_application.declined
Once the application is closed, it will no longer appear in the Merchant report in the Platform Portal.
The platform can create a new merchant if the merchant would like to re-apply for payment processing. Because the previous application was closed and no longer appears in the Platform Portal, you will be able to use the merchant name again when creating a new merchant.
Statuses
Merchant statuses
The merchant status is the descriptor of the current status in the life cycle of a merchant. Indicating if they are onboarded, can accept payments, and receive deposits.

Merchant application statuses
The merchant application status is the descriptor of the current status in the life cycle of a merchant application. Indicating the status of the merchant application through the onboarding and underwriting process.

Merchant status | Merchant application status | Description | Action owner | Platform action |
---|---|---|---|---|
Pending | Created | The merchant and merchant application have been created, but the merchant has not began filling out the application. | Merchant | Follow up with the merchant to help them complete their application. |
Pending | In Progress | The merchant is in the process of filling out their application. | Merchant | Follow up with the merchant to help them complete their application. |
Onboarding | Processing | The merchant has submitted their application and it is going through standard underwriting. | Rainforest | No action required. |
Onboarding | In Review | The merchant requires an additional manual underwriting review. | Platform | Rainforest has reached out to the platform via the underwriting email provided for the additional requirements. |
Onboarding | Needs Information | The merchant requires additional underwriting review that can be submitted via the self-service verification process. | Merchant | The merchant should be directed to the Merchant Onboarding Component to provide the additional requirements. - If a merchant requires manual underwriting review AND self-service verification, there will also be an email sent to the platform and an indicator in the Rainforest Platform Portal. |
Canceled | Declined | The merchant was canceled before becoming active. - Open merchant applications that are 120 days old are automatically canceled. | -- | No action required. |
Active | Completed | The merchant application is approved and the merchant can process payments. | -- | No action required. |
Suspended | Completed | The merchant has been temporarily suspended and cannot process payments or receive deposits. | -- | No action required. |
Deactivated | Completed | The merchant has been permanently deactivated and cannot process payments. | -- | No action required. |
Updated 3 days ago