June 17, 2025


What’s New

  • We added the ability to view more card and line of credit information within the Customer Portal. You can now view an account’s next due date and next due amount within the portal.
  • We added the about to provide multi-factor authentication (MFA) via email within the Customer Portal. To enable this within your own portal, contact your LoanPro representative.
  • We added the ability to enable a Finicity iframe within the Customer Portal to capture banking insights from borrowers. To enable this within your own portal, contact your LoanPro representative.

What’s Fixed

  • We fixed an issue wherein incorrect AutoPay statuses were being displayed within the Customer Portal for line of credit accounts. Now, an account’s AutoPay status is set to ON if AutoPay processing is enabled on the line of credit account and there is currently a pending AutoPay.

June 10, 2025


What’s New

  • We added the Payment Frequency Change page as a selectable destination option when creating a step of an Agent Walkthrough. Now, your Agent Walkthroughs can send users to the Payment Frequency Change page and provide instructions on how to create a frequency change.
  • We added the ability to view Payment Frequency Changes within the Transactions Report of loan accounts. Now, you can see when a frequency change was applied to the account and the new frequency in which payments come due.
  • We added the ability to select whether the “Card balances updated” webhook that’s sent from Secure Payments provides the card’s “real” balance or “optimistic” balance. This update provides greater control over the card balance information you receive from Secure Payments via webhooks and helps prevent over-authorization due to rapid transaction attempts. This option only applies to cards issued via a Bring Your Own Issuer (BYOI) configuration, and the option is can be determined for each Issuer configuration via the Card balances updated webhook trigger option of an issuer’s settings. Here’s a description of each balance type and how they differ:
    • Optimistic balance. The optimistic balance is immediately returned each time an authorization is attempted—regardless of the authorization’s outcome. This balance is optimistic from the perspective of the lender; it is also conservative, meaning it assumes that all approved authorizations should subtract from the available balance of a card—even though that is not always the case. This may result in what might be a lower-than-actual available balance for the borrower. Ultimately, the optimistic balance helps prevent lenders from authorizing transactions when funds are not available.
    • Real balance. The real balance is set on a card after LoanPro has finished processing all queued messages on a card in the order that they were received. This balance is calculated asynchronously from the authorization path. However, it is continuously pushed to Secure Payments as it is updated in LoanPro—typically within seconds after an authorization occurs—so that the optimistic balance within Secure Payments is only used for authorizing transactions for a very small window of time. The real balance is the most accurate representation of the card’s balance because it is calculated based on all transaction history of the card.
  • We made some updates to the "kyc" field that’s associated with Bring Your Own Issuer (BYOI) configurations. We made the "kyc" payload parameter optional for the Create issuer account ↗ Secure Payments API request. Previously, this field was required. Additionally, the "kyc" field is no longer returned within the response of the Get issuer account ↗ request.
  • We added the ability to view the status of a card associated with a line of credit account within the customer portal. Previously, a card’s status could not viewed. The following statuses are viewable within the portal:
    • Active
    • Active – Reissued
    • Active – Virtual Only
    • Inactive
    • Blocked
    • Stolen
    • Lost
    • Expired
    • Cancelled
    • Frozen
    • Pending Activation
    • Pending Emboss

June 3, 2025


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"
}

May 19, 2025


What’s New

  • We added the ability to filter results within the Transaction History Report of a loan account by transaction type. Now, you can filter results by a combination of the following transaction types:
    • Scheduled payments
    • Forecasted payments
    • Payments
    • Charges
    • Credits
    • Advancements
    • Suspend interest transactions
    • Resume interest transactions
    • Amount past due adjustments
    • Days past due adjustments
    • Interest adjustments
    • Interest rate changes

What’s Fixed

  • We fixed an issue in which a processor selection was being ignored when creating enhanced funding transactions via the LMS API. Previously, if you attempted to create a funding transaction with a specific payment processor—specifically, a processor that was not already set as your default processor—the system would ignore the processor selection and use the default processor instead. This issue was only occurring if you also did not provide a Merchant Processor Group ID. Now, the API uses your selected processor to process enhanced funding transactions.

May 12, 2025


What’s New

  • We added an asterisk next to the ‘Due Interest’ value within the Calculated Account History Report to signify when an interest adjustment is present and affecting interest accrual. This addition provides greater visibility into how daily interest accrual is calculated. (Keep in mind that this is only a visual change. The added asterisk is not included in data exports.)

What’s Fixed

  • We fixed an issue that was restricting users from using the pre-configured loans feature to create $0.00 balance loan accounts even when a configurable payment schedule was present. Now, $0.00 balance loan accounts can be created via a pre-configured loan template.

May 5, 2025


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.

April 28, 2025


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

April 14, 2025


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.

April 7, 2025


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.

March 31, 2025


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.

What’s Fixed

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