Integration testing in production

The first merchant created in your production account should be your platform production account. This account will allow you the ability to run live payments and see the money move end-to-end, including a deposit to your account and also serves to provide critical data to Rainforest, including providing us the bank account you'd like us to use for residuals.

1. Review moving to production docs

Follow the steps for moving to production in order to integrate with the Rainforest production environment.

2. Create a new merchant

Use the manual onboarding flow in our Production Portal or your embedded integration (API or component) to create a new merchant that represents your platform. We recommend onboarding via the method you will be using as part of your MVP, so you can test your onboarding flow within production!

3. Submit your company data

Ensure that all the business data, (including legal name, tax ID, and address), your owner data (excluding SSN and DOB which can be skipped or completed with filler data), and your banking data (routing and account number) are accurate.

Please note: Unless otherwise specified, we will use the bank account associated with your test merchant account to deposit platform residuals on a monthly basis. If you would like to change the bank account for platform residuals, please email [email protected] with a voided check or bank letter.

We will perform a light review of the account data in compliance with KYC/KYB requirements, and approve your account or send you any questions we may have. When we approve your merchant, ensure statuses flowed through to your UI correctly and appropriate merchant communications were triggered.

4. Run test payments

Test multiple card and ACH payments for a variety of amounts

1. Ensure payment statuses are flowing correctly through your payments reporting tool
2. Confirm proper descriptors are showing up on the cardholder / bank account statement
3. Track payments through to deposit and ensure statuses are flowing correctly through your reporting tools

5. Refund test payments

Refund each payment using the manual flow in our Production Portal or embedded integration (API or component). We recommend using the method you will be using as part of your MVP to test your refund functionality.

Testing Best Practices

• Use varying amounts to ensure payments will not be flagged for fraud by your issuing bank
• Do not test payments too quickly to avoid velocity flags. Run payments in a similar cadence to your anticipated merchant behavior
• Use a few different card brands and/or ACH accounts if available
• Allow at least some payments to settle and deposit prior to refunding to test the full end to end behavior

🚧

Your production account is not designed for large volume testing. We recommend sandbox for this purpose.

FAQs

Why do I have to provide a bank account for a test merchant?

Since real money moves in production, we will need to deposit the test payment funds into your platform's bank account. This way you can see the money move from end-to-end!

How long will my test merchant take to be approved?

For a typical merchant application, we will provide a response within 2 business days (typically same day); however, if you notify your Customer Service Manager we can escalate this test merchant’s approval.