Mercury Network 3.0 - January 14, 2021 Update
This update (the first update to Mercury Network in 2021) contains enhancements throughout the platform. See the blog post here.
New Features
- Archiving
With this release, we put finishing touches on Mercury Network's ability to archive orders which have no activity for 18 months. By moving these historical orders to a different database, the platform's performance and efficiency will be significantly enhanced, which paves the way for several exciting features to come in 2021.
Mercury Network Payments - Vendor Onboarding
- If our payments processor can't verify a vendor's identity from the minimum information requested, they will ask for additional information, including the potential for requesting a copy of a government-issued ID. Vendors who have entered information which needs further validation can now edit their checking account and easily upload needed identity documents. This will enable verification so they're fully prepared for the upcoming Payments feature.
See the FAQ here. - When signing up for Mercury Network Payments, if an invalid Tax ID has been entered, users will now see a message indicating that a valid Tax ID is required, rather than an "unexpected error".
Retiring "XSites"
- We continued the process of removing references to the no-longer-used XSites. This includes behind-the-scenes code changes, as well as text changes to some email templates and updates to URLs related to the VMP Client portal.
Borrower Payments
- When using the Make a Payment page, borrowers who experienced a transaction error saw an error message which contained a grammatical error. This has been corrected.
- We made adjustments to ensure borrowers can search and find their address when the new Make a Payment link is used. Specifically, this change helps the borrower access their order directly when the link is sent to them from an AMC.
RealView
- When ordering a RealView report within Mercury Network, the Sales Price in the Mercury Network order will be correctly transmitted to RealView.
User Permissions
- There were cases when permissions for new users were not being saved. This has been corrected by requiring the profile to be saved prior to making changes to the notification and preference settings.
Action Required
- To help us investigate possible issues, we have added logging for changes made in the Action Required folder. You won't notice any difference, but this will assist us when troubleshooting is required.