Changelog

What's new

• We've released the first phase of an SCRA feature that helps card and line of credit lenders make adjustments to accounts when a borrower qualifies for SCRA. Now, you can calculate eligible balances at a reduced interest rate during the SCRA window and apply rate changes retroactively.

• We added the ability to combine the payment amount and convenience fee into a single total for bank card payments processed through Repay. Previously, the amount and fee were stored and processed separately. Now, they can be combined and stored in the additional information tab of the Secure Payments transaction.

• We adjusted the Multi-Factor Authentication enrollment and enablement process for agent users. Now, a custom email domain can be set to required to ensure accounts within that domain to use MFA. Users will still be able to opt-in to MFA individually in their account profile. If users remove MFA or never enabled it and are part of a required domain, they will be forced to enroll on their next login. This change deprecates the current Multi-Factor page settings in LMS.

• We have added new context engine variables for the line of credit accounts. Now, additional line of credit values can be retrieved using context variables:

  • rewards-current-points-balance shows the total number of rewards points.
  • credits-array.card-id shows the card ID associated with a credit.
  • status-due-interest shows the outstanding interest that is currently owed on the account.
  • status-due-fees shows the total of all outstanding fees that are currently owed on the account.
  • status-principal-balance shows the current outstanding principal balance on the account.
  • linked-loc-transactions-array shows certain transactions from other Lines of Credit linked to the original account.
    • This is an array variable. Transactions in this array are grouped by the parent account's billing cycles based on the transaction date. Only the current and previous billing cycles are shown.

What's fixed

• We fixed an issue that was restricting the Audit Trail note for webhook notifications to not post to a loan or line of credit account.

• We fixed an issue that restricted Payments Compliance Guardrails from being evaluated, and warning type Change Statement/Due Dates Guardrails from being bypassed within the UI.

• We fixed an issue restricting the line of credit late fee real-time calculator from running, and the charge posted to account event-based trigger from being sent.

• We fixed an issue and allowed the line of credits settledDate payment field to handle a wider range of scenarios. Previously, when payments were posted then settled in different payment periods, it would cause an error due to billing cycle validation. Now, line of credit payments will be processed as expected.

• We fixed an issue restricting line of credit interest charges breakdowns from being recorded on billing cycles.

What's new

• We adjusted the name and format of the "approved?" field that’s returned in the responses of the Secure Payments API requests to create a swipe transaction and create a swipe event. Previously, this field was labeled as "approved?", and it returned a boolean true or false value. This field is now labeled "approval-result", and it returns one of the following results:

  • approved if an action is approved (replaces true) or
  • declined if an action is not approved (replaces false).

What's fixed

• We fixed an issue that was restricting the “Portfolio linked to account” and “Sub-Portfolio linked to account” events from being logged within a loan account’s Audit Trail history. Now, portfolio linking history is captured as intended.

What's new

• We added the ability to determine whether agent users can only log in to LoanPro using a single sign-on (SSO) option, removing the ability to log in with a username and password. This currently requires configuration from LoanPro’s team. If you are interested in implementing this functionality, reach out to your LoanPro representative.

• We added the ability securely view sensitive card information—specifically, the last four digits of the primary account number (PAN) and the expiration date—directly within the LoanPro UI. This change only applies to cards created via an integrated issuing processor. Card’s within a Bring Your Own Issuer (BYOI) configuration do not have this functionality.

• We improved how swipe transaction memo information is captured and stored in LoanPro. Previously, the information within the “merchant descriptor” field of a swipe in Secure Payments was used as memo information within LoanPro. Now, memo information uses the “merchant name” field.

• We added the ability to select whether your Secure Payments and Connections accounts are billed before or after services are rendered. Previously, these accounts could only be pre-billed, requiring a paid balance before services. Now, services can be paid for at the end of your billing cycle instead.

What's fixed

• We fixed an issue that was causing manually exported CSV files in the Loan or Line of Credit Manager to duplicate unexpectedly. Exports are now generated once, as expected.

• We fixed an issue wherein the rule editor wasn’t recognizing certain context variables—mainly those of which that are associated with line of credit accounts—when validating a rule. Now, rules that reference the affected variables validate as expected. The following variables were affected by this issue:

  • Line of credit variables:
    • portfolio-array
    • status-amount-due-30
    • status-highest-credit
    • settings-id
  • Loan variables:
    • customer-custom-fields

• We fixed an issue that was causing certain Role-Based Access Control settings to display for users when they should have been restricted. The following RBAC settings have been updated and now function as intended:

  • Line of Credit > LOC Menu > Servicing > Notes/Alerts > Alerts
  • Line of Credit > LOC Menu > Account Settings > Setup > Buckets > edit
  • Line of Credit > LOC Menu > Account Settings > Setup > calculator enabled
  • Line of Credit > LOC Menu > Account Summary > Reverse Transaction
  • Line of Credit > LOC Menu > Account Summary > Edit Transaction
  • Line of Credit > LOC Menu > AutoPay > Schedule New AutoPay
  • Line of Credit > LOC Menu > AutoPay > AutoPay Status
  • Line of Credit > LOC Menu > AutoPay > Edit
  • Line of Credit > LOC Menu > AutoPay > Process

• We fixed an issue that was causing the “Last Current” data field to calculate incorrectly in some circumstances, affecting the Daily Snapshot Report as well as any references to the status-date-last-current context engine variable. This issue was occurring only if the calculator was run on an account at a time later than 6:00PM MT due to the UTC conversion. If that criteria was met, this field was incorrectly incrementing an additional day to the calculated value of this field. Now, this data field will calculate correctly, as represented by the date on which the value is calculated.

What's fixed

• We fixed an issue that was causing Checkbox-type Custom Fields to be displayed as ‘checked’ before user interaction—even if the default value for the field was set to ‘unchecked’. Now, these Custom Fields will remain unchecked as intended.

• We fixed an issue that was causing the Statement Generated Event-Based Notifications to fail. Notifications for this event now work as intended during Daily Maintenance.

• We fixed an issue that was restricting users from removing default Source Tracking settings for loan accounts. Previously, setting a default Source to ‘None’ was providing a system error. Now, default Sources can be set to ‘None’ as intended.

What's new

• We added the ability to provide a “preferred date” when creating a swipe transaction via the Secure Payments API, allowing you to control when a swipe transaction is applied to a line of credit account. The preferred date for a swipe can be determined by providing the new "preferred_date" payload parameter.

What's new

• We added support for mobile-friendly payment profile creation and card visualization iframes to the Customer Portal.

What's fixed

• We fixed an issue that was affecting the saved searches functionality in reports. Previously, saved searches filters were not being applied to generated reports, affecting reporting results. Now, saved searches work as intended.

• We updated how AutoPays initiated from the Customer Portal determine which payment processor to use. Previously, these AutoPays would use the payment processor associated with an ID of 1. Now, Customer Portal AutoPays use the default bank account payment processor as determined by your tenant settings.

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.

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

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

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.

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.

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.

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.

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.

What's fixed

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

What's new

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

What's fixed

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

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

What's fixed

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

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.

What's fixed

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

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.