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 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",
    "report_type": "DPRMD",
    "institution_id": "59930000000",
    "file_name": "DPRMD-InstitutionID:59930000000-2025-04-13T19:09:15.523Z.json",
    "download_link": "https://linktodownloadthereportfroms3.io"
}