Posted on

March 10, 2025

What’s New

  • We updated the response structure of the Authorize a swipe ↗ API request to include new parameters. Now, the optimistically updated available balance and available advance balance of the card used to make the transaction are included in the new "card" object within the response.
  • We updated the response structure of the Create swipe event ↗ API request to include new parameters. Now, this request’s response returns a new "card" object that holds the available balance and available advance balance of the card associated with the event, as well as a timestamp of when those card balances were last updated.
  • We added a recency indicator to the body of the “Card balance updated” and “Swipe created” webhook messages that are sent from Secure Payments to make it easier to determine which webhooks are most recent. Now, these webhook includes a "recency-indicator" field that holds an integer value. A webhook with the highest incremented integer value is the most recent.
  • We added the ability to track, accrue, and redeem rewards points as credits on line of credit accounts within the UI and via the API. Rewards accrual configuration is customizable and can be set at the program level—allowing you to determine accrual rates and whether accrual accumulates on purchases, payments, or both. To begin offering rewards to your borrowers, reach out to your LoanPro representative.
  • We added the ‘Authorized User’ customer role as an option for credit reporting .csv exports.

Posted on

March 3, 2025

What’s New

  • We added the ability to view a card’s digital artwork within the customer portal. Now, a card’s artwork can be previewed on the Accounts page and shown in full within the card account by clicking the See Card Info button.
  • We added the ability to activate a new card within the customer portal. Now, users will be prompted to activate cards by providing their SSN or ITIN if a card has not yet been activated.
  • We added the ability to add past due adjustments to line of credit accounts. Now, you can create adjustments to increase, decrease, or zero out an account’s past due amount.
  • We added the ability to determine whether the Loan Manager or Line of Credit Manager is the default for your environment. This setting determines where a user is sent by default immediately after logging in.
  • We expanded the Configurable Payment Schedule feature to include the ability to determine a start date for interest only offset schedules. Previously interest only offset type schedules only allowed you to set a number of offset days. Now, you can also determine a specific day of the month for interest only offset schedules.

Bug Fixes

  • No new fixes.
Posted on

February 24, 2025

What’s New

  • We expanded the existing list of columns that can be selected within the line of credit manager. The following columns were added:
    • Percent Credit Utilization 
    • Billing Cycle Due Date
    • Remaining Minimum Payment
    • Linked Accounts Total Balance
    • Highest Credit
    • Remaining Statement Balance
  • We added the ability to create loans with a $0.00 balance as long as one of the following is met: the account uses an interest only loan calculation type or a configurable payment schedule exists and sets a determined payment amount. Previously, $0.00 balance accounts could not be created. 
  • We added the ability to export data from the Credit Utilization Report for line of credit accounts.
  • We expanded the list of customer roles to include “Authorized User”. Previously, a customer profile could have a role of “Primary”, “Secondary”, or “Additional”. Now, you can set a customer profile as the “Authorized User” of a loan or line of credit account.

Bug Fixes

  • We fixed an issue that was restricting configurable payment schedule imports from validating. Now, all configurable payment schedule imports validate properly.
  • We fixed an issue that was limiting the available email enrollment options a new Agent User was granted access to an environment. Now, all email enrollment options are displayed and available for new Agent Users.
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

December 9, 2024

What’s New

  • No new changes.

Bug Fixes

  • We fixed an issue that was causing loan document previews for PDF files to display as a blank screen. Now, all loan document previews load correctly.
  • We fixed an issue where documents were repeatedly uploaded and stored within a loan account via the Recovery Database Network (RDN) integration, causing duplicates. Now, documents uploaded via RDN are uploaded to accounts only once.