This month’s Release Notes are focused on the great work performed by our Forth Development and Quality Assurance Teams to enhance your user journey. Get ready to elevate your CRM Experience with Forth!
What's New (6)
Credit Card Data Displaying on the Advance Page
This new feature addresses credit card data displayed on the Advance page. Merchant Cash Advances typically “re-pay” with ACH payments, which is the way 99% of Centrex Business Account users use the system, however, certain clients, collect “re-payments” via credit card transactions. For those accounts, CC payments are created daily by the system and processed like any other card payment. Formerly, the user needed to navigate back to the contact record to fill in the credit card form. We added a view for this under the “Funding Info” tab. modules/advances/view-funding.php. This should toggle on/off based on the “Repayment Method” selection.
Ytel Phone System Updates
Ytel to Get Contacts with Tasks in “X” Status (DPP-16853)
This new feature adds the ability to filter tasks on the task reports by contact status in addition to the other filters on the page. It adds "Contact Status" as a contact company filter to the query on the task reports page, which will enable further reporting and workflow capabilities with our task page
https://login.forthcrm.com/index.php?module=stats&page=task. It now displays as a multi-select dropdown option sorted by the file types enabled on the account and then the stage/status within that file type.
Ytel User Role (DPP-16696)
This new feature supports our mutual clients with Ytel and standardizes the Ytel setup process by providing a standardized user role with all permissions enabled they need to perform their setup activities using both FORTH CRM and the Ytel platform. This new Ytel user role will not be a billed user role nor will contacts with this user role be able to be logged into from a super admin/admin user from the edit user page in the CRM.
Settlement Voided Reason Reporting
This new feature provides settlement voided reason reporting within the settlement settings user interface. Previously, when voiding a settlement there was no option to provide a reason as to why the settlement has voided. Adding this ability allows additional reports to be created based on the reason why a settlement was voided. This enables broader reporting around settlements and enables the ability to customize voided reasons for the settlement.
Clixsign Documents to be Copied via Webhook
This new feature allows a user to transmit completed Clixsign documents via the tags system/webhooks from an affiliate to a backend, and have the underlying files copy between accounts. We added a new tag {CLIXSIGN_DOC_IDS}, which is a comma-separated list of document IDs to be transmitted, eg: {1538896, 1538892}. The system will now recognize these IDs and copy the completed Clixsign PDFs from the webhook origin account to the destination account. The PDFs will show up under the uploaded docs tab. No Clixsign metadata will be transferred in this process and only a PDF(s) will be received. The selected document will then be accessible in the destination account on the uploaded docs tab.
What's Improved (2)
Cancellation Page Refunds Bypass Gateway Hold
We made a crucial update to our system that enhances the security and efficiency of refund processing for consumers. In our continuous efforts to provide you with the best service, we have identified and addressed a potential loophole in the refund process. Specifically, we implemented a solution to prevent non-approved refunds from being processed when a consumer is on a Forth Pay Gateway Hold. Benefits include:
-
Enhanced Gateway Hold Security: Refunds for consumers on a Gateway Hold will only be processed after hold requirements are met and released.
-
Exclusion from NACHA Batch Process: Client refund transactions designated as "ACH Credit" will no longer be picked up by the daily batch process when the Hold Reason is "Banking Information Changed."
-
Improved Process for Dropped Client Refunds: If a consumer is on a process hold of "Banking Information Changed" and the client is dropped by the DRSP, the hold reason will not change until a Forth Pay agent reviews the consumer authorization and updates the hold to "Dropped by DRSP." This ensures a seamless process for client refunds.
CRM Controls for Return Codes
This update adds four ACH Client Debit Return codes for consumers on a gateway hold for Invalid Bank Accounts and Returned Payment Holds. The initial piece of this update involves the following two return codes:
-
R15 (Beneficiary / Account Holder Deceased)
-
R20 (Non-Transaction Account)
Previously, Forth Pay put the consumer on gateway hold with “Invalid Bank Account” for the following ACH Client Debit Return from the bank: 'R02', 'R03', 'R04', or 'R16'. With these updates, R15 and R20 return codes will now place the consumer’s account on hold with the reason - Invalid Bank.
The second portion of this update involves the following two return codes:
-
R08 (Payment Stopped)
-
R09 (Uncollected Funds)
Previously, Forth Pay put the consumer on gateway hold with “Returned Payments Hold” for when consecutive ACH Client Debit Returned as 'R01'. With this update, the system will place the consumer on hold after three consecutive attempts with the same code or a combination of these codes, with the reason - Returned Payments Hold. To make this transition smoother, we ask DRSPs to familiarize themselves with these specific return codes mentioned above that place their consumers into the Hold status.
API Updates (3)
Paginated Contact List via API
This new feature introduced a new contact lists endpoint that supports the ability to retrieve a paginated list of contacts from the FORTH system. Specifically, this feature enables 3rd party systems to pull list data in a paginated format, which enables further automation capabilities for clients who wish to build more of their processes on top of the FORTH API. This new endpoint will be limited to 100 contacts returning at a single time. This feature also applies to the CTX API. API Documentation on this feature is available by clicking HERE.
API User Selection Dropdown
This update allows users to see the service user's information for context when generating API keys for them on the REST API page in the Admin tab. In other words, it allows the user to know which user ID credentials are being generated. This feature modifies the “Select a User” dropdown on the REST API admin page to show additional information. The same information is shown for both service and standard users, and the use of the feature assumes the client has the Forth CRM API addon enabled and has access to the REST API page.
Settlement Offers for a Contact via API
This feature allows the CRM user to retrieve all settlement offers associated with a contact based on a specific Debt ID. This simplifies the process of accessing settlement offers for a contact. When a valid Debt ID is provided, the system now returns all associated settlement offers. and enhance API integration efficiency by reducing the dependency on pre-known offer IDs. Enhancing this aspect of the CRM system should significantly improve user satisfaction as well as system efficiency. API Documentation on this feature is available by clicking HERE.