Customer Portal NACHA compliance

We have expanded the customer portal's NACHA compliance. Now, the customer portal has expanded payment flexibility, enhanced compliance through dynamic disclosures, and improved data synchronization with the Loan Management System.

Payments & Funding

• Expanded Payment Methods Users can now add and utilize credit/debit cards and savings accounts when creating payment profiles.
• Smart "Extra Towards" Logic One-time payments now automatically respect and apply the tenant-level default settings for the "extra" portion of payments.
• Duplicate AutoPay Warning To prevent accidental double-billing, users now receive a warning prompt if they attempt to set up an AutoPay schedule while an active AutoPay already exists.
• Calendar Visibility The "Make a Payment" flow now visualizes the Next Due Date directly within the calendar date picker.

Compliance & Disclosures

• Separated Disclosure Workflows Payment disclosures can now be configured separately for one-time payments and recurring AutoPay setups, allowing for distinct legal language per transaction type.
• PDF Export Upon the successful processing of a transaction, users can now export the approved disclosure as a PDF for their records.
• Dynamic Disclosure Variables Disclosures are now smarter and can dynamically pull specific transaction details into the text. The supported variables include:
  • Account ID
  • Payment Amount
  • Payment Amount Type
  • Process Date
  • Disclosure Date
  • Payment Account Last 4
  • Payment Account Routing Number
  • AutoPay Frequency
  • AutoPay Name
  • AutoPay Recurrences
  • Company Name
  • Payment Account Type + Last 4

System Logic & Data Sync

• LMS Synchronization for Deletions When a user deletes a payment profile in the portal, the system now sets that profile to Inactive in the Loan Management System.
• Instant Balance Refresh Account balances will now automatically refresh after a payment is submitted.
• Origination Breakdown Views for loan origination transactions show a detailed breakdown of the transaction components.
• MFA & JWT Logic For portals utilizing JWT (JSON Web Token) login methods, the Multi-Factor Authentication settings menu is now disabled to prevent configuration conflicts.