Category: Added

What’s New

• We’ve made a few changes to how API tokens are generated within your environments. Effective immediately, newly generated tokens are presented to the user onscreen once and then masked forever—ensuring only the person creating the token can view and access it. With this is mind, make sure to copy and store API tokens securely when you generate them moving forward. Users with existing tokens will see that their current tokens are visible within the software. These tokens will be deprecated for all users in May 2026. We recommend replacing existing tokens with new ones before then.
• We added the ability to view email attempts that were sent to blocked email addresses within the Customer Communication Tool history. Previously, failures due to blocked email addresses were not shown within the history results. Now, attempts sent to emails that exist on an AWS SES blacklist are reported.
• We added the ability to change the frequency in which payments are made on a loan account. This new functionality is an addition to the change due date tool, and it can be used to change payment frequencies for specified time periods.
• We added the ability to provide metadata on more entities within LoanPro. You can now provide JSON-formatted metadata via the "metadata" field that’s included on the following entities:
  • Customer documents
  • Line of credit documents
  • Loan documents
  • Loan amount past due adjustments
  • Loan days past due adjustments
• We expanded our list of native Event-Based Notifications to include the ability to automatically send customized notifications when the customer profile is updated on a line of credit account. This event was previously only available for loan accounts.
• We added the ability to log a payoff payment on a loan account for an amount that is not equal to the total payoff. This change allows you to label a payment as payoff payment while over or under-paying the account balance. In the past, attempting to do so would automatically result in an adjustment transaction—either a credit or an advancement—to set the accounts final balance as zero. Now, you can determine whether you want an adjustment to be made.
• We added the ability to use array-type context engine variables within the Context Variables widgets of the line of credit Smart Panel. Previously, array-type variables were not supported. As an example, here’s an array-type variable that represents the balance of bucket ID 1:
  • (-> buckets-array :id1 :bucket-balance)
• We added the ability to create issuer configurations for Galileo Pro accounts within Secure payments. Now, Galileo Pro issuer configurations can be created via the Secure Payments UI and API to create and manage cards issued by Galileo.
• We added the ability to receive and download reports generated by Visa DPS Forward. Now, you can receive Visa DPS Forward’s “Transaction Interchange File” report and “Exception Transaction Settlement Detail Data” report. Reports are uploaded to a secure AWS S3 bucket, and a native webhook can be sent from Secure Payments to notify you of when a new file is uploaded and provide a link to the report. Hyperlinks to the reports are valid for 12 hours. Here’s an example of the webhook notification that’s sent when a new file has been uploaded to your account:

{
    "notification_type": "Visa DPS Forward Report Received",
    "report_type": "DPRMD",
    "institution_id": "59930000000",
    "file_name": "DPRMD-InstitutionID:59930000000-2025-04-13T19:09:15.523Z.json",
    "download_link": "https://linktodownloadthereportfroms3.io"
}

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