Forth Pay Account Agreement Field Reordering

The objective of this modification was to provide a better user experience within the "Bank Account" tab of the contact dashboard, by re-ordering bank account fields so users can easily and clearly enter a consumer's bank account information. 

The prior field order was confusing and mistakes were common when inputting bank account information. The fields have now been re-ordered and in some cases renamed. This update also makes all fields required to be saved, so an application cannot be submitted (via the "Save Bank" button) with missing information.

The information input here by the user pulls in and populates the appropriate tags in the ForthPay Custodial account agreement.

API Updates

Get All Advance Statuses Endpoint

This new feature enables a user to see all available advance statuses on a given account. This allows the user to better understand what statuses exist on the account and be able to update advances to new statuses based on the statuses available. In addition, Advance statuses that are added will now appear on subsequent API requests.

This was enabled by creating a new endpoint that now allows someone to access all advance statuses that have been configured on the account under "Advance Settings" https://login.setforth.com/index.php?module=advances&page=settings

Set Advance Status/Fund Advance

This new feature created a new API endpoint that enables a user to set and update the Advance status via the API and fund the advance if the correct status is passed based on the funded status from Advance settings > Rules/Permissions. This allows the user to control the Advance status flow without the need to be in the user interface (UI). API Documentation on this feature is available by clicking HERE. (PENDING HYPERLINK)

Delete Advance

This new feature expands your API capability to allow for the DELETE method to be used when specifying an advance. We added the “DELETE” method to be usable on the advance endpoint and to control how advances can be deleted as to whether or not they have been funded in the system.

This feature will not work with advances that are already funded or currently drafting payments. API Documentation on this feature is available by clicking HERE.

Locking and Unlocking of Advance Pricing

This feature provides users the ability to lock and/or unlock pricing at the API level for an Advance. This feature assumes that an advance exists in the system already, that a valid ID is passed, and that the Advance ID is being maintained by the user updating at the API level. This feature created an endpoint for the API.  API Documentation on this feature is available by clicking HERE.

Update "Contact" API Endpoint to Allow Budget Fields to be Passed

This update to the "Contact" API endpoint now enables clients to pass budget fields when creating and updating contacts through the API endpoints, enhancing their budget tracking and reporting capabilities. It also enables clients to retrieve the list of budget fields (via a new budget field listing endpoint) available for their account to better track and report budget-related information for each contact, customized for unique budgets per account. Overall, this update provides a more tailored budget management experience for clients. API Documentation is available HERE and HERE.

Enable/Disable ACH Drafting via the API

This feature allows a customer to set the ACH auto-draft status via the API. This would allow the customer to control whether or not an advance should be drafted automatically without needing to enable it in the UI. This was implemented by creating a new API endpoint for enabling and disabling the advance auto-draft status. If an advance has not been funded, the system does not allow an automatic draft to be enabled. API Documentation is available by clicking HERE.

API Status Change for Calls

This feature updates the call disposition to contact status mapping functionality as well as validates and returns the appropriate call_result based on the call_disposition value as part of the response. The changes include removing the "status_change" and "call_result" parameters from the POST request body, and logging and including the call_result in the response object.

This feature changes the way call dispositions work. We added a new endpoint to map call dispositions so as to copy the functionality, currently available in the UI, over to the API. Now you can map a disposition to a status change, and then set that disposition using the API.

API Documentation is available by clicking HERE.

API Content-Type Headers

This security feature implements a new header with the value of nosniff onto all API responses. This will enhance the security of the Forth CRM API by mitigating the risks associated with MIME-type confusion attacks.

This feature sets the X-Content-Type-Options header with a value of nosniff to disable MIME sniffing by browsers and user agents, and ensures that the implementation does not override the header with a different value or conflict with existing headers.

For more information, click HERE.

To access other monthly release notes, click Here.