Category: Added

Posted on

February 10, 2025

What’s New

  • We added the ability to provide a nickname when creating a payment profile via the Customer Portal.

Bug Fixes

  • We fixed an issue in which statuses were not updating for some payment transactions processed via ACHQ. Now, all ACHQ payment transactions are updating normally.
  • We fixed an issue that was causing customer generation code values (Jr., Sr., IV, etc.) to be set as “none” when creating cards via Visa DPS. Now, generation codes are not updated when creating a card.
Posted on

February 3, 2025

What’s New

  • We expanded the Smart Panel customization options to allow users to customize Smart Panels for line of credit accounts. Previously, Smart Panel customization was only available on installment loan accounts. Now, you can add or remove the following widgets from view on line of credit accounts:
    • Smart Checklists
    • Portfolios
    • Linked Accounts
    • Notes
    • Customers
    • Action & Results
    • Documents
    • Source Tracking
  • We increased the maximum allowable credit limit for line of credit accounts from 10,000,000.00 to 99,999,999,999.99. 
  • We expanded the card management options available when updating a card’s status via the LoanPro API. The Manage card status request now provides the following card status options:
    • Pending emboss
    • Pending activation
    • Active – reissued
    • Active – virtual only
    • Active
    • Inactive
    • Lost
    • Stolen
    • Expired
    • Blocked
    • Canceled

Bug Fixes

  • We fixed an issue that was allowing users to create cards for issuers that had been inactivated within Secure Payments. Now, cards cannot be created for inactivated issuer accounts. 
  • We updated the default active/inactive status for line of credit document uploads. Previously, documents uploaded to a line of credit account defaulted to inactive. Now, documents default to active.
Posted on

January 28, 2025

What’s New

  • We added a new Smart Quick Queue functionality to the Line of Credit Manager which allows you to create dynamic queues from search results. As accounts qualify or disqualify for the criteria set within the search results, they move in and out of the queue. 
  • We added the ability to provide metadata when creating payments on loan and line of credit accounts via the LoanPro API. The payloads of those requests now include an optional "metadata" field. When used, this information is retrievable when using GET requests to pull payment information.
  • We increased the number of available decimal places for loan interest rates from six to seven.
  • We added a new data visualization to the Credit Utilization Report within line of credit accounts. Now, an account’s credit utilization, total balance, total credit limit, and total linked account balances are shown on an interactive graph.
  • We added new payload parameters to the Secure Payments API request to create a card: "expirationDate", "embossProductId", and "digitalWalletCardArtId". These fields were added to support the standards of integrated card issuing partners. 
  • We added the ability to determine the shipping method of newly created physical and hybrid cards for all integrated card issuer partners. This addition includes new shipping method payload parameters for the create card API request as well as new dropdown options available when creating a card via the UI.
  • We added a new functionality to line of credit accounts that allows you to determine whether payments should immediately increase the account’s available credit or wait until transactions are settled. This feature is optional and must be configured by a LoanPro representative. Reach out to your account manager to learn more.

Bug Fixes

  • We updated how the credit reporting functionality handles dates and times. Previously, this tool was generating reports using UTC as the time zone. Now, the time zone selected within your tenant settings will be used instead.
  • We updated how special characters are handled within the Metro2 credit reporting integration. Previously, the Consumer Account Number field could include dashes, but now they are no longer included. This change was made to adhere to the standards set by the Consumer Data Industry Association (CDIA). Here’s an example of how account numbers are displayed before and after the update:
    • Before: 1-42361-1
    • After: 1423611
  • Big news for our Rules Editor power users: We fixed a bug that was causing the Rule Editor to render as a blank page. Now, the editor loads as intended.
  • We fixed an issue that was restricting some mailhouse notifications from being sent. This issue was only affecting line of credit accounts that were using Dynamic Trigger notifications. Now, all mailhouse notifications are sent correctly.
Posted on

January 14, 2025

What’s New

  • We added two new payload parameters to the Secure Payments API request to create a card: "tos_timestamp" and "kyc_passed_timestamp". These fields are optional and were added to support the standards of integrated card issuing partners.

Bug Fixes

  • No new fixes.

Posted on

December 16, 2024

What’s New

  • We added the ability to update the background image of existing cards via the Secure Payments API. Previously, a card’s background image could only be set when creating the card. Now, you can update an individual card’s background image, as well as update the background image for all cards within a specific card program.
  • We removed the ability to provide a PAN (Primary Account Number) when creating a card via the Secure Payments API. This is a breaking change. If the "pan" payload parameter is included in the request to create a card moving forward, the request will result in a 404 Not Found error.

Bug Fixes

  • No new fixes.
Posted on

November 25, 2024

What’s New

  • We added a new data field to card information that stores when a card was activated to improve card data transparency. Activation date information is stored within a new "activation_date" field, which can be pulled via the /card-details/for-uuid/{card-uuid} ↗ endpoint of the Secure Payments API. Please note that this information is only available for cards created after this release—previously created cards will not include the "activation_date" field.

Bug Fixes

  • We fixed an issue that was causing the AutoPay Processing Status toggle on the line of credit AutoPay page to sometimes display an “off” status even when AutoPay processing was enabled for the account. Now, the Processing Status toggle correctly displays the status of AutoPay processing.
  • We fixed an issue that was causing the value of the linked accounts effective balance in the line of credit daily archive to display as zero. Now, this value is calculated and displayed correctly.

Posted on

November 19, 2024

What’s New

  • We added the ability to access Agent Walkthroughs directly via URLs, making it possible to jump into a Walkthrough without navigating to the Agent Walkthroughs page of a loan account. This addition also includes the ability to forgo the Walkthrough’s rule validation when using a direct URL.
  • We expanded the line of credit AutoPay renewal functionality to automatically change a renewed AutoPay’s status from “Failed” to “Pending”, ensuring that renewed AutoPays are queued for reprocessing and eliminating the need to do so manually.

Bug Fixes

  • We fixed an issue wherein transaction metadata was not being included in transactions processed by Authorize.net processor configurations. This affected only Authorize.net processors that use the V2 option. Now, transactions processed by Authorize.net with the V2 setting will include transaction metadata.
  • We updated how the system generates and displays the amount values for remaining minimum payment and remaining statement balance in the UI and API responses. Instead of calculating the balances manually in LMS, the system now references the Line of Credit Daily Archive database table (line_of_credit_daily_archive). This change ensures the accuracy of the values moving forward.
Posted on

November 11, 2024

What’s New

  • We added the ability to get linked account information via the API, making it easier to view due dates, due amounts, and more. To support the functionality, we created a new endpoint:
  • We expanded the AutoPay functionality for linked line of credit accounts to include a new “Current Due Amount” option. This option calculates a sum of the currently due and past due amounts for all linked accounts, making it easier to allow borrowers to schedule payments for linked accounts that have a combination of current and past due accounts.
  • We added the ability to securely upload, store, and download encrypted files within the LoanPro UI, eliminating the need for a separate SFTP site. Files are stored within the Report File Hub tab of the Administration Reports. 
  • We introduced a new rule validation tool that allows you to write a Clojure rule and check whether a specific account matches the rule criteria. This feature greatly simplifies the process of writing Clojure rules and removes the guesswork of determining whether a rule applies to the intended account(s).

Bug Fixes

  • We fixed an issue that was causing AutoPay errors on accounts that use the “split payment” function to apply payments to multiple linked accounts. Previously, the AutoPay would apply correctly to the main line of credit account but would run into errors when applying to linked accounts. Now, split payment AutoPays apply payments to all linked accounts successfully.
  • We updated the order in which disputes are ordered within the UI. Disputes are now ordered by date instead of ID, ensuring the most recent disputes are listed first.
Posted on

November 4, 2024

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:
  • 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:
  • 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.