New 3DS requirements for Visa
Visa's 3DS integration now requires additional fields that were previously optional. In order to receive 3DS protection on Visa payments, the following billing contact fields will need to be set in the Create payin config request when threeds_mode
is ATTEMPT
.
Update a merchant's billing profile
We've added the capability to update a merchant's billing profile. This feature is available via the Rainforest Portal and the API.
Disable Portal users
We've added the capability of disabling users in the Portal.
ACH return flow improvements
When an ACH payin is returned before it is available for a deposit, the current flow will move the payin status from Processing
to Succeeded
when the ACH return is created (explained here).
Export payment report and deposit report
Both payment report component and deposit report component now offer the ability to export data to a comma-separated values (CSV) file!
Apple Pay for payment processing
Apple Pay in the Rainforest payment component is now available!
Easier onboarding when merchants need to provide more information
During onboarding, if a merchant submits an application that has a problem and needs to be fixed, you can now do that in the Rainforest Portal or allow your merchants to fix it themselves using the merchant onboarding component.
Portal shows merchant's latest application status
We are releasing an update to the Merchants view in the Rainforest Platform Portal to give more visibility into the merchant's latest application.
Better name for risk refusal code
When a Payin is blocked by Rainforest because it appears fraudulent, we will be changing the refusal_code
returned by our API from RAINFOREST_RISK_DECLINE
to RISK_DECLINE
.
Clearer wording in onboarding component
This week, we launched a change to the Onboarding component to clarify the questions around the merchant's estimated payment activity.