What’s New

• We added the ability to add Click-Through Alerts to line of credit accounts. These alerts are presented to the user when they open a line of credit account and they’re rule-based, granting you control over when they’re presented to your users.

What’s Fixed

• We updated the defaults regarding email notification enrollment for newly created agent users. Previously, agent users were enrolled in all email notifications by default when they were created. Now, agent users need to be enrolled manually.
• We fixed an issue in which clicking the ‘See More’ button on a customer profile within the Smart Panel would do nothing. Now, clicking that button will take you to the customer’s profile as intended.
• We fixed an issue in which clicking the ‘Make a Payment’ button on the Statements page within a line of credit account would do nothing. Now, clicking that button will take you to the payment creation page as intended.
• We fixed an issue in which the apply date selection popup window was not being fully displayed when creating a notice-type note on a line of credit account. Now, the date selection window is being displayed correctly and in full.

What’s New

• We added the ability to add notice-type notes to line of credit accounts. Previously, these notes were only available on loan accounts. Notice-type notes display on screen as a pop-up message when an agent opens an account.
• We added the ability to view the history of webhooks that have applied to a line of credit account. Within Servicing > Notes/Alerts > Webhooks, you can now view webhook information—such as the method, payload body, and response—and resend webhooks manually.
• We added the ability to reissue a card directly from a line of credit account. Now, agents can start the reissue process within an account and set the new card’s expiration date.
• We also added the ability to reissue a card via the LoanPro API. Now, cards can be reissued via the /Cards({id})/reissueCard endpoint.
• We added the ability to support multiple disputes on a single swipe transaction. This change was made to support scenarios such as representment.
• We added a “Result” column to swipes’ information to display the most recent result of the swipe transaction whether the swipe was authorized, voided, or settled. To view this information, open a line of credit account within LMS and select a swipe transaction. Next, click View Swipe History at the bottom of the page.
• We added dispute-chargeback-reversal as a new option for the Create swipe event ↗ Secure Payments API request. This swipe event is used when a chargeback is reversed on a previously disputed transaction.
• We updated the naming convention for the “ACH funding – gateway merchant ID” field on Repay processor configurations. This field is now labeled as “Merchant ID”.

What’s New

• We added the ability to quickly and easily copy the entirety of the payload provided by the issuer when a swipe is created within Secure Payments via a clipboard icon. This information and icon is found within the Secure Payments UI by navigating to Swipe History > selecting a swipe > Events then clicking the information icon for an event.

What’s New

• We added the ability to provide a metadata object to transactions made on loan and line of credit accounts. Now, the "metadata" field is included as an option when creating or updating transaction information. Please note that the "metadata" field does not allow for pre-serialized JSON. The "metadata" field is now available for the following transactions:
  • Loan accounts
    • Payments
    • Charges
    • Advancements
    • Credits
    • AutoPays
    • Funding transactions
  • Line of credit accounts
    • Payments
    • Charges
    • Advancements
    • Credits
    • AutoPays
    • Funding transactions
    • Swipes
• We added the ability to provide immediate destination and origin information when creating and using a Nacha payment processor configuration. Previously, Secure Payments used a Nacha processor’s routing number value as the immediate destination and the company ID as the immediate origin as defaults. Now, immediate destination and origin is configurable.

What’s Fixed

• We fixed an issue that occasionally caused the Automations tab of the Smart Panel to display as empty. Now, this tab displays available Quick Actions more reliably.

What’s New

• We updated the loan_status_archive database table to include a new effective_interest_rate column that stores a loan’s current, daily interest rate. This rate is updated daily during LoanPro’s Daily Maintenance process, and it considers the loan setup rate, schedule roll configuration, interest rate changes, and interest suspensions.
• You may notice some new fields and settings appear in the platform related to rewards. These changes are part of an early rollout and won’t impact your tenant or operations. No action is needed on your part. We just wanted to keep you informed as we build toward a full rewards solution.

Bug Fixes

• We fixed an issue wherein recurring charges were not being applied to line of credit accounts when expected. Previously, recurring charges that use “Payment Reversed” or “Swipe Created” event types as a trigger were not always resulting in a charge being applied to a qualifying account. Now, all recurring charges are applied to line of credit accounts as expected.

What’s New

• We added a new available widget to loan and line of credit Smart Panels. This new widget displays the associated customer’s payment profile details—including how many payments have been completed, how many have been reversed or failed, and how many have consecutively reversed or failed.
• We added the ability to retrieve robust payment profile history information via the API. The /PaymentAccounts({id})/details endpoint now returns payment profile’s history of failed and successful payments as well as the status of each payment. Here’s a list additions that were made to this endpoint:
  • Each payment result includes a "comments" field which holds a payment failure reason
  • Each payment result includes a "peStatus" field which holds a number that corresponds to a payment status:
    • "1" – Success
    • "2" – Reversed
    • "3" – Edited
    • "4" – Failed
  • Each response includes new summary fields that provide insights into a payment profile’s history. The following fields are now included:
    • "total" – the total number of payments that have been attempted
    • "totalSuccessful" – the total number of successful payments
    • "totalFailed" – the total number of failed payments
    • "consecutiveFailed" – the number of consecutive failed payments
    • "totalReversed" – the total number of reversed payments
    • "consecutiveReversed" – the number of consecutive reversed payments
• We made a number of enhancements to the Customer Portal:
  • We added the ability to enable Multi-Factor Authentication (MFA) for borrower login. To enable MFA for your own portal, reach out to your LoanPro representative.
  • We extended session timeouts and added session extensions. Previously, a session would timeout after 20 minutes of inactivity. Now, login sessions expire after 30 minutes of inactivity, with a session renewal message presented to the user one minute prior to a timeout.
  • We added a ‘Sign Up’ flow to all portals. Now, new borrowers can sign up for portal access by providing their email address. A notification is sent to the provided email address requesting the user to set a password. The new signup flow is accessed by navigating to {yoururl}.onlineaccess.io/#/signup .

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.

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.