What’s New
- We’ve expanded the swipe reversal functionality for line of credit accounts. Reversing a swipe transaction was previously only available within the UI, but now you can reverse swipes via the LMS API. To support this, we created the following endpoint:
/LineOfCredits({id})/Swipes({id})/Reverse
- We’ve added the ability to pull your environment’s variable rate index history via the API. To support this, we created the following endpoints:
/odata.svc/VariableRateIndexHistory
/odata.svc/VariableRateIndexHistoryGlobals
- We updated the information that’s stored when ACH payment transactions are made within Secure Payments to include bank account routing number. Previously, an ACH payment transaction would only include the bank account number and omit the routing number. Due to this, the batching process required a translation step in which Secure Payments would read payment profile tokens, translate them into account and routing number, and list both numbers within the batch file. With this change, batching is faster, and routing numbers are now visible in:
- NACHA batch CSV files
- responses from the GET NACHA batch transactions API request
- transaction information for transactions made via integrated ACH payment processors
Bug Fixes
- We fixed an issue that was causing bank account verification errors for those using the ValidiFi integration. Previously, a character limit constraint imposed on bank account numbers was leading to errors during verification. This constraint has been updated, ensuring bank accounts of all lengths are verified by ValidiFi properly.
- We fixed an issue that was restricting some users from receiving a password reset email when attempting to log in to the Customer Portal. This issue was specifically affecting users who had not yet verified their login email address. Now, if the password reset function is requested from a user that has not verified their email, the Customer Portal will first send an verification email.
- We fixed an issue that caused some API tokens to provide only
401 Unauthorized
responses even when their associated role settings granted access to endpoints. Now, LoanPro support team members can resolve API token issues if requested. Please reach out to your LoanPro support representative if an API token is not functioning properly.